[asterisk-dev] [Code Review] Allow configuration of minsecs and nextaftercmd per mailbox

Tilghman Lesher tlesher at digium.com
Mon Mar 15 18:13:48 CDT 2010


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/555/#review1672
-----------------------------------------------------------



/trunk/apps/app_voicemail.c
<https://reviewboard.asterisk.org/r/555/#comment3741>

    Do we really need the compatibility option 'minmessage' for this, given that for the mailbox, it'll always be named 'minsecs'?



/trunk/apps/app_voicemail.c
<https://reviewboard.asterisk.org/r/555/#comment3743>

    I think it'd be preferable to use sscanf, since 0 is a perfectly legitimate minimum number of seconds for this option.
    
    And why copy from vmmaxsecs?  Shouldn't this be copied from vmminsecs?



/trunk/apps/app_voicemail.c
<https://reviewboard.asterisk.org/r/555/#comment3744>

    Given that these flags are copied from the global space for defaults, wouldn't it make sense to test both positive AND negative options, to ensure that the option is being parsed correctly for the mailbox and isn't just an inherited value?


- Tilghman


On 2010-03-15 17:39:17, Jeff Peeler wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/555/
> -----------------------------------------------------------
> 
> (Updated 2010-03-15 17:39:17)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> Make this work in voicemail.conf:
> 
> [default]
> 1234 => 4242,Example Mailbox,imapuser at localhost,,minsecs=5|nextaftercmd=yes
> 
> 
> This addresses bug 16864.
>     https://issues.asterisk.org/view.php?id=16864
> 
> 
> Diffs
> -----
> 
>   /trunk/apps/app_voicemail.c 252626 
> 
> Diff: https://reviewboard.asterisk.org/r/555/diff
> 
> 
> Testing
> -------
> 
> Tested both options to ensure they were respected and have also created a unit test that checks to see if the vm_user struct is populated correctly (I guess it'll protect against accidental deletions or typos).
> 
> 
> Thanks,
> 
> Jeff
> 
>




More information about the asterisk-dev mailing list