| Summary: | ASTERISK-06424: [patch] A minor issue in meetme join/leave manager events | ||
| Reporter: | Moqtadir Mohammed (imran) | Labels: | |
| Date Opened: | 2006-02-26 02:59:51.000-0600 | Date Closed: | 2006-05-25 16:06:56 |
| Priority: | Trivial | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_meetme |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) patch.diff | |
| Description: | In the current meetme code there is a remote possibility that a MeetmeJoin manager event may be reported more than once for the same user, and also a MeetmeLeave manager event may be sent without a MeetmeJoin event sent in the first place. I have added a flag to make sure that it sends only one MeetmeJoin and also no MeetmeLeave event without a corresponding MeetmeJoin event. | ||
| Comments: | By: Moqtadir Mohammed (imran) 2006-02-26 03:02:36.000-0600 This is my first bug post! Faxed my disclaimer with name Imran Ahmed! By: Serge Vecher (serge-v) 2006-05-03 15:50:18 imran: do you have console logs of such an event occuring? By: Moqtadir Mohammed (imran) 2006-05-03 18:51:50 vechers: No, But it is very obvious in the code itself. For example when a user hangs up when meetme initially plays conf-onlyperson or conf-thereare, a meetmeleave event will be generated without a meetmejoin event sent in the first place. Please let me know if this patch no longer applies, I will update it. Thanks By: Joshua C. Colp (jcolp) 2006-05-25 16:06:56 Fixed in trunk as of revision 30409. Thanks a lot! | ||