From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Wed Jun 01 2005 - 14:30:24 GMT-3
Tim,
As an FYI the dialer-remote name isn't needed for ISDN callback.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Wednesday, June 01, 2005 10:28 AM
To: Brian Dennis; 'Andy'; ccielab@groupstudy.com
Subject: RE: Re Re: ISDN callback/dialer load-threshold.
Brian,
I thought Andy was trying to configure isdn callback, not ppp callback.
Tim
-----Original Message-----
From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
Sent: Wednesday, June 01, 2005 1:24 PM
To: ccie2be; Andy; ccielab@groupstudy.com
Subject: RE: Re Re: ISDN callback/dialer load-threshold.
That isn't going to help as he doesn't even have a PPP callback
configured correctly. He is trying to do callback via dialer callback
and PPP callback at the same time.
Here are the steps for him to fix his problem:
1) Remove all callback related configuration.
R6 - no ppp callback request
R8 - no dialer caller 666111 callback
R8 - no ppp callback accept
2) Test the basic configuration by having R6 call R8.
3) Disconnect the call (isdn test disconnect interface bri0 all).
4) Test the basic configuration by having R8 call R6.
5) Disconnect the call.
6) Add PPP authentication since authentication is need for PPP username
based callback.
R6:
username R8 password CISCO
!
interface BRI0
ppp authentication chap
R6:
username R6 password CISCO
!
interface Dialer1
ppp authentication chap
Note: I'm assuming that your hostnames are R6 and R8
7) Test the authentication by having one of the routers call the other.
8) Disconnect the call.
9) Now apply the PPP callback configuration:
R6:
interface BRI0
ppp callback request
R8:
interface Dialer1
ppp callback accept
dialer string 666111 class CALLBACK
dialer remote-name R6
!
map-class dialer CALLBACK
dialer callback-server username
10) Finally test callback by having R6 call R8.
11) If this doesn't work, start back at step 1 ;-)
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Wednesday, June 01, 2005 9:46 AM
To: 'Andy'; 'john matijevic'; 'mani poopal'; 'Chuck South';
ccielab@groupstudy.com
Subject: RE: Re Re: ISDN callback/dialer load-threshold.
Andy,
I'm not sure what the problem is although I noticed that in the example
on
the Doc-cd, they use the dialer remote-name command and you didn't.
Have a look at this:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
fdia
l_c/fnsprt10/dafcalid.htm#wp1001156
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Andy
Sent: Wednesday, June 01, 2005 12:23 PM
To: ccie2be; 'john matijevic'; 'mani poopal'; 'Chuck South';
ccielab@groupstudy.com
Subject: Re: Re Re: ISDN callback/dialer load-threshold.
Hi Tim,
This is my config, please help me out, this is so confusing.
On R6:
interface BRI0
ip address 10.0.0.6 255.255.255.0
encapsulation ppp
dialer string 888111
dialer-group 1
isdn switch-type basic-ni
isdn spid1 66612345
isdn spid2 66654321
cdapi buffers regular 0
cdapi buffers raw 0
cdapi buffers large 0
ppp callback request
ppp multilink
!
dialer-list 1 protocol ip permit
And this is from R8:
!
interface BRI0
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-ni
isdn spid1 88812345
isdn spid2 88854321
!
interface Dialer1
ip address 10.0.0.8 255.255.255.0
encapsulation ppp
dialer pool 1
dialer string 666111
dialer caller 666111 callback
dialer-group 1
ppp callback accept
!
dialer-list 1 protocol ip permit
======================
Here, the debug dialer when i do pinging R8
From R6:
R6#p 10.0.0.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.8, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R6#
02:55:10: BR0 DDR: Dialing cause ip (s=10.0.0.6, d=10.0.0.8)
02:55:10: BR0 DDR: Attempting to dial 888111
R6#
02:55:40: BRI0: wait for isdn carrier timeout, call id=0x8003
R6#
And from R8:
R8#
02:53:54: BR0:1 DDR: Caller id 666111 matched to profile
02:53:54: Di1 DDR: Caller id: Callback server starting to 666111
R8#
02:54:09: DDR: Callback timer expired
02:54:09: Di1 DDR: beginning callback to 666111
02:54:09: BR0 DDR: rotor dialout [best] least recent failure is also
most
recent failure
02:54:09: BR0 DDR: rotor dialout [best] trying untried dialout
02:54:09: BR0 DDR: rotor dialout [best] also has most recent failure
02:54:09: BR0 DDR: rotor dialout [best]
02:54:09: BR0 DDR: Dialing cause Callback return call
02:54:09: BR0 DDR: Attempting to dial 666111
R8#
02:54:39: BRI0: wait for isdn carrier timeout, call id=0x8002
02:54:39: DDR: Freeing callback to 666111
Router8 seems calling back R6 but it actual does not.
R8#sh dialer
BRI0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
0 incoming call(s) have been screened.
1 incoming call(s) rejected for callback.
BRI0:1 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle
BRI0:2 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle
Di1 - dialer type = DIALER PROFILE
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle
Number of active calls = 0
TIA.
Andy.
----- Original Message -----
From: "ccie2be" <ccie2be@nyc.rr.com>
To: "'Andy'" <trung@vnsystem.net>; "'john matijevic'"
<matijevi@bellsouth.net>; "'mani poopal'" <mani_ccie@yahoo.com>; "'Chuck
South'" <cciesouth@bellsouth.net>; <ccielab@groupstudy.com>
Sent: Wednesday, June 01, 2005 2:39 AM
Subject: RE: Re Re: ISDN callback/dialer load-threshold.
> Andy,
>
> These are my notes on this:
>
> -There are 2 types of callbacks: ISDN callback & PPP callback. They
are
> both well documented in the IOS Dial Technology CG in a separate
chapter
> on
> Callback.
> -ISDN callback is done based on the phone # of device initiating call.
> Use
> isdn caller <#> callback. If the caller ID matches the # in command,
rtr
> will make a callback to that #. If callback must be based on username,
> then
> ppp callback must be used.
>
> If you don't get this work, would you post your config's (both sides),
> along
> with debug dialer output.
>
> HTH, Tim
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Andy
> Sent: Monday, May 30, 2005 1:25 PM
> To: 'john matijevic'; 'mani poopal'; 'ccie2be'; 'Chuck South';
> ccielab@groupstudy.com
> Subject: Re Re: ISDN callback/dialer load-threshold.
>
> Hi John,
> i've tried to configure dialer profile for callback on server side,
not
> with
>
> ppp cmd but "dialer caller xxx callback" instead. Unfortunately it did
not
> work.
> The debug dialer said the client side attempt to call, the server side
> disconnect and starting to callback but... that's all. The isdn bri
did
> not
> come up.
> So what's the problem here ?
>
> TIA,
>
> Andy.
>
> ----- Original Message -----
> From: "john matijevic" <matijevi@bellsouth.net>
> To: "'john matijevic'" <matijevi@bellsouth.net>; "'mani poopal'"
> <mani_ccie@yahoo.com>; "'ccie2be'" <ccie2be@nyc.rr.com>; "'Chuck
South'"
> <cciesouth@bellsouth.net>; <ccielab@groupstudy.com>
> Sent: Saturday, July 31, 2004 11:02 PM
> Subject: RE: Re: ISDN callback/dialer load-threshold.
>
>
>> 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 : Wed Jul 06 2005 - 14:43:40 GMT-3