<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

Zoom Connectivity Architecture

Zoom connectivity is delivered as a Layer-3 hub-and-spoke VPN on the Tata Communications MPLS backbone. The Zoom cloud virtual circuit is the hub; your customer sites are the spokes. Traffic flows over the MPLS backbone using Layer-3 VPN technology. 

Tata Communications peers with Zoom once per Zoom location (not per customer) and distributes Zoom’s public routes to your sites inside a dedicated VPN. Resiliency comes from dual peering within a Zoom region, with the customer choosing the primary and secondary zone at the Zoom application level. The customer is advertised toward Zoom only as a single /32 public NAT address.

Region-based peering and resiliency

Zoom groups its locations into regions and provides primary and secondary peering from locations within the same region for resiliency. Tata Communications establishes a primary and a secondary NNI with the Zoom cloud platform in different MPLS(PoP)  locations that fall under the regions Zoom supports (for example, an India region served from Mumbai and Hyderabad, or an APAC region served from Singapore and Tokyo).

A single EBGP session is established with the Zoom cloud platform per NNI, configured under a VRF-Lite routing domain. Zoom does not support a separate EBGP session per customer - both locations of a region are configured under the same VRF-Lite, so your sites receive Zoom’s public prefixes from both locations of the region.

How the resilient path is chosen

Within a region, Zoom advertises each location’s own prefixes without AS-PATH prepend and the other location’s prefixes with AS-PATH prepend. Tata Communications therefore receives the location-specific prefixes with a higher Local Preference and the other-location prefixes with the default Local Preference. The two peerings act active/active, and your CPE receives the prefixes of both locations.

Failover is handled at your Zoom application level: because your CPE holds Zoom’s public routes for both resilient locations in the region, you choose which location is your primary and which is secondary (the primary and secondary Zoom zone) in your Zoom configuration. Zoom mandates a dual virtual circuit for each customer.

Addressing

  • The EBGP session between Tata Communications and Zoom uses a /30 public non-routable (PNR) IP, mutually agreed at NNI turn-up.

  • Each customer site is allocated a /32 public PNR IP by Tata Communications, configured on the customer CPE for NAT/PAT. This /32 is the only customer address advertised toward Zoom.

  • Tata Communications receives only Zoom’s public prefixes over the peering and advertises them to your sites; your sites advertise only the /32 PNR toward Zoom.

        Per-customer segregation

        A separate VRF is configured for each customer so that Zoom voice services are segregated from existing data services. The hub-and-spoke VPN is arranged so that the two regional hubs do not communicate with each other directly. Internally, routes are exchanged between the customer VPN and the Zoom VPN with fast-convergence settings so reconvergence is quick after a change.

        Service characteristics

        Characteristic

        Support on Zoom connectivity

        IP addressing

        /30 PNR for the Tata Communications–Zoom peering; /32 public PNR per customer for NAT/PAT

        BFD

        Supported, with a 1000 ms timer and a multiplier of 3

        Quality of service

        Zoom does not support QoS; a single class of service applies on the Tata Communications MPLS backbone

        Multicast

        Not supported

        IPv6

        Not supported by Zoom

        Related pages