04-16-2014 03:36 AM - edited 03-16-2019 10:29 PM
Good day colleagues.
I faced with a strange situation please help to understand.
There are two CUCM-a first CUCM1 v6.0, second CUCM2 v8.6.
between CUCM Inter-Cluster Trunk, a call to both sides successfully passes. But if the call immediately after the conversation, the call passes but not heard on either side, and 18-19 seconds after the connection is dropped. But if after a successful call to wait for about a minute and call everything works perfectly. It turns out that one of the CUCM can not immediately end the call and the session hangs. Anyone else encountered this problem?
Solved! Go to Solution.
04-21-2014 03:40 AM
The issue is on the other side. The other side of the trunk is not sending the OLC and OLCAck, causing a media timeout on this cluster where the call is made from.
04-21-2014 08:28 AM
It's difficult to say without looking at the other side. However, it could be
1/ that a media resource such as an MTP/Xcoder may be needed on the other side, and for the second call, this fails. This is less likely because why should only the second call fail?
2/ a defect that the 6.0 cluster is hitting in the h323 protocol stack, causing this issue. This is most likely. The ICT may be behaving in a weird manner.
04-16-2014 05:10 AM
Hello,
I'm not sure I understand your problem clearly. Do you mean that if you make a second call immediately after ending the first call, you have no way audio on the call? And if you make the second call after a minute, there is no problem?
hantale
Sree
04-16-2014 05:23 AM
Hello Sree,
Yes, you are right.
I think after the first call session for a long time (about 1 minute) is not closed.
04-16-2014 05:27 AM
Do you see this with particular phones only? Or is this across all phones?
Is this happening only for skinny/sip phones or both?
Has this ever worked before?
We need to look at detailed CUCM traces to see what's happening. Here's a doc which walks through what needs to be set in the CUCM traces.
https://supportforums.cisco.com/document/126941/cucm-trace-lookup-different-scenarios
04-17-2014 12:53 AM
1. All phones
2. For both phones
3. No, it is a new connection
Which output in RTMT needed for fix this problem?
04-17-2014 12:54 AM
We need detailed Cisco CallManager traces to see what's happening.In RTMT, you'll need to go to Collect Files -> select CCM service from all services and collect them for a time period.
04-17-2014 09:15 PM
04-17-2014 11:52 PM
What are the called and calling numbers? Did you face the issue on the second call?
04-18-2014 12:05 AM
I am call from 1199 to 222 numbers and backward. Yes
(my route pattern 8.xxx and 8.xxxx)
04-18-2014 01:22 AM
I am seeing only calls from 2219, 2216, 2215, 2224, 2234 dialing to 222. Is it one of these calling numbers?
04-18-2014 02:46 AM
No calling number 1199, buy the way, how you see the traces?
Calling time: 17 Aprel 08:40
04-18-2014 03:53 AM
There are no traces for that time in the logs that you have provided.
I extracted the CiscoCallManager SDI and SDL trace zip files, and then searched for dd="222" in them. This stands for Digits Dialed. Every time the digits are dialed, there will be such an instance in the traces.
04-20-2014 11:12 PM
04-20-2014 11:56 PM
Dear ciscoazersun,
I checked the trace and am unable to find any call made to 222. Can you please check if the interval you selected for collecting the traces was right?
04-21-2014 12:47 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: