Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Call rejected, unbindable 1

Status
Not open for further replies.

dutronc66

Technical User
Jan 3, 2005
10
ES
I´m implementing ISDN dialup connection from several 803 cisco remote routers to a 2600 central Route on the same Bri interface.

I have no problem when the central one calls but the remote routers can´t. In the central route q931 debug i have the next lines:

ISDN BR1/0: RX <- SETUP pd = 8 callref = 0x10
Channel ID i = 0x89
Display i = 'aaaaa', 0x20, 'PROMETEO', 0x20, 'usename1'
Signal i = 0x40 - Alerting on - pattern 0
Calling Party Number i = 0x0083, 'aaaaa', Plan:Unknown, Type:Unknown
Called Party Number i = 0x81, 'bbbbb', Plan:ISDN, Type:Unknown
ISDN BR1/0: Event: Received a DATA call from aaaaa on B1 at 64 Kb/s
ISDN BR1/0: Event: Accepting the call id 0x3EDC
ISDN BR1/0:1: Incoming call rejected, unbindable
ISDN BR1/0: TX -> RELEASE_COMP pd = 8 callref = 0x90
Cause i = 0x8095 - Call rejected

The isdn status is:

ISDN BRI1/0 interface
dsl 8, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 84, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 8 CCBs = 0
The Free Channel Mask: 0x80000003
Number of L2 Discards = 0, L2 Session ID = 28

I really don't know what's hapenning. I don' know if there is a problem with the ISDN switch, the routers configuration or the ISDN.

I hope somebody could help, thanks
 
Are you using caller id on the line? The "Cause i = 0x8095 - Call rejected" message indicates a problem with caller-id but I need more information. It looks like your L1 and L2 are working otherwise. Can you post configs?
 
thanks.

The central config is the next:

version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname xxxxx
!
enable password 7 104D
!
username aaaaaa password wwww
username bbbbbb password wwww

ip subnet-zero
!
!
no ip domain-lookup
!
isdn switch-type basic-net3
!
interface FastEthernet0/0
description connected to EthernetLAN
ip address xxx.xxx.xxx.xxxx xxx.xxx.xxx.xx
duplex auto
speed auto
!
interface BRI1/0
description connected to aaaaa,bbbbb
no ip address
encapsulation ppp
dialer pool-member 1
dialer pool-member 2
isdn switch-type basic-net3
!
interface BRI1/1
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/2
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/3
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/4
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/5
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/6
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/7
no ip address
shutdown
isdn switch-type basic-net3
!
interface Dialer1
description connected to aaaaa
ip address yyy.yyy.yyy.yy1 zzz.zzz.zzz.zzz
encapsulation ppp
no ip split-horizon
dialer pool 1
dialer remote-name aaaaa
dialer string xxxxx
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
interface Dialer2
description connected to bbbbb
ip address xxx.xxx.xx1 zzz.zzz.zzz.zzz
encapsulation ppp
no ip split-horizon
dialer pool 2
dialer remote-name bbbbb
dialer string yyyyy
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!


ip classless
ip route rrr.rrr.rrr.rrr zzz.zzz.zzz.zzz yyy.yyy.yyy.yy2
ip route sss.sss.sss.sss zzz.zzz.zzz.zzz xxx.xxx.xxx.xx2

no ip http server
ip pim bidir-enable
!
!
dialer-list 1 protocol ip permit
snmp-server community public RO
!
line con 0
exec-timeout 0 0
password wwww
login
line aux 0
line vty 0 4
password wwww
login
!
!
end


And the remote config (it's the same for every router):

version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname bbbbb
!
boot-start-marker
boot-end-marker
!
enable password wwww
!
username xxxxx password wwww
!
!
no aaa new-model
ip subnet-zero
no ip domain lookup
!
isdn switch-type basic-net3
!
interface Ethernet0
description connected to EthernetLAN
ip address sss.sss.sss.sss zzz.zzz.zzz.zzz
!
interface BRI0
no ip address
encapsulation ppp
dialer rotary-group 1
dialer-group 1
isdn switch-type basic-net3
no cdp enable
!
interface Dialer1
description connected to xxxxx
ip address xxx.xxx.xxx.xx2 zzz.zzz.zzz.zzz
encapsulation ppp
no ip split-horizon
dialer in-band
dialer map ip xxx.xxx.xxx.xx2 name xxxxx broadcast DDDDD
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
!
ip classless
ip route 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xx2
no ip http server
!
dialer-list 1 protocol ip permit
snmp-server community public RO
snmp-server enable traps tty
!
line con 0
exec-timeout 0 0
password login
transport preferred all
transport output all
stopbits 1
line vty 0 4
password login
transport preferred all
transport input all
transport output all
!
no rcapi server
!
!
!
end

I hope you can help me.
 
Paste this into one of the remote routers and try to make a call. The central site is using "dialer profiles" and the remote site is using "legacy ddr" commands. However, the rotary-group and dialer inband statements are leftover from modem days. With ISDN BRI they aren't necessary. Also, I changed the default route to point to the dialer interface.

!
configure terminal
!
interface BRI0
no ip address
encapsulation ppp
no dialer rotary-group 1
no dialer-group 1
dialer pool-member 1
isdn switch-type basic-net3
no cdp enable
!
interface Dialer1
description connected to xxxxx
ip address xxx.xxx.xxx.xx2 zzz.zzz.zzz.zzz
encapsulation ppp
no ip split-horizon
dialer pool 1
no dialer in-band
dialer string DDDDDD
dialer remote-name xxxxxx
no dialer map ip xxx.xxx.xxx.xx2 name xxxxx broadcast DDDDD
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
no ip http server
!
end
!
wr


Also, is there a reason you turned off split-horizon on the routers?

HTH

Tad
 
Thank you very much. i'm testing in 2 hours.

I don't know if split-horizon should be on or off. What's your advice?
 
Since you're doing static routes, I'd leave split-horizon on. Turning it off on the central router is one of the solutions to advertising routes in a hub and spoke configuration but your configs don't need it.

Tad
 
Once the basic ISDN is working you may want to add a "dialer load-threshold [load]" and a "dialer fast-idle [time]" to the configs. The first brings up the second line on the BRI and the second allows the dialers to timeout sooner if there is contention for the line.

Tad
 
In which conf I have to put these two commands)
The central? remotes? or boths?

