Download ActiveXperts SMS Messaging Server 4.1

ActiveXperts SMS Messaging Server - Product Overview

• Mobile users are able to query databases for stock quantities, new orders or customer information
• Mobile users can receive critical information while they are away from the office
• Mobile users can receive notifications when important e-mails (from specific users or with specific subjects) have arrived
• Companies can route urgent calls to the service personnel
• Companies can send daily (stock) prices to their personnel or customers
• Remote workers can update their time sheets
• IT personnel can remotely restart services or reboot servers
• Multimedia companies - like radio stations and television stations - can setup their own voting system, enabling customers to bring out votes and request voting reports
• Entertainment companies - like bars and dancing's - can send out information about special events to their customers
• Emergency Response Centers can offer a service to locals to report crime by a short message

    SMS Messaging Server Design

• The Configuration Database contains all configuration parameters, like communication devices, scripts, general settings, etc. Can be any OLE/DB compliant database, like MS Access, MS SQL and MySQL (default: MS Access);
• The Message Database contains all incoming and outgoing messages. Can be any OLE/DB compliant database, like MS Access, MS SQL and MySQL (default: MS Access).

	Fig. 1: SMS Messaging Server Design

    SMS Messaging Manager and SMS Messaging Monitor

	Fig. 2: SMS Messaging Server Manager  [larger]		Fig. 3: SMS Messaging Server Monitor  [larger]

    SMS Messaging Manager API

   Option Explicit
   
   Dim objMessageDB, objConstants, objMessage 
   
   Set objMessageDB = CreateObject( "AxSmsServer.MessageDB" )    ' Create API objects 
   Set objConstants = CreateObject( "AxSmsServer.Constants" )    ' Create API objects 
   
   objMessageDB.Open                                             ' Open the Database
   WScript.Echo "Open, result: " & objMessageDB.LastError
   
   Set objMessage   = objMessageDB.Create                        ' Create new message in database
   WScript.Echo "Create, result: " & objMessageDB.LastError
   
   objMessage.Direction     = objConstants.MESSAGEDIRECTION_OUT  ' Set direction: outgoing
   objMessage.Type          = objConstants.MESSAGETYPE_SMS       ' Set type: SMS
   objMessage.Status        = objConstants.MESSAGESTATUS_PENDING ' Set status: pending
   objMessage.ChannelID     = 0  ' First available SMS channel   ' Use first available SMS channel
   objMessage.ScheduledTime = ""                                 ' Immediate schedule 
   objMessage.Recipient     = "+31625044454"                     ' SMS recipient
   objMessage.Body          = "SMS Messaging Server Test SMS"    ' SMS body
   objMessageDB.Save( objMessage )                               ' Save modified message in database
   WScript.Echo "Save, result: " & objMessageDB.LastError
   
   objMessageDB.Close                                            ' Close the database
   WScript.Echo "Close , result: " & objMessageDB.LastError

   Option Explicit
   
   Function ProcessMessage( numMessageID )
      Dim objMessageDB, objDebugger, objConstants, objMessageIn, objMessageOut
   
      Set objConstants        = CreateObject( "AxSmsServer.Constants" )
      Set objMessageDB        = CreateObject( "AxSmsServer.MessageDB" ) 
   
      objMessageDB.Open       ' Open the Message Database
   
      ' Get message record from the database
      Set objMessageIn        = objMessageDB.FindFirstMessage( "ID = " & numMessageID ) 
   
      ' Create new message (the reply message)
      Set objMessageOut       = objMessageDB.Create
   
      objMessageOut.Direction = objConstants.MESSAGEDIRECTION_OUT
      objMessageOut.Status    = objConstants.MESSAGESTATUS_PENDING
      objMessageOut.Type      = objMessageIn.Type 
      objMessageOut.Recipient = objMessageIn.Sender  
      objMessageOut.ChannelID = 0
      objMessageOut.Body      = "Thanks for your message!"
      objMessageDB.Save objMessageOut
     
      objMessageDB.Close      ' Close the Message Database
   
   End Function

ActiveXperts SMS Messaging Server - Product Features

    SMS

• Send and Receive SMS messages on multiple communication lines simultaneously;
• Support for GSM Modems and GSM phones (GSM 07.05 and GSM 07.07 specifications) for low-volume messaging;
• Support for SMPP-compliant SMSC centers (SMPP 3.x) for high-volume messaging, according to Industry Standard SMPP 3.x for external and internal connections;
• Support for multiple SMPP/SMSC connections and multiple GSM modems/phones running simultaneously;
• Support for multi-numbering formats;
• Support for multi-part messages, to allow messages longer than 160 characters;
• Support for SMS delivery verification;
• Support for Unicode, to support foreign languages like Chinese, Turkisch, etc.;
• Support for WAP Push messages and WAP Bookmark messages;
• Support for traffic limitations (maximum number of SMS messages per day);
• Full TAPI (Windows Telephony) support;
• Incoming SMS messages are stored in a central, vendor-independent message database (default: MS Access);
• Outgoing SMS messages are fetched from the message database and sent through an available GSM/SMPP communication channel;
• All SMS communications can be viewed real-time using the SMS Messaging Monitor application;

    E-mail

• Send and Receive e-mail messages on multiple network connections simultaneously;
• Native SMTP- and POP3 support;
• Incoming e-mail messages are stored in a central message database (default: MS Access);
• Outgoing e-mail messages are fetched from the message database and sent through an available SMTP communication channel;
• All E-mail communications can be viewed real-time using the SMS Messaging Monitor application;

    Database

• All configuration information is stored in a central, vendor independent database. An MS Access based configuration is installed by default. SQL scripts are provided to streamline migration to MS SQL or any other vendor-independent database;
• All incoming and outgoing messages is stored in a central, vendor independent database. An MS Access based message database is installed by default. SQL scripts are provided to streamline migration to MS SQL or any other vendor-independent database;
• The SMS Messaging Server Manager enables you to define different views of the database;
• An API is provided to allow custom scripting. The API provides full access to the Configuration Database and the Message Database.

    Scripting

• VBScript is the default scripting language;
• Each incoming message is processed by the system. Depending on the Script configuration in the Configuration Database, one or more VBScript programs are triggered to process the message;
• The SMS Messaging Server API can be used in VBScript. A lot of sample code is included, showing how to use the API in VBScript;

    Monitoring, Logging and Tracing

• The Monitor applications shows the real-time activity of the Channels; all modem operations and network operations (SMPP, POP3 and SMTP) can be viewed real-time;
• Logging can be written to ASCII files, an MS Access database, MS SQL server or any other OLE-DB/ADO compliant database. Product is shipped with an Access database file that works out-of-the-box;
• Maximum Log size is configurable.
• Message tracing allows you to see exactly what happened with a message, at what time. For instance, you can see at what time a message was received by a POP3 server, at what time it was received by SMS Messaging Server and at what time it was processed by the system.

System requirements

Case Studies