asterisk users - May 2010 - Meetmee user introduction disabled

I updated Asterisk to 1.6.2.7 and now the user introduction in the
meetme application is no longer working:

[May 27 09:26:51] WARNING[2407]: channel.c:4034 ast_request: No channel
type registered for 'DAHDI'
    -- Created MeetMe conference 1023 for conference '800'
[May 27 09:26:51] WARNING[2407]: app_meetme.c:3640 find_conf: No DAHDI
channel available for conference, user introduction disabled (is
chan_dahdi loaded?)
[May 27 09:26:51] WARNING[2407]: app_meetme.c:3646 find_conf: No DAHDI
channel available for conference, conference recording disabled (is
chan_dahdi loaded?)


The conference itself seems to work. The box does not have any special
hardware so dadhi is only needed for timing and as I understood for
conference mixing. As part of the update I also updated the dadhi
modules and the kernel (all with "yum update"):

kmod-dahdi-linux-2.3.0.1-1_centos5.2.6.18_194.3.1.el5
kmod-dahdi-linux-2.2.1-1_centos5.2.6.18_164.11.1.el5

First I noted that dahdi_dummy is no longer present in
kmod-dahdi-linux-2.3.0.1-1. Reverting back to kmod-dahdi-linux-2.2.1-1
solved that issue, now the module is loaded again.
lsdahdi
### Span  1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: Linux26) 1"
(MASTER)
lsmod|grep dahdi_dummy
dahdi_dummy             8612  0
dahdi                 194504  14
dahdi_dummy,xpp,dahdi_transcode,wcb4xxp,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,dahdi_voicebus,wct4xxp


Asterisk however shows the same warning message. So I guess something
has changed in the meetme application itself and it does not seem to use
dahdi_dummy anymore?
What steps can I take?

Theo

On Thu, May 27, 2010 at 4:05 AM, Theo Band <theo.band at greenpeak.com>
wrote:
> First I noted that dahdi_dummy is no longer present in
> kmod-dahdi-linux-2.3.0.1-1.
Not exactly true.

myhost01 asterisk # lsmod | grep dahdi
dahdi_dummy             5812  0
dahdi_transcode         8968  1 wctc4xxp
dahdi_voicebus         42048  2 wctdm24xxp,wcte12xp
dahdi                 198992  24
dahdi_dummy,xpp,dahdi_transcode,wcb4xxp,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,dahdi_voicebus,wct4xxp
crc_ccitt               4096  2 wctdm24xxp,dahdi

myhost01 asterisk # dmesg | grep dahdi
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.3.0
> Reverting back to kmod-dahdi-linux-2.2.1-1
> solved that issue, now the module is loaded again.
I suppose it would. I got dahdi_dummy with 2.3.0 by analyzing how the
build process worked, and doing some tricks. I could see dahdi_dummy.c
was in the package but it wasn't getting built.

Here's the trick.

If you pull down the combined dahdi package, extract it,
cd into the extracted top-level folder
cd linux (which is the dahdi proper stuff)

make MODULES_EXTRA=dahdi_dummy

That worked for me.
Do the make install too.

asktest01 linux # make MODULES_EXTRA=dahdi_dummy
make -C drivers/dahdi/firmware firmware-loaders
make[1]: Entering directory
`/usr/local/src/dahdi-linux-complete-2.3.0+2.3.0/linux/drivers/dahdi/firmware'
make[1]: Leaving directory
`/usr/local/src/dahdi-linux-complete-2.3.0+2.3.0/linux/drivers/dahdi/firmware'
make -C /lib/modules/2.6.28.9/build
SUBDIRS=/usr/local/src/dahdi-linux-complete-2.3.0+2.3.0/linux/drivers/dahdi
DAHDI_INCLUDE=/usr/local/src/dahdi-linux-complete-2.3.0+2.3.0/linux/include
DAHDI_MODULES_EXTRA="dahdi_dummy.o " HOTPLUG_FIRMWARE=yes modules
DAHDI_BUILD_ALL=m
make[1]: Entering directory `/usr/src/linux-2.6.28.9'
  CC [M] 
/usr/local/src/dahdi-linux-complete-2.3.0+2.3.0/linux/drivers/dahdi/dahdi_dummy.o

  Building modules, stage 2.
  MODPOST 31 modules
  CC     
/usr/local/src/dahdi-linux-complete-2.3.0+2.3.0/linux/drivers/dahdi/dahdi_dummy.mod.o
  LD [M] 
/usr/local/src/dahdi-linux-complete-2.3.0+2.3.0/linux/drivers/dahdi/dahdi_dummy.ko
make[1]: Leaving directory `/usr/src/linux-2.6.28.9'

It seems that these days you need to provide extra arguments to get
dahdi_dummy, and it's getting filtered by default.