Source record · tier 2 current vendor documentation

Configure trunks, route groups, and dial plans for Webex Calling

Publisher: Cisco
URL: https://help.webex.com/en-us/article/n0xb944/Configure-trunks,-route-groups,-and-dial-plans-for-Webex-Calling
Published: 2026-09-07
Updated: unknown
Accessed: 2026-09-24
HTTP status: 200
License: Cisco website terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

A Webex Calling dial plan is configured once for the whole enterprise, holds dial patterns for on-premises destinations (ESN/on-net numbers, +E.164 patterns, SIP URI domains) with wildcards ! and X, and names a trunk or route group as its routing choice. in context
A Webex Calling route group holds between 1 and 10 trunks, and calls are distributed randomly among trunks of the same priority. in context
A Webex Calling trunk can be deleted only when it is not in use. in context
Control Hub shows each trunk's status as online, offline, unknown or impaired under Calling > Call Routing > Trunk; online means every Webex Calling Edge proxy connected to the Local Gateway, and status refreshes every 3 minutes. in context
Calls to On-Premises Extensions is enabled per location: calls from that location to an unknown 2-10 digit extension go to the selected route group or trunk, bounded by a Maximum Unknown Extension Length. in context
A certificate-based trunk requires a verified domain, accepts the SBC address as an FQDN or SRV, and that address must be unique across the organization. in context
Cisco recommends copying the registering trunk information from Control Hub into a local file for use when configuring the Local Gateway. in context
A trunk can be deleted in Control Hub only when it is not in use. in context
Webex Calling dial plans route calls matching enterprise extension, E.164 or SIP URI domain patterns to on-premises destinations through a trunk or route group. in context
A location uses the gateway for PSTN when its PSTN connection is set to Premises-based PSTN (Local Gateway) under Calling > Locations > Assign or Manage. in context
The Control Hub trunk's Max Concurrent Calls value must be set according to the Local Gateway's capacity. in context
After a registering trunk is created, Control Hub shows the Register Domain, Trunk Group OTG/DTG, Line/Port, Outbound Proxy Address, and a username and password. in context
Lost registering-trunk credentials can't be recovered; they must be regenerated from the trunk information screen with Retrieve Username and Reset Password. in context
A route group holds up to 10 trunks with priorities; calls are spread randomly among same-priority trunks and fall back to lower priorities when higher ones fail. in context
A Webex Calling trunk name can't be more than 24 characters long. in context
A Local Gateway trunk is created in Control Hub under Services > Calling > Call Routing > Trunk with Add Trunk. in context
Control Hub reports a trunk as Online, Offline, Impaired or Unknown; Unknown means connection in progress for a newly added gateway and Impaired means at least one Webex Calling edge proxy can't connect to it. in context
When adding a trunk, Control Hub asks for a location, a trunk name, and a trunk type of Registering or Certificate-based; certificate-based trunks also take a device type, SBC address, domain and port. in context
A Webex Calling trunk is added in Control Hub under Services > Calling > Call Routing > Trunk with a location, trunk type and, for certificate-based trunks, a device type. in context
A Webex Calling certificate-based trunk uses mutual TLS and its certificate must carry the SBC FQDN as common name or subject alternative name. in context
Webex Calling dial plans route calls matching dial patterns (E.164, enterprise significant numbers or SIP URI domains) to a trunk or route group, are configured globally and apply to all users regardless of location. in context
The Webex Calling trunk Dual Identity Support setting changes how the From and P-Asserted-Identity headers are populated on the initial INVITE sent to the Local Gateway. in context
Webex Calling can route unknown 2 to 10 digit extensions from a location to a selected trunk or route group when Calls to On-Premises Extensions is enabled for that location. in context
A Webex Calling route group holds up to 10 trunks with priorities for load balancing and redundancy. in context
Only SBCs that appear in the Control Hub trunk device-type list are validated as Webex Calling Local Gateways. in context
A Webex Calling trunk is a connection between Webex Calling and the premises, terminated on a supported session border controller acting as a Local Gateway, which interconnects the trunk with on-premises PSTN and/or a PBX. in context
A Webex Calling trunk can be deleted from its Actions menu only when it is not in use. in context
Webex Calling trunks are registration-based, where the SBC registers to Webex Calling, or certificate-based, where Webex Calling reaches the SBC by FQDN or SRV address using a certificate from a supported CA. in context
The Control Hub Verify Call Routing tool simulates a call and shows the routing decision including permissions, digit patterns and translation patterns. in context

Cite this source record

APA

WarmTransfer. (2026, September 7). Configure trunks, route groups, and dial plans for Webex Calling. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-n0xb944-trunks-route-groups-dial-plans-b

BibTeX

@misc{warmtransfer-cisco-help-n0xb944-trunks-route-groups-dial-plans-b,
  title  = {Configure trunks, route groups, and dial plans for Webex Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-n0xb944-trunks-route-groups-dial-plans-b},
  note   = {Cisco, accessed 2026-09-24}
}