Asterisk 1.8.x app_meetme.so
Tags: app, asterisk, Cmd, ConfBridge, logs, MeetMe, source file
Hello,
I can’t seem to use MeetMe app in asterisk versions beyond 1.8. Its source
file app_meetme.c is present in the apps dir. Also, I can find app_meetme
change-logs on the asterisk website. However, the dialplan doesn’t have
this cmd. I have checked menuselect but it says it has been replaced by
app_confbridge.
Also, If that *is* the case, does ConfBridge (the newer version of meetme)
offer the same options? How do I use them?
Doug Lytle said:
Feb 22, 12 at 9:03 am[Digital^Dude] ® wrote:
It’s still available, but marked as depreciated. So, do a make
menuselect, Applications, scroll all the way to the bottom and check meetme.
Doug
[Digital^Dude] said:
Feb 22, 12 at 9:07 amI did, and I mentioned it in my earlier email too.
Screenshot attached.
Doug Lytle said:
Feb 22, 12 at 9:22 am[Digital^Dude] ® wrote:
You mentioned that the meetme source was there, I was guessing that the
option to compile wasn’t checked so the binary wasn’t available.
I just ran into this myself yesterday when converting a 1.4x box (Still
in progress) to a 10.2.0 RC2 and once checked and re-compiled, meetme
was available.
Doug
"Matthew Jordan" said:
Feb 22, 12 at 10:19 amAbdul Basit said:
Feb 22, 12 at 10:24 amConfBridge is not much flexible as MeetMe.
[Digital^Dude] said:
Feb 22, 12 at 11:23 amDoug, I can find the following in asterisk 10 changelogs:
The following error will consistently
occur when trying to dial into 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?) 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 by FreePBX if
hardware does not exist, causing MeetMe to be unable to open a
DAHDI pseudo channel. * Allow chan_dahdi to create a pseudo
channel when there is no chan_dahdi.conf file to load. (closes
issue ASTERISK-17398) Reported by: Preston Edwards
This would mean that meetme should not have dahdi as a compilation
dependency.
source:
http://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-10-current
"Kevin P. Fleming" said:
Feb 22, 12 at 12:28 pmNo, this is incorrect. First, you are confusing DAHDI and chan_dahdi.
MeetMe absolutely requires, and will always require DAHDI, because DAHDI
is used for mixing the audio streams together into conferences.
Second, MeetMe also requires chan_dahdi to be loaded, and prior to the
patch you listed above, this required a chan_dahdi.conf file to be
present. The patch listed above changed changed chan_dahdi to load in a
very ‘basic’ configuration when no chan_dahdi.conf file is present.