Local Gateway design and configuration
Verified 2026-09-04 · 17 claims · sources tier 2
Also known as LGW.
Local Gateway design involves choosing between registration-based and certificate-based architectures, each governed by specific platform requirements and scaling limits 115128. Proper configuration requires understanding these structural boundaries and minimum software versions to maintain reliable call processing 115.
How it works
Registration-based Local Gateway trunks authenticate using SIP digest credentials consisting of a shared username and password 4. Registration-based signalling is established outbound only from the enterprise to Webex Calling over SIP with TLS, so no inbound firewall rule is required 15. Webex Calling ignores the registration expiry value sent by the Local Gateway and enforces a value of 120 seconds, refreshing at approximately half that lifetime 14.
Certificate-based trunks authenticate with mutual certificates plus verification of the Local Gateway fully qualified domain name 4. Certificate-based trunks require a domain claimed and verified in Control Hub together with a DNS A or SRV record, whereas registration-based trunks impose no domain claim or DNS requirement 6. Additionally, a certificate-based Local Gateway must be directly reachable from the internet at a public IPv4 address, using one-to-one static NAT if the gateway itself holds a private address 7.
Video is not supported over Local Gateway call flows, and Cisco recommends an audio-only configuration on those trunks 17.
Platform differences and capacity
Supported Local Gateway hardware includes Cisco IOS XE ISR 1100 and 4000 series routers, Catalyst 8200 and 8300 series, Catalyst 8000V Edge Software, and certified third-party session border controllers, and the Local Gateway may be deployed on premises or hosted by a partner 16. However, registration-based trunks support only Cisco Unified Border Element, whereas certificate-based trunks additionally support several third-party session border controllers 13.
A registration-based Local Gateway trunk on CUBE requires Cisco IOS XE Bengaluru 17.6.1a or later, with 17.12.2 or later recommended 11. Conversely, a certificate-based Local Gateway trunk on CUBE requires Cisco IOS XE Cupertino 17.9.1a or later, with 17.12.2 or later recommended 5.
Concurrency scaling differs drastically between the two models. A registration-based Local Gateway is limited to 250 concurrent calls per registering gateway, a ceiling attributed to TLS and TCP signalling performance 12. Calls exceeding the registration-based Local Gateway concurrency ceiling are rejected by the Webex Calling access session border controller with a SIP 403 Forbidden response 10. Field reports suggest that a migration concentrating many users into a single Webex Calling location served by one registration-based Local Gateway can reach the 250 concurrent call ceiling at peak, producing SIP 403 rejections that look like a carrier fault rather than a design limit 1. In contrast, a certificate-based Local Gateway trunk supports up to 2000 concurrent calls over the internet, an order of magnitude more than the registration-based model 8.
Applicability
The claims in this article apply to multi-tenant and premises-based PSTN commercial deployments current as of September 4, 2026 16.
What remains uncertain
Gaps, disputed items, or specific details readers should verify independently include the exact behavior of third-party session border controllers outside of certified Cisco IOS XE hardware platforms, as well as any future adjustments to concurrency ceilings or forced timer intervals imposed by Webex Calling 161214.
See also
Alternative platform
- Session border controller selection and certificationstub — Certificate-based trunks also accept certified third-party SBCs
Limited by
- SIP trunk capacity and concurrent call planningstub — Trunk model sets the concurrent call ceiling
Requires
- Certificate lifecycle management for voicestub — Certificate-based trunks fail when certificates lapse
- DNS SRV and service discovery for SIPstub — Certificate-based trunks need an A or SRV record
- Firewall ports and IP ranges for cloud callingstub — Reachability depends on the published address and port set
Runs on
- Cisco Unified Border Element configuration and licensingstub — CUBE is the reference Local Gateway platform
Referenced by
- CUCM to Webex Calling migration — Coexistence and premises PSTN both run through the Local Gateway
- Webex Calling PSTN options and selection — Premises-based PSTN is delivered by a Local Gateway
- Teams Phone Direct Routing and SBC certificationstub — Both are BYO-carrier SBC models for a cloud PBX
- Webex Contact Center voice channel and PSTN options — Premises PSTN for Contact Center runs through a Local Gateway trunk
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | A migration that concentrates many users into a single Webex Calling location served by 1 registration-based Local Gateway can reach the 250 concurrent call ceiling at peak, producing SIP 403 rejections that look like a carrier fault rather than a design limit. Cisco Preferred Architecture for Webex Calling — Design Overview · Derived from Registration-based Local Gateway page 23 and Location Definitions pages 60-61 | inference | 0.60 | 2026-09-04 |
| 2 | Webex for Government requires Cisco IOS XE Dublin 17.12.1a or later on the Local Gateway. Configure Local Gateway on Cisco IOS XE for Webex Calling · Webex for Government requirements | fact | 0.90 | 2026-09-04 |
| 3 | During coexistence a Local Gateway can simultaneously provide PSTN access and an interconnect to the existing on-premises call control, and the on-premises call control may remain in permanent use alongside Webex Calling. Cisco Preferred Architecture for Webex Calling — Design Overview · Interconnect with On-Premises Call Control, page 31 | fact | 0.90 | 2026-09-04 |
| 4 | Registration-based trunks authenticate with SIP digest credentials consisting of a shared username and password, while certificate-based trunks authenticate with mutual certificates plus verification of the Local Gateway fully qualified domain name. Get started with Local Gateway · Registration versus certificate comparison table | fact | 0.90 | 2026-09-04 |
| 5 | A certificate-based Local Gateway trunk on CUBE requires Cisco IOS XE Cupertino 17.9.1a or later, with 17.12.2 or later recommended. Configure Local Gateway on Cisco IOS XE for Webex Calling · Platform requirements | fact | 0.90 | 2026-09-04 |
| 6 | Certificate-based trunks require a domain claimed and verified in Control Hub together with a DNS A or SRV record, whereas registration-based trunks impose no domain claim or DNS requirement. Get started with Local Gateway · Registration versus certificate comparison table | fact | 0.90 | 2026-09-04 |
| 7 | A certificate-based Local Gateway must be directly reachable from the internet at a public IPv4 address, using 1-to-one static NAT if the gateway itself holds a private address. Configure trunks, route groups, and dial plans for Webex Calling · Network and certificate requirements | fact | 0.90 | 2026-09-04 |
| 8 | A certificate-based Local Gateway trunk supports up to 2000 concurrent calls over the internet, an order of magnitude more than the registration-based model. Cisco Preferred Architecture for Webex Calling — Design Overview · Table 2, Certificate versus registration based Local Gateway, page 27 | fact | 0.90 | 2026-09-04 |
| 9 | Webex Calling does not support wildcard certificates on the Local Gateway, and only certificates carrying the server authentication extended key usage are accepted. Cisco Preferred Architecture for Webex Calling — Design Overview · Certificate-based Local Gateway, pages 24-25 | fact | 0.90 | 2026-09-04 |
| 10 | Calls exceeding the registration-based Local Gateway concurrency ceiling are rejected by the Webex Calling access session border controller with a SIP 403 Forbidden response. Cisco Preferred Architecture for Webex Calling — Design Overview · Registration-based Local Gateway, page 23 | fact | 0.90 | 2026-09-04 |
| 11 | A registration-based Local Gateway trunk on CUBE requires Cisco IOS XE Bengaluru 17.6.1a or later, with 17.12.2 or later recommended. Configure Local Gateway on Cisco IOS XE for Webex Calling · Platform requirements | fact | 0.90 | 2026-09-04 |
| 12 | A registration-based Local Gateway is limited to 250 concurrent calls per registering gateway, a ceiling attributed to TLS and TCP signalling performance. Cisco Preferred Architecture for Webex Calling — Design Overview · Registration-based Local Gateway, page 23 | fact | 0.90 | 2026-09-04 |
| 13 | Registration-based trunks support only Cisco Unified Border Element, whereas certificate-based trunks additionally support several third-party session border controllers. Get started with Local Gateway · Registration versus certificate comparison table | fact | 0.90 | 2026-09-04 |
| 14 | Webex Calling ignores the registration expiry value sent by the Local Gateway and enforces a value of 120 seconds, refreshing at approximately half that lifetime. Cisco Preferred Architecture for Webex Calling — Design Overview · Registration-based Local Gateway, pages 22-23 | fact | 0.90 | 2026-09-04 |
| 15 | Registration-based Local Gateway signalling is established outbound only from the enterprise to Webex Calling over SIP with TLS, so no inbound firewall rule is required. Cisco Preferred Architecture for Webex Calling — Design Overview · Registration-based Local Gateway, pages 22-23 | fact | 0.90 | 2026-09-04 |
| 16 | Supported Local Gateway hardware includes Cisco IOS XE ISR 1100 and 4000 series routers, Catalyst 8200 and 8300 series, Catalyst 8000V Edge Software, and certified third-party session border controllers; the Local Gateway may be deployed on premises or hosted by a partner. Transitioning from Unified CM to Webex Calling — Deployment Guide · Table 3, Local Gateway | fact | 0.90 | 2026-09-04 |
| 17 | Video is not supported over Local Gateway call flows, and Cisco recommends an audio-only configuration on those trunks. Get started with Local Gateway · Video support note | fact | 0.90 | 2026-09-04 |
Sources
Cisco Preferred Architecture for Webex Calling — Design Overview
Configure Local Gateway on Cisco IOS XE for Webex Calling
Configure trunks, route groups, and dial plans for Webex Calling
Get started with Local Gateway
Transitioning from Unified CM to Webex Calling — Deployment Guide
Cite this page
APA
WarmTransfer. (2026, September 4). Local Gateway design and configuration. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-local-gateway
BibTeX
@misc{warmtransfer-webex-calling-local-gateway,
title = {Local Gateway design and configuration},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/webex-calling-local-gateway},
note = {Verified 2026-09-04}
}