Hello, I'm running Fedora Core 3 with udev, and asterisk/zaptel/libpri
from cvs. I have followed the README.udev instructions replacing insmod
with modprobe and rmmod with modprobe -r and adding the 60-zaptel.rules
file, yet no matter what I do I still get this error on boot(or when I
run service zaptel restart):
[root@pbx ~]# /etc/init.d/zaptel restart
Unloading zaptel hardware drivers: wcusb wcfxs wcfxo wct1xxp wct4xxp
tor2 torisa
Removing zaptel module: [ OK ]
Loading zaptel framework: [ OK ]
Loading zaptel hardware modules:
Running ztcfg: Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'
1 error(s) detected
[FAILED]
My card is a Digium T100P, and the zaptel.conf is correct (i've checked
it and had it checked by another asterisk guy.) Anyone have any
suggestions? I've googled a bit but everyone else with this issue has
it because they didn't add the rules file. I checked and their is a
/dev/zap/ctl.
Thanks,
-Ryan
So in FC3 with udev you aparently need to start the zaptel service twice to get it to work properly(according to the digium tech I spoke with today.) However, it looked like it was all working and then I got off the line and rebooted and things were still screwy, so what I did was add a sleep 30 line at the end of the start case in the zaptel init file. and then added an extra slink in /etc/rd3.d right before asterisk to run again. This corrected the problem. -Ryan Ryan Stark wrote:> Hello, I'm running Fedora Core 3 with udev, and asterisk/zaptel/libpri > from cvs. I have followed the README.udev instructions replacing insmod > with modprobe and rmmod with modprobe -r and adding the 60-zaptel.rules > file, yet no matter what I do I still get this error on boot(or when I > run service zaptel restart): > > [root@pbx ~]# /etc/init.d/zaptel restart > Unloading zaptel hardware drivers: wcusb wcfxs wcfxo wct1xxp wct4xxp > tor2 torisa > Removing zaptel module: [ OK ] > Loading zaptel framework: [ OK ] > Loading zaptel hardware modules: > Running ztcfg: Notice: Configuration file is /etc/zaptel.conf > line 0: Unable to open master device '/dev/zap/ctl' > > 1 error(s) detected > > [FAILED] > > My card is a Digium T100P, and the zaptel.conf is correct (i've checked > it and had it checked by another asterisk guy.) Anyone have any > suggestions? I've googled a bit but everyone else with this issue has > it because they didn't add the rules file. I checked and their is a > /dev/zap/ctl. > > Thanks, > -Ryan > _______________________________________________ > 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
Ryan Stark wrote:> Hello, I'm running Fedora Core 3 with udev, and asterisk/zaptel/libpri > from cvs. I have followed the README.udev instructions replacing insmod > with modprobe and rmmod with modprobe -r and adding the 60-zaptel.rules > file, yet no matter what I do I still get this error on boot(or when I > run service zaptel restart): > > [root@pbx ~]# /etc/init.d/zaptel restart > Unloading zaptel hardware drivers: wcusb wcfxs wcfxo wct1xxp wct4xxp > tor2 torisa > Removing zaptel module: [ OK ] > Loading zaptel framework: [ OK ] > Loading zaptel hardware modules: > Running ztcfg: Notice: Configuration file is /etc/zaptel.conf > line 0: Unable to open master device '/dev/zap/ctl' > > 1 error(s) detectedDid you reboot after creating the 60- file in /etc/udev/rules? -- Michael Welter Introspect Telephony Corp. Denver, Colorado US +1.303.674.2575 mike@introspect.com www.introspect.com