Re: [asterisk-users] Meetmee user introduction disabled

2010-06-03 Thread David Backeberg
On Thu, May 27, 2010 at 6:17 PM, Theo Band  wrote:
> I used to build Asterisk from source including the zaptel-dummy module.
> Last year I decided to upgrade and use a yum repository. I hoped that
> this would be less hassle compared to manually chasing after the latest
> release, compiling etc. And after every kernel update the modules need
> to be recompiled. The yum flow does it all for me using this repository:

You're going to have to file a complaint / bug / fix against whoever
maintains your repository, or go back to building from source.

Or get a hardware card to use for timing, as that would solve your
need for dahdi_dummy :)

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Meetmee user introduction disabled

2010-05-27 Thread Theo Band
David Backeberg wrote:
> On Thu, May 27, 2010 at 4:05 AM, Theo Band  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
>
>   
What I mean is that it is no longer present in the package:
rpm -qf /lib/modules/2.6.18-164.11.1.el5/dahdi/dahdi_dummy.ko
kmod-dahdi-linux-2.2.1-1_centos5.2.6.18_164.11.1.el5

rpm -ql kmod-dahdi-linux-2.3.0.1-1_centos5.2.6.18_194.3.1.el5|grep
dahdi_dummy.ko

>> 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
>   
I used to build Asterisk from source including the zaptel-dummy module.
Last year I decided to upgrade and use a yum repository. I hoped that
this would be less hassle compared to manually chasing after the latest
release, compiling etc. And after every kernel update the modules need
to be recompiled. The yum flow does it all for me using this repository:

[asterisk-current]
name=CentOS-$releasever - Asterisk - Current
baseurl=http://packages.asterisk.org/centos/$releasever/current/$basearch/
enabled=1
gpgcheck=0
#gpgkey=http://packages.asterisk.org/RPM-GPG-KEY-Digium

This is why I prefer not to compile and install anything outside of
yum/rpm.
> 
> It seems that these days you need to provide extra arguments to get
> dahdi_dummy, and it's getting filtered by default.
>
>   

So what you describe is probably what the package builders also need to
know. How can I report such an issue other than using this forum? I
don't think a private mail to the maintainer is the best option.

And although kmod-dahdi-linux-2.2.1-1 contains the dummy module, the
newer version of meetme still does not work. So that's a meetme
application issue I think.


-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Meetmee user introduction disabled

2010-05-27 Thread David Backeberg
On Thu, May 27, 2010 at 4:05 AM, Theo Band  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.

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] Meetmee user introduction disabled

2010-05-27 Thread Theo Band
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

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users