SOLVED TDM400P - FXS no dial tone

[Mashman]

I am having problem to setup my TDM400P. The card has 1-FXO(channel 1) and 2 FXS Channel 2 and 3)

I have made the setup according to the following guide: freepbx.org/support/documentation/administration-guide/interfacing-to-a-pstn

Unfortunatly, I don’t get a dial tone on the FXS 2 and 3. Any help is appreciated.

Thanks

Here are my config files




root@pbx:~ $ ztcfg -vvv

Zaptel Version: 1.4.5.1
Echo Canceller: MG2
Configuration
======================


Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Slaves: 02)
Channel 03: FXO Kewlstart (Default) (Slaves: 03)

3 channels configured.



/etc/asterisk/zapata.conf
;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks


usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
faxdetect=incoming

;faxdetect=outgoing
;faxdetect=no

;Include genzaptelconf configs
#include zapata-auto.conf

;Include AMP configs
#include zapata_additional.conf



/etc/asterisk/zapata-auto.conf



callerid=asreceived

; Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1"
signalling=fxs_ks
; Note: this is a trunk. Create a ZAP trunk in AMP for Channel 1
context=from-zaptel
group=0
channel => 1

signalling=fxo_ks
; Note: this is an extension. Create a ZAP extension in AMP for Channel 2
context=from-internal
group=1
channel => 2

signalling=fxo_ks
; Note: this is an extension. Create a ZAP extension in AMP for Channel 3
context=from-internal
group=1
channel => 3

; channel 4, WCTDM, inactive.



/etc/asterisk/zapata_additional.conf

; do not edit this file, this is an auto-generated file by freepbx
; all modifications must be done from the web gui

;;;;;;[2102]
signalling=fxo_ks
record_out=Adhoc
record_in=Adhoc
mailbox=2102@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=yes
dial=ZAP/2
context=from-internal
callprogress=no
callerid=device <2102>
busydetect=no
busycount=7
accountcode=
channel=>2

;;;;;;[2103]
signalling=fxo_ks
record_out=Adhoc
record_in=Adhoc
mailbox=2103@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=yes
dial=ZAP/3
context=from-internal
callprogress=no
callerid=device <2103>
busydetect=no
busycount=7
accountcode=
channel=>3

 

[darmock]

Silly question is the tdm card plugged into the power supply via the extra 4 pin connector on the tdm card. I had a similar problem and had forgotten to plug it in

Tom

 

[Mashman]

Yes the power is pluged into the card. I have green lights for the first 3 modules. when the phone is off-hoock and dial a number, I get a tone when I press any digits.

thanks

 

[Titanous]

I had exactly the same issue every time I rebooted.
Try doing

/etc/init.d/zaptel restart
amportal restart

From the shell.

If that doesn't work, do you have them configured in FreePBX?

 

[Mashman]

Bingo! it work! But when I do a reboot, I get the same problem untill I execute the zaptel and amportal restart.

Is there a way to resolve this issue?

I have tried to do a genzaptelconf again, but it does the same thing... need to do a restart on zaptel after the reeboot

Thanks!

 

[drink@home]

tdm400 not working after reboot

The problem is a missing link in the /etc/rc.d/rc3.d directory.
Fix it by logging in as root.
Then type:
chkconfig zaptel on
and press enter.
The system returns to the prompt.
type:
shutdown now -r
to restart. Watch for the zaptel drivers to load during startup. It should work after a reboot now.

 

[Mashman]

Resolved!

Yeah! The issue is resolved!

Thanks

 

[tiggerpaws]

it did not work for me, how come it says no such file or directory?

 

[rossiv]

it did not work for me, how come it says no such file or directory?

This is from 2007. There have been MANY changes since then, namely the switch in naming from 'Zaptel' to 'Dahdi'.