search for: q921_state

...es 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!...

...-ethmf module. My interface is a RedFone foneBridge2 4 Span; and I'm connecting to a BT E1 PRI / ISDN30e with 15 lines on span 1, and a legacy Panasonic PBX on span 4. Upon connection of the E1 I get the following in pri debug span 1: Sending Unnumbered Acknowledgement q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:664 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:664 q921_dchannel_up: q921_state now...

...ing Set Asynchronous Balanced Mode Extended Sending Set Asynchronous Balanced Mode Extended Periodically I see: Sending Set Asynchronous Balanced Mode Extended Sending Set Asynchronous Balanced Mode Extended -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:664 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED == Primary D-Channel on span 1 up -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:...

...ABME from network peer. Sending Unnumbered Acknowledgement > [ 02 01 73 ] > Unnumbered frame: > SAPI: 00 C/R: 1 EA: 0 > TEI: 000 EA: 1 > M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ] > 0 bytes of data -- Restarting T203 counter q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:664 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED -- Restarting T203 counter == Primary D-Channel on span 1 up pri intense debug span 1 < [ 02 01 7f ] < Unnumbered frame: < SAPI: 00 C/R: 1 EA: 0 < TEI: 000 EA...

...0) q931.c:3766 q931_receive: call 32776 on channel 1 enters state 0 (Null) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null -- Got Disconnect from peer. Sending Unnumbered Acknowledgement q921.c:858 q921_reset: 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 -- Got UA from network peer Link up. q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:805 q921_dchannel_up: q921_s...

...that problem is in our box. Fast running zttest give me: --- Results after 279 passes --- Best: 100.000 -- Worst: 99.987 -- Average: 99.994354, Difference: = 99.994368 After enable pri debug span 1 we get -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:782 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:733 q921_dchannel_up: q921_state now is = Q921_LINK_CONNECTION_ESTABLISHED -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:782 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:733 q921_dchannel_up: q921_state no...

...D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- zttest gives me an average of 99.992% and zttool shows no alarms. But every about 3,5 minutes we get this (with "debug span 1" enababled): 1 -- Timeout occured, restarting PRI 1 q921.c:859 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED 1 Sending Set Asynchronous Balanced Mode Extended 1 q921.c:534 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH == Primary D-Channel on span 1 down [Apr 10 12:16:05] WARNING[28541]: chan_zap.c:2498 pri_find_dchan: No D-channels available! Using Prim...

...CE[3772]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 1 [Mar 26 18:39:24] NOTICE[3772]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 2 ... ... See the full output at http://sprunge.us/cdFf I enabled PRI debugging for span 1, which gives this: q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED Sending Set Asynchronous Balanced Mode Extended q921.c:150 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH -- Got UA from network peer Link up. q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:664 q921_dchannel_up: q921_s...

...arm cleared on channel 1 > [Mar 26 18:39:24] NOTICE[3772]: chan_zap.c:6678 handle_init_event: > Alarm cleared on channel 2 > ... > ... > > See the full output at http://sprunge.us/cdFf > > I enabled PRI debugging for span 1, which gives this: > > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > Sending Set Asynchronous Balanced Mode Extended > q921.c:150 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH > -- Got UA from network peer =A0Link up. > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:6...

...arm cleared on channel 1 > [Mar 26 18:39:24] NOTICE[3772]: chan_zap.c:6678 handle_init_event: > Alarm cleared on channel 2 > ... > ... > > See the full output at http://sprunge.us/cdFf > > I enabled PRI debugging for span 1, which gives this: > > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > Sending Set Asynchronous Balanced Mode Extended > q921.c:150 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH > -- Got UA from network peer =A0Link up. > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:6...

...i.c:4385 handle_alarms: Detected alarm on channel 31: Red Alarm<br> [Apr&nbsp; 3 10:44:40] WARNING[21089]: chan_dahdi.c:2012 dahdi_disable_ec: Unable to disable echo cancellation on channel 31: Invalid argument<br> -- Timeout occured, restarting PRI<br> q921.c:438 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED<br> q<b>931.c:4019 q931_dl_indication: link is DOWN</b><br> q931.c:4030 q931_dl_indication: cancel call 1 on channel 1 in state 11 (Disconnect Request)<br> Sending Set Asynchronous Balanced Mode Extended<br> q921.c:211 q921_se...

...rom 10 to (but not including) 12 -- ACKing packet 11, new txqueue is -1 (-1 means empty) -- Since there was nothing left, stopping T200 counter -- Stopping T203 counter since we got an ACK -- Nothing left, starting T203 counter -- Restarting T203 timer q921.c:842 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED I would see the RELEASE message, and then a 'Making new call' indication following which i would see a RELEASE COMPLETE message with ' Invalid call reference value' and then the line resets. Any idea why this would happen..? Thanks sam!!