Which two statements regarding Full and Half call model processing are true? (Choose two.)

Question

Options

• AAvaya Aura® Session Manager (SM) always performs Half call model processing.
• BAvaya Aura® Communication Manager (CM) configured as a Feature Server performs Full call
• CAvaya Aura® Communication Manager (CM) configured as an Evolution Server performs Full call
• DAvaya Aura® Session Manager (SM) always performs Full call model processing.

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

Explanation

A and B are correct because Session Manager is architecturally designed as a Back-to-Back User Agent (B2BUA) that splits every call into two independent legs - this is the definition of Half call model, and SM does this always, without exception. Communication Manager configured as a Feature Server offloads endpoint registration to SM and relies on SM to anchor calls, but CM itself processes both legs together as a single complete call - the Full call model.

C is wrong because CM configured as an Evolution Server actually performs Half call model processing. In Evolution Server mode, CM retains local endpoint registrations while SM anchors the SIP routing, so the call is still split into halves by SM's involvement. "Evolution" signals a transitional hybrid mode, not a full standalone processor.

D is wrong because it directly contradicts A - SM never performs Full call model processing; its role as a SIP proxy/B2BUA inherently means it always processes half-calls.

Memory tip: Use the alliteration - "Feature Server = Full call" (two F's). Everything else involving SM is Half, because SM literally "cuts" the call in half as a B2BUA. If you remember that one pairing, you can eliminate C and D instantly.

No community discussion yet for this question.