Configuration · guide

Setting up a Webex Calling location

Webex Calling

Verified 2026-09-30 · 60 sources · tier 2

For Webex Calling administrators with full administrator privileges in Control Hub adding a new site..

A Webex Calling location establishes site-level network addressing, PSTN connectivity, dialing logic, and emergency call routing 32 54. Cisco's provisioning sequence structures location configuration prior to registering endpoints or activating user-facing features 59.

Before you start

Cisco Calling Plan is only selectable if your organization has purchased an outbound calling plan, the location resides in an eligible country, and the tenant data center region supports Cisco Calling Plan 3.
Locations previously assigned another PSTN option cannot later switch to Cisco Calling Plan 4. WarmTransfer's reading of the sources is that organizations anticipating future Cisco Calling Plan use should select it during initial location onboarding 5.
For premises-based PSTN, local gateways operate on Cisco Unified Border Element (CUBE) on IOS XE 29. Registration-based trunks require IOS XE 17.6.1a or later, while certificate-based trunks require IOS XE 17.9.1a or later 29.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

How will this location reach the PSTN?

Do the organization-wide dialing defaults fit this location?

Who routes this location's emergency calls?

Three questions. One permanent page you can send to your manager.

Step 1 Gather carrier and emergency prerequisites

Cisco Calling Plan

Do

Confirm that your tenant is hosted in a supported data-center region, that an outbound calling plan has been purchased, and that your country appears in the Cisco Calling Plan country list 3 6. Obtain the legal contract signatory's contact details along with the emergency services address (ESA) for the physical site 11. If existing numbers will be ported, assemble a signed Letter of Agency and a carrier billing statement dated within the last 30 days 10.

Verify

Verify that the location country is listed among the supported territories: Belgium, Canada, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Lithuania, Luxembourg, Netherlands, Poland, Sweden, Switzerland, the United Kingdom, the United States, Australia, or New Zealand 6. If operating under a Cisco Calling Plan trial, note that live emergency call routing cannot be guaranteed, international and Premium Services I and II calling are blocked, and a maximum of 10 standard numbers are allocated 12.

Rollback

Suggested rollback: No configuration changes are made in this step; discontinue preparation if prerequisites are not met.

Cloud Connected PSTN

Do

Establish your Cloud Connected PSTN (CCP) contract with the authorized partner and determine whether your carrier supports integrated number ordering within Control Hub or manages telephone numbers externally 2 40.

Verify

Confirm provider integration status in Control Hub 2. When an external number management model is used by the carrier, Control Hub displays a notice stating that number management is disabled by the carrier 40.

Rollback

Suggested rollback: No configuration changes are made in this step; verify partner contracts before continuing.

Premises-based PSTN through a local gateway

Do

Prepare a local gateway running Cisco Unified Border Element on IOS XE 29. Select between a registration-based trunk (requiring SIP registration by the gateway) or a certificate-based trunk (validated using gateway FQDN and mutual certificate exchange) 57.

Verify

Check gateway image levels to confirm that registration-based trunks have at least IOS XE 17.6.1a and certificate-based trunks have at least IOS XE 17.9.1a 29.

Rollback

Suggested rollback: No Control Hub changes occur during local gateway staging.

Step 2 Create the location record

Do

In Control Hub, navigate to Management > Locations and select Add location 30 32. Enter the location name, country or region, street address, city, state or province, ZIP or postal code, time zone, announcement language, and email language 32. When prompted upon saving, choose the option to add numbers later 30. Confirm address accuracy prior to saving; after PSTN and an emergency service address are assigned, address fields become uneditable from the location overview page and must be updated via the emergency service address configuration 1.

Verify

Confirm that the newly created record is listed under Management > Locations with the expected address and time zone settings 30.

Rollback

To remove the site, delete the location using the Actions menu next to the entry under Management > Locations after verifying that all users and workspaces have been reassigned or deleted 15. Deletion operations typically complete in a few minutes but can take up to an hour, displaying progress under Deletion Status 17. Deleting a location permanently releases all its assigned numbers to the PSTN carrier, ending organization ownership 16.

