| Summary: | ASTERISK-08530: MeetMeJoin manager event sent when leaving room | ||
| Reporter: | Meni Livne (meni) | Labels: | |
| Date Opened: | 2007-01-09 09:37:02.000-0600 | Date Closed: | 2007-01-10 12:56:24.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_meetme |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I have a user joining a new dynamic MeetMe room, simply by having a line like exten = 901,1,MeetMe(901,d) in the dialplan. When joining the room, relevant manager events besides MeetMeJoin are fired, and "meetme list 901" in the CLI shows the user in the room. However, no MeetMeJoin event is received until the user hangs up. Only then is the relevant MeetMeJoin sent. No MeetMeLeave event is ever received. After hanging up, the user still appears in the output of "meetme list 901" in the CLI. | ||
| Comments: | By: Meni Livne (meni) 2007-01-10 12:43:44.000-0600 After inspecting, this is apparently not a bug in Asterisk or Zaptel, but is instead caused by Xen 3.0.2 on x86_64 (see http://lists.xensource.com/archives/html/xen-users/2006-07/msg00267.html ). The MeetMe application would get stuck playing the 'conf-onlyperson' file to the Zap channel, due to the RTC problem in the Xen kernel. So sorry about that. This bug can be closed. By: Joshua C. Colp (jcolp) 2007-01-10 12:56:24.000-0600 Closed - Xen issue. | ||