Incoming call on POTS not being answered by TDM Card

[RizSher]

Installed TDM400P card with 1FXO/3FXS ports. For some reason, incoming calls to my POTS line don't seem to work. CLI shows:

Starting Zap/1-1 at ,s,1 failed so falling back to exten 's'
== Starting Zap/1-1 at ,s,1 still failed so falling back to context 'default'
-- Executing [s@default:1] Playback("Zap/1-1", "vm-goodbye") in new stack

Zapata.conf:

; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
signalling=fxs_ks
group=0
channel=1
rxwink=300 ; Atlas seems to use long (250ms) winks
usedistinctiveringdetection=yes
immediate=no
usecallerid=yes
callerid=asreceived
ukcallerid=yes
cidsignalling=v23
cidstart=polarity
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=128
rxgain=3.0
txgain=3.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


#include zapata-channels.conf

Can anyone see anything obviously wrong with this?. Btw, if a change is made to zapata.conf, is amportal restart enough to apply those, of genzaptelcon?.

 

[jroper]

can you post the contents of #include zapata-channels.conf

zapata-channels will need to be edited to have the context as from-zaptel

You then need to assign the telephone number of each channel to zapata channels module in FreePBX, Then in inbound routes, you will need an inbound route for each telephone number.

reload chan_zap.so should commit your changes, but an amportal restart is probably safer.

Joe