sbc trunking · published

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

Limited by

Requires

Runs on

Referenced by

Claims

#ClaimStatusConfidenceVerified
1A 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
inference0.602026-09-04
2Webex 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
fact0.902026-09-04
3During 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
fact0.902026-09-04
4Registration-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
fact0.902026-09-04
5A certificate-based Local Gateway trunk on CUBE requires Cisco IOS XE Cupertino 17.9.1a or later, with 17.12.2 or later recommended.fact0.902026-09-04
6Certificate-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
fact0.902026-09-04
7A 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.fact0.902026-09-04
8A 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
fact0.902026-09-04
9Webex 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
fact0.902026-09-04
10Calls 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
fact0.902026-09-04
11A registration-based Local Gateway trunk on CUBE requires Cisco IOS XE Bengaluru 17.6.1a or later, with 17.12.2 or later recommended.fact0.902026-09-04
12A 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
fact0.902026-09-04
13Registration-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
fact0.902026-09-04
14Webex 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
fact0.902026-09-04
15Registration-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
fact0.902026-09-04
16Supported 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.fact0.902026-09-04
17Video 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
fact0.902026-09-04

Sources

tier 2 current vendor documentation

Cisco Preferred Architecture for Webex Calling — Design Overview

Cisco Systems, Inc. (CTG TME) · 2025-08 · accessed 2026-09-04

tier 2 current vendor documentation

Configure Local Gateway on Cisco IOS XE for Webex Calling

Cisco Systems, Inc. (Webex Help Center) · 2026-07-09 · accessed 2026-09-04

tier 2 current vendor documentation

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

Cisco Systems, Inc. (Webex Help Center) · 2026-04-28 · accessed 2026-09-04

tier 2 current vendor documentation

Get started with Local Gateway

Cisco Systems, Inc. (Webex Help Center) · 2026-07-09 · accessed 2026-09-04

tier 2 current vendor documentation

Transitioning from Unified CM to Webex Calling — Deployment Guide

Cisco Systems, Inc. (CTG TME) · 2025-12 · accessed 2026-09-04

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}
}