We have three CUCM 8.5 clusters globally, connected via an MPLS network. The North American cluster has a SIP trunk to Polycom DMA- both the North American CUCM cluster and Polycom DMA cluster is within the same data center. I have a SIP trunk between the NA CUCM and DMA so audio calls from CUCM can join conferences within the Polycom world, and have a route pattern in NA CUCM pointed to DMA.
For redundancy/effeciency pusposes, the EMEA and APAC CUCM clusters should also have route patterns/trunks pointing directly to the DMA in North America. However, my concern is that while those local cluster may be able to calculate BW consumption correctly to North America (because they'll define their SIP trunks to be in the "North America" location), since it doesn't traverse through the NA CUCM, the NA "Locations" BW caculation will not show an accurate portrayal of calls active to those remote clusters (or amount of voice BW being consumed on our local MPLS access circuit). Therefore, my preference is to have the remote cluster point their DMA route pattern over our Intercluster Trunks, so WAN BW calculations are correct.
My question is: There is no LOCATIONS "Information sharing" between clusters in CUCM 9.1 (target version), so that EMEA cluster would notify N.A. CUCM cluster that he is utilizing his "NA Locations" for calls (going directly to Polycom DMA), and not going through the NA CUCM cluster, so NA CUCM cluster includes that in his Call Admission Control? I'm comfortable with that not existing in CUCM 8.5, but I know there are Locations/CAC enhancements in 9.1 which I'm not too familiar with.
The Location Bandwidth Manager (LBM) is a Unified CM Feature Service managed from the serviceability web pages and responsible for all of the Enhanced Location CAC bandwidth functions. The LBM can run on any Unified CM subscriber or as a standalone service on a dedicated Unified CM server in the cluster. A minimum of one instance of LBM must run in each cluster to enable Enhanced Location CAC in the cluster. The LBM performs the following functions:
Locations and links path assembly
Bandwidth calculations over the effective paths in the assembly
Servicing bandwidth requests from the Cisco CallManager service (Unified CM call control)
Replication of bandwidth information to other LBMs within the cluster and between clusters when intercluster Enhanced Location CAC is enabled
Providing configured and dynamic information to serviceability
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...