350-801 · Question #159
Which two approaches are taken to implement CAC within Cisco UCM in full-mesh topology? (Choose two.)
The correct answer is B. RSVP-enabled locations C. location-based CAC. Call Admission Control (CAC) in Cisco UCM is implemented using the Locations model. In a full-mesh topology, two approaches work together: (C) Location-based CAC, where bandwidth pools are defined per location and UCM tracks usage against configured limits; and (B) RSVP-enabled…
Question
Which two approaches are taken to implement CAC within Cisco UCM in full-mesh topology? (Choose two.)
Options
- Adevice pool
- BRSVP-enabled locations
- Clocation-based CAC
- DAudio Codec Preference List
- Ephysical location
How the community answered
(17 responses)- A6% (1)
- B94% (16)
Explanation
Call Admission Control (CAC) in Cisco UCM is implemented using the Locations model. In a full-mesh topology, two approaches work together: (C) Location-based CAC, where bandwidth pools are defined per location and UCM tracks usage against configured limits; and (B) RSVP-enabled locations, where UCM uses Resource Reservation Protocol to dynamically reserve bandwidth end-to-end before admitting a call, providing more precise control in complex mesh topologies. Device pools (Choice A) are an administrative grouping construct, not a CAC mechanism. Audio Codec Preference Lists (Choice D) influence codec selection, not admission control. Physical location (Choice E) refers to a UCM field for informational purposes, not a CAC mechanism.
Topics
Community Discussion
No community discussion yet for this question.