08-28-2008 06:15 AM - edited 03-15-2019 12:54 PM
Hi,
Were having issues dialing the UK from or California office. We can dial all of our international sites except the UK. Below is a debug for the dial peer and q931 on the PRI. The number were calling is British Telecom as an example.
Dial String=9011441189241400, Expanded String=9011441189241400, Calling Number=
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH
*Aug 28 13:57:59.577: //-1/1B5FDEA3B9C1/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=34 Is Matched
*Aug 28 13:57:59.577: //-1/1B5FDEA3B9C1/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Aug 28 13:57:59.577: //-1/1B5FDEA3B9C1/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=34
!
*Aug 28 13:57:59.585: ISDN Se0/0/1:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num 4088632913
*Aug 28 13:57:59.589: ISDN Se0/0/1:23 Q931: Applying typeplan for sw-type 0xD is 0x1 0x1, Called num 011441189241400
*Aug 28 13:57:59.589: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0312
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98382
Exclusive, Channel 2
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x2180, '4088632913'
Plan:ISDN, Type:National
Called Party Number i = 0x91, '011441189241400'
Plan:ISDN, Type:International
*Aug 28 13:57:59.693: ISDN Se0/0/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8312
Cause i = 0x829C - Invalid number format (incomplete number)
Any ideas or has someone seen this before?
Thanks.
Solved! Go to Solution.
08-28-2008 12:21 PM
You need to call your provider & ask them what plan & type is required. Then you can change to that using either a translation rule or an isdn map on your PRI interface. I had this same problem where I was able to call certain parts of Europe, but not everywhere. In my case I needed to add
isdn map address 011.* plan isdn type national
which changes all of my International to "type" National.
08-28-2008 06:53 AM
Have you contacted your carrier about this, if so what did they say? Im thinking that maybe they dont want to see the "011" and just want to see the number with the type marked as "international".
08-28-2008 06:55 AM
Hi,
Can you try my number..442079011226.
Also send the full debug isdn q931...
We need to know the direction of the disconnect...Is it from your telco or gateway?
I tried the number from here in London and it works okay..01189241400
08-28-2008 06:59 AM
The number is correct and digit lengt is correct I would like at the type of call you are sending to the Telco perhaps change it to unknown ?
08-28-2008 07:04 AM
Hi,
This is the meaning of the cause code you are experiencing....
Invalid number format...This call happen when you are calling out using a network type number (enterprise) when you should be calling out unknown or national.
Here in the UK we use Unknown..so you may want to change from international to unknown..and try again
08-28-2008 07:38 AM
Thanks,
If this is the second reply sorry...
I have contacted ATT and they said they were able to call the UK from our switch and that the problem was on our router.
Below is all the debug q931 when calling aokanlawon....
*Aug 28 15:34:07.937: ISDN Se0/0/1:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num 4088632913
*Aug 28 15:34:07.941: ISDN Se0/0/1:23 Q931: Applying typeplan for sw-type 0xD is 0x1 0x1, Called num 011442079011226
*Aug 28 15:34:07.941: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0319
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x2180, '4088632913'
Plan:ISDN, Type:National
Called Party Number i = 0x91, '011442079011226'
Plan:ISDN, Type:International
*Aug 28 15:34:08.057: ISDN Se0/0/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8319
Cause i = 0x829C - Invalid number format (incomplete number)
I'm new to voice so I'm just getting started...please be patient....where do I change to unknown??? In the dial-peer cor list??
Thanks for the help.
08-28-2008 07:52 AM
Do you have CCM or express ?if CCM then as a quick test do the following
Locate the gateway you use for the call via the route pattern for 9.11 l, if you are lucky you may have a specific gateway for international calls
2. On the gateway page locate the section -
Call Routing Information - Outbound Calls
3. Look for Called party IE number type and maybe Calling party IE number type and change them to unknown
4. Make a test call again and see if it works. If it does leave it as it is but make test calls on the other possible route patterns in case it effects them
if CME you need to use translations to change the type to unknown on the dial -peer or maybe hard code it directly on the dial-peer for your external calls
08-28-2008 08:18 AM
Thanks,
Here is what my current dial peer looks like after I added the numbering-type unknown...is this the correct command?????
dial-peer voice 34 pots
translation-profile outgoing CALLERID
numbering-type unknown
destination-pattern 9011T
port 0/0/1:23
prefix 011
After the change I still get...
Calling Number=, Called Number=9011441189241400, Peer Info Type=DIALPEER_INFO_SPEECH
*Aug 28 16:11:34.617: //-1/C7FEE611BB49/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9011441189241400
*Aug 28 16:11:34.617: //-1/C7FEE611BB49/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Aug 28 16:11:34.617: //-1/C7FEE611BB49/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=34
*Aug 28 16:11:34.625: ISDN Se0/0/1:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num 4088632913
*Aug 28 16:11:34.629: ISDN Se0/0/1:23 Q931: Applying typeplan for sw-type 0xD is 0x1 0x1, Called num 011441189241400
*Aug 28 16:11:34.629: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0327
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x2180, '4088632913'
Plan:ISDN, Type:National
Called Party Number i = 0x91, '011441189241400'
Plan:ISDN, Type:International
*Aug 28 16:11:34.749: ISDN Se0/0/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8327
Cause i = 0x829C - Invalid number format (incomplete number)
Is this the correct change???
08-28-2008 08:19 AM
Sorry...this is a call manager express router where this is happening.
08-28-2008 08:51 AM
Did ATT say whether or not they want the 011 sent to the switch. I know generally if your PRI is on a 5ess switch, then they dont want to see the 011. Try stripping the 011 and leave the call type as international. I did this just the other day and it worked.
voice translation-rule 1
rule 1 /^9011/ // type unknown international
voice translation-profile INTL
translate called 1
voice-port 0/0/1:23
translate outgoing INTL
Try that and see if the call goes thru. I did this for one of my customers who couldnt dial intl and ATT was their provider.
Hope that helped.
08-28-2008 09:32 AM
08-28-2008 09:33 AM
To answer your question ATT did not say anything about 011 being in the call. When I dial France 011 goes out the PRI with no issue.
08-28-2008 09:41 AM
Mike, see if you can do some testing with your carrier, and they can setup traps in the switch to see what exactly is being sent out when you make the call, and they should be able to tell you what they need to see coming from the router in order for the call to be successful.
I had an issue like this yesterday, the customer could make all intl calls, except for one number in austria. They could even call other numbers in austria with no issue. When we tested with the telco, the issue ended up being in the long distance carrier's switch and they were able to resolve the issue.
Hope that helped.
08-28-2008 10:25 AM
Can you confirm, what call processing agent you are using.
If you are using Callmanager, the change has to be made in callmanager
08-28-2008 10:27 AM
The issue is with CME.
thanks.
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