Cisco Bug: CSCtc36395 - Issues with Static locations when using SAF trunk
May 18, 2010
- Cisco Collaboration Systems Release
Known Affected Releases
Symptom: Over subscription or under utilization of WAN links in terms of number of calls when using 'Locations' based CAC. Conditions: Defining Static Locations in CUCM might not work on CUCM in certain scenarios. For example, in a setup there are two CUCM clusters and one CME - Cluster1 and Cluster2 and CME. Cluster1 -- WAN1 -- Cluster2 | | WAN2 | | CME In the above deployment, we cannot specify a bandwidth in Locations for SAF trunk that would represent WAN1 link and WAN2 link separately in cluster1. Depending upon the BW specified there is a potential for over subscription on one of the WAN link. If we had a CUCM cluster3 instead of CME then we could have the remote end configured to reflect the correct WAN link bandwidth and potentially correct the issue. But there is a problem in this approach when cluster1 is used as tandem cluster between cluster2 and 3. We also cannot represent the bandwidth of each location correctly when the three sites are fully meshed.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases