| Summary: | ASTERISK-06628: [patch] Add manager events to report meetme mute/unmute actions | ||
| Reporter: | nicolasg (nicolasg) | Labels: | |
| Date Opened: | 2006-03-27 17:30:37.000-0600 | Date Closed: | 2006-05-08 06:26:26 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_meetme |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) app_meetme_mute.patch | |
| Description: | Very minor patch that adds manager events for reporting when a user was muted/unmuted. It does not add new manager actions to mute/unmute, just reports the state change. ****** ADDITIONAL INFORMATION ****** Event: MeetmeMute Privilege: call,all Meetme: 901 Usernum: 2 Event: MeetmeUnmute Privilege: call,all Meetme: 901 Usernum: 2 | ||
| Comments: | By: Tilghman Lesher (tilghman) 2006-03-28 12:00:13.000-0600 I'm wondering if this might be better off as a more generic event, such as: Event: Meetme Subevent: Mute Conference: 100 User: 2 Event: Meetme Subevent: Unmute Conference: 100 User: 2 I'd like to avoid top level namespace pollution as much as possible. By: nicolasg (nicolasg) 2006-03-28 12:43:50.000-0600 It is ok by me. I have just used similar meetme events as the ones we have now: Event: MeetmeJoin Event: MeetmeLeave OEJ is (re)organizing manager events. I will go with whatever Event/Namespace you guys decide. By: Matt O'Gorman (mogorman) 2006-05-08 06:26:25 Committed revision 25447. with minor changes | ||