You are configuring Shared Bandwidth Management for Call Admission Control (CAC) between Communication Manager (CM) and Session Manager (SM). Which two tasks must you perform to achieve this?…

Question

Options

• ASpecify the shared bandwidth limit on the Communication Manager (SIP) Entity screen
• BCreate Network Region Groups (NRG) in Communication Manager
• CCreate Locations in Session Manager
• DCreate a Bandwidth Share Group in SM
• EMatch the Network Region used for the SIP users with the Domain in SM

• A
  2% (1)
• B
  86% (36)
• D
  2% (1)
• E
  10% (4)

Explanation

Configuring Shared Bandwidth Management for CAC requires both sides of the CM-SM integration to have their bandwidth structures defined and linked. Network Region Groups (NRGs) in CM (B) are what CM uses to expose grouped bandwidth capacity to SM, and Locations in SM (C) are SM's native construct for bandwidth management - the two are linked together so both systems enforce a shared bandwidth pool rather than each independently policing calls.

A is wrong because the shared bandwidth limit is configured on the SM Location, not on the CM SIP Entity screen - the SIP Entity screen handles connection parameters, not bandwidth sharing. D is wrong because "Bandwidth Share Group" is a fabricated term; SM uses Locations (not a separate Share Group object) to manage bandwidth. E is wrong because matching Network Regions to Domains is relevant to routing and user registration, not to the bandwidth-sharing mechanism - the correct linkage for shared CAC is NRG (CM) ↔ Location (SM).

Memory tip: Think of it as two sides of a bridge - CM builds its side with Network Region Groups, SM builds its side with Locations, and the bridge (shared bandwidth) only works when both sides are constructed.

No community discussion yet for this question.