Results 1 to 10 of 17

Thread: VM notification via SMS

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #12
    Join Date
    Jan 2009
    Posts
    22

    Default Re: VM notification via SMS

    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.

    Code:
    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:

    Code:
    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.
    Last edited by lost; 04-30-2010 at 11:23 AM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •