Can't get meetme to work. The ztdummy driver is loaded:
[root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy
ztdummy 7748 0
zaptel 196612 1 ztdummy
Although it won't load under normal conditions. I have to 'modprobe
ztdummy' manually:
[root@bil-pdev-6 asterisk-1.2.1]# /etc/init.d/zaptel start
Loading zaptel framework: [ OK ]
Waiting for zap to come online...Error: missing /dev/zap!
[root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy
[root@bil-pdev-6 asterisk-1.2.1]# modprobe ztdummy
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'
1 error(s) detected
FATAL: Error running install command for ztdummy
[root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy
ztdummy 7748 0
zaptel 196612 1 ztdummy
This seems to be relevant too:
[root@bil-pdev-6 asterisk-1.2.1]# more /proc/zaptel/1
Span 1: ZTDUMMY/1 "ZTDUMMY/1 1"
And finally, when I call meetme in Asterisk 1.2.1, I see:
Dec 20 16:57:27 WARNING[8822]: chan_zap.c:912 zt_open: Unable to open
'/dev/zap/pseudo': No such file or directory
Dec 20 16:57:27 ERROR[8822]: chan_zap.c:7364 chandup: Unable to dup channel: No
such file or directory
Dec 20 16:57:27 WARNING[8822]: app_meetme.c:458 build_conf: Unable to open
pseudo channel - trying device
Dec 20 16:57:27 WARNING[8822]: app_meetme.c:461 build_conf: Unable to open
pseudo device
-- Playing 'conf-invalid' (language 'en')
== Spawn extension (macro-DynamicMeetme, s, 2) exited non-zero on
'IAX2/192.168.10.7:4569-1' in macro 'DynamicMeetme'
== Spawn extension (Company1, dynamicmeetme, 1) exited non-zero on
'IAX2/192.168.10.7:4569-1'
-- Hungup 'IAX2/192.168.10.7:4569-1'
Anyone got any ideas???
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20051220/6d9c59f9/attachment.htm
On 12/20/05, Douglas Garstang <dgarstang@oneeighty.com> wrote:> > > Can't get meetme to work. The ztdummy driver is loaded: > > [root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy > ztdummy 7748 0 > zaptel 196612 1 ztdummy > > Although it won't load under normal conditions. I have to 'modprobe ztdummy' > manually: > > [root@bil-pdev-6 asterisk-1.2.1]# /etc/init.d/zaptel start > Loading zaptel framework: > [ OK ] > Waiting for zap to come online...Error: missing /dev/zap! > [root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy > [root@bil-pdev-6 asterisk-1.2.1]# modprobe ztdummy > Notice: Configuration file is /etc/zaptel.conf > line 0: Unable to open master device '/dev/zap/ctl' > > 1 error(s) detected > > FATAL: Error running install command for ztdummy > [root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy > ztdummy 7748 0 > zaptel 196612 1 ztdummy > > This seems to be relevant too: > > [root@bil-pdev-6 asterisk-1.2.1]# more /proc/zaptel/1 > Span 1: ZTDUMMY/1 "ZTDUMMY/1 1" > > And finally, when I call meetme in Asterisk 1.2.1, I see: > > Dec 20 16:57:27 WARNING[8822]: chan_zap.c:912 zt_open: Unable to open > '/dev/zap/pseudo': No such file or directory > Dec 20 16:57:27 ERROR[8822]: chan_zap.c:7364 chandup: Unable to dup channel: > No such file or directory > Dec 20 16:57:27 WARNING[8822]: app_meetme.c:458 build_conf: Unable to open > pseudo channel - trying device > Dec 20 16:57:27 WARNING[8822]: app_meetme.c:461 build_conf: Unable to open > pseudo device > -- Playing 'conf-invalid' (language 'en') > == Spawn extension (macro-DynamicMeetme, s, 2) exited non-zero on > 'IAX2/192.168.10.7:4569-1' in macro 'DynamicMeetme' > == Spawn extension (Company1, dynamicmeetme, 1) exited non-zero on > 'IAX2/192.168.10.7:4569-1' > -- Hungup 'IAX2/192.168.10.7:4569-1' > > Anyone got any ideas??? >Yes. If you're using Linux with a udev filesystem you need to look at README.udev in the zaptel build folder which gives you some lines to add to your udev config so the zaptel devices are created in /dev. This seems to be where your error messages are coming from here. -- Bird's The Word Technologies, Inc. http://www.btwtech.com/
Thanks. That did the trick. :) -----Original Message----- From: BJ Weschke [mailto:bweschke@gmail.com] Sent: Tuesday, December 20, 2005 4:41 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Meetme and ztdummy On 12/20/05, Douglas Garstang <dgarstang@oneeighty.com> wrote:> > > Can't get meetme to work. The ztdummy driver is loaded: > > [root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy > ztdummy 7748 0 > zaptel 196612 1 ztdummy > > Although it won't load under normal conditions. I have to 'modprobe ztdummy' > manually: > > [root@bil-pdev-6 asterisk-1.2.1]# /etc/init.d/zaptel start > Loading zaptel framework: > [ OK ] > Waiting for zap to come online...Error: missing /dev/zap! > [root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy > [root@bil-pdev-6 asterisk-1.2.1]# modprobe ztdummy > Notice: Configuration file is /etc/zaptel.conf > line 0: Unable to open master device '/dev/zap/ctl' > > 1 error(s) detected > > FATAL: Error running install command for ztdummy > [root@bil-pdev-6 asterisk-1.2.1]# lsmod | grep ztdummy > ztdummy 7748 0 > zaptel 196612 1 ztdummy > > This seems to be relevant too: > > [root@bil-pdev-6 asterisk-1.2.1]# more /proc/zaptel/1 > Span 1: ZTDUMMY/1 "ZTDUMMY/1 1" > > And finally, when I call meetme in Asterisk 1.2.1, I see: > > Dec 20 16:57:27 WARNING[8822]: chan_zap.c:912 zt_open: Unable to open > '/dev/zap/pseudo': No such file or directory > Dec 20 16:57:27 ERROR[8822]: chan_zap.c:7364 chandup: Unable to dup channel: > No such file or directory > Dec 20 16:57:27 WARNING[8822]: app_meetme.c:458 build_conf: Unable to open > pseudo channel - trying device > Dec 20 16:57:27 WARNING[8822]: app_meetme.c:461 build_conf: Unable to open > pseudo device > -- Playing 'conf-invalid' (language 'en') > == Spawn extension (macro-DynamicMeetme, s, 2) exited non-zero on > 'IAX2/192.168.10.7:4569-1' in macro 'DynamicMeetme' > == Spawn extension (Company1, dynamicmeetme, 1) exited non-zero on > 'IAX2/192.168.10.7:4569-1' > -- Hungup 'IAX2/192.168.10.7:4569-1' > > Anyone got any ideas??? >Yes. If you're using Linux with a udev filesystem you need to look at README.udev in the zaptel build folder which gives you some lines to add to your udev config so the zaptel devices are created in /dev. This seems to be where your error messages are coming from here. -- Bird's The Word Technologies, Inc. http://www.btwtech.com/ _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users