What are the Rules for Selecting CCA-SP Bridges and Clusters?

What are the rules for selecting CCA-SP Bridges and Clusters?

How does a partner specify the bridge and cluster when preparing a telephony domain request?

Who should a partner contact if they need help with selecting a bridge or cluster?

Rules for selecting CCA-SP bridges and clusters
The CCA-SP Portal requires a partner to specify the bridge and cluster when preparing a telephony domain request. This document provides guidance for making this specification. It comprises the following sections:

  • Definitions
  • Cluster selection
  • Bridge selection
  • Where to get help
The following terms are useful in understanding guidance on how to select a CCA-SP bridge or cluster.
  • Webex Site / URL: A Webex site name (“xxx.webex.com”) is a unique URL, where customer employees can host meetings and have attendees join.  A site can have a unique configuration such as: version, permissions, list of hosts, page branding, and telephony configuration.
  • Webex Cluster: A group of servers in a pool that will share a primary and a secondary location of service across different data centers. Clusters are specific to geographic regions. Each Webex site is tied to a specific cluster.
  • Webex Audio Bridge: A group of devices that is built to host audio calls to Webex meetings. Bridges can have unique configurations, including multiple tenants and call-in/callback parameters.  In CCA-SP, a primary bridge and a backup bridge are termed a set. A partner connects to a set via a peering circuit. The following constraints apply:
    • Bridges are specific to a given region.
    • Partner must be certified on each bridge, so that when capacity on an existing bridge is exhausted, the partner must be certified on another bridge.
    • Each peering circuit must be associated with a unique Routing Profile.
  • Webex Telephony Domain: Telephony domains define a set of telephone numbers that are associated with a specific Webex Cluster and Audio Bridge. Each Webex site must be assigned to a telephony domain. A telephony domain can be shared among sites as long as all sites are on the same Webex cluster. Although a telephony domain is limited to a single cluster; a number set can be “reused”. That is, two or more TDs may have identical number sets, but each TD must be named uniquely and hosted by a distinct cluster. Note that number sets cannot span bridges.
  • Common Media Edge (CME): The CME is a new architecture in which SIP signaling is not tied to a single bridge set. After a partner has migrated to CME, it is no longer necessary to specify the bridge in a telephony domain request.  
Cluster selection
In general, a cluster should be located in the same region as a customer. This minimizes latency on the connection. If that is not possible, e.g., because a partner is not yet certified in the customer’s region, then a cluster should be chosen that is as close as possible to the customer’s region. Practically speaking, this means a cluster in the Eastern US should be used for EMEAR customers, and one in the Western US for APJC customers.
Within a region, if a partner already has a telephony domain provisioned on a cluster, the partner may simply choose to place a new one on the same cluster. For help determining the cluster, see: WBX63978 - How Do I Tell what Cluster My Site is on?
If that is not possible, then the partner may use the following default cluster mapping. In this mapping, “Enterprise” refers to customers who have purchased all Webex services, meaning Webex Meetings, Webex Training, Webex Events, and Webex Support. “Corporate” refers to all other customers:
  • EMEA Enterprise : Cluster W
  • EMEA Corporate: Cluster AI
  • APJ Corporate/Enterprise:  Cluster AS
  • US EC customers: Cluster E
  • US West Corporate:  Cluster S
  • US East Corporate:  Cluster AA
  • US West Enterprise:  Cluster IE
  • US East Enterprise:  Cluster AB

Bridge selection
As stated above, once a partner has migrated to CME, it is not necessary to specify a bridge in a TD request.

Most partners are certified for at most, one bridge set per region. In these cases, once the customer’s region is known, the bridge is pre-determined. If a partner’s TD request team is uncertain about bridge identity, the first line of attack should be to ask the partner’s network team supporting CCA-SP.
In a few cases, a partner is certified for multiple bridges in a region, and has capacity on more than one set. If more than one bridge is available, the desired number set determines the bridge that should be used, since numbers cannot be shared across bridges. If an entirely new set of numbers is to be used, the partner should select the bridge with the greatest remaining capacity, so that the maximum number of new customers can be served by the new number set.

Where to get help

If a partner needs further assistance in selecting a bridge or cluster, please contact Cisco using the Telephony Domain provisioning mailer provided to you during your onboarding by the Cisco team:
  • Example: cca_<partner_name>_td_provisioning@cisco.com

Was this article helpful?