4

I am attempting to setup a system to receive and process SMS messages automatically. The system is intended for use in a context (an unfunded migrant workers' union in India) where both finances and sysadmin skills are extremely constrained (I would be the only person, in the near future, who would be administering the system). The intention is to make some functions - registration of members, generation of ID cards, communication of alerts and other information - easier.

However, for receiving and sending SMS, I have not been able to find any email to SMS or other kind of gateway that functions in India. Perhaps there is one (edit: apparently Clickatell does have an India service, but the prices appear astronomical). If not, can one rely on a USB mobile modem (such as those provided by many mobile providers in India)? It seems like, with utilities such as gammu or bitpim, SMS operations on such a modem could be scripted. Is this actually feasible, though?

Thanks in advance for your thoughts and suggestions.

edit: Original first question removed since the two questions had little to do with each other. The original first question has been asked separately here

Community
  • 1
ShankarG
  • 946

2 Answers2

3

The best tool I found for this was an Open Source Package that runs on a Linux server, or Windows with cygwin. Like Randolph, I ran this with (three) serial-connected GSM modems.

http://smstools3.kekekasvi.com/index.php?p=

The SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.

You can send short messages by simply storing text files into a special spool directory. The program monitors this directory and sends new files automatically. It also stores received short messages into another directory as text files. Binary messages (including Unicode text) are also supported, for example ring tone messages. It's also possible to send a WAP Push message to the WAP / MMS capable mobile phone.

The program can be run as a SMS daemon which can be started automatically when the operating system starts. High availability can be ensured by using multiple GSM devices (currently up to 64, this limit is easily changeable).

The program can run other external programs or scripts after events like reception of a new message, successful sending and also when the program detects a problem. These programs can inspect the related text files and perform automatic actions, for example storing information into a database (for example MySQL or Microsoft SQL Server), sending an automatic reply, forwarding messages via eMail (SMS to eMail gateway), ... and whatever you like.

The SMS Server Tools runs on Microsoft Windows (with CygWin) and any Unix including Solaris, BSD, FreeBSD and GNU/Linux. This software needs a GSM modem (or mobile phone) with SMS command set according to the european specifications GSM 07.05 (=ETSI TS 300 585) and GSM 03.38 (=ETSI TS 100 900). AT command set is supported. Devices can be connected with serial port, infrared, USB or network modems using a socket.

Linker3000
  • 28,240
2

Having largely implemented the application now, I can also answer the question :). Both gammu and gnokii are options (the SMS Server Tools are, as said, unmaintained) and their performance with different actual mobiles varies very widely. I had to do testing of five handsets before I found one that works consistently. I now use gammu-smsd, with an sqlite backend, that triggers a bash script to do SMS processing and handle sending of replies. Use and manipulation of the data is through a Python-coded web application.

I find gammu-smsd much more extensive and powerful than the smsd that comes with gnokii; it offers a range of configuration options, which you can find here. It also provides a useful tool called gammu-smsd-inject that makes sending SMS's very easy. Should note that the gnokii folks were also very friendly and helpful. Hope this information helps someone in future.

ShankarG
  • 946