Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

strange **ERROR** on isdn

Hi All,

I am having some problems on an ISDN link that dials into our main office.

The router dials out, but I am not seeing the call come in at the central office.

Attached is a text file showing the basic config and the output from debug isdn standard.

thanks in advance for any help. :)

26 REPLIES
Blue

Re: strange **ERROR** on isdn

also run a 'debug isdn q931'

this will show us some behind the scenes isdn operation.

how about show us the isdn interface configs as well.

New Member

Re: strange **ERROR** on isdn

Hi,

Please find the debug isdn q931 and q921. It is strange that they are not showing much and makes me really believe that my problem is with the remote router.

The central router is working for other sites that dial in as well.

I have also ran the configuration through output interpretor with no errors. A few warnings, but no errors. I have changed the IP addresses and the passwords on the configuraion.

I keep comming up with that weird **Error**. I havent seen it before and think this is a real hint.

thanks very much for your help.

New Member

Re: strange **ERROR** on isdn

on the central router , use the isdn test call int bri x/x command onto its own number and see if this works. what type of router at central and what isdn cards ?

Hall of Fame Super Silver

Re: strange **ERROR** on isdn

While I agree that running debug isdn q931 is frequently good and may give helpful information, I believe that the debug that was posted does show that there is an incoming call. The debug that I would be particularly interested in would be debug ppp authentication. I suspect that there is an authentication problem - especially because I do not see any authentication configured in the partial config that was posted.

HTH

Rick

New Member

Re: strange **ERROR** on isdn

Hi and thanks very much for your reply. I took the authentication out of the previous config just to narrow down potential prospects.

When I run debug ppp events, authentication, and negotiatiion.... I am not getting output. Also, when I run debug ISDN at the central site, I can see that the call is not making it back to the central office. The router tries to dial out, but it is not successful in making it past the first ISDN switch as the debug q921 shows on another reply.

I ran the config past the output interpretor tool this morning with no reported errors as well. hmmm.... not sure what to do at this point. I might pass this one onto our lead engineer who will hopefully log a TAC case.

Thanks again for all of your help.

Hall of Fame Super Silver

Re: strange **ERROR** on isdn

I am surprised that you are not getting any output from debug ppp negotiation, ppp authentication, or ppp events. I thought that the original debug did indicate an incoming call. Perhaps the output of debug isdn q931 would be more helpful that I had thought.

HTH

Rick

New Member

Re: strange **ERROR** on isdn

Hi Rick,

Thanks for that. I ran debug q931 again and then added ppp neg. Didnt see much come through for ppp negotiation though.

please see attached.

a

Hall of Fame Super Silver

Re: strange **ERROR** on isdn

Thanks for posting the additional information. There is quite a bit of debug enabled and very little debug output which I thought was strange. So I went back to the information that you had posted before and took a closer look at the show tech that you posted. I found this in the output:

BRI unit 0:

Layer 1 is DEACTIVATED. (ISDN L1 State F3)

This indicates that there is a problem with the BRI circuit. Can you check this out and let us know what you find?

HTH

Rick

New Member

Re: strange **ERROR** on isdn

Hi,

I checked the central router and it is receiving calls from other routers.

I also reconfigured this remote router to dial our other central router with identical problems and the strange error message.

Thanks very much for your reply.

New Member

Re: strange **ERROR** on isdn

Not sure which debug you have turned on, but "debug isdn Q931" would be more helpful. This will show you the actuall ISDN messages that are being passed between the router and central office and give you a better idea where the failure is happening.

New Member

Re: strange **ERROR** on isdn

hi,

the output of debug isdn q931 for you here.

i have had a look and it seems like the router is not bringing up the layer one interface.

it is all very strange.

thanks very much for your help

Hall of Fame Super Silver

Re: strange **ERROR** on isdn

It does appear that there is a problem with the BRI. If you post the output of show isdn status it might help to confirm this.

HTH

Rick

New Member

Re: strange **ERROR** on isdn

Hi Rick,

Thanks,

Here is the output you requested.

C

Access to this computer system is restricted to authorised personnel only.

Terminate this session immediately if this system has been accessed in error.

You are warned

a) that unautherised access to or modification of information held in this

computer system, and/or

b) unauthorised copying of software, will render you liable to civil damages

and/or criminal penalties in Australia and other countries; and

c) that all sessions on this computer system are monitored, logged and

recorded.

By continuing with this session you represent and warrent that you are

authorised to access this computer system.

Contact a member of CSC Network and Comms in Australia on

+61-(0)8-9420-3090 if you need assistance with your host.

User Access Verification

Username: peterc

rtph101>en

Password:

rtph101#show isdn status

Global ISDN Switchtype = basic-net3

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-net3

Layer 1 Status:

DEACTIVATED

Layer 2 Status:

Layer 2 NOT Activated

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0

rtph101#term mon

rtph101#show ip int brief | include Dialer1

Dialer1 10.162.0.5 YES NVRAM up up

rtph101#ping 10.62.0.6

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.62.0.6, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

rtph101#show isdn status

Global ISDN Switchtype = basic-net3

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-net3

Layer 1 Status:

DEACTIVATED

Layer 2 Status:

Layer 2 NOT Activated

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x80000003

--More--

Layer1 does not come up.

New Member

Re: strange **ERROR** on isdn