Thanks
 
The first command goes on all routers. The second command goes on the central.
 
Hi, i put the new conf on to the remote router but it didn't go right.

There are five remote routers (i only put 2 to simplify)and i reconfigured the router the one that is bound to dialer five (in the central route). Maybe, this would be the problem.

Should i add the "dialer load-threshold [load]" and the "dialer fast-idle [time]" commands before or this is not the problem.

Thanks
 
What happened? Also, on the central router I see several BRI interfaces with no configuration. Are those being used at all?

Don't add the two commands until the basic ISDN is working. Did you reload the routers after you changed the configs? Sometimes that is necessary. What is your output for:

show ISDN status, debug ppp authentication, debug ppp negotiation, and debug dialer?

Also, check the username/password combinations on both sides to make sure they are entered correctly. (I'd retype them just to be sure.)
 
I have only used one BRI interface for five dialers (the interface BRI1/0 is connected to the five remore routers)

Yes, i reloaded the router after changin' its conf.

I did the debugs on the remote one (sorry i have no the other one)

ISDN BR0 Q931: TX -> SETUP pd = 8 callref = 0x03
Bearer Capability i = 0x8890
Standard = CCITT
Transer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x83
Called Party Number i = 0x80, 'bbbb'
Plan:Unknown, Type:Unknow
ISDN BR0 Q931: RX <- SETUP_ACK pd = 8 callref = 0x83
Channel ID i = 0x89
ISDN BR0 Q931: RX <- CALL_PROC pd = 8 callref = 0x83
Channel ID i = 0x89...
ISDN BR0 Q931: RX <- ALERTING pd = 8 callref = 0x83
Progress Ind i = 0x8088 - In-band info or appropriate now available
Display i = 'bbbb PROMETEO username'
ISDN BR0 Q931: RX <- DISCONNECT pd = 8 callref = 0x83
Cause i = 0x8095 - Call rejected
Progress Ind i = 0x8088 - In-band info or appropriate now available

The ISDN status is all right (Layer 1 activated and Layer 2 MULTIPLE_FRAME_ESTABLISHED)

When i did the ppp debug no entry appeared (no ppp negotiation, I suppose)

I did a dialer debug also:

BR0 DDR: rotor dialout [best] least recent failure is also most recent failure
BR0 DDR: rotor dialout [best] also has most recent failure
BR0 DDR: rotor dialout [best]
BR0 DDR: Dialing cause ip (s=xxxx.xxxx.xxxx.2, d=xxx.xxx.xxx.1)
BR0 DDR: Attempting to dial bbbbb...
BRI0: wait for isdn carrier timeout, call id=0x800B
DDR: Dialing failed, 3 packets unqueued and discarded

Notice this:

remote#sh int dialer 1
Dialer1 is up (spoofing), line protocol is up (spoofing)
Hardware is Unknown
Internet address is 10.16.1.2/24
MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec...

The BW is 56 Kb, but the BRI0 is 64 (problem?)

I´m too confused, i have more debugs if you want. Thanks
 
The BW should be 64Kbps for the BRI. Is the line using robbed-bit signaling from the ISDN provider? That is an issue and explains the dialer inband commands. Find out from the provider if this is the case. Did you post the full configs for the central and remote routers?
 
If you've got 56K, add a "speed 56" under the dialer1 on the remote routers.
 
Oops. Wrong command syntax for the dialer profile. The speed is for the dialer map with legacy DDR. Correct syntax under the dialer interface:

dialer string ddddddd class 56k.
 

I'll try to explain better (i'm spanish)

If you write a sh int command:

remote#sh int
BRI0 is up, line protocol is up (spoofing)
Hardware is BRI with S/T interface and POTS
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,

You see the BW is 64 Kbit but the Bw that appears in the Dialer 1 is 56 kb:

remote#sh int dialer 1
Dialer1 is up (spoofing), line protocol is up (spoofing)
Hardware is Unknown
Internet address is 10.16.1.2/24
MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec,

