9.1 Webex Calling Architecture, Locations & Number Management

9.1 Webex Calling Architecture, Locations & Number Management

Cisco Webex Calling is an enterprise-grade cloud Private Branch Exchange (PBX) built upon a globally distributed, multi-tenant microservices architecture. It provides centralized cloud administration, unified communications capabilities, and seamless public switched telephone network (PSTN) connectivity for organizations of all sizes. Designing a cloud telephony deployment requires understanding how physical facilities map into administrative boundaries, how telephone numbering plans are structured, and how statutory emergency calling mandates are enforced.

---

1. Webex Calling Multi-Tenant Architecture

The Webex Calling infrastructure separates the signaling plane from the media plane across globally distributed Cisco data centers.

+-----------------------------------------------------------------------------------------+
|                               CISCO WEBEX CLOUD INFRASTRUCTURE                          |
|                                                                                         |
|   +------------------------------------+    +---------------------------------------+   |
|   |     SIGNALING & CONTROL PLANE      |    |        MEDIA DISTRIBUTION PLANE       |   |
|   | - Session Managers (Active-Active) |    | - Globally Distributed Media PoPs     |   |
|   | - Webex Control Hub API Microserv. |    | - Interactive Connectivity Est. (ICE) |   |
|   | - Policy & Call Routing Engines    |    | - Secure RTP (SRTP) Relays            |   |
|   +-----------------+------------------+    +-------------------+-------------------+   |
|                     |                                           |                       |
+---------------------|-------------------------------------------|-----------------------+
                      | SIP Signaling (TLS 8934)                  | SRTP Media (UDP)
                      v                                           v
       +-------------------------------+           +-----------------------------+
       |    ENTERPRISE BRANCH OFFICE   |           |    REMOTE / NOMADIC USER    |
       | - Dedicated Location Boundary |           | - Webex App (Mobile / PC)   |
       | - Cisco IP Phones (MPP 8800)  |           | - RedSky Dynamic E911 Probe |
       | - Local Gateway / CUBE (mTLS) |           | - Interactive Video / Voice |
       +-------------------------------+           +-----------------------------+

Core Architectural Components

1. Signaling Control Plane: Enterprise endpoints (Webex Multiplatform Phone [MPP] firmware and Webex App clients) register to Cisco's access session border controllers using Session Initiation Protocol (SIP) over Transport Layer Security (TLS), destination TCP port 8934. Active-active microservice clusters across redundant geographic zones handle call state, presence tracking, and supplementary service invocation without a single point of failure.
2. Media Distribution Plane (Media PoPs): Voice and video streams utilize Secure Real-time Transport Protocol (SRTP). Webex Calling optimizes media routing using Interactive Connectivity Establishment (ICE), Session Traversal Utilities for NAT (STUN), and Traversal Using Relays around NAT (TURN). When two registered endpoints reside on the same enterprise campus Local Area Network (LAN), ICE negotiates direct point-to-point media delivery, completely bypassing the cloud media path to conserve WAN bandwidth and eliminate round-trip latency.
3. Cisco Webex Control Hub: A single-pane-of-glass administrative portal providing unified provisioning, role-based access control (RBAC), analytics, historical call detail records (CDRs), and real-time operational troubleshooting telemetry.

---

2. Locations as Administrative Boundaries

In Webex Control Hub, a Location represents a physical campus, branch office, or regional facility. It serves as the primary organizational container and regulatory anchor for user provisioning, PSTN carrier assignment, internal dial plans, and emergency dispatch routing.

Essential Location Attributes

• Physical Address & Country: Defines local telecommunications regulatory boundaries, emergency services jurisdictions, and country-specific PSTN dialing habits (such as domestic 10-digit dialing versus national prefix dialing).
• Time Zone & Announcement Language: Sets local time presentation on IP phone displays and establishes the default audio prompt language for voicemail, system greetings, and automated attendants.
• Internal Dialing: The extension length (2 to 10 digits, default 4) is set organization-wide under Calling > Service Settings > Internal Dialing, while each location gets its own unique routing prefix (1 to 7 digits) for inter-location dialing. Extensions in every location therefore have the same length, for example 1000-1999 in one site and 2000-2999 in another.
• Main Company Number: The central telephone number for the facility. It acts as the default Calling Line ID (CLID) for outbound calls placed by users who do not have an individual Direct Inward Dialing (DID) number, and serves as the destination for general inbound public inquiries.
• Outgoing Calling Permissions: Location-level defaults for which call types users may dial, which users and workspaces can override (Section 9.4).
• PSTN Connection Association: Every location must be linked to a PSTN service model: Cisco Calling Plans, Cloud-Connected PSTN (CC-PSTN), or a customer-managed Premises-Based Local Gateway.

