2Way SMS Messaging
Two Way SMS Messaging is for receiving the information sent by SMS to special number and process the information. According to number ownerâ„¢s requirements and provide the information back to the user as an Excel file.
That can receive SMS messages, and return a response based upon the content of the received SMS message.
When an SMS message is received, the gateway will evaluate the content of the message, and can either execute a program, or connect to an HTTP URL, based upon the content of the message. The decision of how to process a received message is based upon the first word of the received SMS message. In the terminology of the gateway, this first word of the received message is called the SMS Command Prefix. Based upon this SMS Command Prefix, the gateway will execute a command associated with the prefix. If the received prefix does not match any defined prefix, then it is considered to be a match for a special wildcard prefix, denoted as *.
When a command is executed based upon the receipt of an inbound message, the command line for the program or HTTP request can include replaceable parameters from the contents of the SMS message. The following replaceable parameters are supported:
To return results back to the user, the command can either return a simple text response directly to the gateway (Command returns response text is checked), or the command can generate a more complex response to the gateway via a separate HTTP request to the gateway. An executable program returns a simple text response to the gateway by printing results to the screen, where the gateway captures the screen output, and generates an SMS response to send the screen output text back to the sender via SMS. An HTTP request returns a simple text response to the gateway by returning content of the MIME type text/plain.
When an HTTP command is used, if the command is to return a response to the gateway directly, the HTTP response must be of the MIME content type text/plain.
It is also possible for any HTTP command to return an HTTP redirect response to the gateway, which instructs the gateway to fetch an alternative URL, even a URL command that contains parameters to tell the gateway to submit a message. This can be useful for creating a 2-way command script that responds with binary message content.
If an HTTP command requires HTTP authentication with a username and password, the URL format of http://username:password[at]host.name/path is supported. When a URL command is defined in this format, the gateway will connect to http://host.name/path using an authorization header of the specified username and password.
The "Command to Execute" field can also specify an e-mail address, in which case any received SMS messages that match the configured "SMS Command Prefix" will be forwarded to the specified e-mail address. To specify an e-mail address for the "Command to Execute", use the format "mailto:user[at]domain.com".
If the wildcard SMS command prefix is not associated with any command, any inbound SMS messages that do not match a prefix will be saved to the SMS-IN directory with a file extension of .SMS, and they may be processed by another application independent of the gateway.
Number of modules: 3
Module 1: Advertiser Operations
In this Module
1. Advertise can Register with details (Processing is assumed to be manual)
2. Can add codes and assign corresponding SMS and email with attachment replies (can set it automatic)
3. Can see all the incoming messages to the keywords and initiate follow up Email or SMS.
4. Export list of all emails to CSV file
5. View the list of credits left in his account
Module 2: Admin Operations:
In this Module
1. Viewing the pending registrations and approving them
2. Recharge the advertiser's account with the reply SMS credits
3. Settings page with an http URL SMS gateway to send the message (by changing this, he should be able to change to gateway of his choice)
Module 3: User Message Request.
In this module, User can send message to a special number requesting for the information.
Team Size: 1
Operating System : Windows-XP
Front End : Visual Studio .NET Framework
Back End : MS SQL Server-2005
Processor Type : Pentium IV
RAM : Minimum of 512 MB
Hard Disk Capacity: 20 GB (or more)