Any Cisco Experts in here?
#1
Scooby Regular
Thread Starter
Join Date: Jan 2001
Location: Isle of Man
Posts: 359
Likes: 0
Received 0 Likes
on
0 Posts
Hi all,
Anyone know Cisco IOS like the back of their hand?
Im having trouble getting an ISDN Cisco 801 router to connect to the users ISP.
The router can be pinged from within the network ok, but immediately disconnects when trying the ISDN line.
The line has been tested by BT, another router has been used with thier config loaded, and a phone has been used on the line which worked ok.
Still get same problem when using the other router.
Sample of debug isdn q931 is here...
00:01:60129542144: ISDN BR0: TX -> SETUP pd = 8 callref = 0x01
00:01:60136176268: Bearer Capability i = 0x8890
00:01:60129583104: Channel ID i = 0x83
00:01:60129583104: Called Party Number i = 0x80, '08440406203'
00:01:14: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x81
00:01:14: Channel ID i = 0x89
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x81
00:01:15: Cause i = 0x8AA9 - Temporary failure
00:01:64424550400: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x01
00:01:64431143564: Cause i = 0x80A908 - Temporary failure
00:01:64424550400: ISDN BR0: TX -> SETUP pd = 8 callref = 0x02
00:01:64431143564: Bearer Capability i = 0x8890
00:01:64424550400: Channel ID i = 0x83
00:01:64424550400: Called Party Number i = 0x80, '08440406203'
00:01:15: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x81
00:01:15: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x82
00:01:15: Channel ID i = 0x89
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x82
00:01:15: Cause i = 0x8AA9 - Temporary failure
00:01:68719517696: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x02
00:01:68726110860: Cause i = 0x80A908 - Temporary failure
00:01:16: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x82
Any ideas? as its all a bit greek to me!
Cheers,
Mark...
[Edited by markpm - 1/21/2003 12:53:47 PM]
Anyone know Cisco IOS like the back of their hand?
Im having trouble getting an ISDN Cisco 801 router to connect to the users ISP.
The router can be pinged from within the network ok, but immediately disconnects when trying the ISDN line.
The line has been tested by BT, another router has been used with thier config loaded, and a phone has been used on the line which worked ok.
Still get same problem when using the other router.
Sample of debug isdn q931 is here...
00:01:60129542144: ISDN BR0: TX -> SETUP pd = 8 callref = 0x01
00:01:60136176268: Bearer Capability i = 0x8890
00:01:60129583104: Channel ID i = 0x83
00:01:60129583104: Called Party Number i = 0x80, '08440406203'
00:01:14: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x81
00:01:14: Channel ID i = 0x89
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x81
00:01:15: Cause i = 0x8AA9 - Temporary failure
00:01:64424550400: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x01
00:01:64431143564: Cause i = 0x80A908 - Temporary failure
00:01:64424550400: ISDN BR0: TX -> SETUP pd = 8 callref = 0x02
00:01:64431143564: Bearer Capability i = 0x8890
00:01:64424550400: Channel ID i = 0x83
00:01:64424550400: Called Party Number i = 0x80, '08440406203'
00:01:15: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x81
00:01:15: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x82
00:01:15: Channel ID i = 0x89
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x82
00:01:15: Cause i = 0x8AA9 - Temporary failure
00:01:68719517696: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x02
00:01:68726110860: Cause i = 0x80A908 - Temporary failure
00:01:16: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x82
Any ideas? as its all a bit greek to me!
Cheers,
Mark...
[Edited by markpm - 1/21/2003 12:53:47 PM]
#3
This is the important bit
00:01:15: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x81
00:01:15: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x82
00:01:15: Channel ID i = 0x89
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x82
00:01:15: Cause i = 0x8AA9 - Temporary failure
00:01:68719517696: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x02
00:01:68726110860: Cause i = 0x80A908 - Temporary failure
00:01:16: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x82
From reading through the log, the router has connected to bt, and raised the br0 interface. However, the
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x82
00:01:15: Cause i = 0x8AA9 - Temporary failure
Shows the cause code of A9 which indicates a problem with the line. Now if another router has worked, it could be that this router has been incorrectly configured.
If you want and can send me a copy of the running config then I can have a look through it for you??
Email as per profile
00:01:15: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x81
00:01:15: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x82
00:01:15: Channel ID i = 0x89
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x82
00:01:15: Cause i = 0x8AA9 - Temporary failure
00:01:68719517696: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x02
00:01:68726110860: Cause i = 0x80A908 - Temporary failure
00:01:16: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0x82
From reading through the log, the router has connected to bt, and raised the br0 interface. However, the
00:01:15: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0x82
00:01:15: Cause i = 0x8AA9 - Temporary failure
Shows the cause code of A9 which indicates a problem with the line. Now if another router has worked, it could be that this router has been incorrectly configured.
If you want and can send me a copy of the running config then I can have a look through it for you??
Email as per profile
#4
Scooby Regular
Another router was used with the dodgy one's configu file and worked, so the config must be OK.
What about the BRI interface? maybe it's just faulty.
Can you swap the BRI card between routers and try?
Stefan
What about the BRI interface? maybe it's just faulty.
Can you swap the BRI card between routers and try?
Stefan
#5
Possibly relevant, I use a Draytek router rather than Cisco but if the line is busy I get a "temporary failure" message rather than "line busy" which would make more sense....
I used a free ISP (Ace Internet) to test mine when I thought I had a fault..
http://www.ispreview.co.uk/0845list/0845.shtml
Thanks
Gavin
[Edited by GavinP - 1/21/2003 1:50:52 PM]
I used a free ISP (Ace Internet) to test mine when I thought I had a fault..
http://www.ispreview.co.uk/0845list/0845.shtml
Thanks
Gavin
[Edited by GavinP - 1/21/2003 1:50:52 PM]
#6
Scooby Senior
Join Date: Oct 2000
Location: Zurich, Switzerland
Posts: 3,105
Likes: 0
Received 0 Likes
on
0 Posts
Last one I had like this, customer hadn't payed ISP bill
Can you use q931 debug on UK ISDN? If so, try;
http://www.cisco.com/warp/customer/129/isdn_disc_code.html
Richard
Can you use q931 debug on UK ISDN? If so, try;
http://www.cisco.com/warp/customer/129/isdn_disc_code.html
Richard
Trending Topics
#8
Scooby Regular
Thread Starter
Join Date: Jan 2001
Location: Isle of Man
Posts: 359
Likes: 0
Received 0 Likes
on
0 Posts
Woo, thanks for the replies chaps...
(I posted this on 2 Cisco/Networking forums and have had NO replies!)
Dowser, it IS a q931 debug log, and that website was most helpful, thanks.
Ozzy, its a small Cisco 801 so no separate BRI card AFAIK.
And Chockymonster, thanks for the offer of taking a look through the config for me, but gotta respect customers network security at the moment Im afraid. Im sure you understand...
It does look like a BT (or MT over here) problem to me from what Ive gleaned from deciphering the failure codes, so armed with this latest info we are looking into it further...
Many thanks again,
Mark...
(I posted this on 2 Cisco/Networking forums and have had NO replies!)
Dowser, it IS a q931 debug log, and that website was most helpful, thanks.
Ozzy, its a small Cisco 801 so no separate BRI card AFAIK.
And Chockymonster, thanks for the offer of taking a look through the config for me, but gotta respect customers network security at the moment Im afraid. Im sure you understand...
It does look like a BT (or MT over here) problem to me from what Ive gleaned from deciphering the failure codes, so armed with this latest info we are looking into it further...
Many thanks again,
Mark...
#9
Looks very strange to me. The router says the BT switch is causing the disconnect. You might want to try and upgrade the IOS as sometimes if the router should do everything correct ans you know there is no config problem it's the IOS. This is the very first part of the ISDN setup and the 64k bearer has not even been setup, this is just signalling at the moment so not much can go wrong.
You might also want to try dialing yourself to see if anything happends. You could either get a standard setup message and a disconnect or if the router is configured it will answer on the second B Channel. This will test the basic setup of the router and the connection from the router to the ISDN switch.
You should see something like this if the router answers itself
00:07:16: ISDN BR0: TX -> SETUP pd = 8 callref = 0x04
00:07:16: Bearer Capability i = 0x8890
00:07:16: Channel ID i = 0x83
00:07:16: Called Party Number i = 0x80, '01xxxxxxxx'
00:07:16: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x84
00:07:16: Channel ID i = 0x89
00:07:16: ISDN BR0: RX <- SETUP pd = 8 callref = 0x01
00:07:16: Sending Complete
00:07:16: Bearer Capability i = 0x8890
00:07:16: Channel ID i = 0x8A
00:07:16: Called Party Number i = 0x81, '2xxxxx'
00:07:17: ISDN BR0: Event: Received a DATA call from <unknown> on B2 at 64 Kb/s
00:07:17: ISDN BR0: TX -> CALL_PROC pd = 8 callref = 0x81
00:07:17: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
00:07:17: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to unknown
00:07:17: ISDN BR0: TX -> ALERTING pd = 8 callref = 0x81
00:07:17: ISDN BR0: TX -> CONNECT pd = 8 callref = 0x81
00:07:17: ISDN BR0: RX <- CONNECT_ACK pd = 8 callref = 0x01
00:07:17: ISDN BR0: RX <- ALERTING pd = 8 callref = 0x84
00:07:17: ISDN BR0: RX <- CONNECT pd = 8 callref = 0x84
00:07:17: ISDN BR0: TX -> CONNECT_ACK pd = 8 callref = 0x04
00:07:17: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
00:07:17: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01xxxxxxxxxx
00:07:23: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to isdn-router
00:07:23: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01xxxxxxxxxx
Si
[Edited by SiCotty - 1/21/2003 7:00:48 PM]
[Edited by SiCotty - 1/21/2003 7:03:40 PM]
You might also want to try dialing yourself to see if anything happends. You could either get a standard setup message and a disconnect or if the router is configured it will answer on the second B Channel. This will test the basic setup of the router and the connection from the router to the ISDN switch.
You should see something like this if the router answers itself
00:07:16: ISDN BR0: TX -> SETUP pd = 8 callref = 0x04
00:07:16: Bearer Capability i = 0x8890
00:07:16: Channel ID i = 0x83
00:07:16: Called Party Number i = 0x80, '01xxxxxxxx'
00:07:16: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x84
00:07:16: Channel ID i = 0x89
00:07:16: ISDN BR0: RX <- SETUP pd = 8 callref = 0x01
00:07:16: Sending Complete
00:07:16: Bearer Capability i = 0x8890
00:07:16: Channel ID i = 0x8A
00:07:16: Called Party Number i = 0x81, '2xxxxx'
00:07:17: ISDN BR0: Event: Received a DATA call from <unknown> on B2 at 64 Kb/s
00:07:17: ISDN BR0: TX -> CALL_PROC pd = 8 callref = 0x81
00:07:17: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
00:07:17: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to unknown
00:07:17: ISDN BR0: TX -> ALERTING pd = 8 callref = 0x81
00:07:17: ISDN BR0: TX -> CONNECT pd = 8 callref = 0x81
00:07:17: ISDN BR0: RX <- CONNECT_ACK pd = 8 callref = 0x01
00:07:17: ISDN BR0: RX <- ALERTING pd = 8 callref = 0x84
00:07:17: ISDN BR0: RX <- CONNECT pd = 8 callref = 0x84
00:07:17: ISDN BR0: TX -> CONNECT_ACK pd = 8 callref = 0x04
00:07:17: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
00:07:17: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01xxxxxxxxxx
00:07:23: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to isdn-router
00:07:23: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01xxxxxxxxxx
Si
[Edited by SiCotty - 1/21/2003 7:00:48 PM]
[Edited by SiCotty - 1/21/2003 7:03:40 PM]
#10
Scooby Regular
Thread Starter
Join Date: Jan 2001
Location: Isle of Man
Posts: 359
Likes: 0
Received 0 Likes
on
0 Posts
Thanks again guys.
The customer called us late on this afternoon to say it had 'fixed itself'!
So, a problem at the other end it was then!
Cheers
Mark...
The customer called us late on this afternoon to say it had 'fixed itself'!
So, a problem at the other end it was then!
Cheers
Mark...
Thread
Thread Starter
Forum
Replies
Last Post
The Joshua Tree
Computer & Technology Related
18
11 September 2015 09:24 PM