06-16-2005 01:58 PM - edited 03-13-2019 09:30 AM
I am unable to make int'l calls from my system. At first I thought it was the carrier, but the more I test the less sure I am because I have run 931 debug at several branches and am seeing the same thing:
Jun 16 17:19:33.273 EDT: ISDN Se4/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0368
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98396
Exclusive, Channel 22
Display i = 'Jeff Williams'
Calling Party Number i = 0x0081, 'xxxxxxxxxx'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x91, '011441142024150'
Plan:ISDN, Type:International
Jun 16 17:19:33.309 EDT: ISDN Se4/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8368
Channel ID i = 0xA98396
Exclusive, Channel 22
Jun 16 17:19:33.309 EDT: ISDN Se4/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8368
Cause i = 0x829F - Normal, unspecified
Progress Ind i = 0x8488 - In-band info or appropriate now available
Jun 16 17:19:35.020 EDT: ISDN Se4/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0368
Cause i = 0x8090 - Normal call clearing
Jun 16 17:19:35.056 EDT: ISDN Se4/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8368
Jun 16 17:19:35.128 EDT: ISDN Se4/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0368
The number in this debug is just for test- it's for BT. Why would several different LECs react the same way unless there's something common (and wrong) in CCM?
My configuraton is very straight forward: my route filter is (international-access) exists, and my route pattern is 9.@, discard predot.
Any help is greatly apprciated!
Also, any international test numbers would be welcome, too.
Jeff
Solved! Go to Solution.
06-20-2005 09:29 PM
You need to configure CM to strip the 011, but keep the international flag. If telco sees the international flag, they don't want to see 011 and vice versa. Telco will add the 011 when the internationa flag is set. I have had best luck stripping the 011 off and keeping the international flag. From my experience, it's what the carriers like to see.
06-16-2005 03:08 PM
Jeff,
The debug shows that you hung up the call not the carrier, as you are the first to send a disconnect message.
It's probably because nothing happened for almost 2 seconds, so call manager hung up. This is the T310 timeout that has expired, try increasing this to something silly like 30 seconds, or as high as you can get it.
BTW you may also want to set your plan and type to unknown, as this can often lead to problems.
see http://www.zytrax.com/tech/protocols/isdn/timers.html
for a list of ISDN timers.
Paul
06-16-2005 06:04 PM
I am having the same problem.
We have Verizon for local and AT&T for long distance and international.
We can call local and lD, but not international.
I was looking at your debug and your bebug shows that you are senting an international call, My debugs do not show that and that is why the carrier is dropping them, Verizon is telling me that they need to see international in callsetup for them to send the call to AT&T, I have tried unknown, but it did not help.
I was told by verizon, to set gateway settings to NATIONAL and ISDN, as soon as i did that international did not work, before that international worked by caller id did not.
so now i am stuck, either i get caller id or international.
any ideas? my isdn q931 debug shows that " no route to destination" error.
06-16-2005 08:06 PM
Here is the output:
5w3d: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x013E
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
Protocol Profile = Networking Extensions
0xA10F02010106072A8648CE1500040A0100
Component = Invoke component
Invoke Id = 1
Operation = InformationFollowing (calling_name)
Name information in subsequent FACILITY message
Progress Ind i = 0x8083 - Origination address is non-ISDN
Calling Party Number i = 0x2181, '2403141329'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '011911126843576'
Plan:ISDN, Type:National
5w3d: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x813E
Cause i = 0x8282 - No route to specified network
06-20-2005 04:44 PM
most telcos do not want to see 'international' and '011' in the same breath. strip the '011' off the call, and it should go through.
06-20-2005 05:23 PM
So you are telling me that i should dial an international number without the 011?? how would the telco know that it is an international call??
Thanks
06-20-2005 06:54 PM
if you add the 011, you should not tag as international, you should tag as national. You can send international calls without the 011 and tag the call as international. Look at the previous calls. Some have National and some have International in the q.931 messages. What I have seen work the most often is to tag all calls as national and send the 011 on international calls.
06-20-2005 07:16 PM
I tried what you suggested, but got the same results:
UMBI-CMM-CARB1B#
5w5d: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x02AC
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
Protocol Profile = Networking Extensions
0xA10F02010106072A8648CE1500040A0100
Component = Invoke component
Invoke Id = 1
Operation = InformationFollowing (calling_name)
Name information in subsequent FACILITY message
Progress Ind i = 0x8083 - Origination address is non-ISDN
Calling Party Number i = 0x2181, '2403141329'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '011911126843576'
Plan:ISDN, Type:National
5w5d: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x82AC
Cause i = 0x8282 - No route to specified network
06-20-2005 09:29 PM
You need to configure CM to strip the 011, but keep the international flag. If telco sees the international flag, they don't want to see 011 and vice versa. Telco will add the 011 when the internationa flag is set. I have had best luck stripping the 011 off and keeping the international flag. From my experience, it's what the carriers like to see.
06-21-2005 07:26 AM
I admit I was very suspicious of this... but I know I don't know everything so I tried it anyway. I set the route pattern (9.@) to discard 'PreDot IntlAccess IntlDirectDial' and it worked like a champ. Still dialing the exact same number (9011...).
Jun 21 11:10:18.994 EDT: ISDN Se4/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0485
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Display i = 'Jeff Williams'
Calling Party Number i = 0x0081, 'xxxxxxxxxx'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x91, '441142024150'
Plan:ISDN, Type:International
Jun 21 11:10:19.050 EDT: ISDN Se4/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8485
Channel ID i = 0xA98397
Exclusive, Channel 23
Jun 21 11:10:24.313 EDT: ISDN Se4/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x8485
Progress Ind i = 0x8488 - In-band info or appropriate now available
Jun 21 11:10:27.996 EDT: ISDN Se4/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0485
Cause i = 0x8090 - Normal call clearing
Jun 21 11:10:28.032 EDT: ISDN Se4/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8485
Jun 21 11:10:28.104 EDT: ISDN Se4/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0485
Thanks a bunch!
Jeff
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide