07-03-2018 07:31 PM - edited 03-18-2019 02:13 PM
Guys,
Have setup a clustered Collab-Edge environment, with the Expressway-Cs neighbouring multiple CUCM Clusters.
The Expressway-C's also have Room TP Licenses with registered SIP Endpoints.
From Endpoint A (registered to Expressway1), I can call to CUCM Cluster 1 (v11.0.1) and vice versa. The logs tell me its a non-traversal call type.
From Endpoint A (same as above), I cannot call CUCM Cluster 2 (v9.1.2) and vice versa. The logs are telling me its a traversal call type. I cannot for the life of me figure out why this call is being marked as traversal? And as I do not have any RMS Licenses installed on the Expressway-C's, the call does not go through..
Has anyone experienced this issue? I have a feeling its the versioning on CUCM that is throwing the licenses out of whack.. however I cant find documentation to back this theory.
Any thoughts?
Ben
07-04-2018 08:02 AM
07-04-2018 04:54 PM
Thanks for your reply..
I can assure you there the path is direct, no inter-working or MS interop.. The Expressway is classifying the call as a traversal when only matching a rule for this CUCM neighour. When I use the same rule and select a different CUCM neighour, the call works fine as the type is a non-traversal..
The only difference is the CUCM Cluster versions.. The CUCM version not working is v9.1.2. Versions that are working are 10.5.2 and 11.0.1. The expressway version is x8.10.4.
I can only 'assume' that the Expressway is not identifying the old CUCM correctly.. hence seeing is a a third-party gatekeeper.. therefore wanting a traversal license to send/receive calls from this neighour.. But I cant find any doco on this..
Have attached the logs for you mate.
8803@... is the VC endpoint registered to Expressway-C
869@.. is the CUCM endpoint
Ben
07-05-2018 10:46 AM
07-05-2018 01:39 PM
07-05-2018 12:24 PM
The issue you are experiencing on calls between EXP-C x8.10.4 and CUCM version 9.1.2 is due to the bug CSCvi82794.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi82794/
It looks like an operability issue with CUCM 9.x and Expressway. We are still looking into this issue. As a workaround, you can set the Neighbor zone profile for the CUCM 9.x to “Default” and go to Configuration > Call Routing > and ensure that call signaling optimization is set to ON.
HTH
Shashank
07-05-2018 01:42 PM
Hi Shashank..
This seems likely.. I have applied the workaround to no avail though mate.. Still consumes a traversal license..
I found out yesterday the actual version of CUCM is 9.1.12 not 9.1.2.
I also have a TAC case opened with Parteek working on this.. SR 684756698
07-16-2018 06:08 PM
Hi Shashank,
Looks like it is BugID:CSCvi82794.. has been updated last week.. no workaround as yet. Looks like the CUCM will need to be bumped up..
Ben
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide