300-825 · Question #21
Refer to the exhibit. Some calls fail to connect after an engineer implements load balancing for a Cisco Meeting Server cluster. The engineer determines that if a call leaves Cisco UCM using the…
The correct answer is B. Cisco UCM is sending calls to a Cisco Meeting Server when the calls are hosted on another Call. See the full explanation below for the reasoning.
Question
Refer to the exhibit. Some calls fail to connect after an engineer implements load balancing for a Cisco Meeting Server cluster. The engineer determines that if a call leaves Cisco UCM using the Cisco Meeting Server 1 SIP trunk, but the conference is already hosted on Cisco Meeting Server 2, then the call fails. If the call leaves Cisco UCM using the Cisco Meeting Server 2 SIP trunk, but the conference is already hosted on Cisco Meeting Server 1, then the call fails. What is the cause of the issue? outgoing SIP TLS data to 10.0.101.111:5061 from 10.0.101.121:43332, size 5430:
BEGINNING OF MESSAGE INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/TLS 10.0.101.121:5061;branch=z9hG4bK6e7932e8ae287a80ee699eb04a6155a2 Call-ID: cf600c54-974c-48e5-92e2-95b1d4b9218f CSeq: 1199885731 INVITE Max-Forwards: 70 Contact: sip:[email protected];transport=tls;isFocus To: sip:[email protected] From: “CCNP Collaboration” sip:[email protected];tag=73a834a850d8ed13 Replaces: [email protected];to-tag=1769141~ba2cc769- 5032-4f8f-a864-9a51 Allow: INVITE, ACK, CANCEL, OPTIONS, INFO, BYE, UPDATE, REFER, SUBSCRIBE, NOTIFY, MESSAGE Supported: timer, X-cisco-callinfo Session-Expires: 1800 Min-SE: 90 User-Agent: Acano CallBridge <SDP omitted> END OF MESSAGE incoming SIP TLS data from 10.0.101.111:5061 to 10.0.101.121:43332, size 402:
BEGINNING OF MESSAGE SIP/2.0 403 Forbidden Via: SIP/2.0/TLS 10.0.101.121:5061;branch=z9hG4bK6e7932e8ae287a80ee699eb04a6155a2 From: “CCNP Collaboration” sip:[email protected];tag=73a834a850d8ed13 To: sip:[email protected];tag=252834177 Date: Mon, 30 Nov 2020 18:25:12 GMT Call-ID: cf600c54-974c-48e5-92e2-95b1d4b9218f CSeq: 1199885731 INVITE Allow-Events: presence Server: Cisco-CUCM12.5 Content-Length: 0 END OF MESSAGE
Options
- ACisco UCM is configured with the wrong X.509 certificate name for the Call Bridge.
- BCisco UCM is sending calls to a Cisco Meeting Server when the calls are hosted on another Call
- CThe Cisco UCM SIP trunk security profile is not configured to accept the replaces header.
- DCisco UCM does not have a SIP trunk to the Call Bridge.
How the community answered
(40 responses)- A3% (1)
- B83% (33)
- C10% (4)
- D5% (2)
Community Discussion
No community discussion yet for this question.