[asterisk-bugs] [Asterisk 0011789]: Wrong behaviour using "d" and "D" options in MeetMe(confno, d/D, pin)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11789 
====================================================================== 
Reported By:                ibc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11789
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-17-2008 16:34 CST
Last Modified:              01-18-2008 02:42 CST
====================================================================== 
Summary:                    Wrong behaviour using "d" and "D" options in
MeetMe(confno,d/D,pin)
Description: 
The doc says:
     'd' -- dynamically add conference
     'D' -- dynamically add conference, prompting for a PIN

But try this:

exten => 1,1,MeetMe(1,D,1234)
exten => 2,1,MeetMe(2,D)
exten => 3,1,MeetMe(3,d,1234)
exten => 4,1,MeetMe(4,d)


And call to each one:

  1: It doesn't ask for pin -> ¿?¿
  2: It asks for pin -> OK
  3: It doesn't ask for pin -> ¿?¿
  4: It doesn't ask for pin -> OK

So cases 1 and 3 are unexpected. IMHO they should be:

  1: It asks for pin (1234)
  2: It asks for pin (user provided)
  3: It asks for pin (1234)
  4: It doesn't ask for pin

Yes, cases 1 and 3 are the same. I think that "D" options should ask for
user provided pin just in case pin is not defined in "MeetMe()". About case
3 I'm not sure of what should be the behaviour.


But in conclusion, for now is not possible to create a dynamic conference
with fixed pin (not user provided when creating the conference).
====================================================================== 

---------------------------------------------------------------------- 
 ibc - 01-18-08 02:42  
---------------------------------------------------------------------- 
> It's not that it necessarily asks for a pin, but rather that it FORCES
the
> conference to have a pin.

Sorry but I don't understand what you mean.
The fact is that "exten => 1,1,MeetMe(1,D,1234)" doesn't ask for PIN. Do
you say htis is the expected behaviour? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-18-08 02:42  ibc            Note Added: 0080849                          
======================================================================