[asterisk-bugs] [Asterisk 0019273]: [patch] app_privacy arguments reference invalid "options" option, interferes with "context" option

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19273 
====================================================================== 
Reported By:                mdavenport
Assigned To:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   19273
Category:                   Applications/app_privacy
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                       SWP-3456 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-05-11 09:50 CDT
Last Modified:              2011-05-27 15:45 CDT
====================================================================== 
Summary:                    [patch] app_privacy arguments reference invalid
"options" option, interferes with "context" option
Description: 
app_privacy has an "options" application argument defined, but it's not
actually used.  This interferes with the use of the "context" option,
since, as documented, you can't use the "context" option.

Attaching patch to remove "options" option, since there's nothing in
app_privacy.c that references it otherwise.
====================================================================== 

---------------------------------------------------------------------- 
 (0135508) lmadsen (administrator) - 2011-05-27 15:45
 https://issues.asterisk.org/view.php?id=19273#c135508 
---------------------------------------------------------------------- 
I disagree. If anyone else had actually figured out the order of the fields
and wrote dialplan matching what the code actually does, then we break
their dialplan.

We need to update the documentation for 1.8 to match the code, and in
trunk we can update the code to do what we feel is right, update CHANGES
and UPGRADE.txt, then make the documentation match what is actually there. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-27 15:45 lmadsen        Note Added: 0135508                          
======================================================================