[Home]

Summary:ASTERISK-13049: [patch] Voicemail password does not save properly
Reporter:Darryl Chandler (darrylmc)Labels:
Date Opened:2008-11-11 11:20:56.000-0600Date Closed:2008-11-19 11:21:33.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_voicemail
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) 20081113__bug13876.diff.txt
Description:When using the VoiceMailMain application to change the mailbox password, the prompt requests the user to enter the password, followed by the pound key. If you do not enter the pound key, the process continues and asks the user to re-enter the passsword followed by the pound key. If the user does not hit the pound key, the application continues to the 'options' menu greeting, and does not let the user know the password was not changed.

****** ADDITIONAL INFORMATION ******

Only the second prompt to re-enter the password followed by the pound key seems to make a difference. Doesn't matter if you used the pound key or not during the initial password entry prompt; as long as you use it on the second one, it works.
Comments:By: Darryl Chandler (darrylmc) 2008-11-11 11:22:37.000-0600

Same behaviour exists in 1.2.13. Just mentioning this to show it's not a new bug in this version.
By: Jared Smith (jsmith) 2008-11-11 11:31:51.000-0600

I've confirmed that this does indeed take place.
By: Tilghman Lesher (tilghman) 2008-11-13 19:38:07.000-0600

Fix uploaded for 1.4, but it shouldn't be very different for 1.6.  Note that since this is a bug, not a regression, it is not a candidate for inclusion in 1.6.0, but may be fixed in both 1.4 and 1.6.1.
By: Leif Madsen (lmadsen) 2008-11-19 11:05:41.000-0600

I can't seem to reproduce this in latest 1.4 branch (rev 157503). I'll try again on 1.4.22 proper, but I haven't patched, and I didn't use the # key to verify the password, it just seemed to work fine for me.
By: Leif Madsen (lmadsen) 2008-11-19 11:20:11.000-0600

Well this is definitely an issue on 1.4.22 as I reproduced it, but the issue is gone as of at least r157503 in 1.4, although I didn't go back to try and find where it may have gotten fixed.

Closing the issue as it appears putnopvut fixed without closing the issue :) (per Tilghman)
By: Leif Madsen (lmadsen) 2008-11-19 11:21:33.000-0600

This issue was fixed by putnopvut but some reason this issue didn't get closed (maybe this was during the bots being down?) Anyways it was fixed and this issue is now closed. w00t!

Fixed in revision 156816.