RE: ISDN Basic-Net 3

From: Dave Bregman (DBregman@Houstons.com)
Date: Fri May 20 2005 - 15:22:56 GMT-3

Usually this problem can be fixed using the 'name' parameter on the
dialer maps. It tells the called router that it already has a
connection to the calling router and it won't try to use the second B
channel to call back to return the ping. Of course, I'm just quoting
Scott's Student Handbook. :-)

Dave Bregman
CCIE #14626

> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> Behalf Of Scott Morris
> Sent: Friday, May 20, 2005 10:59 AM
> To: 'Hinet--???'; 'SIMON HART'; ccielab@groupstudy.com
> Subject: RE: ISDN Basic-Net 3
>
>
> The two B channel problem is not related specifically to
> HDLC! So that
> won't make a different per se! I can do unidirectional over HDLC
> encapsulation provided my phone number gets mapped correctly....
>
> Scott
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> Behalf Of
> Hinet--???
> Sent: Friday, May 20, 2005 12:34 PM
> To: 'SIMON HART'; ccielab@groupstudy.com
> Subject: Re: ISDN Basic-Net 3
>
> I guess you must forget the line "encapsulation ppp"
> if you forgot you will have "hdlc" encapsulation with your
> bri interface ,
> and it will cause the two routers maintain 2 separate B channel .
> as Scott mentioned ~~~
>
>
>
> ----- Original Message -----
> From: "Scott Morris" <swm@emanon.com>
> To: "'SIMON HART'" <simon.hart@btinternet.com>;
> <ccielab@groupstudy.com>
> Sent: 2005e945f20f% d8
> e
>  08:58
> Subject: RE: ISDN Basic-Net 3
>
>
> > It depends on what the other side configuration is.... But
> I'd be willing
> > to bet you are ending up with two UNIdirectional links. Do
> a 'debug isdn
> > q931' and 'debug ip packet' on the other side. You will
> likely see the
> > first line go up, the first packet come in, and as it tries
> to send out
> the
> > reply packet it will place another phone call (not
> realizing it's already
> > connected).
> >
> > This has nothing to do with the isdn switch-type per se.
> It has to do
> with
> > incoming call information (show dialer as an example) and
> whether the
> router
> > believes it's already connected or it has to dial out to
> send the reply
> (per
> > the dialer map). It's simply a L3 to L2 mapping correlation issue.
> >
> > HTH,
> >
> > Scott
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]
> On Behalf Of
> > SIMON HART
> > Sent: Friday, May 20, 2005 6:38 AM
> > To: ccielab@groupstudy.com
> > Subject: ISDN Basic-Net 3
> >
> > This may seem like a fairly trivial question, but I have
> not seen this
> > before, any help?
> >
> > I have configured a Legacy DDR using Basic Net-3 on an ISDN BRI0
> >
> > int bri0
> > isdn switch-type basic-net3
> > ip address 172.1.1.2 255.255.255.0
> > dialer map ip 172.1.1.1 name Rack1R3 720451 dialer-group 1
> >
> > dialer-list 1 permit protocol ip
> >
> > Whenever I initiate a call from this interface both ISDN B
> channels come
> up.
> > There are no dialer load threshold statements etc. I can
> see both lines
> > coming up on the local and remote routers. I have
> connectivity with both
> > ends (so I am not dialing back on myself).
> >
> > Why is this the case? How do I stop it? I am sure that
> this is not normal
> > behaviour
> >
> > Thanks
> >
> > Simon
> >
> >
> ______________________________________________________________
> _________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> ______________________________________________________________
> _________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________
> _________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________
> _________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:59 GMT-3