Hallo there,
I’m rather new to Linux and Asterisk, but I’m learning.
Configuration:
CentOS release 4.3 (Final)
Asterisk 1.2.4
Digium cards:
1 X TE110P (PRI E1)
1 X TDM400P (4 port)
I had everything up and running and user AAH 2.5 to start with. After I’ve done a yum update -y (kernel update) I started to experience problems! First Zap would not been working at all, then I reverted back to Kernel Version 2.6.9-34.EL. At first Asterisk did not start up and after some trying I managed to get Asterisk up and running. Problem is that configuration of the cards changed order. IE I used to have the TE110P as my span 1 and the TDM400P as span 2 and ztdummy as span 3. Now I have the TDM400P as span 1, ztdummy as span 2 and the TE110P as span 3!
1.) According to documentation it has to do with the load order of the modules, how do I change the order?
2.) Why did this happen?
3.) Everytime I reboot the system Kudzu comes up and I have to reconfigure the Digium card?
zaptel.conf:
span=3,0,0,cas,ami,crc4
bchan=5-19,21-35
dchan=20
fxsks=1
fxsks=2
fxsks=3
fxsks=4
loadzone = us
defaultzone = us
zapata.conf
language=en
context=from-pstn
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=incoming
;Include genzaptelconf configs
#include zapata-auto.conf
;Include AMP configs
#include zapata_additional.conf
signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master
switchtype=national
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 milliseconds
callerid=asreceived
group=1
channel => 5-19,21-35
Any help would be greatly appreciated, I’m clueless…
Regards
CW