Project1 - SMS Service Web2Mobile and the Challenge
In the sidebar I have provided the link for SMS Service. This is a small module I wrote. It works perfect, I have only tested it for T-mobile yet. But please if you a chance try it and let me know the results.
There are many limitations to this though:
1. It needs carrier information. If you have a friend who knows nothing about your carrier, then she/he cannot conveniently send you SMS without knowing your carrier. Is there any way that this can be resolved? I know they call it reverse lookup, but how do i do it programmatically? I don't want to run curl and parse html of certain existing sites that do this for free. There should be some interesting and elegant solution to this.
2. Currently only ascii based text messages upto 160 characters can be sent. It would be genius if this limit can be surpassed and html-based sms messages with unlimited length could be sent using the same Email Gateway system! I don't think this has been ever done before by anyone succesfully.
Both the above limitations can be overcome using pricey solution, where a wireless modem is used to actually send the messages. But you know, the network is in place [Email Gateways], infrastructure is in place, why then opt for pricey solutions? We are techies and lets see if we can nail this down! It's an open challenge.
There are many limitations to this though:
1. It needs carrier information. If you have a friend who knows nothing about your carrier, then she/he cannot conveniently send you SMS without knowing your carrier. Is there any way that this can be resolved? I know they call it reverse lookup, but how do i do it programmatically? I don't want to run curl and parse html of certain existing sites that do this for free. There should be some interesting and elegant solution to this.
2. Currently only ascii based text messages upto 160 characters can be sent. It would be genius if this limit can be surpassed and html-based sms messages with unlimited length could be sent using the same Email Gateway system! I don't think this has been ever done before by anyone succesfully.
Both the above limitations can be overcome using pricey solution, where a wireless modem is used to actually send the messages. But you know, the network is in place [Email Gateways], infrastructure is in place, why then opt for pricey solutions? We are techies and lets see if we can nail this down! It's an open challenge.
posted by shlok at 11:49 AM
6 Comments:
I researched this morning on the issue and looked through our source code to see how we do it (have avoided names for obvious reasons). So, it turns out that we use the service provided by http://www.netnumber.net. They have a web service associated with that. Checkout http://netnumber.net/developer/home.jsp. Although i didn't see any documentation on the web service. The WSDL is located here: http://netnumber.net/content/developer/wqs.wsdl. Not sure if you came across this before.
yes, I had come across Enum solution. I researched it. I used public services of enum.org and enum.com and tested using dig. But now i will try with netnumber as well... I don't know if netnumber charges some fee for this?
so seems to me, enough is a private service. You might notice a session start, where login/pass authentication takes place, based on which there maybe certain authentication on server-side.
The wsdl did not show anything of this kind though but maybe this interface is next after authentication.....
I haven't tested the netnumber wsdl. Someone here told me that netnumber is the closest approximation to a central repository of such mappings. Secondly it handles cases when you've moved your existing number to a different carrier. The wsdl provides limited functionality though - just spid and something else. About it being free? May be using the wsdl is.
wsdl is just an interface. There maybe stepwise calls to these interefaces ... like wsdl [authentication], step2 wsdl [access data] ....
The wsdl provided did not work ......
Post a Comment
<< Home