|
List Info
Thread: Re: Intl Calls with Verizon in Philadelphia area
|
|
| Re: Intl Calls with Verizon in
Philadelphia area |
 
United States |
2007-08-31 08:56:35 |
What is the cause code that you receive back from the
telco?
I have used translation rules in the past on H323 gateways
to do what you were doing and I do believe that 44 is United
Kingdom and found that the provider was prefixing 011 also
and thus the call failing. I just sent them, for United
Kingdom calls, 44XXXXX and it worked just fine.
Brian
---- CarlosOrtiz bayviewfinancial.com wrote:
> I am not able to send International calls through our
PRI's at a location
> outside of Philly. Local and LD work fine. debugs at
the router show the
> number being sent to the telco are fine.
>
> Debug ISDN q931
>
> Calling Party Number i = 0x2181, '215664XXXX'
> Plan:ISDN, Type:National
> Called Party Number i = 0x91,
'011448458787000'
>
> I found a CCO TAC case where this exact problem is
described and addressed
> by changing the calling plan type from national to
unknown using the
> following command under the D channel interface.
>
> isdn map address .* plan isdn type unknown
>
> This did in fact change the plan type but I was unable
to complete local,
> LD and Intl after adding this.
>
> Any suggestions?
>
> Carlos
>
>
>
>
>
>
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
|
|
| Re: Intl Calls with Verizon in
Philadelphia area |
United States |
2007-08-31 10:06:07 |
|
Here is a test call :
ug 31 11:04:48.367 EDT: ISDN Se0/1/0:23
Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type
13
Aug 31 11:04:48.367 EDT: ISDN Se0/1/0:23
Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type
13
Aug 31 11:04:48.371 EDT: ISDN Se0/1/0:23
Q931: Applying typeplan for sw-type 0xD is 0x1 0x1, Called num 011448458787000
Aug 31 11:04:48.371 EDT: ISDN Se0/1/0:23
Q931: TX -> SETUP pd = 8 callref = 0x0243
Bearer Capability
i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel
ID i = 0xA98393
Exclusive, Channel 19
Progress
Ind i = 0x8183 - Origination address is non-ISDN
Calling
Party Number i = 0x2181, '2156641300'
Plan:ISDN, Type:National
Called Party
Number i = 0x91, '011448458787000'
Plan:ISDN, Type:International
Aug 31 11:04:48.467 EDT: ISDN Se0/1/0:23
Q931: RX <- CALL_PROC pd = 8 callref = 0x8243
Channel
ID i = 0xA98393
Exclusive, Channel 19
Aug 31 11:04:48.583 EDT: ISDN Se0/1/0:23
Q931: RX <- PROGRESS pd = 8 callref = 0x8243
Cause
i = 0xC484 - Vacant code or prefix digit not dialed
Progress
Ind i = 0x8288 - In-band info or appropriate now available
Aug 31 11:04:50.855 EDT: ISDN Se0/2/0:23
Q931: Ux_DLRelInd: DL_REL_IND received from L2
| "Brian E. Henry";
<bhenry33adelphia.net>
08/31/2007 09:56 AM
Please respond to
bhenry33adelphia.net |
|
|
To
| CarlosOrtizbayviewfinancial.com
|
cc
| cisco-voippuck.nether.net
|
|
Subject
Re: [cisco-voip] Intl Calls with Verizon
in Philadelphia area | | |
|
What is the cause code that you receive back from
the telco?
I have used translation rules in the past on H323 gateways to do what you
were doing and I do believe that 44 is United Kingdom and found that the
provider was prefixing 011 also and thus the call failing. I just
sent them, for United Kingdom calls, 44XXXXX and it worked just fine.
Brian
---- CarlosOrtizbayviewfinancial.com wrote:
> I am not able to send International calls through our PRI's at a location
> outside of Philly. Local and LD work fine. debugs at the
router show the
> number being sent to the telco are fine.
>
> Debug ISDN q931
>;
> Calling Party Number i = 0x2181, '215664XXXX'
> Plan:ISDN,
Type:National
> Called Party Number i = 0x91, '011448458787000'
>
> I found a CCO TAC case where this exact problem is described and addressed
> by changing the calling plan type from national to unknown using the
> following command under the D channel interface.
>
> isdn map address .* plan isdn type unknown
>
> This did in fact change the plan type but I was unable to complete
local,
> LD and Intl after adding this.
>
> Any suggestions?
>
> Carlos
>
>
>
>
>
>
>
|
| Re: Intl Calls with Verizon in
Philadelphia area |
|
2007-08-31 10:36:01 |
|
It is more than likely rejecting the call because you have international access code '011' prefixed AND you have the isdn/international designation. Some providers just want one or the other.
Did you try the following under the serial interface for your PRI?
isdn map address 011.* plan unknown type unknown
If you are using MGCP you might change the dot in your route pattern to 9011.! and do digit discard predot.
On 8/31/07,
CarlosOrtizbayviewfinancial.com">CarlosOrtizbayviewfinancial.com < CarlosOrtizbayviewfinancial.com">CarlosOrtizbayviewfinancial.com> wrote:
Here is a test call :
ug 31 11:04:48.367 EDT: ISDN Se0/1/0:23
Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type
13
Aug 31 11:04:48.367 EDT: ISDN Se0/1/0:23
Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type
13
Aug 31 11:04:48.371 EDT: ISDN Se0/1/0:23
Q931: Applying typeplan for sw-type 0xD is 0x1 0x1, Called num 011448458787000
Aug 31 11:04:48.371 EDT: ISDN Se0/1/0:23
Q931: TX -> SETUP pd = 8 callref = 0x0243
Bearer Capability
i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel
ID i = 0xA98393
Exclusive, Channel 19
Progress
Ind i = 0x8183 - Origination address is non-ISDN
Calling
Party Number i = 0x2181, '2156641300'
Plan:ISDN, Type:National
Called Party
Number i = 0x91, '011448458787000'
Plan:ISDN, Type:International
Aug 31 11:04:48.467 EDT: ISDN Se0/1/0:23
Q931: RX <- CALL_PROC pd = 8 callref = 0x8243
Channel
ID i = 0xA98393
Exclusive, Channel 19
Aug 31 11:04:48.583 EDT: ISDN Se0/1/0:23
Q931: RX <- PROGRESS pd = 8 callref = 0x8243
Cause
i = 0xC484 - Vacant code or prefix digit not dialed
Progress
Ind i = 0x8288 - In-band info or appropriate now available
Aug 31 11:04:50.855 EDT: ISDN Se0/2/0:23
Q931: Ux_DLRelInd: DL_REL_IND received from L2
What is the cause code that you receive back from
the telco?
I have used translation rules in the past on H323 gateways to do what you
were doing and I do believe that 44 is United Kingdom and found that the
provider was prefixing 011 also and thus the call failing. I just
sent them, for United Kingdom calls, 44XXXXX and it worked just fine.
Brian
---- CarlosOrtizbayviewfinancial.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">CarlosOrtizbayviewfinancial.com wrote:
> I am not able to send International calls through our PRI's at a location
> outside of Philly. Local and LD work fine. debugs at the
router show the
> number being sent to the telco are fine.
>
> Debug ISDN q931
>;
> Calling Party Number i = 0x2181, '215664XXXX'
> Plan:ISDN,
Type:National
> Called Party Number i = 0x91, '011448458787000'
>
> I found a CCO TAC case where this exact problem is described and addressed
> by changing the calling plan type from national to unknown using the
> following command under the D channel interface.
>
> isdn map address .* plan isdn type unknown
>
> This did in fact change the plan type but I was unable to complete
local,
> LD and Intl after adding this.
>
> Any suggestions?
>
> Carlos
>
>
>
>
>
>
>
_______________________________________________
cisco-voip mailing list
puck.nether.net">cisco-voippuck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
[1-3]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|