Location Configuration Specifications

---

3. Enterprise Number Management

Webex Calling supports a versatile inventory of telephone number classifications to accommodate complex multinational numbering plans.

+---------------------------------------------------------------------------------------+
|                         CONTROL HUB TELEPHONE NUMBER INVENTORY                        |
+-----------------------------+-----------------------------+---------------------------+
| Direct Inward Dialing (DID) | Toll-Free Numbers (TFN)     | Extension-Only Numbers    |
| - Standard E.164 (+1...)    | - Service/Queue Ingress     | - On-Net Internal Calling |
| - User & Workspace Binding  | - Inbound Customer Care     | - Zero Carrier Cost       |
| - External PSTN Reachable   | - Toll-Free Surcharges      | - No External PSTN Direct |
+-----------------------------+-----------------------------+---------------------------+

Number Types & Assignment

1. Direct Inward Dialing (DID): Globally routable E.164 telephone numbers assigned directly to individual users, executive desks, conference rooms, or critical automated applications. Incoming calls from the public network ring the designated destination without passing through an attendant.
2. Toll-Free Numbers: Numbers where the calling party incurs no charge; the receiving enterprise absorbs all inbound toll costs. Commonly assigned to main customer support queues and sales automated attendants.
3. Extension-Only Numbers: Users, workspaces, and features can have just an extension (2 to 10 digits) with no DID. They are reachable internally, and their outbound PSTN calls present the location's main number as the caller ID. (Webex Calling's separate virtual extensions feature maps an extension to a frequently called external number.)

Assigning Numbers to Target Entities

• Users: Bound to primary calling licenses (such as Webex Calling Professional). A user can be assigned a DID, an extension, or both.
• Workspaces: Configured for collaborative hardware in physical spaces (conference rooms, huddle spaces, lobby desks, warehouse courtesy phones) rather than individual identity accounts.
• Call Routing Applications: Auto Attendants, Hunt Groups, Call Queues, and Paging Groups each require a directory number or extension within the location's dial plan.

Virtual Lines

A Virtual Line is a line with its own extension or number, voicemail, and call settings that is not tied to one person. It can appear on the devices and Webex App of several users or workspaces without a separate license: the organization is entitled to one virtual line per Professional license, and only users and workspaces with a Professional license can host virtual lines.

                              +--------------------------+
                              |       VIRTUAL LINE       |
                              |   Extension: 5500 (DID)  |
                              | "Tier-2 Escalations Desk"|
                              +-------------+------------+
                                            |
               +----------------------------+----------------------------+
               |                                                         |
               v                                                         v
+------------------------------+                          +------------------------------+
|     EXECUTIVE ASSISTANT      |                          |      DEPARTMENT MANAGER      |
| User: Alice (Ext 1001)       |                          | User: Bob (Ext 1002)         |
| Hardware: Cisco 8865 Desk Ph |                          | Hardware: Webex App Desktop  |
| Appearance: Primary (Line 1) |                          | Appearance: Primary (Line 1) |
| Appearance: Line 5500 (Ln 2) |                          | Appearance: Line 5500 (Ln 2) |
+------------------------------+                          +------------------------------+

• Key Operational Capabilities: Supports independent call holding, call transfer, call park, shared line appearances with Busy Lamp Field (BLF) status, and distinct ring cadence settings.
• Common Applications: Executive-assistant line sharing, departmental escalation hotlines, and shared service desk answer pools.
• Licensing Efficiency: Enables organizations to deploy secondary shared line appearances across dozens of phones without procuring dedicated per-seat licenses for non-human entities.

