Re: [nsp] How to bind BRI to dialer interface properly

From: kouji.baba@equant.com
Date: Mon Dec 10 2001 - 20:21:14 EST

Next message: Benjie Ko: "[nsp] Tunneling options"
Previous message: Majdi S. Abbas: "Re: [nsp] OSPF update"
Maybe in reply to: kouji.baba@equant.com: "[nsp] How to bind BRI to dialer interface properly"
Next in thread: Cheung, Rick: "RE: [nsp] How to bind BRI to dialer interface properly"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

Rick,

Thanks for your suggestion.

I put "ppp authentication chap" on BRI, and incoming call is accepted
properly.

Thanks and best regards,
-----
Kouji Baba

                    Rick Burts
                    <rburts@netcraf To: kouji.baba@equant.com
                    tsmen.net> cc: cisco-nsp@puck.nether.net
                                           Subject: Re: [nsp] How to bind BRI to dialer interface properly
                    2001/12/07
                    12:59

I would suggest that you include ppp auth chap on the BRI as well as the
dialer interfaces. This will enable the router to authenticate incoming
calls.

The output of debug ppp auth would be more helpful than the deb isdn
event.

Rick

kouji.baba@equant.com wrote:
>
> Hello,
>
> I am implementing ISDN dialup connection from two site to one hub site.
> Incoming call from first site(aaaaa) is correctly bound to dialer0,
> but incoming call from second site(bbbbb) is rejected.
> Following is debug output by "debug isdn event"
>
> Dec 6 02:39:39: ISDN BR0:1: Incoming call rejected, unbindable
>
> Here is configuration of hub site.
> version 12.1
> !
> hostname ccccc
> !
> username aaaaa password 0 aaaaa
> username bbbbb password 0 bbbbb
> !
> isdn switch-type ntt
> !
> interface Ethernet0
> ip address 192.168.7.252 255.255.255.0
> !
> interface BRI0
> no ip address
> encapsulation ppp
> dialer pool-member 1 max-link 1
> isdn switch-type ntt
> !
> interface Dialer0
> ip address 192.168.201.3 255.255.255.248
> encapsulation ppp
> dialer pool 1
> dialer remote-name aaaaa
> dialer idle-timeout 30
> dialer string 1234567899
> dialer-group 1
> ppp authentication chap
> !
> interface Dialer1
> ip address 192.168.202.1 255.255.255.0
> encapsulation ppp
> dialer pool 1
> dialer remote-name bbbbb
> dialer idle-timeout 30
> dialer string 1234567800
> dialer-group 1
> ppp authentication chap
> !
> dialer-list 1 protocol ip permit
> !
>
> When I use "dialer caller xxxx" in dialer1 configuration,
> call from site(bbbbb) is bound to dialer1 correctly.
> But the site will be overseas in future, so caller-ID is not usable.
>
> Is there any way to bind BRI to dialer1 properly?
>
> Regards,
> -----
> Kouji Baba

-- Rick Burts CCIE 4615 CCSI Email: rburts@netcraftsmen.net Chesapeake NetCraftsmen O:410.757.3050, 1290 Bay Dale Drive, #312 C:443.994.0675 Arnold, MD 21012-2325 WWW: http://www.netcraftsmen.net

With 6 CCIEs on staff Chesapeake NetCraftsmen offers services in network consulting and training. Our services include Network Design, Implementation, Troubleshooting as well as Network Management.

Next message: Benjie Ko: "[nsp] Tunneling options"
Previous message: Majdi S. Abbas: "Re: [nsp] OSPF update"
Maybe in reply to: kouji.baba@equant.com: "[nsp] How to bind BRI to dialer interface properly"
Next in thread: Cheung, Rick: "RE: [nsp] How to bind BRI to dialer interface properly"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:57 EDT