[cisco-voip] Wacky telco issues... cannot call the UK
Kevin Thorngren
kthorngr at cisco.com
Tue Dec 1 08:36:57 EST 2009
Further info....
IOS has default Plan and Type values for the supported switch types
based on the specs for that switch. IOS validates the plan and type
in the h225 setup message against the default values for the outgoing
switch type. If they don't match then IOS sets the values to the
default for the ISDN setup message. The reason for this is that the
VOIP leg can set the type and plan values independent of specs for the
outgoing ISDN switch. These defaults can be overridden by using
translation rules and/or isdn map address. The isdn map address
configuration takes precedence over any applied translation rules.
For example this is the default plan and type settings for primary-ni:
7 digits - plan = isdn type = subscriber/local
10 digits - plan = isdn type = national
15 digits - plan = isdn type = international
everything else is set to plan = unknown type = unknown
Your RP sets the plan and type to unknown. The number you called is
15 digits:
Called Party Number i = 0x91, '011441787883195'
When the GW created the ISDN setup message it checked the default
rules and found that the number is 15 digits, marked the h225 type and
plan as invalid and set the type/plan for the outgoing ISDN setup
message to international/ISDN:
Nov 30 18:28:20.394 CST: ISDN Se0/1/0:23 Q931: pak_private_number:
Invalid type/plan 0x0 0x0 may be overriden; sw-type 13
Hope this helps clear up the mystery of your call routing to the UK,
France and Belgium.
Kevin
On Dec 1, 2009, at 7:50 AM, Justin Steinberg wrote:
> are you sure IOS was sending out calls to other counties with
> unknown unknown? IOS may have some logic related to the number of
> digits in the number as to when it adds the international type.
>
> It could also be that IOS was sending all calls out as international
> and your International provider was using a special route to UK
> where it was being rejected there and sent back to you.
>
> I always use that isdn map command for international calls and send
> calls out with the leading 011 and unknown/unknown and never have
> any trouble. Just add it to your template and you should be good
> from here out.
>
> Justin
>
> On Tue, Dec 1, 2009 at 12:58 AM, Jonathan Charles
> <jonvoip at gmail.com> wrote:
> We had telco out, they plugged something (I wasn't on site at the
> time) into the back of the smartjack and called the UK without a
> problem.
>
> The same RP on CCM is able to call Europe, Oceania, Asia, etc.
>
> For some reason, calls to the UK were hitting the gateway (outbound)
> as ISDN International while all other international calls were going
> unknown unknown... as soon as we forced unknown unknown, the calls
> worked...
>
> My question was, where is this type and plan coming from....
>
> Telco denied it, and CCM was only doing it for calls to the UK (there
> are two international RPs, one with a # and one without.... both force
> called type and plan to unknown unknown....)
>
>
> Jonathan
>
> On Mon, Nov 30, 2009 at 11:25 PM, Nick Matthews
> <matthnick at gmail.com> wrote:
> > There can always be something downstream from the provider causing
> > that issue - some switch in the UK perhaps?
> >
> > The difference is going to be seen when you compare the isdn q931
> > debugs from the working and non-working case. We see a number of
> > these problems - only 1800 numbers, only cell phone numbers, etc and
> > it's because of the provider's interconnect to other switches.
> >
> >
> > -nick
> >
> > On Mon, Nov 30, 2009 at 9:45 PM, Jonathan Charles
> <jonvoip at gmail.com> wrote:
> >> Right, but why would it do it for JUST the UK?
> >>
> >> I mean, it doesn't do it for France or Belgium...
> >>
> >> And it isn't stripping the 011...
> >>
> >> And I have super, double-secret, uber-confirmed that it is an
> NI2...
> >>
> >>
> >>
> >>
> >>
> >> Jonathan
> >>
> >> On Mon, Nov 30, 2009 at 7:58 PM, Nick Matthews
> <matthnick at gmail.com> wrote:
> >>> I believe there is something in the spec of some of the ISDN
> switch
> >>> types that dictates this change. I believe the change is along
> the
> >>> lines of 'strip the 011 and put international in the plan or
> type', by
> >>> default. This is an interop issue and can also be fixed
> sometimes by
> >>> changing the switch type. Basically the router is trying to play
> >>> nicely in terms of interop, but sometimes the other vendor doesn't
> >>> like that. You would have a problem either way, and this is
> just the
> >>> less likely scenario. You can blame the ISDN people for that :)
> >>>
> >>> -nick
> >>>
> >>> On Mon, Nov 30, 2009 at 8:29 PM, Jonathan Charles <jonvoip at gmail.com
> > wrote:
> >>>> To be honest, I doubt it...
> >>>>
> >>>>
> >>>> J
> >>>>
> >>>> On Mon, Nov 30, 2009 at 7:17 PM, Mike Taylor <mtaylor at employees.org
> > wrote:
> >>>>> Mate, I wish I could explain why.... All I know is, it does
> work...
> >>>>>
> >>>>> We had to add that to a dedicated Vodafone to get it to pass
> caller-id
> >>>>> correctly...
> >>>>>
> >>>>> Maybe a Cisco person could explain how it works?
> >>>>>
> >>>>> :-)
> >>>>>
> >>>>> Mike
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Jonathan Charles [mailto:jonvoip at gmail.com]
> >>>>> Sent: Tuesday, 1 December 2009 1:30 p.m.
> >>>>> To: Mike Taylor
> >>>>> Cc: Mike Lydick; cisco-voip
> >>>>> Subject: Re: [cisco-voip] Wacky telco issues... cannot call
> the UK
> >>>>>
> >>>>> This fixed it... but why???
> >>>>>
> >>>>> How was it getting tagged ISDN International in the first
> place???
> >>>>>
> >>>>>
> >>>>> Jonathan
> >>>>>
> >>>>> On Mon, Nov 30, 2009 at 6:11 PM, Mike Taylor <mtaylor at employees.org
> > wrote:
> >>>>>> Does this help?
> >>>>>>
> >>>>>> !
> >>>>>> interface Serial0/0/0:15
> >>>>>> no ip address
> >>>>>> encapsulation hdlc
> >>>>>> isdn switch-type primary-net5
> >>>>>> isdn overlap-receiving
> >>>>>> isdn incoming-voice voice
> >>>>>> isdn map address .* plan unknown type unknown
> <-------------
> >>>>>>
> >>>>>> Regards,
> >>>>>> Mike
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: cisco-voip-bounces at puck.nether.net
> >>>>>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
> Jonathan
> >>>>>> Charles
> >>>>>> Sent: Tuesday, 1 December 2009 12:59 p.m.
> >>>>>> To: Mike Lydick
> >>>>>> Cc: cisco-voip
> >>>>>> Subject: Re: [cisco-voip] Wacky telco issues... cannot call
> the UK
> >>>>>>
> >>>>>> Nope, it is an NI2... super duper confirmed...
> >>>>>>
> >>>>>>
> >>>>>> J
> >>>>>>
> >>>>>> On Mon, Nov 30, 2009 at 5:38 PM, Mike Lydick <mike.lydick at gmail.com
> >
> >>>>> wrote:
> >>>>>>> I was thinking the same. Also does the provider require
> Software
> >>>>>>> Select features? Mega-com...
> >>>>>>>
> >>>>>>>
> >>>>>>> Best Regards,
> >>>>>>>
> >>>>>>> Mike Lydick
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Mon, Nov 30, 2009 at 6:30 PM, Scott Voll <svoll.voip at gmail.com
> > wrote:
> >>>>>>>>
> >>>>>>>> Can you leave it international and strip the 011?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Mon, Nov 30, 2009 at 3:16 PM, Jonathan Charles
> >>>>>>>> <jonvoip at gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> OK, here's one that is stumping me...
> >>>>>>>>>
> >>>>>>>>> CUCM 7.0, H.323 Gateways with 3 PRIs.
> >>>>>>>>>
> >>>>>>>>> We can call all over Europe, Oceania, Asia... but not the
> UK.
> >>>>>>>>>
> >>>>>>>>> Calls go out:
> >>>>>>>>>
> >>>>>>>>> ch = primary-ni interface = User
> >>>>>>>>> Nov 30 17:07:21.704 CST: ISDN Se0/1/0:23 Q931: TX -> SETUP
> pd = 8
> >>>>>>>>> callref = 0x147B
> >>>>>>>>> Bearer Capability i = 0x8090A2
> >>>>>>>>> Standard = CCITT
> >>>>>>>>> Transfer Capability = Speech
> >>>>>>>>> Transfer Mode = Circuit
> >>>>>>>>> Transfer Rate = 64 kbit/s
> >>>>>>>>> Channel ID i = 0xA98397
> >>>>>>>>> Exclusive, Channel 23
> >>>>>>>>> Calling Party Number i = 0x2181, '8475552096'
> >>>>>>>>> Plan:ISDN, Type:National
> >>>>>>>>> Called Party Number i = 0x91, '011441787883195'
> >>>>>>>>> Plan:ISDN, Type:International Nov 30
> 17:07:21.744
> >>>>>>>>> CST: ISDN Se0/1/0:23 Q931: RX <- CALL_PROC pd = 8 callref
> = 0x947B
> >>>>>>>>> Channel ID i = 0xA98397
> >>>>>>>>> Exclusive, Channel 23 MC003137# Nov 30
> 17:07:21.744
> >>>>>>>>> CST: ISDN Se0/1/0:23 Q931: RX <- PROGRESS pd = 8 callref =
> 0x947B
> >>>>>>>>> Cause i = 0x829F - Normal, unspecified
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> And fail.
> >>>>>>>>>
> >>>>>>>>> On the Route Pattern, we are forcing plan and type to
> >>>>>>>>> unknown/unknown; telco came in and made these calls
> successfully
> >>>>>>>>> from the smartjacks; I have a dial peer invoking a
> translation profile:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> !
> >>>>>>>>> voice translation-rule 2
> >>>>>>>>> rule 1 // // type international unknown plan isdn unknown !
> >>>>>>>>> !voice translation-profile UK
> >>>>>>>>> translate called 2
> >>>>>>>>> !
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> !
> >>>>>>>>> dial-peer voice 60 pots
> >>>>>>>>> translation-profile outgoing UK
> >>>>>>>>> destination-pattern 01144T
> >>>>>>>>> port 0/0/0:23
> >>>>>>>>> prefix 01144
> >>>>>>>>> !
> >>>>>>>>>
> >>>>>>>>> There are no transformation patterns on the system, there
> are no
> >>>>>>>>> translation patterns on the system; every other
> international call
> >>>>>>>>> succeeds without any issue (plan and type are unknown)...
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Any ideas? I seriously have no idea where this plan and
> type are
> >>>>>>>>> coming from, or how to get rid of them...
> >>>>>>>>> _______________________________________________
> >>>>>>>>> cisco-voip mailing list
> >>>>>>>>> cisco-voip at puck.nether.net
> >>>>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> cisco-voip mailing list
> >>>>>>>> cisco-voip at puck.nether.net
> >>>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> _______________________________________________
> >>>>>> cisco-voip mailing list
> >>>>>> cisco-voip at puck.nether.net
> >>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>> _______________________________________________
> >>>> cisco-voip mailing list
> >>>> cisco-voip at puck.nether.net
> >>>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>>
> >>>
> >>
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091201/0bf8c87b/attachment.html>
More information about the cisco-voip
mailing list