|Summary:||ASTERISK-07140: [patch][post 1.4] Allow reversal of message presentation order, i.e. from newest first to oldest first and optional busy msg|
|Reporter:||Joe Cracchiolo (jjcinaz)||Labels:|
|Date Opened:||2006-06-09 18:58:59||Date Closed:||2007-09-08 07:07:44|
|Environment:||Attachments:||( 0) voicemail1.patch|
|Description:||Adds two features. The first is a per-mailbox option to change the message presentation order from oldest first to newest first. This option was requested by those who keeps lots of voicemail in their mailbox. These people, who generally also have messy desks, wanted to hear the newest messages first. This option can be enabled by including the option REVERSEORDER in the options of the mailbox. For example:|
5000 => 0000,John Doe,firstname.lastname@example.org,,operator=yes|reverseorder=yes
Another option is added, called unavailfallback to force the system to play the unavailable message when no busy message has been recorded for the mailbox. Useful for cases where calls to the voicemail app with the 'b' option are used and users have neglected to record.
|Comments:||By: Joshua C. Colp (jcolp) 2006-06-09 21:32:19|
For future reference all new features should be done against trunk, as 1.2 is a bug fixing only branch. As well we are currently in a feature freeze in trunk as well, since we'll soon be releasing 1.4. Once that's done someone will gladly look at your patch!
By: jmls (jmls) 2006-10-31 11:59:27.000-0600
would you please update this patch so it can be applied to trunk. Thanks.
By: jmls (jmls) 2006-11-19 13:31:00.000-0600
would you be able to provide a patch applied against trunk for this feature ? Thanks.
By: Tilghman Lesher (tilghman) 2007-01-07 10:23:34.000-0600
Need an updated patch for trunk, please.
By: jmls (jmls) 2007-05-28 02:25:08
JJCinAZ, would you be able to provide a patch applied against trunk for this feature ? Thanks.
If not, please just let me know and I will close this.
By: Michiel van Baak (mvanbaak) 2007-09-08 07:07:43
No response for too long.
If you have an updated patch please reopen this bug and attach the patch.