300-820 · Question #223
After an engineer implements load balancing in the Cisco CMS cluster, they observe that shortly after the second Call Bridge is added to the cluster, call into a space randomly disconnect when the…
The correct answer is D. Enable "Accept Replaces Header" on the SIP Trunk security profile on Cisco UCM. When CMS load balances calls across multiple Call Bridges, it may need to move a call leg from one Call Bridge to another. This is accomplished using the SIP 'Replaces' header, which instructs the remote end (UCM in this case) to replace an existing call dialog with a new one…
Question
After an engineer implements load balancing in the Cisco CMS cluster, they observe that shortly after the second Call Bridge is added to the cluster, call into a space randomly disconnect when the calls are from endpoints registered with Cisco UCM. Which action resolves the issue?
Options
- AEnable "Accept Unsolicited Notification" on the SIP Trunk security profile.
- BEnable "Accept Presence Subscription" on the SIP Trunk security profile on Cisco UCM.
- CEnable "Accept Out-of-dialog REFER" on the SIP Trunk security profile".
- DEnable "Accept Replaces Header" on the SIP Trunk security profile on Cisco UCM.
How the community answered
(39 responses)- A15% (6)
- B8% (3)
- C3% (1)
- D74% (29)
Explanation
When CMS load balances calls across multiple Call Bridges, it may need to move a call leg from one Call Bridge to another. This is accomplished using the SIP 'Replaces' header, which instructs the remote end (UCM in this case) to replace an existing call dialog with a new one. By default, Cisco UCM's SIP Trunk security profile does not accept the Replaces header, causing the call to fail/disconnect when CMS attempts the load-balancing transfer. Enabling 'Accept Replaces Header' on the SIP Trunk security profile in Cisco UCM allows UCM to process these requests correctly. Options A, B, and C address different SIP behaviors (unsolicited NOTIFYs, presence subscriptions, and out-of-dialog REFERs) that are unrelated to the load-balancing disconnect scenario.
Topics
Community Discussion
No community discussion yet for this question.