Call Admission Control (CAC) Sharing allows which two components of Avaya Aura to centrally coordinate the allocation of bandwidth for calls? (Choose two.)

Question

Options

• AAvaya Aura Communication Manager (CM)
• BAvaya Aura Session Manager (SM)
• CAvaya Aura System Manager (SMGR)
• DAvaya Aura Media Server (AAMS)

• A
  92% (24)
• C
  4% (1)
• D
  4% (1)

Explanation

CAC Sharing is specifically designed as a joint coordination mechanism between Communication Manager (CM) and Session Manager (SM), enabling them to exchange real-time bandwidth usage data so neither component over-allocates WAN capacity independently - CM manages traditional/H.323 call paths while SM manages SIP routing, and together they enforce a unified bandwidth budget across both domains.

Why the distractors are wrong:

• System Manager (SMGR) is an administrative/management platform used to configure the Aura suite - it does not participate in real-time call signaling or bandwidth enforcement.
• Avaya Aura Media Server (AAMS) handles media processing tasks like transcoding and conferencing - it processes media streams but plays no role in admission control decisions.

Memory tip: Think of CAC Sharing as a "traffic agreement" between the two call-handling engines - CM (the legacy/H.323 side) and SM (the SIP side). SMGR is the administrator (manages configs, not calls), and AAMS is the media worker (handles audio, not routing decisions). Only the two components that actually admit calls need to share CAC data.

No community discussion yet for this question.