Can not make international call issue

Unanswered Question
Jan 28th, 2009
User Badges:


1 T1PRI connected to vendor for incoming and outgoing calls.

9.@ as normal route pattern for outgoing calls.

44001.!# is test route pattern for T1PRI line;

The issue is, when dial 9011xxxxxxx to make international call, it failed with fast busy tone. When using 44001 011xxxxxxx# to test, it works which means no issue on the vendor side.

Both 9.@ and 44001.!# are configured as below:

Route Pattern

Partition: Global_PT

Numbering Plan: North American Numbering Plan

Gateway or Route List: PSTN

Route Option Route this pattern

Which others do I need to check?


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
testeven Wed, 01/28/2009 - 12:00
User Badges:
  • Cisco Employee,


Which and how many digits are sent to the TELCO?

You can get a debug isdn q931 from the GW and place a call using each RP. See if you are sending the call with the exact same digits. Be careful not to send 011........... to your TELCO and also sending the call as an international call. If that's the case probably the TELCO is attaching an additional 011 making the called number 011011........... As that is an invalid number, maybe that is why you are getting the fast busy.

Hope this helps!



Jaime Valencia Wed, 01/28/2009 - 12:09
User Badges:
  • Cisco Employee,
  • Hall of Fame,


MGCP or H323?

does telco expect call to be marked as international or national??

how many digits?


testeven Wed, 01/28/2009 - 15:18
User Badges:
  • Cisco Employee,

Did you check the debugs to see who sends the disconnect message and how many digits are sent and how many digits the TELCO expects?

Also see if you have a misconfigured Route Filter on the 9.@ RP and the Plan/Type, probably needs to be Unknown instead of International.



jeffshen1215 Fri, 01/30/2009 - 10:15
User Badges:

1. There is no Route Filter configured (none)in 9.@ RP of international call_Partition.

2. due to authorization limit, I don't have access to do the GW debug, all i can do is to get a CDR record.


jeffshen1215 Fri, 01/30/2009 - 10:25
User Badges:

Here is my understanding of the issue:

1. Since 44001.!# RP works, so there should be no service interuption on the T1 provider side.

Am I right?

2. Is there any difference between 9.@ and 44001.!# RP?

Both of them are configured as international call partition, NANP, and Route list, etc.

Why 44001.!# works while 9.@ doesn't?


This Discussion