Meetme Participants muted by Leader can UnMute Itself with*1

[fluciano]

Hi,

We are next to buy FOP2 and we have installed the Trial.

Almost Everything is Ok but to moderate Audioconferences we need that muted participants (by the leader) in the FOP2 Panel could unmute by itself using *1.

Actually if the Leader mute participants, the can't unmute by itself. They always hear the message 'conf-muted.gsm' and there is no way they can unmute itself if they want to talk.

[nicolas]

You are calling the meetme application incorrectly in your diaplan. it has nothing to do with FOP2:

This comes straight from the meetme help text in asterisk:

s: Present menu (user or admin) when '*' is received (send to menu).

In your dialplan, you are most probably passing the 's' option to meetme, if you want to change behavior, pass the correct options or the ones that suits you best.

This has nothing to do with FOP2.

Best regards,

[fluciano]

Thank you Nicolás,

The thing is that we are generating the Meetme rooms using the Elastix 2.2 GUI and we are turning on the "Allow Menu" option in the room, (Surely it sends the "s" option when it uses Meetme). The proble is that menu works for everybody (Leader / Participants) while we don't use mute using the Fop2 mute option. If the participant uses *1 without FOP2 manipulation, he can mute/unmute itself. The problem is that if with FOP2 we mute him and he uses *1 to unmute itself, he only receives the 'conf-muted.gsm' message. Thats why we thought it was related with FOP2.

We will try using hard code to construct a meetme room with the 's' option in the dialplan, and we wil tell you later if it worked or not.

Thank you Again

[fluciano]

Nicolás:

As I said in my last Reply, now I can confirm you that FOP2 is making something different to mute Leader/Users. Even users have menu optios activated, they can NOT unmute itslef if previosly using FOP2 someone has muted them. There is my very simple Dialplan and unmute is not working with *1 even menu is available for admin/users; every time they use *1 they still receive the 'conf-muted.gsm' message:

[conferences2]
exten => 5556,1,Answer
exten => 5556,n,Wait(2)
exten => 5556,n,MeetMe(,s)
exten => 5556,n,Hangup

We really like this app but we need to solve this little issue.

Thank you

Fernando Luciano

[nicolas]

FOP2 does nothing to allow or not allow things in Meetme. It justs sends AMI commands to mute/unmute. It has one catch, depending on your asterisk version and manager configuration, sometimes the initial mute state that can be set "outside" fop2 is not acknowledge, this happens mostly with confbridge, but it might happen with meetme. In that case, you need to mute "twice" from fop2 to actually send the mute command, and to let unmute work.

However, back to your post, you DO NOT HAVE TO USE THE "s" OPTION !! If you do not want users to be able to use a menu from within meetme, DO NOT USE that option. Again, it is not a fop2 thing, it's an asterisk dialplan configuration thing.

FOP2 does not change any configuration in Asterisk for anything, it justs fires up commands, and read events. Whatever happens after that is asterisk and not fop2. Try it with a custom conference where there is no "s" option, then *X will not work, fop2 or not fop2.

Best regards,

[Robertford21]

1

[Robertford21]

*1

[Robertford21]

*1