Summary: | ASTERISK-05677: [patch] users change their mailbox password, and these changes are lost after an asterisk reload | ||
Reporter: | Manuel Merelles (manuel) | Labels: | |
Date Opened: | 2005-11-22 13:23:15.000-0600 | Date Closed: | 2008-01-15 15:57:43.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_voicemail |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) vminclude.patch | |
Description: | We configure the global voicemail parameters at voicemail.conf, and we use the INCLUDE sentence in a per context basis having one vm-customer.conf file per customer context in order to facilitate customer provisioning and administration. The users get access to their mailboxes, they're allowed to change their mailboxes passwords as well, but after an asterisk reload all password changes are loss. Example: voicemail.conf global param global param #include "vm-customer-a.conf" #include "vm-customer-b.conf" vm-customer-a.conf [customera] 1010 => 1010, User1 1011 => 1011, User2 vm-customer-b.conf [customerb] 2010 => 2010, User1 2011 => 2011, User2 After a couple of tests we have realized that if we configure the contexts and user mailboxes at the voicemail.conf (main asterisk file) it works fine, even if we reload the asterisk because the changes were written down to the voicemail.conf file. But if we configure the context and user mailboxes in external files as described above, the asterisk seems not to be able to apply the changes to the files losing the password changes after a reload. | ||
Comments: | By: Russell Bryant (russell) 2005-11-22 15:04:04.000-0600 Yes, it is known that #include's are not going to work for voicemail.conf. It's just a feature that is not currently supported for voicemail.conf. I think we should add the message in the attached patch to voicemail.conf.sample. By: Manuel Merelles (manuel) 2005-11-22 16:10:42.000-0600 Thanks for your prompt response and the advise. We'll try to figure out some workaound, becasue we have more than 700 hundred mailboxes split in several files. By: Russell Bryant (russell) 2005-11-22 19:40:11.000-0600 You would probably find that storing the configuration in a database, using the Realtime database configuration engine, would be a more manageable solution to your problem. By: Russell Bryant (russell) 2005-11-23 01:11:47.000-0600 I have added a note to the sample configuration file in both cvs head and v1-2. Thanks! By: Digium Subversion (svnbot) 2008-01-15 15:57:42.000-0600 Repository: asterisk Revision: 7191 U branches/v1-2/ChangeLog U branches/v1-2/configs/voicemail.conf.sample ------------------------------------------------------------------------ r7191 | russell | 2008-01-15 15:57:42 -0600 (Tue, 15 Jan 2008) | 2 lines issue ASTERISK-5677 ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=7191 By: Digium Subversion (svnbot) 2008-01-15 15:57:43.000-0600 Repository: asterisk Revision: 7192 U trunk/ChangeLog U trunk/configs/voicemail.conf.sample ------------------------------------------------------------------------ r7192 | russell | 2008-01-15 15:57:43 -0600 (Tue, 15 Jan 2008) | 2 lines issue ASTERISK-5677 ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=7192 |