---

4. Regulatory Emergency Calling (E911) Architecture

Providing reliable, precise location data to emergency dispatchers is both a technical requirement and a strict legal obligation. Webex Calling incorporates native tools and third-party integrations to comply with statutory standards.

Statutory Framework: Kari's Law & Ray Baum's Act

• Kari's Law (47 U.S.C. § 623):
  1. Direct 911 Dialing: Telephony systems must permit callers to reach 911 directly without dialing an outside access digit (such as dialing 9 before 911).
  2. Concurrent Notification: The system must generate an automated alert (via email, SMS, or screen pop) to designated on-premises monitoring personnel (such as a security desk or receptionist) whenever a 911 call is initiated, identifying the caller's extension and timestamp.
• Ray Baum's Act (Section 506):
  • Mandates that every 911 call must deliver a dispatchable location to the Public Safety Answering Point (PSAP). A dispatchable location consists of the validated civic street address plus granular room-level details (building, floor, suite, or quadrant) necessary to allow first responders to locate the caller without delay.

Emergency Callback Number (ECBN)

The Emergency Callback Number (ECBN) is the telephone number delivered in the SIP signaling headers (From and P-Asserted-Identity) to the PSAP. If an emergency call drops unexpectedly, the emergency dispatcher dials the ECBN to re-establish immediate contact.

• User-Specific ECBN: Assigned to users with dedicated DIDs. The dispatcher calls back directly to that user's specific desk or mobile client.
• Location-Level ECBN: Assigned to extension-only users who lack personal DIDs. Rather than presenting an unroutable extension or an unmonitored main company IVR number, the location ECBN routes directly to an on-site security office, primary attendant, or dedicated emergency ring group.

Dynamic E911 for Nomadic Users (RedSky Integration)

In modern hybrid work models, employees frequently roam between office floors, remote branches, home offices, and hotels. Static IP-to-address mapping cannot guarantee accurate emergency dispatching.

+---------------------------------------------------------------------------------------+
|                         DYNAMIC E911 ARCHITECTURAL FLOW                               |
|                                                                                       |
|  +------------------+                                                                 |
|  | Nomadic Endpoint |                                                                 |
|  | (Webex App / PC) |                                                                 |
|  +--------+---------+                                                                 |
|           | 1. Discovery Probe: Captures BSSID, Gateway IP, LLDP/CDP Chassis Port     |
|           v                                                                           |
|  +------------------+      2. HELD/PIDF-LO Location Lookup      +------------------+  |
|  | Webex Calling    | ========================================> | RedSky Horizon   |  |
|  | Cloud Core       |                                           | Mobility Engine  |  |
|  +--------+---------+                                           +--------+---------+  |
|           |                                                              |            |
|           | 3. SIP INVITE (with Dispatchable Civic Location XML)         | 4. Match   |
|           v                                                              v            |
|  +---------------------------------------------------------------------------------+  |
|  | Public Safety Answering Point (PSAP) Dispatch Center: "Bldg B, 3rd Floor, Rm 312" |  |
+---------------------------------------------------------------------------------------+

1. Network Discovery Telemetry: When a Webex App client initializes or changes networks, it gathers local network telemetry:
   • Wireless Access Point BSSID (MAC address)
   • LLDP-MED or CDP chassis and port IDs
   • Local IPv4/IPv6 default gateway and subnet
2. Location Resolution: The client communicates with the RedSky Horizon Mobility engine via HTTP Enabled Location Delivery (HELD) protocol. If the network signature matches an enterprise-mapped wireless AP or switch port, the exact dispatchable location (e.g., Campus West, Building 4, Floor 3, Cubicle 312) is retrieved.
3. Nomadic User Prompting: If an off-premises employee connects from an unrecognized Wi-Fi network (such as a residential home or hotel), the Webex App displays a mandatory pop-up requiring the user to confirm or enter their current physical street address.
4. Emergency Call Execution: When the user dials 911, Webex Calling injects a Presence Information Data Format Location Object (PIDF-LO) XML body into the outgoing SIP INVITE, routing the session over dedicated emergency trunks to the geographically appropriate local PSAP.

Emergency Calling Feature Matrix