[asterisk-bugs] [Asterisk 0017317]: MeetMe 'L' and 'S' ignore 'C' option

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17317 
====================================================================== 
Reported By:                var
Assigned To:                seanbright
====================================================================== 
Project:                    Asterisk
Issue ID:                   17317
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.7 
JIRA:                       SWP-1441 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-05-10 20:41 CDT
Last Modified:              2011-01-29 11:54 CST
====================================================================== 
Summary:                    MeetMe 'L' and 'S' ignore 'C' option
Description: 
Using MeetMe with options 'S' or 'L', in conjunction with 'C' fails. When
the time-limit is up (L or S) the user's channel is given a soft hangup
instead of following the context as expected. If the user is kicked using
MeetMeAdmin or MeetMeChannelAdmin, it does follow context as expected.

Meetme 'L' option does not state that line will be hungup - though it does
not state that it will not be hungup either:

    'L(x[:y][:z])' - Limit the conference to 'x' ms. Play a warning when
'y' ms are
    left. Repeat the warning every 'z' ms.

Meetme 'S' option does not state that the line will be hungup, it states
the user will be 'kicked' from the conference. This would create an
assumption that 'C' flag would be utilised and the context followed,
however this is not the case:

    'S(x)' -- Kick the user 'x' seconds *after* he entered into the
conference.
    'C' -- continue in dialplan when kicked out of conference


The above was tested with:

* Asterisk 1.6.1.18, dahdi 2.2.1, libpri 1.4.10.2 with a Digium TE220 card
on Debian 5.0.4 (x86)
* Asterisk 1.6.2.7, DAHDI 2.3.0, libpri 1.4.10.2 with a Digium TE220 card
on Debian 5.0.4 (x86)
====================================================================== 

---------------------------------------------------------------------- 
 (0131209) svnbot (reporter) - 2011-01-29 11:54
 https://issues.asterisk.org/view.php?id=17317#c131209 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 304774

_U  branches/1.8/
U   branches/1.8/apps/app_meetme.c

------------------------------------------------------------------------
r304774 | seanbright | 2011-01-29 11:54:44 -0600 (Sat, 29 Jan 2011) | 16
lines

Merged revisions 304773 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.6.2

........
  r304773 | seanbright | 2011-01-29 12:51:28 -0500 (Sat, 29 Jan 2011) | 9
lines
  
  When we pass the S() or L() options to MeetMe, make sure that we honor C
as well.
  
  Without this patch, if the user was kicked from the conference via the
S() or L()
  mechanism, we would just hang up on them even if we also passed C
(continue in
  dialplan when kicked).  With this patch we honor the C flag in those
cases.
  
  (closes issue https://issues.asterisk.org/view.php?id=17317)
  Reported by: var
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=304774 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-29 11:54 svnbot         Checkin                                      
2011-01-29 11:54 svnbot         Note Added: 0131209                          
======================================================================