<div class="gmail_quote">On Fri, May 29, 2009 at 6:23 PM, Giuseppe Sucameli <span dir="ltr"><<a href="mailto:brush.tyler@gmail.com">brush.tyler@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>I'm Giuseppe Sucameli and I'm taking part to GSoC 2009 for the Asterisk <br>Project.<br></blockquote><div><br>Welcome aboard!<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>My proposal is adding fully configurable menus to the Asterisk voicemail <br>application. <br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>In the current app_voicemail the menu is built into the C code and difficult <br>
to modify. <br>The alternative application minivm adds some degree of configurability, <br>but this has to go in the dialplan configuration file, which may not be <br>available to unprivileged users. In any case, mixing the voicemail and dialplan <br>
configuration is undesirable in terms of managing configuration files.<br></blockquote><div><br>I agree with Sean Bright and not sure why unprivileged users would be modifying anything on the server. Could you elaborate on what your goal is on this?<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>We can keep the voicemail configuration separate from the dialplan, <br>so the dialplan writer will only have to dispatch the call, and the voicemail <br>
config will do the rest.<br>
Then one can import/write/modify the voicemail config without having to <br>bother (or needing to have permission) to touch the dialplan itself.<br>
<br>Two file are attached (only text/plain files):<br>> brief.txt <br> explain the voicemail_menu.conf file structure and its the most <br> important functionality<br><br>> voicemail_menu.conf.txt<br>
is an example of config file to customize the voicemail menu<br>
</blockquote><div><br>There are some inconsistencies with your example which makes it a little hard to follow. You have the start = ast_vm but no ast_vm section defined, did you mean vm_menu? Also a reference to vm_setup_options when I think you meant vm_opt.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>I hope the explanation is average, maybe I have write too much or few :)<br>I wait for your questions and proposals.<br>
</blockquote><div><br>The detail was great, thanks! <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Thanks for your attention.<br>
</blockquote><div><br>I am really looking forward to customization of voicemail. It will make migrating customers much easier. However, I think this is a bit in depth. So here is an idea. For basic users: Make it so that you can change the digits dialed for the current menu items, and have the prompts say the right thing. For advanced users: export the menu items as dialplan functions (maybe have a global variable in voicemail.conf to turn this on/off?) so that users can create a more dynamic voicemail application if they so choose. It would also be nice to add some more (admin controlled) abilities for the users to change more options (like turning on/off attachments for your mailbox)<br>
<br>Whatever happens, I am glad to see this project moving forward! I would be happy to help test.<br><br>-Jonathan<br><br></div></div><br>