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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090402/d3757bf6/attachment.htm
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 <dpoirier at 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 >
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.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
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 <tzafrir.cohen at xorcom.com>wrote:> 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.cohen at xorcom.com<jabber%3Atzafrir.cohen at xorcom.com> > +972-50-7952406 mailto:tzafrir.cohen at xorcom.com > http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir > > _______________________________________________ > -- 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 >-- David Poirier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090403/e101f9cf/attachment.htm
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-04-03 at 11:53 -0700, Dave Poirier wrote:> 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 > <tzafrir.cohen at xorcom.com> wrote: > 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.cohen at xorcom.com > +972-50-7952406 mailto:tzafrir.cohen at xorcom.com > http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir > > _______________________________________________ > > > -- 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 > > > > > -- > David Poirier > _______________________________________________ > -- 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-- Telecomunicaciones Abiertas de M?xico S.A. de C.V. Carlos Ch?vez Prats Director de Tecnolog?a +52-55-91169161 ext 2001 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090403/5e92c7c8/attachment-0001.pgp