Any ideas? Sangoma support is closed for the evening. I have the latest Sangoma drivers and Asterisk 1.4 everything installed. When I fire up asterisk, I keep getting "Primary D-Channel on span 1 up" repeated over and over. The B channels never come up. There are no errors in any of the logs, zttool, or the wanpipe tools. Intense pri debug output: < Unnumbered frame: < SAPI: 00 C/R: 1 EA: 0 < TEI: 000 EA: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended ) ] < 0 bytes of data -- Got SABME 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: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended ) ] < 0 bytes of data -- Got SABME 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 < [ 02 01 7f ] < Unnumbered frame: < SAPI: 00 C/R: 1 EA: 0 < TEI: 000 EA: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended ) ] < 0 bytes of data -- Got SABME 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 Thanks, Steve Totaro http://www.asteriskhelpdesk.com KB3OPB
Which CentOS version? You might try, if you have not already the beta wanpipe drivers, they have: Support for 2.6.20 kernels which include CentOS 5 On 6/6/07, Steve Totaro <stotaro@asteriskhelpdesk.com> wrote:> > Any ideas? Sangoma support is closed for the evening. > > I have the latest Sangoma drivers and Asterisk 1.4 everything installed. > > When I fire up asterisk, I keep getting "Primary D-Channel on span 1 up" > repeated over and over. The B channels never come up. There are no > errors in any of the logs, zttool, or the wanpipe tools. > > Intense pri debug output: > < Unnumbered frame: > < SAPI: 00 C/R: 1 EA: 0 > < TEI: 000 EA: 1 > < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode > extended > ) ] > < 0 bytes of data > -- Got SABME 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: 1 > < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode > extended > ) ] > < 0 bytes of data > -- Got SABME 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 > < [ 02 01 7f ] > > < Unnumbered frame: > < SAPI: 00 C/R: 1 EA: 0 > < TEI: 000 EA: 1 > < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode > extended > ) ] > < 0 bytes of data > -- Got SABME 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 > > Thanks, > Steve Totaro > http://www.asteriskhelpdesk.com > KB3OPB > > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- Bruce Reeves Nortex Networks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070606/7f05541f/attachment.htm
Which CentOS version? You might try, if you have not already the beta wanpipe drivers, they have: Support for 2.6.20 kernel s which include CentOS 5 On 6/6/07, Steve Totaro <stotaro@asteriskhelpdesk.com> wrote:> > Any ideas? Sangoma support is closed for the evening. > > I have the latest Sangoma drivers and Asterisk 1.4 everything installed. > > When I fire up asterisk, I keep getting "Primary D-Channel on span 1 up" > repeated over and over. The B channels never come up. There are no > errors in any of the logs, zttool, or the wanpipe tools. > > Intense pri debug output: > < Unnumbered frame: > < SAPI: 00 C/R: 1 EA: 0 > < TEI: 000 EA: 1 > < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode > extended > ) ] > < 0 bytes of data > -- Got SABME 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: 1 > < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode > extended > ) ] > < 0 bytes of data > -- Got SABME 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 > < [ 02 01 7f ] > > < Unnumbered frame: > < SAPI: 00 C/R: 1 EA: 0 > < TEI: 000 EA: 1 > < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode > extended > ) ] > < 0 bytes of data > -- Got SABME 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 > > Thanks, > Steve Totaro > http://www.asteriskhelpdesk.com > KB3OPB > > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- Bruce Reeves Nortex Networks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070606/bf9914e2/attachment.htm
On 6/6/07, Steve Totaro <stotaro@asteriskhelpdesk.com> wrote:> When I fire up asterisk, I keep getting "Primary D-Channel on span 1 up" > repeated over and over. The B channels never come up. There are no > errors in any of the logs, zttool, or the wanpipe tools.This is the number one problem I've had with Sangoma's wanpipe drivers. In the past, I've had to roll back to an earlier version of Zaptel to make it work correctly. I'm not sure if that'll help you in this case, but it's worked in the past for me. -Jared