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 -- 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 -- 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! Any clue, anyone? Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100622/53a2171a/attachment-0001.htm
Hi, * [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!* The error means that when it tried using the D channel 72 it was not able to communicate. Probably a misconfiguration or you havent plugged the cable in yet. liu xin 2010/6/22 Mike <list at net-wall.com>> 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 > > -- 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 > > -- 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! > > > > > > > > Any clue, anyone? > > > > Mike > > -- > _____________________________________________________________________ > -- 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 >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100623/3532d7d2/attachment.htm
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 ExtendedAll 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
On Tuesday 22 Jun 2010, 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!I was getting something similar and it turned out to be because a *different* span was configured in chan_dahdi.conf, but not connected to anything. Make sure, if you're only using 3 of the 4 spans, that all lines relating to the unused one are commented out in /etc/asterisk/chan_dahdi.conf (and maybe in /etc/dahdi/system.conf as well). I'm guessing this is due to a change in default behaviour between libpri or DAHDI versions (since an older install worked just fine with "broken" configs). -- AJS