[Freeswitch-users] Controlling Conference Controls

j3flight j3flight at gmail.com
Thu Jun 18 19:38:44 PDT 2009


As far as using multiple digits in the conference controls, that doesn't seem
possible.  I was hoping I could make all the commands require a preceding *,
like *1 for mute, *2 for lock, etc but that didn't work.  I'm sure that
could be added, but then you have other silly issues to worry about...  i.e.
what if someone defines *1 and *10?  

Anyway, the conference app is powerful, especially if you want to leverage
the event socket (which I have yet to try, but I can tell that's where all
the goodies are).  Asterisk's MeetMe has more features out of the box, but
is not nearly as easily customized.  

I feel like mod_conference needs the following things so new folks don't go
cross-eyed trying to get it to work (and I'll be more than happy to assist
with this where I can):
-- if the TTS stuff is required for other features to work, it needs to be
turned on by default (tts is built by default now, right?)
-- a great number of the possible conference parameters are missing from the
default config file.  I've stuck all the possibilities on the wiki (with
missing descriptions in many cases) but those need to be in the default
config with better explanations.  (or, it could be left off the wiki
entirely and a link to the default config file could be used, so
documentation is only kept in one place)
-- Some explanation that the "default" caller controls are HARD-CODED.  I'll
take a look at the wiki in just a minute and clear it up, but the config
file needs an explanation too.  Maybe they should be commented (or removed
entirely) just to prove that you get the default set of caller controls
without them being defined...??
-- 
View this message in context: http://www.nabble.com/Controlling-Conference-Controls-tp24063307p24104639.html
Sent from the Freeswitch-users mailing list archive at Nabble.com.





More information about the FreeSWITCH-users mailing list