Are you sure that the 2 spans that you pulled over from the linux box
have a D channel on them?
Maybe they are part of a trunk group? IE There are 3 PRI's but only
one of them has a D channel?
Could just be the driver is buggy.
Maybe try a PRI debug or PRI intense debug.
-bill
On 16-Aug-05, at 5:16 PM, Chris St Denis wrote:
(sending this again in the hope that this time somebody will be
able to help)
I recently tried adding more PRI lines to my PSTN gateway server
running FreeBSD 5.3-RELEASE-p10 with a TE410P digium card. The one
PRI has been on it for a few months and seems to work fine, but it
would not take the other 2 but got some odd errors. Any ideas?
These 2 PRI came from another active production server (a Linux
server) that works fine so I know the lines themselves aren't the
problem.
Span 2 was showing a red alarm which I could seem to get rid of.
Even with it unplugged and turned off the red alarm stayed (and it
now also on span3 with just the span1 in and enabled). Even when
just span2 had the red alarm, I couldn't get span3 or 4 to work
either (same errors).
=== Asterisk Error Log ===
Aug 9 01:08:51 WARNING[776]: No D-channels available! Using
Primary on channel anyway 24!
Aug 9 01:08:57 WARNING[776]: PRI: !! Unexpected Channel selection 0
Aug 9 01:09:32 ERROR[799]: Unable to open D-channel 72 (Device busy)
Aug 9 01:09:32 ERROR[799]: Unable to start D-channel on span 3
Aug 9 01:09:32 WARNING[799]: chan_zap.so: load_module failed,
returning -1
Aug 9 01:09:32 WARNING[799]: Loading module chan_zap.so failed!
Aug 9 01:10:02 WARNING[817]: PRI: !! Unexpected Channel selection 0
Aug 9 01:14:11 ERROR[450]: Unable to open D-channel 48 (Device busy)
Aug 9 01:14:11 ERROR[450]: Unable to start D-channel on span 2
Aug 9 01:14:11 WARNING[450]: chan_zap.so: load_module failed,
returning -1
Aug 9 01:14:11 WARNING[450]: Loading module chan_zap.so failed!
Aug 9 01:17:02 ERROR[536]: Unable to open D-channel 72 (Device busy)
Aug 9 01:17:02 ERROR[536]: Unable to start D-channel on span 3
Aug 9 01:17:02 WARNING[536]: chan_zap.so: load_module failed,
returning -1
Aug 9 01:17:02 WARNING[536]: Loading module chan_zap.so failed!
Aug 9 01:19:35 ERROR[448]: Unable to open D-channel 72 (Device busy)
Aug 9 01:19:35 ERROR[448]: Unable to start D-channel on span 3
Aug 9 01:19:35 WARNING[448]: chan_zap.so: load_module failed,
returning -1
Aug 9 01:19:35 WARNING[448]: Loading module chan_zap.so failed!
Aug 9 01:21:58 WARNING[528]: PRI: !! Unexpected Channel selection 0
=== /usr/local/etc/zaptel.conf ===
# Several variations in here were tried as I tried different
combinations
# (like span 1 and 3) but here is what it looked like with spans
1-3 enabled.
# This is a ZAP interface file
span=1,0,0,esf,b8zs
span=2,0,0,esf,b8zs
span=3,0,0,esf,b8zs
bchan=1-23,25-47,49-71
dchan=24,48,72
loadzone=us
defaultzone=us
=== /usr/local/etc/asterisk/zapata.conf ===
; All that changed here was more of the channel lines
[channels]
busydetect=1
busycount=7
relaxdtmf=yes
;callreturn=yes
callwaiting=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
usecallerid=yes
echocancel=yes
echocancelwhenbridged=yes
;echotraining=yes ;800
rxgain=0.0
txgain=0.0
immediate=no
callerid=asreceived
context=pstn-in
signalling=pri_cpe
group=1
channel => 1-23
channel => 25-47
channel => 49-71
=== Software Versions ===
zaptel-0.10
libpri-1.0.9
asterisk-1.0.9_1
=== Part of /var/log/messages ===
Aug 9 01:19:34 gateway2 kernel: Zapata Telephony Interface
Registered on major 196
Aug 9 01:19:34 gateway2 kernel: wct4xxp0: <Wildcard TE405/410P
Xilinx> mem 0xfebfec00-0xfebfec7f irq 20 at device 5.0 on pci0
Aug 9 01:19:34 gateway2 kernel: wct4xxp0: [GIANT-LOCKED]
Aug 9 01:19:34 gateway2 kernel: TE410P version c01a009b
Aug 9 01:19:34 gateway2 kernel: FALC version: 00000005, Board ID: 00
Aug 9 01:19:34 gateway2 kernel: TE410P: Launching card: 0
Aug 9 01:19:34 gateway2 kernel: TE410P: Setting up global serial
parameters for unit 0
Aug 9 01:19:34 gateway2 kernel: Registered tone zone 0 (United
States / North America)
Aug 9 01:19:34 gateway2 kernel: TE410P: Span 1 configured for ESF/
B8ZS
Aug 9 01:19:34 gateway2 kernel: TE410P: Span 2 configured for ESF/
B8ZS
Aug 9 01:19:34 gateway2 kernel: TE410P: Span 3 configured for ESF/
B8ZS
Aug 9 01:19:34 gateway2 kernel: wct4xxp: Setting yellow alarm on
span 1
Aug 9 01:19:34 gateway2 kernel: wct4xxp: Setting yellow alarm on
span 2
Aug 9 01:19:34 gateway2 kernel: wct4xxp: Setting yellow alarm on
span 3
Aug 9 01:19:39 gateway2 kernel: wct4xxp: Clearing yellow alarm on
span 1
Aug 9 01:19:39 gateway2 kernel: wct4xxp: Clearing yellow alarm on
span 3
_______________________________________________
Asterisk-BSD mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
_______________________________________________
Asterisk-BSD mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
