CUCM unable to dial one and only one 800 #

[Rolando Valenzuela]

Hi guys,

Today I would like to expose an odd behavior I am having with my CUCM v9 and I would like a few ideas of what else to check.

I have a route pattern like this one: 9.1[2-9]XX[2-9]XXXXXX which works great! for any long distance number, any 800 number except for ONE which is:

800-937-2237 (McAfee technical support phone number) the number works because I have tested it using my cellphone and Skype.

For some reason I cannot dial that number from any of my phones, every time I tried to dial it the call rings, rings and rings but the call is not going anywhere.

I have used the DNA analyser and the call is in fact using the router patter showed above.

I tried using the specific pattern 9.18009372237 but still I having the same results (the calls keeps ringing)

What else can I check?

Thank you!!!

Rolando Valenzuela

PD: I'm not very skilled reading the debug commands like "debug isdn q931" but I can attach it if you want

[will.alvord]

You can check at your gateway to ensure that the call is in fact getting that far although there's no reason to believe that it's not based on what you've provided.  You can avoid debugs and issue a "show call active voice compact".  Your successful cell/skype calls rule out a problem at the far end.  That isolates all but your service provider.  It could be a translation issue or other carrier issue.  I'd open up a ticket with your provider.  In fact, I wouldn't even bother checking the gateway personally.  I'd probably check while I was on hold to open the ticket, but just tell them that your calls to that number are just getting endless ringback.

hope that helps,

will

[Jaime Valencia]

Post the debug isdn Q931 from the call

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[Rolando Valenzuela]

Sure,

Find the debug messages attached.

You will notice the call was made from my extension (6665)

@Will, I will talk with my ISP as well

[Rolando Valenzuela]

Hi guys! another update.

I talked with ATT and the see the call hitting their devices which is good, but the technician told me that the call is failing because the call type is Unknown and I am not sending a 10 digit string (which is incorrect because I have set the external mask for my DN)

What do you think? I'm attaching another example with a working call using the same T1.

Do I need to tweak something in the call manager?

Thank you!!!

[Manish Gogna]

Hi Rolando,

From the debugs we can see that CUCM is sending just the 4 digit calling party number to the gaeway. In case of the non working call recieve a call proceed followed by call progress and then we send out a disconnect as we do not recieve a Connect message for next 12 seconds. I would suggest creating a separate specific Route pattern for this Mcafee number and apply a 10 digit calling party mask as required by them.

HTH

Manish

[Rolando Valenzuela]

Hello all! thank you so much for all the help!! after a lot of troubleshooting we were able to find the solution.

The problem was not AT&T,  at the end the IVR of the numbers we were dialing needed "Earlier Media" so that is what we enable in our gateway and call manager.

-GATEWAY Configuration-
!
!
voice call convert-discpi-to-prog
!
!
interface Serial0/1/0:23
no ip address
isdn switch-type primary-ni
isdn incoming-voice voice
isdn send-alerting
isdn outgoing display-ie
no cdp enable

We needed to enable two option in our trunk configuration

-TRUNK configuration in CUCM-
Media Termination Point Required (enabled) 
MTP Preferred Originating CodecRequired Field (enabled and codec set) 

PD: We do fixed the calling party information from 4 digits to 11 digits (1+ten digits) just to have a standard with AT&T.