Hello all, after spending a great deal of time reading and searching, I am stumped.
Any hints are very welcome and appreciated.
Conference does not work, it always say: "that is not a valid conference number" and the log show:
WARNING[5025] app_meetme.c: Unable to open pseudo device
logger.c: -- Automatically generated pseudo channel
I have installed zaptel-1.4.12.1, running asterisk 1.4.22 on a Centos 5 fully updated Kernel 2.6.18-92.1.18.el5 on a real machine.
at boot I see zaptel start ok, zttest does talk back,
/dev/zap has:
crw-rw---- 1 asterisk asterisk 196, 254 Nov 27 12:18 channel
crw-rw---- 1 asterisk asterisk 196, 0 Nov 27 12:18 ctl
crw-rw---- 1 asterisk asterisk 196, 255 Nov 27 12:18 pseudo
crw-rw---- 1 asterisk asterisk 196, 253 Nov 27 12:18 timer
I ran genzaptelconf a few times, fully re-install from scratch compiling zaptel and installing it before asterisk goes in.
What else can I do to test or track this down and make it work.
Thanks
Sergio
__________________
do you have zaptel hardware?
do you have zaptel hardware? if not have you loaded the ztdummy driver?
No I dont have zaptel
No I dont have zaptel hardware. and as far as I can tell the dummy driver is loaded.
otherwise zttest it would not run or would it? . I lsmod and it is there.
How else can I tell?
Thanks.
lsmod is the way to
lsmod is the way to tell.
asterisk 1.4.22 is also the first release that uses the new dahdi drivers...
From the asterisk.org site:
Asterisk 1.4.22 includes a large number of bug fixes for the 1.4 release series of Asterisk. 1.4.22 also includes support for DAHDI. For more information about the transition from Zaptel to DAHDI, please see the following help file:
http://svn.digium.com/view/asterisk/tags/1.4.22/Zaptel-to-DAHDI.txt?view...