Alternatively, you may use Start menu -> Programs -> SMS Reception Center.
You will see the main window of the program:
What you see is a graphic interface of the editor that we will use to define actions which are taken on each incoming message. Now we want to check if the program works with your phone, and the empty list of actions is good enough for the first steps, so don't try to change the list now. Go to the menu instead and select Run -> Install. Now you will see the popup dialog window:
We are about to start the SMS Reception service. What is that service, at last?
SMS Reception Center separates two different tasks from each other: editing rulesets (action lists) for message handling is one task, and processing messages (in connection with a phone) is another one. You prepare a list of actions in the Editor, then you have to feed it to the Service which will work with the phone and act as you instructed it.
There are two modes for running the service, Desktop mode and NT Service mode. The first mode is the most appropriate for debugging and testing purposes, so we will use it now.
At this step you must select a COM port which is connected with a phone. When you use data cable, this port will be COM1 or COM2 in most cases. If infrared connection is used, there is usually some software-emulated COM-port, and you have to select this emulated port. Some NOKIA phones require vendor-specific software to work properly as a modem; this software may provide a virtual COM-port too. Virtual COM-port is usually accessible as COM3, COM4 or COM5.
Now you are about to start SmsRc service. Please ensure that you have no worthy unread messages in your phone. They will be silently removed! If you have a chance to receive a worthy message at any time, don't do this test until you learn how to store incoming messages in a text file.
Select a port and click OK button (or press Enter). Now look at the system tray at the windows task bar. You will see the SmsRc service icon there.
When you move mouse pointer to that icon, the tooltip message is displayed. If everything is alright and the program works with your phone correctly, this message will become looking like this: Ericsson (R520) on COM2, i.e. it will contain the phone's manufacturer name and model name.
Initial message is always Connecting to phone on COMn; if it doesn't change in a few seconds as described above, there is some problem and the program is not working with you phone now. What to do in such a situation?
If you click on the tray icon with right mouse button, you will see a menu. In case of problems, select Save debug log in this menu and choose a log file name. E-mail us (mailto:email@example.com), name your phone, describe the connection you use and attach the debug log. We will try to get it working.
Select Edit -> Insert -> Store message... and you will see dialog window with action parameters you are allowed to set up:
Here is the description of parameters that we'll use now:
The picture above is an illustration of variable substitutions in parameters. The Log entry format field contains a reference to the Sender variable. When a message arrives, this variable is set to the phone number of the message's originator.
When you right-click on a field that allows variable substitutuions, the popup menu with available variables appears. On this picture we see this menu with predefined variables in it: these variables are set for each incoming message automatically.
Please choose a file name as you like, define Log entry format to be [%Sender%] wrote: [%Message%] and press Enter key to save this action.
The list of actions in the editor will now look like this:
Let's see how this example works. We have changed the list of actions, but the service doesn't know anything about it — we need to use Menu -> Run -> Install... to tell the service about changes. Let's do it now...
There is a feature in SMS Reception Center which is good for such a test. When Desktop SmsRc service is running, you can go to the menu and select Run -> Test message... there; then you will see a dialog window:
When you fill these two fields and click on the OK button, you make SmsRc service think that there was an incoming message. This message is handled exactly the same way as any real incoming message will be handled.
In the example we're discussing now, the sender's phone and message's text that you type in this window will be appended to the text file that you have selected. When you are sure that messages are handled in the way you like, you can switch to real messages.
Unregistered users, plese remember: SmsRc service won't handle more than 6 messages per session before registering the program, including both test messages and real ones. You should restart the service after each 6 messages processed.
Here we described the condition under which this action is taken: the message's sender number must be +79165551234. Note that we also checked Take no further action after this one; thus if the phone receives any message from +79165551234, it will be stored in the file we selected, and no further actions will be taken on that message.
There are four types of string comparison that may be used to describe action's condition. We are using exact match in this example, but it's good to know what do the other types mean:
Now it's time to begin to use action lists that contain more than one action. I recommend to use unconditional Store message action as the first one; thus, no incoming message can ever be lost due to erroneous setup.
Look at the example above: each incoming message is unconditionally forwarded to four recipients. Two of these recipients are mobile phones, and the other two are user, computer, or workgroup names.
Now remember what we learned before about generating test messages (pseudo-incoming messages, really). The point is that, together with message forwarding facility, this feature may turn SMS Reception Center into the program for sending bulk SMS!
Imagine that after setting up this example and starting the SmsRc service, you use Run -> Test message facility discussed before:
There is no real incoming message involved, as you already know. But the action you've set up will react on the test message exactly as on any real incoming message. Thus this messsage will be really forwarded to four recipients.
CAUTION: Never forward incoming messages to your own phone unconditionally! If you do this, SMS Reception Center can enter the infinite loop of receiving-message-and-forwarding-it-to-itself, which is not what you want.
In this example, a message is forwarded to the given four recipients only if it's first word contains 4MANAGERS. Thus 4MANAGERS is a keyword which denotes the list to which a message must be forwarded.
Combining several such actions enables you to maintain several lists of recipients.
The last about this example: note that we used containing instead of is exactly in the condition. There is a reason behind that: if you set up several actions of this kind, the first word of messages text may contain more than one keyword! If there are two actions with keywords 4MANAGERS and 4DEVELOPERS, they both will be triggered if the keyword is 4MANAGERS,4DEVELOPERS.
First we need to create a database accessible through some ODBC driver. It may be Microsoft™Access file.
Create a table called SMSLists with the following columns in it:
Click on the Connect DB button and select appropriate ODBC driver and connection parameters for your database. It's good if you have some experience with ODBC, but even if you don't, the ODBC interface for database selection is rather intuitive and easy to use.
When you have selected the database that contains the SMSLists table mentioned above, let's set up another parameters of this action:
The simple SQL query will produce a one-column result containing all recipients for particular keyword. We stated explicitly that we expect a one-column result from this query, and this result must be stored in variable named Recipients. Note, it's the first time we defined a new variable!
Save this action and add another one; as you've already guessed, it's a Send message action. Now we can use Recipients variable in the Send to parameter:
Now you know enough to set up message forwarding using the database to keep several lists of recipients. Notice that all database-related actions share the same ODBC connection. Thus if the location of your database has changed, you need to adjust connection string for one such action only: another actions will use the new connection automatically.
Take the previous example and insert a new action in the beginning of action list:
To use this feature, you must create a table named OutgoingSMs with the following columns in it:
Status=2 means that the message was not sent after 3 retries. It may be the hardware problem or operator's fault; you have to set Status back to 0 if you want the message's delivery to be attempted next time.
These columns are mandatory, but the table may have any other columns as well.
You should insert records with Status=0 into this table; when the SmsRc service is running, it takes all these records, sends out the messages and then updates Status to 1, thus indicating that the message was sent.
The other things that weren't mentioned in this document we consider obvious to you: e.g. how to use cut-copy-paste and new-open-save file in the editor. We believe that you don't need any explanations on this topics.