Webex Calling and the Local Gateway

Webex Calling solves the same on-prem-to-cloud problem as Direct Routing, using its own name for the same idea: the Local Gateway.

Cisco's version of the same idea

Webex Calling solves the same problem as Teams Direct Routing, keeping existing on-prem PSTN connectivity while moving call control to the cloud, using its own naming: the Local Gateway. Functionally, a Local Gateway is exactly the SBC role described earlier in this module, just branded for the Webex ecosystem.

What a Local Gateway actually does

The Local Gateway sits on-premises, most commonly Cisco's own CUBE, Cisco Unified Border Element, and registers with Webex Calling in the cloud. It routes calls between Webex-hosted users and whatever sits on-prem, an existing PBX, existing extensions, or a direct connection to an ITSP for PSTN access.

Two ways to reach the PSTN

Webex Calling offers Local Gateway for keeping your own premises-based carrier connection, and a separate option called Cloud Connected PSTN, where a certified partner provider delivers PSTN access entirely in the cloud, no on-prem hardware at all. Which one a business chooses depends mostly on whether they want to keep an existing carrier relationship or hand PSTN connectivity over entirely.

The pattern repeats everywhere

Teams Direct Routing and Webex Calling's Local Gateway are the same architecture wearing two different vendor names: an on-prem SBC, certified by the cloud platform, bridging your existing telephony investment into a cloud-hosted call control system. Once you recognise this shape, most enterprise UC platforms turn out to be variations on it.