09-18-2014 05:25 AM - edited 03-17-2019 12:12 AM
Hello,
I have an issue with one of our branch office where they can't make outbound call to any local number. Whenever they made a call, system prompts say "number cannot be completed as dialed.." but I'm pretty much sure that I have route pattern and correct translation in both of our CUCM and H323 GW. I attached result of debug output and DNA.
Any troubleshooting steps need to be done?
Note: No problem dialing out long distance, just local calls.
System: CUCM System version: 7.1.5.20000-6 and H323GW
In CUCM
9.[2-9]XXXXXX | US Local | PT-AUS-PSTN | RL-AUS-LOCAL | |||
9.[2-9]XX[2-9]XXXXXX | US Local | PT-AUS-PSTN | RL-AUS-LOCAL |
In H323 GW
voice translation-rule 1
rule 1 /\(^51221\)\(57[5-6]..\)/ /\2/
!
voice translation-rule 2
rule 1 /\(^[2-9]......$\)/ /9\1/
rule 2 /\(^[2-9]..[2-9]......$\)/ /91\1/
rule 3 /\(.*$\)/ /9011\1/
!
voice translation-rule 3
rule 1 /\(57[5-6]..$\)/ /51221\1/
rule 2 /^9\([2-9]......$\)/ /\1/
rule 3 /^91\([2-9]..[2-9]......$\)/ /\1/
rule 4 /^9011\(.*$\)/ /\1/
!
voice translation-rule 5
rule 1 /\(^9011.*\)/ /\1/ type any national
!
!
voice translation-profile IN-FROM-XOPRI
translate calling 2
translate called 1
translate redirect-called 3
!
voice translation-profile OUT-TO-XOPRI
translate calling 3
translate called 5
translate redirect-called 3
voice-port 0/0/0:23
translation-profile incoming IN-FROM-XOPRI
translation-profile outgoing OUT-TO-XOPRI
voice-port 0/0/1:23
translation-profile incoming IN-FROM-XOPRI
translation-profile outgoing OUT-TO-XOPRI
dial-peer voice 1 pots
preference 1
incoming called-number .
direct-inward-dial
dial-peer voice 2010 pots
trunkgroup XOPRI
description Local Calls 7-digits
preference 1
destination-pattern 9[2-9]......
forward-digits 7
Solved! Go to Solution.
09-27-2014 05:24 AM
Hi Jhun,
Both the calls selects the same incoming dial peer 3000 and outgoing dial peer 2010.
Both the calls are sent to the same PRI to provider.
Comparing the ISDN setup messages, they are similar to each other wrt calling number, called number, Plan, Type. However, we see that the provider is rejecting one of the calls with reason (Unallocated/unassigned number) and allowing the other.
Successful call:
ISDN setup sent.
Sep 26 01:24:29 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0908
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x2181, '5122157546'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '9205252'
Plan:ISDN, Type:Subscriber(local)
Received call proceed from the provider.
Sep 26 01:24:29 CDT: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8908
Channel ID i = 0xA98381
Exclusive, Channel 1
Sep 26 01:24:29 CDT: //246955/0092E4C3975E/CCAPI/cc_api_call_proceeding:
NAUSVG01-XO#Interface=0x4224DD28, Progress Indication=NULL(0)
Received Alerting from the provider.
Sep 26 01:24:31 CDT: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x8908
Progress Ind i = 0x8088 - In-band info or appropriate now available
Received Connect from the provider.
Sep 26 01:24:31 CDT: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8908
Failed call:
ISDN sent sent to the provider.
Sep 26 01:25:17 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0909
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x2181, '5122157546'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '9829053'
Plan:ISDN, Type:Subscriber(local)
Received Release complete from the provider.
Sep 26 01:25:17 CDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8909
Cause i = 0x8081 - Unallocated/unassigned number
As mentioned by Carlo, its an issue with the provider and you need to check with them.
HTH,
Jagpreet Singh Barmi
09-18-2014 05:39 AM
Hi.
Your provider response is
09-27-2014 04:10 AM
09-27-2014 05:24 AM
Hi Jhun,
Both the calls selects the same incoming dial peer 3000 and outgoing dial peer 2010.
Both the calls are sent to the same PRI to provider.
Comparing the ISDN setup messages, they are similar to each other wrt calling number, called number, Plan, Type. However, we see that the provider is rejecting one of the calls with reason (Unallocated/unassigned number) and allowing the other.
Successful call:
ISDN setup sent.
Sep 26 01:24:29 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0908
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x2181, '5122157546'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '9205252'
Plan:ISDN, Type:Subscriber(local)
Received call proceed from the provider.
Sep 26 01:24:29 CDT: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8908
Channel ID i = 0xA98381
Exclusive, Channel 1
Sep 26 01:24:29 CDT: //246955/0092E4C3975E/CCAPI/cc_api_call_proceeding:
NAUSVG01-XO#Interface=0x4224DD28, Progress Indication=NULL(0)
Received Alerting from the provider.
Sep 26 01:24:31 CDT: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x8908
Progress Ind i = 0x8088 - In-band info or appropriate now available
Received Connect from the provider.
Sep 26 01:24:31 CDT: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8908
Failed call:
ISDN sent sent to the provider.
Sep 26 01:25:17 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0909
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x2181, '5122157546'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '9829053'
Plan:ISDN, Type:Subscriber(local)
Received Release complete from the provider.
Sep 26 01:25:17 CDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8909
Cause i = 0x8081 - Unallocated/unassigned number
As mentioned by Carlo, its an issue with the provider and you need to check with them.
HTH,
Jagpreet Singh Barmi
03-27-2015 11:15 PM
Thank's Guys.. you are right and very sorry for late reply.. this issue was resolved by the provider.
09-18-2014 06:09 AM
Area code 512 requires 10 digit dialing per:
http://www.nanpa.com/enas/area_code_query.do
from log it seems you are sending it as 7 digits. Can you send 10 digits?
Chris
09-27-2014 04:09 AM
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