[asterisk-bugs] [Asterisk 0015707]: [patch] Passing the mute flag to MeetMe() makes the new user have "muted" himself, not an admin mute
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Aug 17 15:56:39 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15707
======================================================================
Reported By: modelnine
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15707
Category: Applications/app_meetme
Reproducibility: always
Severity: feature
Priority: normal
Status: feedback
Asterisk Version: 1.6.1.2
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-08-12 15:55 CDT
Last Modified: 2009-08-17 15:56 CDT
======================================================================
Summary: [patch] Passing the mute flag to MeetMe() makes the
new user have "muted" himself, not an admin mute
Description:
Generally, in the scenarios I deploy app_meetme in, using a dialplan-flag
for muting a joining user means that the respective user is a spectator
(who can later be invited to speak), so the listener flag does not apply to
this scenario.
The attached patch changes the semantics of the mute flag to mean that the
user has been admin muted on joining, not self-muted, which can be reversed
by simply going to his menu.
This is a change in semantics of the mute flag, which I find rather more
intuitive. But adding a separate flag to make a joining user have been
admin muted would similarly be sensible.
======================================================================
----------------------------------------------------------------------
(0109181) modelnine (reporter) - 2009-08-17 15:56
https://issues.asterisk.org/view.php?id=15707#c109181
----------------------------------------------------------------------
Perfectly sensible to create a new option (or rather option argument) for
this, as it changes existing semantics. I'm currently testing the attached
patch, which adds an option argument to m, which can either be m(a) or not.
In case an 'a' is found in the option argument, an admin mute is given on
connect, otherwise a normal mute.
The attached patch also includes a more comprehensive fix for
https://issues.asterisk.org/view.php?id=15704,
which I can't set into relation with the patch (and so I've posted the
patch there, too).
Issue History
Date Modified Username Field Change
======================================================================
2009-08-17 15:56 modelnine Note Added: 0109181
======================================================================
More information about the asterisk-bugs
mailing list