I don’t have a dahdi card (Using SIP) so I installed linux dahdi for dahdi_dummy. But meetme is still complaining with:
[2009-06-16 15:47:22] WARNING[4510]: channel.c:3690 ast_request: No channel type registered for ‘DAHDI’
[2009-06-16 15:47:22] WARNING[4510]: app_meetme.c:3098 find_conf: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?)
lsmod confirms dahdi_dummy present
suggestions where I am goig wrong please?
Is chan_dahdi supposed to be present on a system with no dahdi hardware.?
meetme definitely wants chan_dahdi
I don’t have dahdi hardware and so I installed dahdi-linux-2.2.01 to provide dahdi_dummy for timing.
According to menuselect I am not permitted to install chan_dahdi.
menuselect shows: XXX chan_dahdi
1.6.1.0 definitely works with dahdi only for dahdi_dummy.
If you look carefully, menuconfig will show you what it thinks is missing.
Did you re-run configure on Asterisk, after installing dahdi?
centos*CLI> core show version
Asterisk 1.6.1.0 built by root @ centos on a i686 running Linux on 2009-07-02 14:10:32 UTC
centos*CLI> dahdi show status
Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO
DAHDI_DUMMY/1 (source: RTC) 1 UNCONFI 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)
I am pretty sure that I had included everything in make menuselect, but to be sure I rebuilt from scratch. Chan_dahdi is xxx in menuselect, I expect this is because of the lack of dahdi hardware.
One more point. have installed using user&group asterisk, under /usr/local/asterisk
DAHDI_DUMMY seems to be working, it is certainly being reported as working by dahdi_tools etc.
The other asterisk features are working:
voicemail, call parking, outbound calls, inbound calls and same context calls are all OK.
The problem is calling a meetme number. From the dialling phone all I hear is theAll I hear is the invalidpin message and on the console I see the following.
== Using SIP RTP CoS mark 5
– Executing [2699@willow:1] MeetMe(“SIP/92691-08d579f0”, “2699,i,1234”) in new stack
== Parsing ‘/usr/local/asterisk/etc/asterisk/meetme.conf’: == Found
[Jul 8 13:55:56] WARNING[5955]: channel.c:3690 ast_request: No channel type registered for ‘DAHDI’
– Created MeetMe conference 1023 for conference ‘2699’
[Jul 8 13:55:56] WARNING[5955]: app_meetme.c:3098 find_conf: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?)
– <SIP/92691-08d579f0> Playing ‘conf-invalidpin.slin’ (language ‘en’)
== Spawn extension (willow, 2699, 1) exited non-zero on ‘SIP/92691-08d579f0’
Don’t guess. Look at what menuconfig tells you is the failed dependency for dahdi. I don’t want to divert to check may test rig, but I am fairly sure that I have chan_dahdi enabled with only dahdi_dummy. In fact, if it weren’t there, I am sure dahdi show state would have been unrecognized.
Thanks again for replying but there is no guessing going on.
from the menuselect:
Depends on: res_smdi(M), dahdi(E), tonezone(E)
Can use: pri, ss7
Dahdi must be available as app_meetme has dahdi as a dependency and it compiles. and res_smdi is also met. zone has been set to uk
I had a typo in meetme.conf that was stopping meetme from working, after fixing that I still get the chan_dahdi problem:
[Jul 9 11:49:04] WARNING[21199]: channel.c:3690 ast_request: No channel type registered for ‘DAHDI’
Jul 9 11:49:04] WARNING[21199]: app_meetme.c:3098 find_conf: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?)
– <SIP/92691-08bb4598> Playing ‘conf-onlyperson.slin’ (language ‘en’)
I hear the “onlyperson” message but a pin is not requested
relevent line from extensions.conf
exten => 2699,1,MeetMe(2699,Mip,1234)
Dahdi_dummy is available:
Concentrate on menuconfig. Until you get chan_dahdi out of an XXX state, there is no point in checking the output from Asterisk.
I suspect, if you look at your configure.log, you will find a problem with TONEZONE.
My impression is that XXX means that an (E) dependency has failed. (M) dependencies look like they are other options controlled by menuselect, and you will get < >, rather than XXX, which you can change, resulting in the dependency changing.Concentrate on menuconfig. Until you get chan_dahdi out of an XXX state, there is no point in checking the output from Asterisk.
I suspect, if you look at your configure.log, you will find a problem with TONEZONE.
My impression is that XXX means that an (E) dependency has failed. (M) dependencies look like they are other options controlled by menuselect, and you will get < >, rather than XXX, which you can change, resulting in the dependency changing.
Thanks, In the end I found that creating /usr/include/dahdi and copying in
tonezone.h
I could do a clean:
./configure
make
make install