Hi all,

Show dialer output:

Jun 26 08:26:30 WAST: BR0/0 DDR: rotor dialout [best] least recent failure is al

so most recent failure

Jun 26 08:26:30 WAST: BR0/0 DDR: rotor dialout [best] also has most recent failu

re

Jun 26 08:26:30 WAST: BR0/0 DDR: rotor dialout [best]

Jun 26 08:26:30 WAST: BR0/0 DDR: Dialing cause ip (s=10.162.0.5, d=10.162.0.6)

Jun 26 08:26:30 WAST: BR0/0 DDR: Attempting to dial 0894279500.....

Success rate is 0 percent (0/5)

rtph101#

Jun 26 08:27:00 WAST: BRI0/0: wait for isdn carrier timeout, call id=0x8032

Jun 26 08:27:00 WAST: DDR: Dialing failed, 5 packets unqueued and discarded

Hall of Fame Super Silver

Re: strange **ERROR** on isdn

Thanks for posting this information that I asked about. The show isdn status confirms that you have some issue with the ISDN connection:

Layer 1 Status:

DEACTIVATED

There are several things that might produce the layer 1 status of deactivated. I would suggest that you check to verify that the cable connecting the router to the ISDN circuit is well connected. You might also try swapping the cable to see if there is a cable problem. You might check with the provider to see if they have a problem and to check out the ISDN wiring.

HTH

Rick

New Member

Re: strange **ERROR** on isdn

Hi,

Please try to do one thing if your ISDN is workin.

Can you place a call command on the router to call your number just to verify if the ISDN line is working. beside Rick suggestions obviously says that there's something wrong with your ISDN connection. It might be a cable or the ISDN card.

here's the command

isdn call interface bri "x" "any number" speed xx

where x - your routers bri interface

any number - try your mobile phone or office phone.

speed - can place 56 or 64

From this you will know if your ISDN is really active.

Thanks

Jeric

New Member

Re: strange **ERROR** on isdn

Hi Jeric,

no good mate.

rtph101#term mon

rtph101#isdn test call interface bri 0/0 0894279500

rtph101#

i think i will try and configure the bri for the old legacy ddr tomorrow and see if i can get something working that way.

thanks anyway

New Member

Re: strange **ERROR** on isdn

I think this will probably confuse the issue, but I also get the same ISDN error message.

I have replaced a 1600 with an 1800 router. I have ISDN backup configured. The 1600 dials and connects fine. The 1800 gets the same message, and the central router reports no attemped connection.

ISDN BR0/1/0 **ERROR**: CCBRI_Go: NO CCB Src->HOST call id 0x800C, event 0x5 ces 1

Any ideas would be greatly appreciated as I have 4 more sites to swap out.

Could it be something with the Australian ISDN implementation???

New Member

Re: strange **ERROR** on isdn

Hi and thank you so much for sharing that. I have this problem on a number of routers and was starting to think i was going right around the bend. This problem must be caused by something.... :)

New Member

Re: strange **ERROR** on isdn

Alalli,

Have you been able to get any resolution to this problem?

I have just discovered (via my Telstra bill) that the ISDN has been dialing every 1-2 seconds for a month and I now have a $60,000 bill to deal with. I even had the BRI interface in a shutdown state for most of this time, and it was still dialing. Be very careful.

New Member

Re: strange **ERROR** on isdn

Hi there,

i am facing the same problem with a new 1841 router

layer1 remains deactivated

and the same **ERROR**: CCBRI_Go: NO CCB Src->HOST still comes up

i will appreciate any feedback if you reached a solution

regards

New Member

Re: strange **ERROR** on isdn

Hi Elie,

My situation was different than yours in that mine started working when we replaced the BRI port.

The one thing you could check is if you have a new version Bri card or an old one. It does seem to make a difference.

You can check the version of the card by issuing a show controller command.

I have found that sometimes there are problems with version 1 cards in a new router and version 3 cards in an old router.

I think that cisco say they all work together; but I am not so sure. Telstra have changed the way they do signalling now as well so the cards have to communicate correctly with the NTU.

If you are having the same problem I was having.... you will see that the router was not releasing the BRI port after the call was over. As far as the Telstra NTU was concerned.... the router still had the call. To check, you could issue a clear bri command after one successful call and then make another call immediately. If the second call makes it through, then it sounds like you have the same problem.

hope this helps!!!

a

New Member

Re: strange **ERROR** on isdn

Hi Al,

Thanks for your reply,

I downgraded the IOS from 12.4 c1841-ipbase-mz.124-1c.bin to 12.3 c1841-ipbase-mz.123-8.T5.bin that i got from a working router and it worked.

I suppose it is a bug in 12.4

regards

Elie

New Member

Re: strange **ERROR** on isdn

Hi Alalli,

I think you issue a wrong command.

try this

isdn call interface bri 0/0 "0894279500" speed 64

other way, ddr will do as well.

we just want to figure out if your router can actually place a call.

Regards

Jeric

New Member

Re: strange **ERROR** on isdn

my router would not accept that syntax. it did accept the syntax i used.

New Member

Re: strange **ERROR** on isdn

Oopss my fault. the command that I quoted is no longer supported on ios 12.2,

forget about it and do as what you think,configure ddr.

thanks

324
Views
34
Helpful
26
Replies
CreatePlease to create content