International calls failing

[Chris Austin]

We are having calls from the US to UK fail but we can call other countries.

From working with the carrier, the failing calls are being tagged international and as such we do not need to send 011+the number.  When a call is successfull to other countries the call is tagged as unknown and as such the carrier needs to see 011.  I cannot find where Call Manager is able to determine if the call should be tagged international or unknown.  Or why it marks calls to 011-44 international but calls to 011-85 as unknown.

I am using a "standard" 9.011! route pattern for international calls.  My gateway is an h323 with 4 PRI, all of which have international access. 

I was thinking that under the gateway configuration "Call Routing Information - Oubound Calls" that it would be either the Called Party IE Number type or the Called Number Plan.  If I changed that to "unknown" it would  mark/tag all calls as unknown instead of some being international and some not, but it did not work.  I also changed it under the route group settings but that didn't make a difference either.

Does anyone have any suggestions?

[Nadeem Ahmed]

Do you have debug for failed calls normally i have seem some carrier would expect "UNKNONW" in clg and cld party number with prefix 011 and number and some expected exact tagging with international in clg and cld party number without 011 prefix. it would be good idea to check with provider what they are expecting in clg and cld plan and type with number. You can test the both also post the debug isdn q931 debug to see what causing but i would suggest just check once with provider. Br, Nadeem

[Chris Austin]

I have run through the Dialed Number Analyzer (I love that tool) and it is routing as expected.  There is only one route pattern it could match which is the 9.011!.

I don't have an output of the debug I ran earlier but I will try to get one.  However, in the q931 output for the failed call to 011-44 you can see where we are sending the full number 011-44+number and the call is tagged as international.  In the same output for the successfull call you can see the same except it is 011-85+number and it is tagged as unknown.  I was on the phone with the carrier and he informed me that since "we" are tagging the 011-44 call as international they do not need to receive the full 011-44+number just the 44+number.  On the call to 011-85 it was tagged unknown and it would need 011 which we sent and why it was successful.

[Chris Austin]

I forgot to mention that in the q931 debug on the failed call where the call is tagged as internation we get an error back from the carrier for unknown format.  The carrier tech said this was because we were sending the 011 with it.

[Nadeem Ahmed]

either you can create translation pattern or on dial-peer for international one just remove if you have prefix 011 or something. lets say if you have dial-peer voice 9011T pots===then no need doing any stripping of digit or prefexing as provider without 011 and in pots explicit get stripped. best way as you have using H.323 GW create translation pattern or use above method to achieve what provider is expecting . Br, Nadeem

[Brandon Buffin]

Can you try making a separate route pattern for 01144, mark as unknown and send the full number?

Brandon

[Brandon Buffin]

Could there be another route pattern these calls are hitting? Use Dialed Number Analyzer to make sure the call is being routed as you suspect with respect to route pattern, gateway, etc.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/dna/8_6_1/dnaguide.html

Brandon

[Vivek Batra · Accepted solution]

This is really strange. With the same service provider and for call to two different countries, they are expecting different number plan. 

Considering that is what they are expecting, create two translation rules in gateway;

1. For calls made to UK;

rule 2 /^901144\(.*\)$/ /44\1/ type any unknown plan any unknown

2. For calls made to countries other than UK;

rule 1 /^9011\(.*\)$/ /011\1/ type any unknown plan any unknown

Please let us know how it goes then.

- Vivek

[Chris Austin]

This worked!!!!

I tried created a new route pattern for 9.01144! and on the route pattern I set it to "unknown".  Somehow when the call went out the gateway it was still being tagged as ISDN/International.

What fixed it was rule 1 as a translation rule in the gateway.  Since the carrier tech said if we are going to send 011 with the international calls it needed to be unknown this was a blanket rule that would ensure all international calls were unknown/unknown.

This was was difficult because for this configuration a Common RG was created for the over all Device Pool.  The overall DP was used at multiple location which were not having problems.  I was trying avoid making changes in CUCM that would impact route patterns for the Common RG so the change on the local gateway fixed it.

[Vivek Batra]

Thanks for updating the results.

- Vivek