Hope someone has a solution or something regarding this. Callmanager 4.1, 7961 phone. External phone number mask sometimes is not sent when making an outgoing call, the AS5350 is instead seeing the 4 digit DN being sent. Of course when this happens, the call fails with cause code 28. This seems to happen to certain numbers only.
strip number-of-digits?(Optional) Number of leading digits to be stripped from the original called number before forwarding to the other ephone-dn in the loopback-dn pair. Range is from 1 to 32. Default is to not strip any digits.
That would make sense if we were using CME, but we are using CCM 4.1 with an H323 Gateway. Somewhere along the path from the phone to the gateway, the external phone number mask is being replaced with the directory number. When that happens we get an ISDN cause code 28 on the AS5350 and the caller gets a fast busy.
There are a few. All of the POTS dial-peers that send calls out have no digit-strip configured on them, so the dial-peers were already ruled out, and in fact should have no bearing on this since the DN doesn't match the DID for the examples I have. I get call examples that will show the DN to a number, and then call the same number again and the DID is there. I think it is somehow in the Callmanager that this is happening. When I first got the case, I setup a spare phone and mirrored the customers phone with the exception of the line information, I left off the did and caller name. I made a test call to the numbers in question while running debug isdn q931, and caught the call in progress. I found it got cause code 28. I next went and added the DID to the line information, placed another call to the same number and it went through, aha problem solved. Wrong, the persons line was configured with the DID information, so that wasn't it. At this point I don't know where to look as it is intermittent and not just to this one customer, but to several on this system going out this one trunk group. I have a ticket open with the carrier, Level3, but they have not done much to help, even with several hundred call examples.
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...