[Asterisk-Users] Problem with a TDM-400P

Nigel Smith nige4subs at fea.st
Wed Apr 26 17:35:51 MST 2006


(Sorry of this appears in the list twice, but I wasn't sure if it was
blocked or not)

Hi there,

I'm having a problem with my TDM-400P which has been working like a
charm up until very recently. It started to fail last week, and so I was
hoping someone could illuminate me with some information as to why.  Its
configuration is as follows:

------------
FXS (green) module is in position 1, closest to the bracket. This
appears to be the failing component.
FXO (red) module is in position 4, furthest from the bracket
------------

>From what I can gather it's just the FXS module that is failing, and not
the card. What I was hoping someone could tell me is whether the whole
card is U/S or just that module, based on the information I have
provided below. Any help will be greatly appreciated.

Thanks,
Nigel


The interesting parts of the zapata.conf are:
------------------
; The FXS port, or the "phone" port
signalling=fxo_ks
echocancel=yes ; You can set this to 32, 64, or 128, tweak to your needs.
echocancelwhenbridged=yes
echotraining=400 ; Asterisk trains to the beginning of the call, number
is in milliseconds
mailbox=1000 at home
group=1
context=outgoing ; Points to the default context of your extensions.conf
channel => 1
usecallerid=no
;cidsignalling=bell
;cidstart=ring
;hidecallerid=no
callwaiting=yes


; The FXO port, or the "line" port
signalling=fxs_ks
group=2
;rxwink=300              ; Atlas seems to use long (250ms) winks
;hanguponpolarityswitch ; doesn't work on ADSL lines
busydetect=yes
busycount=3
context=incoming-pstn
channel=> 4 ; Again change the 'X' to the number of FXO modules you have
usedistinctiveringdetection=no
usecallerid=no
;sendcalleridafter=2
;cidsignalling=bell
;cidstart=ring
;hidecallerid=no
;restrictcid=no
callwaiting=yes
--------------------

The asterisk failure is
-------------
Apr 27 10:00:46 splash asterisk[14625]: WARNING[14625]: chan_zap.c:923
in zt_open: Unable to specify channel 1: No such device
Apr 27 10:00:46 splash asterisk[14625]: ERROR[14625]: chan_zap.c:6878 in
mkintf: Unable to open channel 1: No such device here = 0, tmp->channel
= 1, channel = 1
Apr 27 10:00:46 splash asterisk[14625]: ERROR[14625]: chan_zap.c:10314
in setup_zap: Unable to register channel '1'
Apr 27 10:00:46 splash asterisk[14625]: WARNING[14625]: loader.c:414 in
__load_resource: chan_zap.so: load_module failed, returning -1
Apr 27 10:00:46 splash asterisk[14625]: WARNING[14625]: loader.c:554 in
load_modules: Loading module chan_zap.so failed!
----------------
And asterisk promptly dies.

If I execute the following:
------------
#  ztcfg -vvvvvv

Zaptel Configuration
======================


Channel map:

Channel 01: FXO Kewlstart (Default) (Slaves: 01)
Channel 04: FXS Kewlstart (Default) (Slaves: 04)

2 channels configured.
----------
You can see that the channels are configured OK.

And the output from the following commands is a little strange as well:
-------------
# cat /dev/zap/1
cat: /dev/zap/1: No such device
# cat /dev/zap/2
cat: /dev/zap/2: No such device or address
# cat /dev/zap/3
cat: /dev/zap/3: No such device or address
# cat /dev/zap/4
(And lots of stuff gets spewed out onto the screen)
--------------






More information about the asterisk-users mailing list