asterisk users - Mar 2005 - zaptel configuration issues (zaptel.conf vs. zapata.conf)

Feel free to hit me with a cluestick; maybe it will jar something lose...

I'm running a stock *@home 0.6 install and after four days of
excrutiatingly annoying debugging, I finally came across the obvious
problem. The zaptel driver is reading /etc/zaptel.conf; which by
default configures one FXS Kewlstart channel. Asterisk, according to
"full" log, will see the first channel, then fail to load chan_zap.so
and not configure channels 2 through 4 (I have a TDM400p card in the
box...at least I think that's what it is)

AMP has three "zapata" configuration files in /etc/asterisk. My
question is: which is which and how do I get them to all harmonize so
this damn thing works, once and for all? I tried putting an #include
statement in /etc/zaptel.conf for sh*ts and giggles to no avail.

I'm sorry if I missed something obvious when reading the wiki or
example configuration files I've found on the net. I'm not a phone
person at all (though this does seem so very very easy, which makes
this so very very frustrating) and everyone question I've had so far
was easily answered somewhere, in some document.

TIA for any and all help

Regards,
aaron.glenn

did you try the auto-config?

--- Aaron Glenn <aaron.glenn@gmail.com> wrote:
> Feel free to hit me with a cluestick; maybe it will
> jar something lose...
> 
> I'm running a stock *@home 0.6 install and after
> four days of
> excrutiatingly annoying debugging, I finally came
> across the obvious
> problem. The zaptel driver is reading
> /etc/zaptel.conf; which by
> default configures one FXS Kewlstart channel.
> Asterisk, according to
> "full" log, will see the first channel, then fail to
> load chan_zap.so
> and not configure channels 2 through 4 (I have a
> TDM400p card in the
> box...at least I think that's what it is)
> 
> AMP has three "zapata" configuration files in
> /etc/asterisk. My
> question is: which is which and how do I get them to
> all harmonize so
> this damn thing works, once and for all? I tried
> putting an #include
> statement in /etc/zaptel.conf for sh*ts and giggles
> to no avail.
> 
> I'm sorry if I missed something obvious when reading
> the wiki or
> example configuration files I've found on the net.
> I'm not a phone
> person at all (though this does seem so very very
> easy, which makes
> this so very very frustrating) and everyone question
> I've had so far
> was easily answered somewhere, in some document.
> 
> TIA for any and all help
> 
> Regards,
> aaron.glenn
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
>
http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   
>
http://lists.digium.com/mailman/listinfo/asterisk-users
> 

		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Aaron Glenn
> Sent: Wednesday, March 09, 2005 5:25 PM
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] zaptel configuration issues 
> (zaptel.conf vs. zapata.conf)
[snip]
> I'm running a stock *@home 0.6 install and after four days of 
> excrutiatingly annoying debugging, I finally came across the 
> obvious problem. The zaptel driver is reading 
> /etc/zaptel.conf; which by default configures one FXS 
> Kewlstart channel. Asterisk, according to "full" log, will 
> see the first channel, then fail to load chan_zap.so and not 
> configure channels 2 through 4 (I have a TDM400p card in the 
> box...at least I think that's what it is)
[snip]

Aaron,

I just setup a TDM11B (one FXS module on channel 1 and one FXO on
channel 4)

Here is the /etc/zapata.conf that I used with Asterisk@Home 0.6 to get
that working:

fxoks=1
fxsks=4
loadzone = us
defaultzone=us

Then, I replaced /etc/asterisk/zapata.conf with this:

[channels]
language=en
busydetect=yes
busycount=6
cidsignalling=bell
cidstart=ring
callerid=asreceived
busydetect=yes
busycount=6

; this section is for the fxs port (telephone instrument)
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1
immediate=no
signalling => fxo_ks
channel => 1

; this section is for the fxo port (pstn line)
context=from-pstn       ; <==== where to send incoming calls within
extensions.conf
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
threewaycalling=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echotraining=800
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1
immediate=no
signalling => fxs_ks
channel => 4

Now, I think that AAH, via AMP, overwrites /etc/asterisk/zapata.conf and
that maybe one ought to place all custom changes to in the
/etc/asterisk/zapata-channels.conf file. Frankly, though, this is all
supposition and my setup is currently working for me using the
/etc/asterisk/zapata.conf file.

FYI, for me the genzaptelconf command is not working to correctly set up
my TDM11B

HTH,

Tom