We recently updated our Asterisk (1.4.24) box from Zaptel (1.4.12.1) to
Dahdi (2.1.0.4). Everything seemed to go smooth with the exception of
meetme. Meetme seems to not be able to find a zap channel for conferencing.
We use voice introductions in our conference bridge and it seems to break
that fe
That's very strange ... the code when is compiling checks whether
zaptel is present and then
the #define HAVE_ZAPTEL is set.
Since your error says No "ZAP" channel ...
and the code says
ast_log(LOG_WARNING, "No %s channel available for conference, user
introduction disabled\n", dahdi_chan_name);
Thanks for the reply Martin. I'm pretty sure that we are running dahdi (see
below). Could the problem be that I didn't remove the Zaptel libraries prior
to compiling Asterisk? If that's the case I should be able to rerun the
./configure without the zaptel libs and see if that fixes it. I'm just not
On Fri, Apr 03, 2009 at 08:24:41AM -0700, Dave Poirier wrote:
> Thanks for the reply Martin. I'm pretty sure that we are running dahdi (see
> below). Could the problem be that I didn't remove the Zaptel libraries prior
> to compiling Asterisk?
No. With Asterisk >= 1.4.22 it will check for "DAHDI"
Well maybe turn the dahdichanname=no to yes...
And check if you can open "cat /dev/dahdi/pseudo" ... or better yet
maybe you're running asterisk with user asterisk
and it doesn't have access to /dev/dahdi/pseudo ... ? Meetme tries to
open that for timing source.
Martin
On Fri, Apr 3, 2009 at 10:2
Asterisk runs as root on this system. Verified by looking at the running
processes.
#cat /dev/dahdi/pseudo
Predictably spits out the same char over and over.
I did manage to fix the behavior by removing dahdichanname=no from
asterisk.conf. This did however break any reference to ZAP channels in m
On Thu, Apr 02, 2009 at 10:22:55AM -0700, Dave Poirier wrote:
> We recently updated our Asterisk (1.4.24) box from Zaptel (1.4.12.1) to
> Dahdi (2.1.0.4).
Have you rebuilt Asterisk after that?
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.co...@xorcom.com
+972-50-7952
Yes that was on a fresh build. I updated from zaptel to dahdi at the same
time as moving from Asterisk 1.4.22 to 1.4.24.
On Fri, Apr 3, 2009 at 11:23 AM, Tzafrir Cohen wrote:
> On Thu, Apr 02, 2009 at 10:22:55AM -0700, Dave Poirier wrote:
> > We recently updated our Asterisk (1.4.24) box from Za
Last time I upgraded Zaptel to DAHDI I had a similar problem until I
erased the zaptel modules. The problem is that the Zaptel modules load
before DAHDI and you have a conflict with Asterisk. Delete everything
from /lib/modules/(Kernel Version)/misc and then reinstall DAHDI.
On Fri, 2009
Hi did list his lsmod and it doesn't show dahdi modules ...
For me it seems to be that dahdichanname=no ...
Martin
On Fri, Apr 3, 2009 at 4:17 PM, Carlos Chavez wrote:
> Last time I upgraded Zaptel to DAHDI I had a similar problem until I
> erased the zaptel modules. The problem is that
I meant zaptel modules ... no zaptel modules loaded on his system
Martin
On Fri, Apr 3, 2009 at 5:28 PM, Martin wrote:
> Hi did list his lsmod and it doesn't show dahdi modules ...
> For me it seems to be that dahdichanname=no ...
>
> Martin
>
> On Fri, Apr 3, 2009 at 4:17 PM, Carlos Chavez wro
11 matches
Mail list logo
