Implementation: MCS7835 running CCM 3.1(1) using 7960s & AS5300/H.323 gateway.
Issue: Intermittent dialing delays when dialing local numbers.
Issue Description: When the delay is occuring, you dial local number (e.g., 94531042) the number sits on the screen for 10 seconds without ever changing display from [94531042_] to [TO: 94531042]; then drops the call.
When the delay is not occuring, the screen changes from [94531042_] to [TO: 95431042] almost immediately.
Symptom conclusion: It seems that despite the route or translation patterns, RFs, RLs, DDI, etc.. the symptoms persist to occur intermittently & at random with any local number dialed.
Suspicions: Possible compatibility issue between AS5300/H.323 Gateway & CCM 3.1(1)?
CCM 3.0(9) notable comparisons: In same network, on another MCS7835 running 3.0(9) using same AS5300 and identicle dialing plans, 7960 phones almost instantly show [To: 94531042] on screen, and dial with minimal delays every time.
Thanks for your response. I have a TAC case open & have reviewed several traces (successful calls & failed). Do not see any obvious explanations or variations in the traces for what is happening.
This did catch our eye though:
This NoPotentialMatchesExist is showing on both successful & failed calls so doesn't appear to be the issue.
Additionally, on failed calls it shows that the RL was identified, the gateway device was identified, & then right after identifying gateway device it says:
[extending call to device]
The call then fails. Then there are no more messages in the trace. The very next message is a InboundStim (keepalive) messages between phone & ccm.
TAC has yet to respond to my open case (2 hours old) & I have a 3.1 customer upgrade scheduled for 6pm eastern. We believe that we have reviewed all published caveats but if we can't resolve this problem we are not prepared to deploy 3.1 with these local dialing issues.
Any further guidance you could provide would be very appreciated.
Word: "don't get too buried in the CCM application & abandon the basics".
We have made some progress. We have a physical problem. AS5300 has (2) PRIs coming into it from PSTN. (1) of which is taking massive errors (& guess what, no network management at this customer).
Nevertheless, obviously the problem is not due to CCM 3.1. The (2) pots 9T dial peers on the AS5300 are in tandem so we would only get these issues when we happened to be hitting the dial peer associated with the lame PRI circuit.
Shut it down & now all is well.
However, there is still one remaining issue.
There is a good PRI. We are now researching who is "giving up" on the call & why it's not rerouting to the good PRI.
Any thoughts on call setup timeout values on CCM? I'm hopeful that we can handle the issue (timeout/reroute) on the AS5300 config but for MGCP gateways shouldn't all manipulation be done on CCM?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...