Configure Webex Calling for your organization

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization

Published

2026-08-05

Updated

unknown

Accessed

2026-09-15

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• For a Webex Calling location in a country with neither Cisco Calling Plans nor a Cloud Connected PSTN provider, Local Gateway is the remaining PSTN option. inferred in context
• Cisco positions Webex Calling Premises-based PSTN (Local Gateway) for keeping the current PSTN provider or connecting non-cloud sites with cloud sites. in context
• In Webex Calling each location has exactly one PSTN option, but different locations in the same organization can use different options. in context
• Webex Calling offers three PSTN options per location: Cisco Calling Plans (Cisco PSTN), Cloud Connected PSTN (CCP) and Premises-based PSTN (Local Gateway). in context
• In Webex Calling the PSTN option is chosen per location and each location has exactly one PSTN option, although different locations in the same organization can use different options. in context
• Webex Calling offers three PSTN options when adding a location: Cisco PSTN (Cisco Calling Plan), Cloud Connected PSTN from a certified provider, and premises-based PSTN through a Local Gateway. in context
• 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. in context
• 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 in context
• 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. in context
• 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. in context
• 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. in context
• Only customer administrators can initiate a PSTN connection change, because the change requires signing an E911 agreement. in context
• 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. in context
• 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. in context
• Integrated CCP lets the administrator procure and provision phone numbers from the CCP partner inside Control Hub. in context
• Migrating a location from integrated IntelePeer CCP to Cisco PSTN is listed as unsupported. in context
• Changing an existing location's PSTN connection to Cisco PSTN is not supported for the Japan region. in context
• A location must have a main number assigned if it has any trunks or any extension-only entities. in context
• Non-integrated CCP requires the customer to procure phone numbers from the CCP partner outside Control Hub. in context
• For non-integrated CCP or premises-based PSTN, the location wizard asks for phone numbers as comma-separated values, which are validated before saving. in context
• Each Webex Calling location has only one PSTN option. in context
• When a listed CCP provider shows an Order numbers now option, Cisco recommends choosing it so the location benefits from integrated CCP. in context
• 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. in context
• Premises-based PSTN (Local Gateway) is the option for keeping a current PSTN provider or connecting non-cloud sites with cloud sites. in context
• In the location wizard, only CCP partners that support the location's country are displayed. in context
• 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. in context
• 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). in context
• 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. in context
• 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. in context
• The PSTN connection is chosen per location, and each location has only one PSTN option. in context
• A location with trunks or extension-only entities must have a main number; without one, its trunks are not usable and its extension-only entities cannot make or receive internal or external calls. in context
• 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. in context
• For Cloud Connected PSTN, an Order numbers now option lets integrated providers' numbers be procured from within Control Hub. in context
• 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. in context
• Pre-existing locations that have had other PSTN capabilities assigned are currently not eligible for Cisco Calling Plan. in context
• 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 in context
• 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). in context
• Internal extension length defaults to 4 digits and can be set from 2 to 10 digits. in context
• After the extension length is increased, existing speed dials to internal extensions are not updated automatically. in context
• A location is added from Management > Locations in Control Hub, and on Save the administrator is asked whether to add numbers now or later. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• A trunk must be created before Premises-based PSTN can be configured for a location. in context
• 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. in context
• 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. in context
• 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. in context
• For a Premises-based PSTN (Local Gateway) location, any number port runs between the customer and their own PSTN carriers outside the Cisco Calling Plan port workflow and Cisco PTS; Webex Calling only needs the numbers added to the location and activated in Control Hub. inferred in context
• A PSTN connection change to Cisco Calling Plans may need several port orders (for example when multiple carriers are involved). These orders are linked so they complete together, the location's connection switches only after the last linked order finishes porting, and with multiple carriers this can take up to 10 business days. in context
• An existing location can switch from Premises-based PSTN or non-integrated Cloud Connected PSTN to Cisco Calling Plans through a PSTN connection change in Control Hub (Management > Locations > Calling > PSTN > Manage), which creates the port orders for the location's numbers. disputed in context
• During a PSTN connection change to Cisco Calling Plans, all portable numbers keep working apart from a short interruption at the scheduled port completion time. in context
• A PSTN connection change to Cisco Calling Plans cannot start from an integrated IntelePeer location or from a Dedicated Instance location. Inactive (non-portable) numbers must be cleared first, and only customer administrators can start the change because it requires signing an E911 agreement. in context
• The Cisco Calling Plan prerequisites in the organization setup article say the location must be new, and that pre-existing locations that have had other PSTN capabilities assigned aren't currently eligible. disputed in context
• Each Webex Calling location has exactly one PSTN option (Cisco Calling Plan, Cloud Connected PSTN, or Premises-based PSTN through a local gateway), but different locations can use different options. in context
• Cisco positions Premises-based PSTN (Local Gateway) for customers who want to keep their current PSTN provider or connect non-cloud sites with cloud sites. in context
• A Webex Calling location's PSTN connection is set on the location's Calling tab by choosing Cisco PSTN, Cloud Connected PSTN, or Premises-based PSTN through a Local Gateway. in context
• Creating a Webex Calling location requires a unique location name, a country or region, a full address, announcement and email languages, and a time zone. in context
• Additional Webex Calling locations are created in Control Hub under Management, Location, after the First Time Setup Wizard has created the initial location. in context
• Assigning a main number to a Webex Calling location is mandatory if the location has any trunks or extension-only entities, and the main number serves as the location's default caller ID. in context
• The Webex Calling location article's PSTN connection choices (Cisco PSTN, Cloud Connected PSTN, Local Gateway) do not name Webex Contact Center PSTN, so the Control Hub step that attaches Webex Contact Center PSTN to the dedicated location is not documented there. inferred in context
• A location binds 1 PSTN option, an emergency address used for 911 service, a main number that also serves as external caller identity, a time zone, and a routing prefix. in context
• Assigning a main number to a location is mandatory if the location has any trunks or any extension-only entities. in context
• A location routing prefix may be 1 to 7 digits, and internal extension length is configurable from 2 to 10 digits with a default of 4. in context
• Once a location has a PSTN connection and an emergency service address configured, its address fields cannot be edited from the location overview page; the emergency service address is updated instead and Control Hub then synchronises the overview page address from it. in context
• Deleting a Webex Calling location deletes all of its assigned services and numbers, and Cisco states that the numbers are released back to the PSTN provider and the organisation no longer owns them. in context
• Cisco warns that where user extensions synchronised from Active Directory through Directory Connector already include the location routing prefix, Webex Calling adds the routing prefix again, producing duplicated prefixes. in context
• Cisco states that the outbound dial digit prefix requirement is ignored for outbound calls placed in E.164 format, and that where a national number begins with the same digit as the outbound dial digit the system removes that initial digit, so the outbound dial digit must be added in front of the rest of the national number. in context
• The optional Emergency Location Identifier on a Webex Calling location is sent to the emergency call provider inside the P-Access-Network-Info private SIP extension header, applies only in countries whose regulations require the identity of the cell to be established on an emergency call, and Cisco names France as such a country while stating that the United States and Canada determine location by other methods. in context
• Cisco states that once dialling the outbound dial digit is enforced for a location, any external destination number that does not include it, such as a call forwarding destination, no longer works, while emergency calls may be dialled with or without it. in context
• Where an extension is the same as a national number, Cisco states that the extension takes precedence over the national number, and recommends enabling an outbound dial digit for that reason. in context
• The Allow extension dialing between locations toggle is enabled by default and must be disabled where the same extension exists in more than 1 location; with it disabled, an extension dialled by a caller reaches the matching user in the caller's own location and other locations are reachable only by dialling the enterprise significant number. in context
• Internal extension length is configurable from 2 to 10 digits with a default of 4, and Cisco states that after the extension length is increased, existing speed dials to internal extensions are not automatically updated. in context
• A new Webex Calling location is hosted in the regional data centre corresponding to the country selected in the First Time Setup Wizard, rather than in a data centre chosen per location. in context
• A location that holds a local gateway cannot be deleted while that local gateway is being used for other locations. in context
• A location using premises-based PSTN can select only 1 trunk, and the same trunk can be selected by more than 1 location. in context
• A Webex Calling location routing prefix may be 1 to 7 digits and the length includes the steering digit, so a routing prefix length of 4 leaves only 3 digits to identify the site. in context
• Changing a location's time zone does not update the time zones of features associated with that location, and Cisco names auto attendant, hunt group and call queue as features whose time zone must be edited in each feature's own general settings. in context
• Cisco lists 3 cases where changing a location's PSTN connection to Cisco PSTN is not supported: the Japan region, a location integrated with IntelePeer, and a Dedicated Instance location. in context
• When adding a location, Cisco states that the Cisco PSTN option is only visible if at least 1 committed Cisco Calling Plan Outbound Calling Plan has been purchased, the location is in a supported country, the organisation is hosted in a supported Webex Calling data centre region, and the location is new, because pre-existing locations that have had other PSTN capabilities assigned aren't eligible for the Cisco Calling Plan. disputed in context
• The Emergency Service Address disclaimer required the first time a Cisco PSTN connection is set up at a location must be signed by a customer administrator account, and Cisco states the system does not allow partner administrators or cross-launched customer administrators to sign it. in context
• The organisation configuration article documents changing the PSTN connection of an existing location to Cisco PSTN, naming premises-based Local Gateway locations and non-integrated Cloud Connected PSTN locations as the starting points, and gives an 11-step Control Hub procedure for it. disputed in context
• An integrated Cloud Connected PSTN provider supplies numbers into Control Hub so that procuring and provisioning happen in one place, while a non-integrated provider requires the numbers to be procured from the partner outside Control Hub and entered by hand. in context
• While a location is undergoing a PSTN connection transition its numbers cannot be added, deleted, or moved in or out, while the existing numbers keep working and can still be assigned and unassigned. in context
• In the Control Hub Cloud Connected PSTN partner list, partners displayed with a logo always offer Regional Media for Cloud Connected PSTN, and for a partner displayed as a text string followed by a bracketed region the administrator must choose the region closest to the location's country to obtain Regional Media. in context

Cite this source record

APA

WarmTransfer. (2026, August 5). Configure Webex Calling for your organization. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-njvdjf2-configure-wxc-for-org

BibTeX

@misc{warmtransfer-cisco-help-njvdjf2-configure-wxc-for-org,
  title  = {Configure Webex Calling for your organization},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-njvdjf2-configure-wxc-for-org},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-15}
}