Hi Tom,
I apologize in advance if my question seems obvious and out of place. I am new to SMS and have had some difficulty in finding sources of information that explain how the SMS system works and what approaches are best for solving particular problems.
now, SMS is a slight part of GSM specs, and, yes, it's a hard piece of work getting all together in mind ;)
We are interested in using SMS on campus to deliver crime alerts to mobile phones of our students, faculty and staff. In order to do this, we obviously need to have their phone number. Do we also need to collect who their wireless carrier is, or is the number sufficient?
Actually you either need their MSISDNs (mobile station numbers) or let them "opt-in/out" to the service via SMS itself. Like letting them send "alert crime start" for having them subscribing to the "list" and "alert crime stop" for unsubscribing. Just an example.
AFAIK, the US has also number portability, which means you can't identify the operator of a MSISDN via it's network prefix. So, it "may" be hard to determine their operator without having access to a number portablity database. (which I know of the VeriSign telecom group is operating in Kansas City).
Our campus computing infrastructure runs on Sun Solaris Unix and Red Hat Enterprise Linux. We are not interested in running a Windows server based product.
same with us ;)
We will probably have to establish a relationship with a SMSC in order to deliver these SMS messages to students. How does one go about finding appropriate vendors for doing this?
Now, you basically have 2 alternatives:
a) connect to every carrier you want to support. Which is the "hard way". Espacially in the US, where carriers still have some issues with european-well-known protocols like SMPP and/or EMI/UCP.
This would imply that when your application receives an SMS MO (mobile originated) with a subscribtion request, you get also "the route" of the message and hence the orginating carrier for the MSISDN.
b) us an aggregator, which leaverages the difficulties of option a) for you. You only connect to that aggregator and route message transparently to the various carries via the aggregator.
Decission matrix for a) or b) depends on cost, performance and reliablility of the aggregator.
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
