Which Call Admission Control mechanism is supported for the Cisco Extension Mobility Cross Cluster solution?
Click on the arrows to vote for the correct answer
A. B. C. D. E.B.
Configuring extension mobility cross cluster (EMCC) is nothing you should take lightly.
EMCC requires a lot of configuration parameters including the exporting and importing of each neighbor clusters X.509v3 digital certificates.
EMCC is supported over SIP trunks only.
Presence is another feature thats only supported over SIP trunks.
If you want to be able to perform scalable Call Admission Control (CAC) in a distributed multi-cluster call processing model, you will need to point an H.225 or Gatekeeper controlled trunk to an H.323 Gatekeeper for CAC but if you want to support presence and EMCC between clusters and maintain CAC.
The Cisco Extension Mobility Cross Cluster (EMCC) solution enables users to access their personal settings, including their user profile and device settings, from any Cisco Unified Communications Manager (CUCM) cluster within their organization. EMCC allows users to move between clusters while maintaining their personalized settings, providing a seamless experience across the enterprise.
In terms of Call Admission Control (CAC) mechanisms, the EMCC solution supports the Intercluster Enhanced Location CAC. This CAC mechanism enables CUCM clusters to exchange information about available bandwidth and call capacity. It uses the concept of locations, which represent physical locations where devices are located, and can be used to define bandwidth requirements for calls made within or between locations.
Intercluster Enhanced Location CAC can be used in conjunction with other CAC mechanisms, such as RSVP CAC or Location CAC, to ensure optimal bandwidth utilization and prevent oversubscription. However, in the case of the EMCC solution, Intercluster Enhanced Location CAC is the primary CAC mechanism used to manage call admission control across clusters.
RSVP CAC is a signaling-based CAC mechanism that uses the Resource Reservation Protocol (RSVP) to reserve network resources for calls. It is typically used in conjunction with other CAC mechanisms, such as Location CAC or Intercluster Enhanced Location CAC.
Location CAC is a CAC mechanism that uses the location-based call admission control policy to ensure that calls are not placed or forwarded to a location that is currently oversubscribed.
H.323 gatekeeper is not a CAC mechanism but rather a call routing and control component used in H.323-based networks.
Visiting cluster's LBM hub is not a CAC mechanism but rather a component used in the Local Route Group feature, which enables CUCM to route calls to the most appropriate gateway based on the location of the calling and called parties.
In summary, the EMCC solution supports Intercluster Enhanced Location CAC as the primary CAC mechanism for managing call admission control across clusters, with the option to use other CAC mechanisms such as RSVP CAC or Location CAC as needed.