Calls through Expressway Cluster fail when traversing Second Expressway-C Peer

[j.dewiele]

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.

Any ideas anyone?

[Ayodeji Okanlawon]

Please enable diagnostics loggin on both c and e of the failing pair. Reproduce the issue. Stop the logs once you have finished reproducing it and attach 

it here. Include calling and called number 

Also collect cucm logs for the same call and attach here as well