What statement about the H.323 to SIP routing is true?

Question

Options

• AAvaya Aura® Communication Manager does feature processing for both endpoints.
• BAvaya Aura® Communication Manager does feature processing for H.323 endpoint only.
• CAvaya Aura® Communication Manager does feature processing for SIP endpoint only.
• DAvaya Aura® Communication Manager does not do feature processing for any endpoint in this

• A
  88% (22)
• C
  4% (1)
• D
  8% (2)

Explanation

When a call is routed between an H.323 endpoint and a SIP endpoint through Avaya Aura® Communication Manager (CM), CM acts as the central feature processing engine for both endpoints - this is the key architectural role CM plays as a back-to-back call controller, applying dial plans, features (hold, transfer, conferencing, etc.), and class of service for all parties involved.

Why the distractors are wrong:

• B is wrong because CM doesn't limit feature processing to just H.323 endpoints; SIP calls passing through CM are equally subject to its feature logic.
• C is wrong for the same reason in reverse - H.323 endpoints don't lose feature processing just because the other leg is SIP.
• D is wrong because the entire value proposition of routing calls through CM (rather than peer-to-peer) is precisely that CM does perform feature processing; bypassing CM would mean losing those features.

Memory tip: Think of CM as a "translator booth" sitting in the middle of every H.323↔SIP call. The translator handles the conversation rules for both speakers - not just one side. If CM weren't doing feature processing for both, there'd be no reason to route through it at all.

No community discussion yet for this question.