Step 3 Configure PSTN connectivity

Cisco Calling Plan

Do

Navigate to Management > Locations, select the location, open the Calling tab, and click Manage next to PSTN Connection 53. Select Cisco Calling Plans, submit the legal contract signatory contact information, enter the physical Emergency Services Address (ESA), and save 11. This ESA applies by default across all numbers provisioned to the location 7.

Verify

Verify that the location PSTN connection status indicates Cisco Calling Plan 53. Verify that the ESA validates successfully, as Cisco warns unvalidated addresses can delay emergency services dispatch and trigger third-party relay center surcharges 8.

Rollback

Location ESAs may be modified at any time from location calling settings 7.

Cloud Connected PSTN

Do

Select the location under Management > Locations, access the Calling tab, click Manage next to PSTN Connection, click Continue on the warning dialogue, select Cloud Connected PSTN, choose your certified partner from the list, and save 53 54.

Verify

Confirm that the location PSTN connection profile reflects Cloud Connected PSTN with the selected provider 53.

Rollback

Reopen Manage beside PSTN Connection under the Calling tab to select an alternative connection 53. Note that an organization cannot assign Cisco Calling Plan to a location once any other PSTN method has been configured 4.

Premises-based PSTN through a local gateway

Do

Establish a trunk and bind it to this location record, as trunks must be assigned to a location before use and are required prior to enabling premises PSTN 56 52. Return to the location's Calling tab, click Manage next to PSTN Connection, acknowledge the warning prompt by selecting Continue, select Premises-based PSTN, choose the trunk, and save 53.

Verify

Verify that Premises-based PSTN is shown as the active connection under PSTN Connection and confirm the trunk association 53 56.

Rollback

Reopen Manage next to PSTN Connection to modify trunk links 53. Locations hosting a local gateway cannot be deleted while that gateway is shared with other operational locations 14. A location assigned premises PSTN is permanently ineligible for Cisco Calling Plan 4.

Step 4 Add and activate phone numbers

Cisco Calling Plan

Do

Order new numbers directly in Control Hub in discrete blocks of 10, 50, or 100, up to a limit of 100 standard numbers per submission 9. Note that toll-free numbers are restricted to locations in the United States and Canada 9. To port active lines, submit a port request for up to 1,000 numbers per order with no supplemental porting fees 10.

Verify

Under Services > PSTN & Routing > Numbers, filter by this location to verify inventory 37. Confirm that ported numbers appear in the inventory; unactivated ported lines remain inactive until explicit activation, even if assigned to users or features 41.

Rollback

Numbers may only be deleted when fully unassigned, and Control Hub blocks deleting the final remaining telephone number in an organization 38. Numbers cannot be transitioned back to an inactive state in Control Hub once activated 43.

Cloud Connected PSTN

Do

For integrated CCP partners, select Order numbers now within Control Hub to procure inventory directly 2. For non-integrated carriers, navigate to Services > PSTN & Routing > Numbers, select Manage > Add, select the target location, and paste comma-separated telephone numbers 37. Numbers must follow E.164 format, though national formatting is permitted for United States lines 39. Up to 1,000 numbers may be submitted per operation 42. Check Activate Numbers Later if line porting remains in progress 36. Where external number management is enforced by the partner, administrative number entry within Control Hub is disabled 40.

Verify

Click Validate and verify that all entries populate the Validated Numbers container with no syntax or location mismatch errors displayed 44.

Rollback

Delete unassigned lines via Services > PSTN & Routing > Numbers 38. Control Hub provides no mechanism to deactivate an active telephone number 43.

Premises-based PSTN through a local gateway

Do

Navigate to Services > PSTN & Routing > Numbers, select Manage > Add, select this location, and input the PSTN carrier numbers delivered over your local gateway separated by commas 37. Apply E.164 formatting (United States numbers may alternatively use national dialing syntax) 39. Batches of up to 1,000 numbers can be added in a single transaction 42. Enable Activate Numbers Later if circuit turn-up or carrier cutover has not finalized 36.

Verify

Click Validate and ensure that submitted numbers appear in the Validated Numbers list without error alerts 44.

Rollback

Numbers may only be deleted when fully unassigned, and Control Hub blocks deleting the organization's last number 38. Numbers cannot be deactivated once active 43.

Step 5 Assign the location main number

Do

Navigate to the location settings view in Control Hub and pick a primary directory line from the Main Number drop-down list 34. Establishing a main number is mandatory if the site incorporates local trunks or hosts extension-only entities, including users, workspaces, virtual lines, or features 33. If a toll-free number is selected as the main number, configure an emergency callback number separately because toll-free lines do not maintain emergency service addresses 35.

Verify

Verify that the selected telephone number appears in the Main Number field in the location summary 34.

Rollback

Select a replacement directory number from the Main Number drop-down menu 34. Ensure another valid number is assigned before disassociating the previous selection if the location maintains trunks or extension-only subscribers 33.

Step 6 Configure internal and external dialing rules

Yes: use organization internal dialing settings and no outbound dial digit

Do

Navigate to Calling > Settings > Service > Internal Dialing and inspect the tenant defaults for routing prefix length, steering digit, internal extension length, and cross-location extension dialing 46. Confirm that location extensions align with the tenant extension length, which defaults to 4 digits and can range from 2 to 10 digits 27. Confirm that extension dialing between locations remains disabled if duplicate extension ranges exist across your organization 26. Leave the outbound dial digit blank under location dialing settings so the organization-level phone-number format governs outbound dialing 31 45.

Verify

Inspect Management > Locations > (location) > Calling > Dialing to ensure the Outbound dial digit field is blank 31. Check Calling > Settings > Service > Internal Dialing to confirm extension length settings 46.

Rollback

Adjusting organization internal dialing values impacts all provisioned sites 46. Note that increasing tenant extension length does not automatically update pre-existing internal extension speed dials 28.

No: set a location routing prefix or outbound dial digit

Do

Navigate to Management > Locations > (location) > Calling > Dialing 31. Under Internal Dialing, assign a unique routing prefix, which ranges from 1 to 7 digits inclusive of the organization steering digit 31 55. Under External Dialing, enter an outbound dial digit if site users require an access digit for PSTN calls 31. When overlapping extensions exist across sites, ensure cross-location extension dialing is disabled so users dial the routing prefix plus extension (Enterprise Significant Number) 26. Configuring an outbound dial digit forces this location into E.164 dialing format and disables permissive dialing, regardless of the broader organization format configuration 47.

Verify

Verify that the assigned prefix and dial digit are stored under Management > Locations > (location) > Calling > Dialing 31. Check call routing behaviors using the Verify Call Routing tool 58.

Rollback

Delete the outbound dial digit in location dialing settings to revert the site to tenant-wide calling number formatting 45. Modify or remove the routing prefix in the same panel 31.

Step 7 Configure the emergency callback number

Do

Navigate to Management > Locations > (location) > Calling > Numbers > Emergency Callback Number 23. Select either the location main number or an assigned, attended direct line within the location 23. Do not configure a toll-free number as the emergency callback number 35. For provisioned end users assigned direct telephone numbers, Cisco recommends setting each user's ECBN to their personal telephone number 24.

Verify

Verify that the chosen number is listed in the Emergency Callback Number field 23. This value represents the calling line identity delivered to PSTN carriers so public safety answering points (PSAPs) can return interrupted emergency calls 22.

Rollback

Select the alternative callback option under Management > Locations > (location) > Calling > Numbers > Emergency Callback Number 23.

Step 8 Configure emergency routing and addresses

Cisco Enhanced Emergency Calling (RedSky) (U.S., territories and Canada only)

Do

After Enhanced Emergency Calling is enabled tenant-wide, open Management > Locations > (location) > Calling > Enhanced Emergency Calling 20. Enable network connectivity sharing, execute test calls to 933, and only activate Route Emergency Calls to RedSky once the test call behavior succeeds 18.

