I've seen this when, for lack of a better term, the AS5300 becomes
"desynchronized" with the phone switch. I've had this happen a lot when you hose
the router for an extended period of time like when you overload the console
with debugging and the router stops temporarily. The telco thinks the PRI/BRI is
in a certain state, your AS5300 thinks it's in a different state. I suppose this
could happen if the power cycle of the router was very rapid.
Shutting down the interface for a minute or so and then turning it back on would
likely deal with the issue.
Jason Young
CNS - Network Design, Anheuser-Busch
(314)577-4597
> -----Original Message-----
> From: Dave VanAuken [mailto:dave@hawk-systems.com]
> Sent: Thursday, May 24, 2001 2:11 PM
> To: cisco-nsp@puck.nether.net
> Cc: Scott Madley; George Robbins
> Subject: RE: serial channels not available = busy signal
> after cold boot
>
>
> The AS5300 was only down for about 5 seconds... he waltzed in, said
> "what does this do" turned it off, then back on... sounds like a bad
> joke doesn't it.
>
> Here is the output from "debug isdn q921" during an attempted call.
> I deleted the NAS config file from below for size consideration, you
> can retrieve it from the previous post if needed.
>
> Greek to me, any ideas?
>
>
> May 24 13:03:07.007: ISDN Se0:23: TX -> RRp sapi = 0 tei = 0 nr = 26
> May 24 13:03:07.015: ISDN Se0:23: RX <- RRf sapi = 0 tei = 0 nr =
> 26
> May 24 13:03:17.015: ISDN Se0:23: TX -> RRp sapi = 0 tei = 0 nr = 26
> May 24 13:03:17.023: ISDN Se0:23: RX <- RRf sapi = 0 tei = 0 nr =
> 26
> May 24 13:03:19.299: ISDN Se0:23: RX <- INFOc sapi = 0 tei = 0 ns =
> 26 nr =
> 26 i =
> 0x080202670504038090A21803A983866C0C218339303537323539303834700BA13930
> 35
> 37323833333839
> May 24 13:03:19.299: ISDN Se0:23: TX -> RRr sapi = 0 tei = 0 nr =
> 27
> May 24 13:03:19.299: %ISDN-6-CHAN_UNAVAILABLE: Interface Se0:23
> Requested Channe
> l 6 is not available
> May 24 13:03:19.303: ISDN Se0:23: TX -> INFOc sapi = 0 tei = 0 ns =
> 26 nr =
> 27 i = 0x080282675A080380AC18
> May 24 13:03:19.311: ISDN Se0:23: RX <- RRr sapi = 0 tei = 0 nr =
> 27
> May 24 13:03:29.311: ISDN Se0:23: TX -> RRp sapi = 0 tei = 0 nr = 27
> May 24 13:03:29.319: ISDN Se0:23: RX <- RRf sapi = 0 tei = 0 nr =
> 27
>
> >-----Original Message-----
> >From: Scott Madley [mailto:scott.madley@cbeyond.net]
> >Sent: Thursday, May 24, 2001 2:46 PM
> >To: George Robbins; cisco-nsp@puck.nether.net; dave@hawk-systems.com
> >Subject: RE: serial channels not available = busy signal
> >after cold boot
> >
> >
> >That is probably what happened. LEC's like to turn circuits
> >down after 20 or
> >so minutes of failure.
> >
> >Do a debug isdn q.921, that will give you the appropriate D
> >channel debug
> >information, and more then likely help you out with
> >determing the root-cause
> >of the problem.
> >
> >-Scott
> >
> >> -----Original Message-----
> >> From: George Robbins [mailto:grr@shandakor.tharsis.com]
> >> Sent: Thursday, May 24, 2001 2:40 PM
> >> To: cisco-nsp@puck.nether.net; dave@hawk-systems.com
> >> Subject: Re: serial channels not available = busy signal
> >> after cold boot
> >>
> >>
> >> Check with the telco to make sure that they didn't turn down the
> >> ISDN BRI interface when there was an apparent circuit problem.
> >>
> >> Check that your t1 controlllers show up and not looped.
> >>
> >> George
> >>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:38 EDT