Just to poke something in here, I am developing an XMPP -> SMS gateway that can be used to send any XMPP message to a mobile phone.
We use Wadja.com to send the messages (they are a free but advertising supported) and from what I know are not accepting new "free" accounts. We got one because we developed twe2.com (twitter to SMS). The XMPP -> SMS gateway currently supports Wadja. Until XMPP is available on the app engine, I could open a http endpoint on www.twe2.im for you to send your message a mobile phone. All messages would be from "twe2", let me know if you or anyone is interested and I will check with that we are ok to proxy some of the SMS's Paul 2009/4/7 Ray Malone <rayish...@gmail.com> > > I agree. I'm using a gateway as well. I wouldn't recommend the email > method. Jim, I am curious on who you are using for .03 a text. > > On Apr 7, 10:30 am, Jim <jeb62...@gmail.com> wrote: > > I've had problems with that approach in the past including: > > > > -- the email to text gateways operated by the cell carriers can be > > very slow > > -- I've found that the gateways often mess up the formatting of the > > message, depending on the gateway it might wind up in the SMS with > > things like "SUBJ:" and "BODY" and junk like that cluttering up your > > message. > > -- determining the correct email gateway to use from the cellphone > > number is no longer reliable. It used to be you could look up with > > the area code and exchange and determine which carrier issued the > > number and then know which email gateway to use. Well, actually you > > can still do that but with cellphone number portability, you don't > > know which carrier currently services the number, you just know which > > carrier issued the number. So you wind up having to ask your > > customer to provide their phone number and specify which carrier they > > use. > > > > I recently did an integration to a SMS gateway. They have a variety > > of APIs including HTTPS, XML, SOAP, etc. They have a callback > > mechanism so your app gets status updates on the delivery status of > > each message. Only draw back is it cost $0.03 per message. There may > > be cheaper ones out there, I'm not sure as I got tired of looking > > around and three cents was reasonable for my usage. > > > > It just depends on if you're willing to live with the limitations, > > then the email approach is fine. If you need something cleaner and > > more reliable, then I suggest subscribing to a sms gateway service. > > > > On Apr 7, 1:21 am, MajorProgamming <sefira...@gmail.com> wrote: > > > > > I am currently developing an app that will send text message > > > reminders. I was thinking of using each carrier's email gateway to > > > handle the messages. Are there any potential scaling problems with > > > this method? > > > > > (I plan on sending the text messages via the GAE Email system) > > > > > Thank you, > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
