Multitech MTCBA-G-UF1 Specifications Page 7

  • Download
  • Add to my manuals
  • Print
  • Page
    / 40
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 6
Chapter 3. SMS Messaging Server design
3. SMS Messaging Server design
3.1. Introduction
The SMS Messaging consists of the following components (see Figure-1):
SMS Messaging Server service – multi-threading SMS Messaging engine;
Configuration Database – a vendor independent configuration database;
Message Database – vendor independent database where all incoming and outgoing
messages are stored;
Applications and Scripts;
GSM Modem channels and SMPP Provider channels;
SMTP and POP3 channels;
VBScript Triggers – to process incoming messages;
Figure 1 – SMS Messaging Server Design
The configuration information is stored in a database. This database can be any OLE/DB
compliant database, including MS SQL, MS Access, MySQL and Oracle. 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 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.
Page view 6
1 2 3 4 5 6 7 8 9 10 11 12 ... 39 40

Comments to this Manuals

No comments