Unable to place calls to a single Cell User?!?!?

Ben Rodriguez · ‎04-17-2012

So check this out.

CUCM 8.6 w/ MGCP to a PRI. Paetec is the Telco.

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

Apr 16 2012 17:12:54.305: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x319D

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98395

Exclusive, Channel 21

Calling Party Number i = 0x2181, '212xxxxxxx' ********** NUMBER OMITTED HERE FOR PRIVACY *************

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '1914xxxxxxx' ********** NUMBER OMITTED HERE FOR PRIVACY *************

Plan:ISDN, Type:National

Apr 16 2012 17:12:54.385: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0xB19C

Apr 16 2012 17:12:54.385: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x319C

Apr 16 2012 17:12:54.389: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xB19D

Channel ID i = 0xA98395

Exclusive, Channel 21

Apr 16 2012 17:12:55.621: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0xB19B

Cause i = 0x8090 - Normal call clearing

Apr 16 2012 17:12:55.645: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x319B

Apr 16 2012 17:12:55.657: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xB19B

Apr 16 2012 17:12:58.365: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8 callref = 0xB19D

Progress Ind i = 0x8488 - In-band info or appropriate now available

Apr 16 2012 17:12:58.617: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0xB19D

Cause i = 0x8090 - Normal call clearing

Apr 16 2012 17:12:58.637: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x319D

Apr 16 2012 17:12:58.649: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xB19D

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.

Anyone got any ideas?

Thanks very much,

Miles

William Bell · ‎04-17-2012

Well, my first thought was around this line:

CG NetEng wrote:

Called Party Number i = 0xA1, '1914xxxxxxx' ********** NUMBER OMITTED HERE FOR PRIVACY *************

Plan:ISDN, Type:National

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.

Sorry I don't have anything more definitive.

HTH.

Regards,

Bill

http://ucguerrilla.com

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

Julio Cascante · ‎04-18-2012

Hello,

Try the following command under the PRI serial interface:

isdn map address ^1914* plan unknown type unknown

What this does is to tell the router to map the plan type unknown and type unkown to any # that starts with 1914 the * means anything else.

Regards,

Ben Rodriguez · ‎04-18-2012

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.

Thanks for the responses Bill and Julio.

Sorry for the Red Herring.

Miles