Webex Calling architecture and deployment models

See also

Sources

1. 1
   The Storage region setting that determines where Webex Calling stores an organisation's call recordings applies only when Webex is the call recording provider, and Cisco states that if a provider other than Webex is chosen the storage region setting does not display.

   Manage call recording for Webex Calling · Enable call recording at organization level, step 3 · Checked 2026-09-16
2. 2
   Cisco states that Webex Calling users can be set up to use Webex Calling services from within Microsoft Teams, and that the administrator selects the default calling application for the organisation while individual users may be configured to use other applications.

   Cisco Preferred Architecture for Webex Calling — Design Overview · Introduction, Supported Devices · Checked 2026-09-16
3. 3
   Each Webex Calling customer is provisioned on one Webex Calling instance, all provisioning information for that customer is stored in that instance, and the SIP signalling of every endpoint and Local Gateway provisioned for that customer is tied to the instance the customer is provisioned on.

   Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Webex Calling Data Centers · Checked 2026-09-16
4. 4
   Each Webex Calling data centre hosts the call routing functions and holds customer calling configuration data, and also hosts 2 tiers of session border controller: access SBCs that terminate all customer-facing SIP connections from Local Gateways endpoints and soft clients, and peering SBCs that terminate the SIP peering connections to SIP service providers.

   Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Webex Calling Data Centers · Checked 2026-09-16
5. 5
   Cisco states that the Webex Calling data centre location information does not apply to Webex Calling Dedicated Instance.

   Data Center locations for Webex Calling · closing note after Table 2 · Checked 2026-09-16
6. 6
   Cisco describes Dedicated Instance as an entitlement within Webex Calling that provides a Cisco Unified Communications Manager based stack of applications in a private cloud dedicated to a single customer.

   Cisco Preferred Architecture for Webex Calling — Design Overview · Introduction, Webex Calling Solution Overview, Dedicated Instance paragraph · Checked 2026-09-16
7. 7
   The Preferred Architecture design overview dated August 2025 lists the Webex Calling regions as the United States Canada Europe the United Kingdom Australia Japan and Saudi Arabia, and names no Indian region, while the data centre article dated 14 November 2025 lists Chennai and Mumbai among the data centres.

   Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, paragraph following Figure 1, against Table 1 of the data centre article · Checked 2026-09-16
8. 8
   Webex Edge Connect peers a customer's Webex meetings and Webex Calling traffic with an Equinix Cloud Exchange location to provide guaranteed bandwidth and quality of service, and Cisco offers it as the access connectivity option beyond over-the-top Internet.

   Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Webex Edge Connect · Checked 2026-09-16
9. 9
   For an inter-region call the access session border controllers in both regions anchor the media, the traffic between those access SBCs traverses the global Webex backbone, and only the part of the media flow between the endpoints and their own region's access SBC traverses the Internet as the access network.

   Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Figure 4 Inter-region Media Flow with Regional Access SBC · Checked 2026-09-16
10. 10
    Media flows involving a Local Gateway are always anchored on the access session border controllers of the region in which that Local Gateway is deployed.

    Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, paragraph following Figure 4 · Checked 2026-09-16
11. 11
    In Cisco's worked example of a call between 2 phones in Australia for a customer assigned to the United States region, the media path is kept on the access session border controllers in the Australia region under the control of the United States instance while the SIP signalling for the call goes back to the call control entity in the United States region, and Cisco describes that regional media path as the fallback that ICE optimization can replace with a direct path.

    Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Figure 3 Regional Access SBCs, worked example · Checked 2026-09-16
12. 12
    Webex Calling uses SIP for signalling and SRTP for media, the Webex App and phones and registering Local Gateways initiate a TLS signalling connection to Webex Calling and are authenticated by it, and Webex Calling sends signalling traffic back over that same connection, which Cisco describes as providing simple firewall traversal; dynamic NAT can be used for IP phone and registration-based Local Gateway addresses.

    Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, paragraph following Figure 1 · Checked 2026-09-16
13. 13
    For over-the-top connections Cisco states that the network between Webex Calling and on-premises endpoints and Local Gateways should have at most 100 ms one-way latency, 10 ms packet jitter and 0.5 percent packet loss.

    Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Over-the-top TLS Connections · Checked 2026-09-16
14. 14
    Cisco states that the initial Webex Calling region selection cannot be changed later, that the decision should be taken early in a transition to avoid excessive signalling round-trip delay, and recommends selecting the Webex Calling instance that provides the lowest signalling round-trip times for the largest number of users in the deployment.

    Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Webex Calling Data Centers · Checked 2026-09-16
