Re: [asterisk-users] PRI span problem - no D channel
I checked, it made sense. But it isnt it :-) The fourth span is commented out, but the third one isnt (and shouldn't be since it's active). Thanks for the tip though, could have easily been this. Mike > -Original Message- > From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users- > boun...@lists.digium.com] On Behalf Of A J Stiles > Sent: Thursday, June 24, 2010 6:24 > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] PRI span problem - no D channel > > 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 > > -- > _ > -- 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 -- _ -- 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
Re: [asterisk-users] PRI span problem - no D channel
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 -- _ -- 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
Re: [asterisk-users] PRI span problem - no D channel
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-boun...@lists.digium.com [mailto:asterisk-users- > boun...@lists.digium.com] On Behalf Of Tzafrir Cohen > Sent: Wednesday, June 23, 2010 3:09 > To: asterisk-users@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 > >
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_LI
Re: [asterisk-users] PRI span problem - no D channel
there is a link, maybe it can help you, please refer it http://bbs.openvox.cn/viewthread.php?tid=263&extra=page%3D4 2010/6/23 Mike > Same as the other spans coming out of the same MUX! > > signalling = pri_cpe > > > > I got 2 spans working fine from the same MUX. This one isn't working for > some reason. > > > > The all have similar configs, except where I need to change channel number > and primary channel number. > > > > Mike > > > > > > > > *From:* asterisk-users-boun...@lists.digium.com [mailto: > asterisk-users-boun...@lists.digium.com] *On Behalf Of *liuxin > *Sent:* Wednesday, June 23, 2010 1:47 > > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > *Subject:* Re: [asterisk-users] PRI span problem - no D channel > > > > what is the value of signalling in the file > /etc/asterisk/dahdi-channles.conf ? > > 2010/6/23 Mike > > I thought the same, but the cable is in and the light is green. > > > > Mike > > > > > > *From:* asterisk-users-boun...@lists.digium.com [mailto: > asterisk-users-boun...@lists.digium.com] *On Behalf Of *liuxin > *Sent:* Tuesday, June 22, 2010 22:05 > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > *Subject:* Re: [asterisk-users] PRI span problem - no D channel > > > > 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 > > 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 >
Re: [asterisk-users] PRI span problem - no D channel
Same as the other spans coming out of the same MUX! signalling = pri_cpe I got 2 spans working fine from the same MUX. This one isn't working for some reason. The all have similar configs, except where I need to change channel number and primary channel number. Mike From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of liuxin Sent: Wednesday, June 23, 2010 1:47 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] PRI span problem - no D channel what is the value of signalling in the file /etc/asterisk/dahdi-channles.conf ? 2010/6/23 Mike I thought the same, but the cable is in and the light is green. Mike From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of liuxin Sent: Tuesday, June 22, 2010 22:05 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] PRI span problem - no D channel 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 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 E
Re: [asterisk-users] PRI span problem - no D channel
what is the value of signalling in the file /etc/asterisk/dahdi-channles.conf ? 2010/6/23 Mike > I thought the same, but the cable is in and the light is green. > > > > Mike > > > > > > *From:* asterisk-users-boun...@lists.digium.com [mailto: > asterisk-users-boun...@lists.digium.com] *On Behalf Of *liuxin > *Sent:* Tuesday, June 22, 2010 22:05 > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > *Subject:* Re: [asterisk-users] PRI span problem - no D channel > > > > 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 > > 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 > > Sendin
Re: [asterisk-users] PRI span problem - no D channel
I thought the same, but the cable is in and the light is green. Mike From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of liuxin Sent: Tuesday, June 22, 2010 22:05 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] PRI span problem - no D channel 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 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_CONN
Re: [asterisk-users] PRI span problem - no D channel
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 > 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 f
[asterisk-users] PRI span problem - no D channel
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 -
