Top Posting is bad, but it sucks when you need to reply to a HTML formatted email, and put in all the pretty >'s... So, please don't send in HTML :)
Anyway, my 0.02c worth would be to leave password (and other fields) encryption up to the individual module, this leaves it generic. However, regardless of where you store the details, I'd suggest encrypting passwords is a good idea. Just because they have root access and can read the existing voicemail/erase details, it doesn't actually reveal the password itself. This is the whole idea behind obfuscating passwords. Also, it sounds good to be able to search by first name, last name, or perhaps any other field in the database. So better is to pass the search field name rather than just f or l. ie, search by staff id, or by email address, etc... Regards, Adam Greetings, Jtodd and I have been discussing some significant changes to the way voicemail2 and app_directory interface with user data by implementing a loadable voice mail user api in both voicemail2 and directory applications. I wanted to open this discussion up a bit to the whole dev list for input before the pen hits the paper. If you are interested in this, please check out the feature request and attached notes found at the following url. http://bugs.digium.com/bug_view_page.php?bug_id=0000153 I believe this list is a better forum for continued idea discussion regarding the changes rather that the bugnotes so if you have comments, please reply to this thread. Thanks, Scrubb/Ben _______________________________________________ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev
