|Summary:||ASTERISK-17398: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?)|
|Reporter:||Preston Edwards (preston_edwards)||Labels:|
|Date Opened:||2011-02-13 13:37:42.000-0600||Date Closed:||2011-08-31 11:14:28|
|Environment:||Attachments:||( 0) jira_asterisk_17398_v1.8.patch|
|Description:||The following error will consistently occur in an Asterisk 1.8 environment when trying to dial-in to a MeetMe conference when the server does not have Dahdi hardware installed:|
app_meetme.c: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?)
This will cause user introductions to be disabled, including name announcement, etc.
While chan_dahdi IS loaded correctly during compilation and install of Asterisk/Dahdi, including associated modules, etc., a chan_dahdi.conf configuration file in /etc/asterisk is not created if hardware does not exist, causing MeetMe to think it can't open a dahdi_dummy channel.
Remedy to this is to rename the chan_dahdi.conf.sample file to chan_dahdi.conf and restart Asterisk--this error will go away and the introductions will work just fine.
Since I've seen numerous unanswered posts when searching Google to try and find an answer to this, I thought I'd file this as an issue to get the chan_dahdi.conf file created automatically for the above scenario so it's not a manual process.
|Comments:||By: Preston Edwards (preston_edwards) 2011-02-13 18:54:32.000-0600|
Sorry, didn't mean to choose major--rather minor severity.
By: Shaun Ruffell (sruffell) 2011-02-13 22:11:44.000-0600
Thanks for the bug report. I moved this out of dahdi-linux since it will most likely need to be addressed in user space.
By: Philippe Lindheimer (p_lindheimer) 2011-02-13 23:07:56.000-0600
tested and confirmed, when no chan_dahdi.conf file is present, the introductions don't happen and the error messages is printed, but the conference still works fine. Once an empty configuration file is present, it works as before.
The error was reported with FreePBX initially, where we do not provide a chan_dahdi.conf file unless the user loads the DIgium dahdi configuration module, but that module is not needed when no hardware is configured...
By: Russell Bryant (russell) 2011-07-18 10:50:02.183-0500
I think we should just let chan_dahdi load even if it doesn't have a config file.
By: Richard Mudgett (rmudgett) 2011-08-15 12:03:51.125-0500
[^jira_asterisk_17398_v1.8.patch] Will allow chan_dahdi to create the pseudo channel when there is no chan_dahdi.conf file to load.