A customer has just configured Avaya Aura® Media Server (AAMS) on their Avaya Aura® Communication Manager (CM). They are saying that the AAMS is never being used by CM, but instead is always using the

Question

Options

• AThe CM license has no CM Media Server VoIP Channels.
• BNo trunk-group members have been configured,
• CThe VoIP Channel License Limit has not been set on the media-server CM SAT screen.
• DThe Dedicated VoIP Channel Licenses has not been set on the media-server CM SAT screen.

• A
  56% (15)
• B
  26% (7)
• C
  7% (2)
• D
  11% (3)

Explanation

Option A is correct because Avaya uses a two-layer licensing model for AAMS: the Media Server license on WebLM enables the AAMS element itself (explaining why its status shows normal and In-Service), but CM also requires CM Media Server VoIP Channel licenses within its own license file to actually allocate and use those DSP resources. Without those channels licensed on CM, CM has no capacity to route media through AAMS and silently falls back to the G450 gateway DSPs instead.

Why the distractors are wrong:

• B - Trunk-group membership controls call routing paths, not which media resource (gateway vs. media server) handles DSP/RTP processing; missing members would cause call failures, not a silent fallback.
• C & D - The VoIP Channel License Limit and Dedicated VoIP Channel Licenses fields on the CM SAT media-server screen are configuration settings that distribute already-licensed channels; you cannot configure capacity that was never licensed in the first place, making these downstream of the real problem.

Memory tip: Think "WebLM licenses the box, CM licenses the bandwidth." If AAMS looks healthy but never gets used, the missing piece is almost always the VoIP channel count in CM's own license - the gateway is the fallback, not the failure.

No community discussion yet for this question.