Zaptel problem

[eliasferreyra]

Hello all..
i hope anybody can helpme.
im installing from scratch on centos 5.5

ViciDial 2.2.1
asterisk-1.4.21.2
zaptel-1.4.12.1
libpri-1.4.9

and when i try to load asterisk asterisk -vvvvgc
i receive this:
Asterisk Event Logger Started /var/log/asterisk/event_log
[Aug 26 10:21:20] ERROR[6242]: asterisk.c:3196 main: Asterisk has detected ablem with your Zaptel configuration and will shutdown for your protection. have options:
1. You only have to compile Zaptel support into Asterisk if you need One option is to recompile without Zaptel support.
2. You only have to load Zaptel drivers if you want to take advantag Zaptel services. One option is to unload Zaptel modules if you don't need .
3. If you need Zaptel services, you must correctly configure Zaptel.



can anybody helpme....
thanks.

[williamconley]

Yep. Install GoAutoDial. Even if only to compare the installation method/configuration files.

You stated scratch install ... but what directions are you following?

[eliasferreyra]

im usinng this method
http://ray-solomon.com/vicidial.html

and i started and finish , only need to install zaptel as well...

[williamconley]

I beg to differ. If you have not successfully run Vicidial on this box yet, it is premature to say zaptel will be your last piece of the puzzle. More like "next". I always recommend those installing from scratch use the GoAutoDial .iso if possible. Even if they install GoAutoDial on a "spare/fake" and use it for reference. Cuz Gardo made GoAutoDial WORK. So there's something very useful in there.

When you installed zaptel ... did you get any errors?

[eliasferreyra]

Ok but im installing by remote, the server is on another country....




williamconley
When you installed zaptel ... did you get any errors?
No...

my Centos installation is 5.5 64bit

[striker]

hi

try dahdi instead of zaptel
i am also used the ray solomon method ,but instead of zaptel i used dahdi and i didnt faced any issues

[eliasferreyra]

striker

how can i install dahdi instead of zaptel

how can i set config

[williamconley]

using the directions for dahdi from the vicidial wiki scratch install instructions ...

[striker]

remove the zaptel first
lsmod | grep zaptel

check the output of the above command and remove it my using modprobe -r
modprobe -r zaptel
modprobe -r zap_dummy
do it for all the zpatel modules which are listed under lsmod |grep zaptel

then download and install dahdi

1. download the latest dahdi from asterisk.org to /usr/src

2.untar the dahdi files (tar -xvzf dahdi-linux-complete-2.5.0+2.5.0tar.gz )

3. cd dahdi-linux-complete-2.5.0

4. make all
5. make install
6. make config

then go to the nano /etc/rc.d/rc.local
edit the below
### load zaptel drivers
modprobe zaptel
modprobe ztdummy
/sbin/ztcfg -vvvvvvvvvvvv

to

modprobe dahdi
modprobe dadhi_dummy
/sbin/dahdi_cfg -vvvvvvvvvvvvv

[eliasferreyra]

im receiving that
WARNING[15492]: app_meetme.c:829 build_conf: Unable to open DAHDI pseudo device



when i try to login on vicidial agent page

and the modprobe dahdi_dummy is not loading

i cant see on lsmod | grep dahdi

smod | grep dahdi
dahdi_transcode 42116 1 wctc4xxp
dahdi_voicebus 88096 2 wctdm24xxp,wcte12xp
dahdi 223620 11 xpp,dahdi_transcode,wcb4xxp,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,dahdi_voicebus,wct4xxp
crc_ccitt 35265 2 wctdm24xxp,dahdi

[eliasferreyra]

ok i solved this

i recompiled asterisk again....

[omarrodriguezt]

Just in case I resolve the situation without recompile asterisk.
Just start the service dahdi using /etc/init.d/dahdi start

If you want that the service run at startup:
chkconfig --level 35 dahdi

[williamconley]

excellent postback. wonder why it was not running to begin with.

[omarrodriguezt]

It was a fresh install. I don't know why was not running by default.