Home > Archive > CCNP > December 2000 > help real life isdn issue !!!





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author help real life isdn issue !!!

2000-12-13, 7:27 pm

i am trying to connect 2 sites with isdn (point to point). it will be using ddr.
right now both sites are configured to dialup but i want to disable dialup on SITE1.
anyway the issue is....when there is ip traffic a dialup happens but the debug isdn q931 comes up with some errors and the call hangs up.

first a few things..switch type is ok.
confirmed that with the show isdn status command..spids are valid.

the errors which are notable are
Cause i=0x82C1 bearer capability not implemented
Signal i=0x03 network congestion tone on

bearer capability i=0x8890218F

the configs:

site 2 config....(remote site that needs to call up)
!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname SITE2
!
enable password mike
!
username SITE1 password letmethru
ip subnet-zero
no ip domain-lookup
isdn switch-type basic-ni1
!
interface Ethernet0/0
ip address 20.20.1.1 255.255.255.0
no logging event subif-link-status

!
interface BRI0/0
encapsulation ppp
dialer rotary-group 0
no logging event subif-link-status
isdn spid1 20272723210101 7272321
isdn spid2 20272723290101 7272329
no fair-queue
!
interface Ethernet1/0
ip address 20.20.2.1 255.255.255.0
no logging event subif-link-status

!
interface Ethernet1/1
ip address 20.20.3.1 255.255.255.0
no logging event subif-link-status

!
interface Ethernet1/2
ip address 20.20.4.1 255.255.255.0
no logging event subif-link-status

!
interface Ethernet1/3
ip address 20.20.5.1 255.255.255.0
no logging event subif-link-status

!
interface Dialer0
ip unnumbered Ethernet0/0
encapsulation ppp
dialer in-band
dialer idle-timeout 300
dialer map ip 10.30.62.14 name SITE1 speed 56 broadcast 2026987524
dialer map ip 10.30.62.14 name SITE1 speed 56 broadcast 2026987525
dialer hold-queue 10
dialer load-threshold 200 either
dialer-group 1
ppp authentication chap callin
ppp multilink
!
ip http server
ip classless
ip route 0.0.0.0 0.0.0.0 10.30.62.14
ip route 10.30.62.14 255.255.255.255 Dialer0 permanent
dialer-list 1 protocol ip permit
!
line con 0
password mike
login
line aux 0
line vty 0 4
password mike
login
!
end
------------------------

site 1 config

!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname SITE1
!
enable password mike
!
username SITE2 password letmethru
ip subnet-zero
no ip domain-lookup
isdn switch-type basic-ni1
!
interface Ethernet0/0
ip address 10.30.62.14 255.255.255.0
!
interface BRI0/0
no ip address
encapsulation ppp
isdn spid1 20269875240101 6987524
isdn spid2 20269875250101 6987525
dialer rotary-group 0
no fair-queue
!
interface Ethernet1/0
no ip address
shutdown
!
interface Ethernet1/1
no ip address
shutdown
!
interface Ethernet1/2
no ip address
no logging event subif-link-status
shutdown
!
interface Ethernet1/3
no ip address
shutdown
!
interface Dialer0
ip unnumbered Ethernet0/0
encapsulation ppp
dialer in-band
dialer idle-timeout 300
dialer map ip 20.20.1.1 name SITE2 speed 56 broadcast 2027272321
dialer map ip 20.20.1.1 name SITE2 speed 56 broadcast 2027272329
dialer hold-queue 10
dialer load-threshold 200 either
dialer-group 1
no fair-queue
ppp authentication chap callin
ppp multilink
!
ip http server
ip classless
ip route 0.0.0.0 0.0.0.0 20.20.1.1
ip route 20.20.1.1 255.255.255.255 Dialer0 permanent
dialer-list 1 protocol ip permit
!
line con 0
password mike
login
line aux 0
line vty 0 4
password mike
login
!
end


should i disable the dialer map statements on site1?
and also shd i take off the broadcast in the dialer map statement?
i dont want broadcasts to go through.

any help will be appreciated.

regards
mongol

