[Asterisk-bsd] T100P PRI with Zaptel-BSD
Kevin - Your.Org
kevin at your.org
Sun Sep 30 16:20:32 CDT 2007
I'm not sure if this really is the right list for this question or
not, so apologies if I'm in the wrong place...
Does anyone have a T100P working as a PRI with Asterisk on FreeBSD?
I took a box/configuration that was working under Linux, reinstalled
FreeBSD 6.2 on the same server, and I'm having trouble bringing the
PRI up now.
zttool shows the span is up, no alarms. ztcfg shows:
Keyword: [loadzone], Value: [us]
Keyword: [defaultzone], Value: [us]
Keyword: [span], Value: [1,1,0,esf,b8zs]
Keyword: [bchan], Value: [1-23]
Keyword: [dchan], Value: [24]
Zaptel Version: 1.4.0-BSD
Echo Canceller: MG2
Configuration
======================
SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Channel map:
Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: Clear channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Clear channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08)
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: Clear channel (Default) (Slaves: 12)
Channel 13: Clear channel (Default) (Slaves: 13)
Channel 14: Clear channel (Default) (Slaves: 14)
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: Clear channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
Channel 18: Clear channel (Default) (Slaves: 18)
Channel 19: Clear channel (Default) (Slaves: 19)
Channel 20: Clear channel (Default) (Slaves: 20)
Channel 21: Clear channel (Default) (Slaves: 21)
Channel 22: Clear channel (Default) (Slaves: 22)
Channel 23: Clear channel (Default) (Slaves: 23)
Channel 24: D-channel (Default) (Slaves: 24)
24 channels configured.
Most of the time when I start asterisk up, I just get "Sending Set
Asynchronous Balanced Mode Extended" repeated over and over again.
Occasionally it looks like it's starting to bring the D channel up:
-- 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
-- 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
-- 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
-- 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
-- Timeout occured, restarting PRI
q921.c:375 t200_expire: 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
[Sep 30 14:55:19] WARNING[1287]: chan_zap.c:2394 pri_find_dchan: No D-
channels available! Using Primary channel 24 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
But it never gets any further than that. Anyone seen this before? The
exact same zaptel.conf and zapata.conf under an older version in
Linux worked fine, so I think my config is mostly correct. This is
looking more like a driver/hardware issue, maybe? This is now
running 1.4.0 from the zaptel-bsd port, and 1.4.11 of Asterisk also
from ports(with the zaptel option checked), under 6.2-RELEASE.
-- Kevin
More information about the Asterisk-BSD
mailing list