From: Bob Sinclair (bsinclair@netmasterclass.net)
Date: Thu Jun 16 2005 - 15:59:17 GMT-3
Tim,
The isdn calling-number requirement is tied to whether the switch/switch
simulator (not the switch-type, per se)supports caller-ID automatically. Our
adtran requires it. Perhaps someone with more telco experience can elaborate.
For lab purposes I would include it on the initial caller.
HTH,
Bob Sinclair
CCIE #10427, CCSI 30427, CISSP
www.netmasterclass.net
----- Original Message -----
From: ccie2be
To: 'Bob Sinclair' ; 'Chris Lewis (chrlewis)' ; ccielab@groupstudy.com
Sent: Thursday, June 16, 2005 2:30 PM
Subject: RE: isdn caller
HI Bob,
I was wondering about this also.
Do you know if this command, isdn calling-number, is always needed or does
it depend on if spids are configured or the type of switch being used?
Would you recommend always using this command when configuring isdn
callback?
Thanks a lot, Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Bob
Sinclair
Sent: Thursday, June 16, 2005 2:18 PM
To: Chris Lewis (chrlewis); ccielab@groupstudy.com
Subject: Re: isdn caller
Chris,
Here are working configs. The switch is an Adtran. R2 is calling R1
initially. We find it necessary to add the command "isdn calling-number"
on
the side that initially calls.
username R2 password 0 nmc
interface BRI0
ip address 172.16.12.1 255.255.255.0
encapsulation ppp
dialer map ip 172.16.12.2 name R2 broadcast 5552010
dialer map ip 172.16.12.2 name R2 broadcast 5552011
dialer-group 1
isdn switch-type basic-ni
isdn spid1 21255520080101
isdn spid2 21255520090101
isdn caller 5552010 callback <<<<<<<<<<<<<<<<<<<<
ppp authentication chap
R2:
username R2 password 0 nmc
interface BRI0
ip address 172.16.12.2 255.255.255.0
encapsulation ppp
dialer map ip 172.16.12.1 name R1 broadcast 5552008
dialer-group 1
isdn switch-type basic-ni
isdn spid1 21255520100101
isdn spid2 21255520110101
isdn calling-number 5552010 <<<<<<<<<<<<<<<<<<<<<<<<<<<
ppp authentication chap
HTH,
Bob Sinclair
CCIE #10427, CCSI 30427, CISSP
www.netmasterclass.net
----- Original Message -----
From: Chris Lewis (chrlewis)
To: ccielab@groupstudy.com
Sent: Thursday, June 16, 2005 1:21 PM
Subject: isdn caller
Hi,
Anyone with advice on this one, it would be appreciated. I am
comfortable with ppp callback, but have tried isdn caller to accomplish
the same with no success.
In this setup R1 calls R2, R2 drops the call and initiates callback,
this calls reaches R1, but it is rejected for some reason. Configs plus
debugs for R1 and R2 follow:
BTW, I can bring up the link by pinging the other end from either
router, so basic ISDN connectivity worked prior to adding the isdn
caller stuff
R1 (the side making the first call)
Interface BRI0/0
ip address 1.1.21.1 255.255.255.0.
encapsulation ppp
dialer idle-timeout 60
dialer wait-for-carrier-time 20
dialer map ip 1.1.21.2 8358662
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866101 8358661
isdn spid2 0835866301 8358663
ppp authentication chap
R2 (the side doing callback)
Interface BRI0/0
ip address 1.1.21.2 255.255.255.0.
encapsulation ppp
dialer idle-timeout 60
dialer enable-timeout 10
dialer map ip 1.1.21.1 8358661
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866201 8358662
isdn spid2 0835866401 8358664
isdn caller 8358661 callback
ppp authentication chap
This is from R1
R1#ping 1.1.21.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.21.2, timeout is 2 seconds:
1d18h: BR0/0 DDR: Dialing cause ip (s=1.1.21.1, d=1.1.21.2)
1d18h: BR0/0 DDR: Attempting to dial 8358662
1d18h: ISDN BR0/0: Outgoing call id = 0x800F, dsl 0
1d18h: ISDN BR0/0: Event: Call to 8358662 at 64 Kb/s
1d18h: ISDN BR0/0: process_bri_call(): call id 0x800F, called_number
8358662, sp
eed 64, call type DATA
1d18h: CCBRI_Go Fr Host InPkgInfo (Len=22) :
1d18h: 1 0 1 80 F 0 4 2 88 90 18 1 83 2C 7 38 33 35 38 36 36 32
1d18h:
1d18h: CC_CHAN_GetIdleChanbri: dsl 0
1d18h: Found idle channel B1
1d18h: CCBRI_Go Fr L3 pkt (Len=7) :
1d18h: 2 1 F 98 18 1 89
1d18h:
1d18h: ISDN BR0/0: LIF_EVENT: ces/callid 1/0x800F HOST_PROCEEDING.....
Success rate is 0 percent (0/5)
R1#
1d18h: CCBRI_Go Fr L3 pkt (Len=21) :
1d18h: 5 1 96 90 4 2 88 90 18 1 89 6C 8 80 38 33 35 38 36 36 32
1d18h:
1d18h: ISDN BR0/0: Incoming call id = 0x001B, dsl 0
R1#
1d18h: BRI0/0: wait for isdn carrier timeout, call id=0x800F
1d18h: ISDN BR0/0: Event: Hangup call to call id 0x800F ces = 1
1d18h: ISDN BR0/0: process_disconnect(): call id 0x800F, call type is
DATA, b_id
b 0x824A2114, ces 1, cause Normal call clearing(0x10)
1d18h: ISDN: get_isdn_service_state(): idb 0x824A2114 bchan 2 is_isdn 1
Not a Pr
i
1d18h: CCBRI_Go Fr Host InPkgInfo (Len=13) :
1d18h: 5 0 1 80 F 3 8 1 90 8 2 80 90
1d18h:
1d18h: CCBRI_Go Fr L3 pkt (Len=4) :
1d18h: 4D 1 F 97
1d18h:
1d18h: ISDN BR0/0: LIF_EVENT: ces/callid 1/0x800F HOST_DISCONNECT_ACK
1d18h: ISDN: get_isdn_service_state(): idb 0x824A2114 bchan 2 is_isdn 1
Not a Pr
i
R1#
1d18h: ISDN BR0/0: HOST_DISCONNECT_ACK: call type is DATA
R1#
This is from R2
R2#
1d18h: DDR: Callback timer expired
1d18h: BR0/0 DDR: beginning callback to 8358661
1d18h: BR0/0 DDR: Attempting to dial 8358661
R2#
1d18h: BRI0/0: wait for isdn carrier timeout, call id=0x8016
1d18h: DDR: Freeing callback to 8358661
R2#
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:41 GMT-3