15. 15
    The region selection for a Webex Calling customer determines the location of the authoritative call control entity for all of that customer's calls, and Cisco states that all Webex Calling call control entities can use access resources in each region so that media for calls anchored on the access layer need not cross to the customer's own region.

    Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Figure 3 Regional Access SBCs · Checked 2026-09-16
16. 16
    Cisco lists 16 Webex Calling data centres in 4 geographies: North America with Chicago Dallas Vancouver and Toronto, Europe with Amsterdam Frankfurt Manchester and London, Asia Pacific with Melbourne Sydney Osaka Tokyo Chennai and Mumbai, and Middle East and Africa with Jeddah and Riyadh, and 8 additional media points of presence at Los Angeles New Jersey Dallas Singapore Seoul Sao Paulo Cape Town and the United Arab Emirates.

    Data Center locations for Webex Calling · Table 1 Webex Calling Data centers and Table 2 Additional Webex Calling Media PoP, read as cells · Checked 2026-09-16
17. 17
    Cisco states that Webex Calling supports video calls between video capable Cisco phones including the 8845 8865 and 8875, Webex Devices, and the Webex App on desktop and mobile when configured with Webex Calling for users.

    Cisco Preferred Architecture for Webex Calling — Design Overview · Introduction, Video Support · Checked 2026-09-16
18. 18
    Wholesale Route-to-Market is a Webex channel solution aimed at the small and medium business segment through service providers, in which Cisco charges the partner a fixed transfer price per package, bills monthly in arrears for the net number of active licences prorated to each customer's activation date, and the partner provisions through Partner Hub, Control Hub or the Wholesale APIs without registering each customer in Cisco Commerce Workplace.

    Wholesale Route-to-Market Solution Guide · Overview of Wholesale Route-to-Market · Checked 2026-09-16
19. 19
    The Wholesale Route-to-Market Solution Guide lists the packages its offer includes twice and differently: its introduction names 9 including Attendant Console and Cisco Calling Plan, and its overview section names 7 and includes neither while naming Standard Calling and Enhanced Calling where the introduction says Webex Calling standard and Enhanced Calling Package.

    Wholesale Route-to-Market Solution Guide · Introduction package list against Overview of Wholesale Route-to-Market package list · Checked 2026-09-16
20. 20
    The target architecture adds Webex Calling as the cloud call service, Cisco Directory Connector or the Entra ID wizard application for identity synchronisation, a Local Gateway for PSTN access and Unified CM interoperation, and a Survivability Gateway for fallback calling during outages; Cisco Calling Plan and Cloud Connect require no on-premises equipment.

    Transitioning from Unified CM to Webex Calling — Deployment Guide · Core components, Table 3 · Checked 2026-09-04
21. 21
    No entry explicitly marked as deprecated or end-of-support with an associated date was found in the portion of the Webex Calling release notes that was read; the page is large and was not read in full, so this is not evidence that none exist.inferred

    What's new in Webex Calling · Partial read of the dated entry list · Checked 2026-09-04
22. 22
    Feature entries dated within a month of the research date included called-number based call screening with Mutare on 3 September 2026, Cisco Wireless Phone 9821 support and streamlined certificate management for Local Gateways on 31 August 2026, and enhanced recording notification controls and a new Connections tab in Control Hub on 5 August 2026.

    What's new in Webex Calling · Dated entry list · Checked 2026-09-04
23. 23
    The Webex Calling release notes page is a rolling document whose displayed last-updated date equalled the research date, so claims derived from Webex Calling feature availability go stale quickly.

    What's new in Webex Calling · Page last-updated element · Checked 2026-09-04
24. 24
    Webex Calling divides EMEA into 3 region identifiers with distinct data centre pairs: EU served from London and Frankfurt, EUN served from Frankfurt and Amsterdam, and UK served from London and Manchester.

    Webex Calling Data Centers in the EMEA region · Identifier and DC Locations table · Checked 2026-09-05
25. 25
    The first Webex Calling location created in Control Hub becomes the organisation's Calling region.

    Data Center locations for Webex Calling · body text preceding the data centre table · Checked 2026-09-05
26. 26
    Cisco states that a customer's Webex Calling region cannot be changed once assigned.

    Webex Calling Data Centers in the EMEA region · paragraph following the region identifier table · Checked 2026-09-05
27. 27
    A registration-based local gateway supports up to 250 concurrent calls and a certificate-based local gateway supports more, up to 6,500 depending on connectivity type and session border controller model.

    Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide · page 33, premises-based PSTN connection · Checked 2026-09-05

Documents

Cite this page

WarmTransfer. (2026, September 16). Webex Calling architecture and deployment models. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-architecture

@misc{warmtransfer-webex-calling-architecture,
  title  = {Webex Calling architecture and deployment models},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-calling-architecture},
  note   = {Verified 2026-09-16}
}