2000-12-13, 11:35 pm

Cisco has a great resource you may want to review: http://www.cisco.com/warp/public/79...fbookindex.html

My first question to you would be are you sure you have 56k B channels?

Second point would be to use debug ppp negotiation, cuz you'll learn more about what's going on then what you are currently seeing.


Yankee

[This message has been edited by Yankee (edited 12-13-2000).]

2000-12-13, 11:53 pm

Yankee, if q931 call setup is failing, wouldn't he fail to start ppp negotiation? At least it would unless his call is actually coming up and lcp fails immediately.
I have to go with your first instinct. Don't use 56k B channels unless that's all your telco supports.
And you should also try to have only one site call the other, otherwise you run the risk of having both try to dial at the same time.

MadChef

2000-12-14, 12:30 am

And another thing.....

Why are you trying to use in-band signaling with BRI interfaces? You have a TA there? If you have a U interface (the rj45 guy) then you shouldn't be using in band signaling. Nix dialer in-band.
And why 'ppp auth chap callin" instead of just "ppp auth chap"? Lets see some debug ppp neg output if you can get call setup happening.
You know, I can see no real reason to use dialer profiles here. Whey not just use simple legacy dialing instead? Toss the dialer interface and set everything up on the BRI interface.

Let us know where you get tomorrow. I'm interested now.

MadChef

[This message has been edited by MadChef (edited 12-13-2000).]

2000-12-14, 8:10 pm

i did as u suggested.
all on the bri0/0 interface without rotary and without in-band.
still the same message...call disconnects because carrier capability is not implemented.

is it true that there are 2 kinds of isdn lines u can provision...pure data (expensive) and the normal voice lines...(charged on call basis)...i am made to believe that cisco routers to carry data on such voice isdn lines needs some extra config commands....is this true?
if yes what are they as that would seem normal...as it says bearer capability again and again.
regards
mongol

2000-12-14, 8:19 pm

here is the debug output

SITE1#sh debug
ISDN:
ISDN events debugging is on
ISDN Q921 packets debugging is on
ISDN Q931 packets debugging is on
Dial on demand:
Dial on demand events debugging is on
Dial on demand packets debugging is on
SITE1#
SITE1#
SITE1#
SITE1#
SITE1#
SITE1#
SITE1#
SITE1#ping 20.20.20.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 20.20.20.2, timeout is 2 seconds:

