From: john matijevic (matijevi@bellsouth.net)
Date: Sat Jul 31 2004 - 13:02:25 GMT-3
Hello again Mani,
I have the output, I configured dialer profile on the client:
r1#deb dialer
Dial on demand events debugging is on
r1#ping 172.16.12.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.12.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
r1#
01:40:43: BR0 DDR: rotor dialout [priority]
01:40:43: BR0 DDR: Dialing cause ip (s=172.16.12.1, d=172.16.12.2)
01:40:43: BR0 DDR: Attempting to dial 5552002
01:40:43: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
01:40:43: BR0:1: interface must be fifo queue, force fifo
01:40:43: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
01:40:43: BR0:1 DDR: Callback negotiated - waiting for server disconnect
01:40:43: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
01:40:43: DDR: Callback client for r2 5552002 created
01:40:43: BR0 DDR: has total 0 call(s), dial_out 0, dial_in 0
01:40:43: BR0:1 DDR: disconnecting call
01:40:43: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di0
r1#
01:40:58: BR0:1: interface must be fifo queue, force fifo
01:40:58: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
01:40:58: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
r1#
01:40:59: BR0:1 DDR: dialer protocol up
01:40:59: BR0:1 DDR: Callback received from r2 5552002
01:40:59: DDR: Freeing callback to r2 5552002
r1#
01:41:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1,
changed sta
to up
r1#sh run int d0
Building configuration...
Current configuration : 206 bytes
!
interface Dialer0
ip address 172.16.12.1 255.255.255.0
encapsulation ppp
dialer pool 1
dialer remote-name r2
dialer string 5552002
dialer-group 1
ppp callback request
ppp authentication chap
end
r1#sh run int bri0
Building configuration...
Current configuration : 201 bytes
!
interface BRI0
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-5ess
cdapi buffers regular 0
cdapi buffers raw 0
cdapi buffers large 0
ppp authentication chap
end
r1#
I can also configure it with server if you would like to see.
I hope that helps you.
Here is a link to dialer profiles on DocCD:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
fdial_c/fnsprt5/dcdiprof.htm#1001553
Sincerely,
John Matijevic, CCIE #13254, MCSE, CNE, CCEA
Network Consultant
Hablo Espanol
305-321-6232
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
john matijevic
Sent: Saturday, July 31, 2004 11:32 AM
To: 'mani poopal'; 'ccie2be'; 'Chuck South'; ccielab@groupstudy.com
Subject: RE: Re: ISDN callback/dialer load-threshold.
Hello Mani,
I am pretty sure this can be used via Dialer profiles as well. I am in
the process of testing it, again and will post my configuration when
finished. As far as the two dialer map statements, I only had one dialer
map statement, I also had a switch that I configure that uses one bri
number for both channels.
Sincerely,
John Matijevic, CCIE #13254, MCSE, CNE, CCEA
Network Consultant
Hablo Espanol
305-321-6232
-----Original Message-----
From: mani poopal [mailto:mani_ccie@yahoo.com]
Sent: Saturday, July 31, 2004 11:05 AM
To: ccie2be; john matijevic; 'Chuck South'; ccielab@groupstudy.com
Subject: Re: Re: ISDN callback/dialer load-threshold.
Hi John,
Excellent reply. John now my next question, what is the equivalent
command for call back in non legacy DDR,ie Dialer profiles(is it ppp
callback accept on server/ppp callback request on client or some other
commands). If members have config examples it is appreciated. In the
Chucks ISDN example I saw only one dialer map ip statement, I think it
shold be two statements with both dial strings(for both bri channels of
destination, if not dialer will not bring the second channel)
thanks
Mani
B.ENG,A+,CCNA,CCNP,CCNP-VOICE, CSS1,CNA,MCSE
(416)431 9929
MANI_CCIE@YAHOO.COM
_____
Do you Yahoo!?
Yahoo!
<http://us.rd.yahoo.com/mail_us/taglines/50x/*http:/promotions.yahoo.com
/new_mail/static/efficiency.html> Mail - 50x more storage than other
providers!
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:12:08 GMT-3