How can we help?

Auron SMS Server architecture


Overview

The SMS Server is build up out of a number of components that help you setup your message based application. The image below shows a schematic overview of the SMS Server components and how they integrate in your application.

Auron SMS Server Architecture Overview

Auron Software Architecture Overview

All of these components are installed and setup automatically. Including a number of samples and template triggers. By simply downloading and running the installer on your server.

The following sections go into more detail about each of these components.

The Service

The Auron SMS Server runs as a service on a windows based server. This can be a cloud based server such as AWS or Azure providers but it may also be on premise.

All of the communication channels, such as GSM, SMPP or E-mail channels run in the context of the service. The service is also in charge of running trigger scripts and routing outgoing messages.

Triggers

Trigger scripts are tiny JavaScript, VBScript or SQL scripts that contain your business logic. You can configure a trigger script to run on an incoming message or when it reaches a specific state, such as ‘failed’ or ‘sent’.

Channels

Channels are ways to communicate with the outside world. For instance: to send SMS or E-mail messages or to automatically read files that an external system may generate.

The channels are ultimately the way that the SMS Server communicates with your customers, you employees, your target audience or yourself.

Each channel type represents a type of communication. For example: a GSM channel connects to a GSM device. An SMPP channel connects through the internet to an SMS provider and an IMAP channel remotely reads an e-mail mail box. You can have multiple channels of each type.

The Server Database

The server database contains both the messages and the configuration of the Auron SMS Server. In addition to the server database you can optionally define a separate archive database where messages will archived to after they reach a specified age.

As with the service the server database can be located on premise as well as in the cloud. The SMS Server will work with any recent SQL Server database as well as with Microsoft Azure.

API

This is a completely open and well documented API that can be used to interface with the SMS Server. The trigger scripts use the API to manipulate messages. You can use the API to create external programs and scripts as well.

The setup package of the SMS Server contains a large number of working examples that show how to use the API. The API works with most Windows based development environments including C# .Net, ASP .Net, PHP, Delphi, etc…

User Interface

The SMS Server user interface is mainly the SMS Server Manager. The SMS Server manager is a view on the server database and is used to:

  • Browse and filter messages.
  • Maintain the channel and routing configuration.
  • Create and edit trigger scripts.
  • Configure and start sending bulk messages (campaigns)

In addition, using the API, you can create your own way of interfacing with the SMS Server as well. For instance build your own custom web interface or desktop applications.