Asterisk 2.8 won't accept incoming calls-No Zaptel Channels


#1

I’m setting up a PBX system behind a company-wide PBX (I have a single extension coming into an X100P). Now I have some extensions already up and running. Using the Linsys PAP2T and X-Lite, I have all my internal extensions working perfectly. However, when I call into the system, it just rings.

So I run /sbin/ztcfg -vvvv I get a message stating “0 Channels Configured”. When I run genzaptelconf, I get

Chan Extension Context Language MusicOnHold
pseudo from-zaptel en

From all indications, the card itself is working. In FreePBX (2.2.0beta1), I have an incoming route set for Zaptel Channel 1 to go to my extension, but that doesn’t do anything.

Whenever I add “channel => 1” to my zapata.conf, Asterisk just refuses to restart. In the log: Jun 8 14:30:17 WARNING[14248] chan_zap.c: Unable to specify channel 1: No such device or address

Config is below - any ideas are appreciated. Thanks!

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
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

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

group=1

;Include AMP configs
#include zapata_additional.conf

zapata-auto.conf

; Autogenerated by /usr/local/sbin/genzaptelconf – do not hand edit
; Zaptel Channels Configurations (zapata.conf)

callerid=asreceived

; Span 1: ZTDUMMY/1 “ZTDUMMY/1 1”

=====


#2

Are you sure that the kernel can recongize the X100P. It seems the system did find the hardware card. Please check ‘dmesg’ record to ensure the card had been identified.