January 4, 2011 at 4:06 am
I need to enable SMS Messages to be sent via HTTPS post to a SMS-Gateway.
I have NO Programming experience outside basic stored procedures within SQL 2005.
I have written the neccesary SPs to compile the message and place it into a table. I need a CLR the will be triggered to send any new message placed in the messages table to a list of Mobile numbers.
Any assistance wil be greatly appreciated.
January 4, 2011 at 5:12 am
why via the web interface of some provider? all the providers i know support email to sms, which is easier to do from SQL server; the problem is you have to know the carrier of the recipient,but you could be lazy and send one phone number to all the main providers and let the emails fail if the number is not valid.
I've automated ATT's site using WatiN, but messages like thqt are slow compared to an email.
use www.data24-7.com to find out which carriar a number is:
AT&T – cellnumber@txt.att.net
Verizon – cellnumber@vtext.com or phonenumber@vzwpix.com
T-Mobile – cellnumber@tmomail.net
Sprint PCS - cellnumber@messaging.sprintpcs.com
Virgin Mobile – cellnumber@vmobl.com
US Cellular – cellnumber@email.uscc.net
Nextel - cellnumber@messaging.nextel.com
Boost - cellnumber@myboostmobile.com
Alltel – cellnumber@message.alltel.com
Cincinnati Bell Wireless it’s cellnumber@gocbw.com
Metro Pcs 14352345762@mymetropcs.com
Lowell
January 4, 2011 at 5:32 am
There is and HTTPS web service on the Provider's side that I need to connect to. Unfortunately our dear Mobile Service providers in the good old South Africa do NOT support mail to sms (not as a free service anyway). It is a much cheaper option to send messages to a bulk SMS service provider.
January 4, 2011 at 1:10 pm
I wouldn't use SQLCLR for this, I would use Service Broker and External Activation to solve this problem. You can find out more about the External Activator and how to use it on the following URL.
http://blogs.msdn.com/b/sql_service_broker/archive/tags/external+activator/
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 4, 2011 at 2:58 pm
Jonathan Kehayias (1/4/2011)
I wouldn't use SQLCLR for this, I would use Service Broker and External Activation to solve this problem. You can find out more about the External Activator and how to use it on the following URL.http://blogs.msdn.com/b/sql_service_broker/archive/tags/external+activator/
IIRC, External Activation has been introduced with SS2K8. The forum is SS2K5.
@valkerieforever
Please clarify the SQL Server version. External Activation would be a nice solution...
January 4, 2011 at 3:10 pm
It is downloadable from the SQL 2008 Feature Pack, but it works on Service Broker, and is functional against SQL Server 2005 as well. The original source code that eventually became the External Activator download was for SQL Server 2005 and available open source, but it no longer exists online where it used to. I did find it in the Source Code Download for the Apress 2005 Service Broker book:
http://apress.com/book/downloadfile/3528
It piggy backs Event Notifications and fires the Event on Queue Activation, both of which are supported in 2005, 2008 and Denali.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 4, 2011 at 9:27 pm
The SQL Server is SQL 2005 Standard Edition.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply