Refer to the exhibit.
outgoing SIP TLS data to 10.0.101.111:5061 from 10.0.101.121:43332, size 5430:
BEGINNING OF MESSAGE
INVITE sip:jabberuser@pod1.local 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:
To:
From: ''CCNP Collaboration''
Replaces: 5e158900-10001-ee62f-0@10.0.101.111;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
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''
To:
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
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?
Currently there are no comments in this discussion, be the first to comment!