From: FATHALLAH (sfathallah@mail.cbi.net.ma)
Date: Tue May 06 2003 - 12:41:20 GMT-3
as already requested, please remove the callback config and first test if
your isdn switch deliver the "caller ID" as follow :
at r5
Interface bri0
isdn callerid 6666666
from r3 try to ping r5 and try to issue a debug dialer at R5. if the ping
fail and debug get a callerid screning , that mean your switch deliver the
callerid.
let me know.
Said FATHALLAH.
-----Message d'origine-----
De : Peng Zheng [mailto:zpnist@yahoo.com]
Envoyi : mardi 6 mai 2003 15:14
@ : FATHALLAH
Objet : RE: ISDN callback
Sorry, I made a mistake. Because someone told me to
add ppp callback request .... I thought my config is
wrong without ppp callback request and ppp callback
accept.
So you mean it's possible. I already tried:
My config: r3:
--------------------------------
interface BRI0
ip address 135.35.35.3 255.255.255.240
encapsulation ppp
no ip route-cache
no ip mroute-cache
dialer wait-for-carrier-time 4
dialer map ip 135.35.35.5 name r5 broadcast
4082222222
dialer-group 1
isdn switch-type basic-ni
isdn spid1 40811111111 4081111111
isdn spid2 40811111112 4081111111
ppp authentication chap
On r5:
--------------------------------------
interface BRI1
ip address 135.35.35.5 255.255.255.240
encapsulation ppp
dialer fast-idle 5
dialer enable-timeout 2
dialer map ip 135.35.35.3 name r3 broadcast
4081111111
dialer-group 1
isdn switch-type basic-ni
isdn spid1 40822222221 4082222222
isdn spid2 40822222222 4082222222
isdn caller 4081111111 callback
isdn caller 408xxxxxxx callback
ppp authentication chap
------------------------------------------
I tried ping from r3 to r5, below is output of "debug
dialer".
r3#ping 135.35.35.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 135.35.35.5, timeout
is 2 seconds:
00:18:23: BR0 DDR: Dialing cause ip (s=135.35.35.3,
d=135.35.35.5)
00:18:23: BR0 DDR: Attempting to dial 4082222222..
00:18:27: BRI0: wait for isdn carrier timeout, call
id=0x8007.
00:18:29: BR0 DDR: Dialing cause ip (s=135.35.35.3,
d=135.35.35.5)
00:18:29: BR0 DDR: Attempting to dial 4082222222
00:18:29: BRI0: wait for isdn carrier timeout, call
id=0x8008.
00:18:31: BR0 DDR: Dialing cause ip (s=135.35.35.3,
d=135.35.35.5)
00:18:31: BR0 DDR: Attempting to dial 4082222222
00:18:31: BRI0: wait for isdn carrier timeout, call
id=0x8009.
Success rate is 0 percent (0/5)
I don't know what's wrong and I don't know what's the
reason.
Any idea?
--- FATHALLAH <sfathallah@mail.cbi.net.ma> wrote:
> witch map-class you are talking about? according to
> your config you
> configure the isdn caller callback and not ppp
> callback, so the map-class is
> not required and can be an opposit of the lab
> requirement ( you know in
> ccie, the choice of the implementation method is
> very important ) . also i
> didnt tell you that "isdn caller id" is required,
> it's just a mean to test
> that your switch deliver the "caller id" number
> witch is the requirement of
> "isdn caller callback" configuration to work
> proprely.
>
> Said FATHALLAH.
>
> -----Message d'origine-----
> De : Peng Zheng [mailto:zpnist@yahoo.com]
> Envoyi : lundi 5 mai 2003 21:09
> @ : sfathallah@mail.cbi.net.ma
> Objet : RE: ISDN callback
>
>
> As John said, map-class name is not matching. After
> I
> changed it, it is ok.
> In my lab, "isdn caller id" is not required.
>
>
> --- FATHALLAH <sfathallah@mail.cbi.net.ma> wrote:
> > hi peng.
> > your config is right. but the callerId callback
> > methode need your isdn
> > switch to deliver the callerId. make sure that it
> > get it. you can test this
> > by securing caller ID " isdn caller id "
> >
> > let me know.
> >
> > Said FATHALLAH
> >
> > -----Message d'origine-----
> > De : nobody@groupstudy.com
> > [mailto:nobody@groupstudy.com]De la part de
> > Peng Zheng
> > Envoyi : mardi 29 avril 2003 22:17
> > ?: ccielab@groupstudy.com
> > Objet : ISDN callback
> >
> >
> > Hi,
> > I tried to config callback according:
> >
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/dial_
> > c/dccallid.htm
> >
> > I have r3 and r5, on r3 I use int bri 0, on r5, I
> > use
> > int bri 1.
> >
> > Before callback, on r3
> > ---------------
> >
> >
> > interface BRI0
> > ip address 135.35.35.3 255.255.255.240
> > encapsulation ppp
> > no ip route-cache
> > no ip mroute-cache
> > dialer map ip 135.35.35.5 name r5 broadcast
> > 4082222222
> > dialer-group 1
> > isdn switch-type basic-ni
> > isdn spid1 40811111111 4081111111
> > isdn spid2 40811111112 4081111111
> > ppp authentication chap
> > dialer-list 1 protocol ip permit
> >
> >
> > on r5:
> >
> > interface BRI1
> > ip address 135.35.35.5 255.255.255.240
> > encapsulation ppp
> > dialer map ip 135.35.35.3 name r3 broadcast
> > 4081111111
> > dialer-group 1
> > isdn switch-type basic-ni
> > isdn spid1 40822222221 4082222222
> > isdn spid2 40822222222 4082222222
> > ppp authentication chap
> >
> > dialer-list 1 protocol ip permit
> >
> > -------------------------------------------
> >
> > It works well. Then I added:
> >
> > dialer enable-timeout 2
> > isdn caller 4082222222 callback
> >
> > on r3, and
> >
> > dialer wait-for-carrier-time 4
> > on r5.
> >
> > Then I tried to ping r3 int bri 0 from r5, but int
> > bri
> > on both them weren't brought up. when I use: sh
> > dialer,
> >
> > It's said a callback failure.
> >
> > Does anyone know what's the problem or any
> > suggestion?
> >
> > Thanks.
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> >
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:38 GMT-3