Jabber MRA Fail - No Response between Core and Edge Expressway
Coming off the weekend users aren't able to log into Jabber from an external network. We use an expressway Core/Edge deployment; resolving to our Edge and passing through to the Core.
Checking into the Core/Edge connection I've discovered that the Core Server is unable to connect to the Edge Server (SIP: Failed to connect to <IP> No response from system). I'm able to log into the Edge Server and can verify it's available/online.
I checked the certificate traversal connection and it passed.
Server Certificates are not expired.
We have secondary Core/Edge deployments and both Core2 and Edge2 are able to see each other. Configurations are nearly mirrored for both Core1&2 and Edge1&2
Re: Jabber MRA Fail - No Response between Core and Edge Expressway
First is to start collecting logs on the failed node in the cluster. Then go through the logs and see what is going on. You can also share it here so anyone can help you. If this is urgent then I recommend you open a support case to Cisco TAC.
Please rate replies and mark question as "answered" if applicable.
To participate in this event, please use the button to ask your questions
This topic is a chance to discuss more about how to read Cisco Unified Communications trace files. In this session, Cisco D...
Join us on Thursday, October 3 at 10 am PT for a live chat detailing how Cisco can provide the security for your collaboration tools. In today's agile work environment - customers need to collaborate in real time with partners, vendors and customers,...