[asterisk-bugs] [Asterisk 0014276]: [patch] allow storage of vmsecret in users voicemail spool directory

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14276 
====================================================================== 
Reported By:                klaus3000
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14276
Category:                   Applications/app_voicemail/NewFeature
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 169203 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-19 09:33 CST
Last Modified:              2009-01-19 14:38 CST
====================================================================== 
Summary:                    [patch] allow storage of vmsecret in users voicemail
spool directory
Description: 
When secretinspool=yes in voicemail.conf, voicemail reads and writes the
secret into a file in the users voicemail spool directory. For example if
voicemail is configured for user 1234 in voicemail context foobar, then the
secret will be stored in /var/spool/asterisk/voicemail/foobar/1234/secret.

When secretinspool=no, it uses the old behavior and stores secrets into
the configuration files.

Note: realtime voiceboxes are never influenced by this parameter
====================================================================== 

---------------------------------------------------------------------- 
 (0098148) jtodd (administrator) - 2009-01-19 14:38
 http://bugs.digium.com/view.php?id=14276#c98148 
---------------------------------------------------------------------- 
I like it.  Is there any risk here without locking?  Imagine if the VM
directory is shared across many servers.  Perhaps it's too fast to worry
about locking. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-19 14:38 jtodd          Note Added: 0098148                          
======================================================================