Verify

Confirm during the 933 test call that the automated system articulates the calling device's caller ID and associated physical dispatch address 18.

Rollback

Disable the Route Emergency Calls to RedSky toggle in the location settings 18. Emergency traffic then routes via the location's designated PSTN carrier 19.

The location's PSTN provider

Do

Confirm that your PSTN provider maintains the validated emergency service address for all numbers provisioned to this location, as Webex Calling does not store local provider ESAs internally 25. For Cisco Calling Plan sites, the emergency service address configured for the location applies to all phone numbers at the location by default 7. If operating in the United States or Canada, opt the organization out of Enhanced Emergency Calling so emergency calls flow over your standard PSTN trunks 19.

Verify

Confirm address registration status with your PSTN carrier 25. For Cisco Calling Plan, confirm that the ESA shows as validated in Control Hub to avoid unvalidated relay surcharges or dispatch delays 8.

Rollback

Update provider address records via carrier service tooling, or modify the Cisco Calling Plan ESA within Control Hub calling settings 7 25.

Step 9 Establish outgoing call permissions

Do

Navigate to Management > Locations > (location) > Calling > Call Handling > Outgoing Call Permissions 51. For each classification (Internal, Toll Free, National, International, Operator Assistance, Chargeable Directory Assistance, Special Services I and II, and Premium Services I and II), select Allow, Block, Require Authorization Code, or Auto-transfer (directing to 1 of 3 target destinations) 48 60. You can assign up to 1,000 authorization codes per location 48. Default settings assign Allow across general traffic, while International and Premium Services I and II default to Block with transfer disallowed 49.

Verify

Confirm that configured call types reflect the chosen policy actions 48. Note that location users, workspaces, and virtual lines inherit these policies unless overridden by custom individual digit patterns, which take precedence over location rules 50.

Rollback

Restore customized call types back to the system defaults: Allow for internal and standard destinations, and Block for International and Premium Services I and II 49.

Step 10 Validate call routing behavior

Do

Cisco's configuration workflow orders location-level work before registering devices and configuring features 59. Access Control Hub's Verify Call Routing diagnostic tool 58. Select a provisioned call source at this location and run simulations against an internal extension, an inter-location routing prefix destination, a national public number, and an international destination 58.

Verify

Examine simulation output to verify that outgoing permissions, fraud prevention checks, digit pattern selections, call intercept rules, and translation patterns match design specifications 58. For locations routed via RedSky, verify dynamic emergency routing using test calls to 933 18. Suggested check: Place live outbound test calls to verify two-way audio on newly activated lines.

Rollback

The routing verification tool is read-only and requires no configuration rollback 58.

Applicability

Applies to: Cisco Webex Calling. Deployments: multi-tenant. Sources checked 2026-09-30. - Cisco Calling Plans are supported exclusively in Australia, Belgium, Canada, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Lithuania, Luxembourg, Netherlands, New Zealand, Poland, Sweden, Switzerland, the United Kingdom, and the United States 6.

Cisco Calling Plans do not support calls to X11 services, with the sole exception of 911 13.
Enhanced Emergency Calling using RedSky is limited to the United States, its territories, and Canada 21.
Local gateways require Cisco IOS XE 17.6.1a or later for registration-based trunks, and Cisco IOS XE 17.9.1a or later for certificate-based trunks 29.

What remains uncertain

Live inbound testing procedures for location main numbers are not covered by the sources below.
Test call validation routines for emergency services situated outside the United States and Canada are not covered by the sources below.
Constraints governing PSTN connection changes after numbers have been assigned to a location are not covered by the sources below.
Cisco Unified Border Element command-line interface parameters, dial peer configurations, and carrier-side ordering procedures are not covered by the sources below.
The allowable character set and enforcement mechanisms for outbound dial digits are not covered by the sources below.

Sources

1
For a location that has PSTN and an emergency service address configured, the address fields cannot be edited from the location overview page; the emergency service address is updated instead.
Configure Webex Calling for your organization · section: Create a location, note on address fields · Checked 2026-09-30
2
For Cloud Connected PSTN, an Order numbers now option lets integrated providers' numbers be procured from within Control Hub.
Configure Webex Calling for your organization · section: Set up PSTN connection for a location, Cloud Connected PSTN · Checked 2026-09-30
3
The Cisco PSTN option appears only when the organization has purchased a Cisco Calling Plan outbound calling plan, the location is in a supported country, and the organization is hosted in a Webex Calling data center region where Cisco Calling Plan is supported.
Configure Webex Calling for your organization · section: Set up PSTN connection for a location, Cisco PSTN eligibility list · Checked 2026-09-30
4
Pre-existing locations that have had other PSTN capabilities assigned are currently not eligible for Cisco Calling Plan.
Configure Webex Calling for your organization · section: Set up PSTN connection for a location, Cisco PSTN restriction note · Checked 2026-09-30
5
Because Cisco Calling Plan is not offered to locations that already had another PSTN option, a reader who may want Cisco Calling Plan should choose it when the location is first given a PSTN connection rather than starting on another option.inferred
Configure Webex Calling for your organization · section: Set up PSTN connection for a location, Cisco PSTN restriction note · Checked 2026-09-30
6
Cisco Calling Plans are available in the United States, Canada, Belgium, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Lithuania, Luxembourg, Netherlands, Poland, Sweden, Switzerland, the United Kingdom, Australia and New Zealand.
Cisco Calling Plan · section: Supported countries · Checked 2026-09-30
7
With Cisco Calling Plans the location's ESA applies by default to all phone numbers at the location and can be updated at any time; U.S. and Canada locations can override it per user for non-mobile primary numbers.
Cisco Calling Plan · section: Emergency Services Address · Checked 2026-09-30
8
Cisco warns that if the ESA is not validated, emergency call handling may be delayed and extra charges may apply if calls go to an emergency relay center.
Cisco Calling Plan · section: Emergency Services Address, disclaimer · Checked 2026-09-30
9
Cisco Calling Plan numbers are ordered in Control Hub in consecutive blocks of 10, 50 or 100, with at most 100 standard numbers per order; toll-free numbers are only available for U.S. and Canada locations.
Cisco Calling Plan · section: Order new numbers · Checked 2026-09-30
10
Porting numbers to Cisco Calling Plans needs a signed Letter of Agency and a bill from the last 30 days, allows up to 1,000 numbers per order, and carries no additional porting charge.
Cisco Calling Plan · section: Port numbers · Checked 2026-09-30
11
Setting Cisco Calling Plans as a location's PSTN requires entering the legal contract signatory's contact information and an Emergency Services Address before saving; numbers can be added then or later.
Cisco Calling Plan · section: Set up Cisco Calling Plans for a location, steps · Checked 2026-09-30
12
On a Cisco Calling Plan trial, actual emergency calls cannot be guaranteed, international and Premium Services I and II calling are blocked, and at most 10 standard numbers are available.
Cisco Calling Plan · section: Limitations and trial restrictions · Checked 2026-09-30
13
Except for 911, Cisco Calling Plans do not support calls to X11 services, including directory service calls.
Cisco Calling Plan · section: Emergency calling / limitations · Checked 2026-09-30
14
A location with a local gateway cannot be deleted while that local gateway is used by other locations.
Delete a location from your Webex Calling organization · section: Delete a location, local gateway restriction · Checked 2026-09-30
15
Before a location can be deleted, all its users and workspaces must be removed; deletion is done from the Actions menu beside the location under Management > Locations.
Delete a location from your Webex Calling organization · section: Delete a location, prerequisites and steps · Checked 2026-09-30
16
Deleting a location permanently releases all its numbers back to the PSTN provider, so the organization no longer owns them.
Delete a location from your Webex Calling organization · section: Delete a location, number release note · Checked 2026-09-30
17
Location deletion usually takes a couple of minutes but can take up to an hour, and its progress shows as Deletion Status next to the location.
Delete a location from your Webex Calling organization · section: Delete a location, timing · Checked 2026-09-30
18
For a RedSky location, the administrator first enables network connectivity sharing, places test calls to 933 (which announce the caller ID and known address), and only then turns on Route Emergency Calls to RedSky.
Enhanced Emergency Calling for Webex Calling · section: Enable Enhanced Emergency Calling for a location, steps and test calls · Checked 2026-09-30
19
An organization whose PSTN service provider handles emergency calling can opt out of Enhanced Emergency Calling, and emergency calls then route through the existing PSTN provider.
Enhanced Emergency Calling for Webex Calling · section: Opt out · Checked 2026-09-30
20
After Enhanced Emergency Calling is enabled for the organization, it must be turned on separately for each location under Management > Locations > (location) > Calling > Enhanced Emergency Calling.
Enhanced Emergency Calling for Webex Calling · section: Enable Enhanced Emergency Calling for a location · Checked 2026-09-30
21
Enhanced Emergency Calling for Webex Calling uses RedSky's cloud E911 service for dynamic location-based routing to PSAPs and is available for the U.S., its territories and Canada.
Enhanced Emergency Calling for Webex Calling · section: Overview · Checked 2026-09-30
22
The emergency callback number is the number presented to the PSTN provider on an emergency call so the PSAP can call back, and it is mapped to the emergency service address.
Configure emergency callback number in Control Hub · section: Overview · Checked 2026-09-30
23
A location's emergency callback number is either the location main number or an assigned number attended within the location, set under Management > Locations > (location) > Calling > Numbers > Emergency Callback Number.
Configure emergency callback number in Control Hub · section: Configure emergency callback number for a location · Checked 2026-09-30
24
A user's emergency callback number can be the user's own number, the location default ECBN, or another assigned number from the user's location, and Cisco recommends users with their own number use it.
Configure emergency callback number in Control Hub · section: Configure emergency callback number for a user · Checked 2026-09-30
25
Webex Calling does not store the emergency service address itself; the PSTN provider maintains the mapping of the number to the location-specific ESA.
Configure emergency callback number in Control Hub · section: Emergency service address · Checked 2026-09-30
26
Extension dialing between locations should be enabled only if no extensions are duplicated across the organization; with duplicates it is disabled and users dial the Enterprise Significant Number (routing prefix plus extension).
Configure Webex Calling for your organization · section: Configure internal dialing, Allow extension dialing between locations · Checked 2026-09-30
27
Internal extension length defaults to 4 digits and can be set from 2 to 10 digits.
Configure Webex Calling for your organization · section: Configure internal dialing, Internal Extension Length · Checked 2026-09-30
28
After the extension length is increased, existing speed dials to internal extensions are not updated automatically.
Configure Webex Calling for your organization · section: Configure internal dialing, Internal Extension Length note · Checked 2026-09-30
29
The local gateway platform is Cisco Unified Border Element on IOS XE, with registration-based trunks requiring at least IOS XE 17.6.1a and certificate-based trunks at least 17.9.1a.
Get started with Local Gateway · section: Requirements for Local Gateway, software versions · Checked 2026-09-30
30
A location is added from Management > Locations in Control Hub, and on Save the administrator is asked whether to add numbers now or later.
Configure Webex Calling for your organization · section: Create a location, final steps · Checked 2026-09-30
31
Location-level dialing is set under Management > Locations > (location) > Calling > Dialing, where Internal Dialing takes the routing prefix other locations dial and External Dialing takes an optional outbound dial digit.
Configure Webex Calling for your organization · section: Configure internal dialing for a location / external dialing · Checked 2026-09-30
32
Adding a Webex Calling location in Control Hub asks for a location name, country or region, street address, city, state or province, ZIP or postal code, time zone, announcement language and email language.
Configure Webex Calling for your organization · section: Create a location (Management > Locations > Add location) · Checked 2026-09-30
33
A location must have a main number if it has any trunks or any extension-only entities such as users, workspaces, virtual lines or features.
Configure Webex Calling for your organization · section: Assign a main number to a location · Checked 2026-09-30
34
The main number is chosen from a drop-down list in the location's settings after the location has numbers, and users can use it as their external caller ID.
Configure Webex Calling for your organization · section: Assign a main number to a location · Checked 2026-09-30
35
If a toll-free number is chosen as the location main number, the emergency callback number must be updated separately because a toll-free number has no emergency service address.
Configure Webex Calling for your organization · section: Assign a main number to a location, toll-free note · Checked 2026-09-30
36
The Activate Numbers Later option makes added numbers available immediately for configuration while they stay inactive until activated, which suits numbers still being ported.
Manage phone numbers in Control Hub · section: Add phone numbers to a location, Activate Numbers Later · Checked 2026-09-30
37
Numbers are added from Services > PSTN & Routing > Numbers by choosing Manage > Add, selecting the location, entering comma-separated numbers and saving.
Manage phone numbers in Control Hub · section: Add phone numbers to a location · Checked 2026-09-30
38
A number can only be deleted when it is unassigned, and the organization's last number cannot be removed.
Manage phone numbers in Control Hub · section: Delete phone numbers · Checked 2026-09-30
39
Numbers must be entered in E.164 format for all countries, except that United States numbers may also use national format.
Manage phone numbers in Control Hub · section: Add phone numbers to a location, number format note · Checked 2026-09-30
40
When a Cloud Connected PSTN provider manages numbers externally, Control Hub shows that number management is disabled by the carrier and the administrator cannot add, delete, activate or modify those numbers there.
Manage external numbers with Control Hub · section: Manage external numbers · Checked 2026-09-30
41
An inactive number assigned to a user or feature remains inactive until it is activated manually or in bulk.
Manage phone numbers in Control Hub · section: Activate phone numbers · Checked 2026-09-30
42
Up to 1,000 numbers can be added in one add operation.
Manage phone numbers in Control Hub · section: Add phone numbers to a location · Checked 2026-09-30
43
Control Hub does not support deactivating numbers once active.
Manage external numbers with Control Hub · section: Manage external numbers, activation note · Checked 2026-09-30
44
When numbers are entered for a non-integrated Cloud Connected PSTN or Premises-based PSTN location, Validate moves valid entries to Validated Numbers and leaves invalid entries with an error message.
Configure Webex Calling for your organization · section: Add numbers during location creation · Checked 2026-09-30
45
The organization-level calling phone-number format (E.164 or National) applies only to locations that do not have an outbound dial digit configured.
Configure dialing behavior for outbound calls · section: Configure dialing behavior, phone number format · Checked 2026-09-30
46
Organization-wide internal dialing is set under Calling > Settings > Service > Internal Dialing, covering location routing prefix length, steering digit, internal extension length and whether extension dialing between locations is allowed.
Configure Webex Calling for your organization · section: Configure internal dialing (organization settings) · Checked 2026-09-30
47
When a location has an outbound dial digit configured, permissive dialing is disabled and E.164 format is always used there, even if the organization format is National.
Configure dialing behavior for outbound calls · section: Configure dialing behavior, outbound dial digit note · Checked 2026-09-30
48
Each outgoing call type can be set to Allow, Block, Require Authorization Code (up to 1,000 codes per location) or auto-transfer to one of three configured numbers.
Outgoing call permissions for Webex Calling locations · section: Permission actions · Checked 2026-09-30
49
Location outgoing permissions default to Allow for most call types, but International and Premium Services I and II default to Block with transfer disabled.
Outgoing call permissions for Webex Calling locations · section: Call types and default settings table · Checked 2026-09-30
50
Location outgoing permissions apply by default to the location's users, workspaces and virtual lines, while custom digit patterns set on an individual user, workspace or virtual line are applied first.
Outgoing call permissions for Webex Calling locations · section: Digit patterns and order of precedence · Checked 2026-09-30
51
Location outgoing call permissions are under Management > Locations > (location) > Calling > Call Handling > Outgoing Call Permissions.
Outgoing call permissions for Webex Calling locations · section: Configure outgoing call permissions for a location · Checked 2026-09-30
52
A trunk must be created before Premises-based PSTN can be configured for a location.
Configure Webex Calling for your organization · section: Set up PSTN connection for a location, Premises-based PSTN prerequisite · Checked 2026-09-30
53
The PSTN connection for a location is set by selecting the location, choosing Manage next to PSTN Connection, acknowledging the risk prompt with Continue, choosing the PSTN option and saving.
Configure Webex Calling for your organization · section: Set up PSTN connection for a location, steps · Checked 2026-09-30
54
Each Webex Calling location uses one PSTN connection option: Cisco Calling Plan (shown as Cisco PSTN), Cloud Connected PSTN, or Premises-based PSTN through a local gateway.
Configure Webex Calling for your organization · section: Set up PSTN connection for a location · Checked 2026-09-30
55
The location routing prefix is 1 to 7 digits including the steering digit, and lets users reach an extension at another location by dialing the prefix plus the extension.
Configure Webex Calling for your organization · section: Configure internal dialing, Location Routing Prefix Length · Checked 2026-09-30
56
Every Webex Calling trunk must be assigned to a location in Control Hub before it can be used.
Configure trunks, route groups, and dial plans for Webex Calling · section: Configure a trunk, prerequisites · Checked 2026-09-30
57
Webex Calling trunks are either registration-based, where the gateway performs SIP registration, or certificate-based, where Webex trusts the gateway by its FQDN and certificate.
Configure trunks, route groups, and dial plans for Webex Calling · section: Configure a trunk, trunk types · Checked 2026-09-30
58
Control Hub's Verify Call Routing tool takes a call source (cloud user, workspace, virtual line or premises trunk) and a number or URI, and shows the outgoing call permissions, fraud prevention, digit patterns, call intercept and translation patterns applied to the call.
Configure trunks, route groups, and dial plans for Webex Calling · section: Verify call routing · Checked 2026-09-30
59
Cisco's configuration workflow orders location-level work as add locations, then configure calling settings (dial plan, premises-based PSTN and trunks), then manage phone numbers, before registering devices and configuring features.
Webex Calling Configuration Workflow · section: Configuration workflow, location and user steps · Checked 2026-09-30
60
Webex Calling outgoing call permissions are set per call type, and the call types are Internal, Toll Free, National, International, Operator Assistance, Chargeable Directory Assistance, Special Services I and II, and Premium Services I and II.
Outgoing call permissions for Webex Calling locations · section 'Permissions by call type' · Checked 2026-09-30

