From: Sean C. (Upp_and_Upp@xxxxxxxxxxx)
Date: Sun Mar 24 2002 - 06:07:08 GMT-3
That's good that the configs worked the 2nd time around. Your configs
looked fine the first time. Your concern is merited, I have the same. I
never doubted your multilink, I just knew that multilink in my lab had a
history of acting quirky. Also, I noticed your routers have 12.2
installed, I think the lab uses 12.1.
Don't you just luv ISDN? Happy routing,
Sean
----- Original Message -----
From: "Lab Candidate" <labccie@yahoo.com>
To: "Sean C." <Upp_and_Upp@hotmail.com>; "Nick Shah" <nshah@connect.com.au>;
"Ahmed Mamoor Amimi" <mamoor@ieee.org>; <ccielab@groupstudy.com>
Sent: Saturday, March 23, 2002 9:08 PM
Subject: Re: ISDN callback scenario - solved
I logged on the rack today and redid everything, it just worked like a
charm.
I still don't know what went wrong yesterday. Sean, I don't think the ppp
multilink matters in my case. to prove it, I configured it with and without,
and also configured one-sided, it all worked. This kind of situation and
problem
is what I'm afraid most when it comes to lab date, which is this coming
Thursday.
To all that are interested in solution, I pasted the final working config
below:
==================== r2 =======================
2#sh conf
Using 1721 out of 29688 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname r2
!
boot system flash:c2600-jk9o3s-mz.122-7a.bin
!
username r3 password 0 cisco
ip subnet-zero
!
interface BRI0/0
ip address 40.40.40.2 255.255.255.0
encapsulation ppp
dialer idle-timeout 60
dialer map ip 40.40.40.3 name r3 broadcast 3589
dialer-group 1
isdn switch-type basic-ni
isdn spid1 2588
isdn spid2 3588
no cdp enable
ppp callback request
ppp authentication chap
ppp multilink
!
ip classless
ip http server
ip pim bidir-enable
!
dialer-list 1 protocol ip permit
!
bridge 1 protocol ieee
!
dial-peer cor custom
!
line con 0
line aux 0
line vty 0 4
login
!
end
r2#
==================== r3 =======================
Using 2109 out of 29688 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname r3
!
!
username r2 password 0 cisco
ip subnet-zero
!
isdn switch-type basic-ni
call rsvp-sync
!
interface BRI0/0
ip address 40.40.40.3 255.255.255.0
encapsulation ppp
dialer callback-secure
dialer map ip 40.40.40.2 name r2 class dc1 broadcast 2588
dialer load-threshold 1 outbound
dialer-group 1
isdn switch-type basic-ni
isdn spid1 3589
isdn spid2 2589
no cdp enable
ppp callback accept
ppp authentication chap
!
ip classless
ip http server
ip pim bidir-enable
!
!
map-class dialer dc1
dialer callback-server username
access-list 101 permit ip host 172.16.2.2 host 172.16.2.1
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
!
line con 0
line aux 0
line vty 0 4
!
end
r3#
--- "Sean C." <Upp_and_Upp@hotmail.com> wrote:
> Hello,
>
> Well, I just took my stab at the callback scenario and it worked fine
using
> the configs from Lab candidate (do you need to be that anonymous?). I
also
> added the commands 'dialer enable-timeout 5' on the callback router and
> 'dialer wait-for-carrier 10' but the callback worked whether these were
> configured or not.
>
> The only thing I can't guarantee is my multilink. I have it enabled on
both
> sides butttt sometimes the multilink works, sometimes multilink doesn't
> work. I have a feeling it's more my simulator or the code than anything.
> The calls still go through, just sometimes the 2nd channel doesn't get
> brought up.
>
> IOS r5 - Version 12.1(8)
> IOS r6 - Version 12.1(12)
> !
> hostname r5
> !
> username r6 password 0 cisco
> !
> interface BRI0
> description Callback router
> ip address 40.40.40.2 255.255.255.0
> encapsulation ppp
> dialer callback-secure
> dialer enable-timeout 5
> dialer map ip 40.40.40.1 name r6 class test broadcast 2221
> dialer map ip 40.40.40.1 name r6 class test broadcast 2222
> dialer load-threshold 3 either
> dialer-group 1
> isdn switch-type basic-net3
> isdn spid1 1111
> isdn spid2 1112
> ppp callback accept
> ppp authentication chap
> ppp multilink
> !
> map-class dialer test
> dialer callback-server username
> !
> dialer-list 1 protocol ip permit
> !
> =============================
> hostname r6
> !
> username r5 password 0 cisco
> !
> interface BRI0
> description Calling router
> ip address 40.40.40.1 255.255.255.0
> encapsulation ppp
> dialer wait-for-carrier-time 10
> dialer map ip 40.40.40.2 name r5 broadcast 1111
> dialer map ip 40.40.40.2 name r5 broadcast 1112
> dialer load-threshold 3 either
> dialer-group 1
> isdn switch-type basic-net3
> isdn spid1 2221
> isdn spid2 2222
> no peer neighbor-route
> ppp callback request
> ppp authentication chap
> ppp multilink
> !
> dialer-list 1 protocol ip permit
> !
>
>
> r6#p
> Target IP address: 40.40.40.2
> Repeat count [5]: 15
> Datagram size [100]: 1500
> Type escape sequence to abort.
> Sending 15, 1500-byte ICMP Echos to 40.40.40.2, timeout is 2 seconds:
> 00:44:01: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
> 00:44:01: %LINK-3-UPDOWN: Interface BRI0:2, changed state to down..
> 00:44:07: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
> 00:44:07: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to
up.!!!
> 00:44:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:2, changed
> state to up
> 00:44:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1,
> changed state to up!!!!!!!!
> Success rate is 73 percent (11/15), round-trip min/avg/max = 384/388/396
ms
> 00:44:13: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to 1111 r5
>
> The initial up/down/up on the r6's output is the calling going to r5,
> accepted by r5, r5 disconnecting per callback feature, and the r5
> successfully calling r6 back.
>
> HTH,
> Sean
>
>
> ----- Original Message -----
> From: "Nick Shah" <nshah@connect.com.au>
> To: "Lab Candidate" <labccie@yahoo.com>; "Ahmed Mamoor Amimi"
> <mamoor@ieee.org>; <ccielab@groupstudy.com>
> Sent: Saturday, March 23, 2002 2:10 PM
> Subject: Re: ISDN callback scenario
>
>
> hmm...on one router you have got ppp multilink configured on the client
> side, and not on the server, This *may* cause dialer callback-secure to
> reject the call as improperly configured. try removing ppp multilink.
>
> If that still doesnt resolve the issue, I would do a debug on ppp nego. &
> authentication and see that r2/r3 is getting authenticated and negotiating
> call back parameters...
>
> hth
> Nick
>
> -----Original Message-----
> From: Lab Candidate <labccie@yahoo.com>
> To: Ahmed Mamoor Amimi <mamoor@ieee.org>; ccielab@groupstudy.com
> <ccielab@groupstudy.com>
> Date: Saturday, 23 March 2002 8:47
> Subject: Re: ISDN callback scenario
>
>
> >I took out dialer callback secure and it still desn't work giving the
same
> error message "callback
> >is not configured for user r2". But it works perfectly when I changed it
to
> caller ID callback.
> >Any ider what's going on here?
> >
> >
> >--- Ahmed Mamoor Amimi <mamoor@ieee.org> wrote:
> >> first try this with the minimum config.
> >> remove the call-back secure then try.
> >>
> >> i was wondering if call-back works with multilink.. !! let me know ..
> >>
> >> -Mamoor
> >>
> >>
> >> ----- Original Message -----
> >> From: Lab Candidate <labccie@yahoo.com>
> >> To: <ccielab@groupstudy.com>
> >> Sent: Saturday, March 23, 2002 12:59 PM
> >> Subject: ISDN callback scenario
> >>
> >>
> >> > r2 and r3 are setup with basic ISDN callback as below.
> >> > r2 callback client, r3 callback server.
> >> > everything is configured as CCO example, but when r2 calls r3
> >> > when r2 pings r3, r2 calls and disconnects, and waiting for r3.
> >> > but r3 never calls back.
> >> > r3 debug says "callback is not configured for user r2"
> >> > debug output and r2/r3 configs attached below.
> >> > what's the problem here please?
> >> >
> >> > r3#
> >> > 2d05h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up
> >> > 2d05h: BR0/0:1 DDR: No callback configured for user r2.
> >> > 2d05h: BR0/0:1 DDR: disconnecting call
> >> > 2d05h: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 2588
r2
> >> > 2d05h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down
> >> > 2d05h: BR0/0:1 DDR: disconnecting call
> >> >
> >> > ===============r2==================
> >> > version 12.2
> >> > service timestamps debug uptime
> >> > service timestamps log uptime
> >> > no service password-encryption
> >> > !
> >> > hostname r2
> >> > !
> >> > no logging buffered
> >> > !
> >> > username r3 password 0 cisco
> >> > ip subnet-zero
> >> > !
> >> > !
> >> > interface BRI0/0
> >> > ip address 40.40.40.1 255.255.255.0
> >> > encapsulation ppp
> >> > dialer map snapshot 1 name r3 broadcast 2589
> >> > dialer map ip 40.40.40.2 name r3 broadcast 2589
> >> > dialer load-threshold 50 either
> >> > dialer-group 1
> >> > isdn switch-type basic-ni
> >> > isdn spid1 2588 2588
> >> > isdn spid2 3588 3588
> >> > no cdp enable
> >> > ppp callback request
> >> > ppp authentication chap
> >> > ppp multilink
> >> > !
> >> > dialer-list 1 protocol ip permit
> >> > !
> >> > !
> >> > line con 0
> >> > exec-timeout 0 0
> >> > line aux 0
> >> > line vty 0 4
> >> > password tts
> >> > no login
> >> > !
> >> > end
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:20 GMT-3