1.1. Product OverviewSMS Messaging Server is an SMS messaging framework that enables companies to send, receive and process SMS messages. The framework is designed to support virtually any scenario where low-and high volume SMS messaging is required.Use SMS Messaging Server in the following scenarios:
SMS Messaging Server consists of the following components:
1.2. Product FeaturesSMS Messaging Server features the following:
1.3. About the Short Message Service (SMS)1.3.1. Introduction The Short Message Service (SMS) is part of the GSM specification and allows messages to be sent to and from GSM mobile networks throughout the world. A single short message can contain up to 160 characters and comprise of words, numbers or an alphanumeric combination. Short messages can be received with voice, data and fax calls. SMS also provides confirmation that a short message has been delivered to its destination. Non-textual short messages can also be sent to carry 8-bit binary data. Messages comprising of Unicode character sets which include Arabic and Chinese characters can also be carrier in SMS. SMS is a store and forward service where a short message is sent via a Short Message Service Center (SMSC). An advantage of this is that the destination mobile device does not have to be on the network at the time when the message is sent. If a destination mobile device is not available at the time the message is sent, the SMSC service center will retry to deliver the message. Delivery of a short message takes only a few seconds from SMSC to the mobile device. SMS messages can be up to 140 octets or 160 characters in length and can carry information coded in different ways. The most common 'coding scheme' is the GSM default alphabet. This allows a simplified text alphabet to be coded into 7 bits per character. Most advanced applications will typically use 8-bit data where the SMSC makes no assumptions on the coding scheme and allows applications to use the 140 octets as they wish. 1.3.2. GSM modems SMS Messaging Server supports GSM modems to send and receive SMS Messages. It supports a broad range of GSM modems that support the ETSI GSM 07.05 guidelines. Modern GSM devices (made by Nokia, Siemens, Sony Ericsson, etc.) use the similar subset of AT+C command set and are - as a result - also supported by ActiveXperts SMS Messaging Server. You can connect a GSM modem through one of the following interfaces:
ActiveXperts recommends MultiTech MTCBA-G-UFx modems and WaveCom 1306B GSM modems. ActiveXperts bundles the SMS Messaging Server software with a MultiTech modem:
1.3.3. SMPP Providers SMS Messaging Server supports SMPP 3.x compliant SMSC providers. The SMPP protocol allows a client (i.e. ActiveXperts SMS Message Server) to access the SMSC's ('Short Message Server Center') systems to send and/or receive SMS messages. To allow connection between SMS Messaging Server and an SMPP compliant SMSC center, an IP connection between these two systems is required, either directly or through the Internet. Usually, an SMSC center provides multiple sites, to ensure that the service is always available. An SMSC provider ensures high-volume messaging, usually around 10 SMS messages per second, or even more. You need to sign-up with an SMPP-compliant center before you can actually use their service. It normally requires a small sign-up free, and a fee for an SMS bundle per month. SMS Messaging Server provides free SMPP messaging for a limited number of SMS messages. You can connect to the ActiveXperts SMPP server and send/receive messages right after installation, without the need to sign-up with an SMSC center first. If you want to know about a list of SMPP providers recommended by ActiveXperts Software, click here. 1.4. SMS Messaging Server Design1.4.1. Introdution The SMS Messaging consists of the following components:
The configuration information is stored in a database. This database can be any OLE/DB compliant database, including MS SQL Server. By default, SMS Messaging Server is shipped with an MS Access configuration database: Configuration.mdb. Messages are also stored in an OLE/DB compliant database, separate from the configuration. By default, SMS Messaging Server shipped with an MS Access message database: Messages.mdb. Migration to MS SQL Server can be done easily. The SMS Messaging Server service is responsible for controlling the so called 'Channels'. A Channel is a communication device or communication protocol. The SMS Messaging Server service reads messages from the Message Database and provides these to the designated channel; it also polls the channels regularly to see if there are any new incoming messages. The SMS Messaging Server triggers VBScript programs whenever there are new messages in the Message Database. Scripts are only triggered when a certain condition is matched. A Channel is a communication device or a communication protocol. You can define a 'Channel' for each GSM Modem, SMPP provider, POP3 connection and SMTP connection. These Channels are stored in the Configuration Database. The SMS Messaging Server service reads the Channel configuration from the Configuration Database and controls each Channel by a separate process (also called 'thread'). The SMS Messaging Server Manager enables you to change the Configuration Database. Using this Manager application, you can create new Channels, modify existing Channels, delete Channels and modify general options. This Manager application can also be used to view Messages and define Filters on the Message database. SMS Messaging Server is shipped with a selection of ActiveX/COM objects to manage the Configuration Database and the Message Database. This way, Administrators can fully customize the User Interface of the product; it also enables them to generate new messages themselves from a script or a custom application. The configuration database includes information about the channels (GSM channels, SMPP channels, POP3 channels and SMTP channels) as well as information about. Messages are also stored in an OLE/DB compliant, central database. By default, SMS Messaging Server is shipped with an MS Access message database (Messages.mdb). 1.4.2. Channels A 'Channel' is a communication device or a communication protocol. Messages are sent and received by such a Channel. You can define 'Channels' for each of the following devices/protocols:
You can define a 'Channel' for each GSM Modem, SMPP provider, POP3 connection and SMTP connection. These channels are stored in the Configuration Database. The SMS Messaging Server service reads the Channel configuration from the Configuration Database and controls each Channel by a separate process (also called 'thread'). 1.4.3. Triggers Incoming messages can be processed by VBScript programs. As soon as a new message is received by the system, VBScript program(s) are launched based on certain condition(s). A trigger is a pair that consists of a SQL-like condition and a VBScript program. If the trigger's condition is matched, the associated VBScript program is called. 1.5. Send an SMS MessageBefore you can send an SMS message, you must first setup an SMS Channel. You can either setup a GSM Channel or an SMPP Channel.After the SMS Channel has been setup, you can send an SMS message in three ways:
IMPORTANT: It is the ActiveXperts SMS Messaging Server serivce (Engine) that actually sends the SMS message, through one of the configured channels. The Manager (or ASP web interface, or SMS Messaging Server API) is just reads/writes the messages to the message database. 1.6. Process MessagesYou can process SMS and E-mail Messages by the use of Triggers.To read more about triggers, please read Chapter 9: Projects and Triggers. |