08-22-2019 08:07 AM
Hi, good afternoon.
We had a some disconnect calls incoming from PSTN with cause code 16, the calls dropped when going off-hook. The current version of CUCM is 7.1.5.33900-10, gateway H323 with E1 R2-digital.
We tried a check/unchecked MTP of gateway, check/unchecked Wait for Far End H.245 Terminal Capability Set, reset the gateway on the CUCM, configured the same DN at Ip Communicator but not solve.
In trace for RTMT appears the message: - ERROR: H245 signaling connection aborted!!!
Any suggest to fix the issue.
Attached sample trace for CUCM.
Best regards!
08-22-2019 09:50 AM
This bug doesn't say it affects CUCM 7.x, but perhaps this will lead you to more results.
CSCtq17099
Here is another case. https://community.cisco.com/t5/ip-telephony-and-phones/call-disconnect-errors/td-p/2491395
And they had some pretty good troubleshooting with this one.
https://community.cisco.com/t5/ip-telephony-and-phones/intermittent-dropped-calls/td-p/3024381
Good luck.
08-27-2019 07:33 AM
Hi, I collected new traces and return the messages below:
08/27/2019 09:47:28.054 CCM|DbMobility: getMatchedRemDest starts: cnumber = 1124842598|<CLID::StandAloneCluster><NID:: ><LVL::Detailed><MASK::ffffff>
08/27/2019 09:47:28.054 CCM|DbMobility: getMatchedRemDest: full match case|<CLID::StandAloneCluster><NID:: ><LVL::Detailed><MASK::ffffff>
08/27/2019 09:47:28.054 CCM|DbMobility: can't find remdest 1124842598 in map|<CLID::StandAloneCluster><NID:: ><LVL::Error><MASK::ffffff>
08/27/2019 09:48:16.969 CCM|DbMobility: getMatchedRemDest starts: cnumber = 1150640556|<CLID::StandAloneCluster><NID:: ><LVL::Detailed><MASK::ffffff>
08/27/2019 09:48:16.969 CCM|DbMobility: getMatchedRemDest: full match case|<CLID::StandAloneCluster><NID:: ><LVL::Detailed><MASK::ffffff>
08/27/2019 09:48:16.969 CCM|DbMobility: can't find remdest 1150640556 in map|<CLID::StandAloneCluster><NID:: ><LVL::Error><MASK::ffffff>
08/27/2019 09:48:20.010 CCM|DbMobility: getMatchedRemDest starts: cnumber = 1152783618|<CLID::StandAloneCluster><NID:: ><LVL::Detailed><MASK::ffffff>
08/27/2019 09:48:20.010 CCM|DbMobility: getMatchedRemDest: full match case|<CLID::StandAloneCluster><NID:: ><LVL::Detailed><MASK::ffffff>
08/27/2019 09:48:20.010 CCM|DbMobility: can't find remdest 1152783618 in map|<CLID::StandAloneCluster><NID:: ><LVL::Error><MASK::ffffff>
We checked the SNR feature and not active in our environment.
Any suggested?
Regards
08-27-2019 10:29 AM
Kleber,
It certainly appears to be looking for a remote destination in those traces, which seems strange if you have not set up it. Maybe we can get this post bumped up to Anthony or Maren's attention and they may have an answer for you. This isn't something I have seen before and hopefully they have.
Jason
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: