[cisco-voip] Wacky telco issues... cannot call the UK

[Jonathan Charles]

You mean this:

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


Jonathan


On Mon, Nov 30, 2009 at 7:15 PM, Kevin Thorngren <kthorngr at cisco.com> wrote:
> That's the magic of IOS.  Somewhere in 12.3, I believe, automatic
> configuration of the plan and type was added.  The automatic config is based
> on the rules of ISDN switch type selected.  I have seen the automatic change
> applied using "debug isdn q931" but it is not in your output.  It would have
> shown just before the ISDN setup.
> As you found you can change this using the isdn map address command.  You
> can also change it with translation profiles, like you tried.  I suspect
> that maybe your translation rule didn't match.  Maybe this rule would have
> worked:
> rule 1 // // type any unknown plan any unknown
> Kevin
> On Nov 30, 2009, at 7:30 PM, Jonathan Charles wrote:
>
> 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
>
>