VoIP Mailing List Archives

[mcollins at fcnetwork.com]

[nicholas at gnial.com.br]

Deliver the vm message physically.

[mike at jerris.com]

On Oct 8, 2008, at 3:21 PM, Nicholas Amorim wrote:

[anthony.minessale at g...]

you can email them ?


On Wed, Oct 8, 2008 at 5:10 PM, Nicholas Amorim <nicholas@gnial.com.br (nicholas@gnial.com.br)> wrote:

[nicholas at gnial.com.br]

Yes, I can email them. But certainly would be more interesting to add a event to voicemail received. It opens a wide whole world of possiblities Including real-time alerts, etc.

The info that I need:

Which user received the voicemail
Access to the file which voicemail was recorded
Date/Time of received voicemail

Just that, I guess. I would capture the event, send all those infos through an url and then delete the voicemail from the machine.

The url receives it and stores on a database, making it kinda scalable.

On Wed, Oct 8, 2008 at 7:38 PM, Anthony Minessale <anthony.minessale@gmail.com (anthony.minessale@gmail.com)> wrote:

[shawnl at waterwheelne...]

I might add the following if available as well

CallerID
LengthOfCall/Message

(Does FS have a voicemail priority flag?) If so I would add the priority


Can there also be added an event to when a call is transferred into
voicemail (not sure if the doesnt already exist)

I can see where monitoring the events, getting an event when the call
has been transferred into voicemail would be useful.

Shawn

Nicholas Amorim wrote:

[mike at jerris.com]

Voicemail metadata is already stored in a database (of your choice via odbc) and if you store the files on some remotely mountable location you should get the same effect. I'll try to throw an event in today but I think some of what your trying to do is already done for you.

Mike

On Oct 8, 2008, at 8:25 PM, Nicholas Amorim wrote:

[anthony.minessale at g...]

All of that information is already in the email =D
you can template out the email with all that data which is expanded on the fly per message.

by the time we finished adding what you want we will have recreated SMTP from scratch


On Wed, Oct 8, 2008 at 7:34 PM, Michael Jerris <mike@jerris.com (mike@jerris.com)> wrote:

[peder at networkoblivi...]

I think what he wants is to have some remote server get the events and
the email so that users can access it from the remote server, not FS.
He doesn't want it emailed to the end user.

Anthony Minessale wrote:

[anthony.minessale at g...]

Right,

I understand that. But if you look at it from another paradigm, you have 2 choices.

1) You can email it to your own back end program that can do whatever it wants with the email.
The email *is* an event with the message attached and as a bonus you have guaranteed delivery.

2) You can short circuit the email program in the core by setting the mailer settings to some program
that is not actually an email program but a program that inhales the email file and again does whatever
it wants with the message. (see figure 1)
The FreeSWITCH eventing system would have to inhale the entire thing into
memory to deliver it and the end result would look identical to, well, an email.

3) In either case the email template can contain anything you choose including any channel variables
and several other special voicemail specific values as can be seen in the default template.
There is nothing stopping you from formatting the email body to contain machine readable presentation
of the parameters so when you feed the message to a program it can be parsed easily.


Anyway, what do I know, *shrug*

Figure 1
in switch.conf.xml you could change these to your own program or a perl script etc.
<param name="mailer-app" value="sendmail"/>
<param name="mailer-app-args" value="-t"/>



On Thu, Oct 9, 2008 at 8:28 AM, peder@networkoblivion.com (peder@networkoblivion.com) <peder@networkoblivion.com (peder@networkoblivion.com)> wrote: