ast guy
2008-Jan-16 10:55 UTC
[asterisk-users] Unable to open master device '/dev/zap/ctl'
Hi,
I'm using zaptel-1.2.22.1 with asterisk-1.2.10 and following steps to
make zaptel working...
OS is gentoo linux 2006.1
Hardware:
---------
0000:05:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX
Modem/ISDN interface
Subsystem: Unknown device 8085:0003
Flags: bus master, medium devsel, latency 32, IRQ 22
I/O ports at b400
Memory at ff900000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
- Compiled, installed zaptel
- Compiled, installed Asterisk
gigli ~ # modprobe zaptel
/var/log/messages:
Jan 16 15:42:31 gigli Zapata Telephony Interface Registered on major 196
Jan 16 15:42:31 gigli Zaptel Version: 1.2.22.1
Jan 16 15:42:31 gigli Zaptel Echo Canceller: KB1
gigli ~ # modprobe wcfxo
/var/log/messages:
Jan 16 15:42:33 gigli ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 22
(level, low) -> IRQ 22
Jan 16 15:42:33 gigli wcfxo: DAA mode is 'FCC'
Jan 16 15:42:33 gigli Found a Wildcard FXO: Wildcard X101P
gigli # ztcfg -v
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'
1 error(s) detected
Asterisk log
-------------
[chan_zap.so] => (Zapata Telephony)
== Parsing '/etc/asterisk/zapata.conf': Found
Jan 16 15:43:30 WARNING[5415]: chan_zap.c:915 zt_open: Unable to open
'/dev/zap/channel': No such file or directory
Jan 16 15:43:30 ERROR[5415]: chan_zap.c:6861 mkintf: Unable to open
channel 1: No such file or directory
here = 0, tmp->channel = 1, channel = 1
Jan 16 15:43:30 ERROR[5415]: chan_zap.c:10288 setup_zap: Unable to
register channel '1'
Jan 16 15:43:30 WARNING[5415]: loader.c:414 __load_resource:
chan_zap.so: load_module failed, returning -1
Jan 16 15:43:30 WARNING[5415]: loader.c:554 load_modules: Loading
module chan_zap.so failed!
Zaptel File /etc/zaptel.conf:
-----------------------------
fxsks=1
loadzone = us
defaultzone=us
UDEV file /etc/udev/rules.d/50-udev.rules:
-----------------------------------------
# Asterisk Zaptel devices
KERNEL=="zapctl", NAME="zap/ctl"
KERNEL=="zaptimer", NAME="zap/timer"
KERNEL=="zapchannel", NAME="zap/channel"
KERNEL=="zappseudo", NAME="zap/pseudo"
KERNEL=="zap[0-9]*", NAME="zap/%n"
ZAPATA file:
-----------
gigli # cat /etc/asterisk/zapata.conf
[trunkgroups]
[channels]
context=default
switchtype=national
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
cidstart=ring
hidecallerid=no
callwaiting=yes
restrictcid=no
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes
rxgain=5.0
txgain=5.0
immediate=no
callerid=asrecieved
busydetect=yes
busycount=4
musiconhold=default
context=default
group=1
channel =>1
Can anyone give hint, what am I missing ?
-ag
Tzafrir Cohen
2008-Jan-16 11:01 UTC
[asterisk-users] Unable to open master device '/dev/zap/ctl'
On Wed, Jan 16, 2008 at 03:55:08PM +0500, ast guy wrote:> Hi, > > I'm using zaptel-1.2.22.1 with asterisk-1.2.10 and following steps to > make zaptel working... > > OS is gentoo linux 2006.1 > > Hardware: > --------- > > 0000:05:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX > Modem/ISDN interface > Subsystem: Unknown device 8085:0003 > Flags: bus master, medium devsel, latency 32, IRQ 22 > I/O ports at b400 > Memory at ff900000 (32-bit, non-prefetchable) [size=4K] > Capabilities: [40] Power Management version 2 > > - Compiled, installed zaptel > - Compiled, installed Asterisk > > gigli ~ # modprobe zaptel > > /var/log/messages: > Jan 16 15:42:31 gigli Zapata Telephony Interface Registered on major 196 > Jan 16 15:42:31 gigli Zaptel Version: 1.2.22.1 > Jan 16 15:42:31 gigli Zaptel Echo Canceller: KB1 > > gigli ~ # modprobe wcfxo > > /var/log/messages: > Jan 16 15:42:33 gigli ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 22 > (level, low) -> IRQ 22 > Jan 16 15:42:33 gigli wcfxo: DAA mode is 'FCC' > Jan 16 15:42:33 gigli Found a Wildcard FXO: Wildcard X101P > > gigli # ztcfg -v > Notice: Configuration file is /etc/zaptel.conf > line 0: Unable to open master device '/dev/zap/ctl'ls -l /dev/zap/ ls -l /sys/class/zaptel/> > 1 error(s) detected > > > Asterisk log > ------------- >Don't waste your time on Asterisk. Fix Zaptel first.> Zaptel File /etc/zaptel.conf: > ----------------------------- > > fxsks=1 > loadzone = us > defaultzone=us > > > UDEV file /etc/udev/rules.d/50-udev.rules: > ----------------------------------------- > > # Asterisk Zaptel devices > KERNEL=="zapctl", NAME="zap/ctl" > KERNEL=="zaptimer", NAME="zap/timer" > KERNEL=="zapchannel", NAME="zap/channel" > KERNEL=="zappseudo", NAME="zap/pseudo" > KERNEL=="zap[0-9]*", NAME="zap/%n"Looks OK. The only missing line is a permissions line. But not porblem when you run ztcfg as root. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Chris Bagnall
2008-Jan-16 20:39 UTC
[asterisk-users] Unable to open master device '/dev/zap/ctl'
Make sure asterisk is in the "dialout" group in /etc/passwd The default gentoo ebuild of zaptel creates /dev/zap/* with group dialout, and if you're using the gentoo ebuild of asterisk, it'll run as asterisk:asterisk, so you need to make sure asterisk is a member of the dialout goup otherwise it'll never be able to access /dev/zap/* FWIW, as a fellow Gentoo user, 2006.1 is a bit dated, and you'd be well worth updating to 2007.0 if you can spare the time - it'll save you a lot of messing around with gcc versions etc. later down the line. Regards, Chris -- C.M. Bagnall, Director, Minotaur I.T. Limited For full contact details visit http://www.minotaur.it This email is made from 100% recycled electrons
ast guy
2008-Jan-17 09:31 UTC
[asterisk-users] Unable to open master device '/dev/zap/ctl'
there is no /proc/zap folder .. can you tell how can I create /dev nodes. I have tested the same configurations on FC5 and these device links were created ... drwxr-xr-x 2 root root 160 Jan 17 10:59 . drwxr-xr-x 13 root root 3640 Jan 17 11:00 .. crw------- 1 root root 196, 1 Jan 17 10:59 1 crw------- 1 root root 196, 254 Jan 17 10:59 channel crw------- 1 root root 196, 0 Jan 17 10:59 ctl crw------- 1 root root 196, 255 Jan 17 10:59 pseudo crw------- 1 root root 196, 253 Jan 17 10:59 timer crw-rw---- 1 root root 196, 250 Jan 17 10:59 transcode -ag>create nodes and links /proc/zapOn Jan 16, 2008 3:39 PM, Chris Bagnall <lists at minotaur.cc> wrote:>> Make sure asterisk is in the "dialout" group in /etc/passwd >> >> The default gentoo ebuild of zaptel creates /dev/zap/* with group dialout, >> and if you're using the gentoo ebuild of asterisk, it'll run as >> asterisk:asterisk, so you need to make sure asterisk is a member of the >> dialout goup otherwise it'll never be able to access /dev/zap/* >> >> FWIW, as a fellow Gentoo user, 2006.1 is a bit dated, and you'd be well >> worth updating to 2007.0 if you can spare the time - it'll save you a lot >> of messing around with gcc versions etc. later down the line. >> >> Regards, >> >> Chris >> -- >> C.M. Bagnall, Director, Minotaur I.T. Limited >> For full contact details visit http://www.minotaur.it >> This email is made from 100% recycled electrons
ast guy
2008-Jan-17 10:37 UTC
[asterisk-users] Unable to open master device '/dev/zap/ctl'
*Walter Willis,
*Thanks a lot, got the commands from zap Makefile and it worked, now can
create conference room, my question still stands why it didn't create
itself. Will go through make file to get an answer to that.
Anyone else facing the issue can resolve by running following commands
mknod /dev/zap/ctl c 196 0
mknod /dev/zap/transcode c 196 250
mknod /dev/zap/timer c 196 253
mknod /dev/zap/channel c 196 254
mknod /dev/zap/pseudo c 196 255
-ag
>any version of asterisk not create nodes into /proc/zap
>create to command, view into make file how to create nodes
>On Jan 16, 2008 8:48 PM, Walter Willis <walterwn at gmail.com> wrote:
> create nodes and links /proc/zap
>
>
>
> On Jan 16, 2008 3:39 PM, Chris Bagnall <lists at minotaur.cc> wrote:
>
> > Make sure asterisk is in the "dialout" group in /etc/passwd
> >
> > The default gentoo ebuild of zaptel creates /dev/zap/* with group
> > dialout, and if you're using the gentoo ebuild of asterisk,
it'll run as
> > asterisk:asterisk, so you need to make sure asterisk is a member of
the
> > dialout goup otherwise it'll never be able to access /dev/zap/*
> >
> > FWIW, as a fellow Gentoo user, 2006.1 is a bit dated, and you'd be
well
> > worth updating to 2007.0 if you can spare the time - it'll save
you a
> > lot of messing around with gcc versions etc. later down the line.
> >
> > Regards,
> >
> > Chris
> > --
> > C.M. Bagnall, Director, Minotaur I.T. Limited
> > For full contact details visit http://www.minotaur.it
> > This email is made from 100% recycled electrons
> >
> >
> >
> >
> > _______________________________________________
> > -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >
> > asterisk-users mailing list
> > To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20080117/e7388cdd/attachment.htm