Alpha Feature: SMS Control

A web service would be useful for me as well. I'd like to do things like: forward calls to work at start of workday, cell when at lunch, remove forwarding at end of workday. DND activation and deactivation at certain times which vary depending on day of week. Given a web service I could set up cron jobs to perform these actions.

Another thought would be to come up with a list of all desired actions and make them controllable via whichever frontends can accept the needed parameters and returned data: web panel, web service, SMS, and telephone/voice interface.

So whats the status of an API or Web Service? I've got to setup something to schedule DND for nap times because my wife's father is a freaking idiot and always calls at the most in opportune times.

Quote:

---

Originally Posted by bubbanc

So whats the status of an API or Web Service? I've got to setup something to schedule DND for nap times because my wife's father is a freaking idiot and always calls at the most in opportune times.

---

Aren't in-laws great? :p

Quote:

---

Originally Posted by hines86fan

Can you add a command to toggle simul ring?

---

I would like to see this as well.

Also, how about putting the available commands in the SMS VPanel page? I know not every customer uses these forums.

Quote:

---

Originally Posted by Chris N

A web service would be useful for me as well. I'd like to do things like: forward calls to work at start of workday, cell when at lunch, remove forwarding at end of workday. DND activation and deactivation at certain times which vary depending on day of week. Given a web service I could set up cron jobs to perform these actions.

Another thought would be to come up with a list of all desired actions and make them controllable via whichever frontends can accept the needed parameters and returned data: web panel, web service, SMS, and telephone/voice interface.

---

This type of thing has been on the top of my wishlist. I'd love to see some scheduling capabilities as mentioned, esp for DND and forwarding. The idea that it changes for days of the week would be great. Even better would be if you could specify callers who were always exempt for the scheduling (ie older parents who never call at ridiculous hours unless there's an emergency ;) ).

That said, I'm really excited about the SMS feature! You don't know how many times lately I've had to navigate through the Voipo control panel from my phone to turn off/on forwarding. Love that the single SMS would do the same. (BTW, by keeping the web interface simple, it loads rather well on my phone and doesn't take forever to perform actions.)

Quote:

---

Originally Posted by varaonaid

This type of thing has been on the top of my wishlist. I'd love to see some scheduling capabilities as mentioned, esp for DND and forwarding. The idea that it changes for days of the week would be great. Even better would be if you could specify callers who were always exempt for the scheduling (ie older parents who never call at ridiculous hours unless there's an emergency ;) ).

That said, I'm really excited about the SMS feature! You don't know how many times lately I've had to navigate through the Voipo control panel from my phone to turn off/on forwarding. Love that the single SMS would do the same. (BTW, by keeping the web interface simple, it loads rather well on my phone and doesn't take forever to perform actions.)

---

You can do scheduling by using the API system very ..very easily.

Is SMS Control still working?

I tried (for the first time) to forward my phone to a number, and I got an error message from AT&T Wireless saying "Invalid Number. Please re-send using a valid 10 digit mobile number or valid short cut." I sent the SMS to 95495.

Should that number work with AT&T Wireless?

I'm running out of options - I need to be able to remotely enable and disable forwarding. Now that Remote Access isn't working, I hoped that I could do the same thing with SMS (even though I don't like to pay for an SMS message every time I need to make a change).

Gary Sanders

What was the exact command you sent? Change your number to 123 if posting here.

Quote:

---

Originally Posted by VOIPoTim

What was the exact command you sent? Change your number to 123 if posting here.

---

Hi, Tim,

Voipo1 fwd 1234567890

(Note the lack of upper case, since I couldn't find a way to create a message with all caps). Is it case sensitive?

Since my last message I've been playing with the Voipo API's, and got that working. I just created a web address with all the Forwarding parameters I needed hard-coded in, and saved that to my bookmarks in my cell phone, which has web access. I also hard-coded a FWD OFF address.

So now I can just use the API web address to turn Forwarding ON and OFF. The added benefit is I don't have to worry about SMS fees.

The only drawback is the API doesn't provide any status feedback after the command, so I'll just have to call the number afterward and see if it's properly forwarded.

Gary Sanders

I just received a new cell phone and was recreating VOIP1 templates. I didn't have my old cell on so I had to do a little searching in the forums to find the listing (and this thread). It may be handy to 'pin' this thread; maybe there already are, I just couldn't find them.

BTW was the 86476 number ever implemented? I tried it but got back the Error Invalid Number message from ATT. Not really much of an issue as the 95495 number works just fine.

For the good of the order, I just tried some SMS messages without the VOIPO1 prepend on the 95495 number and they worked as well.

95495 is the only one active. This feature doesn't really get enough use to justify doing our own SMS code (86476) at the current time ($1K+ per month).

Everything works great on it though....it's just the extra VOIPO1 prefix that has to be added.

I just showed this to my wife and she loves it.

I am noticing that the fail command does not seem to be working for me. fwd works fine. Could someone else test this?

Has anyone tried this using an iPhone? My wife just got an iPhone (so I'm not familiar with the device). I registered it in the Beta/SMS Controls tab of VPanel, made sure it was toggled green, then sent "voipo1 dnd voicemail" to 95495. I used "Messages" on the iPhone, which I assume is the SMS application. Nothing happened.

I then used my cell phone (which is registered to my Add-on line) to send the same command to the same number, and it worked fine.

The only thing that was odd about the iPhone was that when I entered the number "95495," the phone converted it to "95-495." Is there some special way to enter 5-digit SMS addresses on the iPhone?

I just messed around with this a little on an iPhone 4 and things went ok, but the voicemail command wasn't recognized. When you tried it on your other cell phone, voicemail was recognized?

Quote:

---

Originally Posted by VOIPoLucas

I just messed around with this a little on an iPhone 4 and things went ok, but the voicemail command wasn't recognized. When you tried it on your other cell phone, voicemail was recognized?

---

Yes, my other cell caused the DND feature to go from "Disabled" to "Voicemail." That was with my Add-on line, not my primary line (my cell phone is registered to the Add-on line, while my wife's iPhone is registered to the primary lline).

Maybe I'll try some other commands with the iPhone -- possibly the DND to Voicemail command is broken?

Interesting. It tested the command "voipo1 fwd me" and it worked. I then tested "voipo fwd off" and it didn't work. Morever, each time I tried "voipo fwd off" I got an SMS from mobivity.com asking me to configure my keyword.

Does VOIPo somehow use Mobivity as an SMS gateway?

Edit: I looked up Mobivity, and its short code is 95495, which is the code for this feature. I guess VOIPo uses Mobivity's API. So it looks like this is a problem at VOIPo's end.

OK, last comment: by a combination of fat fingers and the iPhone's auto-complete, I was sending the wrong keyword (hence the reply from Mobivity) and/or the wrong command (fed instead of fwd).

However, I have confirmed that the "fwd voicemail" does not work, whereas other commands do work, even "fwd off." And as I said earlier, the command "fwd voicemail" does work when sent from a different cell phone. Go figure.

You might think you are talking to yourself,
but there is an audience, and experiences are good to share :)

Could you add a "set the MWI light" feature to the web and/or SMS API?

I'd like to be able to remotely set my Message Waiting Indicator light.

Thanks! Ben