[asterisk-bugs] [Asterisk 0013241]: [patch] Ability to force forwarding WITH comment

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Aug 7 13:29:47 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13241 
====================================================================== 
Reported By:                jaroth
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   13241
Category:                   Applications/app_voicemail/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 130693 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-05 14:25 CDT
Last Modified:              2008-08-07 13:29 CDT
====================================================================== 
Summary:                    [patch] Ability to force forwarding WITH comment
Description: 
This patch adds a configuration keyword to the voicemail.conf file called
"forcecomment".  The default is "no".  When set to "yes", voicemail users
will not be given the choice to forward with comment or forward without
comment.  Voicemail will go right into recording the comment.

====================================================================== 

---------------------------------------------------------------------- 
 (0091209) Corydon76 (administrator) - 2008-08-07 13:29
 http://bugs.digium.com/view.php?id=13241#c91209 
---------------------------------------------------------------------- 
The problem with this is that it's a policy question masquerading as a
feature patch.  Note that it's very simple to evade the requirement of a
prepend: even 20ms of prepended sound counts as a prepend succeeding.

The only way to succeed with such a policy question is simply to require
your staff to prepend a message, and enforcing this policy.  It is
otherwise an ineffective solution. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-07 13:29 Corydon76      Note Added: 0091209                          
======================================================================




More information about the asterisk-bugs mailing list