<div>I've been using multiple digits successfully right from the start, about 2 or 3 weeks ago. They do the separation of *1 and *10 the same way as several other systems -- by time. If you dial *, then 1, then wait past a timeout, then 0, you'll get *1, and *10 if you did it faster. I've tested by using 3 and 34 as separate commands, and I'm using *<digit> commands on my working system. Perhaps you should try again?</div>
<div> </div>
<div>Obviously, if you were confused, the docs on this could definitely be better. I'll check out the TTS stuff in the morning, and figure out those other parameters after that. Unless the original author wants to pipe up, of course.<br>
<br></div>
<div class="gmail_quote">On Thu, Jun 18, 2009 at 7:38 PM, j3flight <span dir="ltr"><<a href="mailto:j3flight@gmail.com">j3flight@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>As far as using multiple digits in the conference controls, that doesn't seem<br>possible. I was hoping I could make all the commands require a preceding *,<br>
like *1 for mute, *2 for lock, etc but that didn't work. I'm sure that<br>could be added, but then you have other silly issues to worry about... i.e.<br>what if someone defines *1 and *10?<br><br>Anyway, the conference app is powerful, especially if you want to leverage<br>
the event socket (which I have yet to try, but I can tell that's where all<br>the goodies are). Asterisk's MeetMe has more features out of the box, but<br>is not nearly as easily customized.<br><br>I feel like mod_conference needs the following things so new folks don't go<br>
cross-eyed trying to get it to work (and I'll be more than happy to assist<br>with this where I can):<br>-- if the TTS stuff is required for other features to work, it needs to be<br>turned on by default (tts is built by default now, right?)<br>
-- a great number of the possible conference parameters are missing from the<br>default config file. I've stuck all the possibilities on the wiki (with<br>missing descriptions in many cases) but those need to be in the default<br>
config with better explanations. (or, it could be left off the wiki<br>entirely and a link to the default config file could be used, so<br>documentation is only kept in one place)<br>-- Some explanation that the "default" caller controls are HARD-CODED. I'll<br>
take a look at the wiki in just a minute and clear it up, but the config<br>file needs an explanation too. Maybe they should be commented (or removed<br>entirely) just to prove that you get the default set of caller controls<br>
without them being defined...??<br><font color="#888888">--<br>View this message in context: <a href="http://www.nabble.com/Controlling-Conference-Controls-tp24063307p24104639.html" target="_blank">http://www.nabble.com/Controlling-Conference-Controls-tp24063307p24104639.html</a><br>
</font>
<div class="im">Sent from the Freeswitch-users mailing list archive at Nabble.com.<br><br><br>_______________________________________________<br></div>
<div>
<div></div>
<div class="h5">Freeswitch-users mailing list<br><a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br><a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br>