VM notification via SMS

[rcrcr]

Lost:

Would you mind posting your sieve rule here for the benefit of others?

Thanks!

rcrcr

[lost]

1. On VPanel, set the email to "voipo_vm_sms@mydomain.com"

2. Added the Sieve rule below, which rearranged and squeezed the original message before sending it to mine and wife's phone. I then filed it to the trash folder because there's already another email notification with the voice attachment in the inbox.

require ["envelope", "fileinto", "imapflags", "reject", "notify", "vacation", "regex", "relational", "comparator-i;ascii-numeric", "copy"];

if header :contains ["to"] "voipo_vm_sms@mydomain.com"  {
  notify :method "mailto" :options ["cellphone1@messaging.sprintpcs.com", "Squeeze", "Low", "From", "Orig"] :message "$subject$ / $text[47]$ / $subject$ 
VM:8328387000"; 

  notify :method "mailto" :options ["cellphone2@messaging.sprintpcs.com", "Squeeze", "Low", "From", "Orig"] :message "$subject$ / $text[47]$ / $subject$ 
VM:8328387000";

  fileinto "INBOX.Trash";
  stop;
}

Tim,

The original message from VOIPO is, as noted by another poster, is in MIME multipart and in turn gets munged by the SMS gateway:

Content-Type: multipart/mixed; boundary="XXXX_boundary_XXXX"
From: "703abcdefg" <703abcdefg@sip.voipwelcome.com>
To: <voipo_vm_sms@mydomain.com>
Subject: Voicemail from "703xyzxxxx" <703xyzxxxx> 00:00:24
X-Priority: 3
X-Mailer: FreeSWITCH
X-Voicemail-Length: 24
Message-Id: <20100430165453.D189939945@vm-v01.voipwelcome.com>
Date: Fri, 30 Apr 2010 16:54:53 +0000 (UTC)


--XXXX_boundary_XXXX
Content-Type: multipart/alternative; 
	boundary="000XXX000"

--000XXX000
Content-Type: text/plain; charset=ISO-8859-1; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Created: Friday, April 30 2010, 11 54 AM
From: "703xyzxxxx" <703xyzxxxx>
Duration: 00:00:24
Account: 703abcdefg@sip.voipwelcome.com
--000XXX000--


--XXXX_boundary_XXXX--

Those users who receive the SMS on their phone with just the bolded, underlined part are lucky because that means the email-to-SMS gateway used by their providers understand MIME multipart, but that's not the case with mine (Sprint, and previously T-Mobile).

If there's a way to configure the FreeSWITCH mailer to not compose the message in MIME multipart, that would help.

[lost]

Just a quick thought, using an external mailer is possible:

http://wiki.freeswitch.org/wiki/Mod_...email_to_Email

The API feature is pretty rich which, as a developer, got me pretty excited to see the possibilities (but yes, it's like opening a pandora box for a widely deployed service like VOIPo).

Most exciting of them, from the FAQ section:

Do I need a text-to-speech engine installed?

No, it will work with sound files or a text-to-speech engine.

[rcrcr]

Lost:

Thanks for that sieve rule. Very helpful.

Best,
rcrcr

[msp]

1. Searching this forum for "sms" indeed yields no results. (?)
2. SMS notification for me worked perfectly with AT&T. Not so since I switched to T-mobile (I received it as an MMS which I couldn't open). After some google searches, it's pretty clear that it's T-mobile's issue. Oh well. Now I just use a mail filter in yahoo mail to send an alert to my phone.

[usa2k]

1. Searching this forum for "sms" indeed yields no results. (?)

It would be nice if http://forums.voipo.com/search.php allowed as few as 3 letters for search words.
Too many acronyms are 3-letter.

[PCM2]

FWIW I switched to an Android smartphone on the same carrier (T-Mobile) and VoIPo's long SMS messages are being delivered properly now. It seems to be either the BlackBerry hardware or maybe RIM's servers at T-Mobile that can't handle longer texts from VoIPo.