BRI0/0: ip (s=20.20.20.1, d=20.20.20.2), 100 bytes, interesting (ip PERMIT)
BRI0/0: Dialing cause ip (s=20.20.20.1, d=20.20.20.2)
BRI0/0: Attempting to dial 2027272321
ISDN BR0/0: Outgoing call id = 0x8069
Packet queued
ISDN BR0/0: Event: Call to 2027272321 at 64 Kb/s
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 81 nr = 68 i = 0x0801690504
0288901801832C0A32303237323732
333231
SETUP pd = 8 callref = 0x69
Bearer Capability i = 0x8890
Channel ID i = 0x83
Keypad Facility i = '2027272321'
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 82
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 68 nr = 82 i = 0x0801E90218
0189
.CALL_PROC pd = 8 callref = 0xE9
Channel ID i = 0x89
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 69
ISDN BR0/0: received HOST_PROCEEDING
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 69 nr = 82 i = 0x0801E94508
0282C1340103
DISCONNECT pd = 8 callref = 0xE9
Cause i = 0x82C1 - Bearer capability not implemented
Signal i = 0x03 - Network congestion tone on
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 70
ISDN BR0/0: received HOST_DISCONNECT
ISDN BR0/0: Event: Call to 2027272321 was hung up.
BRI0/0: wait for carrier timeout, call id=0x8069
BRI0/0: Attempting to dial 2027272329
ISDN BR0/0: Outgoing call id = 0x806A
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 82 nr = 70 i = 0x0801694D
RELEASE pd = 8 callref = 0x69
ISDN BR0/0: Event: Call to 2027272329 at 64 Kb/s
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 83
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 83 nr = 70 i = 0x08016A0504
0288901801832C0A32303237323732
333239
SETUP pd = 8 callref = 0x6A
Bearer Capability i = 0x8890
Channel ID i = 0x83
Keypad Facility i = '2027272329'
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 84
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 70 nr = 84 i = 0x0801E95A
RELEASE_COMP pd = 8 callref = 0xE9
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 71
BRI0/0: ip (s=20.20.20.1, d=20.20.20.2), 100 bytes, interesting (ip PERMIT)
Packet queued
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 71 nr = 84 i = 0x0801EA0218
018A
CALL_PROC pd = 8 callref = 0xEA
Channel ID i = 0x8A
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 72
ISDN BR0/0: received HOST_PROCEEDING
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 72 nr = 84 i = 0x0801EA4508
0282C1340103
DISCONNECT pd = 8 callref = 0xEA
Cause i = 0x82C1 - Bearer capability not implemented
Signal i = 0x03 - Network congestion tone on
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 73
ISDN BR0/0: received HOST_DISCONNECT
ISDN BR0/0: Event: Call to 2027272329 was hung up.
BRI0/0: wait for carrier timeout, call id=0x806A
: Dialing failed, 2 packets unqueued and discarded
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 84 nr = 73 i = 0x08016A4D
RELEASE pd = 8 callref = 0x6A
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 85.
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 73 nr = 85 i = 0x0801EA5A
RELEASE_COMP pd = 8 callref = 0xEA
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 74
BRI0/0: ip (s=20.20.20.1, d=20.20.20.2), 100 bytes, interesting (ip PERMIT)
BRI0/0: Dialing cause ip (s=20.20.20.1, d=20.20.20.2)
BRI0/0: Attempting to dial 2027272321
ISDN BR0/0: Outgoing call id = 0x806B
Packet queued
ISDN BR0/0: Event: Call to 2027272321 at 64 Kb/s
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 85 nr = 74 i = 0x08016B0504
0288901801832C0A32303237323732
333231
SETUP pd = 8 callref = 0x6B
Bearer Capability i = 0x8890
Channel ID i = 0x83
Keypad Facility i = '2027272321'
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 86
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 74 nr = 86 i = 0x0801EB0218
0189
.CALL_PROC pd = 8 callref = 0xEB
Channel ID i = 0x89
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 75
ISDN BR0/0: received HOST_PROCEEDING
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 75 nr = 86 i = 0x0801EB4508
0282C1340103
DISCONNECT pd = 8 callref = 0xEB
Cause i = 0x82C1 - Bearer capability not implemented
Signal i = 0x03 - Network congestion tone on
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 76
ISDN BR0/0: received HOST_DISCONNECT
ISDN BR0/0: Event: Call to 2027272321 was hung up.
BRI0/0: wait for carrier timeout, call id=0x806B
BRI0/0: Attempting to dial 2027272329
ISDN BR0/0: Outgoing call id = 0x806C
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 86 nr = 76 i = 0x08016B4D
RELEASE pd = 8 callref = 0x6B
ISDN BR0/0: Event: Call to 2027272329 at 64 Kb/s
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 87
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 87 nr = 76 i = 0x08016C0504
0288901801832C0A32303237323732
333239
SETUP pd = 8 callref = 0x6C
Bearer Capability i = 0x8890
Channel ID i = 0x83
Keypad Facility i = '2027272329'
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 88
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 76 nr = 88 i = 0x0801EB5A
RELEASE_COMP pd = 8 callref = 0xEB
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 77
BRI0/0: ip (s=20.20.20.1, d=20.20.20.2), 100 bytes, interesting (ip PERMIT)
Packet queued
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 77 nr = 88 i = 0x0801EC0218
018A
CALL_PROC pd = 8 callref = 0xEC
Channel ID i = 0x8A
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 78
ISDN BR0/0: received HOST_PROCEEDING
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 78 nr = 88 i = 0x0801EC4508
0282C1340103
DISCONNECT pd = 8 callref = 0xEC
Cause i = 0x82C1 - Bearer capability not implemented
Signal i = 0x03 - Network congestion tone on
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 79
ISDN BR0/0: received HOST_DISCONNECT
ISDN BR0/0: Event: Call to 2027272329 was hung up.
BRI0/0: wait for carrier timeout, call id=0x806C
: Dialing failed, 2 packets unqueued and discarded
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 88 nr = 79 i = 0x08016C4D
RELEASE pd = 8 callref = 0x6C
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 89.
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 79 nr = 89 i = 0x0801EC5A
RELEASE_COMP pd = 8 callref = 0xEC
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 80
BRI0/0: ip (s=20.20.20.1, d=20.20.20.2), 100 bytes, interesting (ip PERMIT)
BRI0/0: Dialing cause ip (s=20.20.20.1, d=20.20.20.2)
BRI0/0: Attempting to dial 2027272321
ISDN BR0/0: Outgoing call id = 0x806D
Packet queued
ISDN BR0/0: Event: Call to 2027272321 at 64 Kb/s
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 89 nr = 80 i = 0x08016D0504
0288901801832C0A32303237323732
333231
SETUP pd = 8 callref = 0x6D
Bearer Capability i = 0x8890
Channel ID i = 0x83
Keypad Facility i = '2027272321'
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 90
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 80 nr = 90 i = 0x0801ED0218
0189
.
Success rate is 0 percent (0/5)
SITE1#CALL_PROC pd = 8 callref = 0xED
Channel ID i = 0x89
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 81
ISDN BR0/0: received HOST_PROCEEDING
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 81 nr = 90 i = 0x0801ED4508
0282C1340103
DISCONNECT pd = 8 callref = 0xED
Cause i = 0x82C1 - Bearer capability not implemented
Signal i = 0x03 - Network congestion tone on
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 82
ISDN BR0/0: received HOST_DISCONNECT
ISDN BR0/0: Event: Call to 2027272321 was hung up.
BRI0/0: wait for carrier timeout, call id=0x806D
BRI0/0: Attempting to dial 2027272329
ISDN BR0/0: Outgoing call id = 0x806E
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 90 nr = 82 i = 0x08016D4D
RELEASE pd = 8 callref = 0x6D
ISDN BR0/0: Event: Call to 2027272329 at 64 Kb/s
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 91
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 91 nr = 82 i = 0x08016E0504
0288901801832C0A32303237323732
333239
SETUP pd = 8 callref = 0x6E
Bearer Capability i = 0x8890
Channel ID i = 0x83
Keypad Facility i = '2027272329'
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 92
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 82 nr = 92 i = 0x0801ED5A
RELEASE_COMP pd = 8 callref = 0xED
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 83
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 83 nr = 92 i = 0x0801EE0218
018A
CALL_PROC pd = 8 callref = 0xEE
Channel ID i = 0x8A
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 84
ISDN BR0/0: received HOST_PROCEEDING
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 84 nr = 92 i = 0x0801EE4508
0282C1340103
DISCONNECT pd = 8 callref = 0xEE
Cause i = 0x82C1 - Bearer capability not implemented
Signal i = 0x03 - Network congestion tone on
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 85
ISDN BR0/0: received HOST_DISCONNECT
ISDN BR0/0: Event: Call to 2027272329 was hung up.
BRI0/0: wait for carrier timeout, call id=0x806E
: Dialing failed, 1 packets unqueued and discarded
ISDN BR0/0: TX -> INFOc sapi = 0 tei = 112 ns = 92 nr = 85 i = 0x08016E4D
RELEASE pd = 8 callref = 0x6E
ISDN BR0/0: RX <- RRr sapi = 0 tei = 112 nr = 93
ISDN BR0/0: RX <- INFOc sapi = 0 tei = 112 ns = 85 nr = 93 i = 0x0801EE5A
RELEASE_COMP pd = 8 callref = 0xEE
ISDN BR0/0: TX -> RRr sapi = 0 tei = 112 nr = 86
SITE1#