I asked to the ISDN provider for the robbed-bit signaling but they have to find out it (don't forget i live in Spain).
If the line is using robbed-bit signaling i supose then, the central router is rejecting every call, isn't it?
But, why can the central route make outgoing calls?

I have another question: why is a ALERTING mesage appearing? (it's a DATA call nor a voice CALL)

I'll put the confs in 20 min.

Thank you very much
 
Here are the configs. I have a trace made by the ISDN provider (from the Switch to the central route) if you want to

version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname central
!
enable password 7 104D
!
username username1 password ssss
username username2 password ssss
username username3 password ssss
username username4 password ssss
username username5 password ssss
ip subnet-zero
!
!
no ip domain-lookup
!
isdn switch-type basic-net3
!
!
!
interface FastEthernet0/0
description connected to EthernetLAN_
ip address 111.111.111.111 255.255.255.255
duplex auto
speed auto
!
interface BRI1/0
description connected to usernames
no ip address
encapsulation ppp
dialer pool-member 1
dialer pool-member 2
dialer pool-member 3
dialer pool-member 4
dialer pool-member 5
isdn switch-type basic-net3
!
interface BRI1/1
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/2
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/3
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/4
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/5
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/6
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/7
no ip address
shutdown
isdn switch-type basic-net3
!
interface Dialer1
description connected to username1
ip address aaa.aaa.aaa.1 255.255.255.0
encapsulation ppp
no ip split-horizon
dialer pool 1
dialer remote-name username1
dialer string 11111
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
interface Dialer2
description connected to username2
ip address bbb.bbb.bbb.1 255.255.255.0
encapsulation ppp
no ip split-horizon
dialer pool 2
dialer remote-name username2
dialer string 22222
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
interface Dialer3
description connected to username3
ip address ccc.ccc.ccc.1 255.255.255.0
encapsulation ppp
no ip split-horizon
dialer pool 3
dialer remote-name username3
dialer string 33333
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
interface Dialer4
description connected to username4
ip address ddd.ddd.ddd.1 255.255.255.0
encapsulation ppp
no ip split-horizon
dialer pool 4
dialer remote-name username4
dialer string 44444
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
interface Dialer5
description connected to username5
ip address eee.eee.eee.1 255.255.255.0
encapsulation ppp
no ip split-horizon
dialer pool 5
dialer remote-name username5
dialer string 55555
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
interface Dialer6
no ip address
!
ip classless
ip route (ip address) aaa.aaa.aaa.2
ip route (ip address2) bbb.bbb.bbb.2
ip route (ip adresss) ccc.ccc.ccc.2
ip route (ip address) ddd.ddd.ddd.2
ip route (ip address) eee.eee.eee.2
no ip http server
ip pim bidir-enable
!
!
dialer-list 1 protocol ip permit
snmp-server community public RO
!
line con 0
exec-timeout 0 0
password 7 0007
login
line aux 0
line vty 0 4
password 7 121A
login
!
!
end




!
version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname username1
!
boot-start-marker
boot-end-marker
!
enable password ssss
!
username central password ssss
!
!
no aaa new-model
ip subnet-zero
no ip domain lookup
!
isdn switch-type basic-net3
!
!
!
interface Ethernet0
description connected to EthernetLAN_
ip address ...........
!
interface BRI0
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
no cdp enable
!
interface Dialer1
description connected to central
ip address aaa.aaa.aaa.2 255.255.255.0
encapsulation ppp
no ip split-horizon
dialer pool 1
dialer string xxxxx
dialer remote-name central
dialer hold-queue 10
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
no ip http server
!
dialer-list 1 protocol ip permit
snmp-server community public RO
snmp-server enable traps tty
!
line con 0
exec-timeout 0 0
password ssss
login
transport preferred all
transport output all
stopbits 1
line vty 0 4
password cisco
login
transport preferred all
transport input all
transport output all
!
no rcapi server
!
!
!
end
 
Hi,
I had this same problem in an ICND class. It appears that you need to add PPP authentication to the physical interface to bind an incoming call to the appropriate dialer interface.
So i assume that if you add ppp auth chap pap callin to the BRI interface that everything will work fine!

Below i included a little peace of information on this from Cisco's website:

1. Remember that there are four attempts to bind. Assuming that we have more than one dialer profile, the CLID and DNIS bind attempt fails and PPP authentication is not configured (pre-empting the possibility of the fourth test). The following debug dialer message will be generated on the called router.
*Mar 1 11:59:36.521: ISDN BR0:1: Incoming call rejected, unbindable
Solution: Configure ppp authentication chap | pap [callin] on the physical interface.
2. If PPP authentication is enabled on the physical interface, then the fourth attempt to bind will proceed. The router will use the authenticated username to attempt to bind to one of the dialer interfaces in the dialer pool. If that attempt fails, the following debug will be seen on the called router:
*Mar 1 12:03:32.227: BRI0:1:
Authenticated host HQ-NAS with no matching dialer profile
 
Hi,

I put the "ppp authentication Chap Callin" command on the BRI and now it's goin' on.

Thank you very much
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top