Everything in this deployment has been working great for months except that outbound caller ID was being overwritten by Paetec to stamp our main number. Yesterday they removed the CID stamp on their side and now I can control the outbound calling number. Very handy, I can announce my DID's and dial *67 to block CID.
But there is a single employee that as of yesterday cannot be called from here. She has a T-mobile cell phone with a 914 area code. I have the CUCM set to stamp the main number on any outbound call where a CID has not been explicitly set so we are sending the same string out as we were before the change. I can call my 917 T-mobile cell fine and see the main number. But dialing her the call just dies. Here is a debug isdn q931
This deployment is a distributed cluster with the other CUCM and another gateway across town. I am able to call her sucessfully from the other location over their Paetec PRI that has not had its CID settings changed by the Telco.
One other thing, I am able to dial 914.555.1212 sucessfully from HQ.
So, what is causing this? I expect I will need to contact Paetec but this is such a subtle problem I wanted to hear from this group first.
Called Party Number i = 0xA1, '1914xxxxxxx' ********** NUMBER OMITTED HERE FOR PRIVACY *************
Some CO switches bulk when you pass type National AND you prefix the "1". You could test without the "1" to see if that changes things. However, I acknowledge that you have been able to call other T-mobile phones (917) and directory service for the 917 NPA. Which lowers the likelihood that a discrepency between the called party digit presentation and numbering type.
Looking at the Disconnect cause code suggests that if there is a problem, it is not happening at the ISDN Q931 level. Something else is pitching a fit here.
I'd first look at comparing the above (known bad) call trace with a known good trace. Preferably the other T-mobile device in the 917 NPA. I would also get Paetec involved and do some tests with their techs on the line.
Well this is embarassing. The user in question has a Samsung Galaxy S2 on T-Mobile. The version of Android on this phone has an auto-reject feature that works with T-mobile to drop blocked numbers. If you press and hold a contact it pops up with a list of options for that contact and the option for Add to Blacklist appears directly under your thumb.
So there was no problem with the CUCM, Gateway, or Telco.
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...