VoIP Mailing List Archives

[j3flight at gmail.com]

I also saw the option for the "announce-count" conference parameter (which i assume is what you're trying to use) and it didn't seem to work for me either. I couldn't figure out whether I was doing something wrong or if it was not working - that's why I implemented it in JS. Looking at the code now, do you have tts_engine and tts_voice defined in the conference config file. Looks like conference_member_say won't do anything without those...

I can definitely attest to the confusion on your second point... It took me a while to figure out the "default" conference controls as well. As long as you name your caller-controls something else, it all works great. The easy fix would be to modify the included conference config file so that the sample conference controls had a different name. If someone removed them manually, it would work as advertised.

The wiki doc for mod_conference still needs some help too. I tried to fill in what I knew recently by adding all the options I could find in the source and re-arranging the page to make it easier to understand for new folks. I had to leave a bunch of ??? in places though because I didn't know what something did or meant... Can anyone help complete that?

[bjbrashier at gmail.com]

I was indeed looking at "announce-count", but from the code, it looks like that was designed to announce to the caller how many people were on the conference only when they were joining and the number was over a threshold specified in the profile. Not exactly what I was looking for, but it did help me find some of the right variables. And no, it didn't work, but I see now that it's most likely because conference_member_say wasn't working.
 
I didn't think to try to define tts_engine and tts_voice, though, thinking that things like that had likely defaults. Obviously that would be an issue if not. I'll look at that next.
 
Don't quote me on what announce-count is supposed to do, yet -- I only looked at it for long enough to tell that it wasn't what I needed. Once I have things working the way I want, I feel like I'll have enough data to be more certain of what everything does, and then I'll be happy to help you fill those out.

I like your solution on the default controls. Naming them "sample" instead of "default" would do fine. Alternately, if we put a blurb in the comments above the default controls saying "these controls are hard-coded, and changes will not be taken into account. They are here as an example only", that would probably be good enough.
 
Also, it's not clear that the DTMF commands for caller controls can be multiple digits. It might go without saying, but I didn't think about it until a little ways in, so something on the wiki might be nice.

On Thu, Jun 18, 2009 at 5:01 PM, <j3flight@gmail.com (j3flight@gmail.com)> wrote:

[j3flight at gmail.com]

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.


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[bjbrashier at gmail.com]

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?
 
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.


On Thu, Jun 18, 2009 at 7:38 PM, j3flight <j3flight@gmail.com (j3flight@gmail.com)> wrote:

[j3flight at gmail.com]

Well crap, I must have had something else screwed up then with the
multiple digits... I will try it out again soon, thanks for putting me
back on track. I made some more changes to the wiki that hopefully
clean up some confusion on a few things like the caller-controls.


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[bjbrashier at gmail.com]

Actually, that's another good reason to do those wiki and/or code & comments changes... most likely, the reason you thought it couldn't be done is that you tried it and it didn't work... but you tried it on the default profile before you realized that it was hard coded. I know that's what I did and was confused about at first.
 
I want to take a second and point out that while I may be complaining about some difficulties I'm having, the process has actually been FAR easier and faster than I had ever expected. This is a nice, solid product that works amazingly well amazingly quickly. I've been working with it for exactly 5 weeks now, starting from not knowing what SIP was or even that it had anything to do with VoIP. I've got a decent, demo conference bridge working, and am likely to be saving my company a good chunk of change as soon as I work out a few more kinks. A 2-month time to market from complete zero is just incredible.


On Thu, Jun 18, 2009 at 9:45 PM, <j3flight@gmail.com (j3flight@gmail.com)> wrote:

[jason at jasonjgw.net]

Bradley Brashier <bjbrashier@gmail.com> wrote:

[bjbrashier at gmail.com]

OK, I figured out the TTS stuff. It's a matter of choosing an engine (I chose flite), uncommenting a few things, and setting the TTS variables in the conference profile. You do have to rebuild FS to do this.
 
With that working, my count function works, too.
 
I posted a bug last night about conferencing, BTW: if you're using the wait-mod function, where the conference doesn't start until the moderator arrives, and you're also using separate profiles for users and moderators, the users only have the "user" profile until the first moderator arrives. At that time, they switch to also be using the "moderator" profile.
 
Now that TTS is working, I'm going to see about helping you fill out those ???s, and maybe see if I can figure out how to fix the above bug.
 
BB

[bjbrashier at gmail.com]

So it turns out that it wasn't a bug at all -- it is a feature that was not implemented. So I've got some work to do to get that running. Since I said I would, though, here's my analysis of the conference parameters you were asking about:
 
mute-detect-sound
Different sound for if muting using only when mute-detect flag is on.

max-members
Specifies the maximum number of participants in a call.

max-members-sound
If caller cannot join because max is reached, this sound plays. Recommended if max-members is set.

comfort-noise-level
Sets volume of background white noise to generate.

announce-count
Requires TTS. When joining, tells caller how many callers are already in conference if at least the specified minimum.

suppress-events
? Sets a flag, but does not appear to do anything with it.

verbose-events
Maximum verbosity for transcripting.

timer-name
Specifies the name of this profile's timer. To separate it from other timers?
 
BB

On Fri, Jun 19, 2009 at 8:59 AM, Bradley Brashier <bjbrashier@gmail.com (bjbrashier@gmail.com)> wrote:

[bjbrashier at gmail.com]

[jmesquita at gmail.com]

Inline...

On Fri, Jun 19, 2009 at 3:27 PM, Bradley Brashier <bjbrashier@gmail.com (bjbrashier@gmail.com)> wrote:

[bjbrashier at gmail.com]

That sounds like something it might do, but searching through the code I didn't find any use of the flag that parameter sets. It is, of course, possible that I missed it, especially if it's an indirect use.

2009/6/19 João Mesquita <jmesquita@gmail.com (jmesquita@gmail.com)>