2000-12-14, 11:13 pm

I think it might be time to bring the telco in on this one. Is this a long distance call? If so, does your provider have the ability to support long distance ISDN (a problem I've run into before)?
You should be able to get a telco engineer on the phone and have them monitor the call setup from the switch. They may be able to offer some insight. The could also generate calls from the switch and see how you answer. I think your ISDN setup from the router point of view is ok. Time to talk to the telco.

Good luck. Let us know what happens.

MadChef

2000-12-15, 12:55 am

What Mad Chef said rings a bell with me"figuratively" .
We had to change our long distance provider on our PRI to finally get some results.
Jonathan Foster

2000-12-15, 3:27 am

its a local call ....within the same city.
area code is the same.
but i will get the telco to monitor it.
lets see
regards
mongol

2000-12-15, 1:33 pm

Madchef ,

Regarding your first post ,I must disagree with your statement .Configuring dialers with the dialer pool feature is much more flexible than having it configured in the bri interface directly .In this way you will not be able to use the bri interface anymore for another conection .With dialers ,u can configure any dialers u want to use the same physical interface .

Regards.

2000-12-15, 4:07 pm

If anyone is interested here are some debug commands for Remote connectivity:
Debug and Show Commands to Use for Troubleshooting
show isdn status - the status should be:
layer 1 = active
layer 2 = MULTIPLE_FRAMES_ESTABLISHED
If Layer 1 is not active, then the wiring adapter or port may be bad or not plugged in. If Layer 2 is in a state of TEI_Assign then the router is not talking to the switch.


show interface bri0 1 2 -To show you if the B channels are up.

show ppp multilink - To show if you have a multilink connection.

debug isdn q931 - To check ISDN connections as users dial in to see what is happening with the ISDN call (for example, if the connection is being dropped).

debug ppp negotiation - To see if a client is passing PPP negotiation; this is when you check for address negotiation.

debug ppp authentication - To see if a client is passing authentication. If you are using a version prior to Cisco IOS™ release 11.2, use the debug ppp chap command instead.

debug ppp error - To display protocol errors and error statistics associated with PPP connection negotiation and operation.

debug dialer - To see dial-on-demand routing information.

debug ppp multilink events - To show multilink negotiations. (This command is only supported in Cisco IOS™ release 11.2 and later.)

2000-12-15, 4:28 pm

thanks bigK
i have used all those commands many times.
layer 1 and 2 are up.
ppp authentication does not happen till a layer3 connection is made.
its at this point that the connection is failing ....in essence...connect..proceed..then disconnect due to carrier capability not implemented.
on the upside....its giving me all i need for the bcran exams..lol
i am made to believe isdn is a major part.
regards

2000-12-15, 5:04 pm

One thing I do know is Bearer Capability i = 0x8890 is a normal Call Clearing, but I am having trouble decoding i = 0x82C1.

0x = indicates Hex values to follow
8 = indicates ITU-T standard coding
2 = Public network service local
C = is the Cause value
This is the one I am trying to decipher

A possibility:
The connection cannot be completed because the destination does not respond to the call.
(No user responding)

2000-12-19, 4:59 pm

thanks a lot to all of you to have tried to help.
i resolved the problem.
instead of the isdn lines at both ends being direct some as*@#$%@ had wired the lines through the exchange.
so all i had to do was put a 9 before the called number in the dialer map ip statement.
worked like a dream.
goodness what a waste of time but again i dont have to study isdn for bcran anymore ..!!!
thanks again
mongol

2000-12-19, 6:08 pm

quote:
Originally posted by richard21:

Regarding your first post ,I must disagree with your statement .Configuring dialers with the dialer pool feature is much more flexible than having it configured in the bri interface directly .



It certainly is more flexible and you're right that you lock the BRI interface in for this purpose. My PERSONAL preference is to use legacy dialing unless I have a specific reason to use dialer profiles. It helps my feeble little mind if I keep things as simple as possible. Plus, that's the way I learned how to do things first and I'm resistant to change.

MadChef

2000-12-19, 11:47 pm

Well , simplicity might be a good thing but flexibility + simplicity might be even better.

Regards .
Sponsored Links





Free Braindumps | MCSE braindumps software forum

Copyright 2003 - 2008 examnotes.net