[asterisk-users] PRI span problem - no D channel

[Mike]

Thanks for taking a look.  I am using the latest 1.4.33.1 source packages,
(latest libpri, latest dahdi) as of yesterday.

The link is definitely not down, but since this is delivered via DS3 with a
MUX I assume that only means that the wire from the MUX to the Digium card
is ok, but says nothing about the DS3 timelsot.

Since it worked fine prior to a reboot (after which, I assume, the dahdi
services jumped from some old version to the newest one I had) I hesitate to
blame my provider, but I've opened a ticket with them just in case.

Mike


> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-
> bounces at lists.digium.com] On Behalf Of Tzafrir Cohen
> Sent: Wednesday, June 23, 2010 3:09
> To: asterisk-users at lists.digium.com
> Subject: Re: [asterisk-users] PRI span problem - no D channel
> 
> On Tue, Jun 22, 2010 at 09:30:39AM -0400, Mike wrote:
> > Hi,
> >
> >
> >
> > I have the following happen to me after the restart of one of my
servers:
> > out of my 3 PRIs (all configured with the same technical settings), the
> last
> > one isn't coming back.  It's underutilized (chances it didn't get a call
> > since my reboot), if it makes a difference .
> >
> >
> >
> > The PRI goes from provisioned to unprovisioned, and I get this
regularly:
> >
> > [Jun 22 09:03:48] WARNING[30723]: chan_dahdi.c:2790 pri_find_dchan: No
> > D-channels available!  Using Primary channel 72 as D-channel anyway!
> >
> >
> >
> > Here is my PRI debug span:
> >
> >
> >
> > -- Timeout occured, restarting PRI
> >
> > q921.c:468 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > q921.c:211 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
> >
> > [Jun 22 09:03:48] WARNING[30723]: chan_dahdi.c:2790 pri_find_dchan: No
> > D-channels available!  Using Primary channel 72 as D-channel anyway!
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> 
> All the above messages lead me to suspect there's no active D-channel.
> But,
> 
> >
> > -- Got SABME from network peer.
> 
> A certain message has managed to get through from the remote party.
> Layer 1 can't be completely down.
> 
> What version of Asterisk is it? What version of libpri?
> 
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > -- Got SABME from network peer.
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > -- Got SABME from network peer.
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > -- Got SABME from network peer.
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > -- Timeout occured, restarting PRI
> >
> > q921.c:468 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > q921.c:211 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
> >
> > [Jun 22 09:04:19] WARNING[30723]: chan_dahdi.c:2790 pri_find_dchan: No
> > D-channels available!  Using Primary channel 72 as D-channel anyway!
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > Sending Set Asynchronous Balanced Mode Extended
> >
> > -- Got SABME from network peer.
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > -- Got SABME from network peer.
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > -- Got SABME from network peer.
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > -- Got SABME from network peer.
> >
> > Sending Unnumbered Acknowledgement
> >
> > q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
> >
> > q921.c:805 q921_dchannel_up: q921_state now is
> > Q921_LINK_CONNECTION_ESTABLISHED
> >
> > edison*CLI> pri no debug span 3
> >
> > Disabled debugging on span 3
> >
> >  [Jun 22 09:04:51] WARNING[30723]: chan_dahdi.c:2790 pri_find_dchan: No
> > D-channels available!  Using Primary channel 72 as D-channel anyway!
> 
> --
>                Tzafrir Cohen
> icq#16849755              jabber:tzafrir.cohen at xorcom.com
> +972-50-7952406           mailto:tzafrir.cohen at xorcom.com
> http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>                http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users