My tdm400p problems


#1

I just bought a new Digium TDM400p but I got the following errors when the asterisk is starting up:

Oct 17 02:07:30 WARNING[3928]: chan_zap.c:778 zt_open: Unable to specify channel 1: No such device Oct 17 02:07:30 ERROR[3928]: chan_zap.c:6239 mkintf: Unable to open channel 1: No such device here = 0, tmp->channel = 1, channel = 1 Oct 17 02:07:30 ERROR[3928]: chan_zap.c:9191 setup_zap: Unable to register channel '1-2' Oct 17 02:07:30 WARNING[3928]: loader.c:345 ast_load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered channel type 'Tor' == Unregistered channel type 'Zap' Oct 17 02:07:30 WARNING[3928]: loader.c:440 load_modules: Loading module chan_zap.so failed!

the following file is my configuration and logs, could anyone help me to solve this problem ?

dmesg

PCI: Found IRQ 11 for device 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:00:1f.5
Freshmaker version: 73
Freshmaker passed register test
Module 0: Not installed
Module 1: Not installed
Module 2: Installed -- AUTO FXO (FCC mode)
Module 3: Installed -- AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)
Registered tone zone 0 (United States / North America)
application asterisk uses obsolete OSS audio interface

/proc/zaptel/1

Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1"

           1 WCTDM/0/0 FXSKS
           2 WCTDM/0/1 FXSKS
           3 WCTDM/0/2
           4 WCTDM/0/3

/etc/zaptel.conf


fxsks=1-2
defaultzone=us
loadzone=us

/etc/asterisk/zapata.conf


[trunkgroups]
faxdetect=incoming

[channels]
signalling=fxs_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 mill
callerid=asreceived
group=1
context=default ; Points to the default context of your extensions.conf
channel => 1-2 ; Again X is the number of FXO modules you have

[/code]


#2

I’m having a very similar problem. I’m pretty sure that something is wrong with my zapata.conf file. I’ve seen the documentation for the TDM400P cards at digium.com/index.php?menu=configuration, but I must be missing something.

Would someone be willing to post their zapata.conf file with a working TDM400P, Preferable with 4x FXO modules (cause that’s what I’ve got)?


#3

Well looking at dmesg, it looks like the modules are in slots 3 and 4:

Module 0: Not installed
Module 1: Not installed
Module 2: Installed – AUTO FXO (FCC mode)
Module 3: Installed – AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)

But it looks like you are trying to configure slots 1 and 2
/etc/zaptel.conf

fxsks=1-2
defaultzone=us
loadzone=us


#4

[quote=“mismanccc”]I’m having a very similar problem. I’m pretty sure that something is wrong with my zapata.conf file. I’ve seen the documentation for the TDM400P cards at digium.com/index.php?menu=configuration, but I must be missing something.

Would someone be willing to post their zapata.conf file with a working TDM400P, Preferable with 4x FXO modules (cause that’s what I’ve got)?[/quote]

Here ya go…
/etc/asterisk/zapata.conf
[channels]
; These are FXO ports so signal with FXS
signalling=fxs_ks
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes
rxgain=8.1
txgain=-2.5
amaflags=billing
group=0
usecallerid=no
context=incoming
channel=>1-4


#5

I got this problem too. I solved it by force!! My situation is as same as chihuangchiu. I do it by applying the zaptel.conf and zapata.conf and force them to use channel 3&4 instead of 1 or 2. after that i run tcfg and it works back normal again! That’s what i’ve done.


#6

avnho, what you did is not “by force”. As I understand it, that is the proper way to specify things:

Module 0 = Channel 1
Module 1 = Channel 2
Module 2 = Channel 3
Module 3 = Channel 4

Look at the card, see what module numbers are plugged in, configure those channels.


#7

oh! sorry! But before doing that whenever i run ztcfg the ztcfg itself asking me am i using the right config stating wcfxs uses wcfxo and vice versa. My modules are put in slot 3 and 4 but ztcfg still uses slot 1 and 2. I just force it to use 3 and 4 by stating it in zapata.conf and zaptel.conf. Then when i run ztcfg it was working well. So that is my solution. Anyway sorry again for the word force.