[asterisk-bugs] [Asterisk 0018070]: [regression] 'D' option of MeetMe does not work for 1st caller (PIN not asked)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18070 
====================================================================== 
Reported By:                mav3rick
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18070
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.14-rc1 
JIRA:                       SWP-2312 
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-28 11:42 CDT
Last Modified:              2010-10-05 12:23 CDT
====================================================================== 
Summary:                    [regression] 'D' option of MeetMe does not work for
1st caller (PIN not asked)
Description: 
The D option of MeetMe is not working anymore, at least for the first user.

Example :

exten => s,1,MeetMe(1,1DP,42)

The first user entering the conference is not asked for a PIN (bad) :

    -- Executing [s at CONFERENCE:1] MeetMe("SIP/proxy-00000002", "1,1DP,42")
in new stack
    -- Created MeetMe conference 1023 for conference '1'

While the second user is asked for a PIN (good) :

    -- Executing [s at CONFERENCE:1] MeetMe("SIP/proxy-00000003", "1,1DP,42")
in new stack
    -- <SIP/proxy-00000003> Playing 'conf-getpin.gsm' (language 'en')


Seems like dynamically created conference do not ask the pin to the 1st
user. 
Static conferences configured in meetme.conf are working as expected.

It used to work in previous versions of Asterisk (at least in 1.6.0.X).
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018006 Meetme unreliable functionality
related to          0017908 [patch] MeetMe PIN handling broken
related to          0015878 [patch] First caller to dynamic confere...
====================================================================== 

---------------------------------------------------------------------- 
 (0127703) kuj (reporter) - 2010-10-05 12:23
 https://issues.asterisk.org/view.php?id=18070#c127703 
---------------------------------------------------------------------- 
Looking at the code, and based on the existence of the 'P' flag and *'s
propensity to avoid redundant code/options, I interpreted the 'D' flag to
mean "Dynamically add conference, prompting for a PIN to be assigned to the
conference" if none was given. That behavior also is consistent with the
original issue in 0015878, where the user was prompted for a PIN twice:
once to assign it to the conference because 'D' was used and no PIN existed
yet, then one more time to enter the conference which now has a PIN
assigned.

Your understanding may well be correct, though. That's why I said the
first step should be to agree on behavior and document it in a clear and
concise manner, then the code can be adapted accordingly. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-05 12:23 kuj            Note Added: 0127703                          
======================================================================