# Setting up Cloud Connected PSTN for Webex Calling Systems: Webex Calling For Webex Calling customer administrators configuring location PSTN connectivity in Control Hub. Canonical: https://warmtransfer.net/guides/webex-calling-ccp-pstn-setup Last verified: 2026-09-30 Each Webex Calling location has only 1 PSTN option[^44]. An organization can use a different PSTN solution per location, including Cisco Calling Plans, Cloud Connected PSTN, and Local Gateway[^38]. ## Before you start - Confirm that each location will have exactly 1 PSTN connection type, as Webex Calling supports only 1 PSTN option per location[^44]. - Different locations within the same organization can use different connection types, such as Cisco Calling Plans, Cloud Connected PSTN, or a Local Gateway[^38]. - Customer administrator credentials are required because changing a PSTN connection involves signing an E911 agreement[^15]. - See also [Setting up a Webex Calling location](https://warmtransfer.net/knowledge/webex-calling-location-setup). ## What changes by situation - Which PSTN connection will this location use? Cloud Connected PSTN with integrated number ordering; Cloud Connected PSTN with external number procurement; Cisco Calling Plan; Premises-based PSTN through a Local Gateway. - Is the location new, or does it already exist in Control Hub? New location being created now; Existing location being updated. - Which country is the location in? United States or Canada; India; Other country. ## Step 1: Choose the PSTN model for each country or location ### Do Choose among Cisco PSTN (Cisco Calling Plan), Cloud Connected PSTN (CCP), or Premises-based PSTN (Local Gateway) for the location[^51]. Cisco positions Cloud Connected PSTN for customers seeking cloud PSTN from a Cisco CCP partner or when the Cisco Calling Plan is unavailable in that location[^6]. Choose Premises-based PSTN when retaining an existing PSTN provider or connecting non-cloud sites[^47]. Cisco markets Cloud Connect as delivered through more than 60 Certified Calling Providers across more than 90 markets[^5]. When selecting a CCP provider in Control Hub, Cisco recommends selecting an option that displays "Order numbers now" to use integrated CCP[^45]. Integrated CCP enables procuring and provisioning numbers inside Control Hub[^33], whereas non-integrated CCP requires procuring numbers outside Control Hub[^41]. ### Verify Suggested check: Confirm that each planned location has exactly the chosen PSTN option documented. ### Rollback Suggested rollback: Update internal planning records to change the intended connection type before applying changes in Control Hub. ## Step 2: Confirm connection prerequisites **Cloud Connected PSTN with integrated number ordering** ### Do Verify that a customer administrator is available to perform the setup, as changing a PSTN connection requires signing an E911 agreement[^15]. ### Verify Suggested check: Verify that the provider supports the target country and displays the "Order numbers now" capability in Control Hub[^45]. ### Rollback Suggested rollback: Select an alternate provider if the preferred vendor does not offer integrated ordering in that country. **Cloud Connected PSTN with external number procurement** ### Do Procure phone numbers directly from the CCP partner outside Control Hub prior to configuration[^41]. Ensure the numbers are formatted in E.164, though United States numbers may also use national format[^43]. ### Verify Suggested check: Verify that a comma-separated list of partner-provided numbers is prepared for entry[^42]. ### Rollback Suggested rollback: Request order cancellation or number changes directly with the third-party carrier. **Cisco Calling Plan** ### Do Confirm that the partner is an authorized Webex Calling partner that accepted the Webex Calling addendum and that at least 1 committed Outbound Calling Plan license has been purchased[^11]. ### Verify Suggested check: Confirm the location is new, hosted in a compatible data center, and located in a supported country so the PSTN option becomes visible. ### Rollback Suggested rollback: Remove or unassign the purchased calling plan licenses through your partner portal if not proceeding. **Premises-based PSTN through a Local Gateway** ### Do Create a trunk for the location in Control Hub with a name of up to 24 characters, and register the Local Gateway[^46]. Registration-based trunks require at least IOS XE 17.6.1a, while certificate-based trunks require at least IOS XE 17.9.1a[^56]. ### Verify Confirm that the registered gateway displays a green dot beside its name in Control Hub[^46]. ### Rollback Ensure other locations are not sharing the Local Gateway before attempting removal, as a location with a Local Gateway cannot be deleted while that gateway is used by other locations[^46]. ## Step 3: Assign the connection to the location **New location being created now** ### Do Navigate to Management > Location in Control Hub and add the location[^2]. Click Save, select the option to add numbers now, choose the PSTN option (and provider if using CCP), and select whether to activate numbers now or later[^2]. ### Verify Confirm the Connections tab on the Control Hub PSTN page lists the location[^14]. Confirm under Calling > PSTN Connection on the location that the selected connection appears[^55]. ### Rollback Suggested rollback: Access the location's Calling tab and choose Manage under PSTN Connection to select a different option, noting that the bundled cloud PSTN option may no longer appear once another option has been saved. **Existing location being updated** ### Do Review all telephone numbers in the location before making changes; delete or move any numbers no longer owned or not being migrated, and ensure the non-portable numbers list is empty[^50]. Open the location's Calling tab, click Manage under PSTN Connection, click Continue to acknowledge risks, choose the new option, and click Save[^55]. Note that Cisco PSTN is available only for new locations and cannot be assigned to an existing location[^13], and changing an existing location to Cisco PSTN is unsupported in Japan[^36]. ### Verify Confirm that the PSTN Connection field reflects the new selection once complete[^55]. During the transition, verify that existing numbers continue functioning even though adding, deleting, or moving numbers is temporarily blocked[^26]. ### Rollback Click Manage under PSTN Connection to restore the previous provider or trunk setting[^55]. ## Step 4: Apply the India PSTN zone where required **United States or Canada** ### Do Suggested check: Proceed directly to number provisioning, as PSTN zones apply only to locations in India[^31]. ### Verify Suggested check: Confirm that no zone selection screen is presented during configuration[^31]. ### Rollback Suggested rollback: No zone settings exist to revert for this country group. **India** ### Do Select Cloud Connected PSTN on the Connection Type screen, select the provider on the Select a Provider screen[^30], and assign a PSTN zone on the Select a Zone screen to comply with toll bypass regulations[^31]. ### Verify Verify that the PSTN Zone drop-down list displays the assigned zone under Calling Connection > PSTN Connection > Manage[^32]. ### Rollback Change the zone selection under Calling Connection > PSTN Connection > Manage using the PSTN Zone drop-down list[^32]. Note that number portability between different PSTN providers is not supported in India, so provider changes require advance confirmation with both providers[^29]. **Other country** ### Do Suggested check: Proceed directly to number provisioning, as PSTN zones apply only to locations in India[^31]. ### Verify Suggested check: Confirm that no zone selection screen is presented during configuration[^31]. ### Rollback Suggested rollback: No zone settings exist to revert for this country group. ## Step 5: Provision numbers for the location **Cloud Connected PSTN with integrated number ordering** ### Do Order phone numbers directly within Control Hub using the provider's "Order numbers now" workflow[^45][^33]. ### Verify Confirm that ordered numbers appear automatically in Control Hub under the location's number list[^34]. If the provider manages numbers externally, verify that add, delete, activate, and modify controls are disabled in Control Hub[^24]. ### Rollback For externally managed numbers, coordinate returns or cancellations through the provider, as Control Hub does not allow deleting them[^24]. **Cloud Connected PSTN with external number procurement** ### Do Add the partner-procured numbers into Control Hub as comma-separated values, adding up to 1000 numbers at a time[^1][^42]. Ensure numbers follow E.164 format, or national format for United States numbers[^43]. ### Verify Confirm that Control Hub validates the entered numbers upon saving[^1]. ### Rollback Delete numbers that are unassigned; numbers currently assigned to a user, workspace, or feature cannot be deleted[^16]. **Cisco Calling Plan** ### Do Order new numbers in Control Hub individually or in blocks of 10, 50, or 100, up to a maximum of 100 standard numbers per order[^9]. To port existing numbers, submit a signed Letter of Agency and a recent carrier bill[^10]. ### Verify Confirm that the ordered or ported numbers appear in the location's numbers list[^9]. ### Rollback Delete unassigned numbers in Control Hub[^16]. **Premises-based PSTN through a Local Gateway** ### Do Enter carrier numbers delivered across the Local Gateway trunk as comma-separated values, up to 1000 numbers at once[^1][^42]. Use E.164 format for all countries, or national format for United States numbers[^43]. ### Verify Confirm that Control Hub validates the entered numbers upon saving[^1]. ### Rollback Delete unassigned numbers from the numbers list[^16]. ## Step 6: Activate numbers **Cloud Connected PSTN with integrated number ordering** ### Do If numbers are externally managed by the CCP provider, perform activation on the provider side because Control Hub prohibits activating them[^24]. If numbers are not externally managed, activate them from the Actions menu or perform bulk activation for up to 500 numbers at a time[^3]. ### Verify Verify that the numbers show as active before assigning them to users or services[^3]. ### Rollback Control Hub does not support deactivating numbers once activated, whether externally managed or not[^40]. **Cloud Connected PSTN with external number procurement** ### Do Activate inactive numbers using the Actions menu, or bulk activate up to 500 numbers at once[^3]. ### Verify Confirm that the target numbers display an active status in Control Hub[^3]. ### Rollback Control Hub does not support deactivating numbers once they are active[^40]. **Cisco Calling Plan** ### Do Activate any numbers that were provisioned with the "activate later" option via the Actions menu or bulk activation of up to 500 numbers[^3]. ### Verify Confirm that numbers transition to the active state[^3]. ### Rollback Control Hub does not support deactivating numbers[^40]. **Premises-based PSTN through a Local Gateway** ### Do Activate numbers individually through the Actions menu or in bulk for up to 500 numbers at a time[^3]. ### Verify Confirm that the status shows active[^3]. ### Rollback Control Hub does not support deactivating numbers[^40]. ## Step 7: Set the main number and the emergency callback number ### Do Assign a main number to the location; this is mandatory if the location contains trunks or extension-only entities[^37]. If a toll-free number is selected as the main number, update the location's Emergency Callback Number (ECBN) because toll-free numbers do not carry an emergency services address[^52]. Configure the ECBN in Control Hub under Management > Locations > the location > Calling > Emergency Callback Number[^21]. Select the user's direct number, the location default ECBN, or another assigned number belonging to the location (such as a hunt group), ensuring the chosen number is attended[^22]. ### Verify Confirm that the location displays both a main number and an attended ECBN belonging to that location[^22]. ### Rollback Suggested rollback: Select a different number in the location's settings. A number assigned as a location's main number cannot be moved to another location while holding that role[^39]. ## Step 8: Set up emergency calling **United States or Canada** ### Do Configure enhanced emergency calling (RedSky) for the location[^20]. Prepare a RedSky account with a HELD Company ID and secret key, along with network details including access points, switches, and IP subnets[^19]. Toggle on Enhanced Emergency Calling, enable RedSky test calls, and dial 933 to test the routing[^17]. Only after 933 test calls route properly, toggle on Route Emergency Calls to RedSky[^17]. ### Verify Verify that 933 test calls announce the correct caller ID and address across all endpoint types[^17]. Once enabled, emergency calls are sent to the E911 service rather than the configured PSTN connection[^18]. Once PSTN and an emergency service address are configured, the address cannot be edited on the location overview and must be updated via the emergency service address[^23]. ### Rollback Toggle off Route Emergency Calls to RedSky under the location's Enhanced Emergency Calling settings[^17]. **India** ### Do Maintain an accurate location address, as enhanced emergency calling via RedSky is unavailable outside the U.S. and Canada and emergency calls route via standard PSTN routing through the CCP provider[^20]. Update the address via the emergency service address, which Control Hub syncs to the location overview[^23]. ### Verify Suggested check: Confirm emergency dialing requirements directly with the CCP provider. ### Rollback Update the emergency service address in Control Hub to change the address synchronized to the location overview[^23]. **Other country** ### Do Maintain an accurate location address, as locations outside the U.S. and Canada use standard PSTN routing for emergency calls[^20]. When PSTN and an emergency service address are set, change the address by updating the emergency service address[^23]. ### Verify Suggested check: Confirm provider emergency handling procedures directly with your carrier. ### Rollback Update the emergency service address to update the location overview address[^23]. ## Step 9: Place test calls and confirm the path in Control Hub ### Do In Control Hub, open Monitoring > Troubleshooting and search by phone number; the search covers calls completed within the past 21 days[^53]. See also [Setting up outgoing calling permissions in Webex Calling](https://warmtransfer.net/knowledge/webex-calling-calling-permissions-setup). ### Verify Suggested check: Place test inbound and outbound calls using an active number assigned to the location. Verify that the test calls appear as successful rather than failed or refused[^53]. Open the call hop details to confirm the expected PSTN vendor name and verify whether the call routed through a CCP provider or a Local Gateway[^54]. ### Rollback Suggested rollback: No configuration rollback is required for this diagnostic check. ## Applicability Applies to: Cisco Webex Calling and Webex Calling with Verizon CCP. Deployments: multi-tenant and dedicated instance. Sources checked 2026-09-30. Changing an existing location to Cisco PSTN is not supported in the Japan region[^36]. PSTN zones apply exclusively to locations in India[^31]. Webex Calling enhanced emergency calling with RedSky applies only to locations in the United States and Canada[^20]. Webex Calling Regional Media for CCP is available only for Webex Calling for Service Providers and Value Added Resellers, and does not apply to Webex room systems[^49]. ## What remains uncertain Emergency calling routing workflows, caller location reporting, and dispatchable location compliance outside the United States and Canada are not covered by the sources below. The specific porting timelines, required documentation, and submission processes for Cloud Connected PSTN providers are not covered by the sources below. The specific activation lead times required for carrier-side routing on non-integrated CCP connections are not covered by the sources below. ## Sources [^1]: Up to 1000 numbers can be added at once in Control Hub, separated by commas, and they are validated after saving. Source: [Manage phone numbers in Control Hub](https://help.webex.com/en-us/article/wkj3f0/Manage-phone-numbers-in-Control-Hub), Add numbers section. Checked 2026-09-30. [^2]: To give a new location PSTN, go to Management > Location, add the location, click Save, choose to add numbers now, select the PSTN option, and choose whether to activate numbers now or later. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; procedure steps 2 to 6. Checked 2026-09-30. [^3]: Inactive non-mobile numbers are activated from the Actions menu or by bulk activation of up to 500 numbers at a time. Source: [Manage phone numbers in Control Hub](https://help.webex.com/en-us/article/wkj3f0/Manage-phone-numbers-in-Control-Hub), Number states and bulk operations sections. Checked 2026-09-30. [^4]: Because non-integrated CCP numbers are procured from the partner outside Control Hub and Cisco's porting procedure is documented only for Cisco Calling Plans, porting existing numbers onto a CCP connection is most likely arranged with the CCP provider rather than in Control Hub (inferred). Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; non-integrated CCP note, read with cisco-help-nousk9ab-cisco-calling-plan Port numbers section. Checked 2026-09-30. [^5]: Cisco markets Cloud Connect for Webex Calling as delivered through more than 60 Certified Calling Providers across more than 90 markets. Source: [Webex Calling PSTN options for businesses any size, anywhere](https://blog.webex.com/collaboration/webex-calling-pstn-options/), Cloud Connect for Webex Calling section. Checked 2026-09-30. [^6]: Cisco positions Cloud Connected PSTN for customers who want a cloud PSTN solution from a Cisco CCP partner or whose location is not served by the Cisco Calling Plan. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; Cloud Connected PSTN option description. Checked 2026-09-30. [^7]: With PSTN trunking for hybrid deployments, on-premises PBX users can place and receive PSTN calls through a Cloud Connected Partner PSTN via Webex Calling. Source: [PSTN trunking for hybrid Webex Calling deployments](https://help.webex.com/en-us/article/x3f0tm/PSTN-trunking-for-hybrid-Webex-Calling-deployments), Overview; supported PSTN types. Checked 2026-09-30. [^8]: For Cisco Calling Plan locations an emergency service address is mandatory and by default applies to all numbers in the location, with per-user addresses possible in the U.S. and Canada. Source: [Cisco Calling Plan](https://help.webex.com/en-us/article/nousk9ab/Cisco-Calling-Plan), Emergency service address section. Checked 2026-09-30. [^9]: Cisco Calling Plan numbers are ordered individually or in consecutive blocks of 10, 50 or 100, with at most 100 standard numbers per order. Source: [Cisco Calling Plan](https://help.webex.com/en-us/article/nousk9ab/Cisco-Calling-Plan), Order new numbers section. Checked 2026-09-30. [^10]: Porting numbers to Cisco Calling Plans requires a signed Letter of Agency and a recent carrier bill. Source: [Cisco Calling Plan](https://help.webex.com/en-us/article/nousk9ab/Cisco-Calling-Plan), Port numbers section. Checked 2026-09-30. [^11]: Cisco Calling Plans require the partner to be an authorized Webex Calling partner that accepted the Webex Calling addendum and at least one committed Outbound Calling Plan license. Source: [Cisco Calling Plan](https://help.webex.com/en-us/article/nousk9ab/Cisco-Calling-Plan), Prerequisites section. Checked 2026-09-30. [^12]: A location's PSTN option can be changed after provisioning, but some options such as Cisco PSTN may not be available once another option has been assigned. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), PSTN connection notes; changing the PSTN option. Checked 2026-09-30. [^13]: The Cisco PSTN option appears for a location only if at least one committed Cisco Calling Plan OCP is purchased, the location is in a supported country, the location is new, and it is hosted in a compatible Webex Calling data center. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; Cisco PSTN option visibility conditions. Checked 2026-09-30. [^14]: Since August 2026 the Control Hub PSTN page has a Connections tab, alongside the Orders and Providers tabs, that lists locations as a central view of PSTN offers. Source: [What's new in Webex Calling](https://help.webex.com/en-us/article/rdmb0/What's-new-in-Webex-Calling), What's new entry dated August 5, 2026; Connections tab. Checked 2026-09-30. [^15]: Only customer administrators can initiate a PSTN connection change, because the change requires signing an E911 agreement. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; PSTN connection change prerequisites. Checked 2026-09-30. [^16]: A number already assigned to a user, workspace or feature cannot be deleted in Control Hub; only unassigned numbers are eligible for deletion. Source: [Manage phone numbers in Control Hub](https://help.webex.com/en-us/article/wkj3f0/Manage-phone-numbers-in-Control-Hub), Number states and bulk deletion sections. Checked 2026-09-30. [^17]: For each location, toggle on Enhanced Emergency Calling, allow RedSky test calls, place test calls to 933, and only after they route correctly toggle on Route Emergency Calls to RedSky. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enable the E911 service for Webex Calling locations; steps. Checked 2026-09-30. [^18]: At a location with PSTN and the E911 service enabled, emergency calls are identified and sent to the E911 service instead of the configured PSTN. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Deployment scenarios; PSTN and E911 service enabled locations. Checked 2026-09-30. [^19]: Enabling enhanced emergency calling requires a RedSky account with a HELD Company ID and secret key, plus network details such as access points, switches and IP subnets. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Prerequisites section. Checked 2026-09-30. [^20]: Webex Calling enhanced emergency calling (RedSky) is set up for U.S. and Canada locations, while international locations continue to use standard PSTN routing for emergency calls. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Overview and supported countries. Checked 2026-09-30. [^21]: A location's Emergency Callback Number is set in Control Hub under Management > Locations > the location > Calling > Emergency Callback Number, and the PSAP uses it to call back. Source: [Emergency Callback Number in Control Hub](https://help.webex.com/en-us/article/nzqvtyq/Emergency-Callback-Number-in-Control-Hub), Configure ECBN for a location. Checked 2026-09-30. [^22]: ECBN choices are the user's direct number, the location default ECBN, or an assigned number from the user's location such as a user, workspace, virtual line or hunt group number, and the number should be attended and in that location. Source: [Emergency Callback Number in Control Hub](https://help.webex.com/en-us/article/nzqvtyq/Emergency-Callback-Number-in-Control-Hub), ECBN options section. Checked 2026-09-30. [^23]: After PSTN and an emergency service address are set for a location, the address can no longer be edited on the location overview; it is changed by updating the emergency service address, which Control Hub then syncs to the overview. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; important notes. Checked 2026-09-30. [^24]: When numbers are externally managed by a Cloud Connected PSTN provider, an administrator cannot add, delete, activate or modify them in Control Hub. Source: [Manage external numbers with Control Hub](https://help.webex.com/en-us/article/pou6mk/Manage-external-numbers-with-Control-Hub), Overview and administrator restrictions. Checked 2026-09-30. [^25]: Moving mobile numbers between locations in the same country stays enabled even when numbers are externally managed by the CCP provider. Source: [Manage external numbers with Control Hub](https://help.webex.com/en-us/article/pou6mk/Manage-external-numbers-with-Control-Hub), Administrator restrictions. Checked 2026-09-30. [^26]: While a location is undergoing a PSTN connection transition, numbers cannot be added, deleted or moved in or out, but existing numbers keep working and can still be assigned or unassigned. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; number management during PSTN transition. Checked 2026-09-30. [^27]: The India CCP wizard accepts up to 1000 comma-separated numbers with area codes and offers an Activate Numbers Later option. Source: [Webex Calling with Cloud Connected PSTN Provider in India](https://help.webex.com/en-us/article/gvzxbu/Webex-Calling-with-Cloud-Connected-PSTN-Provider-in-India), Add a new connection type; number entry step. Checked 2026-09-30. [^28]: From November 2025, customers in India could use Cloud Connect for PSTN calling through the partner Airtel, with Tata Communications Limited and Tata Tele Business Services announced to follow. Source: [What's new in Webex Calling](https://help.webex.com/en-us/article/rdmb0/What's-new-in-Webex-Calling), What's new entry dated November 14, 2025; India PSTN. Checked 2026-09-30. [^29]: For Indian locations, number portability between different PSTN providers is not supported, and a provider change should be confirmed with both current and new providers first. Source: [Webex Calling with Cloud Connected PSTN Provider in India](https://help.webex.com/en-us/article/gvzxbu/Webex-Calling-with-Cloud-Connected-PSTN-Provider-in-India), Update connection type for Indian location section. Checked 2026-09-30. [^30]: The India CCP procedure selects Cloud Connected PSTN on the Connection Type screen and then Tata Communications Limited (IN) on the Select a Provider screen. Source: [Webex Calling with Cloud Connected PSTN Provider in India](https://help.webex.com/en-us/article/gvzxbu/Webex-Calling-with-Cloud-Connected-PSTN-Provider-in-India), Add a new connection type; steps for Connection Type and Select a Provider screens. Checked 2026-09-30. [^31]: For an India location on Cloud Connected PSTN the administrator must assign a PSTN zone so call routing complies with toll bypass regulations; zones apply only to locations in India. Source: [Webex Calling with Cloud Connected PSTN Provider in India](https://help.webex.com/en-us/article/gvzxbu/Webex-Calling-with-Cloud-Connected-PSTN-Provider-in-India), Add a new connection type; Select a Zone screen and zone notes. Checked 2026-09-30. [^32]: An India location's zone is changed under Calling Connection > PSTN Connection > Manage by choosing a value from the PSTN Zone drop-down list. Source: [Webex Calling with Cloud Connected PSTN Provider in India](https://help.webex.com/en-us/article/gvzxbu/Webex-Calling-with-Cloud-Connected-PSTN-Provider-in-India), Update zone for Cloud Connected PSTN section. Checked 2026-09-30. [^33]: Integrated CCP lets the administrator procure and provision phone numbers from the CCP partner inside Control Hub. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location and Update an existing location; integrated CCP note. Checked 2026-09-30. [^34]: Numbers ordered from an integrated CCP provider are supplied to Control Hub automatically, while numbers from a non-integrated provider are imported by the administrator under Calling > Numbers. Source: [Cloud Connected PSTN](https://webexcallingtraining.verizon.com/cloud-connected-pstn/), PSTN number ordering phase. Checked 2026-09-30. [^35]: Migrating a location from integrated IntelePeer CCP to Cisco PSTN is listed as unsupported. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; limitations list. Checked 2026-09-30. [^36]: Changing an existing location's PSTN connection to Cisco PSTN is not supported for the Japan region. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; regional limitation note. Checked 2026-09-30. [^37]: A location must have a main number assigned if it has any trunks or any extension-only entities. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; main number step and note. Checked 2026-09-30. [^38]: An organization can use a different PSTN solution per location, for example Cisco Calling Plans at one location, Cloud Connected PSTN at a second and Local Gateway at a third. Source: [Cisco Calling Plan](https://help.webex.com/en-us/article/nousk9ab/Cisco-Calling-Plan), PSTN connection options section. Checked 2026-09-30. [^39]: A number can be moved between locations only if both are in the same country and use the same PSTN provider or local gateway, the number is active and unassigned, and it is not the location's main number. Source: [Manage phone numbers in Control Hub](https://help.webex.com/en-us/article/wkj3f0/Manage-phone-numbers-in-Control-Hub), Move numbers between locations section. Checked 2026-09-30. [^40]: Control Hub does not support deactivating numbers, whether or not they are externally managed. Source: [Manage external numbers with Control Hub](https://help.webex.com/en-us/article/pou6mk/Manage-external-numbers-with-Control-Hub), Key limitation note. Checked 2026-09-30. [^41]: Non-integrated CCP requires the customer to procure phone numbers from the CCP partner outside Control Hub. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location and Update an existing location; non-integrated CCP note. Checked 2026-09-30. [^42]: For non-integrated CCP or premises-based PSTN, the location wizard asks for phone numbers as comma-separated values, which are validated before saving. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; procedure step 7. Checked 2026-09-30. [^43]: Numbers added in Control Hub must be in E.164 format for all countries, except that United States numbers may also use national format. Source: [Manage phone numbers in Control Hub](https://help.webex.com/en-us/article/wkj3f0/Manage-phone-numbers-in-Control-Hub), Add numbers section. Checked 2026-09-30. [^44]: Each Webex Calling location has only one PSTN option. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), PSTN connection notes; 'each location has only one PSTN option'. Checked 2026-09-30. [^45]: When a listed CCP provider shows an Order numbers now option, Cisco recommends choosing it so the location benefits from integrated CCP. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; Cloud Connected PSTN provider selection note. Checked 2026-09-30. [^46]: For premises-based PSTN the administrator first adds a trunk for the location in Control Hub (name up to 24 characters), then selects that trunk under the location's PSTN Connection Manage dialog, and a registered gateway shows a green dot beside its name; a location with a local gateway cannot be deleted while that gateway is used by other locations. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Create a trunk and Select a trunk for a location sections. Checked 2026-09-30. [^47]: Premises-based PSTN (Local Gateway) is the option for keeping a current PSTN provider or connecting non-cloud sites with cloud sites. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; Premises-based PSTN option description. Checked 2026-09-30. [^48]: In the location wizard, only CCP partners that support the location's country are displayed. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; step selecting Cloud Connected PSTN. Checked 2026-09-30. [^49]: Webex Calling Regional Media for CCP, which uses local data centers for PSTN calls, is available only for Webex Calling for Service Providers and for Value Added Resellers and does not apply to Webex room systems. Source: [Webex Calling Regional Media for Cloud Connected PSTN](https://help.webex.com/en-us/article/nixlytw/Regional-media-for-Cloud-Connected-PSTN), Overview and supported offers. Checked 2026-09-30. [^50]: Before migrating a location's PSTN connection, review all telephone numbers in the location and delete or move any you no longer own or do not want to migrate; the non-portable numbers list must be empty. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; before migration notes. Checked 2026-09-30. [^51]: When a Webex Calling location is given PSTN, the administrator chooses among Cisco PSTN (Cisco Calling Plan), Cloud Connected PSTN, and Premises-based PSTN (Local Gateway). Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Add a location; PSTN option step. Checked 2026-09-30. [^52]: If a toll-free number is chosen as a location's main number, Cisco recommends updating the location's Emergency Callback Number because a toll-free number has no emergency services address. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; main number note on toll-free. Checked 2026-09-30. [^53]: Control Hub Monitoring > Troubleshooting lets an admin search Webex Calling calls from the past 21 days by phone number and see whether each call succeeded, was refused or failed. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-calls-in-Control-Hub), Search calls section. Checked 2026-09-30. [^54]: For PSTN calls the troubleshooting hop details show the PSTN vendor name and whether the call went through a Cloud Connected PSTN provider or a local gateway, but not the PSTN caller's receive-stream metrics. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-calls-in-Control-Hub), Call hop details section. Checked 2026-09-30. [^55]: To change an existing location's PSTN connection, open the location's Calling tab, click Manage under PSTN Connection, acknowledge the risks with Continue, choose the new option and click Save. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location; step 3. Checked 2026-09-30. [^56]: For Cisco CUBE as Local Gateway, a registration-based trunk requires at least IOS XE 17.6.1a and a certificate-based trunk requires at least IOS XE 17.9.1a. Source: [Get started with Local Gateway](https://help.webex.com/en-us/article/t9xctu), Requirements / software versions for CUBE. Checked 2026-09-30.