Summary:ASTERISK-09761: User in meetme once muted is unable to access menu while muted (and therefore can't unmute self)
Reporter:Steve Feinstein (stevefeinstein)Labels:
Date Opened:2007-06-26 14:22:44Date Closed:2007-07-06 19:18:18
Versions:Frequency of
Environment:Attachments:( 0) full.log
Description:If you enter a  meetme conference with the 's' parameter to enable the star menu, then enter the conference, for example


When dialing the extension 1234567, you'll hear "You're currently the only person in this conference" then a beep.

Then if you press * you'll get the menu as normal.  All functions seem to work as advertised.  
If you mute yourself with *1, you will be unable to access the menu again.

The DTMF log shows the DTMF was received and interpreted correctly.  But nothing  seems to happen.

If from the console you execute the command:
meetme unmute 3141592 1
Then all the DTMF that had been entered by that user up to that point will then be executed in the order they were keyed in.


This problem has been there since at least 1.4.0, and probably 1.2.  I've just tested against trunk (revision 71895), and 1.4.4.

Maybe related to Bug 009418
Comments:By: Joshua C. Colp (jcolp) 2007-06-26 18:56:03

Can you please provide console output, rtp debug, and enable dtmf logging in logger.conf? Thanks.

By: Steve Feinstein (stevefeinstein) 2007-06-27 12:00:35

Log attached.  You can see where appropriate sound files are played after menu keypresses, but once muted there are no sounds played (But DTMF events are logged) for each keypress until I entered the "meetme unmute <conf> all".

By: Steve Feinstein (stevefeinstein) 2007-06-27 12:02:53

Also interesting that when muted, the music on hold stops.  when unmuted it resumes.  This will create a significant voice delay in the client who was muted.

I don't know if this is part of the same problem, or another bug.

By: Joshua C. Colp (jcolp) 2007-06-27 12:33:44

Fixed in 1.4 as of revision 72148 and trunk as of revision 72149.