Using queue at the edge with ELCAC, which two configurations in Cisco UCM are correct? (Choose two.)

Question

Options

• ASet a SIP trunk towards each SIP proxy for IP originated calls. This SIP trunk should use Location=Shadow.
• BConfigure SIP Profile to Reroute Incoming Request using Call-Info header with purpose=x cisco-origin.
• CSet a SIP trunk towards each CVP Call Server for IP originated calls. This SIP trunk should use Location=Phantom.
• DConfigure SIP profile to Reroute Incoming Request using Contact-Info header with purpose=x-cisco- origIP
• ECreate a UCM SIP Profile with Reroute Incoming request based on Contact Header.

• A
  72% (21)
• C
  14% (4)
• D
  3% (1)
• E
  10% (3)

Explanation

When implementing Queue at the Edge with ELCAC (Enhanced Location Call Admission Control) in Cisco UCM, Option A is correct because SIP trunks pointing to SIP proxies for IP-originated calls must use the Shadow location - Shadow is a special ELCAC location that doesn't consume bandwidth from the actual location, allowing UCM to properly track and queue calls when bandwidth limits are reached. Option B is correct because the SIP Profile must be configured to reroute incoming requests using the Call-Info header with purpose=x-cisco-origin, which signals UCM to identify the true origination point of a call and apply the appropriate location-based CAC policy.

Option C is wrong on two counts: the trunk destination should be a SIP proxy, not a CVP Call Server, and the location should be Shadow, not Phantom (Phantom is a different ELCAC construct used for virtual locations). Option D uses the wrong header - it says Contact-Info, but the correct header is Call-Info - and the purpose value "x-cisco-origIP" is fabricated. Option E is too vague and technically wrong; rerouting based on the generic "Contact Header" does not carry the origin information that ELCAC requires.

Memory tip: Think "S-C" - Shadow location on the SIP trunk, Call-Info header in the SIP Profile. Both configurations are about properly identifying and tracking where a call came from so ELCAC can make accurate bandwidth decisions.

No community discussion yet for this question.