Webex Calling now includes a dedicated cloud instance option based on the Cisco Unified Communications Manager architecture. Dedicated Instance is integrated into Webex Calling and takes advantage of Webex platform services, bringing cloud innovation and an enhanced experience to customers.

The Dedicated Instance add-on for Webex Calling includes:

• Cisco Unified Communications Manager

• Cisco Unified IM and Presence

• Cisco Unified Unity Connection

• Cisco Expressway

• Cisco Emergency Responder (Americas region only)

The Dedicated Instance service is primarily delivered over a private connection to the customer premises. This document details the Partner Connect option for customers to use with Webex to extend their organization to Webex Calling – Dedicated Instance.

The Partner Connect model lets partners aggregate all the customer networks and extend the connectivity to their Webex Calling Dedicated Instance.

In a Partner Connect model, the partner uses direct connection or ECX to use with Webex and establish the following:

• Partner's Management and Operations Framework

  • Dedicated Instance Application Management Interface access

  • Management Applications access to their customer apps, for example, Domain Managers

• Partner's Customer Aggregation Framemwork

  • Aggregate customer networks and extend their connection to their respective Dedicated Instance

• Partner's Supplemental Services Framework

  • Cloud based, software services and manages services to the customer

The following section shows two connectivity options for Partners to use with Webex for Dedicated Instance.

Direct : The connectivity is established over direct physical connections between Cisco and the partner at a designated Equinix facility. Virtual Routing and Forwarding (VRF) and Border Gateway Protocol (BGP) sessions are configured across these connections per the Cisco routing policy. Currently, direct connectivity facilities are available at Equinix Data Centers in North America, Europe, Australia, and APJ.

Equinix Cloud Exchange Fabric™ : Exchange connectivity enables partners to interconnect with Cisco virtually, if they are in any Equinix data center around the globe and enabled with Equinix Cloud Exchange Fabric (Equinix Fabric™). With a physical connection to Equinix Fabric (negotiated between partner and Equinix), the partner simply initiates virtual connections from a portal or by invoking Cloud Exchange APIs. Similarly, VRFs (Equinix Fabric virtual connections) and BGP sessions are configured across the connection.

Direct (Cross Connect)	Equinix Cloud Exchange
Two points in each geographic region.	30+ points in the Americas and EMEAR. APJ is targeted for Q1CY2020.
Americas = Dallas, Tx & San Jose, CA - or - EMEA = London, UK & Amsterdam, NL - or - ALJ - Tokyo, JP & Singapore, SG - or - AUS = Sydney, AU & Melbourne, AU - or - EU = Frankfurt, GE & Amsterdam, NL	Available at any Equinix ECX-powered location.
Only charge is for physical connection; no additional charges per customer or virtual connections.	Charge for physical connection and each virtual connection. A virtual connection is required for each customer.
1 G or 10 G connection bandwidth.	Bandwidth options for 200 MB to 10 GB.

Webex Calling Dedicated Instance has the following IP Addressing and ASN requirements.

• Public /31 or /30 for each Physical connection link

  • Direct: 4 Subnets per Geo

  • Equinix Fabric: 4 Subnets per Geo

• Public ASN for BGP Routing between partner and Cisco

• /16 Network per Geo for partner management of UC Applications

Note: The partner’s equipment must support Layer 3 sub-interfaces with dot1q tagging, used for VRF separation. The provided subnets can be shared across all VRFs but must be unique for each physical link. Public addressing of the link subnets and public ASN ensures uniqueness across all partners offering the service and is mandatory. These link subnets will not be routed outside the service.

Partners aggregate customer networks and extend them to their appropriate Dedicated Instance. Partners can plan to use one or multiple of the below options.

MPLS	SD-WAN	VPN
QoS-aware Convenient routing into existing customer networks More costly option VARs/MSPs may require a partner-to-partner agreement: Cross-connects LOAs	Rapid deployment option Re-use existing public Internet Cisco Viptela, Meraki, or other third-party SD-WAN Requires partner-hosted equipment and per-customer premises equipment	Rapid deployment option Re-use existing public Internet Multiple VPN technologies: Dynamic multipoint VPN Site-to-site IPsec Not suitable for more Advanced customer WANs (multi-site) In contrast, SD-WAN provides quicker scale and more flexible mangement

Note: This is not an exhaustive list of customer network aggregation options for partners.

To operationalize a new customer, partner must provide a Dot1Q tag while opening a request in Control Hub, Calling > Dedicated Instance > Cloud Connectivity > , click on Activate for Partner connect.

Select the Region and provide the Dot1Qtags with ranges. The timeline to complete the connection in the Webex datacenters is 10 business days.

Important Notes:

1. For partners to leverage partner connect to extend Webex Calling and Meetings traffic for their customers, they will have to host a NAT server and create an additional connection using a Dot1Q tag.

2. The Partner Connect model cannot be leveraged for Webex Calling and Meetings without the Dedicated Instance add-on.