Documents

tier 2 current vendor documentation

Cite this page

APA

WarmTransfer. (2026, September 30). Setting up a Webex Calling location. WarmTransfer. https://warmtransfer.net/guides/webex-calling-location-setup

BibTeX

@misc{warmtransfer-webex-calling-location-setup,
  title  = {Setting up a Webex Calling location},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/webex-calling-location-setup},
  note   = {Verified 2026-09-30}
}

Setting up a Webex Calling location

Before you start

What changes by situation

Step 1 Gather carrier and emergency prerequisites

Do

Verify

Rollback

Do

Verify

Rollback

Do

Verify

Rollback

Step 2 Create the location record

Do

Verify

Rollback

Step 3 Configure PSTN connectivity

Do

Verify

Rollback

Do

Verify

Rollback

Do

Verify

Rollback

Step 4 Add and activate phone numbers

Do

Verify

Rollback

Do

Verify

Rollback

Do

Verify

Rollback

Step 5 Assign the location main number

Do

Verify

Rollback

Step 6 Configure internal and external dialing rules

Do

Verify

Rollback

Do

Verify

Rollback

Step 7 Configure the emergency callback number

Do

Verify

Rollback

Step 8 Configure emergency routing and addresses

Do

Verify

Rollback

Do

Verify

Rollback

Step 9 Establish outgoing call permissions

Do

Verify

Rollback

Step 10 Validate call routing behavior

Do

Verify

Rollback

Applicability

What remains uncertain

See also

Related to

Referenced by

Sources

Documents

Cite this page