Please help - I'm stuck


#1

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


#2

This is a known bug in RH and not in Zaptel. Were waiting for an update from RH.


#3

Thanks for the reply, however the question is still not aswered. Please help!

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?

Regards

CW


#4

Also, ZTdummy status is UNCONFIGURED - any idea how to fix this please?


#5

If you have a Digium card in your machine, you don’t need to load ztdummy. That’s only required when you don’t actually have any Zaptel hardware.


#6

iirc, you can look at the contents of /etc/rc.d/init.d/zaptel and /etc/sysconfig/zaptel for module loading order.


#7

Thanks for all your responses. How do I change the order of my spans? I want the E1 to be on span 1 and the other card to be span2. When I run the zttool it clearly is the other way around!

Regards

CW


#8

is this still the case when you change module loading order ? have you confirmed the order now ?


#9

Thanks for your help. Yes, the loading order of the modules is correct, but it is still showing the wrong way around in zztool…

Span 1: TDM400P
Span 2: TE110P

In /etc/sysconfig/zaptel I load

MODULES="$MODULES wct1xxp"

FIRST

and

MODULES="$MODULES wcfxs"

SECOND

Any ideas, please?

Regards

CW


#10

without wanting to bang on about it, if the documentation says it’s down to module loading order, and it’s still the wrong way around, are you sure the modules are being loaded in that order ?

what does /var/log/messages contain for the module load ?


#11

Thanks for all your help. Eventually I took out all the cards and inserted only the E1, booted and configured the card - got it working on span 1… Then inserted the other card, and voila - sorted.

Thanks again!

CW


#12

Hi

Just to throw a fly in the ointment.

You do realise that you are using the wrong driver for your TE110 card. This seems a very common problem and for some reason has never been fixed in AAH. The TE110P has its own driver. and the wct1xxp is for the old T100p
Details of the wct drivers and related cards

wct1xxp		T100P - Single Span T1 Card
		     E100P - Single Span E1 Card

wcte11xp	TE110P - Single Span T1/E1 Card

the wct1xxp does work but as with all things it best to use the correct driver.

[/code]