[asterisk-bugs] [Asterisk 0018006]: Meetme unreliable functionality

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18006 
====================================================================== 
Reported By:                var
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18006
Category:                   Applications/app_meetme
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.13 
JIRA:                       SWP-2275 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-09-17 00:18 CDT
Last Modified:              2010-10-22 10:02 CDT
====================================================================== 
Summary:                    Meetme unreliable functionality
Description: 
System: Debian 5.0.4
libpri: 1.4.11.4
dahdi-linux: 2.4.0
dahdi-tools: 2.4.0
asterisk: 1.6.2.13

Setup: Fragmented E1, TE220 (4th Gen)

Using the below ael context, MeetMe will choose to randomly do one of four
functions instead of the expected function of "Don't play any audio files,
drop users into MeetMe inconspicuously". This currently removes the ability
to use 1.6.2.x MeetMe in a professional deployment, leaving us to currently
stay with 1.6.1.x:

 * Work as expected (60% of the time)
 * Mute one or both users (shouldn't happen)
 * Play audio message conf-onlyperson to user (shouldn't happen with the
flags given)
 * Prompt user for introduction message (shouldn't happen with the flags
given)

Note: This setup works without issue on 1.6.1.x, wanting to migrate to
1.6.2.x but this issue has been prevalent since at least 1.6.2.7