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); and in main/asterisk.c #ifdef HAVE_ZAPTEL static char _dahdi_chan_name[AST_CHANNEL_NAME] = "Zap"; #else static char _dahdi_chan_name[AST_CHANNEL_NAME] = "DAHDI"; #endif I deduct from that ... that you're still running zaptel and not dahdi. Because your log should say "No DAHDI channel available ..." UNLESS for some reason you only compiled chan_dahdi.so and copied it manually leaving the old app_meetme.so with HAVE_ZAPTEL flag... paste your lsmod output Martin On Thu, Apr 2, 2009 at 12:22 PM, Dave Poirier <dpoir...@mesd.k12.or.us> wrote: > 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 feature. The error from the console is.... > > # app_meetme.c:2593 find_conf: No Zap channel available for conference, user > introduction disabled > > I've added... > > dahdichanname=no > > to /etc/asterisk/asterisk.conf > > My thought was that would allow Asterisk to use Dahdi just as if it was ZAP. > > asterisk*CLI> zap show status > Description Alarms IRQ bpviol > CRC4 > T2XXP (PCI) Card 0 Span 1 OK 0 0 > 0 > T2XXP (PCI) Card 0 Span 2 RED 0 0 0 > > Span 2 is expected to be down as we don't have it connected to anything. > > asterisk*CLI> zap show channels > Chan Extension Context Language MOH Interpret > 1 incoming_pstn default > 2 incoming_pstn default > 3 incoming_pstn default > 4 incoming_pstn default > 5 incoming_pstn default > 6 incoming_pstn default > 7 incoming_pstn default > 8 incoming_pstn default > 9 incoming_pstn default > 10 incoming_pstn default > 11 incoming_pstn default > 12 incoming_pstn default > 13 incoming_pstn default > 14 incoming_pstn default > 15 incoming_pstn default > 16 incoming_pstn default > 17 incoming_pstn default > 18 incoming_pstn default > 19 incoming_pstn default > 20 incoming_pstn default > 21 incoming_pstn default > 22 incoming_pstn default > 23 incoming_pstn default > > > Should Zaptel be fully removed prior to Asterisk being compiled? It seems > that something with the meetme app is still linked somehow to Zaptel. > > Has anyone else come across this? Any suggestions? > Thanks, > Dave > > > _______________________________________________ > -- 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 > _______________________________________________ -- 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