Hi All, I've had a great time exploring * on & off over the past month and have had a deal of success, very impressed with this product... I have an issue on a debian unstable system with the zap interface. I've compiled and loaded the ztdummy successfully, but when attempting to connect to a conference room I get failure. I get the error chan_zap.c:757 zt_open: Unable to open '/dev/zap/pseudo': Permission denied The real issue is that the /dev/zap/pseudo is really a symbolic link to /boot/pseudo which isn't there. Can anyone tell me where it ought be linked, or if I need to mknod etc to create the virtual device? Cheers, Lewis
On Tue, 2004-09-28 at 02:11, Lewis Shobbrook wrote:> Hi All, > > I've had a great time exploring * on & off over the past month and have > had a deal of success, very impressed with this product... > > I have an issue on a debian unstable system with the zap interface. > I've compiled and loaded the ztdummy successfully, but when attempting > to connect to a conference room I get failure. I get the error > chan_zap.c:757 zt_open: Unable to open '/dev/zap/pseudo': Permission > denied > > The real issue is that the > /dev/zap/pseudo is really a symbolic link to /boot/pseudo which isn't > there. > > Can anyone tell me where it ought be linked, or if I need to mknod etc > to create the virtual device?unload the zapata drivers, delete the zap directory and rerun "make install" in the zapata/zaptel directories so it correctly makes the dev entries. -- Steven Critchfield <critch@basesys.com>
Thanks for the reply Steve,> On Tue, 2004-09-28 at 02:11, Lewis Shobbrook wrote: > > Hi All, > > > > I've had a great time exploring * on & off over the past month and > > have had a deal of success, very impressed with this product... > > > > I have an issue on a debian unstable system with the zap interface. > > I've compiled and loaded the ztdummy successfully, but when > attempting > > to connect to a conference room I get failure. I get the error > > chan_zap.c:757 zt_open: Unable to open '/dev/zap/pseudo': > Permission > > denied > > > > The real issue is that the > > /dev/zap/pseudo is really a symbolic link to /boot/pseudo > which isn't > > there. > > > > Can anyone tell me where it ought be linked, or if I need > to mknod etc > > to create the virtual device? > > unload the zapata drivers, delete the zap directory and rerun > "make install" in the zapata/zaptel directories so it > correctly makes the dev entries. > -- > Steven Critchfield <critch@basesys.com>Did this, the problem slightly shifted... Attempts to meetme resulted in ... Sep 29 13:07:39 WARNING[311315]: channel.c:1901 ast_request: No channel type registered for 'zap' Sep 29 13:07:39 WARNING[311315]: app_meetme.c:227 build_conf: Unable to open pseudo channel - trying device Sep 29 13:07:39 WARNING[311315]: app_meetme.c:230 build_conf: Unable to open pseudo device Chown asterisk:root /dev/zap/pseudo fixed it! Debian run's chroot'ed ... Cheers, Lewis