Calls through Expressway Cluster fail when traversing Second Expressway-C Peer
I have Expressway-C/E clusters configured with two peers each.
When I place a B2B call through the cluster the calls always succeed when they traverse the first Expressway-C peer: the configuration primary.
When the calls traverse the second Expressway-C peer the calls fail but are registered as "missed calls" at the remote client. The calls fail immediately after the 180 ringing is sent from the remote edge. The source CUCM sends a CANCEL in response to receiving the 180 ringing. This looks very much like a media negotiation failure but I don't understand why this would happen for calls traversing the one expressway-c but not the other.
There are no errors reported anywhere in the system. We're using x8.11.
Hi, My name is JanetMy portal ID is https://nwswdvcas-taw.my.webex.com/meet/janet.dvcasI do want you please to delete both my accounts with Webex (free and Paid)So my organisation can join me on another Webex Account as another Host. I did foll...
Our beginner online classes are designed to help IT Admins plan, deploy, and manage their Webex Control Hub environment. Start off by learning what critical elements are needed to deploy Control Hub or move into Webex features that can be used to better ...
I need to modify the SIP header. When I call to the PSTN, the header SIP show From email@example.com (Gateway - Private IP 172.24.10.6) and i need firstname.lastname@example.org (Gateway - Public IP 184.108.40.206). How can I change in theGateway the ...