I am pulling apart the configuration and the source for MiniVM... Until I have worked with it quite a bit you will have to excuse my minivm ignorance :) <br><br>Right now I just have one question, with minivm did you intend to have the administrator, in dialplan, use minivmrecord to place the files in /var/spool/asterisk/voicemail/1234/? On the user side, am I supposed to create a macro to use playback() to then play the message to the user when they login? <br>
<br>I know you are intending for maximum flexibility and it seems to all be grey area. I just have not seen an example of logging in and listening to your voicemail through an extension, all of the macros I see seem to throw it out in to the email ether and delete it from the disk.<br>
<br>I will wait for your ideas and suggestions.... I'm thinking I should possibly create a minivmlogin and a minivmplayback.<br><br>-- Brian McManus<br><br>
<br><br><div class="gmail_quote">On Wed, Dec 3, 2008 at 2:49 AM, Johansson Olle E <span dir="ltr"><<a href="mailto:oej@edvina.net">oej@edvina.net</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;">
<br>
3 dec 2008 kl. 10.09 skrev Tzafrir Cohen:<br>
<div><div></div><div class="Wj3C7c"><br>
> On Wed, Dec 03, 2008 at 09:14:14AM +0100, Johansson Olle E wrote:<br>
>><br>
>> 3 dec 2008 kl. 00.59 skrev Watkins, Bradley:<br>
>>><br>
>>> Off the top of my head, I would say it could be an option to<br>
>>> Record().<br>
>>> This would have the side effect of potentially being useful other<br>
>>> than<br>
>>> within minivm, but might be to fine-grained to make it practical for<br>
>>> my<br>
>>> original stated purpose. That said, it would be easy enough and<br>
>>> perhaps<br>
>>> I'll add it anyway.<br>
>>><br>
>><br>
>>> It could be and option to MinivmRecord, which would reduce the<br>
>>> proliferation of Minivm* applications (which may or may not be<br>
>>> considered a good thing or neutral). This option is also fairly<br>
>>> congruent with the current separation between what the minivm<br>
>>> applications do versus what they expect a dialplan to accomplish.<br>
>>><br>
>> The idea with minivm is to have a larger set of unique apps. Don't<br>
>> hesitate<br>
>> to create a new one if your new functionality doesn't fit into the<br>
>> existing set.<br>
>> We don't want another huge voicemail app ;-)<br>
>><br>
>>> The last option I came up with immediately was a MinivmForward app.<br>
>>> The<br>
>>> primary advantage here is that there might be some chicanery<br>
>>> that's a<br>
>>> little easier to do in C as oppposed to the dialplan, with the<br>
>>> disadvantage that then you're tied to that functionality unless you<br>
>>> want<br>
>>> to change the source and recompile (not an issue with me, but with<br>
>>> respect to users of the applications).<br>
>> I think you need a function to concatenate two recordings, or<br>
>> prepend/<br>
>> append to<br>
>> an existing prompt. Then you need the MinivmForward app - if its'<br>
>> still<br>
>> needed. After concatenating the prompt, it's just another voicemail<br>
>> to store.<br>
><br>
> Assuming you use local files as a storage, right?<br>
><br>
> And what if you don't want to assume that?<br>
<br>
</div></div>Well, we don't have anything else at this point in Mini-voicemail.<br>
If we add any other storage at some point, you're right. Then we<br>
need the MinivmForward app.<br>
<font color="#888888"><br>
/O<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br>