[asterisk-bugs] [Asterisk 0011809]: Voicemail password is not reset in memory when externpass option is used

[noreply at bugs.digium.com]

The following issue has been ASSIGNED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11809 
====================================================================== 
Reported By:                davetroy
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   11809
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 99406 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             01-21-2008 16:57 CST
Last Modified:              01-22-2008 22:31 CST
====================================================================== 
Summary:                    Voicemail password is not reset in memory when
externpass option is used
Description: 
When the externpass option is used, the user's password is supposed to be
reset in the running memory, but not in the configuration file.

As of 1.4.17, 1.6.0-beta1, and trunk, this does not work.  Apparently the
password is set on the current "vmu" data structure, but needs to be
applied to the user stored in the "users" list in order to work.  This is
done with the reset_user_pw function, as is also done in
vm_change_password.

This issue was identified in 7395 and 4602, and allegedly this same fix
was applied then.  However, it is not in the current tree.  Passwords are
not correctly changed without it.

It is possible that there is some redundancy here, but this seems to be
the simplest way to achieve the desired functionality.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-22-08 22:31  Corydon76      Assigned To               => Corydon76       
======================================================================