VM notification via SMS

[lost]

Now why can't all that be shortened to a simple, plain text message that says the callerid, time, and return number, without any of this content-type and MIME gibberish? If VoIPo must use an email-to-SMS gateway, the "content type" should be text and nothing else.

I had to setup my mail provider's Sieve rule to forward to SMS after it does some 'squeezing' of the message. The SMS that arrives on phone looks like this:

From: <caller's number>@mymailserver
Subject: Wednesday, April 28, 2010

voicmil from <caller id> <caller's number> 00:00:18
vm: 8328387000

That way, the message is SMS-acceptable (short message service, needless to say) and I get the salient info about the voicemail: caller number, caller id, and message length. I also added VOIPo's VM so I can dial it directly from the SMS to listen to the message.

It would be great if VOIPo can set this up correctly, so users don't have to mess aroud with mail scripts.

[VOIPoTim]

I had to setup my mail provider's Sieve rule to forward to SMS after it does some 'squeezing' of the message. The SMS that arrives on phone looks like this:

From: <caller's number>@mymailserver
Subject: Wednesday, April 28, 2010

voicmil from <caller id> <caller's number> 00:00:18
vm: 8328387000

That way, the message is SMS-acceptable (short message service, needless to say) and I get the salient info about the voicemail: caller number, caller id, and message length. I also added VOIPo's VM so I can dial it directly from the SMS to listen to the message.

It would be great if VOIPo can set this up correctly, so users don't have to mess aroud with mail scripts.

I know we used to have a short message for that. Are you saying it's sending the same message as an e-mail notification now? If so, we can fix that.

[rcrcr]

Lost:

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

Thanks!

rcrcr