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.... <br clear="all">
<br># app_meetme.c:2593 find_conf: No Zap channel available for conference, user introduction disabled<br><br>I've added...<br><br>dahdichanname=no<br><br>to /etc/asterisk/asterisk.conf<br><br>My thought was that would allow Asterisk to use Dahdi just as if it was ZAP.<br>
<br>asterisk*CLI> zap show status <br>Description Alarms IRQ bpviol CRC4 <br>T2XXP (PCI) Card 0 Span 1 OK 0 0 0 <br>T2XXP (PCI) Card 0 Span 2 RED 0 0 0<br>
<br>Span 2 is expected to be down as we don't have it connected to anything.<br><br>asterisk*CLI> zap show channels <br> Chan Extension Context Language MOH Interpret <br> 1 incoming_pstn default <br>
2 incoming_pstn default <br> 3 incoming_pstn default <br> 4 incoming_pstn default <br> 5 incoming_pstn default <br>
6 incoming_pstn default <br> 7 incoming_pstn default <br> 8 incoming_pstn default <br> 9 incoming_pstn default <br>
10 incoming_pstn default <br> 11 incoming_pstn default <br> 12 incoming_pstn default <br> 13 incoming_pstn default <br>
14 incoming_pstn default <br> 15 incoming_pstn default <br> 16 incoming_pstn default <br> 17 incoming_pstn default <br>
18 incoming_pstn default <br> 19 incoming_pstn default <br> 20 incoming_pstn default <br> 21 incoming_pstn default <br>
22 incoming_pstn default <br> 23 incoming_pstn default<br><br><br>Should Zaptel be fully removed prior to Asterisk being compiled? It seems that something with the meetme app is still linked somehow to Zaptel.<br>
<br>Has anyone else come across this? Any suggestions?<br>Thanks,<br>Dave<br><br>