Home
RECOMMENDED FOR YOU:
SMS Gateway software
Ozeki brings you outstanding
SMS Gateway technology. Use our SMS Server products on Windows,Linux, or Android

C# SMS API
Developers can use our C# SMS API to send SMS from C#.Net. The C# SMS API comes with full source code

PHP SMS API
The ozeki PHP SMS gateway software can be used to send SMS from PHP and to receive SMS usig PHP on your website

SMPP SMS Gateway
SMS service providers use our SMPP gateway solution, that offers a high performance SMPP server and SMPP client gateway with amazing routing capabilities
Ozeki NG SMS Gateway

Ozeki NG SMS Gateway
Product Guide
www.ozekisms.com

Table of Contents

Prerequisites

This page provides detailed information about the hardware and software requirements for your computer to be able to send and receive SMS messages using the Ozeki NG - SMS Gateway software.

To run the Ozeki NG - SMS Gateway software on your computer, you have to meet some essential hardware and software requirements.

Hardware requirements

In all cases better hardware gives you better performance. The most important factor regarding performance is the amount of RAM in you computer, and the speed of your hard disk.

  • CPU: 4 cores
  • RAM: 4 GB (16 GB recommended)
  • Hard disk space: 4 GB (SSD recommended)
  • Ports: RS232 or USB (if you use a GSM modem)
  • Phone-to-PC data cable (USB or RS232) or
  • Network: Internet connection (if you use IP SMS connection)

Virtual hardware

Ozeki NG SMS Gateway is also optimized to run in virtualized environments. Microsoft, VmWare, Linux KVM, Oracle and many other virtualization platforms are supported.

GSM modem

If you wish to use a GSM modem attached to the PC with a phone-to-PC data cable for SMS messaging, you need a suitable device. For more information about suitable telephones for SMS messaging, check out the Recommended SMS Hardware guide.

Software requirements

Ozeki NG - SMS Gateway runs on one of the following operating systems:

  • Windows 11
  • Windows 10
  • Windows 7
  • Windows 8

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2

The following updates should be installed:

  • .NET Framework 4.0

You can download Ozeki NG - SMS Gateway and the programs listed in the software requirements on the Download page (). You should always download and use the latest version of Ozeki NG.

SMS Technology

This page provides a brief explanation for you on the basics of the SMS technology along with a fact sheet, as well as links to pages detailing the technology.

The SMS technology was created by GSM pioneers in Europe. The standardization process is led by the European Telecommunications Standards Institute (ETSI). The SMS technology was created to provide an infrastructure for the transportation of short messages containing a maximum of 140 bytes (8 bit objects) of useful data in mobile telecommunication networks. The transportation is done in the GSM signaling path in traditional GSM networks, and as GPRS packets in GPRS networks. Messages are composed using the PDU specification. An SMS is a binary string containing all the necessary information to form the message header needed for transportation and the message body containing the payload. The basic addressing scheme of SMS messages are mobile telephone numbers called MSISDN.

Standard: GSM (ETS 03.40)
Transport technology: GSM Signaling Path, GPRS
Transport protocol: Short Message Protocol
Addressing scheme: MSISDN
Message description language: SMS PDU
User data length: 140 byte (Concatenated messages can exceed this size)
Basic character set: 7-bit SMS, 8-bit SMS, UCS2

On the Basic Concepts page you can read about the roles of the different SMS messaging entities, illustrated with figures depicting SMS messaging using GSM and IP connection.

On the IP SMS technology page you can read about the convenience of connecting to the Short Message Service Center over the Internet, and you are provided with links to pages detailing the most common IP SMS protocols.

On the GSM SMS Technology page you can read about SMS messaging using a GSM device (modem or phone), and you can find links to pages detailing the different ways of connecting the GSM device to the computer.

On Connection page you can learn the two connection possibilities that allow to connect to the mobile network. The detailed system architecture diagrams also demonstrate the solutions.

On USSD basics page you will find the basic information on USSD (Unstructured Supplementary Services Data) to be familiar with this service. A link to USSD message types is also available in the article.

On GSM modem vs IP SMS page you will be provided with detailed information on the differences between GSM modem connectivity ans IP SMS connectivity to help you make a selection from them.

Connection types

In this page, you are going to get more information about connection types of the Ozeki NG SMS Gateway. You can use the Ozeki NG SMS Gateway in two ways. Ozeki SMS Gateway can be used to send and receive SMS messages. The messages can be transferred to or received from the mobile network in two ways. You can setup a wireless connection (Figure 1) or an IP SMS connection (Figure 2). Both connection types have advantages and disadvantages.

Wireless connections

A wireless connection can be used to send/receive SMS messages if you attach a GSM Modem (or GSM phone) to your PC with a phone to PC data cable. The GSM Modem has a SIM card, that makes it possible to attach to the GSM network. The major advantage to this connection is that it is easy to setup. You can purchase a SIM card and a GSM modem simply and get the system up quickly. To operate this connection the costs are low. You can purchase a prepaid SIM which means you will not have a regular monthly fee. The drawback to this connection type is that it is relatively slow. You can transmit/receive about 10 messages per minute with this connection type. (You can increase this capacity by using more than one GSM modems.) If you want to create an SMS service that will not send/receive a very large number of messages this is an ideal option.

how wireless sms connection works
Figure 1 - Wireless SMS connection

IP SMS connections

Another option is to connect your system directly to the short message service center of a GSM service provider over the Internet. In this case you have a significantly better bandwidth (max. 10 000 SMS/ minute), but you usually have to pay a large monthly fee and it takes a lot of time and is hard to sign a contract with a service provider. IP SMS connections use IP SMS protocols: SMPP or CIMD2 or UCP/EMI. Ozeki SMS products have an excellent implementation of these protocols.

how ip sms connections work
Figure 2 - IP SMS connection

Recommendations

If you want to build a system, we recommend you to start with a wireless GSM Modem connection and if the capacity demands increases you can switch to IP SMS.

Basic concepts / SMS network entities

SMS messages are created by mobile phones or other devices (e.g.: personal computers). These devices can send and receive SMS messages by communicating with the GSM network. All of these devices have at least one MSISDN number. They are called Short Messaging Entities. To understand their roles in the GSM SMS network, please take a look at sms architecture diagram (Figure 1) below:

short messaging entites in the gsm network
Figure 1 - Short Messaging Entities (SME) in the GSM network

The SMEs are the starting points (the source) and the end points (the receiver) for SMS messages. They always communicate with a Short Message Service Center (SMSC) and never communicate directly with each other. An SME can be a mobile telephone. Depending on the role of the mobile phone in the communication, there are two kinds of SMS messages: Mobile-originated (MO) messages and Mobile-terminated (MT) messages. MO messages are sent by the mobile phone to the SMSC. Mobile-terminated messages are received by the mobile phone. The two messages are encoded differently during transmission.

An SME can also be a computer equipped with a messaging software, such as Ozeki NG - SMS Gateway, which can communicate directly with the SMSC of the service provider. For this communication, a mobile phone attached to the PC with a phone-to-pc data cable (Figure 2) or a direct IP link (Figure 3) can be used.

ozeki ng sms gateway used with a mobile phone connected to a pc
Figure 2 - Ozeki NG - SMS Gateway used with a mobile phone attached to the PC

ozeki ng sms gateway used with a direct ip connection
Figure 3 - Ozeki NG - SMS Gateway used with direct IP connection

SMS Network Architecture and Internal Protocols

In the SMS network operated by GSM service providers four layers of transport are used (Figure 1.):


SM-AL (Application Layer)
SM-TL (Transfer Layer)
SM-RL (RelayLayer)
SM-LL (Lower Layers)

Ozeki NG - SMS Gateway is located in the SM-AL layer. When sending an SMS message, the software creates protocol data units (PDUs) transported by the SM-TL layer. When a GSM device attached to the PC receives an SMS message, the message is also encoded according to the SM-TL layer PDU specification. Ozeki NG - SMS Gateway decodes this PDU and makes the message readable for computer programs and computer users.

sms network layers
Figure 1 - SMS network layers

To understand how the SMS travels from the mobile phone to the SMSC, look at Figure 2 below. In this figure you can see which protocols are used and which GSM network entities take place in the communication process. As you can see, the mobile phone (Mobile station) transmits the SMS message to the GSM base station (BTS) through a wireless link. Then the message goes though the backbone network of the service provider. The Mobile Switching Center (MSC), the Home Location Register (HLR) and, optionally, the Visitor Location Register (VLR) is used to find out the appropriate Short Message Service Center (SMSC) which will store and forward the message when the receiving party becomes available.

how sms transportation works
Figure 2 - SMS transportation

SMS messaging with a mobile phone attached to the PC

If you plan to send and receive fewer than 15 000 SMS messages per day, you can use a suitable GSM device (phone or modem) attached to your computer with a phone-to-PC data cable. For information about suitable phones, check out the Supported Phones page. The GSM device has to be equipped with a SIM card that charges (preferably) low rates for SMS messages.

With this setup you can use a computer program such as Ozeki NG - SMS Gateway to send and receive SMS messages. In this case, the software uses the attached device to communicate with the GSM network. If a message is sent out by the gateway running on the computer, it is first sent to the attached GSM device. Then the GSM device transmits it to the SMS Center (SMSC) of the GSM service provider, using a wireless link (Figure 1).

How to configure a GSM phone or GSM modem connection

gsm connectivity for sms messaging
Figure 1 - GSM modem connectivity for SMS messaging

When a message is received, the GSM device stores the message in its memory or on the SIM card, and sends a notification to Ozeki NG - SMS Gateway. When the program receives this notification, it retrieves (reads) the message from the respective memory cell, and then deletes the message from the device to make room for the next incoming message.

The advantage of using a cellular modem is that you do not need Internet connection for SMS messaging. Sending an SMS message using a cellphone takes about 5-6 seconds. Receiving takes about the same time. Good software, such as Ozeki NG - SMS Gateway allows you to attach more than one device to your PC and to use them simultaneously to increase capacity.

The best option to connect a phone to the PC is to use a standard RS232 serial cable. USB cables, InfraRed and BlueTooth connections are not as reliable. You can read more about the connection methods on the following pages:

Serial cable connection
USB cable connection
Infrared (IR) connection
Bluetooth (BT) connection
UCP Connection
SMPP Connection

RS232 Serial Cable and Industrial Modems

This page provides information about the use of an RS232 data cable, as well as about some of the most reliable GSM devices you can attach to your computer for SMS messaging using the Ozeki NG - SMS Gateway software.

In order to send and receive SMS messages from your PC, you can attach your phone to the PC with a phone-to-PC data cable (Figure 1). The cable is attached to the serial port of your computer. The serial port is located on the backside and has 9 pins. The name of the serial port in your operating system is COM1 or COM2.

how to attach the device to a pc with a phone-to-pc cable
Figure 1 - Attaching the device to the PC with a phone-to-PC data cable.

If you have different options (e.g., Serial, USB, IR, BT connection), choosing the serial cable is a good choice. An RS232 serial data cable is a simple and reliable tool. The newest modems use USB data cables. Industrial GSM modems used in environments where performance and reliability are crucial are always connected using RS232 or USB cables.

If you wish to build an environment where continuous operation is important, you should use an industrial GSM modem (Figure 2):

Multitech SMS modem

MultiTech MultiModem is a very fast and reliable modem. The modems has an external GSM antenna, an USB data cable. It can be connected directly to the power supply of your PC. To find out more about the modem, check out the MultiModem EDGE wireless modem page. To find out how to attach a MultiTech MultiModem and how to install a standard modem driver, check out the Installation of a MultiTech MultiModem page.

sierra wireless airlink fastrack

Sierra Wireless AirLink Fastrack

Sierra Wireless delivers a very goog modem. These modem works with an external GSM antenna, an USB data cable. It can be connected directly to the power supply of your PC. To find out more about the modem, check out the Sierra Wireless AirLink Fastrack Xtend EDGE Modem, FXT009 page. To find out how to attach a Sierra Wireless AirLink Fastrack modem and how to install a standard modem driver, check out the Installation of a Sierra Wireless AirLink Fastrack modem page.

wavecom modem

WAVECOM

Wavecom provides very fast and reliable modems for a good price. These modems need an external GSM antenna, an RS232 data cable. Just like the Siemens MC35, they can be connected directly to the power supply of your PC. To find out more about the modem, check out the Wavecom Fastrack page. To find out how to attach a Wavecom modem and how to install a standard modem driver, check out the Installation of a Wavecom modem page.

fargo maestro 20

Fargo Maestro 20

Fargo Maestro is a reliable GSM modem. You can read more about it on the Maestro 20 page.

fargo maestro 100

Fargo Maestro 100

Fargo Maestro is also a reliable GSM modem. You can read more about it on the Maestro 100 page.

siemens tc 35 / siemens mc35

SIEMENS TC35 / SIEMENS MC35

An excellent GSM phone released by Siemens. It can be connected directly to the power supply of the PC. It uses an external antenna, and it has a standard 9 pin RS232 interface. You need a standard RS232 "mouse extender" cable to connect this device to the PC.

nokia modems

NOKIA 30/ Nokia 32

Nokia 30 is also an excellent GSM phone. You can read more about it in its installation guide: Nokia-30-GSM-modem-terminal.pdf

Figure 2 - Industrial GSM modems

To find out more about suitable GSM devices, check out the Supported Phones page.

Installing the standard modem

This page gives you information on how you can set up your external GSM Modem as a standard modem in Windows XP. This is necessary if you wish to use Ozeki NG - SMS Gateway for MMS Messaging. Please follow these steps.

1. As a first step, you need to open your Control panel. To do this, click on Start, and select the Settings/ControlPanel menu item (Figure 1).

2. In the Control Panel Window, click on 'Add Hardware', and then in the 'Add Hardware Wizard'form, click on the 'Next' button (Figure 1).

open the control panel
Figure 1 - Opening the Control Panel


3. In the 'Add Hardware Wizard' window, select the answer 'Yes', and click on the 'Next' button (Figure 2).

is the hardware connected
Figure 2 - Add Hardware Wizard form 1


4. As a the next step, select the 'Add a new hardware device' item from the 'Installed hardware' listbox and then click 'Next' (Figure 3).

add a new hardware device
Figure 3 - Add Hardware Wizard form 2

5. Select the answer 'Install the hardware that I manually select from a list', and click on 'Next' (Figure 4).

install a hardware manually selected from a list
Figure 4 - Add Hardware Wizard form 3

6. Select 'Modems', and click on 'Next' (Figure 5).

select the modems and click the next button
Figure 5 - Add Hardware Wizard form 4

7. Place a checkmark in the 'Don't detect my modem, I will select it from a list' checkbox, and click 'Next' (Figure 6).

dont detect my modem, i will select it from a list
Figure 6 - Add Hardware Wizard form 5

8. The following step is to select the 'Standard 56000 bps Modem', and click on 'Next' (Figure 7).

standard 56000 bpd modem
Figure 7 - Add Hardware Wizard form 6


Figure 7 - Add Hardware Wizard form 6

9. Please choose 'COM1', and click the 'Next' button (Figure 8).

select com1 and click next
Figure 8 - Add Hardware Wizard form 7

Then the installation procedure is complete.

USB Data Cable

This page explains the advantages and disadvantages of using a USB data cable to attach your GSM device to the computer for SMS messaging using the Ozeki NG - SMS Gateway software. You are also provided with some information about installing a USB cable driver, including a link to a page containing step-by-step instructions on how to install a USB cable driver on different Windows operating systems.

In order to send or receive SMS messages using your computer, you can attach your phone to the PC with a phone-to-PC data cable (Figure 1). The cable can be attached to the USB port of your computer. One advantage of using USB connections is that you can attach quite a large number of phones to the same PC with the help of USB hubs available at a low cost. One disadvantage is that you have to install a driver for your cable. Some of the drivers shipped with USB cables have errors and do not allow you to build a reliable system.

usb data cable connection
Figure 1 - USB cable connection

If you install the driver software shipped with the USB data cable, a new "virtual" serial port will be registered in your computer. The name of this serial port will be COM3 or COM4 or some higher number. This is the port you have to specify when configuring the GSM Modem protocol for SMS messaging using Ozeki NG - SMS Gateway. One of the steps you need to take is to select the GSM modem or the COM port your device is attached to (Figure 2).

selecting the port in the device setting tab
Figure 2 - Selecting the port in the Device settings tab

The USB cables available for cellphones are built on a special chip called USB - Serial Bridge. This chip is located inside the cable and is powered by the USB port. When you plug your USB cable into the PC, the Windows operating system will detect this chip and will ask for the USB driver. To find out how to install it, check out the USB Driver Installation Guide. Also, you can find a video guide here.

Some USB cables can use the power current available in the USB port to charge the battery of the phone. If you purchase a cable with this option, make sure that it is charged automatically, and no special software is required. If you have to install a software for charging, there is a high probability that the installed software will lock the serial port and you won't be able to use the cable for SMS messaging and battery charging simultaneously.

If you do not have a USB data cable available for your phone, but you can get a standard RS232 data cable, you can still use USB. For this, you should install a USB - Serial converter (Figure 3). The USB-Serial converter can be attached to the PC's USB port, and the data cable can be attached to it. In this case the installation procedure will be similar to the procedure you would follow when installing a standard USB data cable. First, you attach the cable to the computer, then you install the driver for the cable. The driver will create the "virtual" com port you can use for SMS messaging.

usb to serial converter
Figure 3 - USB - Serial converter

Connect your phone to the PC with Bluetooth (BT)

You can attach your phone to your PC to send and receive SMS messages using a Bluetooth (BT) connection. The Bluetooth technology is based on radio signals. Accordingly, this connection is wireless.

A major advantage of Bluetooth compared to infrared connections is that no line of sight is required. If you have a bluetooth phone within range of your PC, it can be used to send and receive SMS messages. One problem with Bluetooth, however, is that several devices can be within range and a rather complicated pairing process is required when you establish the connection.

The Bluetooth standard provides many services. Among these services there is a Bluetooth serial connection service. To use Bluetooth on your computer, it must be equipped with a bluetooth antenna. In most cases, Bluetooth antennas are connected to the USB port of your PC. When you install the driver of a bluetooth antenna, it will register "virtual" serial ports called COM3, COM4, COM5, etc. When a bluetooth-capable mobile phone is attached, it can be accessed through one of these virtual serial ports.

how bluetooth connection works
Figure 1 - Bluetooth connection

To sum it up:
In order to use the Bluetooth connection, a PC must have Bluetooth support. This can be achieved with an USB bluetooth antenna and an appropriate driver installation. The mobile phone must be Bluetooth-capable and the Bluetooth link must be activated. Following this, the serial connection can be initiated from the PC by opening the appropriate virtual COM port (see Figure 1 above).

Connect your phone to the PC with Infrared (IR)

You can attach your phone to your PC to send and receive SMS messages through an Infrared connection. Most mobile phones have IR ports, and notebook computers are also equipped with it. An Infrared connection is a good option if you want to use Ozeki NG - SMS Gateway for short periods to send and receive messages.

IR ports cannot be used to establish long-lasting connections between the phone and the PC for two main reasons. There must be a line of sight between the two communicating parties, which is often broken if one of the devices is moved. The other problem is the way IR connectivity is implemented in GSM phones. Very often, phones switch off their IR port after a certain period (e.g. 10 minutes) automatically.

If you choose to use Infrared (IR), you must enable your infrared port on the phone. (Sometimes you have to turn it on in the PC as well). When this is done, you should place the phone within range of the IR receiver on the PC. When the PC and the phone begin to communicate over IR, you will see an icon on the right at the bottom of the screen (Figure 1).

infra red connections betwwen the cell phone and the pc
Figure 1 - IR connection between the cell phone and the PC

After this icon appears, a new "Virtual" serial port is registered in your PC. This serial port will have a standard name, e.g.: COM3. When you configure Ozeki NG - SMS Gateway, you should select this newly created COM port.

SMS over GPRS

By default SMS sending is using the "service channel" in the GSM network. This channel has limited throughput, which means it is not possible to send more then 10/12 SMS messages from a mobile device per minute. To address this performance issue, the designers of the GSM/GPRS system, have introduced SMS over GPRS. SMS over GPRS allows higher throughput. If SMS over GPRS is used, an SMS transmission speed of about 30 SMS messages per minute can be achieved.

In order to be able to use GPRS to send SMS messages, your mobile network must have SMS over GPRS support. Most mobile networks do not have this capability. It is also important to use a GPRS modem, that is able to send SMS messages over GPRS. For example the Wavecom Supreme models can do this. Most GSM/GPRS modems on the market unfortunately do not support SMS sending over GPRS. If both, your mobile network and your GPRS modem can handle SMS over GPRS you are lucky and you can use SMS over GPRS.

If SMS over GPRS is available in your network, and is supported by your GSM/GPRS modem, you will be able to achieve SMS thourghput at a much higher rate. The Ozeki NG SMS Gateway software supports SMS over GPRS. To configure it, you have to enable "Use GPRS if available to send messages (much higher speed)" option at "Message handling" tab on the modem configuration form (Figure 1).

sms over gprs settings
Figure 1 - SMS over GPRS settings

IP SMS technology

If you plan to send or receive a large number of SMS messages, it is worth considering using the Internet (Figure 1). Over the Internet (or over a private IP network, such as a leased line), it is possible to connect directly to the GSM operator's SMS Center (SMSC). The SMSC is responsible for receiving, storing and delivering SMS messages in a GSM telephone network. Direct connection to the SMSC has several great advantages.

how to send and receive bulk text messages via sms connection
Figure 1 - IP SMS connection to send and receive a large number of SMS messages

A large number of messages can be sent or received in a short time. The sender phone number can be freely modified. The availability of the service can be monitored.

If you work with great volumes of messages, this solution is cheaper, faster and more reliable than the alternative solution of using a GSM device (phone or modem) connected to a computer with a phone-to-PC data cable.

Ozeki NG - SMS Gateway enables you to connect directly to your service provider's SMSC over the Internet or a leased line using TCP/IP. In order to use this option, you need to sign a contract with your GSM service provider to be given direct access to its SMSC.

Once you have a contract, you will receive the service provider's IP address, a port number, a username and password to access their service. Often they will ask you to set up a VPN connection to their service. When a connection to the SMSC is available, an SMS protocol is required for you to be able to send and receive SMS messages. The most common protocols are UCP, SMPP and CIMD2. (Of course, all of these are supported by Ozeki NG - SMS Gateway. In fact, you can use more than one of these protocols simultaneously.) You can read more about these protocols on the following pages.

Universal Computer Protocol (UCP)
Short Message Peer to Peer Protocol (SMPP)
Computer Interface Message Distribution version 2(CIMD2)
Premium rate SMS service
SS7 protocol

Note that some service providers use custom protocols, for example XML over HTTP. If you wish to use Ozeki NG - SMS Gateway with your service provider, and your protocol is not yet included in our program, please contact us (info@ozeki.hu). There is a good chance we will provide additional support for your service free of charge.

UCP IP SMS protocol

Ozeki NG - SMS Gateway supports the Universal Computer Protocol / External Machine Interface (UCP/EMI). This protocol is often used by GSM service providers for IP SMS connectivity. The currently used protocol versions (v3, v3.5, v4.0) can be used to transfer high volumes of SMS traffic. It is used for both premium rate and normal rate SMS messages.

One of the advantages of using UCP connections is that you can specify the sender address of the message. The sender address can be a custom phone number or a short word containing alphanumeric characters. (See the instructions about the overridable checkbox below.) Note, however, that some GSM service providers restrict the use of this option.

Another advantage of UCP is that it allows sending messages of every type the GSM network can carry. It can be used to send binary SMS messages (operator logos, ringtones), WAP Push messages, as well as other types of messages. (Check out the Appendix for links to pages about different message types.) Concatenated SMS messages and various alphabets can also be used.

How to set up an UPC connection: How to set up an UPC connection

In order to use UCP to connect to an SMSC over the Internet or other private TCP/IP network, you need to subscribe to the service of a service provider.

If you wish to use UCP to connect to your service provider, you need the following information from the service provider:

IP address of the SMSC
Port number of the SMSC
User name
Password

Some service providers require you to set up an IPSEC VPN tunnel to connect to their SMSC (Figure 1).

ucp connection with vpn
Figure 1 - UCP connection with VPN

In most cases you need a fix IP address, which you have to let the GSM service provider know so that they can give you access through their firewall. In some situations, the service provider does not want you to be able to set up more than one UCP connection from your computer to their service. If this is the case, they might ask you to use a specific source port for the connection.

TCP IP SMS connections

This guide explains why is TCP/IP a good choice for transfering SMS messages. Most IP SMS protocols, such as the SMPP Protocol, the CIMD2 protocol, the UCP protocol are based on TCP/IP. Read the following section to understand why.

What is TCP/IP

The TCP/IP protocol is used to setup bidirectional, reliable communication channels over the Internet. RFC 793 defines the TCP/IP standard. This RFC is maintained by the standardization body called IETF.

How is TCP/IP SMS connection created?

Transmission Control Protocol (TCP) is designed to be a bidirectional, ordered, and reliable data transmission protocol between two end points (programs). In this context, the term reliable means that it will retransmit the packets if it gets lost in the middle. TCP guarantees the reliability by sending back Acknowledgment (ACK) packets back for a single or a range of packets received from the peer. See the TCP state diagram (Figure 1).

Figure 1 - TCP/IP connection state diagam

How is TCP/IP SMS connection destroyed?

TCP is a bidirectional communication protocol, so when the connection is established, there is not a difference between the client and the server. Also, either one can call quits, and both peers needs to agree on closing to fully close an established TCP connection. This goes same for the control signals such as termination request/response.

Let's call the first one to call the quits as the active closer, and the other peer the passive closer. When the active closer sends FIN, the state goes to FIN-WAIT-1. Then it receives an ACK for the sent FIN and the state goes to FIN-WAIT-2. Once it receives FIN also from the passive closer, the active closer sends the ACK to the FIN and the state goes to TIME-WAIT. In case the passive closer did not received the ACK to the second FIN, it will retransmit the FIN packet.

RFC 793 sets the TIME-OUT to be twice the Maximum Segment Lifetime, or 2MSL. Since MSL, the maximum time a packet can wander around Internet, is set to 2 minutes, 2MSL is 4 minutes. Since there is no ACK to an ACK, the active closer can't do anything but to wait 4 minutes if it adheres to the TCP/IP protocol correctly, just in case the passive sender has not received the ACK to its FIN (theoretically).

In reality, missing packets are probably rare, and very rare if it's all happening within the LAN or within a single machine.

Common protocols - Premium-rated SMS services

Mobile service providers often allow 3rd party content providers to create mobile services using premium rate SMS messages. These services may be games for prizes, tests, data services etc. Premium rate SMS messages make it possible to collect money from users of these value-added services. Since the amount of money collected is rather small, these services are often referred to as micropayment services.

Today's most popular premium SMS services are downloadable games, logos, ringtones, background pictures and information services (e.g.: weather, news, programs).

These services work in the following way:

The person who would like to use the premium rate service sends an SMS message to a premium rate phone number. When the SMS arrives in the Short Message Service Center (SMSC) of the service provider, the SMSC recognizes that the destination phone number belongs to a "content server". As the next step, the message is transferred to a content provider's server over a TCP/IP connection. The content provider's server receives the SMS messages and generates a response SMS according to the implemented business logic. The response SMS travels back to the SMSC for transmission over TCP/IP, just as the request SMS was transferred to the content server. In most situations, the content server and the SMSC communicate over the Internet (Figure 1).

the premium-rated service architecture
Figure 1 - Premium-rated service architecture

The business logic of the content server can be simple or complex. One of the most common solutions is based on content interpretation. A simple algorithm compares the incoming message text to a set of keywords, and generates a response based on the keyword. Another common application collects the phone numbers of the received messages and uses these phone numbers to provide periodic information services, such as traffic report or weather report every morning. There are many other types of solutions, as well. One thing they have in common is that in every case a reply SMS message must be sent back to acknowledge the service request within a limited response time (usually in 2 minutes).

Some useful information:

  • Premium rate SMS prices cannot be chosen freely. In most cases the content provider must select a price offered by the GSM service provider.
  • One premium rate phone number can run several services, but can only operate with one price.
  • It is not possible to send/receive premium rate SMS messages using SIM cards of foreign countries. It means that there is no such thing as premium rate roaming.
  • When creating a solution, it is important to check if premium rate messages can be sent to our service from every GSM network in the country. Sometimes it is necessary to sign a contract with all GSM providers independently.
  • Premium rate SMS services cannot be operated using a GSM phone attached to the PC with a phone-to-pc data cable.
  • Premium rate SMS service phone numbers are often different from normal price phone numbers. They often use a special prefix, such as 06 90.
  • If there is no response to the premium rate SMS, the Mobile Service provider does not charge the customer.

SMPP gateway

Introduction to SMPP

The Short Message Peer to Peer (SMPP) protocol is an open, industry standard protocol designed to provide a flexible data communication interface for the transfer of SMS in the mobile network. It is used to transfer SMS messages between External Short Message Entities (ESME), Routing Entities (RE) and Short Message Service Centers (SMSC). SMPP is capable of carrying any text message type.

The SMPP protocol today (in 2022) is most often used to transfers messages between businesses and SMS service providers. Businesses operate SMS sending applications hosted in their data centers. These applications connect to SMS service providers using the SMPP protocol. The SMPP protocol is based on a TCP/IP link that is established between a computer in the data center of the business and the computer of the of the sms service provider.

The computer of the business, that is sending the messages is called the SMPP client. The computer of the service provider, who is responsible for delivering the SMS messages to the mobile network is called the SMPP server. The SMPP server is also often referered to as Short Message Service Center (SMSC) or Message Center (MC).

The SMPP link between the SMPP client and the SMPP server is most frequently a secure VPN connection (Figure 1). Secure SMPP services use TLS over TCP/IP to encrypt the connection.

smpp gateway
Figure 1 - SMPP connection between a PC and the SMSC

How can I use the SMPP protocol to send SMS from my own business?

If you wish to use the SMPP protocol to connect to the SMSC of a mobile network operator or an Internet based SMS service provider, you need to setup an SMPP gateway. To configure the SMPP gateway, and you need to get the SMPP server address and the SMPP login credentials from an SMS service provider.

What is an SMPP gateway?

An SMPP gateway is an SMS delivery software installed on the computer of businesses. An SMPP gateway, such as Ozeki NG SMS Gateway, uses the SMPP protocol over the internet to send and receive sms messages to SMS services.

How do business use an SMPP gateway?

Business users can use the SMPP gateway in various ways. Office users prefer to use E-mail to SMS or Excel to SMS solutions, while software developres write SMS applications using an API (e.g. C# sms api), or use an SQL to SMS setup.

What is an SMPP gateway address, and where do I get one?

To setup an SMPP gateway you need to get the following information from your sms service provider:

  • Get the IP address or hostname of the SMPP service
  • Find out the port number of their SMPP service
  • Ask for user name (which is often called as SMPP System ID)
  • Ask for a password

The IP address and port are called the SMPP server address.

The SMPP System ID and password are called SMPP login credentials.

What else do I need to use an SMPP gateway

To use an SMPP gateway, you also need the SMS sender ID. The SMS sender ID is the phone number that will be displayed on the recipient mobile as the sender of the SMS. Your SMS service provider will either give you a phone number, a phone number range, an alphanumeric sender ID or an SMS short code sender ID. Some providers allow you to use any phone number or alphanumeric string as a sender ID. You need to configure the SMS sender ID in Ozeki NG SMS Gateawy when you configure the SMPP connection.

SMPP sender ID alternatives:

  • Phone number or long code. The SMPP sender address is a full phone number. Example: +36201234567
  • Alphanumeric sender id. The SMPP sender id is made up of letter and nubmer. Example: Ozeki
  • A short code as SMPP System ID. A short number of digits. Example: 1234
  • Address range. A list of phone number you can pick from. Example from +36201111111 to +36202222222
  • Free to choose sender ID. Example: any of the above chosen on a per sms basis

Are there any free SMS services I can use with my SMPP gateway?

Although there are no free SMS services on the Internet, you can create a free SMPP service for yourself with the help of your Android mobile phone. In this case your Android mobile will be the SMS service provider. The SMPP server address will be the IP address and port of the phone, and the you can setup your own SMPP username and password. The SMPP sender ID will be the phone number of the SIM card in the phone. You wil connect to your Android mobile phone over Wifi.

To setup your Android Moible phone as an SMS service provddier first read the SMS Gateway technology overview guide, then setup an Android SMPP gateway app on your mobile. The Android SMS gateway app will give you access to the built in SMPP server of the Android mobile phone. Please also read the how can I send sms free of charge guide. Note that running an SMPP gateway on your Android mobile will be limited in terms of capacity to a few thousand SMS per day. You can only increase the capacity by using multiple phones connected to a centeral SMS gateway.

For business applications we recommend you to setup an SMPP gateway on a powerful windows computer instead of a phone, and subscribe for an on-line SMPP sms service. The SMS Gateway technology guide is a must read if you consider this option.

How can I setup my own SMPP gateway

If you wish to setup your own SMPP gateway, follow the instructions on the How to set up an SMPP SMS gateway page

Further information on SMPP Gateway technology and the SMPP protocol

For a better understanding of SMPP, you should be familiar with some of the following terms. A Message Center (MC) is a generic term used to describe systems such as a Short Message Service Centre (SMSC), GSM Unstructured Supplementary Services Data (USSD) Server, or Cell Broadcast Centre (CBC).

An ESME typically represents a fixed network SMS client, such as a WAP Proxy Server, E-mail Gateway, or Voice Mail Server. It may also represent a Cell Broadcast Entity (CBE). A Routing Entity (RE) is a generic term for a network element that is utilized for MC to MC and ESME to MC message routing. A RE has the ability to emulate the functionality associated with both an MC and an ESME. To an ESME, a RE appears as a MC and to a MC, a RE appears as an ESME. A carrier may utilize REs to hide a network of Message Centers, presenting only the REs as the external interface points for ESMEs.

Figure 2 illustrates the context of SMPP in a mobile network:

the smpp inside the mobile network
Figure 2 - SMPP inside the mobile network

How to setup the SMPP sms gateway

This guide presents how to setup an SMPP sms gateway on Windows. It will start with defining what an SMPP sms gateway is and will move on to the setup procedure. We assume you will use these directions to create an SMPP service to serve customers and business users, so we take care to present instructions that will help you create a reliable solution. This page requires some basic knowledge of the SMPP protocol used in SMPP sms gateways and some networking know-how. You will be presented with a few important definitions, well structured step by step instructions and some information on operating the SMPP sms gateway in a virtual machine environment. We hope you will enjoy it.

What is an SMPP sms gateway

An SMPP sms gateway is an sms software communication platform, that is used to provide sms services. An SMPP sms gateway, such az Ozeki SMS Gateway makes it possible to create SMPP client connections and to offer SMPP server services.

How is an SMPP sms gateway used

The reason SMPP sms gateway technology is popular is due to the fact that it can be used to send large volume of SMS messages over the Internet. In other words it is an ideal choice to provide bulk sms service. It is also used by sms content providers to push SMS noticiations, reminders, location infromation or marketing messages to mobile users.

How to setup an SMPP sms gateway (quick instructions)

To setup an SMPP sms gateway start with the following sequence of tutorial steps:

  1. Install Ozeki NG SMS Gateway, then launch your browser with the red Ozeki NG icon on your Windows desktop. This will open the Ozeki NG GUI in your webbrowser.
  2. In the Ozeki home page you will see 3 panels: the SMS service providers panel, the SMS routing panel, SMS users/application panel. Click "Add service provider" in the Service providers panel.
  3. Select the SMPP client connection from the list and click add.

How to setup an SMPP sms gateway (video)

The following video shows you how to create an SMPP client connection using Ozeki NG SMS Gateway. It assumes that Ozeki NG sms gateway is already installed, and it starts from the home screen. You will see in the video where do you have to enter the SMPP gateway IP address, port and SMPP system ID (username) and the SMPP password.

Hardware requirements of the Ozeki SMPP sms gateway solution

  • CPU: 4 cores
  • RAM: 4 GB (16 GB recommended)
  • Hard disk space: 4 GB (SSD recommended)
  • Ports: RS232 or USB (if you use a GSM modem)
  • Phone-to-PC data cable (USB or RS232) (only if you need use a modem)
  • Network: Internet connection (if you use IP SMS connection)

Software requirements of the Ozeki SMPP sms gateway system

  • Windows 10 or Windows server
  • Access to the Windows desktop (locally or remotely)
  • Administrative privileges on the system
  • Firewall access
  • .Net 4.5 or later (comes with Windows 10)

Install the SMPP sms gateway

To setup the SMPP sms gateway, first you need to download ozeki ng sms gateway installation package from ozekisms.com, then you need to perform the standard SMS gateway installation steps (Figure 1), finally you need to open the management console to create the SMPP sms gateway configuration (Figure 2).

install smpp sms gateway
Figure 1 - Install SMPP SMS Gateway

Open the SMPP sms gateway home screen

To create an SMPP SMS gateway conifguration, first you should setup an SMPP client connection to an sms service provider. SMS messages will be sent and received through this connection to the mobile network. Note that you may also connecto to an SMPP user account offered by an SMPP server of another SMPP SMS Gateway installation.

open smpp sms gateway
Figure 2 - Open SMPP SMS Gateway

Click install next to the SMPP client connection

To create the SMPP client connection to the mobile network you need to click on the Install link next to SMPP connection entry in the Add service provider connection page (Figure 3).

configure smpp sms gateway
Figure 3 - Configure SMPP SMS Gateway

Next tasks

Once you have connected your SMPP SMS Gateway to the mobile network, you can create SMPP user accounts to provide SMS service to customers. You may setup credit limits and accounting for your SMPP user accounts. To control the routes your messages use, you can setup Inbound SMS routing rules and outbound SMS routing rules. Finally you will probably configure SQL reporting to get detailed information about the SMS messages sent and received by your SMPP users and SMPP links.

Operating the SMPP sms gateway on a virtual machine

Notwithstanding that the SMPP sms gateway performs better on a physical computer, there are quite a few incentives to using a virtualized environment. Many people take this option when they use an SMPP sms gateway. Maybe the biggest benefit to operating an SMPP sms gateway in a virtualized environment is that it can be hosted in a server hosting facility. Google Cloud, IBM cloud hosting and Kamatera are popular choices among the businesses we do business with. If the SMPP sms gateway is hosted at such a company, you don't have to take care of hardware issues.

If you operate your own virtualized environment, you will like the fact that system backup and system restore becomes very easy in such environments, because the whole virtual machine can be backed up as easily as copying a file. It is also great that it makes it easy to upgrade or replace the unerlying hardware. A handicap to using a virtual machine is that the virtual machine shares the resources of the host computer with other virtual machines. If other virtual meachines eat up the resources, the can slow down. If you run the SMPP sms gateway on a virtual environment make sure you assign sufficient virtual CPUs and virtual memory to the system. This is neccessary, because you want to make sure, that you don't miss out on performance. Also make sure that the virtual network for the SMPP sms gateway is set up properly.

VMware Fusion, VMware Workstation Player, Boot Camp, Citrix Hypervisor, Parallels Desktop, Windows Virtual PC, QEMU, Solarwinds Virtualization Manager can be used to operate the SMPP sms gateway. It is known to work in these environments.

Is it possible to use a custom Sender ID with an SMPP sms gateway?

Since an SMPP sms gateway connection is an IP sms connection, it sends application originated (AO) messages. AO messages can set a custom sender ID for each outgoing SMS. You can change the SMS sender ID to a custom phone number, to an alphanumeric sender ID, or to a short code sender ID.

Conclusion

To recap we can state, that to connect to sms services with the SMPP sms gateway is quite easy. By following the above directions you can create the solution quickly. If you have already completed the steps I am sure if you let your wife (or girlfriend) know, you will be rewarded. If you would like to receive more about the incentives of other smpp sms software products, please open ozeki.hu.

SMPP Version Information

This guide is intended for developers who want to use and integrate SMS over SMPP into their corporate information system. It describes the basic PDUs implemented in the Ozeki SMPP client.

Current SMPP Version Supported by Ozeki NG - SMS Gateway is: SMPP V3.3, SMPP V3.4 and SMPP v5.0

For binding you can use transmitter, receiver and transceiver. If you have an option transceiver is recommended.

The SMPP PDUs that are implemented are:

Connecting to the SMPP Server

  • BIND_TRANSCEIVER / BIND_TRANSCEIVER_RESP
  • BIND_TRANSMITTER / BIND_TRANSMITTER_RESP (was implemented for version v3.3, currently not used)
  • BIND_RECEIVER / BIND_RECEIVER_RESP (was implemented for version v3.3, currently not used)

Checking link activity

  • ENQUIRE_LINK / ENQUIRE_LINK_RESP (Ozeki NG - SMS Gateway checks link activity every 300 seconds; if the link is not active, it will try to reconnect to the server.)

Closing the connection to the SMPP Server

  • UNBIND / UNBIND_RESP

Sending and receiving SMS messages

  • SUBMIT_SM / SUBMIT_SM_RESP
  • DELIVER_SM / DELIVER_SM_RESP

Common protocols - CIMD2

The Computer Interface Message Distribution (CIMD) protocol was introduced by Nokia. The Nokia SMS Center includes an CIMD2 interface that transfers messages between applications and the Nokia Short Message Service Center (SMSC).

CIMD2 is version 2 of the Computer Interface to Message Distribution protocol. The CIMD2 interface is suitable for client applications that send and retrieve messages over TCP/IP sockets, such as Ozeki NG - SMS Gateway.

An application is interconnected through the CIMD2 connection to an SMS Center. The main purpose of this interconnection is to transfer messages from the applications to the mobile stations (MS) and from the MSs to the applications. Other kinds of information can also be conveyed over the interconnection, e.g., status reports from the GSM/GPRS network to the applications.

CIMD2 is capable of transferring any SMS message type, just like UCP/EMI and SMPP.

A CIMD2 connection can be used through an IP link. This link can be a leased line or the Internet. Optionally the link can be protected by VPN (Figure 1).

cimd2 connection with vpn protection
Figure 1 - CIMD2 connection with VPN protection

If you wish to use CIMD2 to connect to your service provider, you need to get the following information from the service provider:

IP address of the SMSC
Port number of the SMSC
User name
Password

SS7 performance

SS7 is the signaling protocol used between SMSCs in the core GSM network. It can carry SMS messages using the SS7/MAP protocol. SS7 works through ISDN lines or through IP. The IP version is not as widely used as the ISDN version. The IP version of SS7 is called SIGTRAN.

Concerning performance, one SS7 link can carry between 12-18 SMS messages per second. If you use four SS7 links at a time, you can carry around 60-70 messages per second. On an E1 connection, you can take up to 30 SS7 links, but practically you may not get more than 16 links. This means that the real speed limit of an SS7 over E1 connection is around 240-300 SMS per second.

Paradoxically Sigtran may give you lower performance, since all the processing load is on your main CPU (rather than offloaded to a specialized SS7 board.

If you connect your Ozeki NG SMS Gateway system to an SMS service provider, that connects to the SS7 network through a single E1 line, your maximum speed will not exceed 300 SMS per second even if you use the provider's full throughput.

USSD Basics

Unstructured Supplementary Services Data (USSD) is a GSM service which allows high speed interactive communication between the subscribers and applications. It is similar to SMS in the way that it allows to send and receive short text messages. It is different in the way that it is session oriented.

Since USSD is session oriented, it gives a very short delay between sending the query and receiving the response. This makes it ideal to query information from the network and to provide text content as a service.

An USSD Gateway is a platform that enables Operators to introduce messaging services with USSD as the bearer, enabling faster response times. The platform is complementary to SMS service and an SMS gateway. An USSD gateway acts as a Gateway between applications and the GSM network and lets you deliver USSD messages of up to 182 characters on a network between mobile stations and applications.

Both SMS and USSD technology use the signaling channel as the bearer by default. (SMS can also use GPRS). While SMS provides a store and forward functionality, USSD is not like this. It is a real time session-oriented service, which means that when a user accesses a service with USSD, a session is established and the radio connection stays open until the user, application, or time out releases it. This provides faster response times for interactive applications. An USSD session needs to be allocated to each and every interaction.

A typical USSD Gateway uses the same application programming interface that the Short Message Service Center does. Therefore, it is easy to port services based on SMS to utilize USSD as the bearer. In practice, only USSD specific modifications are needed to external applications.

An USSD gateway is usually equipped with session management capabilities, that can handle cell switching, to make sure an USSD Session is preserved even when the subscriber changes cells.

A big advantage of USSD comes while the mobile client is roaming. This is because USSD services are well available in roaming networks and all the USSD messages are directed towards the subscriber's Home Network itself, thus, same set of services that are available in home network can be given in visited network too, giving subscribers a Virtual Home Environment (VHE).

An USSD gateway communicates with GSM network entities, such as the HLR using SS7 (Signaling System 7) protocol stack's MAP (Mobile Application Part). It receives and sends out session IDs from the session ID pool, and maintains and destroys the sessions The MAP (Mobile Application Part) layer is present both on the server and on the mobile phones.

The USSD gateway's primary task is to wait for messages from the MAP layer and to route these messages into a content provider system through SMPP or HTTP or any other way. The content provider system can return an USSD response. Allthough the USSD gateway's primary task is to wait for messages, it can also push messages, because it allows both user initiated (pull) and service initiated (push) sessions. Thanks to supported 1-way and 2-way mobile sessions the USSD Gateway enables simple notifications as well as interactive dialogs.

The service provided by the USSD Gateway depends on the ability of the delivery agent or the source to send and receive USSD messages. The Home Network subscriber or the inbound roamer can send an USSD string to maintain or open an interactive session. The MSC connects through to the HLR in the home network (via the SS7 network). The HLR routes the request to the USSD Gateway, which in turn routes the request to the USSD content server. The content server provides the call handling instructions response back through the same path to the serving MSC in the visited or home network.

For each transaction, the USSD Gateways knows what session is going on and if you work with a locator, you also have information about which cell is the GSM phone located at.

The following terms are also important to mention: PSSR, USSN and USSR. Unstructured Supplementary Service Request (USSR) is a message, that can be used to initiate a session by the USSD gateway to the mobile user.

Today almost all mobile networks support the SS7 standard CAMEL for prepaid charging and interoperability. If CAMEL Phase 2 based charging interface is implemented in the USSD Gateway, it is able to perform real-time billing on almost any mobile network. CAMEL based charging should be supported for both network and mobile initiated USSD sessions.

Ozeki NG SMS Gateway is not an USSD gateway. It can act as a client for USSD services by sending and receiving USSD messages on supported GSM modems. Read more about USSD support in Ozeki NG SMS Gateway at the USSD message type page.

GSM modem based wireless links vs IP SMS connections to the mobile network

In this guide you can read about how you can connect your system to the mobile network and which connection method will best suite your needs. You will read about Internet based SMS connections and GSM modem/GSM phone based (wireless) connections. It is strongly recommended to read this article, because it will help you design a well working system.

Introduction

In general, when you make a decision whether you want to use an Internet SMS connection or a GSM modem the first and most important thing to check is the volume of SMS messages you expect to be sent or received in the system. If you will send or receive less then 12000 SMS messages per day a GSM modem will probably be a good option. If you will send or receive more, you should consider to use some kind of Internet SMS connection.

SMS messaging with a GSM modem/GSM phone

If you wish to connect your system to the mobile network wirelessly, you need a GSM modem or GSM phone, that you can attach to your computer with a data cable. In this case your Ozeki NG SMS Gateway software will operate this phone and will send and receive SMS messages wirelessly. To setup this connection method, you need the following components:

Figure 1 - Prerequisites for Ozeki NG SMS Gateway GSM modem connection

Your checklist (for GSM modem connection):

checkbox

SIM Card - You can get this from your local mobile network operator.*
checkbox

Modem - Use a Wavecom, Siemens or Multitech modem.
checkbox

Data cable - Comes with the modem
checkbox

Computer - Recommended: Intel P4 3Ghz, 2GB RAM, 500MB HDD, Windows OS
checkbox

Ozeki NG SMS Gateway - Download it from www.ozekisms.com

*The SIM card will come with a plan, that will determine how much money you will spend on each SMS.

Once you have all the prerequisites, you need to put the SIM card into the phone or modem and you need to attach it to your computer's serial port with a data cable. If your computer does not have a serial port you can use an USB data cable or a USB to RS232 converter. The quick start guide gives you the steps to setup a GSM modem/GSM phone connection, or you can watch the following video: How to send SMS using a GSM modem from a computer.

GSM modem vs GSM phone

When you setup a wireless connection, it is recommended to use a dedicated GSM modem instead of a standard GSM handset. The reason for this is that standard mobile handsets tend to be unreliable. They have a battery, that is likely to fail over time, and their software might not be very stable due to short development cycles. Although standard handsets can be used for sending messages, there is a good chance, that their built in SMS client software will "eat" incoming delivery reports and incoming SMS and MMS messages, and these messages will never make it to the PC through the data cable.

GSM modems are designed for long term use. They have simple, very reliable software that makes SMS and MMS sending and receiving possible. They also have an external antenna giving better signal strength and an external power supply that is not likely to fail.

Advantages of using a GSM modem/GSM phone connection over Internet connections:

  1. If you use a wireless connection to the mobile network through a GSM modem, Internet outages will not stop your system from sending or receiving messages. A wireless connection to the mobile network will work even if a network cable is torn by an excavator at some construction site.
  2. GSM modem based SMS systems are cost efficient. It is very easy to find a price plan, whith low or zero cost SMS tariffs when you purchase a SIM card.
  3. Wireless SMS systems can be setup in a very short time. You can attach almost any mobile phone to your computer with a datacable and you can start sending SMS messages in minutes. Although almost any mobile phone will work, a reliable GSM modem is preferred to have a reliable system.

Disadvantages of using a GSM modem/GSM phone connection:

  1. A single GSM modem can serve up to 12000 SMS messages per day. You can double or triple this number by adding a second or third modem, but this SMS volume still might not be sufficient for every system.
  2. A wireless connection can also fail. For example on new years eve, when everybody is sending new year's greeting SMS to each other the GSM networks might fail to accept messages from mobile devices.
  3. The mobile phone subscription on the SIM card might run out of money. If you use a prepaid SIM card, you will not be able to send SMS messages until you top up your balance.
  4. Only a fix sender address can be used. When you send out an SMS messages the phone number of your SIM card will be the sender address of your messages.

SMS communication through the Internet (IP SMS)

Internet based SMS connections are also called as IP SMS connections. These connections use a TCP/IP link to connect to the Short Message Service Center (SMSC) of a mobile network or an SMS service provider. On this TCP/IP link an upper layer protocol is used to send and receive the messages. In order to setup this solution you need the following prerequisites:

Figure 2 - Prerequisites for Ozeki NG SMS Gateway IP SMS connection

In this case you need to find an SMS service provider who can reach the mobile phones in your area. This SMS service provider should be able to provide SMS service through the Internet. To find such a provider, you can check our website where we list some of them: SMPP SMS Service providers. Once you have found such a provider, you need to sign up for their service to get the connection parameters. You can use these parameters to configure your Ozeki NG SMS Gateway software.

When you select an operator the most important thing is to select one that supports an official SMS protocol. There are 3 official SMS protocols: SMPP, UCP, CIMD2. All of these protocols were designed to serve SMS communication needs. They are asynchronous, high speed, and provide all the functionality SMS communication requires. Some providers will offer SMS service over HTTP. HTTP was designed to serve webpages not SMS. It adds a lot of overhead to SMS communication and is not nearly as fast and efficient as the official SMS protocols. If you sign up for an HTTP SMS service, there is a good chance, that your system will not receive incoming messages and will not be able to handle SMS delivery reports.

The most popular IP SMS protocol is SMPP. Check out the following link on how to configure an SMPP SMS service in Ozeki NG SMS Gateway:

Although not as popular, the UCP (often referred to as UCP/EMI) and CIMD2 will work just as well. The following pages give you setup instructions for these protocols:

If your only option is HTTP, check out this guide to get instructions on how to setup an HTTP SMS Service provider connection:

Advantages of Internet based SMS service provider connections:

  1. High speed. Internet SMS connections can serve up to 500 SMS messages per second
  2. No physical device is needed.
  3. Problems with wireless links, such as low GSM signal strength will not effect your system
  4. Flexible sender address assignment is possible. When you send out an SMS messages you can freely specify the sender phone number.

Disadvantages of Internet based SMS service provider connections:

  1. Can be time-consuming finding the appropriate person and signing a contract with a large mobile network operator to allow your system to connect to their Short Message Service Center (SMSC)
  2. Can be expensive. SMS Service providers often require you a monthly fee or a minimum monthly SMS volume.
  3. Takes more time to setup. Often firewalls need to be opened and parameters need to be negotiated with the SMS service providers.

Switching from GSM modem to IP SMS connection

Our customers often start with a GSM modem connection and a lower capacity software license first and they switch over to IP SMS connection and a higher capacity license when the SMS traffic on their system increases. This switch can be made seamlessly and it does not require any real change. All is needed is a small configuration change in Ozeki NG SMS Gateway: The new IP SMS connection should be configured and SMS traffic should be routed to it from the old GSM modem connection.

Building a fail-safe system

If possible it is best to have both a wireless and an IP SMS connection at the same time and Ozeki NG SMS Gateway should be configured to use the IP SMS connection when available, and if the IP SMS connection fails for whatever reason, the software should switch over to the wireless connection automatically to keep the SMS communication working. This automatic failover switching can be setup by installing two service provider connections and by configuring a backup route in Ozeki NG SMS Gateway.

To sum it up

Whatever your needs are, it is worth to spend some time on picking the appropriate connection method. In all cases Ozeki NG SMS Gateway will be a good choice to manage the connection. If you have Ozeki NG SMS Gateway installed you can check the "Add service provider" link on the Management console to find out more information.

If you don't have Ozeki NG SMS Gateway installed, I recommend you to proceed to the download page:

Download Ozeki NG SMS Gateway!

Ozeki NG vs Ozeki 10

If you would like to build a communication system that could handle the connection between a computer and a service provider to send SMS messages, you will have two options. If you wish to send SMS messages only and you do not want to implement the software into your corporate chat communication channel, or you have an older OS running on your computer, the correct choice for you is the Ozeki NG. On the other hand, if you wish to have a more secure, more versatile gateway software that could handle a corporate chat software and SMS messages as well as an e-mail communication channel, the best choice for you is the Ozeki 10 software package. Below, you could examine the table where we list you all the main differences between the two software.

Ozeki NGOzeki 10
First release 2007 2018
Supported OS Windows Xp, 20xx, Vista, 7, 8, 10 Windows 7, 8, 10
Windows 201x
Linux on Intel
Linux on Arm
Messaging SMS (Mobile network) SMS (Mobile network)
P2P (Internet)
Security No encryption SSL/TLS for SMS clients (SMPP, UCP, CIMD2)
HTTPS graphical user interface (GUI)
End-to-end security in Peer to Peer (P2P)
Built in clients GSM Modem
SMPP client
CIMD2 client
UCP client
HTTP client
Service provider specific connections
GSM Modem
SMPP client
CIMD2 client
UCP client
HTTP client
Service provider specific connections
Built in servers SMPP (SMS service)
HTTP (SMS service)
SMTP (E-mail to SMS)
POP3 (E-mail to SMS)
SMPP (SMS service)
UCP/EMI (SMS service)
CIMD2 (SMS service)
HTTP (SMS service)
P2P (Internet chat)
SMTP (E-mail to SMS)
(No POP3 support)
Message routing model
Outbound:Users to Network connections
Inbound:Network connections to users
Outbound:Users to Network connections
Inbound:Network connections to users
Internal:Users to Users
External:Network connections to Network connections
API HTTP API
SQL API
Text file API
HTTP API
SQL API
Text file API
User authentication Local system users Local system users
SQL user database
HTTP user database
LDAP user database
Active directory
P2P user authentication
Graphical user interface Page refresh model, http, minimal AJAX
(The GUI is faster in Ozeki NG)
Full AJAX, https, secure websocket
Live updates and status information updates without page reload
(The GUI is slower in Ozeki 10)

Download Information

You can download Ozeki NG - SMS Gateway software and the necessary prerequisites from the Download page.

The download URL is:

You need to download the following packages:

  • .NET Framework 4.0
  • Ozeki NG - SMS Gateway

To start downloading, click the download link. You can decide whether to open the file or view the downloads. If you open it, the installation process will start immediately (Figure 1).

Figure 1 - Downloading the software


To find out how to install the program, check out the Installation Steps in the next chapter.

Installation Steps

In this guide you can learn how to install Ozeki NG - SMS Gateway software. You will be instructed what to do in each dialogue box of the Ozeki NG - SMS Gateway Setup Wizard to successfully finish the installation.

Step 1 - Downloading Ozeki NG SMS Gateway

The latest release of Ozeki SMS Gateway can be downloaded from the Ozeki 10 SMS Gateway download page. To download the installer in compressed format, you need to click on the first OzekiNG-SMS-Gateway_x.x.xx.zip link as Figure 1 shows below. We recommend you to always download the latest version. This version always contains all the currently available features and improvements.

downloading the ozeki ng sms gateway
Figure 1 - Downloading Ozeki NG SMS Gateway

Step 2 - Open the downloaded file

When the download finished, you have to open the compressed file to be able to run the installer of the software. For that, please click on the downloaded file as you can see it on Figure 2 in your browser or open the Downloads folder on your computer.

open the downloaded file
Figure 2 - Open the downloaded file

Step 3 - Run the installer

After you extracted the .zip file, just click on the executable file to start the installation process just like in Figure 3.

run the downloaded installer
Figure 3 - Run the installer

Step 4 - Install Ozeki NG SMS Gateway

As soon as you clicked on the .exe file, the installer starts with a License Agreement screen (Figure 4). Please review them then, click 'I Agree' button to continue.

Agree the installers license agreement
Figure 4 - Run the installer

Step 5 - Set installation location

On the next page define the destination folder of the Ozeki NG SMS Gateway. Click install to start the installation (Figure 5).

set the installations location
Figure 5 - Set installation location

Step 6 - Set admin password

During the installation you need to define the password for the admin user. You will be able to use this password to login into Ozeki NG SMS Gateway (Figure 6).

set the admins password
Figure 6 - Set admin password

Step 7 - Login to the GUI

After the installation finishes, both the Installation Complete dialog box and the login window will show up. Enter the username and the newly created password and click on the OK button to login (Figure 7).

login to the graphical user interface
Figure 7 - Login to the GUI

Step 8 - Ozeki NG SMS Gateway home page

Finally the home page of the Ozeki NG SMS Gateway will appeare (Figure 8).

the home page of the ozeki ng sms gateway
Figure 8 - Ozeki NG SMS Gateway home page

System database

Storing great numbers of messages in files can slow down your system especially when messages need to be read/imported before sending. To avoid this issue you can use System Database option of Ozeki NG SMS Gateway that will store all messages in a database instead of a file. In this way you can speed up sending of great numbers of messages.

Please read how you can import messages into a database: System Database Importer

To configure System Database option go to Edit menu and select Server Preferences sub-menu in Ozeki NG SMS Gateway (Figure 1).

server preferences menu
Figure 1 - Server Preferences

Click on Databases tab and select System database settings. Here enable Use database server instead of file system to store message option. Then specify Database connection type and Database connection string and provide the following parameters (Figure 2):

system database setting window
Figure 2 - System database settings

Please note:

When you switch to System Database, you can receive an error message since the system cannot find messages. The reason for this: the system searches for messages still in the file but system database stores them in a database. To avoid this error message please read How to import messages into system database.

  • Oracle Configuration
  • MSSQL 2008 Configuration
  • MySQL onfiguration
  • System database configuration in Oracle

    In case you need to store great numbers of SMS text messages it is possible that your system will be slowed down by this amount of stored files. By default, Ozeki NG SMS Gateway stores messages in files. In this way, it is highly recommended to use the System Database option in Ozeki NG SMS Gateway. This option allows you to speed up message sending. On this webpage you find a detailed configuration guide for using System Database with Oracle.

    Please note!!!

    When you switch to System Database, you need to restart the Ozeki NG service. After this, it is possible that you receive an error message since the system cannot find messages.

    The reason for this: the system still searches for messages the file but system database stores them in a database. To avoid this error message please read How to import messages to System Database and How to switch from file to database sections.

    Configuration steps

    Go to Edit menu and select Server preferences menu item. Select Databases tab and click on System database settings tab. Here, enable Use a database server instead of file system to store messages. Database connection type needs to be set to OleDb.(Figure 1)

    Provide your Connection string to the database. e.g.: Provider=OraOLEDB.Oracle.1;Persist Security Info=False;User ID=admin;Password=qwe123

    sql sms database settings
    Figure 1 - System database settings

    After this, provide the SQL statement for each tab:

    Create tab:
             
    DECLARE N NUMBER;
    BEGIN SELECT COUNT(*) INTO N FROM ALL_TABLES WHERE
    TABLE_NAME='$utablename';
    IF N = 0 THEN EXECUTE IMMEDIATE 'CREATE TABLE "$utablename" (MESSAGEID VARCHAR(60) 
    DEFAULT NULL,CREATEDATE VARCHAR(100) DEFAULT SYSDATE,SERIALIZEDMESSAGE CLOB DEFAULT NULL)';
    END IF;
    END;
    
    Load index tab:
     
    SELECT MESSAGEID,SERIALIZEDMESSAGE FROM "$utablename" WHERE MESSAGEID IN ($idlist)
     
    Load tab:
     
    SELECT MESSAGEID,SERIALIZEDMESSAGE FROM "$utablename" WHERE MESSAGEID IN ($idlist)
    
    Save tab:
     
    DECLARE vClobVal VARCHAR2(32767) := '$serializedmessage';
    BEGIN INSERT INTO "$utablename" (MESSAGEID,SERIALIZEDMESSAGE) VALUES ('$messageid',vClobVal);
    END;
    
    Delete tab:
    DELETE FROM "$utablename" WHERE MESSAGEID IN ($idlist)
    
    Move tab:
    INSERT INTO "$utablename" (MESSAGEID, CREATEDATE,SERIALIZEDMESSAGE) SELECT MESSAGEID, 
    CREATEDATE, SERIALIZEDMESSAGE FROM "$usourcetable" WHERE MESSAGEID IN ($idlist)
    
    Find old tab:
    SELECT MESSAGEID FROM "$utablename" WHERE CREATEDATE < DATEADD(second,-$maxage,getdate())
    
    Delete old tab:
    DELETE FROM "$utablename" WHERE CREATEDATE < DATEADD(second,-$maxage,getdate())
    
    Update tab:
    DECLARE vClobVal VARCHAR2(32767) := '$serializedmessage';
    BEGIN UPDATE "$utablename" SET SERIALIZEDMESSAGE=vClobVal WHERE MESSAGEID='$messageid';
    END;
    

    System database configuration in MSSQL 2008

    In case you need to store great numbers of SMS text messages it is possible that your system will be slowed down by this amount of stored files. By default, Ozeki NG SMS Gateway stores messages in files. In this way, it is highly recommended to use the System Database option in Ozeki NG SMS Gateway. This option allows you to speed up message sending. On this webpage you find a detailed configuration guide for using System Database in MSSQL 2008.

    Please note!!!

    When you switch to System Database, you can receive an error message since the system cannot find messages.

    The reason for this: the system searches for messages still in the file but system database stores them in a database. To avoid this error message please read How to import messages to System Database and How to switch from file to database sections.

    Configuration steps

    In the follows you can find detailed configuration steps on how you can configure System Database option in Ozeki NG SMS Gateway software. In this example, MSSQL 2008 is used. Please follow the steps below to make your settings effectively.

    It is assumed that you have already downloaded, installed and configured Ozeki NG SMS Gateway and MSSQL 2008.

    First of all, start SQL server Management Studio (Start menu \ All programs \ Microsoft SQL Server 2008 \ SQL Server Management Studio) (Figure 1).

    start sql server management studio
    Figure 1 - Start SQL server Management Studio

    Login as administrator (admin user has been created during the installation of MSSQL Server 2008) (Figure 2).

    login page
    Figure 2 - Login page

    Expand Databases menu. Then right click on Databases and click on New Database. In this way, you can create the database that will include the system database of Ozeki NG SMS Gateway. It is recommended to create a new database to avoid confusion (Figure 3).

    create new database
    Figure 3 - Create new database

    On New Database form specify Database name(in this example, we use ozeki_sys) and click on OK (Figure 4).

    database name
    Figure 4 - Database name

    Under Databases menu item you can see the created database (Figure 5).

    created database
    Figure 5 - Created database

    Now expand Security menu item. Then right click on Logins and select New login (Figure 6).

    new login
    Figure 6 - New login

    On the appeared form please specify the follows (Figure 7):

    1. Specify Login name: it is the user name (in this example: "ozeki")
    2. Enable SQL Server authentication checkbox and specify the Password.
    3. Disable User must change password at next login checkbox.
    4. Specify Default database (in this example: "ozeki_sys").

    specify details
    Figure 7 - Specify details

    After you have specified the details on New login form, click on User mapping still on the same form (Figure 8).

    user mapping
    Figure 8 - User mapping

    Enable the checkbox of the created database (in this example it is "ozeki_sys") and click on ... button at the end of the row (Figure 9).

    enable database
    Figure 9 - Enable the database

    On the appeared Select Schema form click on Browse to be able to select the schema you wish to use for the user (Figure 10).

    sms system database browser
    Figure 10 - SMS System database browser

    Select the schema you wish to use (in this case dbo schema is needed) and click on OK (Figure 11).

    select schema
    Figure 11 - Select the schema

    On Figure 12 you can see the selected schema is listed. Click on OK again.

    selected schema is listed
    Figure 12 - Selected schema is listed

    You also need to specify Database role membership for the created database (Figure 13). You can do so by selecting the wished items at the bottom of New login form. Please select:
    db_ddladmin
    db_owner
    Public is selected by default. Please leave it selected.

    Finally, click on OK to create the user.

    database role membership
    Figure 13 - Database role membership

    If you made settings correctly, you can see the created user under Logins menu item (Figure 14). In this example it is "ozeki".

    created user
    Figure 14 - Created user

    Now start Ozeki NG SMS Gateway and login with your username and password (Figure 15).

    log into ozeki ng sms gateway
    Figure 15 - Log into Ozeki NG SMS Gateway

    Go to Edit menu and select Server preferences menu item (Figure 16).

    server preferences
    Figure 16 - Server preferences

    Select Databases tab and click on System database settings tab (Figure 17). Here, enable Use a database server instead of file system to store messages. Database connection type needs to be OleDb.

    Then specify the Database connection string as follows:

    Provider=SQLOLEDB.1;Data Source=YourComputerName;Persist Security Info=False;Integrated Security=SSPI;User ID=YourUserName;Password=YourUserPassword;Initial Catalog=YourDatabaseName

    Please customize the Database connection string according to the follows:

    YourComputerName= the IP address or domain name of the computer on which the database server has been installed. If the Ozeki NG SMS Gateway and the database server are on the same computer, this value is (local).

    YourUserName= username for the database.

    YourUserPassword= password belongs to the username.

    YourDatabaseName= the catalog or database that you have created for storing the system database. (In this example, it is "ozeki_sys")

    Finally, click on OK.

    system database settings
    Figure 17 - System database settings

    Now restart the Ozeki NG service by right clicking on the Ozeki icon on the tray and select Restart service option (Figure 18).

    restart service
    Figure 18 - Restart service

    After restart, go to View menu and select System DB events menu item (Figure 19).

    system db events
    Figure 19 - System DB events

    If the configuration was correct then you can see the following server event: "Database connection successful" (Figure 20).

    database connection successful
    Figure 20 - Database connection successful

    If you send a test message it needs to be appeared in the Sent box in Ozeki NG SMS Gateway as Figure 21 demonstrates.

    sent test message
    Figure 21 - Sent test message

    As a consequence of the test message it can be seen that the database tables containing the messages have been created in the database successfully for the given user (Figure 22).

    database tables have been created successfully
    Figure 22 - Database tables have been created successfully

    System database configuration in MSSQL 2012/2014

    In case you need to store great numbers of SMS text messages it is possible that your system will be slowed down by this amount of stored files. By default, Ozeki NG SMS Gateway stores messages in files. In this way, it is highly recommended to use the System Database option in Ozeki NG SMS Gateway. This option allows you to speed up message sending. On this webpage you find a detailed configuration guide for using System Database in MSSQL 2012/2014.

    Please note!!!

    When you switch to System Database, you can receive an error message since the system cannot find messages.

    The reason for this: the system searches for messages still in the file but system database stores them in a database. To avoid this error message please read How to import messages to System Database and How to switch from file to database sections.

    Configuration steps

    In the follows you can find detailed configuration steps on how you can configure System Database option in Ozeki NG SMS Gateway software. In this example, MSSQL 2012/2014 is used. Please follow the steps below to make your settings effectively.

    It is assumed that you have already downloaded, installed and configured Ozeki NG SMS Gateway and MSSQL 2012/2014.

    First of all, start SQL server Management Studio (Start menu \ All programs \ Microsoft SQL Server 2012/2014 \ SQL Server Management Studio).

    Login as administrator (admin user has been created during the installation of MSSQL Server 2012/2014) (Figure 1).

    login window
    Figure 1 - Login

    Expand Databases menu. Then right click on Databases and click on New Database. In this way, you can create the database that will include the system database of Ozeki NG SMS Gateway. It is recommended to create a new database to avoid confusion (Figure 2).

    create a new database
    Figure 2 - Create new database

    On New Database form specify Database name (in this example, we use ozeki_sys) and click on OK (Figure 3).

    name the database
    Figure 3 - Database name

    Under Databases menu item you can see the created database (Figure 4).

    created database
    Figure 4 - Created database

    Now expand Security menu item. Then right click on Logins and select New login (Figure 5).

    new login
    Figure 5 - New login

    On the appeared form please specify the follows (Figure 6):

    1. Specify Login name: it is the user name (in this example: "ozeki")
    2. Enable SQL Server authentication checkbox and specify the Password.
    3. Disable User must change password at next login checkbox.
    4. Specify Default database (in this example: "ozeki_sys").

    specify details
    Figure 6 - Specify details

    After you have specified the details on New login form, click on User mapping still on the same form (Figure 7).

    user mapping
    Figure 7 - User mapping

    Enable the checkbox of the created database (in this example it is "ozeki_sys") and click on ... button at the end of the row (Figure 8).

    enable the database
    Figure 8 - Enable the database

    On the appeared Select Schema form click on Browse to be able to select the schema you wish to use for the user (Figure 9).

    browse button
    Figure 9 - Browse

    Select the schema you wish to use (in this case dbo schema is needed) and click on OK (Figure 10).

    select the schema
    Figure 10 - Select the schema

    On Figure 11 you can see the selected schema is listed. Click on OK again.

    select schema is listed
    Figure 11 - Selected schema is listed

    You also need to specify Database role membership for the created database (Figure 12). You can do so by selecting the wished items at the bottom of New login form. Please select: db_ddladmin
    db_owner
    Public is selected by default. Please leave it selected.

    Finally, click on OK to create the user.

    database role membership
    Figure 12 - Database role membership

    If you made settings correctly, you can see the created user under Logins menu item (Figure 13). In this example it is "ozeki".

    created user
    Figure 13 - Created user

    Now start Ozeki NG SMS Gateway and login with your username and password (Figure 14).

    log into ozeki ng sms gateway
    Figure 14 - Log into Ozeki NG SMS Gateway

    Go toEdit menu and select Server preferences menu item (Figure 15).

    server preferences
    Figure 15 - Server preferences

    Select Databases tab and click on System database settings tab (Figure 16). Here, enable Use a database server instead of file system to store messages. Database connection type needs to be OleDb.

    Then specify the Database connection string as follows:

    Provider=SQLOLEDB.1;Data Source=YourComputerName;Persist Security
    Info=False;Integrated Security=SSPI;User ID=YourUserName;Password=YourUserPassword;Initial
    Catalog=YourDatabaseName

    Please customize the Database connection string according to the follows:

    YourComputerName= the IP address or domain name of the computer on which the database server has been installed. If the Ozeki NG SMS Gateway and the database server are on the same computer, this value is (local).

    YourUserName= username for the database.

    YourUserPassword= password belongs to the username.

    YourDatabaseName= the catalog or database that you have created for storing the system database. (In this example, it is "ozeki_sys")

    Finally, click on OK.

    system database settings
    Figure 16 - System database settings

    Now restart the Ozeki NG service by right clicking on the Ozeki icon on the tray and select Restart service option (Figure 17).

    restart service
    Figure 17 - Restart service

    After restart, go to View menu and select System DB events menu item (Figure 18).

    system db events
    Figure 18 - System DB events

    If the configuration was correct then you can see the following server event: "Database connection successful" (Figure 19).

    database connection successful
    Figure 19 - Database connection successful

    If you send a test message it needs to be appeared in the Sent box in Ozeki NG SMS Gateway as Figure 20 demonstrates.

    sent test message
    Figure 20 - Sent test message

    As a consequence of the test message it can be seen that the database tables containing the messages have been created in the database successfully for the given user (Figure 21).

    database table created
    Figure 21 - Database tables have been created successfully

    MySQL configuration

    If you wish to use MySQL as the system database please configure the following SQL templates in the Server preferences form:

    The database connection type, you should choose is:

    Odbc
    

    The database connection string you should use is:

    Driver={MySQL ODBC 5.1 Driver};Server=127.0.0.1;Database=ozekisms;User=ozeki;Password=abc123;Option=4;
    

    Create

    CREATE TABLE IF NOT EXISTS $tablename (`messageid` VARCHAR(60) NOT NULL,
    `createdate` DATETIME NULL,`serializedmessage` TEXT NULL,PRIMARY KEY(`messageid`));
    

    Load index

    SELECT messageid FROM $tablename
    

    Load

    SELECT messageid,serializedmessage FROM $tablename WHERE messageid IN ($idlist)
    

    Save

    INSERT INTO $tablename (messageid,createdate,serializedmessage) values ('$messageid',now(),'$serializedmessage')
    

    Delete

    DELETE FROM $tablename WHERE messageid IN ($idlist)
    

    Move

    INSERT INTO $tablename (messageid,createdate,serializedmessage) SELECT messageid,
    createdate,serializedmessage FROM $sourcetable WHERE messageid IN ($idlist)
    

    Find old

    SELECT messageid FROM $tablename WHERE createdate<DATEADD(now(), INTERVAL -$maxage SECOND)
    

    Delete old

    DELETE FROM $tablename WHERE createdate<DATEADD(now(), INTERVAL -$maxage SECOND)
    

    How to import messages into system database

    To be able to speed up sending SMS text messages you can use System Database option of Ozeki NG SMS Gateway that allows storing messages in a database instead of a file. To introduce this option first you need to import your messages from file to database. This page provides you a detailed description on how to import your messages into system database with System Database Importer.

    When you switch to System Database, you can receive an error message since the system cannot find messages.

    The reason for this: the system searches for messages still in the file but system database stores them in a database. To avoid this error message please download System Database Importer.

    Import SMS text messages to system database

    For demonstration I send 200 SMS text messages from a file using Ozeki Performance Tester. Ozeki NG SMS Gateway has already been installed on the computer and I store messages in a file (Figure 1).

    send sms from file
    Figure 1 - Send 200 SMS from a file

    Ozeki NG SMS Gateway sent out the 200 messages (Figure 2).

    sent messages from a file
    Figure 2 - Sent messages from a file

    Now I switch to System Database. In Edit menu select Server Preferences. On Databases tab click on System database settings tab. Here enable Use a database server instead of file system to store message option. Specify Database connection type and Database connection string(Figure 3).

    configure system database
    Figure 3 - Configure System Database

    After the configuration stop Ozeki NG SMS Gateway by right clicking on its icon in the system tray and select Stop service option (Figure 4).

    stop service
    Figure 4 - Stop service

    Download System Database Importer if you haven't done so and start it. Click on the browse button (Figure 5).

    start the importer and browse
    Figure 5 - Start the importer and browse

    Select Ozeki NG SMS Gateway directory and click OK (Figure 6).

    select ozeki ng sms gateway directory
    Figure 6 - Select Ozeki NG SMS Gateway directory

    After the form is filled automatically, you just need to click on Import (Figure 7).

    import
    Figure 7 - Import

    Finally, if you followed the instructions you receive a notification if the Import completed successfully.

    Start Ozeki NG SMS Gateway by right clicking on its icon in the system tray and select Start service option (Figure 8).

    start service
    Figure 8 - Start service

    Finally, I sent the imported messages - in this time from the database and not from the file - and you can see that Ozeki NG SMS Gateway has sent the messages out (Figure 9).

    sent messages from database in ozeki ng sms gateway
    Figure 9 - Sent messages from database in Ozeki NG SMS Gateway

    In conclusion

    With the implementation of System Database Importer you can avoid problematic cases derive from the fact that the system searches for messages still in the file and not in the database. With this solution you can be sure that messages will be imported from the file to the database. In this way you can introduce System Database option easily and successfully into your system to speed up sending great numbers of SMS text messages.

    How to switch from File to Database

    In this brief overview you can read what you need to do if you have stored messages in a file and now you wish to switch to database.

    By default, messages of all users are stored in a file. These files are stored in the folders of users (for example, the messages of user admin are also stored in file) (Figure 1).

    Figure 1 - Messages of users are stored in file

    On Figure 2 you can see the sent messages of user admin stored in file. The file names of these messages are their GUID.

    Figure 2 - Sent messages of user admin in file

    If user admin sends out messages, sent messages will be stored in file. Then messages are forwarded to the SMSC (SMS center) that returns a delivery report about messages. These delivery reports will be matched with the messages stored in the file (Figure 3).

    Figure 3 - Sending messages with file

    However, files are easy to work with, if Ozeki NG SMS Gateway needs to process great numbers of messages the system can slow down because of the hard disc usage. Since Ozeki NG SMS Gateway stores messages in 7 Kb files, hard disc is engaged to a great extent.

    Switch to database

    This situation can be avoided by switching to database. Practically it means that messages will be stored in a database instead of files that will ensure a faster system (Figure 4).

    Figure 4 - Messages stored in database

    In case of sending messages, messages will be stored in the database and the returned delivery reports will be matched the original messages stored in the database (Figure 5).

    Figure 5 - Sending messages with database

    Now if you stored your messages in file and switch to database problems can occur deriving from the fact that there can still be messages stored in the file to which delivery reports have not been returned yet. After switching to database, delivery reports will still be returned to messages that have been stored in file. But since the storage in file option is disabled, Ozeki NG SMS Gateway will only look for original messages in the database (and not in file any more). So if there is a delivery report that is returned for a non-existing message (messages that were originally stored in file) the following error message will appear:

    ERROR 2202:

    Cannot find corresponding envelope for incoming delivery report in sent items. Missing envelope ID: msgID

    Figure 6 - Error when try to match the original message

    To solve this issue you can use Message importer that will allow you to import messages from file to database. Therefore, the system will be able to match the delivery reports with messages that have already been imported into the database.

    Download message importer

    HTTPS

    The Graphical User Interface of the Ozeki NG SMS Gateway can be accessed through HTTPS. All you need to do is to configure an HTTPS port on the server preferences form, then you should assign a HTTP Server certificate to the HTTPS port. In this article you can get a detailed description about how you can setup HTTPS in your Ozeki NG SMS Gateway.

    Ozeki NG SMS Gateway software is prepared for handling HTTPS connections. In order for this to work, a certificate is needed (generated or purchased as Thawte, GoDaddy, etc.)

    In case you are using a generated certificate, you need to install the generated certificate to Thrusted Root Certificate storage on ALL computers from which you wish to connect to Ozeki NG SMS Gateway software through HTTPS connection.

    Use the following step by step description to configure the HTTPS for your Ozeki NG SMS Gateway:

    Step 1) Download and unwrap this .zip file to a folder, for instance c:\https_ngsms

    Step 2) Start a command line with system administartor rights. Please click on Start menu, Search. Here, please type cmd. In the list that appears, please right click on cmd and choose Run as system administrator option.

    run the cmd window
    Figure 1 - Run cmd

    Step 3) Find the folder in command line where you unzipped the attached .zip file.

    find the folder of the unzipped files
    Figure 2 - Find the folder of unzipped files

    Step 4) Please run mkcert.cmd command in a way that you give your computer's IP address, where you wish to be reached through HTTPS, as parameter 1 and the password for the certificate as parameter 2 in the following way:

    mkcert ng_computer_ip_address password

    set the place you wish to be reached through https
    Figure 3 - Set where you wish to be reached through HTTPS

    Step 5) Run HttpConfig.exe as admin.

    Step 6) In the window that appears, please click on SSL tab.

    Step 7) Click on 'Add'.

    add a new ssl configuration
    Figure 4 - Add new SSL Configuration

    Step 8) In the window that appears, to IP address field, please add the computer's IP address where Ozeki NG SMS Gateway software is running. To port field, please add the port number through which HTTPS will watch.

    Step 9) Next to GUID field, please click on 'New' button.

    set an ssl configuration
    Figure 5 - SSL Configuration

    Step 10) In Certificate section, please click on 'Browse'. From the list that appears, please select the certificate that was created by ngsms-CA, then click on 'OK'.

    confirm the certificate
    >Figure 6 - Confirm Certificate

    Step 11) Click on 'OK', following this, please click on 'Apply' and then on 'OK' again.

    accept the configuration
    Figure 7 - Accept the configuration

    apply the settings
    Figure 8 - Apply the settings

    Step 12) In the folder, where you ran mkcert and HttpConfig, an ngsms.cer file was created. Please install this to Thrusted Root Certificates.

    install the created certificate
    Figure 9 - Install the created certificate

    select the thrusted root ertificate
    Figure 10 - Select Thrusted Root Certification

    Step 13) Open the user inteface of Ozeki NG SMS Gateway, in Edit menu, Server preferences menu item, on Client Connectivity tab, please check 'Listen on HTTPS port' checkbox. Following this, please add the port number where you have installed the certificate to 'HTTPS server port' field.

    select the listen on https port
    Figure 11 - Select Listen on HTTPS Port

    Step 14) Restart Ozeki NG service.

    Step 15) Type the computer's IP address and the HTTP port where Ozeki NG SMS Gateway is running to the browser in the following way: https://ng_computer_ip_address:https_port/

    Step 16) Login with username and password.

    login with yourr username and password
    Figure 12 - HTTPS URL

    After you have configured these settings you can access to your Ozeki NG SMS Gateway through HTTPS.

    If you have any question, please contact us at info@ozekisms.com.

    Ozeki firewall settings for Windows 10

    In this guide you can learn how you can allow incoming connections on 9500 and 9501 ports at Windows Firewall(Windows 10).

    Take the following steps:

    To allow incoming connections, first you need to go to Control Panel at Start menu and click on Windows Firewall icon (Figure 1).

    control panel
    Figure 1 - Control Panel

    At Windows Firewall, select "Advanced Settings" (Figure 2).

    windows firewall settings
    Figure 2 - Windows Firewall

    In the next page select "Inbound Rules"(Figure 3).

    advanced settings page
    Figure 3 - Advanced Settings page

    Now click to "New Rule..." button at right(Figure 4).

    inbound rules page
    Figure 4 - Inbound Rules page

    In the next dialog box select the "Port" radio button and then click to "Next" (Figure 5).

    select the type of the rule
    Figure 5 - Select the type of the rule

    At the next page type in the "port numbers" (9500-9501) what you want to enable and click to "Next" (Figure 6).

    type in the port numbers
    Figure 6 - Type in the port numbers

    Leave the radio button on "Allow the connection" and click to "Next" (Figure 7).

    choose the action
    Figure 7 - Choose the action

    Leave all pipes in the boxes and click "Next" (Figure 8).

    select the applying of this rule
    Figure 8 - Select the applying of this Rule

    In the last page "Name the Rule" and click the "Finish" button (Figure 9).

    name the rule
    Figure 9 - Name the Rule

    Finaly you can see your new rule in the list is the rules (Figure 10).

    list of the rules
    Figure 10 - The list of the rules

    Ozeki firewall settings for Windows 8

    In this guide you can learn how you can allow incoming connections on 9500 and 9501 ports at Windows Firewall(Windows 8).

    Take the following steps:

    To allow incoming connections, first you need to go to Control Panel at Start menu and click on Windows Firewall icon (Figure 1).

    the control panel
    Figure 1 - Control Panel

    At Windows Firewall, select "Advanced Settings" (Figure 2).

    windows firewall settings
    Figure 2 - Windows Firewall

    In the next page select "Inbound Rules"(Figure 3).

    the advanced settings tab
    Figure 3 - Advanced Settings page

    Now click to "New Rule..." button at right(Figure 4).

    the inbound rules page
    Figure 4 - Inbound Rules page

    In the next dialog box select the "Port" radio button and then click to "Next" (Figure 5).

    select the type of the rule
    Figure 5 - Select the type of the rule

    At the next page type in the "port numbers" (9500-9501) what you want to enable and click to "Next" (Figure 6).

    type in the port number
    Figure 6 - Type in the port numbers

    Leave the radio button on "Allow the connection" and click to "Next" (Figure 7).

    choose the action
    Figure 7 - Choose the action

    Leave all pipes in the boxes and click "Next" (Figure 8).

    select the applying of the rule
    Figure 8 - Select the applying of this Rule

    In the last page "Name the Rule" and click the "Finish" button (Figure 9).

    name the new rule
    Figure 9 - Name the Rule

    Finaly you can see your new rule in the list is the rules (Figure 10).

    the list of all rules
    Figure 10 - The list of the rules

    Ozeki firewall settings for Windows 7

    In this guide you can learn how you can allow incoming connections on 9500 and 9501 ports at Windows Firewall(Windows7).

    Take the following steps:

    To allow incoming connections, first you need to go to Control Panel at Start menu and click on Windows Firewall icon (Figure 1).

    control panel
    Figure 1 - Control Panel

    At Windows Firewall, select "Advanced Settings" (Figure 2).

    windows firewall
    Figure 2 - Windows Firewall

    In the next page select "Inbound Rules"(Figure 3).

    advanced setting page
    Figure 3 - Advanced Settings page

    Now click to "New Rule..." button at right(Figure 4).

    inbound rules page
    Figure 4 - Inbound Rules page

    In the next dialog box select the "Port" radio button and then click to "Next" (Figure 5).

    select the type of the rules
    Figure 5 - Select the type of the rule

    At the next page type in the "port numbers" (9500-9501) what you want to enable and click to "Next" (Figure 6).

    type in the port numbers
    Figure 6 - Type in the port numbers

    Leave the radio button on "Allow the connection" and click to "Next" (Figure 7).

    choose the action
    Figure 7 - Choose the action

    Leave all pipes in the boxes and click "Next" (Figure 8).

    select the applying of this rule
    Figure 8 - Select the applying of this Rule

    In the last page "Name the Rule" and click the "Finish" button (Figure 9).

    name the rules
    Figure 9 - Name the Rule

    Finaly you can see your new rule in the list is the rules (Figure 10).

    the list of the rules
    Figure 10 - The list of the rules

    Multitech SMS modem

    The MultiTech MultiModem Quad band EDGE modem w/USB MTCBA-E-U is an excellent choice for SMS messaging. It works well with Ozeki NG 10 and Ozeki 10. This is a high speed, professional wireless cellular modem. It operates at 230400 baud, 8N1, which is one of the highest speeds we have found in USB modems. It is very reliable. It does not require an external power supply, it powers itself over the USB port.

    What is a GSM modem?

    A GSM modem is a hardware device that can provide you connection with a service provider. It requires a SIM card to work. It is mostly used to send out automated or bulk messages.

    How sending SMS through a GSM modem works

    This SMS sending solution makes sending SMS messages from your computer possible. This solution consists of a computer with the Ozeki SMS Gateway installed, a MultiTech modem and the recipients mobile phone. The computer with the Ozeki SMS Gateway application is responsible for compiling the message. It needs an address and a text body. It will submit the SMS message for sending through the MultiTech SMS modem which will communicate with a service provider. The service provider will deliver the message to the address phone number as an SMS message.

    send sms pc to gms modem
    Figure 1 - Send SMS PC to GMS modem

    How to send SMS with a GSM modem (Clear steps)

    To send SMS with a GSM modem:

    1. Insert the SIM card into the gsm modem
    2. Plug the antenna into the modem
    3. Connect the modem to your PC with USB cable
    4. Launch the Ozeki SMS Gateway
    5. Run the sms modem autodetection
    6. Specify the sms phone number
    7. Write the text of the SMS message
    8. Click on Send to send the SMS
    9. Review the test SMS message you sent

    MultiTech MultiModem SMS setup (video tutorial)

    In this video you will learn how you can set up a MultiTech MultiModem to send text messages (SMS) using a USB cable. For this setup you need the modem itself, a SIM card, an antenna and a USB cable. First we insert the SIM card into the modem, then we connect the antenna to the modem as well. Now we can connect the modem with the USB cable to the computer. Once the modem is successfully connected to the PC, the power led will light up to indicate that it is working.

    Ozeki SMS modem configuration (video tutorial)

    This video tutorial shows you how you can install and configure an sms modem connection in Ozeki SMS Gateway. In this video we use a MultiTech MultiModem, which is automatically detected as the port by the Autodetect system. After it has been detected, we can turn the connection on and send a text message. We type in our message and phone number, then click on Send. We can see that the message was successfully sent and shows up on the mobile device.

    Drivers for Windows 10

    MultiTech SMS modem documents

    Get the parts that you need to connect the modem succesfully

    To connect the modem successfully, you need a SIM card, an antenna, a USB cable and the modem itself to set up your Multitech SMS modem to your PC. (All shown in Figure 2)
    Make sure that you have all the hardwares that you need to use the modem because every little detail is important.

    the parts you need to connect the modem succesfully
    Figure 2 - The parts you need to connect the modem succesfully

    Insert the SIM card into the modem

    The first step that you have to perform is to plug the SIM card into the modem. This procedure is similar to inserting a SIM card to a mobile phone. The SIM card makes the connection between the modem and the network.
    (Demonstrated in Figure 3)

    insert sim card into the modem
    Figure 3 - The SIM card inserted into the modem

    Connect the antenna to the modem

    After inserting the SIM card, you have to connect the modem to its antenna. Make sure that it is connected corretly in order to get best performance. The function of the antenna is to transmit and receive signal. (Shown in Figure 4)

    connect antenna to the modem
    Figure 4 - The antenna connected to the modem

    Insert the USB cable into the modem

    The next step is to insert the USB cable into the modem. This will connect the modem to your computer, so it is advised to use a perfectly working cable to avoid disconnections. (Figure 5)

    the usb cable have to be inserted
    Figure 5 - The USB cable have to be inserted

    Plug the USB cable into your computer

    Lastly, the other end of the USB cable have to be connected to your PC. Plug it into the computer (As you can see on Figure 6)

    the usb cable connected to the pc
    Figure 6 - The USB cable connected to the PC

    Check the power led

    If you have done everything right until this point the power led on the modem should be on. (Shown in Figure 7)

    check power led if the modem is turned on
    Figure 7 - The modem is turned on now

    Open Ozeki SMS Gateway

    Now your modem is ready to be configured. The first step you have to fulfill is to open Ozeki 10 SMS Gateway on your desktop. To open the program, click on the Ozeki Desktop shortcut twice. (Figure 8)

    open ozeki ten sms gateway
    Figure 8 - Open Ozeki 10 SMS Gateway

    Log in with your Ozeki 10 SMS Gateway account

    Next, log in with your Ozeki 10 SMS Gateway account by typing in your username and password. This account has to be created during the installation process. Only created accounts can be used during this process. (Shown in Figure 9)

    login with your ozeki ten sms gateway account
    Figure 9 - Login with your Ozeki 10 SMS Gateway account

    Add new connection in the SMS Gateway

    In the SMS Gateway application, the first thing that you need to do is to create a new connection. This can be done in the Connections panel where you have to click on the Add new connection... link. (As you can see on Figure 10)

    add new connection in the sms gateway
    Figure 10 - Add new connection in the SMS Gateway

    Select the SMS modem connection to install

    The next window lists you all the connections that you can create in the SMS Gateway application. Now you have to look for the Wireless connections install list and select the SMS modem install item by clicking on the Install link. This will allow you to use the modem in the Ozeki SMS Gateway. (Demonstrated in Figure 11)

    select the sms modem connection to install
    Figure 11 - Select the SMS modem connection to install

    Autodetect the port where you connected the modem

    In the installation menu, at the General tab, you can find the Serial port groupbox. In Port combobox you need to select the port where you connected the modem. For autodetection, just click on the Autodetect button. The Autodetect button will recognize your device if it is connected properly. (Figure 12)

    autodetect the port where you connected the modem
    Figure 12 - Autodetect the port where you connected the modem

    Check the informations

    This Autodetect option will detect your modem, and if it is connected right, the following window should show up with informations about your connected modem and SIM card. You can check in this window that every detail is right with the hardware and the SIM card, just to make sure that you are using the proper hardware. Click the Ok button if you finished reading. (Figure 13)

    details of the detected modem
    Figure 13 - Details of the detected modem

    Send an SMS message using the modem connection

    At this point, you have an SMS modem connection in the SMS Gateway application. To handle SMS messages with this connection, first, you need to enable the connection (Figure 14) by turning on the switch button in the connection details window. The green color shows that you enabled SMS modem connection. Important to note that you can't ignore this step because it is required to have an enabled connection to send SMS.

    turn on the sms modem connection
    Figure 14 - Turn on the SMS modem connection

    Give the recipient's address

    After you enabled the conenction, go to the Test tabpage. It has a General tab, select it and you will find the Recipient and SMS groupboxes. To send the SMS, you need to type the phone number of the recipient into the To: textbox. (Figure 15)

    type the address where you want to send the sms message
    Figure 15 - Type the address where you want to send the SMS message

    Type in the test message

    Next, just type the test message to the SMS groupbox. This message will be sent as an SMS to the previously given address. You can write whatever you want. (Shown in Figure 16)

    write the text of the sms message
    Figure 16 - The text of the SMS message

    Send the SMS

    If you are ready to send the SMS message, just click on the Send button (Figure 17).

    the sms can be sent by clicking on the send button
    Figure 17 - The SMS can be sent by clicking on the Send button

    Check the test message

    If you did everything in the right way, the message will be received by the recipient, as you can see in the test phone. This message is a simple SMS, just like the ones that you would get from other people. This shows you that you are ready to use the Ozeki SMS Gateway and the MultiTech MultiModem for your purposes. (Figure 18)

    the received sms message
    Figure 18 - The received SMS message

    Quick Data sheet

    General
    Form Factor External
    Manufacturer Multi-Tech Systems Inc.
    Interface Type USB
    Connectivity Technology wireless
    Max Transfer Rate 240 Kbps
    Fax Compatibility G3
    Cellular Protocol EDGE, GPRS, GSM
    Antenna External detachable
    Antenna Qty 1
    Package Type OEM
    Connector Type RJ-9
    Min Operating Temperature -30°C
    Max Operating Temperature +65°C
    Brand Multi-Tech
    Product-Line Multi-Tech MultiModem EDGE
    Model MTCBA-E-U
    Packaged Quantity 1
    Compatibility PC

    Summary

    As you can see in the guide, the MultiTech MultiModem works really well with Ozeki SMS Gateway. Using them together lets you to send messages from your computer, helping your company to grow bigger. You can use this to send out automated or bulk messages. After you went through the steps, got the needed hardware and software, you will be able to send SMS using your computer.

    You can download the Ozeki products from here and you can read about hardwares here.

    Now it is time to get Ozeki 10 and a MultiTech MultiModem to your company and start working with them!

    SMS Service Provider Connections

    This chapter explains service provider connectivity and provides information detailing how to configure different service provider connections for SMS messaging using the Ozeki NG - SMS Gateway software.

    In SMS messaging using Ozeki NG - SMS Gateway, a service provider is an entity that is responsible for sending and delivering SMS messages from users/applications of the program to recipient mobile phones, and responsible for sending SMS messages from mobile phones to Ozeki NG - SMS Gateway, which will deliver them to users/applications of the program.

    To be able to send and receive SMS messages using Ozeki NG - SMS Gateway, you need to pay one or more GSM service providers for the service described above, and you have to connect Ozeki NG - SMS Gateway to the SMS Center of one or more service providers.

    You can do this in two ways:

    • You can connect directly to the SMS Center of a GSM service provider over the Internet (IP SMS connection). In this case, you need to make a contract with the service provider. In compensation for your subscription, the GSM service provider will provide you with the information required for connecting to the SMS Center over the Internet (hostname, port, username, password).

    • You can connect to the SMS Center using a GSM modem attached to the PC with a phone-to-PC data cable. In this case you pay for the service by buying a SIM card from the service provider.

    Direct connection to the SMS Center by setting up an IP SMS account with one or more GSM service providers has several advantages, including a greater speed and reliability.

    For SMS messaging with a GSM modem, you need to use a suitable GSM device. For more information, check out the following guide: Recommended hardware / GSM modems

    The format of SMS messages exchanged between Ozeki NG - SMS Gateway and the SMS Center of the GSM service provider is governed by an SMS protocol. When you install a service provider connection, you have to select the appropriate protocol. The service provider will tell you which protocol to use and will give you the protocol-specific parameters, such as the username and password, IP address etc.

    Ozeki NG - SMS Gateway allows the installation and configuration of the following protocols / service provider connections:

    GSM Modem Connectivity

    Video tutorial: How to configure a GSM phone or GSM modem connection

    In this chapter you can learn how to install and configure GSM modem connectivity for SMS messaging using the Ozeki NG - SMS Gateway software.

    Introduction

    If you plan to send and receive fewer than 15 000 SMS messages per day, you can use a suitable GSM device (phone or modem) attached to your computer with a phone-to-PC data cable. For information about suitable phones, check out the Supported Phones page. The GSM device has to be equipped with a SIM card that charges (preferably) low rates for SMS messages.

    With this setup you can use a computer program such as Ozeki NG - SMS Gateway to send and receive SMS messages. In this case, the software uses the attached device to communicate with the GSM network. If a message is sent out by the gateway running on the computer, it is first sent to the attached GSM device. Then the GSM device transmits it to the SMS Center (SMSC) of the GSM service provider, using a wireless link (Figure 1).

    how gsm modem connectivity for sms messaging works
    Figure 1 - GSM modem connectivity for SMS messaging

    When a message is received, the GSM device stores the message in its memory or on the SIM card, and sends a notification to Ozeki NG - SMS Gateway. When the program receives this notification, it retrieves (reads) the message from the respective memory cell, and then deletes the message from the device to make room for the next incoming message.

    The advantage of using a cellular modem is that you do not need Internet connection for SMS messaging. Sending an SMS message using a cellphone takes about 5-6 seconds. Receiving takes about the same time. Good software, such as Ozeki NG - SMS Gateway allows you to attach more than one device to your PC and to use them simultaneously to increase capacity.

    The best option to connect a phone to the PC is to use a standard RS232 serial cable. To find out more about it, check out the RS232 Serial Cable and Industrial Modems page. USB cables, InfraRed and BlueTooth connections are not as reliable. For information about attaching the GSM device with a USB cable, visit the USB Cable page.

    Configuration of the GSM modem connectivity

    When you have installed a GSM modem driver on your computer, you can start to install and configure the GSM modem connectivity.

    You can install and configure this connection using the graphical user interface of Ozeki NG - SMS Gateway. To start the installation, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Console interface. (To find out how to open this interface, check out the QuickStart Guide.)

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu. (To find out more about the menu, visit the Menu page.)

    After you have clicked one of these, the Add service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the GSM Modem protocol, click the Install link in the respective entry in the list (Figure 2).

    starting to install the gsm modem
    Figure 2 - Starting to install the GSM Modem connection

    When you have installed the GSM Modem protocol, the Configuration panel will show up on the right of the interface. The first tab of the panel is the Device settings tab, which consists of a Connection and an Identification section (Figure 3).

    the device settings tab
    Figure 3 - The Device settings tab

    In the Modem or Port dropdown menu in the Connection section, select your GSM modem or the COM port your device is attached to.

    In the SMS center edit box, specify the phone number of the SMS center of the GSM service provider you connect to. This address is provided by your GSM service provider. Some SMSC addresses are listed in this documentation. If you do not know the service center address of your GSM service provider, you can check out Appendix C - SMS Service Center Addresses.

    In the Identification section, specify the telephone number assigned to this connection (the phone number of your GSM device) and the service provider name in the respective edit boxes.

    Note that the phone number to be specified in the Telephone number edit box is a mandatory value. If you leave the edit box blank, the sending will be unsuccessful. Please also note that telephone numbers need to be provided in international format.

    To facilitate identification and to avoid confusion, you should name the connection after the GSM service provider. E.g., if you have set up a GSM Modem connection with Vodafone, it is advisable to name it "Vodafone". Also, note that different connections should be given different names. If you have different connections from the same service provider, you can use different but similar names for them, e.g.: "Vodafone1", "Vodafone2" (or something of the like). However, some load balancing solutions require an identical name for different connections. For details, visit the Load Balancing and the Load Balancing for SMPP v3.3 page.

    After you have selected a modem or port on "Device settings" tab, you can configure MMS settings if you wish to send MMS messages. Click on MMS settings tab. Select "Service provider selection" tab to select a service provider (Figure 4). If you cannot find your mobile network operator in the list, you should specify the MMS settings manually in the "Custom settings" tab (specify "GPRS APN", "MMSC URL", and the gateway to send MMS messages). Finally, on "Network settings" tab you can specify the GPRS connection settings.

    service provider selection tab on the mms settings tab
    Figure 4 - Service provider selection tab on "MMS settings" tab


    To configure logging, click on Logging tab in Configuration panel.

    The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data.

    You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 5).

    logging options
    Figure 5 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles.

    Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 5 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    In the Port settings tab, you can modify the GSM modem initialization and specify the timeout handling commands.

    In the Submit timeout edit box you can specify the maximum waiting time for an SMS Center response confirming that your message has been successfully submitted. Successful submission means that the SMS Center has accepted the message for delivery. You can specify the waiting time by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (30 seconds), leave this edit box unchanged.

    You can choose how to consider a message you have sent if there is no response from the SMS Center after the specified length of time. Select one of the three radio buttons. Select Sent to consider a message sent even if there is no response from the SMS Center. Select Not sent to consider a message not sent if there is no response from the SMS Center.

    Then you can enable the following options: Slow down modem communication, Delay between sending messages(you can specify the exact time), Disconnect and reconnect in case of timeout (Figure 6).

    the port settings tab
    Figure 6 - The Port settings tab


    In the Message handling tab, you can make settings related to retrieving incoming messages and sending outgoing messages (Figure 7).

    the message handling tab
    Figure 7 - The Message handling tab


    In Incoming messages section you can enable two check boxes: Use this connection for receiving messages and Automatically download MMS messages.

    In the Method to use to read incoming SMS dropdown menu, you can select which method to use to read incoming messages: CMT, CMGL or CMGR.

    Use the CMT method to make the GSM device send a notification about incoming messages.

    Use the CMGL method to request the list of incoming messages.

    Use the CMGR method to read the content of memory cells one at a time.

    The latest standard is CMT.

    In Outgoing messages section you can enable or disable the following options: enable Use this connection for sending to be able to send out messages; and Request delivery report SMS if you wish to receive delivery reports via SMS about the status of your sent messages. Include Service Center (SCA) in PDU and Do not use PDU mode (leave unchecked if unsure): SMS messages can be received in two ways: by text mode and by protocol description unit (PDU) mode. If PDU mode is used, any encoding can be implemented. If you check Do not send messages to my own phone number you can prevent the program from sending SMS messages to yourself, i.e. to the phone number of your SIM card. You can also check Use GPRS if available to send messages option as it ensures much higher speed.

    After you have checked the boxes you wish to use, specify SMS command to use. You can select CMGS or CMGT. Then select ATDT or AT+CUSD options for USSD command to use.

    The Configuration panel for service provider connections contains a Connect automatically on startup checkbox (in the bottom left-hand corner). If it is checked, Ozeki NG - SMS Gateway will automatically initiate a connection with the SMS Center when the program has started. If this checkbox is not checked, the connection has to be initiated manually.

    In Charset tab you can specify the characterset handling policy. To Preferred character set you can select UCS2 or GSM7bit. SMS messages can use the GSM 7 bit character set and the UCS2 character set. The GSM 7 bit character set can be used to send Latin characters, the UCS2 character set can be used to send international (Arabic, Chinese, etc.) characters.

    In Charset set selection policy line you can select one of the following options:

    Best match: Convert to preferred character set if lossless conversion is possible. (Character substitutions are not allowed.)

    Transform: Convert to preferred character set if possible. (Character substitutions are allowed.)

    Enforce: Always use the preferred charset. (Character substitutions and character losses are allowed.) (Figure 8).

    the charset tab
    Figure 8 - Charset tab


    You can connect a service provider connection by clicking the Connect link in the panel of the service provider connection. To disconnect a service provider connection, click to the Disconnect (Figure 9).

    link to operation
    Figure 9 - Links to operations

    You can open the panel of a service provider connection by clicking the name of the service provider connection in the Service providers panel in the Management Console.

    The panel of a service provider connection consists of three sections.

    In the upper section you can find the name of the service provider connection (with the name of its protocol in brackets).

    You can see an icon showing if the service provider connection is connected. If it is not, the icon is marked with an "x".

    To the right of the icon you can find links to perform different operations.

    • Configure: to configure or modify the configuration of an installed service provider connection. Clicking this link will take you back to the Configuration panel.
    • Events: to view the logging of the latest server events related to the service provider connection. Clicking it will bring up the Events panel containing the logging of the latest server events.
    • Connect: to connect the service provider connection with the SMS Center.
    • Disconnect: to disconnect the service provider connection from the SMS Center.
    • Uninstall: to uninstall the service provider connection.

    In the middle section of the panel you can see some of the most important configuration information. The options that have been (re)activated during the configuration are marked with a tick. The options that have not been activated or those that have been deactivated during the configuration are marked with an "x".

    In the lower section of the panel of the service provider connection you can read some information about its protocol.

    Installation of a Wavecom Modem

    On this page you can learn how to attach a Wavecom modem to the computer and how to install a standard modem driver for SMS messaging using a GSM modem connection with the Ozeki NG - SMS Gateway software.

    Video tutorial: How to send SMS using a Wavecom modem attached to your computer.

    For SMS messaging using GSM modem connectivity with Ozeki NG - SMS Gateway, you need a suitable GSM device attached to your computer with a phone-to-PC data cable. You also need a modem driver installed on your Windows Operating system. (See the Prerequisites page.)

    If performance, reliability and continuous operation are important, you should use an industrial GSM modem for SMS messaging. The Wavecom Fastrack industrial GSM modem (Figure 1) is one of the most reliable devices for this purpose.

    the wavecom fastrack modem
    Figure 1 - Wavecom Fastrack

    You can attach it to the computer with an RS232 serial cable, and you can install a standard modem driver to allow communication between the computer and the modem.

    To attach the modem and to install the modem driver, follow the instructions below.

    In Figure 2 below you can clearly see that the Wavecom Fastrack modem has a data cable that can be attached to a serial port, a SIM card slot and a SIM card. A network adapter also belongs to the modem. However, it is not included in the figure because of its large size.

    wavecom gsm modem with accessories
    Figure 2 - Wavecom GSM Modem with accessories

    Attach the serial data cable and the power cable to the Wavecom, with the SIM card already inserted (Figure 3).

    attaching the data cable and power cable to the modem
    Figure 3 - Attaching the data cable and the power cable to the modem

    Attach the data cable to the computer.

    attaching the router to the computer
    Figure 4 - Attaching the data cable to the computer

    Make sure the modem works. In Figure 4 you can see the Wavecom modem attached to the computer. If you have inserted the SIM card in the modem, a red LED (light-emitting diode) is supposed to flash at the front (Figure 5).

    the wavecom flashing red led
    Figure 5 - The Wavecom with a flashing red LED

    How to enable low level logging for a GSM modem

    open gsm modem connection
    Figure 1 - Open GSM modem connection

    select logging tab in configuration
    Figure 2 - Select logging tab in configuration

    enable low level logging
    Figure 3 - Enable low level logging

    log file location
    Figure 4 - Log file location

    Using multiple modems to send SMS messages

    By attaching multiple modems to your computer, you can increase the capacity of the system and the number of telephone numbers available for sending and receiving SMS messages. In this guide we give you information on how you can connect large number of mobile phones to your computer and how to handle them in Ozeki NG SMS Gateway.

    Connecting several modems (physical connection)

    If you want to connect GSM modems to your system, you can use USB or RS232 data cables that will allow you to attach the modems to the COM ports or the USB ports of your computer. For each modem you want to attach you need a USB or RS232 port. Computers usually have only one or two RS232 (COM) ports available and four or eight USB ports. The number of USB ports however can be increased by attaching USB hubs to the system.

    So to attach several modems, you need to use USB hubs to increase the number of available USB ports in your system.

    If you use USB ports to attach your modems, you will either use USB data cables or RS232 datacables with USB to RS232 converters. In either case you need to install a driver for each USB connection in your system. The drivers will register COM ports in your system. You can use these COM ports to configure your modems in Ozeki NG SMS gateway.

    Connecting several modems (software configuration)

    Once the modems are attached physically, you need to setup a GSM modem connection in Ozeki NG for each attached modem. The SMS quick start guide gives you information on how you can configure a modem in Ozeki NG SMS Gateway. For each connection you setup select a different COM port, when you do the modem autodetection.

    Handling several modems: Routing

    If you have several modems attached to your computer you will probably want to control which applications or users will receive the incoming messages and which GSM Modems will be used when you send out messages. Ozeki NG provides inbound SMS routing and outbound SMS routing functionality to be able to control where your messages end up. The following webpages contain information on routing configuration:

    Opportunity: Load balancing

    Attaching multiple modems to your system also give you the opportunity to setup load balancing. Load balancing means that the capacity of two or more modems will be added together and it also provides fault tolerance because if any of the members of the load balancing group fails, the other modem(s) will still send out the messages. Load balancing in Ozeki NG SMS gateway can be setup very easily. All you have to do is assign the same "Service provider name" to the modems in the GSM modem configuration form (Figure 3).

    configure the name of the service provider
    Figure 1 - Configure the service provider name

    If you have assigned the same service provider name to multiple modems, you will see them under the same name in the Ozeki NG SMS Gateway's management console (Figure 4).

    load balancing configuration in the management console
    Figure 2 - Load balancing configuration in the management console

    Opportunity: Backup routing

    One more thing you can do if you have multiple GSM modems in your system is backup routing. Backup routing means that if one modem fails in your system the messages can still be sent out on another modem. Backup routing is different from load balancing in the way, that if the default modem (default route) works, the backup modem will not be used. More information about backup routing can be found at the following URL: http://www.ozekisms.com/index.php?owpn=471 (Backup routing)

    Installation of a modem driver

    When you have attached the modem to the computer, you can install the GSM modem driver on your computer's operating system.

    Professional, high quality modems allow a simple installation of the modem driver. For the Wavecom modem, for instance, a Standard 56000 modem driver can be installed. If you have a different sort of modem, the steps described below will be more complicated. Then you will have to select the driver provided by the manufacturer of the mobile phone or data cable when selecting the driver during the installation procedure.

    Select Start Menu / Settings / Control Panel / Add hardware to open the Add Hardware Wizard window (Figure 1).

    opening the add new hardware wizard
    Figure 1 - Add Hardware Wizard

    Continue to install the standard modem driver by selecting Add a new hardware device (Figure 2).

    select the add a new hardware device option
    Figure 2 - Selecting Add a new hardware device

    Select the Advanced mode (Install the hardware that I manually select from a list). See Figure 3.

    select the install the hardware that i manually select from a list option
    Figure 3 - Selecting Install the hardware that I manually select from a list (Advanced)


    Select the Modems item (Figure 4).

    select the modem options
    Figure 4 - Selecting the Modems option

    Select Don't detect my modem; I will select it from a list (Figure 5).

    prevent autodetection
    Figure 5 - Preventing autodetection


    Select the modem driver (Figure 6).

    select the modem driver
    Figure 6 - Selecting the modem driver


    Select the port for the modem to be installed (Figure 7).

    select the port
    Figure 7 - Selecting the port


    After you have selected the port for the modem, you can start to install and configure the GSM Modem protocol.

    You can find the installation and configuration instructions on theGSM Modem Connectivity page.

    One of the steps you need to take is to select the GSM modem or the COM port your device is attached to (Figure 8).

    select the port in the device settings tab
    Figure 8 - Selecting the port in the Device settings tab

    Send SMS with GSM Modem - CMS Error codes

    If you are trying to send an SMS messages with a GSM modem, the modem can return an error code in case there is a problem. The following table lists the most common error codes.

    Introduction

    The error codes listed in this table are called CMS ERROR codes. Please note that CMS errors are modem specific errors, which means, the best you can do to find out what an error code means is to check your modem's manual. Of course we know, that sometimes it is hard to find the modem manual, this is why have published this information.

    The most common errors you will face when you want to send an SMS message are discussed in the following document: Send SMS Error Reasons. If this document does not help, take a look at the following table:

    CMS ERROR 1 "Unassigned (unallocated) number" This cause indicates that the destination requested by the Mobile Station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).
    CMS ERROR 8 "Operator determined barring" This cause indicates that the MS has tried to send a mobile originating short message when the MS's network operator or service provider has forbidden such transactions.
    CMS ERROR 10 "Call barred" This cause indicates that the outgoing call barred service applies to the short message service for the called destination.
    CMS ERROR 17 "Network failure". This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP.
    CMS ERROR 21 "Short message transfer rejected" This cause indicates that the equipment sending this cause does not wish to accept this short message, although it could have accepted the short message since the equipment sending this cause is neither busy nor incompatible.
    CMS ERROR 22 "Congestion". This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.).
    CMS ERROR 27 "Destination out of service" This cause indicates that the destination indicated by the Mobile Station cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signaling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off line, etc.
    CMS ERROR 28 "Unidentified subscriber" This cause indicates that the subscriber is not registered in the PLMN (i.e. IMSI not known).
    CMS ERROR 29 "Facility rejected" This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN.
    CMS ERROR 30 "Unknown subscriber" This cause indicates that the subscriber is not registered in the HLR (i.e. IMSI or directory number is not allocated to a subscriber).
    CMS ERROR 38 "Network out of order" This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately reattempting the short message transfer is not likely to be successful.
    CMS ERROR 41 "Temporary failure" This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the Mobile Station may wish to try another short message transfer attempt almost immediately.
    CMS ERROR 42 "Congestion" This cause indicates that the short message service cannot be serviced because of high traffic.
    CMS ERROR 47 "Resources unavailable, unspecified" This cause is used to report a resource unavailable event only when no other cause applies.
    CMS ERROR 50 "Requested facility not subscribed" This cause indicates that the requested short message service could not be provided by the network because the user has not completed the necessary administrative arrangements with its supporting networks.
    CMS ERROR 69 "Requested facility not implemented" This cause indicates that the network is unable to provide the requested short message service.
    CMS ERROR 81 "Invalid short message transfer reference value" This cause indicates that the equipment sending this cause has received a message with a short message reference which is not currently in use on the MS network interface.
    CMS ERROR 95 "Invalid message, unspecified" This cause is used to report an invalid message event only when no other cause in the invalid message class applies.
    CMS ERROR 96 "Invalid mandatory information" This cause indicates that the equipment sending this cause has received a message where a mandatory information element is missing and/or has a content error (the two cases are indistinguishable).
    CMS ERROR 97 "Message type non existent or not implemented" This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.
    CMS ERROR 98 "Message not compatible with short message protocol state" This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the short message transfer state.
    CMS ERROR 99 "Information element non existent or not implemented" This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.
    CMS ERROR 111 "Protocol error, unspecified" This cause is used to report a protocol error event only when no other cause applies.
    CMS ERROR 127 "Interworking, unspecified" This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being send cannot be ascertained.
    CMS ERROR 128 Telematic interworking not supported x
    CMS ERROR 129 Short message Type 0 not supported x x
    CMS ERROR 130 Cannot replace short message x x
    CMS ERROR 143 Unspecified TP PID error x x
    CMS ERROR 144 Data coding scheme (alphabet) not supported x
    CMS ERROR 145 Message class not supported x
    CMS ERROR 159 Unspecified TP DCS error x x
    CMS ERROR 160 Command cannot be actioned x
    CMS ERROR 161 Command unsupported x
    CMS ERROR 175 Unspecified TP Command error x
    CMS ERROR 176 TPDU not supported x x
    CMS ERROR 192 SC busy x
    CMS ERROR 193 No SC subscription x
    CMS ERROR 194 SC system failure x
    CMS ERROR 195 Invalid SME address x
    CMS ERROR 196 Destination SME barred x
    CMS ERROR 197 SM Rejected Duplicate SM x
    CMS ERROR 198 TP VPF not supported X
    CMS ERROR 199 TP VP not supported X
    CMS ERROR 208 SIM SMS storage full x
    CMS ERROR 209 No SMS storage capability in SIM x
    CMS ERROR 210 Error in MS x
    CMS ERROR 211 Memory Capacity Exceeded X
    CMS ERROR 212 SIM Application Toolkit Busy x x
    CMS ERROR 255 Unspecified error cause
    128...255 Other values in this range are reserved, defined by GSM 03.40 subclause 9.2.3.22 values
    CMS ERROR 300 ME failure
    CMS ERROR 301 SMS service of ME reserved
    CMS ERROR 302 operation not allowed
    CMS ERROR 303 operation not supported
    CMS ERROR 304 invalid PDU mode parameter
    CMS ERROR 305 invalid text mode parameter
    CMS ERROR 310 SIM not inserted
    CMS ERROR 311 SIM PIN required
    CMS ERROR 312 PH SIM PIN required
    CMS ERROR 313 SIM failure
    CMS ERROR 314 SIM busy
    CMS ERROR 315 SIM wrong
    CMS ERROR 316 SIM PUK required
    CMS ERROR 317 SIM PIN2 required
    CMS ERROR 318 SIM PUK2 required
    CMS ERROR 320 memory failure
    CMS ERROR 321 invalid memory index
    CMS ERROR 330 SMSC address unknown
    CMS ERROR 331 no network service
    CMS ERROR 332 network timeout
    CMS ERROR 340 no +CNMA acknowledgment expected
    CMS ERROR 500 unknown error
    256...511 Other values in this range are reserved
    512... manufacturer specific

    CMS Error 500

    In some cases you may receive a CMS Error 500 error message from your modem. This error message indicates, that for some reason the modem was not able to deliver the message. This error can happen if:

    • The phone number you try to send your message to is invalid
    • There is no network coverage
    • You don't have enough money on a prepaid subscription
    • The short message service center of the GSM network operator is temporarily out of service
    • The GSM cell is overloaded

    If none of these issues have caused this problem, there is not much you can do to work around this. The following things might help:

    1. Please make sure you use the latest version of Ozeki NG SMS Gateway. The latest version can be downloaded from the following website: http://www.ozekisms.com/index.php?owpn=112&viewunofficial=on
    2. Enable "slow modem communication" on the "port settings" tab of the "GSM modem configuration" form.
    3. Change the "HW flow" and "SW flow" settings to "None" on the "port settings" tab of the "GSM modem configuration" form.

    If the problem happens occasionally, you can configure multiple retries for message delivery on the "Advanced" tab of the "Edit/server preferences" form by setting the value of the "Max number of tries" field to 6.

    Send SMS using a GSM modem - Connection problems

    Download Hyper Terminal

    In this page I give some information about what to do if your modem is not recognized by the software.

    In some situations Ozeki NG SMS Gateway will not detect your GSM phone. In this case you can test whether you phone responds using Hyper Terminal. Hyper Terminal is built into windows. It is a good tool to test modem connectivity.

    To start hyperterminal, select Start->All programs->Accessories->Communications->HyperTerminal. When Hyperterminal starts, you must provide a name for the connection. Type any name you like to get to the "Connect To" form (Figure 1).

    hyper terminal
    Figure 1 - Hyper Terminal, connect to form

    In the "Connect To" configuration form you can select the COM port your device is attached to. If you use a USB cable, a PCMCIA modem, a BlueTooth connection or an Infrared port, you need to install a driver supplied by the manufacturer of the device. The driver will register a virtual serial port. In hyper terminal select the virtual port created by the driver of your device.

    When the port is selected click Ok, to get to the Port configuration form. On this form specify the port settings. The most common port speeds for GSM phones and modems are 9600, 19200, 57600 and 115200. The Data bits should be set to 8. The Parity to none the Stop bits to 1 and the flow control should be hardware.

    After all configurations are made the terminal window will open. You can use this window to test the communication. The communication can be tested by typing AT into the terminal window. If your GSM phone or modem is working the AT will appear and an OK response will be returned. If your GSM phone or modem is not working then you will not see the AT command after typing it in (Figure 2).

    at command and ok response
    Figure 2 - AT command and OK response

    If the test is successful, which means you have seen the OK response from your GSM phone or modem please close HyperTerminal and the "Autodetect" option in Ozeki NG will work.

    If the test is not successful, one of the following problems need to be resolved:

    • Some other software uses your device. Sometime 3rd party phone manager applications, or SMS solutions block the device. Try to shut down or remove these applications from your system.
    • Your device is not a GSM modem. Please check the manual of your device, to see if it has a built in modem and can be operated with AT commands. Ozeki NG uses AT commands to control your device.
    • The driver supplied with your device is not working. Try to find another driver.

    Installing USB modems

    You can install USB modems to send SMS messages into your system. The advantage to using USB modems is that you can install many modems because you are not limited by the number of physical serial (COM) ports in the system. The disadvantage is that USB modems require you to install a driver that registers a serial port in the system. This driver can be corrupt and can cause problems. This guide gives you instructions on how to use USB modems.

    Introduction

    When you install the driver for an USB modem or an USB to RS232 data cable, a new serial port is registered in the system. This serial port should be configured in Ozeki NG SMS gateway when you setup the GSM Modem service provider connection. To find out what is the port name that belongs to the newly installed modem, you should check the available ports in your system prior to the installation of the USB modem or USB data cable driver.

    Check available ports prior to USB driver installation

    To check the available ports, please open the "Windows control panel", click on "System", then select the "Hardware tab" in the System properties windows. Then click on the "Device Manager". In the Device manager, please open the ports section to see a list of serial ports prior to the USB modem installation (Figure 1).

    determine available ports before installation
    Figure 1 - Determine available ports before installation

    Install USB driver

    The next step is to install the USB modem or USB data cable driver. Then you should plugin your USB modem or phone to your computer (Figure 2).

    install the usb driver
    Figure 2 - Install USB driver

    Check available ports after USB driver installation

    After you have installed your USB modem or USB data cable driver your system properties windows will show a new serial port in your system (Figure 3).

    usb serial port
    Figure 3 - USB serial port

    Configure this serial port in the system.

    Manual installation of USB modem driver

    In some cases it is possible that you cannot install the exe file of the Sierra Wireless Fasttrack Xtend Modem driver. In this case can install the driver files manually. In this chapter you can get information on how to install the driver of the Sierra Wireless Fasttrack Xtend Modem manually.

    Download driver for manual installation

    At first, download the driver files (SierraModemDriver.zip) for the Sierra Wireless Fasttrack Xtend Modem, and extract it to C:\SierraModemDriver directory.

    open device manager
    Figure 1 - Open device manager

    Now connect the GSM modem to your computer through an USB cable. If you have connected the modem and your computer to each other, find the Device manager of your Windows operating system and open it.

    open device manager
    Figure 2 - Open device manager

    Here, find the modem that you would like to use with your Ozeki NG SMS Gateway. Right click on the name of the modem and select Update Driver Software...

    update the driver software
    Figure 3 - Update Driver Software

    On the next window, select Browse my computer for driver software button to locate and install driver software manually.

    browse my computer for driver software
    Figure 4 - Browse my computer for driver software

    Then click on the Browse button and find the driver folder, or provide the path of the driver into the textbox and click on Next button.

    provide the path of the driver
    Figure 5 - Provide the path of the drive

    At the end of the installation, you can find the port number of the modem next to the name of the modem.

    port number of the modem
    Figure 6 - Port number of the modem

    If the modem driver installed successfully, return to your Ozeki NG SMS Gateway, install a new GSM modem Service Provider connection, and click on Configure button. Here select the port of your modem and click on Autodetect.

    autodetect modem
    Figure 7 - Autodetect modem

    MMS Download over GPRS

    The reception of an MMS message has two parts. First an SMS arrives to the modem, that contains the URL of the MMS message. The second phase is the MMS download. In the second phase the modem opens a GPRS connection and it downloads the MMS message from the MMSC. In this guide we give you information on how you can use two modems to speed up the process.

    If you want to receive MMS messages it is a good idea to use two modems. One modem should be connected to Ozeki NG SMS gateway and would be used for receiving SMS messages. The second modem should be connected to the GPRS network and would be used for receiving MMS messages.

    With this configuration you can speed up MMS reception, because the second modem, will always stay connected to the GPRS network and will download your MMS messages as soon as the MMS indication SMS message arrives to the first modem. This way you save the time it takes to setup a GPRS connection for MMS download.

    The quick start guide explains how you can configure Ozeki NG SMS Gateway to receive SMS messages. In the next section I explain how you can configure the second modem, that will always stay connected to the GPRS network.

    To configure your GPRS modem first you have to specify the GPRS access point for MMS download in the modem configuration in Windows. This can be done in the Windows Control Panel as shown in Figure 1 and Figure 2.

    open the modem preferences form
    Figure 1 - Open the modem preferences form

    configure the grps apn
    Figure 2 - Configure the GPRS apn


    The GPRS APN can be configure using the AT+CGDCONT=1,IP,"apnname" modem initialization commands.

    The next step is to setup a windows dialup connection using this modem. In the dialup connection you should use the GPRS activation number as the dial string. This is usually "*99***1#" (Figure 3).

    the grps dial string
    Figure 3 - GRPS dial string

    Once your dialup connection is specified, you should dial it. This will connect you to the GPRS network and will assign an IP address to your connection.

    The final step is to configure the IP routing table to make sure the MMS download traffic goes through the GPRS connection. You can use a windows command shell (cmd.exe) to perform this configuration as described in Figure 4.

    windows routing configuration
    Figure 4 - Windows routing configuration

    After this is done you can configure Ozeki NG SMS Gateway not to use this modem. If you do not want the SMS gateway use this modem then you can check the Do not use this modem for MMS transfers option in Network Settings section of MMS settings tab. By default the SMS gateway uses the existing Internet connection for MMS transfers instead of a new one (Figure 5).

    configure ozeki ng sms gateway
    Figure 5 - Configure Ozeki NG SMS Gateway

    Installation of a Sierra Fastrack modem

    On this page you will be given a step by step installation guide on how to attach a Sierra Fastrack modem to the computer and how to install a standard modem driver for message sending through a GSM modem connection with the Ozeki NG - SMS Gateway software.

    Download Sierra Fastrack Xtend User Guide

    In order to send messages through GSM modem connectivity using Ozeki NG - SMS Gateway, you need to attach a suitable GSM device to your computer with a phone to PC data cable and you also need to install a modem driver on your Windows operating system. (See the Prerequisites page.)

    Download driver for manual installation (if you download and extract this zip file, you will be able to install driver software manually through the device manager of your Windows operating system).

    It is recommended to use an industrial GSM modem for message sending, since industrial modems are reliable and have high performance. Such a modem is Sierra Fastrack modem (Figure 1).

    Sierra Fastrack modem is recommended because it is a new, reliable, industrial GSM modem which is compatible with the main industrial standards. Among an RS232 port, it also has a built-in Micro-USB port, making it easier to connect the device to computers. How? Enabling you to connect the computer to the modem with a native USB support.

    To attach the modem and install the modem driver, please follow the steps below.

    the sierra fastrack modem
    Figure 1 - Sierra Fastrack modem

    Step 1: Connect the cables

    As a first step, insert the SIM card to the modem, attach the USB cable (Figure 2) and the power cable (Figure 3) to the modem.

    attach the usb cable to the modem
    Figure 2 - USB cable attached to the modem

    power cable and usb attached to the modem
    Figure 3 - Power cable and USB cable attached to the modem

    Step 2: Install the drivers

    Download USB Driver Installer (Figure 4) and install it to the computer.

    the usb driver installer
    Figure 4 - USB Driver Installer

    Click on 'Next' to start the installation of the USB Driver Installer (Figure 5).

    start the installation
    Figure 5 - Start the installation

    In the following window, select the USB driver below 'Items to be installed' section and accept the license agreement. Click on 'Install' to finish the installation process (Figure 6).

    finishing the installation process
    Figure 6 - Finishing the installation process

    Step 3: Configure the modem in Ozeki NG - SMS Gateway

    Now open Ozeki NG - SMS Gateway, install GSM modem Service Provider connection, and click on 'Configure'. Here select the port your modem is attached to and click on 'Autodetect' (Figure 7).

    configure the modem settings in the ozeki ng sms gateway
    Figure 7 - Configuring the modem in Ozeki NG - SMS Gateway

    Now your installation process is complete. With this connection, you will get a flexible and reliable system with high performance. For more information, read the related pages below.

    How to change frequency in Sierra GSM modems

    Download Hyper Terminal

    This guide will help you change the frequency when you use a Sierra Fastrack GSM modem. It is useful if your service provider use another frequency than 900/1800 MHz. In this guide you can see how to change the frequency from 900/1800 MHz to 850/1900 MHz. However, other options are also listed in the tables below.

    If you use GSM modem for connecting to the mobile network, it can occur that your service provider uses other frequency than the default frequency in the Sierra modem. This default frequency in Sierra Fastrack Xtend GSM modems is 900/1800 MHz.

    So before you start to use the GSM modem it is highly recommended to ask your service provider about the used frequency. If they use other frequency than the default 900/1800 MHz, you need to set the GSM modem to the used frequency.

    Sierra Fastrack Xtend modems supports the following frequencies: 850, 900, 1800, 1900. You can set the frequency by using AT commands in the modem.

    Please follow this guide to change the frequency range of your Sierra Fastrack modem effectively.

    It is assumed that Ozeki NG SMS Gateway and a Sierra Fastrack Xtend modem has already been installed to your PC.

    First, please stop the Ozeki NG SMS Gateway service by clicking on Stop service (Figure 1).

    stop the ozeki service
    Figure 1 - Stop Ozeki service

    On Figure 2 you can see the message if the Ozeki NG SMS Gateway software has stopped.

    ozeki ng sms gateway service is stopped
    Figure 2 - Ozeki NG SMS Gateway stopped

    Now start Hyperterminal at Start / Accessories / Communications / Hyperterminal (Figure 3). Please note that if you use Windows Vista or newer operating system, you need to download Hyperterminal. You can download Hperterminal from the following website: http://www.hilgraeve.com/htpe/download.html

    start the hyperterminal program
    Figure 3 - Start Hyperterminal

    Create a new connection and provide a name for this connection (Figure 4). Click on OK

    providing a new connection name
    Figure 4 - New connection name

    Select the port that is used by the GSM modem at Connect using drop down menu (Figure 5).

    select the port
    Figure 5 - Select the port

    Select the speed at Bits per second drop down menu. Set it to 115200 (Figure 6). Click on OK.

    set the speed
    Figure 6 - Set the speed

    Check if the connection is successful by typing at command into Hyperterminal. If it returns OK, the connection is successful (Figure 7).

    connection is successful
    Figure 7 - Connection is successful

    Now issue at+wmbs? command to check the frequency. The return values of this command can be the follows:

    Return values for at+wmbs? command:

    Return value Description
    +WMBS: 0,x Mono band mode 850 MHz is selected
    +WMBS: 1,x Mono band mode extended 900 MHz is selected
    +WMBS: 2,x Mono band mode 1800 MHz is selected
    +WMBS: 3,x Mono band mode 1900 MHz is selected
    +WMBS: 4,x Dual band mode 850/1900 MHz is selected
    +WMBS: 5,x Dual band mode extended 900/1800 MHz is selected
    +WMBS: 6,x Dual band mode extended 900/1900 MHz is selected

    As you can see at Figure 8 the GSM modem returns +WMBS: 5,0 meaning that it uses 900/1800mhz by default.

    check the required frequency
    Figure 8 - Check the frequency

    If you issue at+wmbs=4,1 the frequency will be change to 850/1900mhz. If OK is returned the change has been successful (Figure 9).

    Possible Commands:

    CommandDescription
    AT+WMBS=0,x Select mono band mode 850 MHz
    AT+WMBS=1,x Select mono band mode extend 900 MHz
    AT+WMBS=2,x Select mono band mode 1800 MHz
    AT+WMBS=3,x Select mono band mode 1900 MHz
    AT+WMBS=4,x Select dual band mode 850/1900 MHz
    AT+WMBS=5,x Select dual band mode extend 900/1800 MHz
    AT+WMBS=6,x Select dual band mode extend 900/1900 MHz

    Remark:

    • x=0 : The Plug & Play will have to be reset to start on specified band(s).
    • x=1 : The change is effective immediately. This mode is forbidden while in communication and during Plug & Play initialization.

    change the frequency
    Figure 9 - Change frequency

    You can also check of the change has been successful by at+wmbs? command. If the return value is +WMBS: 4,0 then the the frequency has been set to 850/1900 MHz successfully (Figure 10).

    check the chnaged frequency
    Figure 10 - Check the changed frequency

    You can also check the changed frequency by at+cgmm command. In this case the frequency will be shown in text: MULTIBAND G850 1900 (Figure 11).

    frequency in text
    Figure 11 - Frequency in text

    Now start the Ozeki service by clicking on Start service (Figure 12).

    start the service
    Figure 12 - Start service

    Click on Manage/Configure option to configure Ozeki NG SMS Gateway (Figure 13).

    manage/configure options
    Figure 13 - Manage/Configure option

    Log into Ozeki NG SMS Gateway with your username and password (Figure 14).

    log into the ozeki ng sms gateway
    Figure 14 - Log into Ozeki NG SMS Gateway

    If you have not installed a GSM modem connection in Ozeki NG SMS Gateway, then click on Add service provider. In list select GSM/GPRS modem connection and click on Install next to it (Figure 15).

    install a gsm modem connection
    Figure 15 - Install a GSM modem connection

    On the configuration panel of GSM modem connection select the port at Port drop down menu and click on Autodetect (Figure 16).

    select the port and click the autodetect button
    Figure 16 - Select the port and click Autodetect

    On Figure 17 you can see that the GSM modem has been detected successfully. Click on Click here to open the configuration form link.

    gsm modem is detected
    Figure 17 - GSM modem is detected successfully

    On the configuration panel of the GSM modem click on OK to save the changes (Figure 18).

    save the changes you made
    Figure 18 - Save the changes

    If you have followed this guide, you can check in Events menu of the GSM modem connection that 'The GSM modem is registered to the network' and the 'connection is online' (Figure 19).

    gsm modem is now registered to the network
    Figure 19 - GSM modem is registered to the network

    How to transfer calls from SIM card to another phone number using a Sierra Fastrack GSM modem

    Please follow the guide below to be able to transfer incoming calls from a given SIM card to another telephone number when you use Sierra Wireless Fastrack Xtend GSM modem.

    Why to transfer calls

    Transferring refers to redirecting incoming calls from the SIM card to an other phone number.

    Transferring of incoming calls can be useful when there is an incoming call to the GSM modem while SMS messages are also being sent. In these cases the message sending process can be interrupted by the phone call or the message sending is slow down.

    You can avoid these cases by transferring these incoming phone calls to an other telephone number. In this way, calls arriving to the given SIM card will be forwarded to the other phone number.

    For transferring calls from the GSM modem you will need Hyperterminal. Please note that Hyperterminal is included in Windows XP or older operating systems but if you use newer operating system than Windows XP you need to download Hyperterminal.

    You can download Hyperterminal from the following webpage: http://www.hilgraeve.com/htpe/download.html

    Configuration guide

    It is assumed that Hyperterminal has already been downloaded and installed on your PC.

    First of all, start Hyperterminal (Figure 1).

    start the hyperterminal
    Figure 1 - Start Hyperterminal

    Create a new connection in Hyperterminal and provide a name for the new connection and click OK (Figure 2).

    provide a name for the new connection
    Figure 2 - Provide name for the new connection

    Select the port to which the GSM modem is connected in Connect using field. Then click on Configure button to configure the the port (Figure 3).

    configure the port
    Figure 3 - Configure the port

    Set Bits per second field to 115200 and click on OK (Figure 4).

    set the bits per second value
    Figure 4 - Set Bits per second

    In the next window just click on OK (Figure 5).

    just click the ok button
    Figure 5 - Just click OK

    You can test the connection by using an AT command. If OK is returned then the connection is successful and communication with the modem is possible (Figure 6).

    test the connection
    Figure 6 - Test the connection

    Now you can issue the call-forwarding command: AT+CCFC=0,3,"telephone number" For example: AT+CCFC=0,3,"+36301234567".

    Please note that in this command you always need to give the telephone number in international format (with + sign) and between quotation marks ("")

    You can issue this command as follows:
    AT+CCFC=<reason>,<mode>[,<number>] 
    <reason>   
    0: Unconditional
    1: Mobile busy    
    2: No reply        
    3: Not reachable    
    4: All call forwarding 
    5: All conditional call forwarding   
    <mode>   
    0: Disable      
    1: Enable        
    2: Interrogate     
    3: Registration     
    4: Erasure           
    <number>
    

    After issuing this command phone calls arriving for this SIM card will be forwarded to the specified phone number (in this example, to +36301234567 telephone number) (Figure 7).

    call forwarding command
    Figure 7 - Call forwarding command

    If you do not need call forwarding anymore (for example you wish to use the given SIM card in mobile phone and not in the modem) you need to issue the following command to disable call forwarding: AT+CCFC=0,4 (Figure 8).

    command to disable the call forwarding feature
    Figure 8 - Command to disable call forwarding

    Conclusion

    If you follow the steps of this guide you will be able to avoid inconvenient cases when SMS sending process is slow down or interrupted because of an incoming call. In case the call forward is not required anymore you can easily disable it.

    Connecting to modems using COM ports via Ethernet

    It is possible to share devices using serial ports via ethernet by using a rather simple software called Serial to Ethernet Connector. This solution is good when you have a single computer with a device attached to it using a serial port, and you want to share this device to other computers (or virtual machines) via an ethernet network. With this solution, you can share a GSM modem to other computers in a network so they can control it as if they have the modem connected directly to them.

    You can download Serial to Ethernet Connector here: Serial to Ethernet Connector. There are other many other softwares for this case, but this guide will demonstrate the solution using the above software.

    Also, we will use a Sierra Fastrack modem. Installation guide for this type of modem is available here: Installation of a Sierra Fastrack modem.

    Using other softwares/modems are very similar.

    Understanding the concept

    Say, you have a device (or devices) connected to one of your computers. You want to share this device over network, so other computers (e.g. virtual machines) can control the device attached to your computer as well. This way, you can turn the computer with the attached serial device into a server, sharing the COM port used by the device over network. Client computers (e.g. virtual machines) can connect to the server machine and use the device as if it was attached directly to those computers. In this case, we want to set up a connection, so the server machine will have the GSM modem connected and the clients will use that modem to send SMS messages from Ozeki NG SMS Gateway running on them.

    Installing and configuring Serial over Ethernet Connector

    First, you need to install Serial to Ethernet Connector on the machine you will use as the server - this machine has the serial device attached. After the installation, launch the program, and create a server connection.

    You have to give the connection a name - this can be anything. In the connection type radio buttons, you must select Share serial port for incoming connections (Server). Under that section, select the serial port which has the device connected to - we have the Sierra Fastrack modem on COM4. Leave the Create as virtual serial port checkbox unchecked. Next, specify the TCP port which you want to use for recieving data (Figure 1).

    sharing a serial port
    Figure 1 - Sharing a serial port

    Note, that we are in Advanced mode - you can enable advanced mode by clicking the button on the top right corner. This is a must, because you have to specify some connection preferences in order to use the device correctly. Click on the Connection prefs menu, and specify port settings appropriate for your modem. Note, that we have all the checkboxes unticked (Figure 2). Click on Create connection on the top to create this connection.

    advanced settings
    Figure 2 - Advanced settings

    After creating the connection, you can see it running on the left side of the window (Figure 3).

    running server connection
    Figure 3 - Running server connection

    The next step is to install and launch Serial to Ethernet Connector on the client machine(s). These machines will include an Ozeki NG SMS Gateway running, too. After launching Serial to Ethernet Connector, create a Client connection.

    You also need to specify a name for it, and after that, click on the Connect serial port to remote host (Client) radio button. Under that section, select a serial port you will use for the connection - this will be a virtual serial port, so check the Create as virtual serial port checkbox. In this case, we will use COM1. Under that, specify your server's IP/Host name, and the TCP port used for the connection (5000 now). Please note, that you may have to configure your machines' firewalls properly to have Serial over Ethernet Connector working. Click on Add (Figure 4).

    creating a client connection
    Figure 4 - Creating a client connection


    You also need to enable Advanced mode by clicking the button on the top right corner. Move on to the Connection prefs menu, and make sure, you have all the checkboxes unticked. Click on the Create connection button on the top. Now you have a working connection between your server and a client (Figure 5 and Figure 6).

    the advanced client settings
    Figure 5 - Advanced client settings

    running the client connection connected to server
    Figure 6 - Running client connection connected to server

    Testing the shared device

    You have a working connection between your client and your server now. Your server has a GSM modem attached, and your client has Ozeki NG SMS Gateway installed. You can send an SMS from your client machine using the GMS modem attached to your server machine.

    Enter Ozeki NG SMS Gateway on the client, and add a new service provider connection. Install a GSM/GPRS Modem Connection. In the configuration menu of this service provider, select the virtual port used by your client machine (configured in Serial over Ethernet Connector running on the client machine). We are using COM1. Click on the Autodetect button (Figure 7).

    autodetecting the modem
    Figure 7 - Autodetecting modem

    If you configured everything properly, Ozeki NG SMS Gateway will recognize your modem as if it was attached to your client machine directly (Figure 8).

    the modem is detected
    Figure 8 - Modem detected

    You can begin sending SMS messages using the device connected to this client machine (Figure 9 and 10).

    composing the message
    Figure 9 - Composing the message

    message is routed to the gsmodem2
    Figure 10 - Message routed to 'GSMModem2

    In the GSM modem's log, you can check the message sent (example below).

    2/9/2012 7:41:55 AM - INFO 3322: Sending message (try 1/1) admin;SMS:TEXT;
    	92722ab9-e00d-4898-90d7-384a63879d44;admin; +36706000418;This is a test message!;
    	using service provider connection 'GSMModem2 (GSMModem2)'
    2/9/2012 7:41:55 AM - INFO 3201: Message will be sent using 1 PDU(s).
    2/9/2012 7:42:01 AM - INFO 3323: PDU (1/1) accepted by SMSC with message reference: 000418:197
    2/9/2012 7:42:01 AM - INFO 3327: Message successfully sent. Reference: 000418:197
    

    For more information please contact us at info@ozekisms.com.

    Send MMS over Sierra Fastrack Wireless modem

    This text gives information about how to configure custom Multi Media Message (MMS) settings in Ozeki NG SMS Gateway to be able to send and receive MMS messages. If you follow the steps of this guide you will find information on how you can set GSM modem with Ozeki NG SMS Gateway and how you can set MMS sending and receiving with Ozeki NG. Before that please read our guide on how to set up the GSM Modem connection. After the physical connection has been set, you can start the installation and setting up the connection to send MMS messages.

    how mms connection works

    Introduction

    In this topic you will read about Sierra Wireless Fastrack Modem. You can find more information on what hardware products are necessary to connect this GSM Modem with Ozeki NG SMS Gateway. If you follow the guide you will get to know how you can connect a GSM modem with you personal computer and install the USB driver of the GSM modem. If you check the first figure below the text you will see, that you need a GSM modem, a SIM card and an antenna. (Figure 1) The default package of the GSM modem includes a power supply and a USB cable, you will need them too. Please check the following steps to be able to connect your GSM modem to your computer.

    hardware requirements
    Figure 1 - Hardware requirements

    1.) Put the SIM card

    First you need to put your SIM card into your GSM modem as you see at Figure 2. You need to press and secure with the black close. Please check whether the SIM card has been inserted properly and whether it has been secured with the black lock. If you inserted your SIM card you need to connect your GSM modem with a power supply.

    put in the sim card
    Figure 2 - Put SIM card

    2.) Connecting the power supply and the radio antenna.

    The radio antenna is also included in the GSM modem package. You can easly connect the radio antenna to your GSM modem. Please check whether the antenna is connected properly. (Figure 3)

    connect the power supply and the radio antenna
    Figure 3 - Connecting power supply and radio antenna

    The final part of the hardware configuration is the connection of your GSM modem to your computer. Follow the next steps for seting up the GSM modem connection with your computer.

    3.) Connecting your modem to your personal computer on USB port

    You have already connected the cables, the antenna and the SIM card to your modem, now you need to connect the USB cable to the GSM modem. The micro USB is located under the power supply connector of the GSM modem. You need to connect the USB cable into your modem. (Figure 4)

    connect the modem to your computer
    Figure 4 - Connecting the Modem to your Computer

    After you connected the USB cable you should configure and install the driver of the GSM modem to use this USB modem. The following steps will help you in the installation of the driver and after that you will find detailed information on how to connect your GSM modem with the Ozeki NG SMS Gateway. Please read the following steps.

    4.) Installing the USB driver on your operating system

    First you should download the following driver. If you have downloaded the driver please open and run the driver to install and configure the modem. The opening window will pop up when you start the installation. (Figure 5)

    running the installation packet
    Figure 5 - Running the installation packet

    After the opening window, please click on the "Next" button to start the installation of the USB Driver. (Figure 6)

    start the installation process
    Figure 6 - Start the Installation

    After you pressed the Next button the installation will start. During the installation let the driver set and install the following packages. (Figure 7)

    finish the installation process
    Figure 7 - Finishing the installation process

    At the bottom of the next window please enable the USB driver "Items to be installed" checkbox and accept the license agreement. Click on the "Install" to finish the installation process.

    Configuration in Ozeki NG SMS Gateway

    After you installed your GSM modem you need to set the connection with the Ozeki NG SMS Gateway. In this topic you will find information on how to configure your GSM modem. Your GSM modem will be able to send and receive MMS messages using one of the following providers, please click on the "Add new service provider connection". You should set the GSM modem connection after you installed your GSM Modem. If you have a Sierra Wireless modem you can find an installation guide on this at the following webpage.

    You can find this button below the Service provider connection title at the Management Console of the Ozeki NG SMS Gateway software. (Figure 8)

    adding the service provider connection
    Figure 8 - Adding the service provider connection


    At the list of service providers you can you can find the GSM modem service provider connection. If you click on the "Install" button you can add this connection.(Figure 9)

    adding the gsm modem service provider
    Figure 9 - Adding the GSM modem service provider connection


    After that you should check which port belongs to your GSM modem. If you use serial connection please select the port or you can check which port was assigned to the modem. Please visit the following page if you wish to check which port belongs to your modem. You need to select which port was assigned to your GSM modem. (Figure 10)

    selecting the port number
    Figure 10 - Selecting port number

    If you have already selected the port number, you should detect the connection with the "Autodetect" function to set up the connection with the GSM modem. (Figure 11)

    autodetecting the gsm modem
    Figure 11 - Autodetecting the GSM modem

    If the connection was successful you can see it at the "Detemining port connectitvity". As you seen at Figure 12 the opening of the port was successful and the GSM modem was successfully connected to the Ozeki NG SMS Gateway software product.

    detecting the gsm modem
    Figure 12 - Detecting GSM modem

    You can check the solution of the process if you click on the "Events" below the Configure button of the GSM service provider connection. As you seen the connection was successful and you cannot see the cross on the GSM icon. This means that the connection was established. (Figure 13)

    connection is succesful
    Figure 13 - Connection successful

    After the installation you need to configure the MMS settings, for MMS sending and receiving. Please click on the "Configure" link at the service provider connection. (Figure 14)

    configure the mms settings
    Figure 14- Configuring MMS settings

    Please click on the MMS settings tab and Select your MMS service provider. Please look up your own service provider to establish the connection. You can find it in the premade list. After you select the service provider you will see the next screen in your configuration. (Figure 15)

    setting up the mms service provider
    Figure 15 - Setting MMS Service provider

    If your service provider allows "Disable address hiding" please click on it. Please note that custom settings are required if your service provider is not listed in the MMS Service provider combo box of the GSM Modem configuration form. If you cannot find your service provider on the list please select the Custom settings in the dropdown list. (Figure 16)

    custom settings
    Figure 16 - Custom settings


    You need to provide the configuration parameters of your MMS service provider. You can find more "Custom settings" of the MMS service provider on the following website. At Custom settings tab you have to add GPRS APN, MMSC URL, Gateway settings. If you use custom settings please set up Disable address hiding. (Figure 17)

    disable address hiding
    Figure 17 - Disable address hiding

    If your service provider require username and password for the connection please click on the "Network settings" tab. Please ensure and check with your service provider that you provided the proper username and password fir sending and receiving MMS messages. (Figure 18)

    the network tab
    Figure 18 - Network tab


    After following the steps you have already configured the password and username of the connection. This password and username were also provided by your service provider. (Figure 19)

    setting the username and password
    Figure 19 - Setting Username and Password


    You have already configured the connection for MMS sending and receiving the final part of this guide will help you in adding inbound and outbound routing rule and sending a simple MMS message.

    Inbound routing for message receiving

    In this part of the guide you will find information on how can you set up routing rules to send and receive MMS messages. At the management console you can add the inbound and outbound routing rules. Please click on the add button and after that you should set up the inbound routing rules.(Figure 20)

    setting up and inbound routing rule
    Figure 20 - Inbound routing rule set up


    As you seen on Figure 20 you need to configure the routing from your GSM modem to your admin user. It can be another user, too. This user can be a standard user or a database user.

    If you want to send MMS messages, too, outbound routing configuration is also necessary. You can also add a routing rule if you click on Managment console outbound routing "Add" button. After that you need to add a filtering rule from admin or from another user to the GSM modem service provider. (Figure 21)

    outbound routing rule set up
    Figure 21 - Outbound routing rule set up

    After you set the outbound routing rule, you can start to send messages to your recipients. In the next part of the guide you can read about how you can send MMS messages.

    MMS sending

    You should test the MMS sending if you go back to the Managment Console. There you can find the Compose button at the right corner of the screen. If you click on the Compose button you will see the composer window where you can set up the MMS type. Please click on the "Compose button". (Figure 22)

    the compose button
    Figure 22 - The Compose button

    If you clicked on the Compose button you can start to write your MMS. Please select the Multimedia message (MMS) to be able to send MMS messages. (Figure 23)

    setting up the mms message type
    Figure 23 - Setting the MMS message type


    Please add the recipient number, subject, message text and the full path of the picture which you want to attach. (Figure 24) Please click on the "Send" button after you provided the MMS sending requirements. Before you send the MMS please disable your firewall to send and receive MMS messages!

    providing the mms parameter
    Figure 24 - Providing the MMS parameters


    You will see the log of the sending, if the sending was successfull you will receive the MMS message on the telephone of the recipient. (Figure 25)

    sending the mms
    Figure 25 - Sending MMS


    Conclusion

    To summarize the above mentioned, you can send MMS messages with the Ozeki NG SMS Gateway software product through the Sierra Wireless Fastrack GSM modem from computers to mobile phones. To achieve this function you can easily configure your Gateway in a few steps. With this solution you will gain a stable, reliable and well-functioning system which you will be able to save time and money with.

    Sunrise Switzerland

    This document explains how you can setup an IP SMS connection that connects you directly to the Short Message Service Center (SMSC) of Sunrise. This is a web service based link. It allows you to send and receive SMS messages and SMS delivery reports to the mobile network.

    add service provider
    Figure 1 - Add service provider

    install sunrise connection
    Figure 2 - Install Sunrise connection

    configure connection details
    Figure 3 - Configure connection details

    open firewall settings
    Figure 4 - Open firewall settings

    advanced firewall settings
    Figure 5 - Advanced firewall settings

    add new inbound rule
    Figure 6 - Add new inbound rule

    select rule type
    Figure 7 - Select rule type

    specify ports
    Figure 8 - Specify ports

    allow connection
    Figure 9 - Allow connection

    apply the rule
    Figure 10 - Apply the rule

    specify rule name
    Figure 11 - Specify rule name

    inbound rule created
    Figure 12 - Inbound rule created

    SMPP Connection

    Ozeki NG SMS Gateway is the best SMPP software. It can be installed on Windows and allows you to connect to SMPP sms services using the SMPP protocol. It can be used to send and receive text messages to mobile phones over configured SMPP connections. This page provides detailed instructions on how to setup this great SMPP software, and how to configure SMPP service provider connections to connect your system directly to mobile network operators.

    What is an SMPP software

    An SMPP software is an application that runs on Windows or Linux and implements the SMPP protocol. An SMPP software, such as Ozeki NG SMS Gateway can connect to the Short Messages Sercice Center (SMSC) of an SMS service provider and can send and receive SMS messages.

    SMPP software

    How does an SMPP software work?

    An SMPP software connects to the SMSC over a TCP/IP link. This link is established over the Internet. The SMPP protocol operates above the TCP/IP protocol. The SMSC is often referred to as an SMPP server. The software that connects to it is often referred to as an SMPP client. After the TCP/IP connection is established an SMPP bind messages is sent by the SMPP client to the SMPP server. This SMPP bind message (often called as SMPP bind pdu) carries the SMPP system ID which is your login name and the SMPP password. If the SMPP server allows your SMPP client to connect, it will send an SMPP bind resp, and considers the link established. On the established link, it is possible to send and receive SMS messages using SMPP submit sm requests.

    Is Ozeki NG SMS gateway an SMPP software?

    Yes. Ozeki NG SMS gateway is an SMPP software. It can connect to the SMSC using the SMPP protocol and can be used for both sending and receiveing sms messages. It is important to mention, that Ozeki NG SMS gateway can also act as an SMPP SMSC, since it has a built in SMPP server.

    How to setup your SMPP software (Ozeki NG SMS Gateway)

    To send sms from your SMPP software use these steps:

    1. Type http://localhost:9501 into the browser
    2. Find the 'Service providers' panel in the left
    3. Click 'Add service provider...'
    4. To send SMS from SMPP you need the SMPP connection
    5. Click 'install' to install the SMPP protocol
    6. Enter the SMPP server's host and port
    7. Enter the SMPP username and password
    8. Configure the Sender ID for your texts.
    9. Enable SMPP low level logging, to see the SMS traffic
    10. Click Ok to accept the configuration
    11. Open the events tab to see the SMPP bind command used to connect

    How to setup an SMPP protocol connection in Ozeki NG SMS Gateway

    The following video shows how you can configure an SMPP client connection in the Ozeki NG SMS gateway, which is an SMPP software. If you watch the video, you will see, how to select the SMPP protocol and how to provide the SMPP server address, and the SMPP username and password to be used in the connection setup.

    Installation step 1: Install the SMPP protocol

    The SMPP protocol can be used to connect your computer directly to the Short Message Service Center (SMSC) of the service provider. This connection allows you to send and receive SMS messages over the Internet or over a private IP network. To Install the SMPP protocol click on the "Add service provider" link in the Management console or in the software-s main menu.

    You can install and configure this connection using the SMS gateway's graphical user interface by clicking on the "Service provider connections" menu item.

    To start installing and configuring an SMPP connection, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Console interface. (To find out how to open this interface, check out the QuickStart Guide.)

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu.

    After you have clicked one of these, the Add service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the SMPP protocol, click the Install link in the respective entry in the list (Figure 1).

    install the smpp software
    Figure 1 - Starting to install the SMPP connection

    Installation step 2: Configure SMPP

    After you have installed the SMPP Connection, the SMPP configuration form will show up on the right hand side of your screen. The first tab is the SMPP settings tab. This is where you need to enter the SMPP server details: SMPP Host name, SMPP port, SMPP user name and SMPP password. These details are provided by the SMPP server (or SMPP sms service provider), after your account has been created. The SMPP host name and port are used to create the TCP/IP link the SMPP server. The SMPP user name and password are used to login to the SMPP server.

    specifying the server settings
    Figure 2 - Specifying the server settings

    After the SMPP server connection details are configured, specify the telephone number assigned to this connection and the service provider connection name. The telephone number will be used as the SMS Sender ID when you send an SMS. The service provider connection name is used in Ozeki to identify the connection.

    Make sure that you choose a meaningful connection name. For example if you have set up an SMPP connection with Vodafone, it is advisable to name it "Vodafone". Also, note that different connections should be given different names. If you have different connections from the same service provider, you can use different but similar names for them, e.g.: "Vodafone1", "Vodafone2" (or something of the like).

    Tipp: SMPP load balancing

    If you want to install multiple SMPP connections, and you wish to distribute the SMPP SMS traffic between them, you can create load balancing, by providing the same connection name. For example you can create two SMPP connections and if you name bothe "Vodafone", the Ozeki NG SMS Gateway system will distribute the load between them evenly. For more information please visith the SMS load Balancing and the Load Balancing for SMPP SMS v3.3 page.

    Tipp: SMPP Sender ID format

    When you enter the Sender ID into the telephone number filed, you can pick a standard telephone number known as SMS long code, you can use a short local telephone number known as SMS short code or a phone number containing letters and digits known as Alphanumeric Sender ID.

    The most common SMPP sender ID format is the SMS long code, which is a standard mobile telephone number in international format: starting with "+". For example +3620123467 would be a telephone number in Hungary. If you send an SMS using this number in the telephone number field, the recipients will see that your SMS messages came from the mobile phone +3620123467. They will not notice that the SMS came from an SMPP software.

    Tipp: Changing the SMPP sender ID on a per message basis

    You might notice that there is an "override" checkbox next to the telephone number field. You can check the overridable checkbox to allow your users to customize the sender ID on a per message basis. For example if this checkbox is checked and an application is sending SMS using a Database connection, you can specify a different phone number to be displayed as the sender of the message for each SMS.

    Note that the phone number to be specified in the Telephone number edit box is a mandatory value. If you leave the edit box empty, the sending will be unsuccessful.

    Tipp: Configure SMPP logging in your SMPP software

    Logging SMPP protocol messages can be helpful in troubleshooting problems. To configure logging, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data.
    You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 3).

    logging options
    Figure 3 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 3 above).

    If you are happy with the default settings, leave the text boxes unchanged.

    Installation step 3: Select the SMPP protocol version

    Ozeki NG SMS Gateway supports SMPP protocol version 3.3 and SMPP protocol version 3.4. SMPP v3.4 is the most widely used SMPP implementation in 2022. If you need SMPP v5.0, you should switch to an even better SMPP software called Ozeki 10 SMS Gateway.

    By selecting either of the radio buttons (v3.3 or v3.4), you can specify the protocol version.

    In the Connection tab of the Configuration panel, you can define detailed protocol-specific options and specify NPI and TON settings (in the left section) and you can make communication link management settings (in the right section).

    You can specify the system type by entering its name in the System type text box. The system type is for assigning the protocol standard of the other side (SMSC). It is specified by the service provider.

    To specify the bind mode, select one of the three radio buttons: Transmitter, Receiver or Transceiver.

    The bind mode describes the way of communication between Ozeki NG - SMS Gateway and the SMS Center of a service provider.

    • Select Transmitter if you use this connection only for sending SMS messages.
    • Select Receiver if you use this connection only for receiving messages.
    • Select Transceiver if you use this connection for both sending and receiving messages.

    In this section you can also find boxes for NPI and TON settings. NPI is short for Network Protocol Identification. TON is short for Type Of Number. In each of them, you can enter numbers. This information is provided by the GSM service provider (Figure 4).

    connection tab
    Figure 4 - Connection tab

    In the right section of this configuration panel you can manage communication links. At first, in "Windows size" line you can increase the window size, if your SMPP service provider supports windowing.

    If you check the checkbox in the Communication link management section, you can make the program send keepalive packets to maintain connection. Proxy servers will drop a connection after a short period of time if there is no activity on it. Keepalive packets are sent during idle periods to keep the connection open.

    In the Keepalive period edit box you can specify the maximum length of idle connection between the Ozeki NG - SMS Gateway and the SMSC. You can specify it by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (30 seconds), leave this edit box unchanged.

    You can also check the Slow down communication to checkbox (you can provide the exact time in MPM) if your service provider cannot accept messages at a high speed.

    Installation step 4: Configure SMPP submit and SMPP delivery report format

    To configure the SMPP submit sm format used to send SMS messges, you need to open the "Message submission" tab. On this tabpage you may also configure the SMPP delivery report format to be used by the Ozeki SMPP software.

    In the Message submission tab there are two sections: Delivery reports and Submit timeout handling. In "Delivery reports" section you can enable Request delivery reports option. Delivery reports give you message delivery status for submitted messages. They are returned by the service provider when a message arrives to the recipient handset. Then specify the date format used by your service provider in delivery reports in Delivery date format line.

    In Submit timeout handling sector you can specify the preferred way to handle submit timeout. In the Submit timeout edit box you can specify the maximum waiting time for an SMS Center response confirming that your message has been successfully submitted. Successful submission means that the SMS Center has accepted the message for delivery. You can specify the waiting time by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (60 seconds), leave this edit box unchanged.

    You can choose how to consider a message you have sent if there is no response from the SMS Center after the specified length of time. Select one of the three radio buttons.

    • Select Sent to consider a message sent even if there is no response from the SMS Center.
    • Select Not sent to consider a message not sent if there is no response from the SMS Center.
    • Select Retry later to make the program try to send a message later if the SMS Center has not confirmed its status as sent. Then, the message will be placed last in the outgoing message queue and sent out again when it is its turn (Figure 5).

    messsage submission tab
    Figure 5 - Message submission tab

    In Message data tab you can see two sectors: "Character encoding of text messages" and "Message data transport" (Figure 6). First, you can specify the preferred character set (Default, ISO_8859_1, UCS2, GSM7bit) and the character encoding policy (Best match, Transform, Enforce).

    Best match: Convert to preferred character set if lossless conversion is possible. (Character substitutions are not allowed.)

    Transform: Convert to preferred character set if possible. (Character substitutions are allowed.)

    Enforce: Always use the preferred charset. (Character substitutions and character losses are allowed.)

    Then you can enable one of the following options if it is required: Use GSM 7 bit packed encoding, Encode @ sign as iso 8859-1 character, Convert incoming GSM 7 to iso 8859-1.

    In "Message data transport" section you can enable segmentation and reassembly (SAR), to automatically split outgoing messages and reassemble incoming messages if needed as long messages should be sent through the mobile network in several parts.

    As some service providers might ask you to use TLV fields instead of the standard SM field in this section you can select from these options:

    • Put UDH into TLV for binary SMS
    • Put UDH into TLV for text SMS
    • Put msg data into TLV instead of SM field

    message data tab
    Figure 6 - Message data tab

    The last tab is Encoding in Configuration panel. There are the following sections: ESM Class field, Number format encoding, DCS field, Service type.

    In ESM Class field you can enable these options:

    • Put Delivery Report Req. into ESM class
    • Put UDHI into ESM class for text SMS
    • Put UDHI into ESM class for binary SMS

    In case your service provider ask you to set ESM class field to 00 for all messages, please make sure the following options are NOT checked.

    In Number format encoding section you can specify TON and NPI numbers; in the other two section you can specify DCS that determines the charset, the message class and binary message encoding, and service type parameter of SUBMIT SM PDU (Figure 7).

    smpp software features
    Figure 7 - Configure SMPP pdu encoding

    The Configuration panel for service provider connections contains a Connect automatically on startup checkbox (in the bottom left-hand corner). If it is checked, Ozeki NG - SMS Gateway will automatically initiate a connection with the SMS Center when the program has started. If this checkbox is not checked, the connection has to be initiated manually.

    Installation step 5: Start the SMPP connectoin

    Once the SMPP protocol is configured, you Ozeki SMPP software is ready to be used. You can start the connection by clicking on the Connect link of the left hand side of the screen. (Figure 8).

    links to operations
    Figure 8 - Links to operations

    You can open the panel of a service provider connection by clicking its name in the Service providers panel in the Management Console.

    The panel of a service provider connection consists of three sections. In the upper section you can find the name of the service provider connection (with the name of its protocol in brackets). You can see an icon showing if the service provider connection is connected. If it is not, the icon is marked with an "x".

    To the right of the icon you can find links to perform different operations.

    • Configure: to configure or modify the configuration of an installed service provider connection. Clicking this link will take you back to the Configuration panel.
    • Events: to view the logging of the latest server events related to the service provider connection. Clicking it will bring up the Events panel containing the logging of the latest server events.
    • Connect: to connect the service provider connection with the SMS Center.
    • Disconnect: to disconnect the service provider connection from the SMS Center.
    • Uninstall: to uninstall the service provider connection.

    In the middle section of the panel you can see some of the most important configuration information. The options that have been (re)activated during the configuration are marked with a tick. The options that have not been activated or those that have been deactivated during the configuration are marked with an "x".

    In the lower section of the panel of the service provider connection you can read some information about its protocol.

    Flash SMS support in SMPP SMS Services

    The FLASH SMS functionality is implemented in Ozeki NG SMS Gateway. If you use the SMPP protocol, you have to configure your SMPP service provider connection to support FLASH SMS messages.

    Configure your SMPP service provider connection

    You can use FLASH SMS in SMPP connections in two ways:

    1.) The first option: If your SMPP provider does not support TLV fields, you can encode the FLASH SMS message class setting in the DCS field of the SMPP PDU. To use this option, make sure the "Put UDH into TLV for text SMS" checkbox is not checked in Message data tab of the SMPP service provider connection form. On the same tab set the "Server charset:" to "Default"! After this is configured you can send GSM 7 bit charset messages as flash SMS.

    the message data tab

    Please note, that if you use UNICODE characters in SMPP 3.3 or SMPP 3.4 the only way you can use FLASH SMS is if your provider supports the TLV fields.

    2.) The second option: If your SMPP provider supports TLV fields, here is what you should do: Make sure the "Put UDH into TLV for text SMS" checkbox is checked. If TLVs are supported by your service provider, both GSM 7bit and UCS2 messages can be sent as FLASH.

    Custom SMPP System type field

    Some service providers require you to define a special system type parameter. Ozeki NG SMS Gateway v3.0.2 and later versions allow you to define the system type parameter in a better way. This guide gives you information on how this can be done

    The SMPP service provider connection of Ozeki NG SMS gateway allows you to define bytes used in the system type field in hexadecimal format. This gives you full control over the system type field.

    By default if you put "abc" into the system type field, it will mean the following bytes in the SMPP PDU: "616263". In version 3.0.2 or later you can include hexadecimal values in the system type field. For example you can put "a\xF0c". This would mean "61F063" in the SMPP PDU. Note that in the expression \xF0 means that a user defined byte value should be used instead of the character codes. This syntax allows you to define any byte values in the system type field.

    special characters in the smpp system type field
    Figure 1 - Special characters in SMPP System Type field

    SMPP low level logging

    To detect errors in the SMPP communication with your service provider you might need to enable low level logging in the application. In this document we give you information on how to enable this feature to be able to track down errors in the communication

    Introduction

    To enable low level communication logging in the SMPP service provider connection, please check the "Low level communication logging" checkbox in the "Logging" tab of the SMPP service provider connection's configuration form (Figure 1). If this checkbox is enabled, you will see the SMPP protocol messages that are sent to the SMSC and that are received from the SMSC (Figure 2).

    smpp low level communication logging
    Figure 1 - SMPP low level communication logging

    Basically there are three important SMPP protocol message: the login message, the submit message, the incoming SMS message. The SMPP login message is sent by Ozeki NG to the SMSC and if the username and password in the login message was correct, the SMSC sends a response message back. The SMS submit message is also sent by the Ozeki NG SMS software to the SMSC and the SMSC sends an SMPP response if the message was accepted. If you are receiving an SMS, the SMSC send in an SMPP protocol message and the Ozeki SMS software replies to it, to confirm it has accepted the message (Figure 2).

    smpp protocol messages
    Figure 2 - SMPP protocol messages

    If you take a closer look at the protocol messages, you will see, that in the low level communication log you see if the message was sent by the Ozeki software or it was received by the Ozeki software. If the message was sent by the Ozeki software you will see a "<-" sign in front of the SMPP protocol data, if it is an incoming SMPP protocol data you will see a "->" sign in front of the log entry (Figure 3).

    smpp communication
    Figure 3 - SMPP communication

    For example if you are hunting for incoming messages, you should see an SMPP PDU sent to your system from the SMSC in the low level log.

    SMS short code

    In this guide we give you information about how you can send and receive SMS messages using a shortcode number with the SMS Gateway.

    Introduction

    IP SMS connections, such as SMPP, CIMD2, HTTP and UCP/EMI allow you to use a shortcode number as the sender address in your SMS messages. A shortcode number is usually a 4 or 5 digit telephone number (for example: 3344). You receive this telephone number from your SMS service provider, when you sign up for their service.

    If you have a shortcode number assigned to your SMS service, you can also receive SMS messages. The mobile phones can send an SMS message to your short code.

    Limitations

    Shortcode SMS numbers cannot be used if you use a GSM modem attached to your computer (with a phone to pc data cable) to send and receive SMS messages. If you use a GSM modem, the standard (long) telephone number can be used, that belongs to the SIM card in the GMS modem.

    A short code number can only be used in a single country or a single GSM network. SMS messages sent to or from a shortcode are not routed between countries and GSM networks. This means, that mobile phones that are roaming, or that are using a different SMS service provider cannot be reached.

    How to configure

    It is very easy with the Ozeki NG SMS gateway to use a shortcode SMS number. You can configure it on the configuration form of the service provider connection. You must enter the shortcode into the telephone number field (Figure 1).

    configure an sms short code in ozeki ng sms gateway
    Figure 1 - Configure an SMS Short code in Ozeki NG SMS Gateway

    Cancel_sm with Ozeki NG SMS Gateway

    This guide provides you detailed information on how to cancel an SMS text message after it has been sent to the SMS center (SMSC) but it has not been received by the recipient. This functionality can be achieved by cancel_sm service that is first available in 3.15.8 version of Ozeki NG SMS Gateway. Follow the guide below to adopt this service successfully.

    If you send out an SMS message from your database with the help of Database user of Ozeki NG SMS Gateway you need to insert a record into the database. The database user checks the database and it sends out the SMS text message to the SMS center (SMSC). From the SMSC you will receive a report about the fact that the message arrives at the SMSC. This report contains the callback ID of the message. When the report is received the Database user updates the message status to Sent and insert the callback ID into Reference column of the database. This is the usual process of sending SMS from a database (Figure 1).

    sending sms from a database with database user
    Figure 1 - Sending SMS from a database with Database user

    But if the user did not received the message after some time for any reason (for example the handset is off), then it is possible to cancel the message from the SMSC with the help of cancel_sm service. It can be the proper solution if the message has been expired after a definite time.

    To cancel the message from the SMSC, insert a record into the database:

    • Message type: SMS:CANCEL
    • Recipient: the original recipient of the message
    • Message: the received callback ID

    So if you insert the record above into the database, the Database user will poll out it and send a cancel indication to the SMSC and the SMSC will return a confirmation if the message has been canceled (Figure 2).

    cancelling sms with cancel_sm
    Figure 2 - Canceling SMS with cancel_sm

    Configuration guide

    First start Ozeki NG SMS Gateway and go to Database user configuration pane. In SQL Settings menu select SQL for sending tab. Click on Sent tab and type reference='$callbackid' after "status='sent'," (Figure 3).

    type reference
    Figure 3 - Type reference='$callbackid'

    In our example I send out a test message to demonstrate the solution (Figure 4).

    • Recipient: +06205460691
    • Message: Hello World!
    • Status: send

    send out a message
    Figure 4 - Send out a message

    On Figure 5 you can see that the message is accepted for delivery and the callback ID is also defined in this report.

    callback id
    Figure 5 - Callback ID

    With SELECT * FROM ozekimessageout; statement you can query the messages from ozekimessageout table. After clicking on Execute you can see the message data that contain the callback ID among others (Figure 6).

    query the ozekimessageout table
    Figure 6 - Query ozekimessageout table

    Now I insert a record to be sent out into the database where

    • Recipient: is the same as in the original message (+06205460691)
    • Message type: SMS:CANCEL
    • status: send (Figure 7).

    insert a record to send out
    Figure 7 - Insert a record to send out

    In SMPP service provider the following PDUs will be seen: the first row is the cancel indication for canceling the message. The second row is the confirmation about the fact that the message has been canceled (Figure 8).

    pdus for canceling
    Figure 8 - PDUs for canceling

    Optional SMPP parameters

    On this page, you can read about what optional parameters are where they can be given and how they can be customized within the SMPP connection. This guide also gives a definition to what TLV field means and helps to carry out the customization of optional parameters.

    In certain cases it is advisable to add extra parameters to SMPP connection. These parameters are inserted into TLV fields. The fill-out of these fields is only optional and depends on the service provider's requirements. Ozeki NG SMS Gateway supports the functionality of this solution. The following sections are going to demonstrate the use and features of TLV field and explain how to fill them out with optional SMPP parameters.

    What does TLV stand for?

    TLV is a data type, a structure which enables the addition of new parameters to SMPP PDU. TLV is the acronym of Tag Length Value. TLVs are often called 'optional fields'. The TLV extra parameters were added to the SMPP protocol in version 3.4. TLV's can be added as byte stream at the end of the standard SMPP PDU's. The first two bytes give the length of the parameter, the third and fourth byte indicate the value of the actual data which go directly after the set bytes.

    General

    You need to install Ozeki NG SMS Gateway as well as SMPP service provider to send SMS. After configuration the system may require more parameters to gain total functionality. The extra parameteres are called TLVs and they are used to maintain the optimal performance of the system.

    Note: This solution is only available in Ozeki NG SMS Gateway v3.15.33 or above!

    Customization

    1. Send SMS with general customization of TLV parameters

    If you customize your parameters according to the followings, all the messages sent through this SMPP connection will be sent out containing this optional field. After the configuration of SMPP connection further parameters can be set. Click on the Configure menu and select the Message submission tab. Fill in the Optional parameter box with the data as in the example in Figure 1.

    optional parameter box
    Figure 1 - Optional parameter box

    I send a test message afterwards (Figure 2).

    test message
    Figure 2 - Test message

    The success of configuration can be checked at the Events of SMPP service provider. At the end of the PDU you can view the customized parameters the same way as in Figure 3.

    tlv parameters in log
    Figure 3 - TLV parameters in log

    2. Customizing the optional parameters with each SMS

    It is possible to set the optional parameter with each SMS. This way, it can be determined which TLV value is added to the PDU at the SMPP connection. There are two ways to pre-determine the optional field: Database user or HTTP API.

    Database user

    To determine the optional parameters install a Database user. After installation, log in Ozeki NG SMS Gateway and enter the Configure menu in Database user. The name of the field is already containing data. The data is placed after the "tlv_" part. This is the Tag of the TLV field. The data returned in this field will be the Value of the TLV. The Length of the customized TLV field will be calculated from the returned data. To customize the Database user click on the SQL for sending tab and type the "tlv_" keyword and the TLV tag's value into the Polling box as the example shows in Figure 4.

    the tlv tag
    Figure 4 - TLV tag

    In this example the SQL field name is "tlv_5721". The TLV Tag is 5721. The data returned in this SQL field is '38353334322213'. This will be the TLV Value. The TLV Length will be calculated from the TLV Value.

    Enter SQL prompt and give an SQL query. An example is shown in Figure 5.

    sql query
    Figure 5 - SQL query

    In the example the number in tlv_5721 is the TLV Tag, which has a Value,'38353334322213'. The Length is determined by the Value which is '0007'.

    The success of configuration can be checked at the Events of SMPP service provider. At the end of the PDU you can view the customized parameters the same way as in Figure 6.

    log message
    Figure 6 - Log message

    HTTP API

    Optional parameters can be requested in HTTP API as well. The customization of TLV parameters occurs the same way as in case of Database user. The "tlv_" is the TLV field containing the TLV Tag. The data returned is again the Value of the TLV and the Length is calculated from it. To do the customization insert an HTTP request into your browser. Below is an example.

    HTTP request

    http://127.0.0.1:9501/api?action=sendmessage&username=admin&password=abc123&recipient
    =06301234567&tlv_5721=38353334322213&messagetype=SMS:TEXT&messagedata=Hello+world
    

    You can see in the response (Figure 7) that the Ozeki NG SMS Gateway has accepted the message for sending.

    http response in xml
    Figure 7 - HTTP response in xml

    The success of configuration can be checked at the Events of SMPP provider. At the end of the PDU you can view the customized parameters the same way as in Figure 8.

    tlv parameters in http log message
    Figure 8 - TLV parameters in HTTP log message

    In the example the number in tlv_5721 is the TLV Tag, which has a Value,'38353334322213'. The Length is determined by the Value '0007'.

    Dynamic SMPP parameters

    In Ozeki NG SMS Gateway, there is an option to assign dinamic values for the SMPP submit_sm PDUs TON and NPI numbers, ESM class and data coding. This guide gives a definition about these parameters and lists the cases when you can set these parameters dynamically - note that this feature is only available in Ozeki NG SMS Gateway 4.2.5 or above.

    You can read about SMPP connections here: SMPP connection

    The source_addr_ton, source_addr_npi, dest_addr_ton, dest_addr_npi, esm_class and data_coding are SMPP parameters describing the SMPP PDUs. There may be some cases when you need to set these parameters dynamically Ozeki NG SMS Gateway is capable of operating with dynamically set SMPP PDU parameters.

    About SMPP parameters

    Source_addr_ton and dest_addr_ton define the Type of Number (TON) to be used in the SME address parameters. The following TON values are defined:

    TON Value
    Unknown 00000000
    International 00000001
    National 00000010
    Network Specific 00000011
    Subscriber Number 00000100
    Alphanumeric 00000101
    Abbreviated 00000110

    Every other value besides the above are reserved (service providers may differ).

    Source_addr_npi and dest_addr_npi define the Numeric Plan Indicator (NPI) to be used int he SME address parameters. The following NPI values are defined:

    NPI Value
    Unknown 00000000
    ISDN (E163/E164) 00000001
    Data (X.121) 00000011
    Telex (F.69) 00000100
    Land Mobile (E.212) 00000110
    National 00001000
    Private 00001001
    ERMES 00001010
    Internet (IP) 00001110
    WAP Client Id (to be defined by WAP forum) 00010010

    Every other value besides the above are reserved (service providers may differ).

    The esm_class parameter is used to indicate special message attributes associated with the short message. The esm_class parameter is encoded as follows (in the submit_sm PDUs):

    Bits 76543210 Value
        Messaging Mode (bits 1-0)
      xxxxxx00 Default SMSC Mode (e.g. Store and Forward)
      xxxxxx01 Datagram mode
      xxxxxx10 Forward (i.e. Transaction) mode
      xxxxxx11 Store and Forward mode (use to select
    Store and Forward mode if Default SMSC Mode is non Store and Forward)
         
        Message Type (bits 5-2)
      xx0000xx Default message Type (i.e normal message)
      xx0010xx Short Message contains ESME Delivery Acknowledgement
      xx0100xx Short Message contains ESME Manual/User Acknowledgement
         
        GSM Network Specific Feature (bits 7-6)
      00xxxxxx No specific features selected
      01xxxxxx UDHI Indicator (only relevant for MT short messages)
      10xxxxxx Set Reply Path (only relevant for GSM network)
      11xxxxxx Set UDHI and Reply Path (only relevant for GSM network)

    The parameter data_coding defines the encoding scheme of the short message user data. The following values are defined:

    Bits 76543210 Meaning Notes
      00000000 SMSC Default Alphabet  
      00000001 IA5 (CCITT T.50)/ASCII (ANSI X3.4) b
      00000010 Octet unspecified (8-bit binary) b
      00000011 Latin 1 (ISO-8859-1) b
      00000100 Octet unspecified (8-bit binary) a
      00000101 JIS (X 0208-1990) b
      00000110 Cyrillic (ISO-8859-5) b
      00000111 Latin/Hebrew (ISO-8859-8) b
      00000110 UCS2 (ISO/IEC-10646) a
      00001001 Pictogram Encoding b
      00001010 ISO-2022-JP (Music Codes) b
      00001011 reserved  
      00001100 reserved  
      00001101 Extended Kanji JIS (X 0212-1990) b
      00001110 KS C 5601 b
      00001111 reserved  
      ...    
      10111111 reserved  
      1100xxxx GSM MWI control c
      1101xxxx GSM MWI control c
      1110xxxx reserved  
      1111xxxx GSM message class control d

    Notes:

    1. These coding schemes are common to GSM, TDMA and CDMA. The SMPP protocol allows ESME applications to use the same DCS value (i.e. the GSM 03.38 value) for all three technologies.
    2. In cases where a Data Coding Scheme is defined for TDMA and/ or CDMA but not defined for GSM, SMPP uses GSM 03.38 reserved values.
    3. The data_coding parameter will evolve to specify Character code settings only. Thus the recommended way to specify GSM MWI control is by specifying the relevant settings in the optional parameters _ms_msg_wait_facilities and ms_validity.
    4. The data_coding parameter will evolve to specify Character code settings only. Thus the recommended way to specify GSM message class control is by specifying the relevant setting in the optional parameter dest_addr_subunit.

    Using dynamically set SMPP parameters in Ozeki NG SMS Gateway

    There are three cases when you can dynamically set the SMPP PDU parameter values mentioned above.

    While sending an SMTP message, you can set the parameters yourself. You can read a guide about this here: Dynamic parameters in SMTP messages

    You can pass PDU parameters via HTTP too. You can read a guide about this method here: Dynamic SMPP parameters via HTTP

    A database user can set PDU parameters dynamically by saving them into a database table's records. You can read a guide about this here: Dynamic SMPP parameters from database

    Note that if you do not pass SMPP parameter values dynamically, Ozeki NG SMS Gateway will use its configuration to define SMPP parameter values. If you did not configure SMPP values yourself, Ozeki NG SMS Gateway will use default settings. Besides that, you must use decimal values for setting SMPP parameters.

    For more information please contact us at info@ozekisms.com.

    UCP Connection

    In this chapter you can find out how to install and configure the UCP IP SMS protocol for SMS messaging using the Ozeki NG - SMS Gateway software. In addition to an introduction containing general information about this protocol, this page provides detailed installation and configuration instructions.

    Introduction

    As you can read on the Service Provider Connections page, you need to install and configure one or more service provider connections for SMS messaging using Ozeki NG - SMS Gateway. One of the service provider connections supported by the software is the Universal Computer Protocol (UCP) connection.

    This protocol is often used by GSM service providers for IP SMS connectivity. The currently used protocol versions (v3, v3.5, v4.0) can be used to transfer high volumes of SMS traffic. It is used for both premium rate and normal rate SMS messages.

    One of the advantages of using UCP connections is that you can specify the sender address of the message. The sender address can be a custom phone number or a short word containing alphanumeric characters. (See the instructions about the overridable checkbox below.) Note, however, that some GSM service providers restrict the use of this option.

    Another advantage of UCP is that it allows sending messages of every type the GSM network can carry. It can be used to send binary SMS messages (operator logos, ringtones), WAP Push messages, as well as other types of messages. (Check out the Appendix for links to pages about different message types.) Concatenated SMS messages and various alphabets can also be used.

    In order to use UCP to connect to an SMSC over the Internet or other private TCP/IP network, you need to subscribe to the service of a service provider.

    If you wish to use UCP to connect to your service provider, you need the following information from the service provider:

    IP address of the SMSC
    Port number of the SMSC
    User name
    Password

    Some service providers require you to set up an IPSEC VPN tunnel to connect to their SMSC (Figure 1).

    ucp connection with vpn
    Figure 1 - UCP connection with VPN

    In most cases you need a fix IP address, which you have to let the GSM service provider know so that they can give you access through their firewall. In some situations, the service provider does not want you to be able to set up more than one UCP connection from your computer to their service. If this is the case, they might ask you to use a specific source port for the connection.

    Installation and configuration

    You can install and configure this connection using the graphical user interface of Ozeki NG - SMS Gateway.

    To start installing and configuring a UCP service provider connection, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Console interface. (To find out how to open this interface, check out the QuickStart Guide.)

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu.

    After you have clicked one of these, the Add service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the UCP protocol, click the Install link in the respective entry in the list (Figure 2).

    starting the ucp connection installation
    Figure 2 - Starting to install the UCP connection

    When you have installed the UCP Connection, the Configuration panel will show up on the right of the interface. The first tab of the panel is the UCP settings tab.

    First, specify the UCP server settings. This information is provided by the GSM service provider whose service you have subscribed to. The connection parameters are the host name (or IP address), the port number, a username and a password. Service providers often use the phone number of the service or the port number as the username. Enter the information in the respective edit boxes (Figure 3).

    specify the server settings
    Figure 3 - Specifying the server settings

    Then, specify the telephone number assigned to this connection and the service provider name. To facilitate identification and to avoid confusion, you should name the connection after the GSM service provider. E.g., if you have set up an SMPP connection with Vodafone, it is advisable to name it "Vodafone". Also, note that different connections should be given different names. If you have different connections from the same service provider, you can use different but similar names for them, e.g.: "Vodafone1", "Vodafone2" (or something of the like). However, some load balancing solutions require an identical name for different connections. For details, visit the Load Balancing and the Load Balancing for SMPP v3.3 page.

    Some UCP servers require login. If this is the case, check the Server requires login checkbox.

    Enter the information in the respective edit boxes. Remember to enter the phone number in international format: starting with "+". You can check the overridable checkbox to the right of the Telephone number edit box. This ensures that you can replace the phone number specified in the Telephone number edit box with a different one to be displayed as the sender of an outgoing message. You can also replace the number with (alphanumeric) text consisting of a maximum of eleven (11) characters. Therefore, when a message is sent out, e.g. using the Database user, you can specify any different phone number or a name to be displayed as the sender of the message.

    Note that the phone number to be specified in the Telephone number edit box is a mandatory value. If you leave the edit box empty, and if the outgoing SMS message does not carry a sender phone number either, the sending will be unsuccessful.

    To perform general settings related to sending and receiving SMS messages using this protocol, click the General Settings tab. This will open a panel consisting of the Sending and receiving, Timeout handling, Communication link management section.

    In Sending and receiving section you can check any or all of the checkboxes. Which one(s) to check depends on what you wish to use this connection for and whether you need a delivery report. You can choose to use the connection for only sending or only receiving SMS messages (or both sending and receiving), and you can choose to request a delivery report for outgoing messages (Figure 4).

    the general settings tab
    Figure 4 - The General settings tab

    In the other sections of the tab you can make choices and specifications to handle your connection to the SMS Center and the status of your SMS messages.

    In the Submit timeout edit box you can specify the maximum waiting time for an SMS Center response confirming that your message has been successfully submitted. Successful submission means that the SMS Center has accepted the message for delivery. You can specify the waiting time by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (60 seconds), leave this edit box unchanged.

    You can choose how to consider a message you have sent if there is no response from the SMS Center after the specified length of time. Select one of the three radio buttons.

    • Select Sent to consider a message sent even if there is no response from the SMS Center.
    • Select Not sent to consider a message not sent if there is no response from the SMS Center.
    • Select Retry laterto make the program try to send a message later if the SMS Center has not confirmed its status as sent. Then, the message will be placed last in the outgoing message queue and sent out again when it is its turn.

    In the right section of this configuration panel you can manage communication links. At first, in "Windows size" line you can increase the window size, if your UCP service provider supports windowing.

    If you check the checkbox in the Communication link management section, you can make the program send keepalive packets to maintain connection. Proxy servers will drop a connection after a short period of time if there is no activity on it. Keepalive packets are sent during idle periods to keep the connection open.

    In the Keepalive period edit box you can specify the maximum length of idle connection between the Ozeki NG - SMS Gateway and the SMSC. You can specify it by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (30 seconds), leave this edit box unchanged.

    You can also check the Limit speed to checkbox (you can provide the exact time in MPM) if your service provider does not support high speed.

    To configure logging, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 5).

    logging options
    Figure 5 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 5 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    On Advanced tab you can make further settings related to the operator and delivery reports, and you can specify the Original Protocol Identification. In Operator-specific settings you can check or unchecked Server requires login and Include checksum in PDU options if your service provider requires it. In Delivery reports section you can provide the "Notification Type" by giving a number from the follows:

    • 0 is the default value set by your service provider.
    • If you set 1 in the edit box, Delivery Notifications (DN) are reported only.
    • If you set 2 in the edit box, Non-Delivery Notifications (ND) are reported only.
    • If you set 3 in the edit box, both Delivery and Non-Delivery Notifications are reported.
    • If you set 4 in the edit box, Buffered Message Notificatons (BN) are reported only.
    • If you set 5 in the edit box, both Buffered Message Notifications and Delivery Notifications are reported.
    • If you set 6 in the edit box, both Buffered Message Notifications and Non-Delivery Notifications are reported.
    • If you set 7 in the edit box, all notifications (DN,ND and BN) are reported.

    After you set the notification type you can select from these options:

    • Leave (N)PID and (N)AdC empty; Use 0639 and OAdC;
    • Use 0539 and client source IP and port;
    • Use 0539 and the following (N)AdC (Figure 6).

    advanced tab
    Figure 6 - Advanced tab

    On Charsettab you can specify how to handle character set differences. Select Charset Handling Policy from the dropdown menu:

    • Best match: Use the lowest cost charset which contains all characters in the message. (Character substitutions are not allowed.)
    • Transform: Transform to the preferred charset if possible. (Character substitutions are allowed.)
    • Enforce: Always use the preferred charset. (Character substitutions and character losses are allowed.)

    Finally, specify the characterset you preferred: GSM7bit, UCS2, IA5_AO (Figure 7).

    the charset tab
    Figure 7 - Charset tab

    The Configuration panel for service provider connections contains a Connect automatically on startup checkbox (in the bottom left-hand corner). If it is checked, Ozeki NG - SMS Gateway will automatically initiate a connection with the SMS Center when the program has started. If this checkbox is not checked, the connection has to be initiated manually.

    To initiate the connection manually, click the Connect link in the panel of the service provider connection (Figure 8).

    links to operation
    Figure 8 - Links to operations

    You can open the panel of a service provider connection by clicking its name in the Service providers panel in the Management Console.

    The panel of a service provider connection consists of three sections.

    In the upper section you can find the name of the service provider connection (with the name of its protocol in brackets). You can see an icon showing if the service provider connection is connected. If it is not, the icon is marked with an "x".

    To the right of the icon you can find links to perform different operations.

    • Configure: to configure or modify the configuration of an installed service provider connection. Clicking this link will take you back to the Configuration panel.
    • Events: to view the logging of the latest server events related to the service provider connection. Clicking it will bring up the Events panel containing the logging of the latest server events.
    • Connect: to connect the service provider connection with the SMS Center.
    • Disconnect: to disconnect the service provider connection from the SMS Center.
    • Uninstall: to uninstall the service provider connection.

    In the middle section of the panel you can see some of the most important configuration information.

    • The options that have been (re)activated during the configuration are marked with a tick.
    • The options that have not been
    • activated or those that have been deactivated during the configuration are marked with an "x".

    In the lower section of the panel of the service provider connection you can read some information about its protocol.

    CIMD2 Connection

    In this chapter you can find out how to install and configure the UCP IP SMS protocol for SMS messaging using the Ozeki NG - SMS Gateway software. In addition to an introduction containing general information about this protocol, this page provides detailed installation and configuration instructions.

    Introduction

    As you can read on the Service Provider Connections page, you need to install and configure one or more service provider connections for SMS messaging using Ozeki NG - SMS Gateway. One of the service provider connections supported by the software is the CIMD2 connection.

    The Computer Interface Message Distribution (CIMD) protocol was introduced by Nokia. The Nokia SMS Center includes an CIMD2 interface that transfers messages between applications and the Nokia Short Message Service Center (SMSC).

    CIMD2 is version 2 of the Computer Interface to Message Distribution protocol. The CIMD2 interface is suitable for client applications that send and retrieve messages over TCP/IP sockets, such as Ozeki NG - SMS Gateway.

    One of the advantages of using CIMD2 connections is that you can specify the sender address of the message. The sender address can be a custom phone number or a short word containing alphanumeric characters. (See the instructions about the overridable checkbox below.) Note, however, that some GSM service providers restrict the use of this option.

    Another advantage of CIMD2 is that it allows sending messages of every type the GSM network can carry. It can be used to send binary SMS messages (operator logos, ringtones), WAP Push messages, as well as other types of messages. (Check out the Appendix for links to pages about different message types.) Concatenated SMS messages and various alphabets can also be used.

    A CIMD2 connection can be used through an IP link. This link can be a leased line or the Internet. Optionally the link can be protected by VPN.

    If you wish to use CIMD2 to connect to your service provider, you need to receive the following information from the service provider:

    IP address of the SMSC
    Port number of the SMSC
    User name
    Password

    Installation and configuration

    You can install and configure this connection using the graphical user interface of Ozeki NG - SMS Gateway.

    To start installing and configuring a UCP service provider connection, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Console interface. (To find out how to open this interface, check out the QuickStart Guide.)

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu.

    After you have clicked one of these, the Add service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the CIMD2 protocol, click the Install link in the respective entry in the list (Figure 1).

    starting ot install the cimd2 connection
    Figure 1 - Starting to install the CIMD2 connection

    When you have installed the CIMD2 Connection, the Configuration panel will show up on the right of the interface. The first tab of the panel is the CIMD2 settings tab, which consists of a Connection and an Identification section.

    First, specify the CIMD2 server settings. This information is provided by the GSM service provider whose service you have subscribed to. The connection parameters are the host name (or IP address), the port number, a username and a password. The hostname refers to the server that Ozeki NG - SMS Gateway will connect to. This specification allows you to customize a connection. The valid values of the port parameter range from 0 to 65535. The username and the password are text attributes which can also include numerical characters. Service providers often use the phone number of the service or the port number as the username. These specifications are an essential part of the SMSC authentication method. Enter the information in the respective edit boxes (Figure 2).

    In the Use source port edit box you can specify the source port. Only use a value other than 0 if your operator prompts you to do so.

    specifying the server settings
    Figure 2 - Specifying the server settings

    Then, specify the telephone number assigned to this connection and the service provider name. To facilitate identification and to avoid confusion, you should name the connection after the GSM service provider. E.g., if you have set up an SMPP connection with Vodafone, it is advisable to name it "Vodafone". Also, note that different connections should be given different names. If you have different connections from the same service provider, you can use different but similar names for them, e.g.: "Vodafone1", "Vodafone2" (or something of the like). However, some load balancing solutions require an identical name for different connections. For details, visit the Load Balancing and the Load Balancing for SMPP v3.3 page.

    Enter the information in the respective edit boxes. Remember to enter the phone number in international format: starting with "+". You can check the overridable checkbox to the right of the Telephone number edit box. This ensures that you can replace the phone number specified in the Telephone number edit box with a different one to be displayed as the sender of an outgoing message. You can also replace the number with (alphanumeric) text consisting of a maximum of eleven (11) characters. Therefore, when a message is sent out, e.g. using the Database user, you can specify any different phone number or a name to be displayed as the sender of the message.

    To perform general settings related to sending and receiving SMS messages using this protocol, click the General Settings tab. This will open a panel consisting of the Sending and receiving the Timeout handling and Communication link management section.

    In the first section of the panel you can check any or all of the checkboxes. Which one(s) to check depends on what you wish to use this connection for and whether you need a delivery report. You can choose to use the connection for only sending or only receiving SMS messages (or both sending and receiving), and you can choose to request a delivery report for outgoing messages (Figure 3).

    the general settings tab
    Figure 3 - The General settings tab

    In the Timeout handling section of the tab you can make choices and specifications to handle your connection to the SMS Center and the status of your SMS messages.

    In the Submit timeout edit box you can specify the maximum waiting time for an SMS Center response confirming that your message has been successfully submitted. Successful submission means that the SMS Center has accepted the message for delivery. You can specify the waiting time by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (60 seconds), leave this edit box unchanged.

    You can choose how to consider a message you have sent if there is no response from the SMS Center after the specified length of time. Select one of the three radio buttons.

    • Select Sent to consider a message sent even if there is no response from the SMS Center.
    • Select Not sent to consider a message not sent if there is no response from the SMS Center.

    In the right section of this configuration panel you can manage communication links. At first, in "Windows size" line you can increase the window size, if your SMPP service provider supports windowing. The windowing feature of Ozeki NG - SMS Gateway enables the program to initiate more than one operation before receiving responses. For stop-and-wait flow control, use window size 1. (The maximum window size is 128.) You can set how many protocol messages can be sent out before the SMS Center responds to them. Protocol messages can include SMS messages, keepalive packets, etc. The default value is 1. If you set this number too high, your SMS messages may be discarded, as most GSM service providers try to prevent their networks from being overloaded (Figure 5).

    If you check the checkbox in the Communication link management section, you can make the program send keepalive packets to maintain connection. Proxy servers will drop a connection after a short period of time if there is no activity on it. Keepalive packets are sent during idle periods to keep the connection open.

    In the Keepalive period edit box you can specify the maximum length of idle connection between the Ozeki NG - SMS Gateway and the SMSC. You can specify it by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (30 seconds), leave this edit box unchanged.

    You can also check the Limit speed to checkbox (you can provide the exact time in MPM) if your service provider does not support high speed.

    To configure logging, click the Logging tab in the Configuration panel.

    First, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication and/or log in hexadecimal format. Choosing the second option will make the program produce logfiles containing binary codes representing the communication data. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 4).

    logging options
    Figure 4 - Logging options

    You can also make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 4 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    The Advanced tab contains three checkboxes.

    • The Include checksum field for protocol messages checkbox allows you to make the program use a checksum to check the integrity of an SMS message. By default, this checkbox is checked.
    • Check the Replace STX and ETX to operate with custom protocol implementations checkbox to avoid using the STX character, and to replace the ETX with the CR/LF (newline) character.
    • Check the Don't include the originator address when submitting messages checkbox.

    the advanced tab
    Figure 5 - The Advanced tab

    The Include checksum field for protocol messages checkbox allows you to make the program use a checksum to check the integrity of an SMS message. By default, this checkbox is checked.

    • Check the Replace STX and ETX to CR. CR handling method checkbox.
    • Check the Don't include the originator address when submitting messages checkbox

    The Configuration panel for service provider connections contains a Connect automatically on startup checkbox (in the bottom left-hand corner). If it is checked, Ozeki NG - SMS Gateway will automatically initiate a connection with the SMS Center when the program has started. If this checkbox is not checked, the connection has to be initiated manually.

    To initiate the connection manually, click the Connect link in the panel of the service provider connection (Figure 8).

    links to operation
    Figure 6 - Links to operations

    You can open the panel of a service provider connection by clicking its name in the Service providers panel in the Management Console.

    The panel of a service provider connection consists of three sections.

    • In the upper section you can find the name of the service provider connection (with the name of its protocol in brackets).
    • You can see an icon showing if the service provider connection is connected. If it is not, the icon is marked with an "x".

    To the right of the icon you can find links to perform different operations.

    • Configure: to configure or modify the configuration of an installed service provider connection. Clicking this link will take you back to the Configuration panel.
    • Events: to view the logging of the latest server events related to the service provider connection. Clicking it will bring up the Events panel containing the logging of the latest server events.
    • Connect: to connect the service provider connection with the SMS Center.
    • Disconnect: to disconnect the service provider connection from the SMS Center.
    • Uninstall: to uninstall the service provider connection.

    In the middle section of the panel you can see some of the most important configuration information.

    • The options that have been (re)activated during the configuration are marked with a tick.
    • The options that have not been activated or those that have been deactivated during the configuration are marked with an "x".

    In the lower section of the panel of the service provider connection you can read some information about its protocol.

    HTTP SMS Client Connection

    This chapter provides detailed instructions on how to install and configure the HTTP Client service provider connection for SMS messaging using the Ozeki NG - SMS Gateway software.

    As you can read on the Service Provider Connections page, you need to install and configure one or more service provider connections for SMS messaging using Ozeki NG - SMS Gateway. One of the service provider connections supported by the software is the HTTP Client connection.

    The HTTP Client protocol can be used to connect your PC directly to the SMSC for sending SMS messages over the Internet. For each outgoing message an HTTP GET or HTTP POST request is used. Text and binary SMS message types are supported.

    You can install and configure this connection using the graphical user interface of Ozeki NG - SMS Gateway. To start installing and configuring an HTTP Client connection, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Consoleinterface. (To find out how to open this interface, check out the QuickStart Guide.)

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu.

    After you have clicked one of these, theAdd service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the HTTP Client protocol, click the Install link in the respective entry in the list (Figure 1).

    staring to install the http client connection
    Figure 1 - Starting to install the HTTP Client connection

    When you have installed the HTTP Client protocol, the Configuration panel will show up on the right of the interface. The first tab of the panel is the HTTP settings tab, which consists of a Connection and an Identification section.

    In the Connection section, specify the HTTP Client settings. This information is provided by the SMS service provider when you subscribe to the service (Figure 2).

    the http settings tab
    Figure 2 - The HTTP settings tab

    First you need to specify the Target URL of the HTTP server in the template. This URL can contain certain keywords that will be replaced before the URL is called. The following keywords can be used:

    KeywordDescription
    $originatorThis denotes the sender telephone number.
    $recipientThis denotes the recipient telephone number.
    $messagedataThis denotes the first 1024 characters of the message text.
    $messageidThis is the unique identifier string of the message. This identifier is generated by Ozeki NG - SMS Gateway.

    You can also determine the HTTP method: you can select GET or POST.

    Then, specify the telephone number assigned to this connection and the service provider connection name. To facilitate identification and to avoid confusion, you should name the connection after the GSM service provider. E.g., if you have set up an HTTP Client connection with Vodafone, it is advisable to name it "Vodafone". Also, note that different connections should be given different names. If you have different connections from the same service provider, you can use different but similar names for them, e.g.: "Vodafone1", "Vodafone2" (or something of the like). However, some load balancing solutions require an identical name for different connections. For details, visit the Load Balancing and the Load Balancing for SMPP v3.3 page.

    Enter the information in the respective edit boxes. Remember to enter the phone number in international format: starting with "+". You can check the overridable checkbox to the right of the Telephone number edit box. This ensures that you can replace the phone number specified in the Telephone number edit box with a different one to be displayed as the sender of an outgoing message. You can also replace the number with (alphanumeric) text consisting of a maximum of eleven (11) characters. Therefore, when a message is sent out, e.g. using the Database user, you can specify any different phone number or a name to be displayed as the sender of the message.

    Note that the phone number to be specified in the Telephone number edit box is a mandatory value. If you leave the edit box blank, the sending will be unsuccessful.

    To perform general settings related to sending and receiving SMS messages using the HTTP Client connection, click the General Settings tab (Figure 3).

    the general settings tab
    Figure 3 - The General settings tab


    In the upper section of the panel you can check either or both of the checkboxes. Which one(s) to check depends on what you wish to use this connection for. You can choose to use the connection for only sending or only receiving SMS messages (or both sending and receiving). Note that HTTP Client connections are mainly used for sending messages. However, it is possible to set up HTTP polling to download incoming messages from an HTTP server. In the Polling interval edit box you can specify the polling interval in seconds by entering a positive whole number in numerical format. If you are content with the default specification (2 seconds), leave this edit box unchanged.

    In the lower section of the tab you can make choices and specifications to handle your connection to the SMS Center and the status of your SMS messages.

    In the Submit timeout edit box you can specify the maximum waiting time for an SMS Center response confirming that your message has been successfully submitted. Successful submission means that the SMS Center has accepted the message for delivery. You can specify the waiting time by giving the number of seconds in numerical characters representing any positive whole number. If you are content with the default specification (60 seconds), leave this edit box unchanged.

    You can choose how to consider a message you have sent if there is no response from the SMS Center after the specified length of time. Select one of the three radio buttons.

    • Select Sent to consider a message sent even if there is no response from the SMS Center.
    • Select Not sent to consider a message not sent if there is no response from the SMS Center.
    • Select Retry later to make the program try to send a message later if the SMS Center
    • has not confirmed its status as sent. Then, the message will be placed last in the outgoing message queue and sent out again when it is its turn.

    To configure logging, click the Logging tab in theConfiguration panel.

    You can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 4).

    logging options
    Figure 4 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 4 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    On Response parsing tab you can provide a keyword for response messages on successful delivery and keyword in response on failed delivery (Figure 5).

    By default a message delivery is considered successful if the HTTP server responds with an HTTP 200 OK. Some providers return HTTP 200 OK on all submissions and put the status code, that indicates delivery success into the HTTP message body. If this is the case, specify a keyword to search for in the message body.

    If there is no keyword that indicates successful delivery, you can specify a keyword that indicates failed delivery. If this keyword is specified, Ozeki NG will consider a message delivered to the network only if this keyword is not present in the HTTP message body returned by the HTTP server.

    response parsing tab
    Figure 5 - Response parsing tab

    The Info tab enlists the following keywords that can be used in the HTTP template. These keywords will be replaced to the appropriate values prior to the HTTP request is made. The meaning of these values are explained on the following webpage: https://ozekisms.com/p_2353-variables-for-http-client-service-provider-connection.html.

    info tab
    Figure 6 - Info tab

    The Configuration panel for service provider connections contains a Connect automatically on startup checkbox (in the bottom left-hand corner). If it is checked, Ozeki NG - SMS Gateway will automatically initiate a connection with the SMS Center when the program has started. If this checkbox is not checked, the connection has to be initiated manually.

    To initiate the connection manually, click the Connect link in the panel of the service provider connection (Figure 7).

    links to operations
    Figure 7 - Links to operations

    You can open the panel of a service provider connection by clicking its name in the Service providers panel in the Management Console.

    The panel of a service provider connection consists of three sections.

    • In the upper section you can find the name of the service provider connection (with the name of its protocol in brackets).
    • You can see an icon showing if the service provider connection is connected. If it is not, the icon is marked with an "x".

    To the right of the icon you can find links to perform different operations.

    • Configure: to configure or modify the configuration of an installed service provider connection. Clicking this link will take you back to the Configuration panel.
    • Events: to view the logging of the latest server events related to the service provider connection. Clicking it will bring up the Events panel containing the logging of the latest server events.
    • Connect: to connect the service provider connection with the SMS Center.
    • Disconnect: to disconnect the service provider connection from the SMS Center.
    • Uninstall: to uninstall the service provider connection.

    In the middle section of the panel you can see some of the most important configuration information.

    • The options that have been (re)activated during the configuration are marked with a tick.
    • The options that have not been activated or those that have been deactivated during the configuration are marked with an "x".

    In the lower section of the panel of the service provider connection you can read some information about its protocol.

    Variables for HTTP Client Service Provider Connection

    The following table lists the variables you can use in the HTTP requests sent to HTTP Client service provider connections.

    messageidA unique string for the message.
    messagetypeThe message type. For more information please take a look at the SMS Message Types page.
    recipientThe recipient of the message
    originatorThe sender of the message
    messagedataThe message text (or message data for binary messages)
    udHEXFor text messages the message text encoded as a hexadecimal string. For binary messages the binary data encoded as a hexadecimal string.
    udlUser data length (integer)
    udhHEXThe user data header (UDH) as a hexadecimal string.
    udhudHEXThe user data header (UDH) followed by the user data (UD) as a hexadecimal string.
    dcsHEXThe GSM data coding scheme (DCS) in hexadecimal format (possible values: 00-FF)
    dcsDECThe GSM data coding scheme (DCS) in decimal format (possible values: 0-255)
    pidHEXThe GSM protocol ID (PID) in hexadecimal format (possible values: 00-FF)
    pidDECThe GSM protocol ID (PID) in decimal format (possible values: 0-255)
    tpdrreqINTDelivery report request indication (possible values: 0 - no delivery report is requested, 1 - delivery report is requested)
    tpdrreqBOOLDelivery report request indication (possible values: false - no delivery report is requested, true - delivery report is requested)
    tpmmsINTMore messages to send indication (possible values: 0 - no more messages to follow, 1 - more messages to follow)
    tpmmsBOOLMore messages to send indication (possible values: false - no more messages to follow, true - more messages to follow)
    tprpINTReply path indication (possible values: 0 - no reply path, 1 - set reply path)
    tprpBOOLReply path indication (possible values: false - no reply path, true - set reply path)
    vpabsAbsolute validity period. (Time format: YYYY-MM-DD hh:mm:ss)
    vprelHEXRelative validity period as defined in the GSM standard (possible values: 00-FF)
    vprelDECRelative validity period as defined in the GSM standard (possible values: 00-255)
    fdtabsAbsolute first delivery time. (Time format: YYYY-MM-DD hh:mm:ss)
    fdtrelHEXRelative first delivery time as defined in the GSM standard (possible values: 00-FF)
    fdtrelDECRelative first delivery time as defined in the GSM standard (possible values: 00-255)

    HTTP Server Connection

    This chapter provides detailed instructions on how to install and configure the HTTP Server connection for SMS messaging using the Ozeki NG - SMS Gateway software.

    As you can read on the Service Provider Connections page, you need to install and configure one or more service provider connections for SMS messaging using Ozeki NG - SMS Gateway. One of the service provider connections supported by the software is the HTTP Server connection.

    The HTTP Server protocol makes it possible for service providers to pass incoming messages to your service using an HTTP request for each incoming SMS message and they optionally accept a reply message in the HTTP response. This technology is often used by premium-rated SMS services. This connection option can also be used as a "Virtual phone" for software development purposes.

    You can install and configure the HTTP Server connection using the graphical user interface of Ozeki NG - SMS Gateway. To start installing and configuring an HTTP Server connection, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Console interface. (To find out how to open this interface, check out the QuickStart Guide.)

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu.

    After you have clicked one of these, the Add service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the HTTP Server protocol, click the Install link in the respective entry in the list (Figure 1).

    starting to install the http server connection
    Figure 1 - Starting to install the HTTP Server connection

    When you have installed the HTTP Server protocol, the Configuration panel will show up on the right of the interface. The first tab of the panel is the HTTP settings tab, which consists of a Connection and an Identification section.

    In the Connection section, specify the HTTP Server settings. This information is provided by the SMS service provider when you subscribe to the service (Figure 2).

    the http settings tab
    Figure 2 - The HTTP settings tab

    In the Base URL template, specify the base URL.

    In the Identification section, specify the telephone number assigned to this connection and the service provider connection name. To facilitate identification and to avoid confusion, you should name the connection after the GSM service provider. E.g., if you have set up an HTTP Server connection with Vodafone, it is advisable to name it "Vodafone". Also, note that different connections should be given different names. If you have different connections from the same service provider, you can use different but similar names for them, e.g.: "Vodafone1", "Vodafone2" (or something of the like). However, some load balancing solutions require an identical name for different connections. For details, visit the Load Balancing and the Load Balancing for SMPP v3.3 page.

    Enter the information in the respective edit boxes. Remember to enter the phone number in international format: starting with "+". You can check the overridable checkbox to the right of the Telephone number edit box. This ensures that you can replace the phone number specified in the Telephone number edit box with a different one to be displayed as the sender of an outgoing message. You can also replace the number with (alphanumeric) text consisting of a maximum of eleven (11) characters. Therefore, when a message is sent out, e.g. using the Database user, you can specify any different phone number or a name to be displayed as the sender of the message.

    Note that the phone number to be specified in the Telephone number edit box is a mandatory value. If you leave the edit box blank, the sending will be unsuccessful.

    To configure logging, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 3).

    logging options
    Figure 3 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in theLog directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 3 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    The Configuration panel for service provider connections contains a Connect automatically on startup checkbox (in the bottom left-hand corner). If it is checked, Ozeki NG - SMS Gateway will automatically initiate a connection with the SMS Center when the program has started. If this checkbox is not checked, the connection has to be initiated manually.

    To initiate the connection manually, click the Connect link in the panel of the service provider connection (Figure 4).

    links to operations
    Figure 4 - Links to operations

    You can open the panel of a service provider connection by clicking its name in the Service providers panel in the Management Console.

    The panel of a service provider connection consists of three sections.

    • In the upper section you can find the name of the service provider connection (with the name of its protocol in brackets).
    • You can see an icon showing if the service provider connection is connected. If it is not, the icon is marked with an "x"

    To the right of the icon you can find links to perform different operations.

    • Configure: to configure or modify the configuration of an installed service provider connection. Clicking this link will take you back to the Configuration panel.
    • Events: to view the logging of the latest server events related to the service provider connection. Clicking it will bring up the Events panel containing the logging of the latest server events.
    • Connect: to connect the service provider connection with the SMS Center.
    • Disconnect: to disconnect the service provider connection from the SMS Center.
    • Uninstall: to uninstall the service provider connection.

    In the middle section of the panel you can see some of the most important configuration information.

    • The options that have been (re)activated during the configuration are marked with a tick.
    • The options that have not been activated or those that have been deactivated during the configuration are marked with an "x".

    In the lower section of the panel of the service provider connection you can read some information about its protocol.

    HTTPS server configuration

    The HTTP server connection option allows you to receive incoming SMS messages or SMS delivery reports with http requests through the https protocol. To configure this option you need to set a base URL for the listening webserver with the https prefix (Figure 1) and you must configure a server certificate.

    configure a https prefix
    Figure 1 - Configure a https prefix

    You can configure Server Certificates and other listener options by using HttpCfg.exe on Windows XP and Windows 2003 or netsh tool on Windows Vista. The httpcfg.exe executable is shipped with Windows Server 2003. For Windows XP SP2 it can be downloaded from "Windows XP SP2 Support Tools for Advanced Users".

    The following webpage gives information on how you can configure a server certificate for a port: http://msdn.microsoft.com/en-us/library/ms733791.aspx.

    How to: Configure a Port with an SSL certificate

    We suggest you to read the original article at:

    URL: http://msdn.microsoft.com/en-us/library/ms733791.aspx

    To configure a port, the tool you use depends on the operating system that is running on your machine.

    If you are running Windows Server 2003 or Windows XP, use the HttpCfg.exe tool. With Windows Server 2003 this tool is installed. With Windows XP, you can download the tool at

    Windows XP Service Pack 2 Support Tools. For more information, see Httpcfg Overview. The Windows Support Tools documentation explains the syntax for the Httpcfg.exe tool.

    If you are running Windows Vista, use the Netsh.exe tool that is already installed.

    This topic describes how to accomplish several procedures:

    • Determining a computer's current port configuration.
    • Getting a certificate's thumbprint (necessary for the following two procedures).
    • Binding an SSL certificate to a port configuration.
    • Binding an SSL certificate to a port configuration and supporting client certificates.
    • Deleting an SSL certificate from a port number.

    Note that modifying certificates stored on the computer requires administrative privileges.

    To determine how ports are configured

    1. In Windows Server 2003 or Windows XP, use the HttpCfg.exe tool to view the current port configuration, using the query and ssl switches, as shown in the following example.

      httpcfg query ssl
    2. In Windows Vista, use the Netsh.exe tool to view the current port configuration, as shown in the following example.

      netsh http show sslcert

    To get a certificate's thumbprint

    1. Use the Certificates MMC snap-in to find an X.509 certificate that has an intended purpose of client authentication. For more information, see How to: View Certificates with the MMC Snap-in.

    2. Access the certificate's thumbprint. For more information, see How to: Retrieve the Thumbprint of a Certificate.

    3. Copy the thumbprint of the certificate into a text editor, such as Notepad.

    4. Remove all spaces between the hexadecimal characters. One way to accomplish this is to use the text editor's find-and-replace feature and replace each space with a null character.

    To bind an SSL certificate to a port number

    1. In Windows Server 2003 or Windows XP, use the HttpCfg.exe tool in "set" mode on the Secure Sockets Layer (SSL) store to bind the certificate to a port number. The tool uses the thumbprint to identify the certificate, as shown in the following example.

      httpcfg set ssl -i 0.0.0.0:8012 -h 0000000000003ed9cd0c315bbb6dc1c08da5e6
      • The -i switch has the syntax of IP:port and instructs the tool to set the certificate to port 8012 of the computer. Optionally, the four zeroes that precede the number can also be replaced by the actual IP address of the computer.
      • The -h switch specifies the thumbprint of the certificate.
    2. In Windows Vista, use the Netsh.exe tool, as shown in the following example.

      netsh http add sslcert ipport=0.0.0.0:8000 certhash=0000000000003ed9cd0c315bbb6dc1c08da5e6 appid={00112233-4455-6677-8899-AABBCCDDEEFF}
      • The certhash parameter specifies the thumbprint of the certificate.
      • The ipportparameter specifies the IP address and port, and functions just like the -i switch of the Httpcfg.exe tool described.
      • The appid parameter is a GUID that can be used to identify the owning application.

    To bind an SSL certificate to a port number and support client certificates

    1. In Windows Server 2003 or Windows XP, to support clients that authenticate with X.509 certificates at the transport layer, follow the preceding procedure but pass an additional command-line parameter to HttpCfg.exe, as shown in the following example.

      httpcfg set ssl -i 0.0.0.0:8012 -h 0000000000003ed9cd0c315bbb6dc1c08da5e6 -f 2

      The -f switch has the syntax of n where n is a number between 1 and 7. A value of 2, as shown in the preceding example, enables client certificates at the transport layer. A value of 3 enables client certificates and maps those certificates to a Windows account. See HttpCfg.exe Help for the behavior of other values.

    2. In Windows Vista, to support clients that authenticate with X.509 certificates at the transport layer, follow the preceding procedure, but with an additional parameter, as shown in the following example.

      netsh http add sslcert ipport=0.0.0.0:8000 certhash=0000000000003ed9cd0c315bbb6dc1c08da5e6 appid={00112233-4455-6677-8899-AABBCCDDEEFF} clientcertnegotiation=enable

    To delete an SSL certificate from a port number

    1. Use the HttpCfg.exe or Netsh.exe tool to see the ports and thumbprints of all bindings on the computer. To print the information to disk, use the redirection character ">", as shown in the following example.

      httpcfg query ssl>myMachinePorts.txt
    2. In Windows Server 2003 or Windows XP, use the HttpCfg.exe tool with the delete and ssl keywords. Use the -i switch to specify the IP:port number, and the -h switch to specify the thumbprint.

      httpcfg delete ssl -i 0.0.0.0:8005 -h 0000000000003ed9cd0c315bbb6dc1c08da5e6
    3. In Windows Vista, use the Netsh.exe tool, as shown in the following example.

      Netsh http delete sslcert ipport=0.0.0.0:8005

    How to: View Certificates with the MMC Snap-in

    A common type of credential is the X.509 certificate. When creating secure services or clients, you can specify a certificate be used as the client or service credential by using methods such as the SetCertificate method. The method requires various parameters, such as the store where the certificate is stored and a value to use when searching for the certificate. The following procedure demonstrates how to examine the stores on a computer to find an appropriate certificate. For an example of finding the certificate thumbprint, see How to: Retrieve the Thumbprint of a Certificate.

    To view certificates in the MMC snap-in

    Open a Command Prompt window.

    Type mmc and press the ENTER key. Note that to view certificates in the local machine store, you must be in the Administrator role.

    On the File menu, click Add/Remove Snap In.

    Click Add.

    In the Add Standalone Snap-in dialog box, select Certificates.

    Click Add.

    In the Certificates snap-in dialog box, select Computer account and click Next. Optionally, you can select My User account or Service account. If you are not an administrator of the computer, you can manage certificates only for your user account.

    In the Select Computer dialog box, click Finish.

    In the Add Standalone Snap-in dialog box, click Close.

    On the Add/Remove Snap-in dialog box, click OK.

    In the Console Root window, click Certificates (Local Computer) to view the certificate stores for the computer.

    Optional. To view certificates for your account, repeat steps 3 to 6. In step 7, instead of selecting Computer account, click My User account and repeat steps 8 to 10.

    Optional. On the File menu, click Save or Save As. Save the console file for later reuse.

    Viewing Certificates with Internet Explorer

    You can also view, export, import, and delete certificates by using Internet Explorer.

    To view certificates with Internet Explorer In Internet Explorer, click Tools, then click Internet Options to display the Internet Options dialog box.

    Click the Content tab.

    Under Certificates, click Certificates.

    To view details of any certificate

    How to: Retrieve the Thumbprint of a Certificate

    When writing a Windows Communication Foundation (WCF) application that uses an X.509 certificate for authentication, it is often necessary to specify claims found in the certificate. For example, you must supply a thumbprint claim when using the FindByThumbprint enumeration in the SetCertificate method. Finding the claim value requires two steps. First, open the Microsoft Management Console (MMC) snap-in for certificates. (See How to: View Certificates with the MMC Snap-in.) Second, as described here, find an appropriate certificate and copy its thumbprint (or other claim values).

    If you are using a certificate for service authentication, it is important to note the value of the Issued To column (the first column in the console). When using Secure Sockets Layer (SSL) as a transport security, one of the first checks done is to compare the base address Uniform Resource Identifier (URI) of a service to the Issued To value. The values must match or the authentication process is halted.

    You can also use the Makecert.exe tool from the .NET Framework SDK to create temporary certificates for use only during development. By default, however, such a certificate is not issued by a certificate authority, and is unusable for production purposes. For more information, see How to: Create Temporary Certificates for Use During Development.

    To retrieve a certificate's thumbprint

    Open the Microsoft Management Console (MMC) snap-in for certificates. (See How to: View Certificates with the MMC Snap-in.)

    In the Console Root window's left pane, click Certificates (Local Computer).

    Click the Personal folder to expand it.

    Click the Certificates folder to expand it.

    In the list of certificates, note the Intended Purposes heading. Find a certificate that lists Client Authentication as an intended purpose.

    Double-click the certificate.

    In the Certificate dialog box, click the Details tab.

    Scroll through the list of fields and click Thumbprint.

    Copy the hexadecimal characters from the box. If this thumbprint is used in code for the X509FindType, remove the spaces between the hexadecimal numbers. For example, the thumbprint "a9 09 50 2d d8 2a e4 14 33 e6 f8 38 86 b0 0d 42 77 a3 2a 7b" should be specified as "a909502dd82ae41433e6f83886b00d4277a32a7b" in code.

    Send MMS over MM7 connection

    Ozeki NG SMS Gateway can be used to send MMS messages to MMS service providers over the MM7 protocol. In this article you can read about this solution and you will find a helpful configuration guide with screenshots to setup your system.

    Introduction

    MM7 connection can be used to send and receive multimedia messages between computers and MMS-enabled mobile phones. MM7 is an interface between Value Added Service Provider (VASP) and Multimedia Messaging Service Center (MMSC). It is specified by 3GPP and it is based on Web Services. The protocol communicates through HTTP and uses SOAP/MIME/XML message format. Today practically all MMSCs have implemented the MM7 interface. By using MM7 protocol, service providers can send and receive MMS messages, and can receive and read delivery reports.

    With the use of MMS (Multimedia Messaging Service) in your corporate communication you can extend the functions of SMS text messages as MMS messages can include multimedia content. With a powerful and stable SMS gateway software you can send and receive MMS messages to and from mobile phones. To achieve this function you can use Ozeki NG SMS Gateway software.

    To be able to send MMS messages using Ozeki NG SMS Gateway, you need to connect your gateway software to the MMS center of one or more service providers. You can do this in the following way: If you wish to increase speed, reliability and performance you can connect directly to the MMSC over the Internet. In this case, you can use MM7 protocol to connect your gateway. To implement this solution you need a contract with a service provider. Therefore the service provider will provide you the necessary information to be able to connect to their MMSC.

    Configuration in Ozeki NG SMS Gateway

    In Ozeki NG SMS Gateway the messages are submitted using the MM7 protocol which allows you to connect to an HTTP or HTTPS webservice provided by an internet based MMS service provider. The service provider will provide the parameters that are needed during the configuration such as MMS Post URL, VAS ID, VASP ID (Value Added Service Provider).

    To configure your gateway please follow the steps below.

    First, start Ozeki NG SMS Gateway software and login with your username and password. On the left hand side of the interface of Ozeki NG SMS Gateway, click on "Add service provider" (Figure 1).

    add a service provider
    Figure 1 - Add service provider

    Then select "MM7 connection" from IP MMS connections. Click on "Install" next to it (Figure 2).

    install menu
    Figure 2 - Install

    In "Configuration" pane select "General" tab. In "URL parameters" section you need to specify the connection parameters for the MM7 submission of the MMS messages. The parameters are provided by your service provider after you have signed a contract with them. These information are: MMS Post URL, MMS Receive URL, VAS ID, VAS PID.

    You also need to specify the MM7 version information such as 3GPP MMS version and MM7 schema in "Protocol version" section. These parameters are also provided by your service provider.

    Protocol paramters like service code and password can also be entered in this tab (Figure 3).

    general window
    Figure 3 - General

    In "Connection" tab you can set the values for "HTTP authentication". In "Client certificate" you can check "Use client certificate for HTTPS authentication" checkbox and you can also provide the path for X509 Certificate file (Figure 4).

    connection tab
    Figure 4 - Connection tab

    Next switch to "Advanced" tab. In "Identification" section you can specify the sender ID with an e-mail address or with a phone number. Also type in the provider's name. In "Custom header content" section you can add some XML tags to the XML header of the sent data (Figure 5).

    advanced tab
    Figure 5 - Advanced

    In "Logging" tab you do not need to do any configuration as there are default settings. If they are suitable for you just click on "OK". These default settings are the follows: "Log sent and received messages in human readable format" option is enabled in the "Logging" section. The "Log directory", the "Maximum log file size", and "Number of rotated files" are also provided by default in "Log file settings" section (Figure 6). Click on "OK" to finish configuration.

    logging tab
    Figure 6 - Logging

    If you click on "Management" you will see the created MM7 connection under "Service providers" on the left side (Figure 7).

    created connection
    Figure 7 - Created connection

    Testing the connection

    Now to compose an MMS message, click on "Compose" (Figure 8).

    compose a message
    Figure 8 - Compose a message


    Figure 8 - Compose a message

    Then select "Multimedia Message (MMS) from message types(Figure 9).

    select multimedia message
    Figure 9 - Select Multimedia Message


    Then you can start compose your message. To send your message you need to provide the message type, and a recipient phone number. After this specify your subject and compose your text message. Finally, browse for an attachment and click on "Send" (Figure 10).

    send your message
    Figure 10 - Send your message

    Conclusion

    To summarize the above mentioned up, you can send MMS messages with Ozeki NG SMS Gateway over MM7 connection from computers to mobile phones. To achieve this function you can easily configure your gateway in a few steps. With this solution you will gain a stable, reliable and well-functioning system which you will be able to save time and money with.

    Read this article on how you can receive MMS messages over MM7 protocol with Ozeki NG SMS Gateway

    If you have not downloaded Ozeki NG SMS Gateway yet, please go to the download page where you will find all the necessary download information.

    Receive MMS message via MM7 protocol

    Ozeki NG SMS Gateway makes it possible to send MMS messages to MMS service providers over the MM7 protocol. It connects to the MMS center of the mobile service providers over the Internet (IP SMS connection). In this article you can read about this solution and you will find a configuration guide with screenshots to help you setup your MMS system.

    Introduction

    MM7 connection is used to send and receive multimedia messages (MMS) between computers and MMS-enabled mobile phones. MM7 is an interface between Value Added Service Provider (VASP) and Multimedia Messaging Service Center (MMSC). It is specified by 3GPP and it is based on Web Services. The protocol communicates through an MM7 connection and uses SOAP/MIME/XML message format. Today practically all MMSCs have implemented the MM7 interface. By using MM7 protocol, service providers can send and receive MMS messages, and can receive and read delivery reports.

    With the implementation of this solution you can greatly improve your corporate communication and extend the functions of SMS text messages. As MMS messages can include multimedia content they make various and efficient communication possible. In this way they are perfect means of marketing, promotions, but even of information flow. With a powerful and stable SMS gateway software, such as Ozeki NG SMS Gateway, you can easily implement this solution in your corporate IT network.

    To be able to send MMS messages using Ozeki NG SMS Gateway, you need to connect your gateway software to the MMS center of one or more service providers. You can do it in the following way: If you wish to increase speed, reliability and performance you can connect directly to the MMSC over the Internet (IP SMS connection). In this case, you can use MM7 protocol to connect your gateway. To implement this solution you need a contract with a service provider. Therefore the service provider will provide you the necessary information to be able to connect to their MMSC.

    How this solution works

    If you decide to implement this solution to receive MMS messages over MM7 protocol, your MMS system will work as follows: First you need to install an MM7 service provider in Ozeki NG SMS Gateway. This will handle incoming MMS messages. On the basis of the unique ID (GUID) of incoming messages, the user will create a directory in OzekiNG - SMS Gateway\MMS directory. The content of the incoming MMS messages will be saved to this created directory. The incoming messages also will appear in the Inbox folder of the user but only in XML format. You can learn more about this XML format on the following page: XML format.

    Configuration in Ozeki NG SMS Gateway

    In Ozeki NG SMS Gateway the messages are submitted using the MM7 protocol which allows you to connect to an MMS service provider. The service provider will provide the parameters that are needed during the configuration such as the MMS Post URL.

    To configure your gateway please follow the steps below.

    First log into Ozeki NG SMS Gateway with your username and password. After you login, click on Add service provider (Figure 1).

    add new service provider
    Figure 1 - Add new service provider

    Select MM7 Connection and click on Install next to it (Figure 2).

    select the mm7 connection
    Figure 2 - Select MM7 connection

    In Configuration pane select General tab. Now you need to specify the necessary information to connect to the service provider's MMSC. These information will be provided by your service provider after you have signed a contract with them. These information are: MMS Post URL, MMS receive URL, VAS ID, VAS PID (Figure 3).

    specfiy parameters
    Figure 3 - Specify parameters

    If you switch to Advanced tab. Here you can specify the MM7 version information like 3GPP MMS version and MM7 schema in Protocol version section. You can also get these parameters from your service provider. The Sender IDand the Provider name can be defined at Identification section. Sender ID can be an e-mail address or a phone number (Figure 4).

    the mm7 version
    Figure 4 - MM7 version information

    In Logging tab you can leave the default settings unchanged and click on OK if no changes are required (Figure 5).

    logging tab
    Figure 5 - Logging tab

    The received MMS messages can be viewed in the Inbox folder of the given user (Figure 6).

    users inbox
    Figure 6 - User's Inbox

    Conclusion

    To summarize the above mentioned up, you can receive MMS messages with Ozeki NG SMS Gateway over MM7 connection. To achieve this function you can easily configure your gateway in a few steps. In this way you can improve the efficiency of your corporate communication to a great extent. With the implementation of this solution you will gain a stable, secure and well-functioning system with the highest quality which will save you valuable time and money.

    Read this article on how you can send MMS messages over MM7 protocol with Ozeki NG SMS Gateway

    If you have not downloaded Ozeki NG SMS Gateway yet, please go to the download page where you will find all the necessary download information.

    How to allow incoming connections

    On this page you can find detailed information on how you can allow incoming connections at Windows Firewall. This is necessary to be able to receive MMS over MM7 protocol. Please follow the steps of this article to be able to use this solution properly.

    To allow incoming connections, first you need to go to Control Panel at Start menu and click on Windows Firewall icon (Figure 1).

    the control panel menu
    Figure 1 - Control Panel

    At Windows Firewall, select "Advanced Settings" (Figure 2).

    Figure 2 - Windows Firewall

    In the next page select "Inbound Rules"(Figure 3).

    advanced settings page
    Figure 3 - Advanced Settings page

    Now click to "New Rule..." button at right(Figure 4).

    the inbound rules page
    Figure 4 - Inbound Rules page

    In the next dialog box select the "Port" radio button and then click to "Next" (Figure 5).

    select the type of the rule
    Figure 5 - Select the type of the rule

    At the next page type in the "port number" (9400) what you want to enable and click to "Next" (Figure 6).

    type in the port numbers
    Figure 6 - Type in the port numbers

    Leave the radio button on "Allow the connection" and click to "Next" (Figure 7).

    choose the action
    Figure 7 - Choose the action

    Leave all pipes in the boxes and click "Next" (Figure 8).

    select the applying of this rule
    Figure 8 - Select the applying of this Rule

    In the last page "Name the Rule" and click the "Finish" button (Figure 9).

    name the rule
    Figure 9 - Name the Rule

    Finaly you can see your new rule in the list is the rules (Figure 10).

    the list of rules
    Figure 10 - The list of the rules

    How to send/receive MMS messages via EAIF

    This article provides you detailed information on how you can send/receive MMS messages via EAIF protocol with the use of Ozeki NG SMS Gateway. MMS messages are delivered over HTTP protocol to the MMSC and to users. This solution allows easy connection to the MMSC for service providers and ensures value-added services for users.

    Introduction

    EAIF (External Application Interface) is an interface that makes easy and efficient MMS sending/receiving possible in a way which satisfies the needs of service providers and subscribers. It is due to the fact that service providers are able to connect to the MMS center easily via EAIF. Furthermore, end-users can enjoy high-quality services provided over EAIF.

    EAIF is based on OMA (Open Mobile Alliance) standards. It uses PDUs and HTTP extension headers to ensure that all information is conveyed. This solution allows to send/receive MMS messages from your PC to mobile devices and vice versa. In MMS (Multimedia Messages) you can transmit information in various formats. You can send plain text messages, images (JPEG, GIF, etc), Audio clips, Video, vCalendar, vCard, etc. In this way you can further extend and improve corporate communication. To achieve this function you need to download and install Ozeki NG SMS Gateway.

    To be able to send/receive MMS messages via EAIF with Ozeki NG SMS Gateway first you need to connect your SMS gateway to the MMS center of one of the service providers. You can connect directly to the MMS center of service provider over the Internet (IP SMS connection). This IP SMS connection will provide you a reliable and stable performance via EAIF. Please note that you will need a contract with the selected mobile service provider to be able to connect to its MMSC. After the agreement the service provider will provide you the necessary information and parameters needed to the connection.

    Configure Ozeki NG SMS Gateway

    Before you start to configure Ozeki NG SMS Gateway, you need some parameters from your service provider such as "Nokia EAIF server address".

    To configure Ozeki NG SMS Gateway, first start the software and login with your username and password. On the left side of the user interface click on "Add service provider" (Figure 1).

    Figure 1 - Add service provider

    A list of available service provider connections appears. Select "EAIF Connection" in the list and click on "Install" next to it (Figure 2).

    install eaif connection
    Figure 2 - Install EAIF connection

    In Configuration pane select "General" tab. On this tab you need to specify connection parameters for the EAIF submission of MMS messages. These parameters are provided by your service provider (Figure 3). Specify the following parameters:

    • "Listening address": you will be able to receive MMS messages via this port
    • "Nokia EAIF server address": MMS messages will be sent out to this address
    • "HTTP username" and "HTTP password": optional. You only need to provide these parameters if you send MMS messages over HTTPs
    • "Sender ID": it can be a telephone number.

    the general tab
    Figure 3 - General tab

    In "Logging" tab you can leave the settings unchanged if you content with the default ones. Click on "OK" (Figure 4).

    the logging tab
    Figure 4 - Logging tab

    Compose MMS message

    Now you can start to send MMS messages from Ozeki NG SMS Gateway. To do so you just need to click on "Compose" icon in the toolbar (Figure 5).

    compose icon
    Figure 5 - Compose icon

    Select "Multimedia Message (MMS)" from "Message types" (Figure 6).

    select mms message
    Figure 6 - Select MMS message

    Then you can start compose your message. To send your message you need to provide the message type, and a recipient phone number. After this specify your subject and compose your text message. Finally, browse for an attachment and click on "Send" (Figure 9).

    send an mms
    Figure 7 - Send MMS

    If you have not downloaded Ozeki NG SMS Gateway yet, please go to the download page where you will find all the necessary download information.

    SAG ParlayX SOAP/XML Service Provider Connection

    In this page you can find instructions about how to install and configure the SAG ParlayX SOAP/XML service provider connection for SMS messaging using the Ozeki NG SMS Gateway software.

    The DataSync interface of the SAG ParlayX protocol is implemented in a third party application, which can be downloaded on the link below.

    Download:OzekiSagParlayXDataSyncSender.zip

    SAG ParlayX SOAP/XML Service Provider Connection uses ParlayX Web Services

    to connect to the SMSC of your choice. You can send and receive incoming SMS messages or notifications with this service provider.

    You can install the SAG ParlayX SOAP/XML Service Provider connection through the graphical user interface of Ozeki NG SMS Gateway. First, click on the Add button in the top right-hand corner of the Service provider's panel on the Management page.

    add new service provider
    Figure 1 - Add new Service Provider connection

    On the next page you can find the SAG ParlayX SOAP/XML Service Provider connection in the IP SMS connections (SMS) section. Click on the Install button to create the new connection.

    select sag parlayx soap/xml service provider
    Figure 2 - Select SAG ParlayX SOAP/XML Service Provider connection


    On the following page you can find the configuration form of the connection.

    Under General tab, you need to specify the connection parameters for message submission that are correlating with your connection.

    You need to specify the following URLs properly for your service provider:

    • SmsNotificationManager URL
    • SendSms URL
    • NotifySmsDeliveryReceipt URL
    • NotifySmsReception URL

    general settings of the sag parlayx soap/xml connection
    Figure 3 - General settings of the SAG ParlayX SOAP/XML connection


    The next tab is the Parameters tab, which consist of three parts. You can configure Reference Parameters, Charging Information and Additional Parameters.

    In the Reference Parameters section you can specify whether to append a receipt request to outgoing messages. Enable the checkbox if you would like to Send Receipt Request.

    In the Charging Information section you can specify the following charging parametersused in outgoing messages:

    • Description
    • Amount
    • Currency
    • Code

    If you would like to use Charging Information, enable the Append Charging Information to outgoing messages checkbox.

    In the Additional Parameters section you can provide the Sender Name. If you want to Override linkid whenever a new message arrives from the SMSC, enable the checkbox, which belongs to this settings.

    parameters tab of the sag parlayx Ssoap/xml connection
    Figure 4 - Parameters tab of the SAG ParlayX SOAP/XML connection


    Under the Additional Parameters tab you can add some parameters used by the StartSmsNotification request, such as Correlator, Criteria and Sms Service Activation Number.

    In the next section of this tab you can specify the Credentials associated with your account at the provider. Most of these settings are present in the SOAP Header of the request. These are the SP ID, SP Password, Service ID, Service Subscription Address and Payment Address.

    additional parameters tab  of the sag parlayx soap/xml connections
    Figure 5 - Additional Parameters tab of the SAG ParlayX SOAP/XML connection

    In the Logging tab you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the second option the program produces logfiles containing binary codes representing the communication data.

    In the Log file settings section of the tab, you can give the Log directory, the maximum log file size and the number of rotated logfiles. Log rotation saves disk space, as it ensures that olderlogfiles will be automatically deleted from the log directory. In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created.

    logging configuration
    Figure 6 - Logging configuration


    If you have any other questions, please contact us at info@ozekisms.com.

    TDC CPS Connection

    This chapter provides you detailed information on how to install and configure TDC CPS Connection for SMS messaging in Ozeki NG SMS Gateway software.

    As the service provider connections page suggests you need to install one or more service provider connections in Ozeki NG SMS Gateway to be able to send out SMS messages over the Internet. One of these service provider connections is TDC CPS Connection. Please follow this page to learn its installation and configuration process.

    TDC has introduced a new platform that transforms how TDC manages third party content and service providers. This platform is also ensured for SMS messaging.

    In this way a new service provider connection (TDC CPS Connection) has been developed in Ozeki NG SMS Gateway software that allows to connect to the webservice of TDC. In case of sending SMS messages, Ozeki NG SMS Gateway connects to the webservice of TDC. While, in case of receiving SMS messages, the built-in webservice of Ozeki NG SMS Gateway is called by TDC.

    Figure 1 demonstrates how this connection works in practice. Ozeki NG SMS Gateway software connects to the webservice of TDC and sends out SMS messages over this connection.

    how ozeki ng sms gateway connects to a tdc webserver
    Figure 1 - Ozeki NG SMS Gateway connects to TDC webservice

    Configuration

    Step 1. Install TDC CPS Connection

    Log into Ozeki NG SMS Gateway with your username and password. Click on Add new service provider connection(Figure 2).

    add new service provider connection
    Figure 2 - Add new service provider connection

    Select TDC PCS Connection from the list and click on install next to it (Figure 3).

    install tdc cps connection
    Figure 3 - Install TDC CPS connection

    Step 2. Configure TDC CPS Connection

    Now you need to specify the following URL parameters on General tab to configure the installed TDC CPS Connection (Figure 4):

    • Username: Username received from TDC
    • Password: Password received from TDC

    In order to be registered at TDC you need to provide a Local Service Address and an Activation Number.

    • Local Service Address: It is the address of the computer on which Ozeki NG SMS Gateway has been installed. The service will be registered at TDC with this address and Ozeki NG SMS Gateway opens a webservice at this address.
    • Activation Number: It is the phone number that is registered at TDC
    • Polling period: In this field you can specify the time interval in minutes for checking lost messages or reports

    the general tab
    Figure 4 - General tab

    How to send pager messages via SNPP using Ozeki NG SMS Gateway

    This guide provides detailed information on how to install and configure SNPP connection in Ozeki NG SMS Gateway. The Simple Network Paging Protocol (SNPP) allows you to send messages to pagers over the Internet.

    What is a pager

    A pager (or beeper) is a device designed for short messages. A pager is a one-way telecommunication device, meaning that it can only receive short messages. This message can hold a few digits (typically a phone number). Usually, the user of a pager is requested to call this phone number.

    Pagers are still in use today in places where mobile phones typically cannot reach users, and also in places where the operation of the radio transmitters contained in mobile phones is problematic or prohibited (e.g. in a hospital complex).

    What is SNPP protocol and how does it work?

    Simple Network Paging Protocol (in short, SNPP) is a protocol that allows a pager to receive messages over the Internet. Most major paging providers support this protocol. SNPP also serves as an alternative method to paging modems that are used by telecommunications services.

    SNPP is a simple protocol that sends out a page by using only well-documented commands via TCP/IP. In order to connect to an SNPP server, a telnet client and the address of the SNPP server are required. SNPP servers have a standard port, it is port 444.

    For sending text messages via SNPP the follows are required: the port settings of the paging carrier and the pin or ID of the pager. The pin and ID is often the numeric pager number but not always. Maximum message length can be carrier-dependent.

    SNPP is a fairly new protocol so if you are in the need of paging software that supports SNPP, Ozeki NG SMS Gateway is the ideal choice. The latest version supports SNPP in addition to other popular wireless communication protocols.

    Configuration steps

    As Service Provider Connections page already explains, in order to send and receive messages (even pager messages) using Ozeki NG SMS Gateway, you need to install and configure one or more service provider connections. One of the available service provider connections is SNPP connection.

    The Simple Network Paging Protocol (SNPP) is for sending messages to pagers over the Internet.

    For configuring SNPP connection you can use the graphical user interface of Ozeki NG SMS Gateway.

    To start installing and configuring an SNPP connection, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Console interface. (To find out how to open this interface, check out the QuickStart Guide.)

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu.

    After you have clicked one of these, the Add service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the SNPP connection, click on Install next to it in the list (Figure 1).

    install snpp connection
    Figure 1 - Install SNPP connection

    Then in Connection information section of General tab you can specify the IP address (in Server field) and the port of the SNPP connection. In Keepalive period field you can enter the time period in which a keepalive message should be sent to keep the connection alive (Figure 2). Finally, click OK.

    connection information
    Figure 2 - Connection information

    After clicking OK, the SNPP connection is setup and you can start to sending messages to pagers (Figure 3).

    snpp connection is setup
    Figure 3 - SNPP connection is setup

    If you have any questions or need more information, please contact us at: info@ozekisms.com.

    SMTP (E-mail to SMS) Connection

    This chapter provides detailed instructions on how to install and configure and SMTP (E-mail to SMS) service provider connection to send SMS messages through E-mail to SMS services using Ozeki NG - SMS Gateway software.

    As you can read on the Service Provider Connections page, you need to install and configure one or more service provider connections for SMS messaging using Ozeki NG - SMS Gateway. One of the service provider connections supported by the software is the SMTP (E-mail to SMS) connection.

    The SMTP (E-mail to SMS) connection can be used to send SMS messages through E-mail to SMS services. E-mail to SMS connectivity is provided by many mobile network operators and multichannel IP based GSM gateways. If you install this connection, you can connect to these services.

    You can install and configure this connection using the graphical user interface of Ozeki NG - SMS Gateway. To start installing and configuring an SMTP (E-mail to SMS) connection, click the Add button in the top right-hand corner of the Service providers panel on the left of the Management Console interface. (To find out how to open this interface, check out the Quickstart Guide.).

    You can also add a service provider connection by clicking the Add service provider item in the Service providers menu.

    After you have clicked on of these, the Add service provider panel will show up on the right of the interface. The panel contains a list of protocols you can install and use for communication with an SMS service provider.

    To select the SMTP (E-mail to SMS) connection, click the Install link in the respective entry in the list (Figure 1).

    install the smtp email to sms connection
    Figure 1 - Starting to install the SMTP (E-mail to SMS) connection

    When you have installed the SMTP (E-mail to SMS) connection, the Configuration panel will show up on the right of the interface. The first tab of the panel is the General tab, which consists of an E-mail parameters (outgoing messages) and an SMTP server settings section.

    In the E-mail parameters (outgoing messages) section, specify the outgoing e-mail messages' parameters (Figure 2). These areFrom, To, Subject and Body. You can use keywords in these parameter values, these are: $recipient (the SMS message's recipient) and $messagetext (the SMS message's text).

    smtp email to sms connection settings
    Figure 2 - The General settings tab

    In the SMTP server settings section, provide the hostname or IP address of the SMTP server you will use to send outgoing e-mail messages. This can be the same e-mail server you have configured in Outlook. Type in the hostname to the SMTP server host field and the port to the SMTP server port field.

    Note that the above values are mandatory to have the SMTP connection working correctly.

    Under the Advanced tab, you can specify advanced parameters. There are three sections here: Optional SMTP Settings, Charset encoding and Identification (Figure 3).

    smtp email to sms connection advanced settings
    Figure 3 - The Advanced settings tab

    In the Optional SMTP Settings section, you can specify your SMTP username and password if you have an SMTP server that requires authentication. For this case, check My SMTP server requires authentication checkbox and fill in SMTP Username and SMTP Password fields. If your SMTP server requires SSL connection, then check My SMTP server requires SSL connection checkbox too.

    In the Charset encoding section, you can specify the charset encoding used to encode your messages' body and subject by selecting the appropriate values for the Body encoding and Subject encoding fields.

    In the Identification section, you can specify the telephone number assigned to this connection and the service provider connection name. Enter these values in the Telephone number and Service provider name fields. Note, that you must add the telephone number in international format: starting with "+". You can check the overridable checkbox to the right of the Telephone number. This ensures that you can replace the phone number specified in the Telephone number field with a different one to be displayed as the sender of an outgoing message. You can also replace the number with (alphanumeric) text consisting of a maximum of eleven (11) characters. Therefore, when a message is sent out, e.g. using the Database user, you can specify any different phone number or a name to be displayed as the sender of the message.

    To configure logging, click the Logging tab in the Configuration panel.
    The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 4).

    smtp email to sms connection logging tab
    Figure 4 - The Logging tab

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory field. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs.

    In the Maximum log file size text field you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text field, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 8 (see Figure 4 above).

    By checking the Compress rotated files with zip option you can save rotated fields compressed in a zip file.

    To initiate the connection manually, click the Connect link in the panel of the service provider connection (Figure 5).

    smtp email to sms connection links to operations
    Figure 5 - Links to operations

    You can open the panel of a service provider connection by clicking its name in the Service providers panel in the Management Console.

    The panel of a service provider connection consists of three sections.

    • In the upper section you can find the name of the service provider connection (with the name of its protocol in brackets).
    • You can see an icon showing if the service provider connection is connected. If it is not, the icon is marked with an "x".

    To the right of the icon you can find links to perform different operations.

    • Configure: to configure or modify the configuration of an installed service provider connection. Clicking this link will take you back to the Configuration panel.
    • Events: to view the logging of the latest server events related to the service provider connection. Clicking it will bring up the Events panel containing the logging of the latest server events.
    • Connect: to connect the service provider connection with the SMS Center.
    • Disconnect: to disconnect the service provider connection from the SMS Center.
    • Uninstall: to uninstall the service provider connection.

    In the middle section of the panel you can see some of the most important configuration information.

    • The options that have been (re)activated during the configuration are marked with a tick.
    • The options that have not been activated or those that have been deactivated during the configuration are marked with an "x".

    For more information please contact us at info@ozekisms.com.

    HTTP SMS Service Provider

    This chapter provides instructions on how to install and configure the HTTP SMS Service Provider connection for SMS messaging using the Ozeki NG SMS Gateway software.

    Install and configure the HTTP SMS Service Provider

    Step 1 - Open the list of Service Providers

    The HTTP Service Provider is a template-based provider, which lets you to send and receive HTTP Requests and delivery reports based on the schema that you provide. You need to provide us a detailed description about your requests and our developers will develop it based on your provided schema.

    Step 2 - Add HTTP Service Provider to the connection list

    You can install and configure the HTTP Service Provider connection using the graphical user interface of Ozeki NG SMS Gateway. To start installing and configuring an HTTP Service Provider connection, click the Add button in the top right-hand corner of the Service provider's panel on the Management page of the gateway.

    add service provider connection
    Figure 1 - Add Service Provider connection

    Step 3 - Install the HTTP Service Provider

    On the following page you can find the HTTP Service Provider connection. Click on the Install button to create the new connection.

    install http service provider connection
    Figure 2 - Install HTTP Service Provider connection

    Step 4 - Configure the HTTP SMS Service Provider

    On the configuration form of the service provider connection there are 4 tabs, where you can configure the connection.

    Under General tab, you need to specify the connection parameters for message submission. These parameters have to be in the Post URL textbox that is provided by your service provider.

    In the textbox of Listen URL you need to write the IP address of your Ozeki NG - SMS Gateway on which the Gateway will be listening for incoming SMS messages.

    In the Template box you need the select the template, which has been created based on your provided schema.

    In the Encoding textbox you can specify the encoding options with the following settings: If you check the "Use URL encoding in outgoing messages" checkbox your outgoing messages will be URL encoded. The incoming messages will be URL decoded if you check the"Use URL decoding in incoming messages"

    general settings of the http service provider connection
    Figure 3 - General settings of the HTTP Service Provider connection

    Step 5 - Add HTTP/HTTPS authentication (optional)

    In the Connection tab of the configuration form you can fill the form for HTTP authentication. Client certificate can also be set for HTTPS authentication.

    connection tab of the http service provider connection
    Figure 4 - Connection tab of the HTTP Service Provider connection

    Step 6 - Setup SMS content types (optional)

    In the Advanced tab you can specify which content types will be used for outgoing requests and outgoing responses. In the Timeout box you can give the timeout which will be used at sending and receiving HTTP requests. In the Additional Headers textbox you can add additional header values seperated by semicolons.

    advanced tab of the http service provider connection
    Figure 5 - Advanced tab of the HTTP Service Provider connection

    Step 7 - Specify log file details (optional)

    In the Logging tab you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the second option the program produce logfiles containing binary codes representing the communication data.

    In the Log file settings section of the tab, you can give the Log directory, the maximum log file size and the number of rotated logfiles. Log rotation saves disk space, as it ensures that older logfiles will be automatically deleted from the log directory. In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created.

    logging configuration of the https sms service provider
    Figure 6 - Logging configuration

    If you have any other questions, please contact us at info@ozekisms.com.

    Users and Applications

    This section explains the terms user/application in SMS messaging using the Ozeki NG - SMS Gateway software, and provides links to different pages detailing how to install and configure different users and applications.

    In SMS messaging using Ozeki NG - SMS Gateway, a user or application is an entity provided with service with the help of the software. For instance, a user (human person) can log in to Ozeki NG - SMS Gateway to send and receive SMS messages using the graphical user interface (GUI) of the program.

    An application allows automated SMS messaging, without human involvement, though with human configuration. For example, a database user inserts incoming messages into a database, and periodically checks the database for messages to be sent out.

    For reasons of simplicity, applications are also often referred to as users in the documentation and the GUI of Ozeki NG - SMS Gateway.

    Ozeki NG - SMS Gateway allows you to install and configure a large number of and different types of users and applications using the graphical user interface of the software.

    At present, the program supports the installation and configuration of the following users and applications:

    Standard User

    This chapter explains how to install and configure a standard user for SMS messaging using the graphical user interface of the Ozeki NG - SMS Gateway software.

    Ozeki NG - SMS Gateway allows, among others (see the Users and Applications page), the installation and configuration of a Standard user.

    A standard user can use the HTTP user interface to log in to the program to send and receive SMS messages.

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure a standard user.

    To start installing and configuring a standard user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the panel you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To add a standard user, click the Install link in the respective entry in the list (Figure 2).

    installing a standard user
    Figure 2 - Installing a standard user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the Standard user installation panel. Here, you need to enter a unique username in the Username field.

    This will take you to the Authentication tab of the Configuration panel.

    • The Username field contains the unique username you have provided in the previous panel.
    • The Password field contains a password offered by the program. You can and should change it. Your password should be a combination of letters and digits (at least one or two of the latter). From now on, the username and password you have provided can be used to log in to the program (Figure 3).

    user authentication
    Figure 3 - User authentication

    The name of the logged-in user can be read on the right of the title bar of the graphical user interface of Ozeki NG - SMS Gateway. (See Figure 1 on The Menu page.)

    To configure logging related to the user, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log HTTP communication. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 4).

    logging options
    Figure 4 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box in the Logfile settings section, you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 2000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 4 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    To modify the configuration or to view server events related to an installed user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 5).

    clicking a user-related task link
    Figure 5 - Clicking a user-related task link

    To configure or modify the configuration of a user, click Configure.To view the latest server events related to a user, click Events. To uninstall the user, click the Uninstall link.

    SMPP User

    This page explains how to install and configure an SMPP user for SMS messaging using the graphical user interface of the Ozeki NG - SMS Gateway software.

    Ozeki NG - SMS Gateway allows, among others (see the Users and Applications page), the installation and configuration of an SMPP user.

    The software enables all users to connect to the gateway through the Listener port and to exercise their user functions. The creation of an SMPP user account means enabling connection to the Gateway using the SMPP protocol. Anyone who knows the username and the password of a given SMPP user account can connect to the Ozeki NG - SMS Gateway if their IP address is authorized for connection. Once the Gateway has authenticated the user, they are enabled to send and receive messages. Consequently, the creation of an SMPP user allows the Ozeki NG - SMS Gateway to be fully authorized to act as an SMS Center.

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure any user or application.

    To start installing and configuring an SMPP user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu. (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the page you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    An SMPP user allows you to connect SMPP clients to Ozeki NG - SMS Gateway to send and receive SMS messages. Clients can use the SMPP protocol. For connection the clients should use the following settings:

    Host:The IP address of the computer where Ozeki NG is installed.
    Port:9500
    Username:specified when you create an SMPP user
    Password:specified when you create an SMPP user
    System type:Ozeki
    Bind mode:Transceiver
    Protocol version:v3.4

    To add an SMPP user, click the Install link in the respective entry in the list (Figure 2).

    installing an smpp user
    Figure 2 - Installing an SMPP user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the SMPP user installation panel. Here, you need to enter a unique username in theUsername field.

    This will take you to the Authentication tab of the Configuration panel.

    • The Username field contains the unique username you have provided in the previous panel.
    • The Password field contains a password offered by the program. You can and should change it. Your password should be a combination of letters and digits (at least one or two of the latter). From now on, the username and password you have provided can be used to log in to the program (Figure 3).

    user authentication
    Figure 3 - User authentication

    To configure logging related to the SMPP user, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication (SMPP Protocol). You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 4).

    logging options
    Figure 4 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box in the Logfile settings section, you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 4 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    To modify the configuration or to view server events related to an SMPP user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 5).

    clicking a user related task link
    Figure 5 - Clicking a user-related task link

    To configure or modify the configuration of the user, click Configure. To view the latest server events related to the user, click Events. To uninstall the user, click the Uninstall link.

    How to provide SMS Service for SMPP clients

    If you have Ozeki NG SMS Gateway installed on your server, you can provide SMS service for your applications (or your customers). Your applications can connect to Ozeki NG SMS Gateway over the SMPP protocol. This is possible because Ozeki NG SMS Gateway has a built in SMPP SMSC. In this guide you can read about how you can configure your Ozeki NG SMS Gateway to provide SMPP Service.

    1. Introduction

    In this example, we configure Ozeki NG SMS gateway to provide SMS service over the SMPP protocol for two SMS Client Applications (User John and User Paul). These applications will connect to the built in SMSC of Ozeki NG SMS Gateway (Figure 1).I assume the Ozeki NG SMS Gateway software was installed on a server that has an IP address of: 192.168.1.1.

    smpp clients connect to the build in smsc of ozeki ng sms gateway
    Figure 1 - SMPP Clients connect to the build in SMSC of Ozeki NG SMS Gateway

    After installation Ozeki NG SMS Gateway will automatically start the build in SMSC on port 9500. This means that the SMPP Client Applications (User John and User Paul) will connect to 192.168.1.1 on port 9500. The SMPP Protocol they will use is SMPP v3.4 and the connection type will be Transceiver.

    2. How to setup an SMPP user account for SMPP Client Application (User John)

    To make it possible for User John to connect to the built in SMSC of the Ozeki NG SMS Gateway, you have to create an SMPP User account. To do this you should click on Add user in the Management console (Figure 2).

    click on add user
    Figure 2 - Click on Add user

    The next step is to select the SMPP User type and click on install (Figure 3).

    select user type smpp user
    Figure 3 - Select user type SMPP User

    Then you have to provide the username and password. The username should be: john (Figure 4). The password can be wpsd123 (Figure 5).

    smpp client username john
    Figure 4 - SMPP Client username: john

    smpp client password wpsdonetwothree
    Figure 5 - SMPP Client password: wpsd123

    After clicking OK on the SMPP user configuration form, your SMPP user account is successfully created. Following this your SMPP client application can connect to the build in SMSC of your Ozeki NG SMS Gateway using the following connection information. This connection information should be configured in the SMPP Client Application of User John:

    SMPP Connection Information for User John:

    SMPP Host:192.168.1.1
    Port:9500
    Username:john
    Password:wpsd123
    SMPP version:3.4
    SMPP bind:transceiver
    SMPP system type:SMPP

    More detailed information on how to create accounts for SMPP client connections, can be found in the How to add an SMPP user guide. If you repeat the same steps for the client application user Paul, he will also be able to connect to the built in SMSC over SMPP. For example if you specify the password wp44sd55 for user Paul, he can connect to your Ozeki NG SMS Gateway using the following parameters:

    SMPP Host:192.168.1.1
    Port:9500
    Username:paul
    Password:wp44sd55
    SMPP version:3.4
    SMPP bind:transceiver
    SMPP system type:SMPP

    3. Configuring an SMPP Service Provider connection

    Setting up client connections of course, is not enough to get the SMS messages to the wireless network. To make it possible to deliver SMS messages to mobile users, you have to configure an SMS Service Provider connection. You can use IP SMS connections such as SMPP, UCP, CIMD2 to connect to your SMS service provider over the Internet or you can simply attach a GSM modem to your computer with a phone-to-pc data cable to send and receive the SMS messages. In our example (presented on Figure 1.), we attach to the SMS service provider using the SMPP IP SMS protocol. We configure our Ozeki NG SMS Gateway to connect using SMPP to host 223.122.122.45, port 3456.

    To configure this connection, please add an SMPP service provider connection by clicking on "Add" in the management console (Figure 6).

    click add to start the service provider connection installation procedure
    Figure 6 - Click add to start the service provider connection installation procedure

    From the list, you have to select the SMPP Connection, then you have to click on install. This will install an SMPP service provider connection(Figure 7).

    install an smpp service provider connection
    Figure 7 - Install an SMPP service provider connection

    After you have clicked install, you will be presented with the configuration form of the SMPP service provider configuration. On this form you have to configure the connection details of the SMS Service provider connection. The connection details are provided by the SMS Service provider. For example if the GSM network operator Vodafone provides you the SMS Service, they will give you a data sheet with the following information:

    Connection details provided by your SMS Service provider (e.g.: Vodafone):

    SMPP Host:223.122.122.45
    Port:3456
    Username:accnt
    Password:ER32wp

    You receive the information presented in above table when you sign up for their service. This information can be entered on the SMPP Service provider configuration form (Figure 8).

    configure the smpp connection details
    Figure 8 - Configure the SMPP connection details

    After the configuration details are entered you can click connect to start the service. That's all you have to do.

    4. More information

    With Ozeki NG SMS Gateway you can add more than one service provider connection. If more then one connection is available you can use inbound SMS routing and outbound SMS routing to adjust the system according to your needs. You may also want to keep track of all the SMS Messages sent or received for accounting purposes. If this is a requirement, you can configure SQL logging to save a record of all outgoing and incoming messages into a database.

    How to connect Kannel SMS Gateway to Ozeki NG SMS Gateway

    This page explains how to connect Kannel SMS Gateway to Ozeki NG SMS Gateway over SMPP protocol. In this guide you can see how to install and configure an SMPP user using the graphical user interface of Ozeki NG SMS Gateway and the commands you need to use in the configuration files of the Kannel SMS Gateway.

    Step 1: Install an SMPP user

    In order to connect Kannel SMS Gateway to Ozeki NG SMS Gateway, first you need to install and configure a new SMPP User in the graphical user interface of your Ozeki NG SMS Gateway.

    To start installing and configuring an SMPP user, click on the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu. (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels. The panel on the left side contains a list of users that have been installed, while the panel on the right side contains a list of users that can be installed. On the right panel find the SMPP user and click on Install button. It allows you to connect SMPP clients to Ozeki NG - SMS Gateway to send and receive SMS messages.

    installing an smpp user
    Figure 2 - Installing an SMPP user

    After you have clicked on the Install button, you need to provide a unique username. Clicking on the Ok button, the configuration form of the SMPP user appears. Under the Authentication tab of the configuration panel, the Username field contains the unique username you have provided in the previous panel. And the Password field that you should change. Your password should be a combination of letters and digits (at least one or two of the latter). From now on, the username and password you have provided can be used to log in to the program (Figure 3).

    user authentication
    Figure 3 - User authentication

    Now you are ready with the basic settings you need to perform on your SMPP user. The following data can be used in order to connect your Kannel SMS Gateway to Ozeki NG SMS Gateway:

    SMPP Connection Information for Kannel SMS Gateway:

    (This is default SMPP port. If you wish to change, you can perform it unser Edit \Server preferences \ Client connectivity \ SMPP Server textbox).
    SMPP Host:The IP address of Ozeki NG SMS Gateway (in this example: 192.168.113.176).
    Port:9500
    Username:smpp
    Password:The password you have provided in the previous step. SMPP version:3.4
    SMPP bind:transceiver
    SMPP system type:SMPP

    If you would like to read more about SMPP user or how to provide SMS Service for SMPP clients, click on the following links:

    Step 2: Configure Kannel SMS Gateway

    After you have installed Kannel SMS Gateway to your Linux operating system, you need to change its configuration file in order to connect it to Ozeki NG SMS Gateway.

    First stop your Kannel SMS Gateway using the following command:

    service kannel stop
    

    service kannel stop
    Figure 4 - Service kannel stop

    Now open the coniguration file of the gateway with your favourite text editor.

    nano /etc/kannel/kannel.conf
    

    nano kannel conf
    Figure 5 - nano kannel.conf

    You need to provide the following data:

    • group: smsc
    • smsc: smpp
    • interface-version: 34
    • host: 192.168.113.176 (the IP address of the computer on which Ozeki NG SMS Gateway you is installed)
    • port: 9500 (this is the port on which Ozeki NG SMS Gateway is listening incoming SMPP packets)
    • system-id: smpp (this is the unique username we gave in the previous step)
    • smsc-password: smpp (this is the password belongs to the SMPP user in your Ozeki NG SMS Gateway)
    • system-type: default
    • transceiver-mode: 1 (transceiver mode can be used to send or receive SMS messages on the same connection)

    group = smsc
    smsc = smpp
    interface-version = 34
    host = 192.168.113.176
    port = 9500
    system-id = smpp
    smsc-password = smpp
    system-type = default
    transceiver-mode = 1
    

    edit kannel conf
    Figure 6 - Edit kannel.conf

    Now start the Gateway.

    service kannel start
    

    start your gateway
    Figure 7 - Start your Gateway

    Step 3: Check the connection between the two SMS gateways

    Now return to Ozeki NG SMS Gateway to check the status of the connection.

    The following figure shows that the Kannel SMS Gateway has connected to Ozeki NG SMS Gateway successfully.

    status of the connection
    Figure 8 - Status of the connection

    Step 4: Forward incoming messages to Kannel SMS Gateway

    If a message comes into the Ozeki NG SMS Gateway on one of the service provider connection, and you would like to forward it to Kannel SMS Gateway, you need to install a new Inbound routing rule with the following settings:

    • Source: Any
    • Destination: smpp

    inbound routing rule
    Figure 9 - Inbound routing rule

    The following picture shows the event log of the SMPP user that you can see when an SMS message is forwarded to Kannel SMS Gateway.

    sms to kannel
    Figure 10 - SMS to Kannel

    Step 5: Receive SMS messages from Kannel SMS Gateway

    If you would like to send out an SMS message coming from Kannel SMS Gateway you need to setup a new Outbound routing rule with the following settings:

    • Source: smpp
    • Destination: Any

    outbound routing rule
    Figure 11 - Outbound routing rule

    The following picture shows the event log of the SMPP user that you can see when an SMS message is coming from the Kannel SMS Gateway.

    sms from kannel
    Figure 12 - SMS from Kannel

    Conclusion

    If you have followed these steps you can connect your Kannel with your Ozeki NG SMS Gateway over SMPP protocol.

    How to send and receive SMS messages from a database application

    This guide explains how you can setup Ozeki NG SMS Gateway to communicate with your database server. If the steps in this guide are followed, you will be able to send (or receive) SMS messages from a database application. All you have to do is insert data (or read data) from the appropriate database tables.

    This guide gives you the simple steps for the configuration.

    Introduction

    Ozeki NG - SMS Gateway can be used to send and receive SMS messages using a database server with the help of SQL queries. This is possible because database servers allow the sharing of database tables between two applications.

    Database table layouts:
  • Microsoft SQL Express ( Video tutorial)
  • Microsoft SQL Server
  • Oracle ( Video tutorial)
  • MySQL ( Video tutorial)
  • Access
  • PostgreSQL
  • Sybase/SQL Anywhere
  • Informix
  • Other database related information:

  • Automatic information retrieval from a database using SMS messages
  • To be able to send SMS messages from a database application you need to create a database table called ozekimessageout. You can put an outgoing message into this database table using an SQL INSERT command. Ozeki NG - SMS Gateway will periodical check (poll) the ozekimessagout table with an SQL SELECT command, and if it finds a new entry, it will send the SMS message.

    You can receive SMS messages in a similar way. You need to setup a database table called ozekimessagein. If an SMS message is received from a mobile phone, it is inserted by Ozeki NG SMS gateway into the ozekimessagein database table (Figure 1). You can use an SQL SELECT to read this message.

    sms messaging using a database server
    Figure 1 - SMS messaging using a database server

    In order to get this configuration working, you need to have a database server (such as Oracle, Access, MySql, MS SQL, Postgres, Sybase, etc.) installed, and you need to create two database tables: ozekimessageout and ozekimessagein. The ozekimessageout table is used for sending, while ozekimessagein is used for receiving SMS messages. To find out how to create the ozekimessagein and the ozekimessageout table for different database servers, read the respective pages related to the different database users. Check out the links at the end of this introduction.

    Once you have created the database structure, you need to connect Ozeki NG SMS Gateway to your database. To establish a connection you can use an ODBC connection or an OLEDb connection. (To setup the connection you might have to install and configure an OleDB or an ODBC driver. For example MySQL requires the MyODBC Database driver to be installed. For Microsoft SQL Express, Microsoft SQL Server and Oracle, Microsoft Windows has a built in OleDb drier, so you do not have to install a driver separately).

    The connection can be configured with a database connection string. This connection string includes the database driver name, the IP address, the username and the password and the name of the database. More information about the database connection string can be found in our "Database connection strings" manual.

    If you have figured out the connection string for your database server, you need to install and configure a database user in Ozeki NG - SMS Gateway. This is a virtual user that will communicate with a specified database server and will provide you the SQL SMS Gateway functionality.

    For more information about different databases, check out any of the following links:

    How to install a database user

    You can install and configure a database user with the graphical user interface of Ozeki NG - SMS Gateway. Follow the instructions below.

    To start installing and configuring a database user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. (To open the Management Console interface, click the Management Console tab. For more information, check out the User Interface page.) You can also add a user by clicking the Add user item in the Users and applications menu. (Figure 2).

    adding a user
    Figure 2 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the page you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To add a database user, click the Install link in the respective entry in the list of installable users and applications (Figure 3).

    installing a database user
    Figure 3 - Installing a database user

    This will open a panel asking you to give the database user a unique name (Figure 4).

    nameing the database user
    Figure 4 - Naming the database user

    Enter a unique name in the User name edit box, and click OK. Then the installation is finished, and the name of the database user will show up in the list of users on the left in the panel.

    How to configure a database user

    Once you have installed a database user, you can start to configure it. After you have provided a unique name for the database user and clicked OK (see Figure 4 above), the Configuration panel will open.

    The first tab that will show up is the Database connection tab (Figure 5).

    • In the Connection section, select the connection string type in the Connection string type dropdown menu. Make sure that the connection you specify is accessible for the system user account.
    • For Open Database Connectivity, select Odbc.
    • For Object Linking and Embedding Database, select OleDb.

    database connection tab
    Figure 5 - The Database connection tab

    In the Connection string template, modify any variables if necessary. For instance, as you have probably changed the username and password, you will need to modify them in the template. If Ozeki NG - SMS Gateway and the database reside on the same server, "localhost" can be used to describe the database location. If they do not reside on the same server, you need to specify the database location by replacing "localhost" with the IP address.

    Different database servers require different connection strings. By default, this template contains the connection string of the MySQL database server. For information about connection strings of other database servers, check out Appendix B - Connection Strings.

    The connection string for the Oracle SQL server is:
    Provider=MSDAORA.1;Password=YourPassword;User ID=YourUserID;Persist Security Info=True

    The connection string for the MS SQL server is:
    Provider=SQLNCLI;Server=YourServer;Database=YourDatabase;UID=YourUsername; PWD=YourPassword;

    The connection string for the Sybase / SQL Anywhere Server is:
    Provider=ASAProv.90;UID=MyUsername;PWD=MyPassword;DatabaseFile=DatabaseFileLocationOnYourComputer.db; EngineName=Yourdbenginename;Start=YourDatabaseBinaryLocation.exe -c 32M;AutoStop=Yes

    The connection string for the Postgre SQL server is:
    DRIVER={PostgreSQL};SERVER=YourServerIP;port=5432;DATABASE=YourDatabaseName; UID=YourUsername;PWD=YourPassword;

    Additional connection strings can be found in Appendix B - Connection Strings.

    In the Date format section, specify - in the Date format string edit box - the date format string used to create the date value for the SQL statements. The default date format string is yyyy-MM-dd HH:mm:ss. In the date format string, yyyy stands for the year as a four-digit number. If the year has more than four digits, only the four low-order digits appear in the result. If the year has fewer than four digits, the number is padded with leading zeroes to achieve four digits. (Note that for the Thai Buddhist calendar, which can have five-digit years, this format specifier renders all five digits.)

    MM stands for the month as a number from 01 through 12. A single-digit month is formatted with a leading zero.

    The dd string stands for the day of the month as a number from 01 through 31. A single-digit day is formatted with a leading zero.

    HH stands for the hour as a number from 00 through 23, that is, the hour as represented by a zero-based 24-hour clock that counts the hours since midnight. A single-digit hour is formatted with a leading zero.

    The mm string stands represents the minute as a number from 00 through 59. The minute represents whole minutes passed since the last hour. A single-digit minute is formatted with a leading zero.

    The ss string stands for the seconds as a number from 00 through 59. The second represents whole seconds passed since the last minute. A single-digit second is formatted with a leading zero.

    If you are content with this date format, leave the default date format string unchanged. If you wish to change it, rearrange the format specifiers. For example, you can put dd-MM-yyyy HH:mm:ss instead of the default arrangement. For information, about the different date format strings you can use, check out the Date Format Strings page. When you have finished configuring the database connection, click OK.

    To send SMS messages using this connection, you need to make settings in the SQL for sending tab. Click the SQL for sending tab (Figure 6).

    the sql for sending tab
    Figure 6 - The SQL for sending tab

    In the upper section of the panel you have opened, you can see a checkbox. By default, it is checked, and it should be checked if you use this database connection for sending outgoing messages. (To stop using this connection for sending outgoing messages, uncheck the checkbox.)

    Below this checkbox you can specify how often Ozeki NG - SMS Gateway should check the ozekimessageout table for outgoing messages. Specify the frequency in seconds by entering a positive whole number in numerical form. If you are content with the default value (10), leave this edit box unchanged.

    In the lower section of this panel you can specify the maximum number of messages to be sent out with one poll. By default it is 10. If you are content with this default value, leave the edit box unchanged (Figure 7).

    If Maximum number of messages to send with one poll is 10, it means that 10 messages will be sent out with 1 poll. If there are more than 10 messages to be sent, then all the messages will be polled. If there is no messages left, the system will stop for 10 seconds (since it is the default value for checking outgoing messages). For example, if there are 100 messages, there will be 11 polls. (11 polls: 10 messages are sent with 1 poll. Then 100 messages will be sent with 10 polls. Plus there will be 1 last poll for checking for outgoing messages.) In this way, if there are 99 messages there will be 10 polls, etc.

    In other words it is ensured that messages will be sent out even if the default number of messages to be sent with one poll is set to 10 but there are more than 10 messages waiting for sending.

    specifying the frequency of queries and the sql statements
    Figure 7 - Specifying the frequency of queries and the SQL statements

    In the lower section, you can specify SQL statements related to the polling and the status of outgoing messages.
    Modify any variables in the templates, or if you are content with them, leave them unchanged.

    The statement in the Polling template describes the way of selecting outgoing messages.

    • The statement in the Sending template is used if the polling has been successful.
    • The statement in the Sent template is used if the message has been accepted by the service provider.
    • The statement in the Not sent template is used if the message has not been sent.
    • The statement in the Delivered template is used if the message has been delivered to the recipient phone number.
    • The statement in the Undelivered template is used if the message has not been delivered to the recipient phone number.

    For detailed description of SQL statements please go to Detailed description of SQL statements page.

    To receive SMS messages using this connection, you need to make settings in theSQL for receiving tab.Click the SQL for receiving tab (Figure 8).

    the sql for receiving tab
    Figure 8 - The SQL for receiving tab

    In the upper section of the panel you have opened, you can see a checkbox. By default, it is checked, and it should be checked if you use this database connection for receiving incoming messages. (To stop using this connection for receiving incoming messages, uncheck the checkbox.)

    In the lower section of the panel, you can see a template containing an SQL INSERT statement used for inserting incoming messages into the database.If necessary, modify any valuables in the statement. If not, leave it unchanged.

    Below the template you can find three pairs of edit boxes that allow you to make the program prepare the message prior to insert. This may be useful to handle messages containing special characters.

    Each pair consists of one edit box (on the left) for the character to be replaced, and one (on the right) for the characters that will replace the character on the left. By default, the boxes contain the most problematic special characters to be replaced and those to be used instead. Modify these settings if you wish to specify different characters.

    You can also configure the logging related to the database user. Click the Logging tab to open the panel for logging settings. In the Logging section of the panel, you can find three checkboxes. You can choose to check any or all (or none) of them. Your choice depends on whether you want the program to log sent and received messages in human readable format, to log SQL SELECT statements and/or to log SQL UPDATE statements (Figure 9).

    the logging tab
    Figure 9 - The Logging tab

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4.

    If you are content with the default specifications, leave the text boxes unchanged (Figure 10).

    log file settings
    Figure 10 - Log file settings

    To modify the configuration or to view server events related to a database user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 11).

    clicking a user-related task link
    Figure 11 - Clicking a user-related task link

    To configure or modify the configuration of a user, click Configure.

    To view the latest server events related to a user, click Events.

    To uninstall the user, click the Uninstall link.

    Send SMS messages from Microsoft SQL Server

  • Video tutorial: Send and receive SMS from SQL Express (part 1/4, Install and configure SQL Express)
  • Video tutorial: Send and receive SMS from SQL Express (part 2/4, Create database layout)
  • Video tutorial: Send and receive SMS from SQL Express (part 3/4, Configure Ozeki NG database user)
  • Video tutorial: Send and receive SMS from SQL Express (part 4/4, Send a test message)
  • In this chapter you can learn how to send and receive SMS messages using the Microsoft SQL database server. The solution uses the Ozeki NG - SMS Gateway software installed on your PC. The solution uses the following database connection string to connect to the database server:

    Connection string type:

    OleDb
    Connection string:
    Provider=SQLNCLI;Server=YourServer;Database=YourDatabase; MultipleActiveResultSets=True;UID=YourUsername;PWD=YourPassword;

    Here is a quick overview of how this solution is going to work: First you create two database tables: ozekimessageout and ozekimessagein in MS SQL. Then you install and configure Ozeki NG SMS Gateway, to connect to MS SQL and to use these database tables for sending and receiving messages. Once you have the configuration completed, you can send an SMS message by creating a record in the ozekimessageout database table using an SQL INSERT. Ozeki NG will read this record using an SQL SELECT and will send your SMS message using a GSM modem attached to the PC or using an IP SMS connection.

    Step 1 - Create your database tables in Microsoft SQL Server

    MS SQL create table script:

    CREATE TABLE ozekimessagein (
    id int IDENTITY (1,1),
    sender varchar(255),
    receiver varchar(255),
    msg nvarchar(160),
    senttime varchar(100),
    receivedtime varchar(100),
    operator varchar(30),
    msgtype varchar(30),
    reference varchar(30),
    );
    CREATE TABLE ozekimessageout (
    id int IDENTITY (1,1),
    sender varchar(255),
    receiver varchar(255),
    msg nvarchar(160),
    senttime varchar(100),
    receivedtime varchar(100),
    operator varchar(100),
    msgtype varchar(30),
    reference varchar(30),
    status varchar(30),
    errormsg varchar(250)
    );
    Figure 1 - SQL Create table script

    If you want to work with larger messages, you can increase the size of the msg field, or you may also change it's data type.

    You can optionally create an index in the database for the 'id' field of the outgoing SMS table to support SQL updates.

    If you experiencing trouble connecting to the database server, from Ozeki NG SMS Gateway, you might need to allow TCP/IP login in MS SQL Server. The following webpage gives information about this: How to change the login method to allow TCP/IP connections for MS SQL server.

    Step 2 - Create an SQL User in Ozeki NG

    To do this you have to Download and Install Ozeki NG SMS Gateway. After installation you have to log into the SMS gateway using an Internet Explorer (or Firefox) Browser by typing http://127.0.0.1:9501/ and supplying admin as the login name and abc123 as the password. (Hint: do not forget to change your password!). After login, go to the "Users and Applications/Add User" menu item and click on Install next to the database user (Figure 2).

    install database user
    Figure 2 - Install database user

    The last step of the installation is to enter a name for this user. For example enter sql1 (Figure 3). You can type any name here.

    give a unique sql user name
    Figure 3 - Give a unique SQL user name

    Step 3 - Configure the database connection for this SQL User in Ozeki NG

    Ozeki NG uses an ADO/OleDB connection to access you SQL Database server. To setup this connection select OleDb as the connection type and enter the following connection string into the connection string textbox.

    Connection string:

    Provider=SQLNCLI;Server=YourServer;Database=YourDatabase;UID=YourUsername;PWD=YourPassword;

    Please note, that you must modify the variables in the connection string according to your system.

    specifying the connection string for the ms sql database
    Figure 4 - Specifying the connection string for the MS SQL database

    After you have configured the SQL connection string, click OK. By clicking OK Ozeki NG SMS Gateway will try to connect to your database server. You can verify the connection results in the events form. The events form can be accessed by clicking on the appropriate link (Figure 5).

    sql server events
    Figure 5 - SQL Server events

    If the connection is successful, you can send an SMS message by placing a record into the ozekimessageout database table.

    Step 4 - Enable detailed SQL login

    At this point you are ready to send your first SMS, but before you do, you should enable SQL logging to see what the SMS Gateway is doing to get your message. You can enable SQL logging on the Logging tab of the SQL User configuration form (Figure 6).

    enable sql logging
    Figure 6 - Enable SQL Logging

    Step 5 - Send your first SMS message

    To send your first SMS message you should insert a record into the ozekimessagout database table using the following SQL command:

    insert into ozekimessageout (receiver,msg,status) values ("+44111223465","Hello
    world","Send");
    

    Step 6 - Check the logs in Ozeki NG

    After you have inserted the record into the database, you should be able to verify that Ozeki NG has picked up the message for sending. You can do this by taking a look in the events form of the user (Figure 7).

    user events after successful sending
    Figure 7 - User events after successful sending

    If everything goes well you should see the following entries in the log:

    2007.08.09. 9:20:53 - INFO 3500: Opening OleDb connection to database server
    using connection string ...
    2007.08.09. 9:20:53 - INFO 3501: Successfully connected to database.
    2007.08.09. 9:20:53 - User connected.
    2007.08.09. 9:20:55 - SQL Command: 'SELECT id,sender,receiver,msg,msgtype,
    operator FROM ozekimessageout WHERE status='send'' returned 1 rows.
    2007.08.09. 9:20:55 - SQL Command: 'UPDATE ozekimessageout 
    SET status='sending' WHERE id='2'' affected 1 row.
    2007.08.09. 9:20:55 - -> Sending message (dataBase id:2): ';
    SMS:TEXT;VVMSUDVX;;+44111223465;Hello world;'
    2007.08.09. 9:20:55 - INFO 3098: Message sql1;SMS:TEXT;VVMSUDVX;
    sql1;+44111223465;Hello world; accepted for delivery from user 'sql1'.
    2007.08.09. 9:20:55 - INFO 3099: Message successfully sent. sql1;
    SMS:TEXT;VVMSUDVX;sql1;+44111223465;Hello world;
    2007.08.09. 9:20:55 - SQL Command: 'UPDATE ozekimessageout 
    SET status='sent', senttime='2007-08-09 09:20:56' WHERE id='2'' affected 1 row.
    2007.08.09. 9:20:55 - <- Message sent (dataBase id:2): 
    'sql1;SMS:TEXT;VVMSUDVX;sql1;+44111223465;Hello world;'
    

    Send SMS messages using Microsoft SQL Express

  • Video tutorial: Send and receive SMS from SQL Express (part 1/4, Install and configure SQL Express)
  • Video tutorial: Send and receive SMS from SQL Express (part 2/4, Create database layout)
  • Video tutorial: Send and receive SMS from SQL Express (part 3/4, Configure Ozeki NG database user)
  • Video tutorial: Send and receive SMS from SQL Express (part 4/4, Send a test message)
  • On this page you can get the necessary information to configure Microsoft SQL Express database server for SMS messaging. This page is an extension to the How to send SMS from an database server guide. The solution uses the Ozeki NG - SMS Gateway software installed on your PC.

    To setup your system, first you need to install and configure Ozeki NG SMS Gateway for SMS messaging. After Ozeki NG is configured for SMS messaging, you can open it's management console and you can install a database user in it. This database user will make SMS sending and receiving possible from your SQL Express database server. The database user will require you to provide the database connection type and the database connection string. For SQL Express you will have to use the following parameters:

    Connection type:

    OleDb

    Connection string:

    Provider=SQLNCLI;Server=.\SQLEXPRESS;MultipleActiveResultSets=True;
    User ID=ozekiuser;password=ozekipass;Database=ozeki;Persist Security Info=True
    

    After you have configured the database user, you need to create the database layout in SQL express to be able to send and receive SMS messages by using SQL INSERT and SELECT statements. You can create the database layout by opening a windows command prompt (Start->Run->cmd.exe), and starting the SQL Command interpreter by typing:

    C:\sqlcmd -S .\SQLExpress 

    Once the SQL command interpreter is running, you should enter the following commands. If the command interpreter could not connect to SQL express, try the instructions provided on the How to connect to SQL Express using the SQL command line utility page.

    
    create database ozeki
    GO
    
    use ozeki
    GO
    
    CREATE TABLE ozekimessagein (
     id int IDENTITY (1,1),
     sender varchar(255),
     receiver varchar(255),
     msg nvarchar(160),
     senttime varchar(100),
     receivedtime varchar(100),
     operator varchar(30),
     msgtype varchar(30),
     reference varchar(30),
    );
    
    CREATE TABLE ozekimessageout (
     id int IDENTITY (1,1),
     sender varchar(255),
     receiver varchar(255),
     msg nvarchar(160),
     senttime varchar(100),
     receivedtime varchar(100),
     operator varchar(100),
     msgtype varchar(30),
     reference varchar(30),
     status varchar(30),
     errormsg varchar(250)
    );
    
    GO
    
    sp_addLogin 'ozekiuser', 'ozekipass'
    GO
    
    sp_addsrvrolemember 'ozekiuser', 'sysadmin'
    GO
    
    

    Figure 1 - SQL Create table script

    If you want to work with larger messages, you can increase the size of the msg field, or you may also change it's data type.

    After the database layout has been created you are ready to send your first SMS. To send your first SMS message you should insert a record into the ozekimessagout database table. You can use the following SQL command to achieve this:

    insert into ozekimessageout (receiver,msg,status) values ("+44111223465","Hello world","Send");
    GO
    

    Hint: You can download SQLExpress free of charge from the following URL: http://msdn2.microsoft.com/en-us/express/aa718378.aspx

    Trouble shooting

    On some systems, you might have difficulties connecting to SQL Express. This is the error message you might experience:

    ERROR 6001: Database connection error: The 'SQLNCLI' provider is not registered on the local machine..

    SQLNCLI is installed with SQL Server Native Client. This error indicates that this is not installed on your machine. You can try to change the provider to "sqloledb" to use OLE DB and see if that works. In this case your connection string would be:

    Connection type:

    OleDb

    Connection string:

    Provider=SQLOLEDB;Data Source=.\SQLEXPRESS;User ID=ozekiuser;password=ozekipass;
    Database=ozeki;Persist Security Info=True
    

    Or change the whole connection string to ODBC and use the following connection string:

    Connection type:

    ODBC

    Connection string:

    Driver={SQL Server};Server=.\SQLEXPRESS;User ID=ozekiuser;password=ozekipass;
    Database=ozeki;Persist Security Info=True;

    Or change the whole connection string to SQLServer and use the following connection string:

    Connection type:

    SQLServer

    Connection string:

    Server=.\SQLEXPRESS;User ID=ozekiuser;password=ozekipass;Database=ozeki;Persist Security Info=True;
    

    One of these should work.

    Microsoft SQL Server 2008

    If you use Microsoft SQL Server 2008, apply the following connection string:

    Connection string:

    Provider=SQLOLEDB.1;Data Source=YourHostName;Persist Security Info=False;
    Integrated Security=SSPI;User ID=UserName;Password=User'sPassword;Initial Catalog=DatabaseName
    

    How to connect to SQL Express

    This page gives information on how to connect to SQL Express if the default connection method described on the SMS from SQL Express page is not working. Please follow these steps:

    1. By using SQL 2005 configuration manager, please check if both TCPIP and Named Pipes are enabled for SQL Express instance. Also, please make sure SQLBrowser service is running

    2. In Configuration manager, please make sure TCPIP and named pipes protocols are enabled properly for SQL client.

    3. Please check the error log for the sql express instance and make sure TCPIP and Named pipes are enabled. You shall also see the port for

    C:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG

    4. Try different protocols by using SQLCMD to test

    sqlcmd -S np:\\127.0.0.1\pipe\MSSQL$instancename\sql\query
    sqlcmd -S tcp:servername\instancename
    sqlcmd -S tcp:servername\instancename,portnumber
    

    Note: You may need to change the servername, instancename, portnumber properly according to your server configurations.

    Note: This information was originally posted by Peter Yang at the following URL: http://www.eggheadcafe.com/software/aspnet/30324190/sqlcmd-fails-with-login-t.aspx

    If you still cannot connect you may try to change the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer LoginMode =2

    A FAQ question related to SQL Express - SMS gateway:

    I cannot connect to the database server. I have received this errormessage, what should I do?

    Connecting to database (Provider=SQLOLEDB.1;Persist Security Info=False;User ID=myuser;Initial Catalog=mydb;Data Source=mydsn) : 2007-07-25 11:38:25 356:Database plugin 1 : Connection error: Login failed for user 'myuser'. (Provider=SQLOLEDB.1;Persist Security Info=False;User ID=myuser;Initial Catalog=mydb;Data Source=mdsn) :

    This means, that the software cannot connect to your database server. Based on the connection string I assume you use Microsoft SQL server. In this case, please use the following connection string:

    Provider=SQLNCLI;Server=YourServer;Database=YourDatabase;MultipleActiveResultSets=True;>UID=YourUsername;PWD=YourPassword;

    There is a good chance, that the software will be able to connect to your database server as soon as you use this connection string. You might notice, that there is no DSN in this connection string. This is because, you need to connect with username/password authentication.

    If the connection is not established after switching to this connection string, probably the username and password authentication is not enabled in your registry for MSSQL. To enable it, you should set the following setting in your registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer LoginMode=2

    To create a username and a password in Microsoft SQL Server, issue the following command:

    sp_addLogin 'ozekiuser', 'ozekipass'
    GO
    sp_addsrvrolemember 'ozekiuser', 'sysadmin'
    GO

    After applying these changes, please restart the MS SQL services or your computer.

    How to create a user in MS SQL that can be used by Ozeki NG

    To create a SQL Server login that uses SQL Server Authentication (SQL Server Management Studio) follow these steps.

    1. In SQL Server Management Studio, open Object Explorer and expand the folder of the server instance in which to create the new login.
    2. Right-click the Security folder, point to New, and then click Login.
    3. On the General page, enter a name for the new login in the Login name box.
    4. Select SQL Server Authentication. Windows Authentication is the more secure option.
    5. Enter a password for the login.
    6. Select the password policy options that should be applied to the new login. In general, enforcing password policy is the more secure option.
    7. Click OK.

    To create a SQL Server login that uses SQL Server Authentication (Transact-SQL) In Query Editor, enter the following SQL command:

    CREATE LOGIN [login name] WITH PASSWORD = '[password]' ; GO

    Errors connecting to SQL Server Express 2005

    Are you getting errors connecting to SQL Server Express 2005 via remote client software and yet have no problem connecting to it on the local machine?

    Some of the errors you might be seeing are:

    • sql server does not allow remote connections
    • SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified
    • An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider:Named Pipes Provider,error:40-Could not open connection to SQL Server))
    • Server does not exist or access denied

    If yes, then read on because SQL Server Express 2005 is not automatically configured for remote access during installation. It can be enabled however, so the problems you are having are more of a "feature" than a bug.

    Why this page?Well, we too ran into this problem - just as you have now. In recognition of all of the kind help we received from the Internet newsgroups we thought it might be useful to collect the information here so as to provide assistance to others in the same position.

    Here's a quick summary of the actions you need to take. The first three actions have a separate page which provides more details and some screen shots of the procedure.

    1. [Link] Enable the TCP/IP protocol using the Surface Area Configuration Utility
    2. [Link] Make sure the TCP/IP protocol is enabled in the SQL Server Configuration Utility
    3. [Link] Make sure the SQL Server browser is started. Note this step is optional. It is possible to set the SQL Server instance to use a fixed IP address - but this is non-standard for named instances.
    4. Make sure SQL Server and SQL Server Browser are exempted by the firewall on the server machine. This is done by putting sqlservr.exe and sqlbrowser.exe as an exception in the windows firewall. Chris D. sent in a note which might help.
    5. Note: In order to get things to work. You might need to completely reboot the server machine after making the changes. There have been reports that starting and stopping the SQL Server and Browser software is not enough.

    How to enable TCP IP access using the GUI

    surface area configurator

    surface area configurator

    Enabling the TCP/IP protocol in the SQL Server Configuration Utility to Configure SQL Server Express 2005 for Remote Access

    server protocols in server configuration manager
    Figure 1 - Server Protocols in Server Configuration Manager

    enable tcp ip
    Figure 2 - Enable TCP/IP

    On the IP Addresses tab you will probably see several sections - one for each network connection. In the example below there is only one network card (listed in the first section) and a local loopback connection indicated by the standard address of 127.0.0.1 For remote access to the SQL Server Express 2005 instance the loopback connection is of no interest.

    The first section is where the configuration has to be correct. Active option should say Yes as should the Enabled option. The IP address will probably be filled in for you (by Windows) and will be different on your machine.

    If you wish to enable dynamic ports for your SQL Server Express 2005 instance then the TCP Dynamic Ports option should be 0. To disable this option and use a fixed port change this field to a blank value and fill in the port on the TCP Port option. Disabling dynamic ports is non standard for named instances and should really only be done if you know exactly what you are doing and why you want to do it.

    Note: Dynamic ports means that the SQL Server Express 2005 instance gets assigned a random port every time it is started up. In order to connect, the remote client needs to know this port. It asks the Server Browser for the port number (the Server Browser has a well known and unchanging port configuration so it can always be found). The upshot is that if dynamic ports are used then the Server Browser must be started.

    ip addresses settings
    Figure 3 - IP Addresses settings

    Starting the SQL Server Browser to Configure SQL Server Express 2005 for Remote Access

    server config manager

    server browser properties

    server browser properties service tab

    Firewall setup

    The problem down to a hardware firewall at the ISP. If your server is hosted with an ISP, doing the above may not be enough, depending on how the server itself is setup.

    Resolution

    Go to command prompt and type netstat -a

    Within the results you need to see if the box is listening on the ports you think.

    In my case, the hardware firewall was preventing me from being able to connect.

    The solution was to stop using dynamics ports and open up a static port.

    To do this open up the SQL configuration manager. Click on protocols. Double Click on TCP/IP Click on IP Addresses tab As mentioned in the above document, 0 means dynamic ports.

    I found that by setting the static port, this solved my problem. Put an empty string in the TCP Dynamic ports box Set the port you want to connect on in the TCP port box. Do this for the net connections you have.

    Connect to the SQL using:

    IPADDRESS,PORT

    Works great now.

    Obviously, you should check out that doing do will not open you up to security risks with your ISP, however, this was the solution.

    In this article you will find detailed information on how to send SMS text messages from MSSQL Server 2008 with the help of Ozeki NG SMS Gateway. Ozeki NG SMS Gateway needs to be downloaded and installed on your computer to provide SMS functionality to your database.

    If you have installed Ozeki NG SMS Gateway software on your computer then you can start to setup your SMS system. To send SMS messages from MSSQL Server 2008 you need to do the follows: First create a database and then create two database tables in this created database for the outgoing and incoming messages: "ozekimessageout" and "ozekimessagein" in MS SQL. Then you need to configure Ozeki NG SMS Gateway to connect to the database and use these database tables for sending and receiving SMS messages. After the configuration you can start to send messages by inserting a record into "ozekimessageout" database table using an SQL INSERT. Ozeki NG SMS Gateway reads this record with the help of an SQL SELECT and it will send out your message as an SMS to mobile phones. It uses a GSM modem attached to the PC or it connects directly to the SMS center of the mobile service provider over the Internet (IP SMS).

    Create database tables in MSSQL 2008

    Start "SQL Server Management Studio" at Start / All programs / Microsoft SQL Server 2008 / SQL Server Management Studio. Then log into MSSQL Server with your username and password that you usually use for authentication in Windows. Now right click on "Database" menu item and "New Database" (Figure 1).

    create new database
    Figure 1 - Create new database

    Provide a name for this new database (in our example it is "ozeki") and click on "OK" (Figure 2).

    new database name
    Figure 2 - Name the new database

    You can specify international coding if you right click on the database and select "Properties". On the left side click on "Options" and set "Collation" field to your country (Figure 3).

    database properties
    Figure 3 - Database properties

    Next, right click on the created database and select "New Query" (Figure 4).

    new query
    Figure 4 - New query

    Copy the database tables script from this page and click on "Execute" (Figure 5) and (Figure 6).

    Database table script:

    	CREATE TABLE ozekimessagein (
    	id int IDENTITY (1,1),
    	sender varchar(255),
    	receiver varchar(255),
    	msg nvarchar(160),
    	senttime varchar(100),
    	receivedtime varchar(100),
    	operator varchar(30),
    	msgtype varchar(30),
    	reference varchar(30),
    	); 
    	
    	CREATE TABLE ozekimessageout (
    	id int IDENTITY (1,1),
    	sender varchar(255),
    	receiver varchar(255),
    	msg nvarchar(160),
    	senttime varchar(100),
    	receivedtime varchar(100),
    	operator varchar(100),
    	msgtype varchar(30),
    	reference varchar(30),
    	status varchar(30),
    	errormsg varchar(250)
    	);
    	
    Figure 5 - SQL database table script

    execute query
    Figure 6 - Execute query

    If it is done, close "SQL Server Management Studio".

    Create a database user in Ozeki NG SMS Gateway

    To create a database user in Ozeki NG SMS Gateway, first you need to log into the gateway software. Then go to "Add new user or application". Select "Database user" and click on "Install" next to it (Figure 7).

    install database user
    Figure 7 - Install database user

    Provide a name for this user (Figure 8).

    give a unique sql user name
    Figure 8 - Give a unique SQL user name

    Configure the database connection for this SQL user in Ozeki NG SMS Gateway

    To setup this database connection select the connection string type.

    OleDb

    Then customize the following connection string:

    Provider=SQLOLEDB.1;Data Source=YourComputerName;Persist Security Info=False;Integrated Security=SSPI;MultipleActiveResultSets=True;User ID=YourUserName;Password=YourPassword;Initial Catalog=CreatedDatabaseName

    Figure 9 is an example for a customized connection string.

    connection string
    Figure 9 - Connection string

    • Data Source=OZSERVER ### It is the name of the computer on which MSSQL has been installed
    • Integrated Security=SSPI ### It uses Windows authentication
    • User ID=Administrator ### It is the username
    • Password=qwe123RTY ### It is the password
    • Initial Catalog=ozeki ### It is the name of the database that contains "ozekimessagein" and "ozekimessageout" database tables

    You can test this created connection if you click on "SQL Prompt" and you select from the dropdown menu:

    INSERT INTO ozekimessageout (receiver,msg,status) VALUES ('+36205460691','Hello World','send');

    After a short period of time, Ozeki NG SMS Gateway will notice the new row and send out your message.

    Related pages:

    MSSQL Server 2012/2014 Connection

    In this article you will find detailed information on how to send SMS text messages from MSSQL Server 2012/2014 with the help of Ozeki NG SMS Gateway. Ozeki NG SMS Gateway needs to be downloaded and installed on your computer to provide SMS functionality to your database.

    If you have installed Ozeki NG SMS Gateway software on your computer then you can start to setup your SMS system. To send SMS messages from MSSQL Server 2012/2014 you need to do the follows: First create a database and then create two database tables in this created database for the outgoing and incoming messages: "ozekimessageout" and "ozekimessagein" in MS SQL. Then you need to configure Ozeki NG SMS Gateway to connect to the database and use these database tables for sending and receiving SMS messages. After the configuration you can start to send messages by inserting a record into "ozekimessageout" database table using an SQL INSERT. Ozeki NG SMS Gateway reads this record with the help of an SQL SELECT and it will send out your message as an SMS to mobile phones. It uses a GSM modem attached to the PC or it connects directly to the SMS center of the mobile service provider over the Internet (IP SMS).

    Create database tables in MSSQL 2012/2014

    Start "SQL Server Management Studio" at Start / All programs / Microsoft SQL Server 2012/2014 / SQL Server Management Studio. Then log into MSSQL Server with your username and password that you usually use for authentication in Windows. Now right click on "Database" menu item and "New Database" (Figure 1).

    create new database
    Figure 1 - Create new database

    Provide a name for this new database (in our example it is "ozeki") and click on "OK" (Figure 2).

    new database name
    Figure 2 - New database name

    You can specify international coding if you right click on the database and select "Properties". On the left side click on "Options" and set "Collation" field to your country (Figure 3).

    database properties
    Figure 3 - Database properties

    Next, right click on the created database and select "New Query" (Figure 4).

    new query
    Figure 4 - New query

    Copy the database tables script from this page and click on "Execute" (Figure 5) and (Figure 6).

    Database table script:

    CREATE TABLE ozekimessagein (
     id int IDENTITY (1,1),
     sender varchar(255),
     receiver varchar(255),
     msg nvarchar(160),
     senttime varchar(100),
     receivedtime varchar(100),
     operator varchar(30),
     msgtype varchar(30),
     reference varchar(30),
     );
     
    CREATE TABLE ozekimessageout (
     id int IDENTITY (1,1),
     sender varchar(255),
     receiver varchar(255),
     msg nvarchar(160),
     senttime varchar(100),
     receivedtime varchar(100),
     operator varchar(100),
     msgtype varchar(30),
     reference varchar(30),
     status varchar(30),
     errormsg varchar(250)
     );
     

    Figure 5 - SQL database table script

    execute query
    Figure 6 - Execute query

    If it is done, close "SQL Server Management Studio".

    Create a database user in Ozeki NG SMS Gateway

    To create a database user in Ozeki NG SMS Gateway, first you need to log into the gateway software. Then go to "Add new user or application". Select "Database user" and click on "Install" next to it (Figure 7).

    install database user
    Figure 7 - Install database user

    Provide a name for this user (Figure 8).

    give a unique sql user name
    Figure 8 - Give a unique SQL user name

    Configure the database connection for this SQL user in Ozeki NG SMS Gateway

    To setup this database connection select the connection string type.

    OleDb

    Then customize the following connection string:

    Provider=SQLNCLI11;Server=ServerAddress;Database=DatabaseName;Uid=UserName;Pwd=Password;

    Figure 9 is an example for a customized connection string.

    connection string
    Figure 9 - Connection string

    You can test this created connection if you click on "SQL Prompt" and you select from the dropdown menu:

    INSERT INTO ozekimessageout (receiver,msg,status) VALUES ('+36205460691','Hello World','send');

    After a short period of time, Ozeki NG SMS Gateway will notice the new row and send out your message.

    Related pages:

    International/Unicode characters with MSSQL

    This page explains in details how you can send international characters with Ozeki NG SMS Gateway in MSSQL. You will find how to configure an existing database to be able to send international characters and how to create a new database that supports Unicode characters.

    Create new MSSQL database table

    If you use MSSQL and you create a new database table, you need to use nvarchar instead of varchar in the fields where you want to use Unicode characters.

    How to configure an existing MSSQL database to send international characters

    If you already have created MSSQL database tables and you want this database table to support sending UNICODE characters via SMS, follow this configuration guide. You need to configure your MSSQL database to accept international characters such as Arabic, Chinese, etc.

    Configuration guide

    Start MSSQL Server Management Studio. Click on the database to be configured and select Properties (Figure 1).

    properties
    Figure 1 - Properties

    Then click on Options in the menu. In Collation section you can select the types of characters you want the database to accept. In this example I selected Arabic CI AI (Figure 2).

    specify characters
    Figure 2 - Specify characters

    Now in Tables section right click on ozekimessagein table and select Modify (Figure 3).

    modify tables
    Figure 3 - Modify tables

    Set msg field to nvarchar (Figure 4).

    select nvarchar
    Figure 4 - Select nvarchar

    Increase the size of messages from (50) to (160) and Save settings (Figure 5).

    increase size and save settings
    Figure 5 - Increase size and save settings

    Now do the same process with ozekimessageout table. So you need to right click on ozekimessageout table, select Modify, set msg field to nvarchar, increase size to (160) and save the changes.

    Test

    I created a test message containing Unicode characters (Arabic has been selected) and inserted it into ozekimessageout table (Figure 6).

    insert test message into ozekimessageout
    Figure 6 - Insert test message into ozekimessageout

    On Figure 7 you can see that Ozeki NG SMS Gateway sent out the test message (Figure 7)

    sent message in ozeki ng sms gateway
    Figure 7 - Sent message in Ozeki NG SMS Gateway

    SQL to SMS Gateway configuration - MySQL overview

    In this chapter you can learn how to configure the SMS gateway to be able to send and receive SMS messages using a MySQL database server. You will be provided with the installation steps, the configuration details such as the database connection string, database connection type, and with the recommended database table layout.

    To be able to send and receive SMS from a MySQL database you will need to install the MyODBC driver to your computer. This driver can be downloaded from the MySQL website. We recommended to use MyODBC v5.1, because it supports unicode characters.

    After the MyODBC driver has been installed on the computer, you need to configure a database user in the SMS Gateway.

    During the configuration the database connection type, you should choose is:

    Odbc

    The database connection string you should use is:

    Driver={MySQL ODBC 5.1 Driver};Server=127.0.0.1;Database=ozekisms;User=ozeki;Password=abc123;Option=4;

    For newer versions, you will need to update the driver name. For example if you install MySQL ODBC 8.0 you could use the following connection string:

    Driver={MySQL ODBC 8.0 Unicode Driver};Server=127.0.0.1;Database=test;User=test;Password=test;Option=4;

    Please note that the database connection string should be modified to match your database. You should replace the "127.0.0.1" ip address to the hostname or ip address of your database server. Replace "ozekisms" to the name of you database. Replace "ozeki" and "abc123" to the username and password that can be used to connect to your database server.

    The connection string and the connection type should be entered on the Database user configuration form.

    specifying the connection string for the mysql database
    Figure 1 - Specifying the connection string for the MySQL database

    After the database user has been configure in the SQL SMS gatway, the only thing left to do is to create the database tables ozekimessageout and ozekimessagin in your MySQL database. We recommend you to use the following table layout:

    MySQL create table script:

    CREATE TABLE ozekimessagein (
      	id int(11) NOT NULL auto_increment,
      	sender varchar(255) default NULL,
      	receiver varchar(255) default NULL,
      	msg text default NULL,
      	senttime varchar(100) default NULL,
      	receivedtime varchar(100) default NULL,
      	operator varchar(100) default NULL,
      	msgtype varchar(160) default NULL,
      	reference varchar(100) default NULL,
      	PRIMARY KEY (id)
      	) charset=utf8; 
      	
    ALTER TABLE ozekimessagein ADD INDEX (id);
    CREATE TABLE ozekimessageout (
      	id int(11) NOT NULL auto_increment,
      	sender varchar(255) default NULL,
      	receiver varchar(255) default NULL,
      	msg text default NULL,
      	senttime varchar(100) default NULL,
      	receivedtime varchar(100) default NULL,
      	reference varchar(100) default NULL,
      	status varchar(20) default NULL,
      	msgtype varchar(160) default NULL,
      	operator varchar(100) default NULL,
      	errormsg varchar(250) default NULL,
      	PRIMARY KEY (id)
      	) charset=utf8;
      	
    ALTER TABLE ozekimessageout ADD INDEX (id);

    It is strongly recommended to maintain an index in the database for the 'id' field of the outgoing SMS table to support faster SQL updates.

    If you wish you can add additional columns or you can modify these database tables. If you do please review the SQL templates used by the SMS gateway to make sure they will be compatible with the customized database table layout.

    SQL to SMS Gateway configuration - MyOdbc v8 installation

    If you wish to send and receive unicode characters (Chinese, Arabic, etc) in SMS messages from MySQL, you need to use the MySQL Odbc Driver v8 or newer. We also recommend you to use v8 or newer of the database server as well. This guide gives you some hints on how to install the newer driver

    Step 1: Download the driver from mysql.com:

    http://dev.mysql.com/downloads/connector/odbc/

    We recommend you to use the Windows MSI Installer version. It is easy to setup. During installation, all you have to do is click Next, whenever a new form comes up. Finally click Finish. You can see the download window on Figure 1.

    download myodbc
    Figure 1 - Download MyODBC 8

    Step 2: Configure the new connection string

    Use the following connection string in the database user configuration form to connect to your mysql database. Do not forget to change the database name, the username and the password to reflect the settings of your system.

    Driver={MySQL ODBC 8.0.23 Driver};Server=127.0.0.1;Database=ozekisms;User=ozeki;Password=abc123;Option=4;
    

    This connection string is an ODBC connection string, so you should select ODBC for connection string type (Figure 2).

    myodbc connection string type
    Figure 2 - MyODBC Connection String type

    SQL to SMS Gateway configuration - MySQL table definition

    This page gives you the database table layout if you want to setup an SQL to SMS Gateway configuration for MySQL. The tables defined here can be used as a startup. If you wish you can add extra columns to these tables or you can create custom tables.

    If you want to change these table definitions to support your requirements, do not forget to review the SQL templates that are used by the SMS gateway to work with these tables. The following guide gives you information on how to view and modify the SQL templates:

    SQL to SMS Gateway configuration - SQL templates

    The recommended database table layout for MySQL contains two database tables called ozekimessagout and ozekimessagein. Their definitions are displayed in Figure 1.

    CREATE TABLE ozekimessagein (
      	id int(11) NOT NULL auto_increment,
      	sender varchar(255) default NULL,
      	receiver varchar(255) default NULL,
      	msg varchar(160) default NULL,
      	senttime varchar(100) default NULL,
      	receivedtime varchar(100) default NULL,
      	operator varchar(100) default NULL,
     	msgtype varchar(160) default NULL,
      	reference varchar(100) default NULL,
      	PRIMARY KEY (id)) 
      	charset=utf8;
    	
    ALTER TABLE ozekimessagein ADD INDEX (id) ;
    CREATE TABLE ozekimessageout (
      	id int(11) NOT NULL auto_increment,
      	sender varchar(255) default NULL,
      	receiver varchar(255) default NULL,
      	msg varchar(160) default NULL,
      	senttime varchar(100) default NULL,
      	receivedtime varchar(100) default NULL,
      	reference varchar(100) default NULL,
      	status varchar(20) default NULL,
      	msgtype varchar(160) default NULL,
      	operator varchar(100) default NULL,
      	errormsg varchar(250) default NULL,
      	PRIMARY KEY (id)) 
      	charset=utf8;
      	
    ALTER TABLE ozekimessageout ADD INDEX (id);

    Figure 1 - MySQL table definition for SQL to SMS gateway configuration

    MyODBC Driver Installation and Configuration

    On this page you can find out how to install and configure a MyODBC 8 driver for Ozeki NG - SMS Gateway to allow SMS messaging.

    To configure database connectivity in Ozeki NG - SMS Gateway, you need to set up an ODBC driver. To install and configure a MyODBC driver (for a MySQL database), follow the instructions below. The installation and configuration of other database drivers is similar to the process described here.

    Download the MyODBC database driver from the Internet. You can use the following link: http://dev.mysql.com/downloads/connector/odbc/

    Install the downloaded MyODBC database driver by starting the downloaded exe file. The installation is similar to the installation of any Windows application. Click the Next and the OK button to get from one dialog box to the next and to finish the installation.

    When the driver is available on your system, you need to set up a data source. Open Start menu and start typing ODBC. The first result should be the ODBC Data Source. Click it to open the ODBC Data Source Administrator panel, which is part of Windows (Figure 1).

    opening the odbc data source administration panel
    Figure 1 - Opening the ODBC Data Source Administrator panel

    In the ODBC Data Source Administrator panel, you have to define a datasource. Click the User DSN Tab (it is the default tab), and click Add as shown in the figure below. This will bring up the "Create New Datasource" dialog box (Figure 2).

    opening the create new datasource dialog box
    Figure 2 - Opening the Create New Datasource dialog box

    In this form (Figure 3) select the (newly installed) driver, and click Finish. In most cases, when you click Finish, a database server specific configuration form comes up. (You can also open this configuration form by double-clicking the selected driver.)

    select the newly created driver
    Figure 3 - Select the newly created driver

    In the database configurator, which can be seen on Figure 4, you need to provide the following data:

      In the Data Source Name box, enter the name of the data source you want to access. It can be any valid name that you choose.
    • In the Port box, enter the port number if it is not the default (3306).
    • In the User box, enter your MySQL username (your database user ID).
    • In the Password box, enter your password.
    • In the Database dropdown menu, select the database to be current upon connect

    the configuration form
    Figure 4 - The configuration form

    When configuring a MySQL database user in Ozeki NG - SMS Gateway, you have to specify the database connection string in the Database connection tab. Include the configuration specifications of your ODBC driver in the connection string (Figure 5).

    specifying the connection string for the mysql database
    Figure 4 - Specifying the connection string for the MySQL database

    For more information about the configuration of a MySQL user for SMS messaging using Ozeki NG - SMS Gateway, check out the MySQL User page.

    You can find database connection strings for a wide range of different databases In Appendix B - Connection Strings.

    How to send SMS messages from Oracle

    In this guide you can learn how to send and receive SMS messages using an Oracle database. This guide is an extension of the general SQL to SMS configuration guide. It contains Oracle specific information. It is assumed, that you already have an Oracle database server and the Oracle client components installed. You also need Ozeki NG SMS Gateway installed on your system to have this example work.

    In order to be able to send and receive SMS messages from Oracle, you need to install and appropriately configure Ozeki NG - SMS Gateway. Ozeki NG SMS Gateway can send and receive SMS messages through a GSM phone or GSM modem that is attached to your computer with a phone-to-pc data cable or through IP SMS service provider connections over the Internet, such as SMPP, CIMD2 or UCP/EMI connections. After one of these connections is set up, you need to install a Database user in the "Users and Applications" menu of Ozeki NG. Once the Database user is installed and configured properly, you will be able to send SMS messages from Oracle simply by inserting a record into a database table, and incoming SMS messages will be saved into another database table in your Oracle database server.

    To configure the database user in Ozeki NG, please use the following information:

    Connection string type:Oracle
    Connection string:Data Source=127.0.0.1; User ID=username; Password=pwd123;

    (Alternative connection strings for Oracle can be found at the Oracle connections strings page)

    Of course you have to replace the 127.0.0.1 IP address to the IP address or the Data source name of your Oracle database server, and the username and pwd123 field to the database username and database password that matches your user account information stored in Oracle.

    Once the connection is configured in Ozeki NG, all you have to do is create two database tables in your Oracle database according to the following table definition.

    Oracle create table script:

    CREATE TABLE ozekimessagein (
        id int,
        sender varchar(255) default NULL,
        receiver varchar(255) default NULL,
        msg varchar(160) default NULL,
        senttime varchar(100) default NULL,
        receivedtime varchar(100) default NULL,
        operator varchar(120) default NULL,
        msgtype varchar(160) default NULL,
        reference varchar(100) default NULL
        );
        CREATE index index_id ON ozekimessagein(id);
        CREATE SEQUENCE X;
        CREATE TRIGGER ozekimessagein_auto BEFORE INSERT on ozekimessagein
        for each row
        when (new.id is null)
        begin
        SELECT x.nextval INTO :new.id FROM DUAL;
        end;
    CREATE TABLE ozekimessageout (
        id int,
        sender varchar(255) default NULL,
        receiver varchar(255) default NULL,
        msg varchar(160) default NULL,
        senttime varchar(100) default NULL,
        receivedtime varchar(100) default NULL,
        operator varchar(120) default NULL,
        msgtype varchar(160) default NULL,
        reference varchar(100) default NULL,
        status varchar(20) default NULL,
        errormsg varchar(250) default NULL
        );
        CREATE index index_id2 ON ozekimessageout(id);
        CREATE SEQUENCE Y;
        CREATE TRIGGER ozekimessageout_auto BEFORE INSERT on ozekimessageout
        for each row
        when (new.id is null)
        begin
        SELECT y.nextval INTO :new.id FROM DUAL;
        end;

    If you want to work with larger messages, you can increase the size of the msg field, or you may also change it's data type.

    It is strongly recommended to maintain an index in the database for the 'id' field of the outgoing SMS table to support SQL updates.

    If you want to use unicode characters, you should use NVARCHAR2 as the datatype, you should put "Unicode=True" into the connection string and you should make sure that the NLS_CHARACTERSET and NLS_LANGUAGE parameters for your database are set to your language. You may also try to set the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID\NLS_LANG to UTF8

    Note: Oracle 8i clients cannot access NVARCHAR2 data in Oracle 9i databases when the server's national character set is specified as AL16UTF16 (the default setting for Oracle 9i). Because support for the UTF-16 character set was not introduced until Oracle 9i, Oracle 8i clients cannot read it.

    Connection strings for Oracle

    This page lists alternative connection strings you can use with Oracle database.

    .NET Oracle provider.

    For Standard security:

    Connection string type:Oracle
    Connection string:Data Source=MyOracleDB; User Id=myUsername;Password=myPassword;

    For a Trusted connection:

    OS Authenticated connect setting user ID to "/":

    Connection string type:Oracle
    Connection string:Data Source=MyOracleDB;User Id=/;Password=;

    OS Authenticated connect using OSAuthent:

    Connection string type:Oracle
    Connection string:Data Source=MyOracleDB;OSAuthent=1;

    Note: "Data Source=" must be set to the appropriate Net8 name which is known to the naming method in use. For example, for Local Naming, it is the alias in the tnsnames.ora file; for Oracle Names, it is the Net8 Service Name.

    ODBC Driver for Oracle

    For the current Oracle ODBC driver from Microsoft:

    Connection string type:ODBC
    Connection string:Driver={Microsoft ODBC for Oracle};Server=OracleServer.world; Uid=MyUsername;Pwd=MyPassword;

    For the older Oracle ODBC driver from Microsoft:

    Connection string type:ODBC
    Connection string:Driver={Microsoft ODBC Driver for Oracle};ConnectString=OracleServer.world;Uid=myUsername;Pwd=myPassword;

    OLE DB Provider for Oracle (from Oracle).

    For Standard security:

    Connection string type:OleDb
    Connection string:Provider=OraOLEDB.Oracle;Data Source=MyOracleDB; User Id=myUsername;Password=myPassword;/td>

    For a Trusted connection:

    OS Authenticated connect setting user ID to "/":

    Connection string type:OleDb
    Connection string:Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=/;Password=;

    OS Authenticated connect using OSAuthent:

    Connection string type:OleDb
    Connection string:Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;OSAuthent=1;

    Note: "Data Source=" must be set to the appropriate Net8 name which is known to the naming method in use. For example, for Local Naming, it is the alias in the tnsnames.ora file; for Oracle Names, it is the Net8 Service Name.

    How to send SMS from Oracle 10G XE

    If you have downloaded and installed Ozeki NG SMS Gateway you can send SMS text messages from Oracle 10G XE with the use of this software product. To achieve this solution you need to configure Ozeki NG SMS Gateway to be able to send out messages from your database. Please find detailed configuration instructions on this page with helpful screenshots.

    Ozeki NG SMS Gateway is a powerful software product that can be installed to your computer. As it is a two-way SMS gateway, it allows you to send SMS messages from PC to mobile phones, and receive text messages from phones to PC. This software is also support sending messages from databases such as Oracle.

    To be able to send and receive SMS messages from Oracle 10G XE first you need to create two database tables: "ozekimessagein" and "ozekimessageout". You can find the instructions on this process on this page. The SMS gateway will use SQL queries for sending messages.

    Ozeki NG SMS Gateway needs to be connected to the mobile network. You can do this in two ways: you can attach a GSM modem to the PC with a datacable (GSM connectivity) or the SMS gateway can connect directly to the SMS center of the mobile service provider over the Internet (IP SMS connectivity).

    You can configure Ozeki NG SMS Gateway with the help of the Graphical User Interface (GUI).

    Configuration steps

    To configure your SMS system first you need to install Oracle 10G XE to your computer. Then log into it on the web interface (Figure 1).

    log into oracle
    Figure 1 - Log into Oracle

    Click on "SQL" button (Figure 2).

    click on sql button
    Figure 2 - Click on SQL button

    Select "SQL commands" button (Figure 3).

    select sql commands
    Figure 3 - Select SQL commands

    Now specify SQL commands. Enter the following statements to create the table layouts (Figure 4-11).

    CREATE TABLE ozekimessagein (
        id int,
        sender varchar(255) default NULL,
        receiver varchar(255) default NULL,
        msg varchar(160) default NULL,
        senttime varchar(100) default NULL,
        receivedtime varchar(100) default NULL,
        operator varchar(120) default NULL,
        msgtype varchar(160) default NULL,
        reference varchar(100) default NULL
        )

    specify sql statement
    Figure 4 - Specify SQl statement

    CREATE index index_id1 ON ozekimessagein(id)

    specify sql statement
    Figure 5 - Specify SQl statement

    CREATE SEQUENCE X

    specify sql statement
    Figure 6 - Specify SQl statement

    CREATE TRIGGER ozekimessagein_auto BEFORE INSERT on ozekimessagein
        for each row
        when (new.id is null)
        begin
        SELECT x.nextval INTO :new.id FROM DUAL;
        end

    specify sql statement
    Figure 7 - Specify SQl statement

    CREATE TABLE ozekimessageout (
        id int,
        sender varchar(255) default NULL,
        receiver varchar(255) default NULL,
        msg varchar(160) default NULL,
        senttime varchar(100) default NULL,
        receivedtime varchar(100) default NULL,
        operator varchar(120) default NULL,
        msgtype varchar(160) default NULL,
        reference varchar(100) default NULL,
        status varchar(20) default NULL,
        errormsg varchar(250) default NULL
        )

    specify sql statement
    Figure 8 - Specify SQl statement

    CREATE index index_id2 ON ozekimessageout(id)

    specify sql statement
    Figure 9 - Specify SQl statement

    CREATE SEQUENCE Y

    specify sql statement
    Figure 10 - Specify SQl statement

    CREATE TRIGGER ozekimessageout_auto BEFORE INSERT on ozekimessageout
        for each row
        when (new.id is null)
        begin
        SELECT y.nextval INTO :new.id FROM DUAL;
        end

    specify sql statement
    Figure 11 - Specify SQl statement

    Now log into Ozeki NG SMS Gateway with your username and password and click on "Add new user or application" to create a new database user (Figure 12).

    add new user or application
    Figure 12 - Add new user or application

    Select "Database user interface" in the list and click on "Install" next to it (Figure 13).

    select and install user
    Figure 13 - Select and install user

    Provide a name for the created database user (e.g. oracle) and click on "OK" (Figure 14).

    provide a name
    Figure 14 - Provide a name

    In "Database connection" tab you need to specify the follows (Figure 15):

    Connection string type: "OleDb"
    Connection string:

    Provider=OraOLEDB.Oracle.1;Persist Security Info=False;User ID=SYSTEM;Password=qwe123

    database connection tab
    Figure 15 - Database connection tab

    Test

    Now to test the system I will enter an SQL query. I select "INSERT INTO ozekimessageout (receiver, msg, status) VALUES ('+36205460691','Hello World','send')" from the list. Remove the semicolon and click on "Execute" (Figure 16).

    sql query
    Figure 16 - SQL query

    On Figure 17 you can see the sent message in "Sent" folder of Ozeki NG SMS Gateway.

    sent message
    Figure 17 - Sent message

    If I query "ozekimessageout" table with "SELECT * from ozekimessageout" statement then the status of the message will be updated (Figure 18).

    status has been updated
    Figure 18 - Status has been updated

    How to test your oracle connection

    After you have successfully configured your Oracle database link, you might want to send several test SMS messages to test the functionality and the performance of Ozeki SMS Gateway. To do this you may use the following SQL query in Oracle.

    How to send text messages from Oracle in a loop

    In order to send several SMS messagse for testing, the best option is to write a loop in Oracle that will insert multiple records into the outgoing SMS table. To write a loop, you need to use the BEGIN and END commands and use teh FOR IN LOOP statements. Take a look at the following example:

    BEGIN
        FOR v_LoopCounter IN 1..1000 LOOP
    	  INSERT INTO ozekimessageout (receiver, msg, status) 
    	  VALUES ('+36209355418', concat('test',TO_CHAR(v_LoopCounter)), 'send');
            COMMIT;
        END LOOP;
    END;
    

    Send SMS messages from Sybase / SQL Anywhere

    In this chapter you can learn how to send and receive SMS messages using a Sybase SQL Anywhere database with the Ozeki NG - SMS Gateway software. You will be provided with the connection string and the create table script.

    Ozeki NG - SMS Gateway allows you to send and receive SMS messages using a database server with the help of SQL queries. The software supports, among others, the Sybase SQL Anywhere database.

    For SMS messaging with a Sybase SQL Anywhere database you need to install and appropriately configure a database user in the Ozeki NG - SMS Gateway program. Also, you need a Sybase SQL Anywhere database server, in which you have to create an ozekimessageout and an ozekimessagein table for outgoing and incoming messages.

    You can install and configure a Sybase SQL Anywhere user on the graphical user interface of the software. The installation and configuration of a Sybase SQL Anywhere user is similar to that of any other database user.

    To find out how to install and configure a database user, check out the Database User section.

    As the Sybase SQL Anywhere database does not require Open DataBase Connectivity (ODBC), select OleDb in the Connection string type dropdown menu.

    Replace the default database connection string with the one for the Sybase SQL Anywhere database in the Connection string template (Figure 1):

    Provider=ASAProv.90;UID=MyUsername;PWD=MyPassword;DatabaseFile= DatabaseFileLocationOnYourComputer.db;EngineName=Yourdbenginename;Start= YourDatabaseBinaryLocation.exe -c 32M;AutoStop=Yes

    Modify the variables in the connection string according to your needs.

    specifying the connection string for the oracle database
    Figure 1 - Specifying the connection string for the Oracle database

    You can create the ozekimessageout and ozekimessagein tables in Sybase SQL Anywhere using the following script.

    Sybase SQL Anywhere create table script:

    CREATE TABLE "ozekimessagein"
    "id" integer NOT NULL DEFAULT autoincrement ,
    "sender" varchar(255) NULL ,
    "receiver" varchar(255) NULL ,
    "msg" varchar(160) NULL ,
    "senttime" varchar(100) NULL ,
    "receivedtime" varchar(100) NULL ,
    "operator" varchar(100) NULL ,
    "msgtype" varchar(160) NULL ,
    "reference" varchar(100) NULL ,
    PRIMARY KEY ("id"),
    
    )
    go
    commit work
    go
    CREATE TABLE "ozekimessageout"
    (
    "id" integer NOT NULL DEFAULT autoincrement ,
    "sender" varchar(255) NULL ,
    "receiver" varchar(255) NULL ,
    "msg" varchar(160) NULL ,
    "senttime" varchar(100) NULL ,
    "receivedtime" varchar(100) NULL ,
    "operator" varchar(100) NULL ,
    "status"  NULL ,
    "msgtype" varchar(160) NULL ,
    "reference" varchar(100) NULL ,
    "errormsg" varchar(250) NULL ,
    PRIMARY KEY ("id"),
    )
    go
    commit work
    go
    
    CREATE INDEX "ozekimessageinindex" ON "ozekimessagein"
    (
    "id" ASC
    )
    go
    commit work
    go
    
    CREATE INDEX "ozekimessageoutindex" ON "ozekimessageout"
    (
     "id" ASC
    )
    go
    commit work
    go
    

    If you want to work with larger messages, you can increase the size of the msg field, or you may also change it's data type.

    It is strongly recommended to maintain an index in the database for the 'id' field of the outgoing SMS table to support SQL updates.

    How to send SMS from PostgreSQL

    This guide explains how you can send texts from PostgreSQL. It will start with defining what PostgreSQL is and will proceed to the explanation of how it can be used. PostgreSQL is a great tool to send sms, it can be used in various environments. Maybe the greatest benefit of this PostgreSQL solution is that all you have to do is perform some basic configuration and you will be ready to send texts in a short period of time. This solution is based on Ozeki NG SMS Gateway, so you can benefit from that fact that it is high performance, meaning it can send up to 1000 SMS per second. You will be provided with the connection string for the PostgreSQL database, instructions on the ODBC driver installation, with a link to a PostgreSQL database driver download page, and the create table script. We presume your are familiar with the basics of SMS technology. We hope you will find the presented insights beneficial.

    What is PostgreSQL

    PostgreSQL is a database server. PostgreSQL can be used to store business data in database tables. It is often used with Ozeki NG SMS Gateway.

    How to send sms from PostgreSQL (Quick instructions)

    To send sms from PostgreSQL:

    1. Go to ozekisms.com
    2. Click on download to download Ozeki NG SMS Gateway
    3. Extract the files from the zip
    4. Install the downloaded exe file
    5. Start the Ozeki management console
    6. Navigate to 'Add' in the 'Users and applications' panel
    7. Locate the Database connection, click install
    8. Ozeki NG SMS Gateway will send the text messages over this link
    9. Configure PostgreSQL connection using the configuration form
    10. To send texts, use the Test tab
    11. Type in the recipient, the text and click send
    12. Check the event log to see if your texts was sent

    how to send sms from postgresql
    Figure 1 - How to send SMS from PostgreSQL

    Detailed configuration instructions

    Ozeki NG - SMS Gateway allows you to send and receive SMS messages using a database server with the help of SQL queries. The software supports, among others, the PostgreSQL database.

    For SMS messaging with a PostgreSQL database you need to install and appropriately configure a database user in the Ozeki NG - SMS Gateway program. Also, you need a PostgreSQL database server, in which you have to create an ozekimessageout and an ozekimessagein table for outgoing and incoming messages.

    You can install and configure a PostgreSQL user on the graphical user interface of the software. The installation and configuration of a PostgreSQL user is similar to that of any other database user.

    To find out how to install and configure a database user, check out the Database User page.

    As the PostgreSQL database requires Open DataBase Connectivity (ODBC), select Odbc in the Connection string type dropdown menu (Figure 1).

    Replace the default database connection string with the one for the PostgreSQL database in the Connection string template (Figure 1):

    DRIVER={PostgreSQL};
    SERVER=YourServerIP;port=5432;DATABASE=YourDatabaseName;UID=YourUsername;PWD=YourPassword
    

    Modify the variables in the connection string according to your needs.

    specifying the connection string for the mysql database
    Figure 1 - Specifying the connection string for the MySQL database

    ODBC Driver Installation

    As mentioned above, for using a PostgreSQL database you need Open DataBase Connectivity between your database server and Ozeki NG - SMS Gateway.

    For this connectivity, you need to set up an ODBC driver. The PostgreSQL driver is called psqlODBC.

    Installation of the psqlODBC driver

    Download the psqlODBC database driver from the Internet. You can use the following link:

    http://pgfoundry.org/projects/psqlodbc/

    Install the downloaded psqlODBC database driver by launching the downloaded exe file. The installation is similar to that of any Windows application. To move from one dialog box to the next, just click the Next and the OK button during the setup.

    You can create the ozeki message tables in Postgre SQL using the following script.

    Postgre SQL create table script:

    CREATE TABLE ozekimessagein
    (
    id serial,
    sender varchar(255),
    receiver varchar(255),
    msg varchar(160),
    senttime varchar(100),
    receivedtime varchar(100),
    operator varchar(100),
    msgtype varchar(160),
    reference varchar(100)
    );
    
    CREATE TABLE ozekimessageout
    (
    id serial,
    sender varchar(255),
    receiver varchar(255),
    msg varchar(160),
    senttime varchar(100),
    receivedtime varchar(100),
    reference varchar(100),
    status varchar(20),
    operator varchar(100),
    errormsg varchar(250),
    msgtype varchar(160)
    );

    If you want to work with larger messages, you can increase the size of the msg field, or you may also change it's data type.

    It is strongly recommended to maintain an index in the database for the 'id' field of the outgoing SMS table to support SQL updates. Postgre SQL creates index fields by default.

    How to send SMS text messages from Pervasive SQL

    This guide provides you information on how to send and receive SMS text messages using Pervasive SQL with Ozeki NG SMS Gateway. You need to download and install Ozeki NG SMS Gateway to your computer and then create a database user in the software. Please find a more detailed configuration guide below.

    1. Step: Install Pervasive SQL
    2. Step: Start Pervasive Control Center and Documentation
    3. Step: Click on Create a new SQL document option
    4. Step: Select the database in which you wish to create database tables
    5. Step: Insert Create table script

    CREATE TABLE "ozekimessagein"(
     "id" IDENTITY DEFAULT '0',
     "sender" VARCHAR(255),
     "receiver" VARCHAR(255),
     "msg" VARCHAR(320),
     "senttime" VARCHAR(100),
     "receivedtime" VARCHAR(100),
     "operator" VARCHAR(100),
     "msgtype" VARCHAR(160),
     "reference" VARCHAR(100),
     PRIMARY KEY ("id")
    );
    
    CREATE TABLE "ozekimessageout"(
     "id" IDENTITY DEFAULT '0',
     "sender" VARCHAR(255),
     "receiver" VARCHAR(255),
     "msg" VARCHAR(320),
     "senttime" VARCHAR(100),
     "receivedtime" VARCHAR(100),
     "reference" VARCHAR(100),
     "status" VARCHAR(50),
     "msgtype" VARCHAR(160),
     "operator" VARCHAR(100),
     "errormsg" VARCHAR(250),
     PRIMARY KEY ("id")
    );

    1. Step: In SQL menu click on Execute all SQL statements option
    2. Step: Start Ozeki NG SMS Gateway and create a database user
    3. Step: Set Connection string type to OleDb and insert the connection string in Database connection tab

    Provider=PervasiveOLEDB.;Data Source=DataBaseName;User
    ID=UserName;Location=DBHostName;Persist Security Info=False
    

    In this example I used the following parameters (Figure 1):

    • Database name: OZEKI
    • Username: test
    • Location: localhost

    In the connection string please specify YOUR values.

    Figure 1 - Specify connection string

    Date Format Strings to be used in SQL SMS configurations

    This page provides you with date format strings you can use if you want to change the default date format string in the configuration of the Database user of the Ozeki NG - SMS Gateway software.

    When configuring the Database user of Ozeki NG - SMS Gateway, you can specify the date format string used to create the date value for the SQL statements. (See Figure 5 and the instructions below it on the Database User page.)

    If you would like to change the default date format string (dd/mm/yyyy hh:mm:ss) in the Database connection tab of the Database user, you can use any of the date format strings below.

    You can use a hyphen (-), a period (.), a slash (/) or a space ( ) character to separate format specifiers.

    The following formatting characters can be used for date and time formatting:
     
    d Represents the day of the month as a number from 1 through 31. A single-digit day is formatted without a leading zero.
    dd Represents the day of the month as a number from 01 through 31. A single-digit day is formatted with a leading zero.
    ddd Represents the abbreviated name of the day of the week: "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", and "Sat".
    dddd (plus any number of additional "d" specifiers) Represents the full name of the day of the week: "Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", and "Saturday".
    f Represents the most significant digit of the seconds fraction.
    ff Represents the two most significant digits of the seconds fraction.
    fff Represents the three most significant digits of the seconds fraction.
    ffff Represents the four most significant digits of the seconds fraction.
    fffff Represents the five most significant digits of the seconds fraction.
    ffffff Represents the six most significant digits of the seconds fraction.
    fffffff Represents the seven most significant digits of the seconds fraction.
    F Represents the most significant digit of the seconds fraction. Nothing is displayed if the digit is zero.
    FF Represents the two most significant digits of the seconds fraction. However, trailing zeros, or two zero digits, are not displayed.
    FFF Represents the three most significant digits of the seconds fraction. However, trailing zeros, or three zero digits, are not displayed.
    FFFF Represents the four most significant digits of the seconds fraction. However, trailing zeros, or four zero digits, are not displayed.
    FFFFF Represents the five most significant digits of the seconds fraction. However, trailing zeros, or five zero digits, are not displayed.
    FFFFFF Represents the six most significant digits of the seconds fraction. However, trailing zeros, or six zero digits, are not displayed.
    FFFFFFF Represents the seven most significant digits of the seconds fraction. However, trailing zeros, or seven zero digits, are not displayed.
    g or gg (plus any number of additional "g" specifiers) Represents the period or era (A.D. for example). This specifier is ignored if the date to be formatted does not have an associated period or era string.
    h Represents the hour as a number from 1 through 12, that is, the hour as represented by a 12-hour clock that counts the whole hours since midnight or noon. Consequently, a particular hour after midnight is indistinguishable from the same hour after noon. The hour is not rounded, and a single-digit hour is formatted without a leading zero. For example, given a time of 5:43, this format specifier displays "5".
    hh, hh (plus any number of additional "h" specifiers) Represents the hour as a number from 01 through 12, that is, the hour as represented by a 12-hour clock that counts the whole hours since midnight or noon. Consequently, a particular hour after midnight is indistinguishable from the same hour after noon. The hour is not rounded, and a single-digit hour is formatted with a leading zero. For example, given a time of 5:43, this format specifier displays "05".
    H Represents the hour as a number from 0 through 23, that is, the hour as represented by a zero-based 24-hour clock that counts the hours since midnight. A single-digit hour is formatted without a leading zero.
    HH, HH (plus any number of additional "H" specifiers) Represents the hour as a number from 00 through 23, that is, the hour as represented by a zero-based 24-hour clock that counts the hours since midnight. A single-digit hour is formatted with a leading zero.
    m Represents the minute as a number from 0 through 59. The minute represents whole minutes passed since the last hour. A single-digit minute is formatted without a leading zero.
    mm, mm (plus any number of additional "m" specifiers) Represents the minute as a number from 00 through 59. The minute represents whole minutes passed since the last hour. A single-digit minute is formatted with a leading zero.
    M Represents the month as a number from 1 through 12. A single-digit month is formatted without a leading zero.
    MM Represents the month as a number from 01 through 12. A single-digit month is formatted with a leading zero.
    MMM Represents the abbreviated name of the month: "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov" and "Dec".
    MMMM Represents the full name of the month: "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November" and "December".
    s Represents the seconds as a number from 0 through 59. The second represents whole seconds passed since the last minute. A single-digit second is formatted without a leading zero.
    ss, ss (plus any number of additional "s" specifiers) Represents the seconds as a number from 00 through 59. The second represents whole seconds passed since the last minute. A single-digit second is formatted with a leading zero.
    t Represents the first character of the A.M./P.M. designator. The A.M. designator is used if the hour in the time being formatted is less than 12; otherwise, the P.M. designator is used.
    tt, tt (plus any number of additional "t" specifiers) Represents the A.M./P.M. designator. The A.M. designator is used if the hour in the time being formatted is less than 12; otherwise, the P.M. designator is used.
    y Represents the year as at most a two-digit number. If the year has more than two digits, only the two low-order digits appear in the result. If the year has fewer than two digits, the number is formatted without a leading zero.
    yy Represents the year as a two-digit number. If the year has more than two digits, only the two low-order digits appear in the result. If the year has fewer than two digits, the number is padded with leading zeroes to achieve two digits.
    yyy Represents the year as a three-digit number. If the year has more than three digits, only the three low-order digits appear in the result. If the year has fewer than three digits, the number is padded with leading zeroes to achieve three digits.

    Note that for the Thai Buddhist calendar, which can have five-digit years, this format specifier displays all five digits.
    yyyy Represents the year as a four-digit number. If the year has more than four digits, only the four low-order digits appear in the result. If the year has fewer than four digits, the number is padded with leading zeroes to achieve four digits.

    Note that for the Thai Buddhist calendar, which can have five-digit years, this format specifier renders all five digits.
    yyyyy (plus any number of additional "y" specifiers) Represents the year as a five-digit number. If the year has more than five digits, only the five low-order digits appear in the result. If the year has fewer than five digits, the number is padded with leading zeroes to achieve five digits.

    If there are additional "y" specifiers, the number is padded with as many leading zeroes as necessary to achieve the number of "y" specifiers.
    z Represents the signed time zone offset of your system from Greenwich Mean Time (GMT) measured in hours. For example, the offset for a computer in the Pacific Standard Time zone is "-8".

    The offset is always displayed with a leading sign. A plus sign (+) indicates hours ahead of GMT and a minus sign (-) indicates hours behind GMT. The offset ranges from -12 through +13. A single-digit offset is formatted without a leading zero. The offset is affected by daylight savings time.
    zz Represents the signed time zone offset of your system from Greenwich Mean Time (GMT) measured in hours. For example, the offset for a computer in the Pacific Standard Time zone is "-08".

    The offset is always displayed with a leading sign. A plus sign (+) indicates hours ahead of GMT and a minus sign (-) indicates hours behind GMT. The offset ranges from -12 through +13. A single-digit offset is formatted with a leading zero. The offset is affected by daylight savings time.
    zzz, zzz (plus any number of additional "z" specifiers) Represents the signed time zone offset of your system from Greenwich Mean Time (GMT) measured in hours and minutes. For example, the offset for a computer in the Pacific Standard Time zone is "-08:00".

    The offset is always displayed with a leading sign. A plus sign (+) indicates hours ahead of GMT and a minus sign (-) indicates hours behind GMT. The offset ranges from -12 through +13. A single-digit offset is formatted with a leading zero. The offset is affected by daylight savings time.
    : The time separator.
    / The date separator.
    " Quoted string (quotation mark). Displays the literal value of any string between two quotation marks (").
    ' Quoted string (apostrophe). Displays the literal value of any string between two apostrophe (') characters.
    \c The escape character. Displays the character "c" as a literal when that character is preceded by the escape character (\).
    Any other character Any other character is copied to the result string, and does not affect formatting.

    How to schedule SMS messages for sending

    If you use the SQL-SMS gateway configuration of Ozeki NG SMS Gateway, you can schedule your SMS message sendings in a very simple way. Scheduling means that you set a specific date and time for a message to determine when should it be sent.

    Setup scheduled SMS sending (table layout)

    To configure this option, first you need to modify your ozekimessageout table definition to include an extra column for the scheduled delivery time. You can call this column "scheduledtime". To modify the table definition issue the following SQL command in an SQL console:

    alter table ozekimessageout add column scheduledtime
    

    MySQL:
    ALTER TABLE `ozekimessageout` ADD `scheduledtime` DATETIME NULL AFTER `errormsg`;
    

    Setup scheduled SMS sending (configure Ozeki NG)

    After the table layout has been modified, you need to open the database user configuration of Ozeki NG. The configuration modification is simple: you need to modify the SQL query used for selecting messages to be sent (Figure 1). This can be done by clicking on the "SQL for Sending" tab of the SQL user configuration form and changing the "Polling" query to this:

    SELECT
       id,sender,receiver,msg,msgtype,operator
    FROM
       ozekimessageout
    WHERE
       status='send' and scheduledtime<now()
    

    Notice the added where condition that will only select messages that can be sent from the database.

    Figure 1 - How to configure scheduled SMS sending

    After this is configured, to send a scheduled SMS message all you have to do is specify the datetime value in the ozekimessagout table.

    SQL to SMS Gateway configuration - SQL templates

    This section gives you information on how you can customize the SQL commands used to access your database tables. The information presented here is helpful if you wish to setup an SQL to SMS gateway configuration and you wish to alter the default database table layout.

    Default operation of the SMS gateway

    By default the SMS gateway uses two database tables. One of the tables (ozekimessagein) is used for receiving SMS messages. The other (ozekimessagout) is used sending SMS messages . If an SMS message arrives to your gateway, it will be inserted to the ozekimessagin database table using the following SQL command:

    INSERT INTO ozekimessagein (sender, receiver, msg, senttime, receivedtime, msgtype, operator) VALUES ('$originator','$recipient','$messagedata','$senttime','$receivedtime','$messagetype','$operatornames')

    Before this statement is executed by the SMS gateway the keywords (e.g.: $originator, $recipient,...) will be replaced to the corresponding values of the incoming SMS message.

    If you want to send an SMS message, you have to create a record in the ozekimessagout table. The status of the message should be set to "send". The SMS gateway will read the ozekimessagout table using the following SQL query to find your message:

    SELECT id,sender,receiver,msg,msgtype,operator FROM ozekimessageout WHERE status='send'

    After you outgoing SMS messages has been successfully fetched, the record will be updated using the following SQL command:

    UPDATE ozekimessageout SET status='sending' WHERE id='$id'

    This indicates that your SMS messages has been accepted for delivery by the SMS gateway and is saved into the outbox of the SMS gateway. Some time after this the following events can happen to your message:

    1. delivered to network
    2. delivery to network is not possible
    3. delivered to handset
    4. delivery to handset is not possible

    Depending which one of these events occur one of the following SQL commands will be executed on your database record:

    If the "delivered to network" event occurs:

    UPDATE ozekimessageout SET status='sent', senttime='$senttime' WHERE id='$id'

    If the "delivery to network is not possible" event occurs: UPDATE ozekimessageout SET status='notsent' WHERE id='$id'

    If the "delivered to handset" event occurs: UPDATE ozekimessageout SET status='delivered' WHERE id='$id'

    If the "delivery to handset is not possible" event occurs: UPDATE ozekimessageout SET status='undelivered' WHERE id='$id'

    If the status of the message stays in "sending", it indicates, that the Ozeki software has read the message from the database. The message was accepted for delivery and was stored in the outbox folder, but it was not yet accepted by the mobile network operator. It means that it is "waiting for delivery". In this case, if you look at the Graphical User Interface (GUI) of Ozeki NG, you should see the message in your outbox.

    If the status of the message stays in "sending" for a long time, it is highly probable that the messages are not delivered because the mobile network connection is not functioning in your system. To resolve this issue, please check if the service provider connection's link (SMPP, UCP, CIMD2) is working.

    Customized operation of the SMS Gateway

    To change this behavior, you should modify the SQL templates used by the SMS gateway. This can be done by opening the "SQL for sending" or the "SQL for receiving" tab of the "Database configuration form" (Figure 1).

    how to update the sql templates
    Figure 1 - How to update the SQL templates

    On this form you can specify an SQL command that is valid in your database server. You can put stored procedures and complex SQL statements. As long as the SQL command can be executed, the SMS gateway can use it.

    Send SMS messages and receive SMS messages using Informix

    On this page you can find the database configuration you should apply for Informix to be able to send SMS messages and receive SMS messages by inserting and reading data from database tables.

    To connect to Informix, please configure the following database connection string in the database user configuration form:

    Provider=Ifxoledbc.2;password=pppppp;User ID=uuuuuu;Data Source=opcrts@alpha;Persist Security Info=true

    Here is a quick overview of how this solution is going to work: First you create two database tables: ozekimessageout and ozekimessagein in Informix. Then you install and configure Ozeki NG SMS Gateway, to connect to Informix and to use these database tables for sending and receiving messages. Once you have the configuration completed, you can send an SMS message by using an SQL INSERT statement to create a record in the ozekimessageout database table. Ozeki NG will read this record using an SQL SELECT and will send your SMS message using a GSM modem attached to the PC or using an IP SMS connection.

    To create your database tables in Informix you can use the following create table script:

    CREATE TABLE ozekimessagein (
     id serial,
     sender varchar(255),
     receiver varchar(255),
     msg varchar(160),
     senttime varchar(100),
     receivedtime varchar(100),
     operator varchar(30),
     msgtype varchar(30),
     reference varchar(30),
    );
    
    CREATE TABLE ozekimessageout (
     id serial,
     sender varchar(255),
     receiver varchar(255),
     msg varchar(160),
     senttime varchar(100),
     receivedtime varchar(100),
     operator varchar(100),
     msgtype varchar(30),
     reference varchar(30),
     status varchar(30),
     errormsg varchar(250)
    );
    

    Figure 1 - SQL Create table script for Informix

    If you want to work with larger messages, you can increase the size of the msg field, or you may also change it's data type.

    Send and receive SMS from MS Access

    This guide gives you some tips to get you started on sending or receiving SMS messages from Microsoft Access. It gives you the initial installation steps from start all the way to sending your first SMS.

    What is Access

    Access is a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software-development tools. Access can be used to manage business data in tables. It is often combined with Ozeki NG SMS Gateway to send and receive SMS.

    How to send SMS from Access
    How to send SMS from Access

    Introduction

    Ozeki NG can connect to an Access database through an ODBC or through an OLEDB connection. It uses two Access tables. One table is used for sending SMS messages the other table is used for receiving SMS messages. The table structures match the table structure used in the MS SQL database configuration. Ozeki NG uses SQL statements to work with these tables through the ODBC (or OLEDB) connection.

    Quick instructions to Send SMS from Access

    To Send SMS from Access:

    1. Create the Access database layout
    2. Open the Ozeki dashboard
    3. Find the panel named 'Users and applications'
    4. Click on 'Add new user or application...'
    5. Find the Database user (Access is a database)
    6. To Send an SMS from Access install this connection
    7. Type the text "Access" into the application name field
    8. Enter the "Access" connection string
    9. Validate the settings, they must be ok to send sms
    10. To send your first SMS insert a recording into the ozekimessageout table
    11. Check the logs to see if your SMS was SELECTED from Access and sent

    Video tutorial on how to send SMS from Access

    The following video tutorial demonstrates how you can setup an Access SMS solution. It will give you the configuration steps and will show you how this solution can be setup in less then 10 minutes.

    Step 1: Create the databaes layout to send SMS

    The first step to setup an Access to SMS solution is to create the database table layout. You need to create two database tables: ozekimessageout and ozekimessagin. Ozekimessageout will be used for sending SMS and ozekimessagein can be used for receiving. You may download the already created tables from the following link, or you may create them yourself.

    Database tables for sending SMS from Access:
    ozeki_database.accdb

    Below you can see the table definition of these databaes tables. The most important fields in these tables are the sender and receiver and the msg field. The sender field contains the sender telephone number, the receiver field contains the recipient telephone numbber and the msg field contains the messages text.

    Figure 1 - "ozekimessagein" database table

    Figure 2 - "ozekimessageout" database table

    Step 2: Connect your system to the mobile network

    To send SMS messages from access, you need to connect your Ozeki NG SMS Gateway system to the mobile network. You can do this by following the instructions in the The quick start guide for sending SMS. After you are able to send and receive SMS messages manually from the Ozeki User interface, you can configure the Access database connection in Ozeki NG SMS Gateway.

    Ozeki NG SMS Gateway can be connected the mobile network in quite-a-few ways. The ideal option for your environment depends on the volume of texts you plan to send or receive. For sms volumes up to 10 000 text messages per day, the best option is to use a GSM modem or an Android mobile phone as an SMS gateway. The advantage of this choice is that it often allows you to send unlimited SMS messages free of charge.

    For higher SMS volumes you can switch to online SMS services, which means you will send SMS messages over the Internet. When you use on-line SMS service providers you can use a dedicated SMS protocol or an SMS API. There are various SMS protocols out there: SMPP protocol, CIMD2 protocol, UCP/EMI protocol and there are many proprietary protocols based on HTTP. Protocols basd on HTTP are called HTTP SMS APIs. The best option to connect to on-line SMS services is to use an SMPP connection. The SMPP protocol is widely used in the SMS industry. It is used by mobile network operators to exchange SMS traffic between each other. SMPP was designed for SMS, and it gives you high performance, instant access to submit and delivery reports and precise time stamps related to SMS delivery. So choose SMPP if possible.

    If you decide to connect to an on-line SMS service provider, it is a good idea to use the HTTP sms client implementation of Ozeki NG SMS Gateway, or the Ozeki REST SMS API client. It is very important not to implement a proprietary HTTP API of a single SMS service provider, because you will be locked into their service. You will also miss the option of creating wireless backup routes and the ability to use great testig tools. It is much more sensible, to implement an API provided by Ozeki NG SMS Gateway because it will give you the freedom to switch providers if costs are raised, or you wish to reach other networks. With Ozeki NG SMS Gateway you can connect to multiple SMS services at the same time.

    Step 3: Connect Ozeki NG to your Access database

    To send SMS from access, you need to connect Ozeki NG to your Access database tables. To do this you need to setup a database connection in Ozeki NG that points to the Access file. To start, go to "Add new user" in the main menu, and select the database option. (Figure 3).

    Figure 1 -

    After the database connection has been selected, please pick a unique name for this connection. For your first application, you can pick Access1. If you will add a second Access database later, it can be named Access2.

    start the installation of a database connection
    Figure 1 - Start the installation of a database connection

    The next step is to provide a unique name for this connection. In our example we provide "Access1" as the name for the connection (Figure 2).

    provide a unique name for the connection
    Figure 2 - Provide a unique name for the connection

    Once this is done you are ready to configure the connection parameters.

    To connect your SMS gateway to Access, please select ODBC as the connection method and provide the connection string that points to your database (Figure 3).

    setting the connection string
    Figure 3 - Setting the connection string

    The above connection string specifies a connection string with standard security. The connection string points to your access database (*.mdb) and it contains the username and password. These values must be set to match your system. You can use the following connection strings depending on your requirements:

    Standard security:

    Driver={Microsoft Access Driver (*.mdb)};Dbq=C:\mydatabase.mdb;Uid=Admin;Pwd=;

    Workgroup:

    Driver={Microsoft Access Driver (*.mdb)};Dbq=C:\mydatabase.mdb;SystemDB=C:\mydatabase.mdw;

    Exclusive:

    Driver={Microsoft Access Driver (*.mdb)};Dbq=C:\mydatabase.mdb;Exclusive=1;Uid=admin;Pwd=;

    Admin:

    To enable certain pragmatically admin functions such as CREATE USER, CREATE GROUP, ADD USER, GRANT, REVOKE and DEFAULTS (when making CREATE TABLE statements) use this connection string.

    Driver={Microsoft Access Driver (*.mdb)};Dbq=C:\mydatabase.mdb;Uid=Admin;Pwd=;ExtendedAnsiSQL=1;

    Locale identifier:

    Use this one to specify the locale identifier which can help with non-US formatted dates or special character sets. The example bellow uses the en-gb locale identifier (2057)

    Driver={Microsoft Access Driver (*.mdb)};Dbq=C:\mydatabase.mdb;Locale Identifier=2057;Uid=Admin;Pwd=;

    Step 5 - Update your SQL templates

    After you have set the connection string, to get the access connection working, you also have to change the SQL templates. The most important thing to do, is to remove the apostrophe around the $id keyword in all SQL templates. By default the SQL templates used in the Database configuration are not going to work in Access. The following figures (Figure 4-8) show you which templates should be changed. The change is minor.

    modify the sending sql template
    Figure 4 - Modify the sending SQL template

    modify the sent sql template
    Figure 5 - Modify the sent SQL template

    modify the not sent sql template/
    Figure 6 - Modify the Not Sent SQL template

    modify the delivered sql template
    Figure 7 - Modify the delivered sql template

    modify the undelivered sql template
    Figure 8 - Modify the undelivered sql template

    Step 6 - Test your system by sending SMS from Access

    After these co nfigurations have been completed, you can send SMS messages from your access database by inserting a record into the outgoing database table. The Ozeki software will pickup your record and send it as an SMS message.

    To send SMS from the Access table
    • Insert your messages into ozekimessageout. For each message set the status field to "send".
    • Wait for Ozeki SMS gateway to deliver your texts.
    To receive SMS into the Access table
    • Send the SMS from your mobile phone to Ozeki SMS Gateway and wait for the SMS to arrive.
    • View the sms in the ozekimessagin table in Access.

    To sum it up

    By following the above steps you can create the solution quickly. Now you can use Access to send sms. You have seen the benefits Ozeki NG SMS Gateway can bring. If you have already completed the steps I am sure, if you let your boss know, you will be rewarded. If you would like to learn more useful insights about the benefitsof other smiliar solutions, please open ozekisms.com.

    How to connect to Microsoft Access 365

    On this page you will be provided with detailed information on how to connect to Access 365 database. Follow the steps and screenshots below to configure this connection. Please find the connection string, as well.

    Download the database used in the example: ozeki_database.accdb

    Configuration steps

    Before you start to configure your database connection, you need to create two database tables: "ozekimessagein" and "ozekimessageout". Figure 1 and Figure 2 demonstrate how these tables should be created.

    Figure 1 - "ozekimessagein" database table

    Figure 2 - "ozekimessageout" database table

    Please note that in our example the 'ozeki_database.accdb', please place it to a selected folder. In this tutorial it have been saved to the C:\Ozeki\ folder (Figure 3) Although you can save it to any other location. Please memorize the file's location. Later on you will have to use this path in the connection string. You can check the path from the 'File Explorer' (Figure 3). The file is an Access 365 database file.

    Figure 3 - Database file in the file system

    Now you need to install a database user in Ozeki NG SMS Gateway. You need to specify the database connection string for your database server. First select "OleDb" for "Connection string type". Then provide the following Connection string (Figure 4):

    Provider=Microsoft.ACE.OLEDB.12.0;Data Source=PathToYourDatabase;Persist Security Info=False

    Please note that you need to provide the path to your database after "Data Source=" part in the connection string.

    Figure 4 - Configure databse connection

    For Microsoft Access, the next step is very important because without it, Select queries will not work. On "SQL for sending" tab you need to remove apostrophes around the $id keyword in all SQL templates (Figure 5).

    Figure 5 - Modify SQL queries

    Testing the configuration

    When testing, you should use both tables. The one which was created for incoming messages and the one which was created for outgoing messages. In these examples these tables are called 'ozekimessageout' and 'ozekimessagein'.

    To test the configuration, you should INSERT a message record into the outgoing messages table (Figure 6), which is called 'ozekimessageout' in the current example. These messages can be SELECT-ed (polled) by configuring the Database User in the SQL promt menu. Please search these options in the Ozeki Ng SMS Gateway's browser GUI.

    Figure 6 - Insert message into ozekimessageout tabel

    The 'status=' parameter of the message record will change from 'Sending' to 'Sent' to 'Delivered'. The sent message will be visible in the Database User's Sent folder (Figure 7).

    Figure 7 - Message sent

    If an incoming message log event is displayed in the Database User's event log (Figure 8), the message entry will be INSERT -ed in the incoming message database table. The INSERT statement can be configured under the Database User's configuration panel 'SQL for sending' tabpage. This is the statement which INSERT-s incoming messages.

    Figure 8 - Incoming message

    In this example the incoming message table is called 'ozekimessagein'. This is where those SMS messages are INSERT-ed, which are received by the Database User. You should run a SELECT statement on it to read all of the messages (Figure 9).

    Figure 9 - Received messages in the database

    Connecting to Access with OleDB

    You can also connect to an access database with an OleDB database driver. The Microsoft Jet OleDB driver is a good option to use Access databases. In this section we give you the connection strings you can use if you wish to connect through OleDB.

    Standard security

    Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\mydatabase.mdb;User Id=admin;Password=;

    With database password

    This is the connection string to use when you have an access database protected with a password using the Set Database Password function in Access.

    Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\mydatabase.mdb;Jet OLEDB:Database Password=MyDbPassword;

    Workgroup (system database)

    Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\mydatabase.mdb;Jet OLEDB:System Database=system.mdw;

    Workgroup (system database) specifying username and password

    Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\mydatabase.mdb;Jet OLEDB:System Database=system.mdw;User ID=myUsername;Password=myPassword;

    DataDirectory functionality

    Provider=Microsoft.Jet.OLEDB.4.0;Data Source=|DataDirectory|\myDatabase.mdb;User Id=admin;Password=;

    How to connect to Access 2007

    On this page you will be provided with detailed information on how to connect to Access 2007 database. Follow the steps and screenshots below to configure this connection. Please find the connection string, as well.

    Download the database used in the example: ozeki_database.accdb

    Configuration steps

    Before you start to configure your database connection, you need to create two database tables: "ozekimessagein" and "ozekimessageout". Figure 1 and Figure 2 demonstrate how these tables should be created.

    ozekimessagein database table
    Figure 1 - "ozekimessagein" database table

    ozekimessageout database table
    Figure 2 - "ozekimessageout" database table

    Please note that in our example Access 2007 database is placed on the desktop (Figure 3).

    database placed on desktop
    Figure 3 - Database placed on desktop

    Figure 4 demonstrates the path to Access 2007 database.

    path to database
    Figure 4 - Path to databases

    Now you need to install a database user in Ozeki NG SMS Gateway. You need to specify the database connection string for your database server. First select "OleDb" for "Connection string type". Then provide the following Connection string (Figure 5):

    Provider=Microsoft.ACE.OLEDB.12.0;Data Source=PathToYourDatabase;Persist
    Security Info=False
    

    Please note that you need to provide the path to your database after "Data Source=" part in the connection string.

    connection string for the database
    Figure 5 - Connection string for the database

    Then on "SQL for sending" tab you need to remove apostrophes around the $id keyword in all SQL templates (Figure 6).

    remove apostrophes
    Figure 6 - Remove apostrophes from update statements

    This concludes the configuration of the connection.

    Testing the configuration

    To test the configuration insert a row Into "ozekimessageout" table with an SQL INSERT command. Click on "Execute" (Figure 7).

    insert row into ozekimessageout table
    Figure 7 - Insert a row into ozekimessageout table

    In the Outbox of the database user in Ozeki NG SMS Gateway you can see the sent message (Figure 8).

    sent message
    Figure 8 - Sent message

    Figure 9 shows the incoming message for database user in Ozeki NG SMS Gateway.

    incoming message
    Figure 9 - Incoming message

    Now to see the inserted rows, query all row from "ozekimessagein" table with an SQL SELECT command and click on "Execute" (Figure 10).

    select statements
    Figure 10 - Select statements

    As a result of the SQL SELECT command, you can see the incoming message in Ozeki NG SMS Gateway (Figure 11).

    inserted row
    Figure 11 - Inserted row

    SMS Gateway Video at YouTube

    This video was uploaded to YouTube, to help you understand how does an SMS gateway work. It explains an SQL to SMS gateway setup, to help you get started.

    Database connection string builder

    Download:ConnectionStringBuilder.exe (770 Kb)
    Download:ConnectionStringBuilder.zip (340 Kb)

    The database connection string builder tool can be used to create database connection strings. These connection strings can be specified in the "Database user" configuration form to create an SQL to SMS gateway configuration. In this webpage you can find information on how to use the database connection string builder.

    To build a connection string, you must start the downloaded tool, then you should click on the "Build database connection string" button. This will bring up the "Database.connectionstring" form (Figure 1).

    start the building
    Figure 1 - Start the building

    On the "Database.connectionstring" form select "Use connection string", then click on the "Build" button (Figure 2).

    select connection string
    Figure 2 - Select connection string

    On the next form you should select the database driver you wish to use. If you want to use an ODBC connection, you can select the "Microsoft OleDb provider for ODBC drivers" item (Figure 3).

    select odbc connection string
    Figure 3 - Select ODBC connection string

    On the ODBC configuration form, you should select "Use connection string" as your choice, then click on the "Build..." button (Figure 4).

    build odbc connection string
    Figure 4 - Build ODBC connection string

    When you build an ODBC connection string it is important to create a Machine datasource. A machine datasource is available for a background service, such as the Ozeki NG SMS Gateway. User datasources are only available for a logged in user, so they cannot be used in an SQL to SMS gateway configuration. To start select the "Machine datasource" tab, then click "New" (Figure 5).

    build a machine data source
    Figure 5 - Build a machine data source

    During the building the "System datasource" option should be selected. A system datasource is a machine datasource, which means it can be accessed by background services (Figure 6).

    select system data source
    Figure 6 - Select system data source

    From this point the configuration is pretty straightforward. You must select the ODBC driver that matches your database server and you must fill in the connection parameters, such as the hostname, the username and the password. Once this is done you must click OK on all forms to get your connection string.

    Keywords in the SQL templates

    KeywordValue Incoming (insert) Outgoing polling (select) Outgoing sending (update) Outgoing sent (update) Outgoing not sent (update) Outgoing delivered (update) Outgoing undelivered (update)
    $idMessage ID + + + + + + +
    $senttimeSent time in the format specified on the confguration form +     + +    
    $receivedtimeReceived time in the format specified on the confguration form +       +    
    $messagedataMessage text + + + + + + +
    $decodedmessagedataThe decoded text for text messages and a hex string for binary messages. This is different then $messagedata since the $messagedata field will try to decode all data as text. +   + + + + +
    $senderSender address + + + + + + +
    $originatorSame as $sender + + + + + + +
    $receiverRecipient address + + + + + + +
    $recipientSame as $receiver + + + + + + +
    $messagetypeOzeki message type + + + + + + +
    $operatornamesThe names of the service provider connections, that can be used to send this message. The names can be separated by a semicolon or a colon.   +          
    $operatorThe name of the service provider connection to use + +   +      
    $subjectThe message subject (for SMS messages, the first 1024 characters of the message text) +            
    $callbackidThe message submission reference number       +      
    $costThe cost of a message (the number of PDUs used to submit it)       +      
    $reasonThe error reason         +   +
    $errormessageThe error message         +   +
    $currentdatetimeCurrent date and time in the format specified on the confguration form +   + + + + +
    $currentdateCurrent date in the format yyyy-MM-dd +   + + + + +
    $currenttimeCurrent time in the format HH:mm:ss +   + + + + +
    $1The first word in the message. You can use $2 to refer to the second word, $3 to refer to the third word, etc... +            
    $U1The first word in the message in upper case format. You can use $U2 to refer to the second word in upper case format, etc... +            
    SMS message related fields
    $dcshexThe data coding scheme (DCS) byte of the PDU in hexadecimal format +     +      
    $dcsThe data coding scheme (DCS) byte of the PDU in decimal format +     +      
    $pidhexThe protocol identifier (PID) byte of the PDU in hexadecimal format +     +      
    $pidThe protocol identifier (PID) byte of the PDU in decimal format +     +      
    $udhplusudThe user data header and the user data in hexadecimal string format of the first pdu +     +      
    $udhThe user data header in hexadecimal string format of the first pdu +     +      
    $udThe user data in hexadecimal string format of the first pdu +     +      
    $scaService center address +     +      
    $tp_mmsThe TP_MMS flag of the first byte of the PDU. (true or false) +     +      
    $tp_mtThe TP_MT flag of the first byte of the PDU. (true or false) +     +      
    $tp_rpThe TP_RP flag of the first byte of the PDU. (true or false) +     +      
    $tp_srrThe TP_SRR flag of the first byte of the PDU. (true or false) +     +      
    $tp_udhiThe TP_UDHI (User data header inidication) flag of the first byte of the PDU. (true or false) +     +      
    $messageclassThe message class value is a decimal number +     +      
    Multipart SMS messages
    $pducountThe number of PDUs in the message +     +      
    $pdu1_udhudThe user data header and the user data in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_udhud, etc... +     +      
    $pdu1_udhThe user data header in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_udh, etc... +     +      
    $pdu1_udThe user data in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_ud, etc... +     +      
    $pdu1_rawheaderThe pdu header in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_rawheader, etc... +     +      
    $pdu1_rawbodyThe same as $pdu1_udhud. For the second pdu this would be $pdu2_rawpdu, etc... +     +      
    $pdu1_rawpduThe first pdu in hexadecimal format. For the second pdu this would be $pdu2_rawpdu, etc... +     +      
    $rawpdusContains all pdus separated by a semi colon; +     +      
    Optional fields
    $fieldnameField name is the name of a database column that was included in the select statement used to originally pick up the message. This keyword will hold the value of this column in all subsequent updates.   + + + + + +

    High performance SQL to SMS gateway configuration using MSSQL database server (500 MPS+)

    (Requires Ozeki NG SMS Gateway v4.5.0or newer version)

    This guide gives you information on how to configure your Ozeki NG SMS Gateway software to achieve a performance of 500 Messages Per Second (MPS) or more in an SQL to SMS gateway environment. The solution is based on MS SQL server and it requires the installation of the ozAppMSSQL.dll file.

    Introduction

    The configuration works the following way: Ozeki NG SMS Gateway connects to an MS SQL Server 2008 database. It reads outgoing messages from this database and sends these messages to the Short Messages Service Center (SMSC) of an SMS service provider over the Internet through an SMPP connection (Figure 1).

    architecture overview
    Figure 1 - Architecture overview of MS SQL to SMPP configuration

    How to setup

    To setup this system, you need to perform the following steps:

    1. Setup your MS SQL database server
    2. Setup Ozeki NG SMS Gateway
    3. Configure an SMPP connection in Ozeki NG SMS Gateway
    4. Configure SQL to SMS forwarding
    5. Configure Ozeki NG SMS Gateway for high performance operation

    Step 1.) Setup your MS SQL database server

    For this solution to work you need Microsoft SQL Server 2008 (or Microsoft SQL Server 2005). In MS SQL you should create a database. The recommended name for the database is 'ozeki'. You should also create a user with SQL server authentication, who can connect to this database. The username should be 'ozekiuser', the password should be 'ozekipass'. In the database, create the following table structure, and grant SELECT,INSERT and UPDATE privileges to the ozekiuser user.

    CREATE TABLE ozekimessageout (
                     id int IDENTITY (1,1),
                     sender varchar(255),
                     receiver varchar(255),
                     msg varchar(160),
                     msgtype varchar(30),
                     stat int
                    );
                    
    CREATE INDEX idindex ON ozekimessageout (id);
    
    CREATE TABLE msgreferences (
                 id int primary key,
                 reference char(200),
                 senttime datetime,
                 errormessage varchar(2048)
                );
                
    CREATE INDEX refindex ON msgreferences (id);
    
    CREATE TABLE ozekimessagein (
                 id int IDENTITY (1,1),
                 sender varchar(255),
                 receiver varchar(255),
                 msg varchar(160),
                 senttime varchar(100),
                 receivedtime varchar(100),
                 msgtype varchar(30)
                );
    

    Figure 2 - Database table layout

    If you take a look at this table structure you will notice several differences to the default table structure used in the standard Ozeki SQL to SMS solution. The first difference is that the ozekimessageout table contains a stat field instead of status and this field is an integer. The reason for the change in the name of the field is that the status word is a reserved word in MS SQL. The reason for the change in the field type is that it is significantly faster to update integer values, then to update strings in a database.

    In this ozekimessageout table the stat field can have the following values:

    ValueMeaning
    1Message waiting to be submitted
    2Message queued for delivery
    3Message submitted to the SMSC
    4Message rejected by the SMSC
    5Message delivered to handset
    6Message delivery to handset failed

    Figure 3 - Stat field values

    If you want to send an SMS message you need to insert the message with stat value 1 into the ozekimessageout database table. To send a message you can use the following SQL command:

    INSERT INTO ozekimessageout (sender,receiver,msg,msgtype,stat)
    VALUES ('+111111','+222222','Hello world','SMS:TEXT',1);
    

    Figure 4 - Sample SQL command to send an SMS message

    After you have inserted a message for submission, Ozeki NG SMS Gateway will read it and will change the value of the stat field to '2'. This indicates that the message is queued for delivery. A few moments later Ozeki NG tries to submit this message to the SMSC. If message submission is successful the value of the stat field is updated to '3', if message submission fails, the value is updated to '4'. In addition to this update a new record is inserted into a different table called msgreferences, to give you details about message submission results.

    This brings us to note the second change in the database structure: There is a new table called msgreferences. This table contains records that are inserted by Ozeki NG SMS Gateway after a message is successfully submitted to the SMSC or after the message submission fails. The 'id' field in this table contains a value matching the id field of ozekimessageout (this is a foreign key). The second field, called reference, will contain the callback id (message reference value) returned by the SMSC after it accepted the message for delivery. The senttime contains the timestamp of message submission and the error message field holds a text explaining the error in case the message could not be submitted to the SMSC. The reason for introducing this table was that it is faster to insert a new record into a database table then to update an existing record with new text content.

    Step 2.) Setup Ozeki NG SMS Gateway

    Download and install

    Once your database is defined, you are ready to setup Ozeki NG SMS Gateway. To start download Ozeki NG SMS Gateway from the download page, then run the setup wizard by clicking "Next" in each dialog box. This will give you a default configuration.

    Step 3.) Configure an SMPP mobile network connection

    The first step in configuring Ozeki NG SMS Gateway, is to configure a mobile network connection. In our example this is an SMPP connection. The SMPP service connection setup page gives you details instruction on how to setup SMPP. If you could successfully configure your SMPP connection, you should test connectivity by sending a test message from the graphical user interface to your mobile phone. Do this by clicking on the "Compose" button.

    Step 4.) Configure SQL to SMS forwarding

    To setup the SQL to SMS gateway service, you need to setup an instance of the "Database user with batch processing" module. This can be done by clicking on "Add user" menu item the "Users and applications" menu, then clicking on "install" in the "Database user with batch processing for MS SQL" section (Figure 5).

    setup database
    Figure 5 - Setup Database user with batch processing

    During the installation provide a unique user name. "mssql1" is a good choice (Figure 6).

    configure a unique user name
    Figure 6 - Configure a unique user name

    On the configuration form, that comes up after this, turn off logging, by making sure the "Log sent and received messages in human readable format" and the "Log low level communication" checkboxes are not checked. Logging should be turned off to get better performance (Figure 7).

    turn of logging
    Figure 7 - Turn off logging

    The final step in configuring the SQL to SMS gateway system, is to specify the database connection string. The database connection string can be specified by clicking on the "MS SQL Settings" link in the left hand panel. The default connection string is:

    Server=.\SQLEXPRESS;User ID=ozekiuser;password=ozekipass;Database=ozeki;Persist Security Info=True

    In this connection string change .\SQLEXPRESS to the name of the MS SQL server instance. If you want to use the default MS SQL server instance, this can be changed to a single dot: ".". Please also set the username and password and the name of the database (Figure 8).

    setup the connection string
    Figure 8 - Setup the connection string

    Step 5.) Configure Ozeki NG SMS Gateway for high performance operation

    The final step is to adjust Ozeki NG SMS Gateway to give you the throughput you desire. In order to achieve high throughput, you need to disable some functionality, that eats up resources. In short do the following:

    Open the "Server preferences form" from the "Edit menu". In the server preferences form open the "Advanced" tab and apply the following configure:

    1. Uncheck the "Match delivery reports" to original messages checkbox
    2. Check the "Delete messages that were forwarded to a client, or processed by an application" checkbox
    3. Uncheck the "Use persistent message queues" checkbox

    The appropriate configuration can be seen on Figure 9.

    high performance configuration
    Figure 9 - High performance configuration

    Testing

    To test the configuration you can insert several messages into the ozekimessagout database table and check the event log of Ozeki NG SMS Gateway to see the performance they were sent.

    Testing a high performance SQL to SMS configuration on your LAN

    This guide gives you information on how you can setup a test environment to evaluate the performance of Ozeki NG SMS Gateway. This environment is useful to test the configuration explained in the "High performance SQL to SMS gateway configuration (500 MPS+)" guide.

    Introduction

    The configuration presented here demonstrates how you can transfer SMS messages from a database server to a Short Messages Service Center (SMSC) at a rate of 500 messages per second or more. The configuration is made up of two systems: Computer "A" and Computer "B" (Figure 1).

    Computer "A" represents the short messages service center (SMSC). The role of this computer is to accept SMPP client connections and to simulate SMSC functionality. In our test environment the SMSC functionality will be simulated with the built in SMPP server of Ozeki NG SMS Gateway. (In a real life system you will not install computer "A". It will be operated by an SMS service provider and you will connect to it through the Internet.)

    Computer "B" represents a high performance SQL to SMS Gateway computer. This computer reads SMS messages from an MS SQL database server and send these messages through an SMPP link to the SMSC. This functionality is established with Ozeki NG SMS Gateway. (This is the system you purchase from Ozeki.)

    The hardware configuration of both computer "A" and computer "B" should be: Intel Core 2 Quad Q9550 2.83 GHZ CPU, Samsung 160Gb 7200 RPM SATA2 HDD, 4 GB RAM, Windows XP OS. Of course you can use other hardware configuration. If you have a more powerful hardware you will achieve greater performance.

    The network connection between computer "A" and computer "B" should be a 100 Mbps ethernet LAN.

    test environment
    Figure 1 - Test environment

    Setting up "Computer A"

    To setup "Computer A" as an SMSC you need to perform the following steps:

    1. Download Ozeki NG SMS Gateway
    2. Install Ozeki NG SMS Gateway with the default settings
    3. Install a HTTP Server service provider connection
    4. Install an SMPP user
    5. Optimize Ozeki NG SMS Gateway for high performance

    After installation "Computer A" will act as an SMSC.

    Setting up "Computer B"

    To setup "Computer B" as an SQL to SMS gateway you need to perform the following steps:

    1. Download Ozeki NG SMS Gateway
    2. Install Ozeki NG SMS Gateway with the default settings
    3. Install an "SMPP service provider connection" to connect the system to Computer "A"
    4. Install a "Database user with batch processing"
    5. Optimize Ozeki NG SMS Gateway for high performance

    After installation "Computer B" will act ash an SQL to SMPP gateway.

    Settings for the SMPP link

    When you setup the SMPP connection, you should follow these guidelines:

    On computer "A", when you create the SMPP user, please provide the following information:

    • username: "smp1"
    • password: "qwe123"

    On computer "B", when you configure the SMPP service provider connection, please configure the following information:

    • host: The IP address of computer "A"
    • port: 9500
    • username: smp1
    • password: qwe123

    How will the system work?

    The system will work in a transparent way, that allows you to track every step from message reading from the database to SMPP forwarding. To track the events all you have to do is to examine the logs the software generates. A separate log file is written for each component.

    To start the testing procedure of your system, you will insert messages into the ozekimessageout database table. For example you can insert 20 000 messages at your first test. After you have inserted the messages, you don't have to do anything else. The process from this point is fully automatic.

    The first step of the process is executed by the "Database user". The "Database user" checks periodically the ozekimessageout table. It will find your messages and will read 5000 messages in the first batch and will queue these messages for delivery in the "Ozeki NG SMS Gateway engine". (After all your messages are delivered, it will read the next 5000 messages. If you have less the 5000 initially, it will work with less.)

    After the "Database user" has read the messages from the database and have queued them for delivery, the "Ozeki NG SMS Gateway engine" will pass these messages to the "SMPP service provider connection" for delivery. The "SMPP service provider" connection is the SMPP client module of the Ozeki NG SMS Gateway software. It runs on computer "A" and it connects to the built in SMPP server of computer "B" through the LAN. The connection is a TCP/IP based network link. The actual message delivery speed on this link is determined by two factors: the network bandwidth and the speed the SMSC is able to accept messages. Since currently the SMSC is also an Ozeki NG SMS Gateway software, and you connect your systems through an Ethernet LAN, you don't have to worry about network and SMSC performance.

    The next step in the process takes place on computer "B". On computer "B" the built-in SMPP server of Ozeki NG SMS Gateway accepts the messages and adds them to the delivery queue of an SMPP user. (Remember that you had to setup an SMPP user account on computer "B", and you had to configure the username and password of this SMPP user account on computer "A" to establish the link.)

    Finally on computer "B", Ozeki NG SMS Gateway forwards the messages to the "HTTP Server" service provider connection. The HTTP server service provider connection in this case acts as a "dummy link" to the mobile network. Instead of sending the messages to mobile phones it saves them to a text file. The path of the text file is "C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Drivers\HTTPServer0\outbox.txt". This is OK for testing, since during performance tests we don't want to reach actual mobile phones. When you setup your system with a real SMSC, your messages will be forwarded to the mobile network.

    How to insert a large number of test messages?

    To insert a large number of test messages to your MS SQL server, you need to use an SQL console. For example Microsoft SQL Server Management Studio allows you to enter SQL commands on your database server. The following SQL script can be used to generate 20000 test messages.

    Begin transaction
    DECLARE @recno int;
    SET @recno=20000
    While @recno>0 Begin
      SET @recno=@recno-1
      INSERT INTO ozekimessageout (receiver,msg,stat) VALUES
      ('+2222222',CAST(@recno AS varchar)+' sms message text',1);
    End;
    Commit
    

    How to find out what the actual transfer speed was?

    To find the transfer speed, all you have to do is to open the event log of the "Database user with batch processing" module. You can do this by clicking on the "Users and applications" menu item, then selecting the user, then clicking on "events" (Figure 2). In the event view you will have a row showing the throughput.

    message transfer speed
    Figure 2 - Message transfer speed

    Configure Ozeki NG SMS Gateway for high performance

    This guide gives information on how you can configure Ozeki NG SMS Gateway for high performance operation. It explains what features take up server resources and how you can disable these features. After applying the settings on this page, you can check your system performance by following the instructions on the "Testing a high performance SQL to SMS configuration on your LAN" page.

    Introduction

    Ozeki NG SMS Gateway can be used in various environments, where different requirements are set. To satisfy the needs of customers the software includes many features. Some of these features provide functionality at the cost of performance. To build a high performance system, we explain these features so you can decide whether they are important for you or would you trade them in for performance.

    Task #1 - Turn off detailed logging

    Detailed log files help in resolving problems and, help in tracking messages one by one. In low throughput systems, and during initial configuration of SMSC connections, it is very useful to have detailed logs. For high performance systems, when several hundreds of messages are sent per second, writing of logs to disk can slow down the system, due to the large amount of disk IO.

    To build a high performance system, please disable logging on the following forms:

    • The service provider connection's configuration, form (e.g.: SMPP config form)
    • The user's or application's configuration form (e.g.: Database user config form)
    • The server preferences form

    Task #2 - Turn off delivery report matching

    When an SMS messages is submitted to the SMSC the SMSC returns a message reference (callback ID). After the message is delivered to the mobile handset the SMSC sends back a delivery report SMS, that contains the message reference of the originally submitted SMS. Ozeki NG SMS Gateway by default is configured to build a delivery report reference table, where all message references are stored. This table helps in finding the originally sent messages when a delivery report arrives. The task of pairing incoming delivery reports to submitted messages is called "delivery report matching". Delivery report matching is very convenient, however in high volume systems, where millions of messages are sent, the delivery report reference table can grow very large. This large data set can slow down delivery report matching and can put a break on system performance.

    To build a high performance system, please disable delivery report matching! You can do this by opening the "Server preferences form", then clicking on the "Advanced tab". On this tab, you need to make sure the "Match delivery reports to original messages" checkbox is NOT checked.

    Task #3 - Turn off persistent message queues

    If messages in the Ozeki NG SMS Gateway engine are stored on the disk instead of memory, a lot of disk I/O is required to keep the data updated. The advantage to storing messages on the disk comes on power failures. If the power is lost the gateway can start from where it left off. If messages are stored in memory, in case of power failure, they need to be resubmitted.

    For high capacity systems, do not use persistent message queues! To achieve this open the "Advanced" Tab of the server preferences form and uncheck the "Use persistent message queues" checkbox!

    Task #4 - Remove processed messages from the system automatically

    On smaller capacity systems, the system administrator might want to browse older messages in the Graphical User Interface. To support this requirement Ozeki NG SMS Gateway stores the messages in the disk for later browsing. If the number of messages increases browsing becomes difficult and large message queues can slow down the system.

    To keep a high performance system healthy, you need to remove processed messages from the system automatically. To achieve this open the "Advanced" Tab of the server preferences form and check the "Delete messages that were forwarded to a client, or processed by an application" checkbox.

    Screenshot of the server preferences form

    If you system is configured to high performance the advanced tab of the server preferences form will look like this:

    high performance sms software configuration
    Figure 1 - High performance configuration

    Ozeki Batch Processing Tester

    On this page you will find Ozeki Batch Processing Tester that will help you test the total message processing speed. This tester insert messages into the table from which Batch processing user polls out messages. In this way you can insert any number of messages into this table and batch processing user will send out them. After sending you receive the total message processing speed. Find the details of the solution in this guide.

    Download: Ozeki_batch_processing_tester.exe (11 Kb)

    First you need to log into Ozeki NG SMS Gateway with your username and password. Then add a new HTTP service provider connection. To do so, click on "Add service provider" in "Service providers" section (Figure 1).


    Figure 1 - Add new service provider

    Select "HTTP Server Connection" in the list and click on "Install" next to it (Figure 2).


    Figure 2 - Install HTTP server

    Leave the "Configuration" tab of the created connection unchanged and click on "OK" (Figure 3).


    Figure 3 - HTTP Server settings

    Now add a new outgoing route by clicking on "Add new route" in the "Outgoing" section (Figure 4).


    Figure 4 - Add new route

    Now specify the source and destination of the outgoing messages. Set "batch_processing" to "Source" and set the created HTTP server as "Destination". In this way you can ensure that messages will not be sent out from Ozeki NG SMS Gateway but you can test performance (Figure 5).


    Figure 5 - Source and destination of outgoing route

    Click on MSSQL Settings option of Batch processing user. Select the connection string and copy it (Figure 6).


    Figure 6 - Copy connection string

    Start Ozeki Batch Processing Tester and paste the connection string (Figure 7).


    Figure 7 - Paste connection string

    Now specify the number of messages to be inserted in Number of messages field and click on Start (Figure 8).


    Figure 8 - Specify the number of messages

    After messages has been sent you will receive a summary containing the total message processing speed (Figure 9). In our example I sent out 5000 messages and the total message processing speed was 66 MPS.


    Figure 9 - Summary about sending

    High performance SQL to SMS gateway configuration using Oracle database server (500 MPS+)

    (Requires Ozeki NG SMS Gateway v4.5.0 or newer version)This guide gives you information on how to configure your Ozeki NG SMS Gateway software to achieve a performance of 500 Messages Per Second (MPS) or more in an SQL to SMS gateway environment. The solution is based on Oracle and it requires the installation of Ozeki NG SMS Gateway.

    Introduction

    The configuration works the following way: Ozeki NG SMS Gateway connects to an ORACLE database using an oledb connection. It reads outgoing messages from this database and sends these messages to the Short Messages Service Center (SMSC) of an SMS service provider over the Internet through an SMPP connection (Figure 1).

    architecture overview of oracle to sms configuration
    Figure 1 - Architecture overview of ORACLE to SMS configuration

    How to setup

    To setup this system, you need to perform the following steps:

    1. Setup your ORACEL database server
    2. Setup Ozeki NG SMS Gateway
    3. Configure an SMS Service Provider connection in Ozeki NG SMS Gateway
    4. Configure SQL to SMS forwarding
    5. Configure Ozeki NG SMS Gateway for high performance operation

    Step 1.) Setup your ORACLE database server

    For this solution to work you need Microsoft SQL Server 2008 (or Microsoft SQL Server 2005). In ORACLE you should create a database. The recommended name for the database is 'ozeki'. You should also create a user with SQL server authentication, who can connect to this database. The username should be 'ozekiuser', the password should be 'ozekipass'. In the database, create the following table structure, and grant SELECT,INSERT and UPDATE privileges to the ozekiuser user.

    CREATE TABLE ozekimessageout (
                     id int ,
                     sender varchar(255),
                     receiver varchar(255),
                     msg varchar(160),
                     msgtype varchar(30),
                     stat int,
                     operator varchar(30)
                    );
    
    CREATE INDEX idindex ON ozekimessageout (id);
    
    CREATE index index_id3 ON ozekimessageout(id);
    CREATE SEQUENCE z;
    CREATE TRIGGER ozekimessageout_auto BEFORE INSERT on ozekimessageout
    for each row
    when (new.id is null)
    begin
       SELECT z.nextval INTO :new.id FROM DUAL;
    end;
    /
    
    CREATE TABLE msgreferences (
                 id int primary key,
                 msgid int,
                 stat int,
                 reference char(200),
                 senttime varchar(100),
                 errormessage varchar(2048)
                );
    
    CREATE INDEX refindex ON msgreferences (id);
    CREATE SEQUENCE M;
    CREATE TRIGGER msgreferences_auto BEFORE INSERT on msgreferences
    for each row
    when (new.id is null)
    begin
       SELECT M.nextval INTO :new.id FROM DUAL;
    end;
    /
    
    
    CREATE TABLE ozekimessagein (
                 id int ,
                 sender varchar(255),
                 receiver varchar(255),
                 msg varchar(160),
                 senttime varchar(100),
                 receivedtime varchar(100),
                 msgtype varchar(30)
                );
    
    CREATE index index_id4 ON ozekimessagein(id);
    CREATE SEQUENCE U;
    CREATE TRIGGER ozekimessagein_auto BEFORE INSERT on ozekimessagein
    for each row
    when (new.id is null)
    begin
       SELECT U.nextval INTO :new.id FROM DUAL;
    end;
    /
    

    Figure 2 - Database table layout

    If you take a look at this table structure you will notice several differences to the default table structure used in the standard Ozeki SQL to SMS solution. The first difference is that the ozekimessageout table contains a stat field instead of status and this field is an integer. The reason for the change in the name of the field is that the status word is a reserved word in ORACLE. The reason for the change in the field type is that it is significantly faster to update integer values, then to update strings in a database.

    In this ozekimessageout table the stat field can have the following values:

    ValueMeaning
    1Message waiting to be submitted
    2Message queued for delivery
    3Message submitted to the SMSC
    4Message rejected by the SMSC
    5Message delivered to handset
    6Message delivery to handset failed

    Figure 3 - Stat field values

    If you want to send an SMS message you need to insert the message with stat value 1 into the ozekimessageout database table. To send a message you can use the following SQL command:

    INSERT INTO ozekimessageout (sender,receiver,msg,msgtype,stat)
    VALUES ('+111111','+222222','Hello world','SMS:TEXT',1);
    

    Figure 4 - Sample SQL command to send an SMS message

    After you have inserted a message for submission, Ozeki NG SMS Gateway will read it and will change the value of the stat field to '2'. This indicates that the message is queued for delivery. A few moments later Ozeki NG tries to submit this message to the SMSC. If message submission is successful the value of the stat field is updated to '3', if message submission fails, the value is updated to '4'. In addition to this update a new record is inserted into a different table called msgreferences, to give you details about message submission results.

    This brings us to note the second change in the database structure: There is a new table called msgreferences. This table contains records that are inserted by Ozeki NG SMS Gateway after a message is successfully submitted to the SMSC or after the message submission fails. The 'id' field in this table contains a value matching the id field of ozekimessageout (this is a foreign key). The second field, called reference, will contain the callback id (message reference value) returned by the SMSC after it accepted the message for delivery. The senttime contains the timestamp of message submission and the error message field holds a text explaining the error in case the message could not be submitted to the SMSC. The reason for introducing this table was that it is faster to insert a new record into a database table then to update an existing record with new text content.

    Step 2.) Setup Ozeki NG SMS Gateway

    Download and install

    Once your database is defined, you are ready to setup Ozeki NG SMS Gateway. To start download Ozeki NG SMS Gateway from the download page, then run the setup wizard by clicking "Next" in each dialog box. This will give you a default configuration.

    Step 3.) Configure an SMPP mobile network connection

    The first step in configuring Ozeki NG SMS Gateway, is to configure a mobile network connection. In our example this is an SMPP connection. The SMPP service connection setup page gives you details instruction on how to setup SMPP. If you could successfully configure your SMPP connection, you should test connectivity by sending a test message from the graphical user interface to your mobile phone. Do this by clicking on the "Compose" button.

    Step 4.) Configure SQL to SMS forwarding

    To setup the SQL to SMS gateway service, you need to setup an instance of the "Database user with batch processing" module. This can be done by clicking on "Add user" menu item the "Users and applications" menu, then clicking on "install" in the "Database user with batch processing for Oracle" section (Figure 4).

    setup database user with batch processing
    Figure 4 - Setup Database user with batch processing

    During the installation provide a unique user name. "oracle1" is a good choice (Figure 5).

    configure a unique user name
    Figure 5 - Configure a unique user name

    On the configuration form, that comes up after this, turn off logging, by making sure the "Log sent and received messages in human readable format" and the "Log low level communication" checkboxes are not checked. Logging should be turned off to get better performance (Figure 6).

    turn off logging
    Figure 6 - Turn off logging

    The final step in configuring the SQL to SMS gateway system, is to specify the database connection string. The database connection string can be specified by clicking on the "ORACLE Settings" link in the left hand panel. The default connection string is:

    Provider=OraOLEDB.Oracle;Data Source=MyOracleDB; User Id=myUsername;Password=myPassword;
    

    If you use Oracle Expres edition, the following connection string might work for you:

    Provider=OraOLEDB.Oracle;dbq=localhost:1521/XE;User Id=SYSTEM;Password=qwe123;
    

    In the connection string change settings to point to your ORACLE instance. Please set the username and password and the name of the database (Figure 7).

    setup the connection string
    Figure 7 - Setup the connection string

    Step 5.) Configure Ozeki NG SMS Gateway for high performance operation

    The final step is to adjust Ozeki NG SMS Gateway to give you the throughput you desire. In order to achieve high throughput, you need to disable some functionality, that eats up resources. In short do the following:

    Open the "Server preferences form" from the "Edit menu". In the server preferences form open the "Advanced" tab and apply the following configure:

    1. Uncheck the "Match delivery reports" to original messages checkbox
    2. Check the "Delete messages that were forwarded to a client, or processed by an application" checkbox
    3. Uncheck the "Use persistent message queues" checkbox

    The appropriate configuration can be seen on Figure 8.

    high performance configuration
    Figure 8 - High performance configuration

    Testing

    To test the configuration you can insert several messages into the ozekimessagout database table and check the event log of Ozeki NG SMS Gateway to see the performance they were sent.

    Detailed description of SQL statements

    This page provides you detailed information on the various SQL statements of database user. Please browse through the screenshots to learn how and when the statements are executed during the SMS sending process.

    Polling statement will be executed by default in every "10" seconds. The time of the execution can be set in "Check the ozekimessageout table every ... sec. for outgoing messages (Figure 1).

    polling statement
    Figure 1 - Polling statement

    Figure 2 demonstrates that the database has been polled and there is no outgoing message in the database table.

    no outgoing message
    Figure 2 - No outgoing message

    If there are outgoing messages in the database they will return with the polling statement and the database user updates record to "Sending" (Figure 3).

    outgoing messages
    Figure 3 - Outgoing message

    Sending statement is executed if Polling was successful and there is an outgoing message in the table (Figure 4).

    sending statement
    Figure 4 - Sending statement

    Then messages are forwarded to the Service Provider in Ozeki NG SMS Gateway via outbound route (Figure 5).

    messages forwarded to the service provider
    Figure 5 - Messages forwarded to the service provider

    If the Service Provider of Ozeki NG SMS Gateway forwards the message to the SMSC (SMS center), the Service provider will return that "Message delivered to network". In this case the database user will update the record to "Sent" (Figure 6).

    message delivered to network
    Figure 6 - Message delivered to network

    If the message has been sent from the Service provider in Ozeki NG SMS Gateway Sent statement is executed (Figure 7).

    sent statement
    Figure 7 - Sent statement

    If the Service provider of Ozeki NG SMS Gateway cannot forward the message to the SMSC for some reason, the status of the message will be "Message not sent" in the SMS gateway. The database user then updates the record to "Not sent" (Figure 8).

    message cannot be delivered
    Figure 8 - Message cannot be delivered to network

    If the message cannot be sent to the service provider in Ozeki NG SMS Gateway Not sent will be executed (Figure 9).

    not sent statement
    Figure 9 - Not sent statement

    If the SMSC sends a delivery report containing "Message delivered to handset" the database user will update the record to "Delivered" (Figure 10).

    message is delivered to handset
    Figure 10 - Message is delivered to handset

    If the delivery report contains "Message successfully delivered to handset", Delivered statement will be executed (Figure 11).

    delivered statement
    Figure 11 - Delivered statement

    If the delivery has been failed the database user will update the record to "Undelivered" (Figure 12).

    message delivery failed
    Figure 12 - Message delivery failed

    If the SMSC reports that the message cannot be delivered, Undelivered statement will be executed (Figure 13).

    undelivered statement
    Figure 13 - Undelivered statement

    SQL polling technology

    This guide gives information about how the polling system works in Ozeki NG SMS Gateway database user. The information provided can help in controling and modifying the behaviour.

    Default operation

    By default the system works the following way:

    1. You insert your messages into the Ozekimessageout datase table with the status of "send"
    2. The Ozeki software reads these messages with an SQL select command and updates the status to "sending"
    3. After the status is updated to "sending", the Ozeki software puts these messages into the outbox queue.
    4. The Ozeki SMS engine, takes the messages from the outbox queue and sends it to the mobile network.
    5. If the mobile network confirms, that it accepted the message for delivery, the status of the message in the databse table is changed to "sent"
    6. If the mobile network rejects the message for any reason (e.g. there is no money on the subscription), the status is updated to "notsent".
    7. After the mobile network accepted the message for delivery, it tries to deliver the SMS to the recipient mobile phone. If the SMS reaches the mobile phone, a delivery report is returned to the Ozeki NG software by the mobile network. When the delivery report is received, the Ozeki NG software updates the database record to "delivered" status. Please note, that it might be possible, that the delivery report comes in after several hours, or sevaral days. This can happen for example if the recipient mobile phone is switched off.
    8. In some cases the mobile network will not be able to deliver the SMS to the recipient phone. For example if the recipient phone is never switched on. In this case it will send an error report to Ozeki NG. If Ozeki NG receives this error report, it will update the status of the database record to "undelivered" in the ozekimessageout table.

    What is polling and how does it work?

    The term polling refers to the fact, that Ozeki NG must check the ozekimessagout database table periodically for outgoing messages. The default polling mechnaism works the following way:

    Ozeki NG SMS Gateway executes an SQL SELECT statement on the database every 10 seconds (This is the polling interval). If it finds outgoing messages in the database table, it will take out a maximum of 10 messages for delivery (this is the maximum polling count). If the number of available messages for sending in the ozekimessagout database table is less then the maximum polling count, the software assumes that there are no more messages waiting to be sent, and will wait another 10 sec before checking again for new messages. If the number of available messages for sending in the ozekimessagout database table is more then the size of the maximum polling count, the software will execute another poll on the database immediately after the first poll is finished. This means that you don't have to worry about the length of the polling interval. If there are messages in the database the Ozeki software will read them as fast as possible.

    Controling the maximum outbox size?

    In some cases it might be possible, that there are several thousands, or even millions of messages waiting to be sent in your ozekimessageout database table. In this case you probably don't want Ozeki NG to take all of them at once. To control the maximum number of messages in the Ozeki outbox, you can adjust the "MaxQueueSize" parameter in the C:\Program Files\Ozeki\OzekiNG - SMS Gateway\config\user-sql1.txt configuration file. Note that after adjusting this parameter, you will have to restart the Ozeki NG service.

    If you adjust this parameter, Ozeki NG SMS Gateway will suspend polling temporarily if the outbox level reaches the specified limit. It will resume polling as soon as the outbox level goes bellow 80% of the specified limit.

    How to set dynamic keywords in Ozeki NG SMS Gateway

    This page explains how you can set dynamic keywords in Ozeki NG SMS Gateway effectively. The example below uses Oracle 10g XE database for demonstration.

    When you use Ozeki NG SMS Gateway you can set keywords in the SQL table to achieve various functions. For the list of the available keywords please check Keywords in the SQL templates page.

    However, there is a possibility to define further keywords beside the above mentioned ones to get further functions. These dynamic keywords can be specified in your database (in this example in Oracle 10g XE database). After you specified your keywords, Ozeki NG SMS Gateway will poll the variable names and parameters from the database.

    Since this example uses uses Oracle 10g XE database for demonstration, it is required that the Oracle database has been configured to Ozeki NG according to the following webpage: https://ozekisms.com/p_2646-how-to-send-sms-from-oracle-10g-xe.html.

    Step by step guide

    First you need to create the necessary database tables and structures. Insert the following SQL commands and click on Run:

    Create table dynamicvariables and click Run (Figure 1):

    CREATE TABLE dynamicvariables ( 
      id int, 
      varname varchar(30) default NULL, 
      varvalue varchar(30) default NULL
    )

    sql command for creating dynamicvariables table
    Figure 1 - SQL command for creating dynamicvariables table

    Create index on dynamicvariables and click Run (Figure 2):

    CREATE index index_id3 ON dynamicvariables(id)

    create index
    Figure 2 - Create index

    Create sequence and click Run Figure 3):

    CREATE SEQUENCE Z

    Figure 3 - Create sequence

    Create trigger and click Run (Figure 4):

    CREATE TRIGGER dynamicvariables_auto BEFORE INSERT on dynamicvariables 
    for each row 
    when (new.id is null) 
    begin 
       SELECT z.nextval INTO :new.id FROM DUAL; 
    end

    Figure 4 - Create trigger

    Now I insert a test variable (AMOUNT) (Figure 5):

    INSERT INTO dynamicvariables(varname, varvalue) VALUES ('AMOUNT','1560')

    Now I insert a test variable (CURRENCY) (Figure 6):

    INSERT INTO dynamicvariables(varname, varvalue) VALUES ('CURRENCY','€')

    Figure 6 - Test variable

    Now start Ozeki NG SMS Gateway. Go to the configuration panel of the database user and click SQL for Sending tab (Figure 7). On Polling tab enter the following SQL statement for polling messages:

    SELECT id,sender,receiver,replace(replace( msg, 'AMOUNT', (select varvalue 
    from dynamicvariables where varname='AMOUNT')), 'CURRENCY', (select varvalue 
    from dynamicvariables where varname='CURRENCY')),msgtype,operator FROM 
    ozekimessageout WHERE status='send'
    

    Figure 7 - Polling tab

    Then insert a test parameter in the ozekimessageout table in Oracle (Figure 8):

    INSERT INTO ozekimessageout (receiver,msg,status) VALUES ('+36205460691','test 
    data from amount table: AMOUNT, and test data from currency table: CURRENCY','send');
    

    Figure 8 - Test parameters

    Figure 9 demonstrates a sent message in Ozeki NG SMS Gateway that has been sent with this configuration.

    Figure 9 - Sent message

    For more information please contact us at info@ozekisms.com.

    Dynamic SMPP parameters from database

    By using a database user, you are allowed to dynamically set source_addr_ton, source_addr_npi, dest_addr_ton, dest_addr_npi, esm_class and data_coding SMPP parameters dynamically by saving them into the appropriate database records. This guide explains how you can set SMPP parameters dynamically by using a database user - note that this feature is only available in Ozeki NG SMS Gateway 4.2.5 or above.

    You can read about dynamic SMPP parameter settings here: Dynamic SMPP parameters

    You can read about the database user here: Database users

    Setting SMPP parameters from database

    First, you need to create the database user's table for sending so it can contain values for SMPP parameters too. Have a look at the example below.

    CREATE TABLE IF NOT EXISTS 'ozekimessageout' (
      	'id' int(11) NOT NULL AUTO_INCREMENT,
      	'sender' varchar(255) DEFAULT NULL,
     	'receiver' varchar(255) DEFAULT NULL,
      	'msg' text,
      	'senttime' varchar(100) DEFAULT NULL,
      	'receivedtime' varchar(100) DEFAULT NULL,
      	'reference' varchar(100) DEFAULT NULL,
      	'status' varchar(20) DEFAULT NULL,
      	'msgtype' varchar(160) DEFAULT NULL,
      	'operator' varchar(100) DEFAULT NULL,
      	'errormsg' varchar(250) DEFAULT NULL,
      	'source_addr_ton' int(3),
    	'source_addr_npi` int(3),
    	'dest_addr_ton' int(3),
    	'dest_addr_npi' int(3),
    	'esm_class' int(3),
      	'data_coding' int(3)
      	PRIMARY KEY ('id'),
      	KEY 'id' ('id')
    )
    

    After preparing the database table, you need to update the SELECT statement in the database user's configuration - you need to add the appropriate field names to the SQL statement (Figure 1).

    updating the select statement
    Figure 1 - Updating the SELECT statement for polling

    After these steps, the database user can send messages with dynamically set SMPP parameter values. Note, that the database records must contain decimal values (or NULL, if you don't want to dynamically set SMPP parameters).

    When sending a message, if the message's record contains a value for an SMPP parameter, the message will be sent with that parameter value. If the record has a blank field for a parameter value then the SMPP service's configured value will be used (Figure 2).

    smpp parameter settings
    Figure 2 - SMPP parameter settings

    If you have left these fields blank, default values will be used.

    SMS Autoreply from Database

    This guide gives you information on how to create an autoresponding application that uses information stored in your database. The solution presented on this webpage can be used with any database server (Microsoft SQL, Oracle, MySQL, Sybase, etc...). This solution is ideal to create the following service (Figure 1):

    1. A mobile user sends in a keyword in an SMS message to the system.
    2. The system looks up the response SMS message from the database based on this keyword.
    3. The system sends the response SMS message back to the mobile user.

    I assume you already have a working service provider connection configured, that is capable of sending and receiving messages (e.g. you have a GSM modem attached to your server computer and your GSM modem is configured in Ozeki NG).

    system architecture
    Figure 1 - System architecture

    Step 1 - Setup the Autoreply Database User

    In order to create the explained service first you need to install an Autoreply Database User (Figure 2). Detailed information about how this user can be installed is available in the "Autoreply Database User installation guide".

    install the autoreply database user for sms information queries
    Figure 2 - Install the Autoreply Database User for SMS information queries

    Step 2 - Create the database layout

    The next step is to create your database table, that stores the response SMS messages (Figure 3). In our example we use Microsoft SQL Express as the database server. The following guide gives you information on how you can create a database layout using SQL Express: Create database layout for SMS autoresponses. In our example we use the following table. (Of course you can change the table layout according to your needs and you can use multiple database tables.)

    > select * from autoreplymessage;
    id          keyword                        msg
    ----------  ------------------------------ -------------------------------------
     1          default                        There is no data for this keyword.
     2          red                            Red is a good color.
     3          blue                           Blue is not the best option.
    
    (3 rows affected)
    

    Figure 3 - Database table layout for SMS information query

    Step 3 - Configure the Autoreply Database User to use your database

    When your database is ready, you need to enter the database connection information (connection type and connection string) into the database settings configuration form of the Autoreply Database user. This configuration form can be opened by clicking on the "Database setup" menu item (Figure 4).

    database settings for sms information query
    Figure 4 - Database settings for SMS information query

    On this form you can select the database connection type and you can enter the connection string. In our example (for SQL Express) the connection information that should be used is:

    Connection type: OleDb
    
    Connection string:
    Provider=SQLNCLI;Server=.\SQLEXPRESS;User ID=ozekiuser;password=ozekipass;
    Database=ozeki;Persist Security Info=True
    

    For other database servers, such as Oracle, MySQL, etc..., you can find information about how to format the connection string in the Database Connection Strings guide.

    Step 4 - Write the autoresponding command script

    The final step to make SMS information query possible is to write the script file. The script file is a plain text file that controls which SQL command should be executed when an incoming SMS arrives. You can edit the scriptfile with notepad or any other text editor. In our example the location of the script file is:

    C:\Program Files\Ozeki\OzekiNG - SMS Gateway\config\TestApp\sqlscript.txt

    The contents of the script file in our example has three sections (Figure 5). The first two sections are triggered for a response SMS if the keyword "RED" or "BLUE" is received in an SMS message. The final section creates the default response message if something else was received.

    C:\Program Files\Ozeki\OzekiNG - SMS Gateway\config\TestApp\sqlscript.txt
    k^RED
    SELECT '$sender',msg from autoreplymessage where keyword='red'
    
    k^BLUE
    SELECT '$sender',msg from autoreplymessage where keyword='blue'
    
    k.*
    SELECT '$sender',msg from autoreplymessage where keyword='default'
    

    Figure 5 - example script file

    Autoreply Database user can recognize the following keywords:

    KeywordValue
    $originatorIt is replaced to the sender telephone number of the messages
    $sender It is replaced to the sender telephone number of the messages (an alias for originator)
    $recipientIt is replaced to the telephone number that received the message
    $receiverIt is replaced to the telephone number that received the messages (an alias for recipient)
    $messagedataIt is replaced to the message text
    $keywordIt is replaced to the keyword in the message
    $afterIt is replaced to the message the message text after the keyword in the message
    $senttimeIt is replaced to the timestamp, that represents when the message was sent
    $receivedtimeIt is replaced to the timestamp, that represents when the message was received
    $messagetypeIt is replaced to the message type (in most cases this will be SMS:TEXT)
    $idIt is replaced to the unique string identifier of the message
    $operatorIt is replaced to the name of the service provider connection that received the message
    $1The first word in the message. You can use $2 to refer to the second word, $3 to refer to the third word, etc...

    The structure of the autoreply script is explained in the following documents:

    Script file structure for SMS information query from database

    Sample script file for SMS information query from database.

    Step 5 - Testing the solution

    After this is done, you can test the solution by sending an SMS message to your SMS gateway. The SMS gateway will forward the message to the Autoreply Database User, where the command script will be executed for the response. The response will be returned by an SQL SELECT query defined in the script file. After the appropriate SQL SELECT is executed the response messages will be sent back to you in SMS. To track what is going on, read the logs in the following directory:

    C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    Autoreply Database User installation guide

    This guide gives you the steps to install the Autoreply Database User.

    To start installing and configuring an Autoreply Database User user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add new user or application item in the Users and applications menu (Figure 1).

    add new user or application
    Figure 1 - Add new user or application

    This will bring up an interface consisting of two panels. The panel on the left contains a list of users that have been installed. In the bar at the bottom of the page you can read how many users have been installed. The panel on the right contains a list of users that can be installed. Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets). Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for. To add an SMPP user, click the Install link in the respective entry in the list (Figure 2).

    install the user
    Figure 2 - Install the user

    Now provide a unique name for the user to be installed (Figure 3).

    provide a name for the user
    Figure 3 - Provide a name for the user

    The Configuration panel appears. If you are content with the default settings you can leave this window unchanged and click on "OK" (Figure 4).

    logging tab
    Figure 4 - Logging tab

    In Advanced tab you can specify the phone number of the sender, and you can provide a username and a password to login. In the lower section of this tab you can enable Allow routing table override option. If routing table override is enabled, this user can specify the preferred service provider connection for each message. You can also enable Enable accounting for this user option. If you enable accounting, a credit limit can be set for this user. The user will not be allowed to send more messages then the credit limit.

    advanced tab
    Figure 5 - Advanced tab

    Create database layout for SMS autoresponses

    In this guide we create an example database layout for an autoresponding SMS application that uses data stored in an SQL database. We use the Microsoft SQL Express database server that can be downloaded from the Microsoft website.

    Step 1. - Download and install Microsoft SQL Express.

    You can download the Microsoft SQL Express Database Server from the following location:

    Download details: Microsoft SQL Server 2019 Express Edition

    Step 2 - Create your database tables in Microsoft SQL Express

    You can create a database and the appropriate database tables by opening a windows command prompt (Start->Run->cmd.exe), and starting the SQL Command interpreter by typing:

    C:\sqlcmd -S .\SQLExpress

    Once the SQL command interpreter is running, you should enter the following commands

    create database ozeki
    GO
    
    use ozeki
    GO
    
    CREATE TABLE autoreplymessage (
     id int IDENTITY (1,1),
     keyword varchar(30),
     msg varchar(160),
    );
    GO
    
    sp_addLogin 'ozekiuser', 'ozekipass'
    GO
    
    sp_addsrvrolemember 'ozekiuser', 'sysadmin'
    GO
    
    Figure 1 - SQL Create table script

    Step 3 - Put some data into your keyboard database

    To be able to create a response automatically for certain keywords we must fill the autoreplymessage database table:

    insert into autoreplymessage (keyword,msg) values ("default","There is no data for this keyword.");
    insert into autoreplymessage (keyword,msg) values ("red","Red is a good color.");
    insert into autoreplymessage (keyword,msg) values ("blue","Blue is not the best option.");
    GO
    

    Step 4 - Make Microsoft SQL Express ready to accept your username and password

    Unless you have mixed mode authentication configured in SQL express, you will not be able to connect to your database from Ozeki NG because Ozeki NG runs as a system service in the background. To enable mixed - mode authentication, you should open the registry editor (Start->run->regedit.exe) and in the Registry you should change the LoginMode value from 1 to "2", here:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer
    
    LoginMode =2
    

    After this change you might have to restart the SQL Express to make sure the changes take effect.

    File structure for controlling SQL information query from database

    This document explain the file structure of the script file that is used to control which SQL query is executed when an incoming SMS message arrives to the system.

    Introduction

    The script file contains sections. Sections are separated by an empty line. There is now limit for the number of sections. When the script is consulted sections are read sequentially. The first section that matches an incoming SMS is used to create the response SMS message.

    A section contains a condition and a set of SQL commands called action (Figure 1). The condition is the first line in the section. Any number of SQL commands can follow this line. If the condition matches all the SQL commands following the condition will be executed until an empty line is found. The SQL commands can return one or more response messages.

    sections in the script file
    Figure 1 - Sections in the script file

    Condition

    The condition is a single line statement. It has two parts the match target selector, and the match pattern (Figure 2). The match selector is a single letter, that determines which part of the incoming SMS message is checked with the matching pattern.

    information query condition
    Figure 2 - Information query condition

    The match selector letter can be one of the following:

    k - keyword //The first word of the SMS message
    converted to uppercase
    n - sender telephone number 
    m - the message text 
    

    The match pattern is a standard regular expression. Regular expressions are explain in the Regular expressions tutorial.

    Some examples:

    .* - matches any letter
    ^abc.* - matches a text starting with abc
    .*abc.* - matches a text that contains abc
    

    Action

    If the condition matches the incoming SMS message, the SQL commands in the section will be executed. You can use one ore more SQL SELECT statements to query the information for the response messages and you can use SQL INSERT, SQL UPDATE or any other SQL statement to modify the database. Before the SQL commands are executed on the database, the following words are replaced in them:

    $originator - is replaced to the sender telephone number of the messages
    $recipient - is replaced to the telephone number that received the
    message
    $messagedata - is replaced to the message text
    $keyword - is replaced to the keyword in the message
    $senttime - is replaced to the timestamp, that represents when the
    message was sent
    $receivedtime - is replaced to the timestamp, that represents when the
    message was received
    $messagetype - is replaced to the message type (in most cases this will
    be SMS:TEXT)
    $id - is replaced to the unique string identifier of the message
    $operator - is replaced to the name of the service provider connection
    that received the message
    

    The SQL statements will be executed in the order they follow each other. Every SQL statement must be written on a single line.

    (Hint: In most cases you will only use one SQL SELECT to get the content for the response SMS message.)

    Response

    When SELECT SQL statements are executed, they can return one or more response messages. A response message is a row in the result set of the SQL select. A row in the result set should contain the following columns:

    recipient - The 1st column in the result set (Mandatory)
    messageData - The 2nd column in the result set (Mandatory)
    messageType - The 3rd column in the result set (Optional)
    sender - The 4th column in the result set (Optional)
    operatorNames - The 5th column in the result set (Optional)
    

    The SMS gateway will process the returned results and will send them as SMS messages.

    Example

    The following is an example script that matches two keywords: RED and BLUE and handles unmatched incoming messages with a default response.

    C:\Program Files\Ozeki\OzekiNG - SMS Gateway\config\TestApp\sqlscript.txt
    k^RED
    INSERT INTO  log (sender,message) VALUES ('$sender','$messagedata');
    SELECT '$sender',msg FROM autoreplymessage WHERE keyword='red'
    
    k^BLUE
    SELECT '$sender',msg FROM autoreplymessage WHERE keyword='blue'
    
    k.*
    SELECT '$sender',msg FROM autoreplymessage WHERE keyword='default'
    

    Autoreply User

    This page explains how to install and configure an autoreply user for SMS messaging using the graphical user interface of the Ozeki NG - SMS Gateway software. You will be provided with step-by-step installation and configuration instructions, including explanations of configuration examples.

    Ozeki NG - SMS Gateway supports the installation and configuration of an autoreply user (among several other users and applications, see the Users and Applications page).

    The autoreply user allows you to automatically reply to and forward incoming messages to various phone numbers, based on the sender address and the message content.

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure an autoreply user.

    Installation

    To start installing and configuring an autoreply user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the panel you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To start installing an autoreply user, click the Install link in the respective entry in the list (Figure 2).

    installing an autoreply user
    Figure 2 - Installing an autoreply user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the Autoreply user installation panel. Here, you need to enter a unique username in the Username field.

    Configuration

    The Autoreply script tab of the Configuration panel will show up after you have specified a unique username for the autoreply user (Figure 3).

    the autoreply script tab
    Figure 3 - The Autoreply script tab

    This panel contains two edit boxes. The upper edit box is for the name of the autoreply script file. The default name includes the unique name you have given the autoreply user in the Autoreply user installation panel. If you are content with the default name, leave this edit box unchanged. If not, rename the default autoreply script file.

    In the lower edit box, you can edit a script for one or more automatic reply and message forwarding rules. To maintain readability, you can include comments in your script. Indicate them with a hashmark (#) at the beginning of each line of a comment. The edit box contains a configuration script, which you can use as a template to edit your script.

    Each automatic reply or message forwarding rule consists of a part called filter and a part called action. The filter decides whether the action should be applied to an incoming message. The filter can be used to identify certain phone numbers or incoming message text and react accordingly. The action part of the rule can be used to create a reply or to forward the message to another GSM phone number.

    Example configurations

    Replying to all incoming messages

    Rule:

    n.* SENDER Thank you for your message
    

    Interpretation: Reply to the sender of every incoming message.

    Explanation: In the filter of the rule, n.* means that this rule should be applied to all incoming messages (n means that the filter applies to the sender phone number, and .* means that every number is accepted.)

    In the action of the rule, SENDER means that the sender of the incoming message is the recipient of the reply message. Thank you for your message is the text of the reply message.

    Forwarding all incoming messages to a specified phone number

    Rule:

    n.*
    +36203105366 MSG

    Interpretation: Forward all incoming messages to +36203105366.

    Explanation: In the filter of the rule, n.* means that this rule should be applied to all incoming messages (see the previous example).

    In the action of the rule, +36203105366 means the recipient phone number that the reply message will be sent to. (Make sure you specify the phone number in international format, starting with a leading plus sign (+). MSG> means that the text of the incoming message will be inserted into the outgoing message. To forward an incoming SMS message to more than one phone number, add a new line to the rule, containing another phone number and MSG (e.g.: +36205222245 MSG) You need to specify each recipient phone number in a separate line.

    Forwarding to a specific number if the sender phone number matches

    Rule:

    n^+36209937723
    +36205222245 MSG

    Interpretation: If an incoming SMS message is from the +36209937723 phone number, forward it to +36205222245.

    Explanation: In the filter of the rule, n.^+36209937723 means that this rule should be applied if the phone number is +36209937723.

    In the action of the rule, +36205222245 means the recipient phone number that the reply message will be sent to. MSG means that the text of the incoming message will be inserted into the outgoing message. To forward an incoming SMS message to more than one phone number, add a new line to the rule, containing another phone number and MSG (eg.:+36205722246 MSG). You need to specify each recipient phone number in a separate line.

    Forwarding to one or more phone numbers based on the keyword of the incoming message

    Rule:

    # If the message starts with the word "important",
    forward it # to +36205222245 and +36203105366
    m^important.*
    +36203105366 SENDER: MSG
    +36205222245 MSG 

    Interpretation: If the message starts with the word "important", forward it to +36205222245 and +36203105366 including the sender phone number in the text of the message.

    Explanation: Above the rule there is a comment written in two lines, each starting with a hashmark sign (#). The comment describes what the rule means. In the filter of the rule, m^important.* means that this rule should be applied if the message starts with the word "important".

    In the action of the rule, +36203105366 SENDER: MSG means that the incoming message will be forwarded to +36203105366 including the sender phone number in the text of the message.

    The +36205222245 MSG line means that the incoming message will be forwarded to +36205222245. The message forwarded to this number will not include the sender phone number of the incoming message.

    To configure logging related to the autoreply user, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log SMS messaging related to rules that have been applied (see the section about the Autoreply script tab above). You should check one or both of the checkboxes, as logfiles can be useful in debugging communication problems (Figure 4).

    logging options
    Figure 4 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box in the Logfile settings section, you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 4 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    In Advanced tab you can specify the phone number of the sender, and you can provide a username and a password to login. In the lower section of this tab you can enable Allow routing table override option. If routing table override is enabled, this user can specify the preferred service provider connection for each message. You can also enable Enable accounting for this user option. If you enable accounting, a credit limit can be set for this user. The user will not be allowed to send more messages then the credit limit.

    advanced tab
    Figure 5 - Advanced tab

    To modify the configuration or to view server events related to an installed user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 6).

    clicking a user related task link
    Figure 6 - Clicking a user-related task link

    AutoReplyEasy User

    This page explains how to install and configure an AutoReplyEasy user for SMS messaging using the graphical user interface of the Ozeki NG - SMS Gateway software.

    Ozeki NG - SMS Gateway supports the installation and configuration of an AutoReplyEasy user (among several other users and applications, see the Users and Applications page).

    The AutoReplyEasy user allows you to automatically reply to incoming messages, sending a reply message to the sender phone number of the incoming message.

    This feature makes the AutoReplyEasy user similar to the Autoreply User. However, there are some differences between them.

    The Autoreply user allows you to reply to and forward incoming messages to various phone numbers, based on the sender address and the message content. The AutoReplyEasy user, however, only allows you to automatically send a reply message to the sender phone number of the recipient message. The reply can be a plain text or a WAPPUSH SMS. A WAPPUSH SMS is basically a specially encoded message which includes a link to a WAP or webpage address.

    Unlike the Autoreply user, the AutoReplyEasy user does not require you to edit rules following a rule syntax in the autoreply script file. Instead of having to set rules in the script file, you only have to edit your reply message. (This is the reason for the distinction "Easy" in its name.)

    The reply message can contain the following special keywords. These keywords will be replaced to the appropriate content in the message text before the reply message is sent.

    $MSGThe incoming message text
    $SENDERThe originator number
    $RECEIVERThe recipient number

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure an AutoReplyEasy user.

    Installation

    To start installing and configuring an AutoReplyEasy user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the panel you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To start installing an AutoReplyEasy user, click the Install link in the respective entry in the list (Figure 2).

    installing an autoreplyeasy user
    Figure 2 - Installing an AutoReplyEasy user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the AutoReplyEasy user installation panel. Here, you need to enter a unique username in the Username field.

    Configuration

    The Autoreply script tab of the Configuration panel will show up after you have specified a unique username for the AutoReplyEasy user (Figure 3).

    the autoreplyeasy script tab
    Figure 3 - The AutoReplyEasy script tab

    This tab contains an uneditable text box, a dropdown menu and an editable text box.

    The uneditable text box is for the name of the AutoReplyEasy script file. This file name, which includes the unique name you have specified for your AutoReplyEasy user during the installation, is provided by the program. In the AutoReplyEasy type dropdown menu, you can select the type of your reply message. In the editable text box below, you can simply edit your reply message.

    To configure logging related to the AutoReplyEasy user, click the Logging tab in the Configuration panel.

    The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log SMS messaging related to rules that have been applied. You should check one or both of the checkboxes, as logfiles can be useful in debugging communication problems (Figure 4).

    logging options
    Figure 4 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box in the Logfile settings section, you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 4 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    In Advanced tab you can specify the phone number of the sender, and you can provide a username and a password to login. In the lower section of this tab you can enable Allow routing table override option. If routing table override is enabled, this user can specify the preferred service provider connection for each message. You can also enable Enable accounting for this user option. If you enable accounting, a credit limit can be set for this user. The user will not be allowed to send more messages then the credit limit.

    advanced tab
    Figure 5 - Advanced tab

    To modify the configuration or to view server events related to an installed user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click on the link of the task you wish to perform (Figure 6).

    configure link
    Figure 6 - Configure link

    Autoreply Easy user, how to send a WAP PUSH

    The autoreply easy user allows you to send other message types, then text. The most common alternative SMS type is WAP PUSH. This screenshot shows you how to configure the autoreply easy user to return a WAP PUSH message as the response.

    return a wap push message as the response

    How to send SMS or receive SMS from a Text file

    This chapter explains how to install and configure Ozeki NG SMS gateway in order to be able to send and receive SMS messages from a txt file. You will be provided with step-by-step instructions on how to install and configure the File user, that makes this possible, along with explanations about the different file formats you can use to send and receive SMS messages with the File user.

    A File user is an application, that allows you to send and receive messages using text files. When an incoming message arrives, the File user creates a text file for the message and places it into the incoming directory. If you would like to send a message, all you have to do is place a text file into the outgoing directory. The File user will periodically check this outgoing directory for messages to be sent. If it finds messages there, they will be sent out as SMS messages.

    When you install a File user, Ozeki NG - SMS Gateway will automatically create the incoming and the outgoing directory along with other directories for SMS messages related to the File user. These directories can be found in a collection directory named smsTemp by default. You can rename this collection directory and the subdirectories. However, make sure you specify them correctly for the File user in the respective edit boxes containing the paths in the General tab of the Configuration panel (see the Configuration section below).

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure a File user.

    Installation

    To start installing and configuring a File user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the panel you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To start installing a File user, click the Install link in the respective entry in the list (Figure 2).

    installing a file user
    Figure 2 - Installing a File user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the File user installation panel. Here, you need to enter a unique username in the Username field.

    General configuration

    The General tab of the Configuration panel will show up after you have specified a unique username for the File user (Figure 3).

    The upper section of the tab contains the File format dropdown menu. Select an appropriate file format: List, Simple or Verbose. (For more information, see the File formats section below.)

    Below the File format dropdown menu, there is an edit box. In this, you can specify how often the program should check the outgoing directory for messages to send. Enter the number of seconds in numerical format, representing a positive whole number. If you are content with the default specification (every 10 seconds), leave the edit box unchanged.

    setting the file format and the query frequency
    Figure 3 - Setting the file format and the query frequency

    The lower section of the tab contains five edit boxes containing paths to directories. Each path includes a different subdirectory name. As mentioned above, the installation of the File user automatically creates different directories for messages. The status of a message defines which directory it can be found in. Each path leads to a directory containing messages of a specific status (Figure 4).

    default paths
    Figure 4 - Default paths

    The first directory (INBOX) is for incoming messages, i.e., messages delivered to Ozeki NG - SMS Gateway and destined to the File user (according to inbound routing rules).

    The second directory (OUTBOX ) is for outgoing messages, i.e., messages originated by the File user for Ozeki NG - SMS Gateway to send out (according to outbound routing rules).

    The third directory (SENT) is for messages that have been successfully sent out and accepted by an SMS Center for delivery.

    The fourth directory (FAILED) is for messages that have failed to be sent out. These messages have not been accepted by the SMS Center for delivery.

    The fifth directory (DELIVERED) is for messages that have been delivered to the recipient phone. When Ozeki NG - SMS Gateway receives a delivery report from the SMS Center, a sent message will be inserted into this directory.

    Sending an SMS message

    When you wish to send a message using the file plugin your application and the SMS engine will work on the same set of files. This cooperation can have conflicts if the same file is accessed by the SMS engine and your application at the same time. To avoid the possible conflicts you can use a locking mechanism when you use the File API.

    In the following example I will give you the steps you should take if you wish to send files using a safe way. (These steps are particularly important if you are using the network to put files to be sent into the SMSout directory. If you use FTP, NFS or Samba to access the remote directory make sure you follow these steps.)

    To perform sending 4 directories are used:

    1. C:\smsTemp\smsout\ - the outgoing directory
    2. C:\smsTemp\smssent\ - the directory that holds the messages that were successfully sent
    3. C:\smsTemp\smsfailed\ - the directory that holds the messages that could not be sent.
    4. C:\smsTemp\smsdelivered\ - the directory that holds the messages that have arrived to the destination handset.

    To send an SMS first you should create a "lock" file in the outgoing directory. A lock file is used to make sure the SMS Engine will not start to read the real file containing the messages while the file is still being written. The lock file is an empty file, that has a name that matches the real file. The lock file name has a special extension: .lock. This extension is appended to the end of the filename. After the lock file is created you can edit the real file containing the outgoing message text. When you are finished simply delete the lock file.

    Step 1.) Create: C:\smsTemp\smsout\mysms.sml.lock

    Step 2.) Create: C:\smsTemp\smsout\mysms.sml Write : C:/smsout/mysms.sml

    Step 3.) Delete: C:\smsTemp\smsout\mysms.sml.lock

    After you have created your file, you need to wait. The SMS Engine will delete your file, and will try to send the messages. When the sending is done a new text file will be placed into the smssent or the smsfailed directory based on the sending results. When the file is created the same locking steps are performed.

    Please take a look at thefollowing diagram:

    sending and sms using the file user
    Figure 5 - Sending an SMS using the file user

    If the new text file is saved into the sent directory, it means the message was successfully delivered to the SMS network. If delivery reports are configured on the service provider connection configuration form and delivery reports are supported by the SMS service provider, you will receive a status report SMS when the SMS is delivered to the destination handset. If this happens, the SMS engine will create a text file with the same locking steps in the smsdelivered directory.

    File formats

    As mentioned above, Ozeki NG - SMS Gateway supports the following file formats: simple, verbose and list. You can use any of these formats to send a message. To select a particular format use the configuration form of the file user.

    The simple file format

    If you select the simple file format in the dropdown menu (see Figure 3 above), each incoming message will be saved in a separate file. The name of the file is the sender phone number, and the only line of the file contains the message. For example:

    c:\smsout\+36203105366

    Hello world
    

    To send messages using the simple file format, create a separate text file for each outgoing message and place these files into the smsout directory. The name of the text file has to be the recipient phone number. When the message has been sent out, the text file will be automatically deleted from the directory.

    Note that if you want to send more than one message to the same recipient phone number, you can only place a new message into the outgoing directory if the previous message has been sent out and is no longer there. This is because you cannot have two files with the same name in the same directory. If the previously inserted file is still in the directory (has not yet been sent out), you can only insert the new file by overwriting the previous file. Therefore, if you insert a new file with the same name (which is the telephone number of the recipient) into the outgoing directory, your previous SMS message will not be sent out at all. This is because the file containing it will be replaced with a new one. Replacing the previous file is essentially equal to deleting it.

    Accordingly, if you select the simple file format, an incoming message from a specific sender phone number will overwrite (delete) the previous message from the same number. Therefore, it is always only the latest message from a specific phone number that will be saved in the inbox. This may be inconvenient if you wish to save more than one SMS message from the same sender. Take this into consideration when you select the file format in the respective dropdown menu.

    On the other hand, this file format may be convenient for position tracking SMS applications. The movement of vehicles can be tracked with a GSM device transmitting the vehicle's position coordinates via SMS to the File user of Ozeki NG - SMS Gateway. In this case, it may not be problematic (or it may even be desirable) that only the latest report is saved in the inbox.

    The verbose file format

    The verbose file format is similar to the simple file format inasmuch as each message resides in a separate file. The difference is that the file contains more information than just the message text. The main advantage of this file format is that you can place into the directory more than one file containing a message to the same destination (phone number). You can give each file any name, which has to be different from the name(s) of any other files(s). Note that the extension of the file has to be .sms .

    The first line in the file has to contain the sender phone number, the second line contains the recipient phone number, and the message text follows these in the next line. For example:

    c:\smsout\anyname.sms

    +36203105366
    +36209937723
    The message text

    The list file format

    The list file format is a convenient way to send and receive a large number of SMS messages. In this case more than one message is stored in the same file.

    For outgoing messages you should create a text file in which each line contains a message with the recipient's phone number (in international format) before it. The phone number and the message text is separated by a space character. When the messages are ready to be sent, place the file into the outgoing (smsout) directory. The file name needs to have the .sml extension (sml stands for SMS list). For example:

    c:\smsout\list.sml
    +36205555366 This is the first message
    +36209937723 This is the second message
    +36307789723 Use Ozeki NG - SMS Gateway!
    

    You should place this text file into the c:tmpsmsout directory. For example you can save it as "c:\tmp\smsout\mysms.txt"

    The xml file format

    The XML file format can also be used for sending SMS messages with Ozeki NG SMS Gateway. In this case you need to save the file in XML extension and you should specify the XML file in the following format:

    
      
          ORINIGATOR_NUMBER 
          RECIPIENT_NUMBER 
          Message text 
           
          SMS:TEXT:FORMATTED 
      
    
    

    • Between Originator tags you can find the originator number.
    • Between Recipient tags you can find the recipient number.
    • Between Text tags you can find the text message.
    • Between Time tags you can find the exact time when the message needs to be sent out.

    Logging configuration

    To configure logging related to the File user, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log file content.

    You should check one or both of the checkboxes, as logfiles can be useful in debugging communication problems (Figure 5).

    logging options
    Figure 6 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box in the Logfile settings section, you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 4 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    In Advanced tab you can specify the phone number of the sender, and you can provide a username and a password to login. In the lower section of this tab you can enable Allow routing table override option. If routing table override is enabled, this user can specify the preferred service provider connection for each message. You can also enable Enable accounting for this user option. If you enable accounting, a credit limit can be set for this user. The user will not be allowed to send more messages then the credit limit.

    advanced tab
    Figure 7 - Advanced tab

    To modify the configuration or to view server events related to an installed user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 6).

    clicking a user realted task link
    Figure 8 - Clicking a user-related task link

    How to send SMS text messages in CSV file format

    This guide provides you detailed information on how you can send SMS text messages in CSV file format with Ozeki NG SMS Gateway. Please follow the configuration guide below to be able to apply this solution.

    It is possible to export Excel tables into CSV file format. In this way data of the table will be structured in a table of lists form. In the created CSV file each line corresponds to a row of the original table. Within a line, fields are separated by commas, and each field belongs to one table column. (Please see Figure 1 for an Excel table and Figure 2 for an exported CSV file from the table).

    Finally you will be able to send data in CSV file format via SMS text messages with the help of a File user in Ozeki NG SMS Gateway. This solution allows you to send text messages in a simple file format instead of Excel tables.

    Configuration

    Figure 1 demonstrates the Excel table that will be exported into CSV file format.

    excel table
    Figure 1 - Excel table

    On Figure 2 you can see the CSV file after the export.

    csv file after export
    Figure 2 - CSV file after export

    In Ozeki NG SMS Gateway go to "Add new user or application" and click on "install" next to File user interface to create a new file user (Figure 3).

    create a file user in ozeki ng sms gateway
    Figure 3 - Create a file user in Ozeki NG SMS Gateway

    On General tab select CSV from the dropdown menu as File format and click on "OK" (Figure 4).

    csv as file format
    Figure 4 - CSV as File format

    Now the CSV file needs to be copied into smsout folder (by default it is in c:\smsTemp\smsout\). Then Ozeki NG SMS Gateway sends out the messages (Figure 5).

    ozeki ng sms gateway sends out the messages
    Figure 5 - Ozeki NG SMS Gateway sends out the messages

    On Figure 6 you can see the sent messages in "Sent" folder in Ozeki NG SMS Gateway.

    sent messages in ozeki ng sms gateway
    Figure 6 - Sent messages in Ozeki NG SMS Gateway

    How to send SMS from shared files (shared by network drivers) with File user of Ozeki NG SMS Gateway

    On this page you can find the step-by-step configuration guide on how to send SMS messages from shared files with the File user of Ozeki NG SMS Gateway.

    To create this solution first you need to configure Ozeki NG SMS Gateway software to be able to send SMS messages from your PC. You can find step-by-step guide at:

    Quick start guide. The Ozeki SMS software is able to connect to the mobile network either with a GSM modem connection or IP SMS connection.

    After you have configured your Ozeki NG SMS Gateway software and you can also install a service provider connection to connect the SMS software to the mobile network.

    On how to send SMS messages from the File user of Ozeki NG SMS Gateway please read the following page: How to send SMS from a Text file.

    Configuration guide

    After you have configured Ozeki NG SMS Gateway software you can start the configuration process for sending SMS from shared files.

    The main configuration steps will be the follows:

    1. Stop Ozeki NG SMS Gateway service in Services window
    2. Disable Simple File Sharing option at Folder options menu
    3. Go to the installation folder of Ozeki NG SMS Gateway
    4. Select Properties of Ozeki NG SMS Gateway
    5. Add a NETWORK SERVICE user at Security tab
    6. Go to Properties of Ozeki NG SMS Gateway in Services window
    7. On Log On tab it needs to set the NETWORK SERVICE user
    8. Open Groups menu at Local user and Groups window
    9. Right click on Administrators and select Add to group menu item
    10. Add NETWORK SERVICE user
    11. Start Ozeki NG SMS Gateway service
    12. Specify the network path that is set to the driver in Ozeki NG SMS Gateway: \\computer_name\shared_folder

    Now please follow the step by step configuration guide below:

    First, start to run Services (Figure 1).

    services
    Figure 1 - Services

    Stop Ozeki NG SMS Gateway service (Figure 2).

    stop the service
    Figure 2 - Stop the service

    In Tools menu select Folder Options... Figure 3).

    folder options
    Figure 3 - Folder Options...

    Click on View tab and disable Use simple file sharing option (Figure 4).

    disable use simple file sharing
    Figure 4 - Disable Use simple file sharing

    Now go to the installation folder of Ozeki NG SMS Gateway. Right click on this folder and select Properties (Figure 5).

    installation folder of ozeki ng sms gateway
    Figure 5 - Installation folder of Ozeki NG SMS Gateway

    In Ozeki NG SMS Gateway Properties window select Security tab and click on Add button to add a network service user (Figure 6).

    add a network service user
    Figure 6 - Add a network service user

    Then click on Advanced (Figure 7).

    select advanced
    Figure 7 - Advanced...

    Click on Find now (Figure 8).

    find now
    Figure 8 - Find now

    Select Network service in the list and click on OK (Figure 9).

    network service
    Figure 9 - Network service

    Click on OK again (Figure 10).

    network service appeared
    Figure 10 - Network Service appeared

    You can see that Network Service appeared in the list. Enable Full Control checkbox that will enable the other options below automatically. With this step you provide permission to this Network Service user to get access to the folder of Ozeki NG SMS Gateway (Figure 11).

    enable full control
    Figure 11 - Enable Full Control

    Go to Services window and right click on Ozeki NG SMS Gateway. Click on Properties option (Figure 12).

    properties of ozeki ng sms gateway
    Figure 12 - Properties of Ozeki NG SMS Gateway

    On Log on tab of Ozeki NG SMS Gateway Properties window enable This account option. In this way, the browse button will be active so click on this browse button (Figure 13).

    enable this account
    Figure 13 - Enable This account

    Click on Advanced option (Figure 14).

    select advanced
    Figure 14 - Advanced...

    Click on Find now (Figure 15).

    find now
    Figure 15 - Find now

    Select Network Service in the list and click on OK (Figure 16).

    select network service
    Figure 16 - Select Network Service

    Click on OK again (Figure 17).

    click on ok
    Figure 17 - Click on OK

    On Log on tab of Ozeki NG SMS Gateway Properties window please make sure that Password and Confirm password field is NOT filled. Click on OK (Figure 18).

    log on tab
    Figure 18 - Log on tab

    Start Local User Manager(Figure 19).

    start local user manager
    Figure 19 - Start Local User Manager

    Select Administrators from Groups menu. Right click on Administrators and click on Add to group... (Figure 20).

    add to group
    Figure 20 - Add to group...

    In Administrator Properties window click on Add button (Figure 21).

    click add
    Figure 21 - Add

    Add the Network Service user: Click on Advanced (Figure 22).

    select advanced
    Figure 22 - Advanced...

    Click on Find now (Figure 23).

    find now
    Figure 23 - Find now

    Select Network Service in the list and click on OK (Figure 24).

    select network service
    Figure 24 - Select Network Service

    Click on OK again (Figure 25).

    click on ok
    Figure 25 - Click on OK

    On Administrators Properties window also click on OK (Figure 26).

    administrators properties
    Figure 26 - Administrators Properties

    Finally, start Ozeki NG SMS Gateway service in Services window (Figure 27).

    start service
    Figure 27 - Start service

    Specify the path to the network folder on the Configuration panel of File user in Ozeki NG SMS Gateway (Figure 28).

    specify the path to the network folder
    Figure 28 - Specify the path to the network folder

    E-mail User

    This chapter provides an introduction to the E-mail user. You can learn what it can be used for, and how to install it using the graphical user interface of the Ozeki NG - SMS Gateway software. You are also provided with links to respective pages instructing you how to configure it to send an e-mail as an SMS message and to send an SMS message as an e-mail.

    Ozeki NG - SMS Gateway allows, among others (see the Users and Applications page), the installation and configuration of an E-mail user. This is an automated user that can be used to realize two-way e-mail - SMS gateway service. It can forward an incoming e-mail as an SMS message to a specified phone number (or phone numbers), and an incoming SMS message as an e-mail to a specified e-mail address or e-mail addresses (Figure 1).

    system architecture of the service
    Figure 1 - System architecture of the service

    The Ozeki NG - SMS Gateway software acts as an e-mail client, using an SMTP server to send, and a POP3 server to receive messages. You can use its graphical user interface to install and configure an E-mail user.

    For detailed instructions on how to realize a two-way E-mail - SMS gateway service and a detailed explanation of Figure 1, check out the How to Set up an E-mail - SMS Gateway page.

    To start installing and configuring an E-mail user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 2).

    adding a user
    Figure 2 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the panel you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To start installing an E-mail user, click the Install link in the respective entry in the list (Figure 3).

    installing an email user
    Figure 3 - Installing an E-mail user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the E-mail user installation panel. Here, you need to enter a unique username in the Username field.

    After specifying a unique username for the E-mail user, the E-mail to SMS tab of the Configuration panel will show up. Now you can start to configure the user. To find out how to configure it to forward an incoming e-mail as an incoming SMS message to a specified phone number, check out the E-mail to SMS Configuration page. To learn how to configure it to send an incoming SMS message to a specified e-mail address, read the SMS to E-mail Configuration page.

    To modify the configuration or to view server events related to an installed user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 4).

    user related task links
    Figure 4 - User-related task links

    E-mail to SMS Configuration

    This section provides you with step-by-step instructions on how to configure the E-mail user of the Ozeki NG - SMS Gateway software to forward an incoming e-mail as an SMS message to a specified phone number.

    The E-mail user, which is one of the installable users of Ozeki NG - SMS Gateway, can forward an incoming e-mail as an SMS message to a specified phone number. It will periodically download e-mails from a POP3 e-mail account and forward the first 160 characters of the body of an e-mail to the phone number specified in the configuration form of the user. It can also forward an e-mail as an SMS message to a phone number (or phone numbers) specified in the subject line of the e-mail (Figure 1).

    incoming email sent out as sms
    Figure 1 - Incoming e-mail sent out as SMS

    After the installation of the E-mail user (for installation instructions, check out the E-mail User page), you can start to configure it using the graphical user interface of the software.

    After specifying a unique username for the E-mail user, which is the last step of the installation, the E-mail to SMS tab of the Configuration panel will show up. This tab consists of POP3 server, Recipient settings, Filter e-mail messages and Advanced section (Figure 2).

    the email to sms tab
    Figure 2 - The E-mail to SMS tab

    As mentioned above, Ozeki NG - SMS Gateway can periodically download incoming e-mail messages from a POP3 account. The downloaded e-mail messages will be forwarded by SMS to a specified phone number. The subject line of the e-mail can also contain telephone numbers.

    In the POP3 Server edit box in the POP3 settings section, specify the address of the server.

    In the Port edit box, enter the number of the POP3 port.

    In the POP3 Username edit box, specify the username of the POP3 user account.

    In the POP3 Password edit box, specify the password of the POP3 user account.

    In the Download interval edit box, you can specify how often the program should check the POP3 account for new messages to download.

    In the Recipient settings section, specify a recipient phone number in the Send SMS to phone numbers edit box. This is the phone number that the SMS (the first 160 characters of the e-mail) will be sent to. Specify it in international format, starting with the leading plus sign (+). You can check the following two check boxes: Use phone numbers included in the e-mail subject and Use phone numbers in the to address (+36123647@domain.com format) if it is required

    If you check the Use phone numbers included in the e-mail subject checkbox below, the SMS will be sent to the phone number(s) in the subject line of the e-mail if it contains any. In this case, the SMS message will not be sent to the phone number specified in the Send SMS to (phone number) edit box. It will only be sent to the phone number(s) specified in the e-mail subject line. If it contains more than one phone number, they have to be separated with a semicolon. It should look something like this: +36703384532;+36303658734;+36203462111

    the recipient settings section
    Figure 3 - The Recipient settings section

    In the Filter e-mail messages section, you can make specifications as to which e-mails should be forwarded as SMS messages to one or more mobile phones. As you may receive a large number of e-mails (including a great deal of spam), you may have to pay a large amount of money if all of them are forwarded via SMS. Therefore, it is advisable to specify the sender(s), the receiver(s) and the keyword(s) in the subject lines of the e-mails to be forwarded via SMS (Figure 4).

    the filter email messages section
    Figure 4 - The Filter e-mail messages section

    In the From e-mail address(es) edit box, you can specify the e-mail address(es) from which e-mails should be forwarded via SMS (e.g.: somebody100@hotmail.com). You can enter one or more e-mail addresses, separated with a semicolon (;).

    In the To e-mail address(es) edit box, you can specify the e-mail address(es) of recipients whose incoming e-mails should be forwarded via SMS (e.g.: somebody100@yahoo.com). You can enter one or more e-mail addresses, separated with a semicolon (;).

    In the Keyword(s) in Subject edit box you can specify one or more keywords that should be included in the subject line(s) of email(s) to be forwarded via SMS (e.g.: order). You can enter one or more keywords, separated with a semicolon (;).

    The specifications in Figure 4 above will result in the E-mail user forwarding only e-mails sent from somebody100@hotmail.com to somebody100@yahoo.com, including the keyword "order" in their subject lines. You could add other sender and recipient e-mail addresses or keywords in the respective edit box, which would increase the set of e-mails to be forwarded as SMS messages.

    If you need different specifications, e.g. you want the E-mail user to forward an e-mail only if the sender address is somebody100@hotmail.com, the recipient is someone200@yahoo.com, and the keyword is "invoice", you need to add and configure another E-mail user. If you put someone200@yahoo.com next to somebody100@yahoo.com, and "invoice" next to "order", the number of possible combinations of the sender address, the recipient address and the keyword will be increased. As a result, if an e-mail is from somebody100@hotmail.com, the recipient is somebody100@yahoo.com and the keyword is "invoice", then the email will be forwarded as an SMS message. To avoid this, specify the sender, the recipient and the keyword in the Filter e-mail messages section in the Configuration panel of a different E-mail user. (You can add, install and configure as many users as you like.)

    In Advanced section you can enable the following options: Send e-mail to sender if SMS was delivered to network, Send e-mail to sender if SMS was delivered to handset, Send e-mail to sender if SMS was not delivered because of an error.

    In the Maximum message length edit box, specify how many of the first characters of the e-mail message should be sent as an SMS message. Enter the number in numerical format representing a positive whole number. If you specify a larger number than 160, a concatenated (i.e. more than one) SMS message will be sent. A long message will be split into single pieces. Then, each piece can contain a maximum of 153 characters. This is because the information for concatenation needs to be stored in the SMS. Each piece will be sent as a single SMS message. When they reach the destination, the recipient mobile phone will combine them back to one long message. If you are content with the default value (160) in the edit box, leave it unchanged.

    If you check the Include the sender e-mail address in the SMS checkbox, you can include the sender e-mail address at the beginning of the downloaded e-mail message (Figure 5).

    the advanced tab
    Figure 5 - The Advanced tab

    To find out how to configure the E-mail user of the Ozeki NG - SMS Gateway to send an incoming SMS message as an e-mail, check out the SMS to E-mail Configuration page.

    For detailed instructions on how to realize a two-way E-mail - SMS gateway service, check out the How to Set up an E-mail - SMS Gateway page.

    Google mail (Gmail) to SMS and SMS to Gmail Configuration

    This section provides you with step-by-step instructions on how to configure the Gmail to forward the incoming emails to Ozeki NG E-mail user and how to receive email notifications from your incoming SMS messages.

    Gmail to SMS configuration

    The Ozeki NG - SMS Gateway can periodically download incoming e-mail messages from your GMail POP3 account. The downloaded e-mail messages will be forwarded by SMS to a specified phone number. The subject line of the e-mail can also contain telephone numbers.

    google mail settings pop access and forwarding pop access
    Figure 1 - Google Mail - Settings/Pop Access & Forwarding/POP Access

    Ozeki NG - POP3 settings in the E-mail user:

    • POP3 Server: pop.gmail.com
    • Port: 995
    • POP3 Username: your login name
    • POP3 Password: your password
    • SSL: enable

    You need to check the SSL box.

    popthree settings in the email user of the ozeki ng
    Figure 2 - POP3 settings in the E-mail User of the Ozeki NG

    SMS to Gmail Configuration

    If an SMS message arrives in the Ozeki NG, it can be forwarded to your Gmail e-mail address.

    smtp server settings in the sms to email tab
    Figure 3 - SMTP server settings in the SMS to E-mail tab

    Ozeki NG - SMTP settings in the E-mail user:

    • SMTP Server: smtp.gmail.com
    • SMTP Port: 25

    My SMTP server requires authentication.

    • SMTP Username: your login name
    • SMTP Password: your password
    • Use this e-mail address as the sender address: ozekisms@gmail.com

    My SMTP server requires SSL connection.

    Yahoo mail to SMS and SMS to Yahoo mail Configuration

    You can read a step-by-step guide on how to configure the Yahoo mail to forward the incoming emails to Ozeki NG E-mail user and how to receive email notifications from your incoming SMS messages to your Yahoo mail box.

    Yahoo mail to SMS configuration

    The Ozeki NG - SMS Gateway can periodically download incoming e-mail messages from your Yahoo mail POP3 account. The downloaded e-mail messages will be forwarded by SMS to a specified phone number. The subject line of the e-mail can also contain telephone numbers.

    yahoo mail options mail pop access forwarding
    Figure 1 - Yahoo mail - Options/Mail/Pop Access & Forwarding

    yahoo mail specify the web pop access
    Figure 2 - Yahoo mail - Specify the Web & POP Access

    Ozeki NG - POP3 settings in the E-mail user:

    • POP3 Server: pop.mail.yahoo.co.uk
    • Port: 110
    • POP3 Username: your login name
    • POP3 Password: your password
    • SSL: unchecked

    If you wish to use SSL your port number will be 995 instead of 110.

    SMS to Yahoo mail configuration

    If an SMS message arrives in the Ozeki NG, it can be forwarded to your Yahoo e-mail address.

    Ozeki NG - SMTP settings in the E-mail user:

    • SMTP Server: smtp.mail.yahoo.co.uk
    • SMTP Port: 25
    • My SMTP server requires authentication.
    • SMTP Username: your login name
    • SMTP Password: your password
    • Use this e-mail address as the sender address: ozekisms2007@yahoo.co.uk

    The SMTP server doesn't require SSL connection.

    SMS to E-mail Configuration

    This page provides you with step-by-step instructions on how to configure the E-mail user of the Ozeki NG - SMS Gateway software to forward an incoming SMS message as an e-mail to a specified e-mail address.

    The E-mail user, which is one of the installable users of Ozeki NG - SMS Gateway, can forward incoming SMS messages from a standard e-mail client to a specified e-mail address (or e-mail addresses). It will send e-mails using an SMTP server. The e-mail address is the first word of the SMS message. You can also specify this e-mail address in the configuration form of the E-mail user.

    incoming sms sent out as email
    Figure 1 - Incoming SMS sent out as e-mail

    You can use the graphical user interface of Ozeki NG - SMS Gateway to send an incoming SMS message as an e-mail.

    After specifying a unique username for the E-mail user, the Configuration panel will show up. To start performing the SMS to E-mail configuration, click the SMS to E-mail tab.

    This tab consists of the SMTP server, Recipient, SMTP authentication, and Encoding sections (Figure 2).

    the smtp server section of sms to email tab
    Figure 2 - The SMTP server section of SMS to E-mail tab

    Outgoing e-mails are relayed by an SMTP server. In the SMTP server section, you can specify the address and the port of the SMTP server. Enter the information in the respective edit boxes.

    If an SMS message arrives, it can be forwarded to one or more e-mail addresses. You can specify a e-mail address in the configuration form, or you can rely on the e-mail address information in the SMS itself.

    In the To (e-mail) edit box in the Recipient section, you can specify the e-mail address to send incoming SMS messages to. Check the Use e-mail address in SMS if present checkbox below the edit box to make the program send the SMS message to the e-mail address specified in the SMS message itself. If you check this checkbox, the e-mail will not be sent to the e-mail address specified in the configuration form. It will only be sent to the e-mail address(es) specified in the SMS itself. The e-mail addresses have be separated with a colon. It should look something like this: someaddress@hotmail.com;anotheraddress@yahoo.com;a_third_address@freemail.hu

    In the CC (e-mail) edit box at the bottom of the Recipient section, you can specify another e-mail address to send a copy of an incoming SMS message to. Note, however, that if you rely on the e-mail addresses in the SMS itself, the e-mails will not be sent to this address. Then, they will only be sent to the e-mail addresses specified in the SMS (Figure 3).

    the recipient section of sms to email tab
    Figure 3 - The Recipient section of SMS to E-mail tab

    If your SMTP server requires authentication, open the SMTP authentication section and set the username and password (Figure 4).

    Some SMTP servers require user authentication for security reasons. To send messages using such an SMTP server, check the My SMTP server requires authentication checkbox, and specify your SMTP username and password in the respective edit boxes.

    the smtp authentication section of sms to email tab
    Figure 4 - The SMTP authentication section of SMS to E-mail tab

    To find out how to configure it to forward an incoming e-mail as an incoming SMS message to a specified phone number, check out the E-mail to SMS Configuration page.

    For detailed instructions on how to realize a two-way E-mail - SMS gateway service, check out the How to Set up an E-mail - SMS Gateway page.

    ERROR 2541 - Mail loop prevention

    When you setup an e-mail to SMS gateway, you might receive the following error message: "ERROR 2541: This e-mail will be not sent as SMS to prevent SMS loops remove the SMS/REPORT tag from the subject line."

    This error message happens if you have the [SMS] tag or the [REPORT] tag in the subject line of the downloaded e-mail.

    When the Ozeki software sends a message it returns status reports in e-mail to the sender e-mail address about the delivered message. Status report e-mails contain information such as when the message was delivered to the mobile network, or when the message was delivered to the mobile handset. These status report emails have the [REPORT] tag in the subject line. If a status report e-mail is downloaded by the Ozeki NG SMS Gateway software for sending from a mailbox, it will not be sent due to this [REPORT] tag.

    This loop prevention feature is included, because it is quite frequent, that the Ozeki NG SMS Gateway software is configured in a way to take messages from a mailbox for delivery, and to deliver the status reports to the same mailbox.

    The [SMS] tag is used in a similar way. It is used for incoming messages. If a message comes in the e-mail user can forward it to a mailbox as an e-mail message. When it composes the e-mail message, it includes the [SMS] tag in the subject line. This is very useful, because it the same mailbox is used for outgoing messages, no conflict will happen, since incoming SMS messages will not be sent.

    HTTP Client User

    This chapter explains how to install and configure an HTTP Client user for SMS messaging using the graphical user interface of the Ozeki NG - SMS Gateway software.

    Ozeki NG - SMS Gateway allows, among others (see the Users and Applications page), the installation and configuration of an HTTP Client user.

    The HTTP Client takes incoming messages and passes them in an HTTP GET or an HTTP POST request to an external web server. The HTML page returned by the web server can contain SMS messages that will be sent by the server (Figure 1).

    ozeki ng sms gateway as an http sms gateway
    Figure 1 - Ozeki NG - SMS Gateway as an HTTP SMS Gateway

    The HTTP client is a very convenient feature of Ozeki NG Gateway, as it can translate mobile communication into HTTP-based communication. The Ozeki NG Gateway works as both a gateway and a translator between mobile communication and the Internet. It enables you to create HTTP client connections that can forward messages to a web address (URL).

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure any user.

    To start installing and configuring an HTTP Client user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 2).

    adding a user
    Figure 2 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the page you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To add an HTTP user, click the Install link in the respective entry in the list (Figure 3).

    installing an http client user
    Figure 3 - Installing an HTTP Client user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the HTTP Client user installation panel. Here, you need to enter a unique username in the Username field.

    Once you have installed an HTTP Client user, you can start to configure it. After you have provided a unique name for the HTTP Client user and clicked OK, the Configuration panel will open.

    The first tab that will show up is the Incoming tab. In this panel you need to specify HTTP Client settings. This information is provided by the SMS service provider when you subscribe to the service (Figure 4).

    the incoming tab
    Figure 4 - The Incoming tab

    In the Target URL template you can specify the URL of the HTTP server. This URL can contain certain keywords that will be replaced before the URL is called. The following keywords can be used:

    KeywordDescription
    $originatorThis denotes the sender telephone number.
    $recipientThis denotes the recipient telephone number.
    $messagetypeThis the text containing the SMS message format.
    $messagedataThis contains the message text.
    $receivedtimeThis is the timestamp, denoting when the message was received.
    $receivedtime12The time when the message was received in 12 hour format.
    $senttimeThis is the timestamp, denoting when the message was sent.
    $senttime12The time when the message was sent in 12 hour format.
    $messageidThis is the unique identifier string of the message. This identifier is generated by Ozeki NG - SMS Gateway.
    $dcsThe SMS data coding scheme.
    $pidThe protocol identifier.
    $operatorThe instance name of the service provider connection that received the message.

    Below this template, you can specify the HTTP request method by selecting the GET or the POST radio button.

    The HTTP transaction is initiated by the SMS Gateway and is served by a web based application. ASP, PHP, JSP are good options to create a web based application that can process the incoming messages. These applications can optionally return one or more response SMS messages in the HTTP response. The format for the HTTP response is discussed on the SMS Message format page. An example of the response your application can return is:

    {SMS:TEXT}{Vodafone}{+447778888888}{+447779999999}{Hello world}

    In Outgoing tab you can specify the URL from which outgoing messages can be downloaded. A webpage can be checked periodically for messages to be sent. In Polling period you can set this period in seconds (Figure 5).

    outgoing tab
    Figure 5 - Outgoing tab

    In Delivered to network section of Delivery reports tab you can specify the HTTP URL to be called when a message is successfully delivered to the network. In Delivered to handset section the HTTP URL to be called when a message is successfully delivered to the handset can be defined. In Delivery error section you can set the HTTP URL to be called on message delivery errors (Figure 6).

    delivery reports tab
    Figure 6 - Delivery reports tab

    To configure logging related to the HTTP user, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 7).

    logging options
    Figure 7 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box in the Logfile settings section, you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 5 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    To modify the configuration or to view server events related to an HTTP Client user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 8).

    clicking a user related task link
    Figure 8 - Clicking a user-related task link

    Colour SMS User

    This chapter explains how to install and configure a Colour SMS user for SMS messaging using the graphical user interface of the Ozeki NG - SMS Gateway software.

    Ozeki NG - SMS Gateway allows, among others (see the Users and Applications page), the installation and configuration of a Colour SMS user.

    The Colour SMS protocol was developed by T-mobile Hungary for premium rate SMS services. It is an easy to use HTTP based SMS protocol. When a customer tries to access a premium rate SMS service by sending an SMS to a premium rate phone number, the SMSC transfers this message as an HTTP post request to the HTTP Server operated by the content provider. The content provider returns a response to the HTTP request in XML format. This response is sent as an SMS message back to the customer. The HTTP server operated by the service provider is Ozeki NG - SMS Gateway. This user implements this functionality (Figure 1).

    colour sms transport
    Figure 1 - Colour SMS transport

    Due to the nature of the HTTP protocol, it is always required to return a response to incoming messages in a short period of time. The Colour SMS protocol is often used with other connection methods, such as UCP to make delayed responses to incoming messages possible. Using a UCP connection, response messages can be sent at a later time, which is useful if you would like to set up periodic SMS notifications, such as weekly news service.

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure any user.

    To start installing and configuring a Colour SMS user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 2).

    adding a user
    Figure 2 - Adding a user

    This will bring up an interface consisting of two panels.

    • The panel on the left contains a list of users that have been installed. In the bar at the bottom of the page you can read how many users have been installed.
    • The panel on the right contains a list of users that can be installed.
    • Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets).
    • Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To add a Colour SMS user, click the Install link in the respective entry in the list (Figure 3).

    installing a colour sms user
    Figure 3 - Installing a Colour SMS user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the Colour SMS user installation panel. Here, you need to enter a unique username in the Username field.

    Once you have installed a Colour SMS user, you can start to configure it. After you have provided a unique name for the Colour SMS user and clicked OK, the Configuration panel will open.

    The first tab that will show up is the HTTP settings tab. In this panel you need to specify HTTP Client settings. This information is provided by the SMS service provider when you subscribe to the service (Figure 4).

    the http settings tab
    Figure 4 - The HTTP settings tab

    In the Target URL template you can specify the URL of the HTTP server. This URL can contain certain keywords that will be replaced before the URL is called.

    Below this template, you can specify the HTTP request method by selecting the GET or the POST radio button.

    To configure logging related to the Colour SMS user, click the Logging tab in the Configuration panel. The tab has a Logging and a Log file settings section. Here, you can choose whether to make the program write log entries about sent and received messages in human readable format and/or log low level communication. Choosing the latter option will make the program produce logfiles containing binary codes representing the communication data. You should check at least the Log sent and received messages in human readable format checkbox, as logfiles can be useful in debugging communication problems (Figure 5).

    logging options
    Figure 5 - Logging options

    In the Log file settings section of the tab, you can make specifications for the size and the number of available logfiles. Log rotation saves disk space, as it ensures that older (and probably no longer needed) logfiles will be automatically deleted from the log directory, which is specified in the Log directory text box. By default, the access path to the logfiles is: C:\Program Files\Ozeki\OzekiNG - SMS Gateway\Logs

    In the Maximum log file size text box in the Logfile settings section, you can specify the maximum size of a logfile. Once this size is reached, a new logfile will be created. Specify the number of kilobytes for the size of a logfile by entering a positive whole number. By default, the maximum logfile size is 8000 kB.

    In the Number of rotated files text box, specify the maximum number of rotated logfiles that are saved. Specify this number by entering a positive whole number. By default, the number of logfiles that are saved is 4 (see Figure 5 above).

    If you are content with the default specifications, leave the text boxes unchanged.

    To modify the configuration or to view server events related to a Colour SMS user, open the panel of the user's account. To do this, click the name of the user in the Users and Applications panel of the Management Console. In the panel of the user's account, click the link of the task you wish to perform (Figure 6).

    clicking a user related task link
    Figure 6 - Clicking a user-related task link

    Appstarter user

    In this tutorial you will find information on how you can set up Ozeki NG SMS Gateway with an external application. The Application starter feature of Ozeki NG SMS Gateway software product allows you to run programs in case an SMS message comes in. Please follow these steps to set up this helpful solution. You can find video tutorials above which give you some information on how to use this functionality.

    app starter indroduction

    Introduction

    In this guide you will find information on how you can you run an application with the Application starter user of Ozeki NG SMS Gateway when an incoming SMS is received. First you need to configure the SMS service provider connection in your Ozeki NG SMS Gateway. For receiving SMS messages the configuration of a service provider connection is neccessary. You can find information at this website on how to set up Ozeki NG SMS Gateway with SMPP service provider connection. On the following webpage you can find a list which includes moreservice providers. After you configured the service provider connection you can start the installation of the Appstarter user.

    Configuration in Ozeki NG SMS Gateway

    Please follow the steps below to configure the Appstarter user to start your application when an incoming message is received. The first step of the configuration is that you need to install the Appstarter user of Ozeki NG SMS Gateway. (Figure 1)

    installation of application starter
    Figure 1 - Installation of Application starter

    You need to provide the name of the Appstarter user. In this example the name is "appstarter". Please check the following steps to install Appstarter user. (Figure 2)

    setting appstarter name
    Figure 2 - Setting "appstarter" name

    Before you start using the Appstarter user, you should set the paramters poperly with the "Configure" link of the user. (Figure 3)

    configuring application starter
    Figure 3 - Configuring Application Starter

    When you set up the Appstarter you need to create a process.bat file. You can provide your own .bat file if you modify the parameters of the Appstarter user. In this sample you will get to know how you can write the default parameters of a message (sender,messagetext) into a text file. When an SMS is received the software will execute the process.bat file. Then you should create the .bat file with the following parameters:

    echo %1 %2 >> C:\inputsms.txt
    

    This way a new text file will be created when the sms received. It is also possible to run an external application. After you created this file, please save the file as process.bat. The script will get the parameters from the Appstarter user of Ozeki NG SMS Gateway. It is important that the applications you configured in the appstarter user, are started by the Ozeki NG service process. You can add your own application if you modify the Command textbox of the Appstarter user. (C:\Windows\notepad.exe). After you have changed the Command path of your application, the application will be started when you have received SMS messages. (Figure 4)

    starting an application notepad exe
    Figure 4 - Starting an application "notepad.exe"

    This process is a service process, that runs in the background. You can configure the Ozeki NG SMS Gateway service if you set the Control Panel/Administrative tools/Services menu item.

    opening the service properties form
    Figure 5 - Opening the service properties form

    After you opened the Services menu, in your services list you will find the service of Ozeki NG SMS Gateway. Please right click on the program and open Properties, then the Properties window will pop up. In the "Log on" tab please enable the "Allow service to interact with desktop" option. (Figure 6)

    setting properties
    Figure 6 - Setting properties

    Starting your Application by receving SMS messages

    Before you start receiving SMS messages please check your routing rules. You should configure an incoming routing rule and you should add a new routing rule from your service provider and set the Appstarter user as the destination parameter. After you configured the inbound routing you can start receiving messages. If you receive SMS messages your application will start automatically after the Appstarter user received the SMS messages.

    sms receiving
    Figure 7 - SMS receiving

    Conclusion

    To summarize the above mentioned, you can start your own application with the Ozeki NG SMS Gateway software product. With this tutorial you can run your own application by receiving an incoming SMS message. To achieve this function you can easily configure your Gateway in a few steps. With this solution you will gain a stable, reliable and well-functioning system.

    SMS Voting

    The SMS voting function of Ozeki NG SMS Gateway makes it possible to create various SMS voting events. This article provides detailed information on this built-in SMS voting application of Ozeki NG SMS Gateway. Among others you will read about this solution and you will know how to implement this functionality in your gateway.

    Fields of applications

    As it was mentioned above with SMS voting function of Ozeki NG SMS Gateway you can create various SMS voting events, for example, SMS quizzes, SMS polls, SMS surveys, etc. SMS voting is the best way to get people's opinion. It can be applied in entertainment and business sectors as well. So it can be used for two reasons: for entertainment and for marketing reasons.

    If you wish to use SMS voting for entertainment reasons, you will attract more people. As there are unlimited questions to be asked from people, you can always launch SMS voting. People like discuss their opinions on all sorts of topics and see whether they agree with others or not.

    If you want to apply SMS voting for marketing reasons you can make your company more flexible as you will always be informed about the opinions of your customers. Therefore you will always be up-to-date about their opinions about your products or services, in this way you can do the necessary steps for satisfy their exact needs. Furthermore, you can use SMS voting to collect the mobile phone numbers of your customers. This is possible by configuring the built in addressbook of the Voting user. Later you can use this phone number list to send advertisements to the cellphones.

    Benefits

    If you decide to implement this solution you will get a stable, reliable and well-working function in your system. You can attract more customers or audience with this functionality as it is fast and convenient for your customers or audience. You can also gain several advantages of the solution. For example, you do not need to fill forms to summarize the received votes. You can get the results in real-time, furthermore, you can display them with a screen device. In this way you can make your service more attractive for people. You will also enjoy benefits of SMS voting function if you wish to use it in business life. With the help of this solution you can attract more customers as you will be more flexible and well-informed about their needs. To know more about any customer related issue, you just need to launch SMS voting in that topic.

    Implementation of SMS voting function in Ozeki NG SMS Gateway

    Before you start to configure your gateway you need to connect your corporate IT system to the mobile network to transmit SMS messages. You can do this in two ways: you can use a GSM phone or modem attached to your PC, or you can deliver and receive messages over the Internet. Please go to Quick Start Guide to learn how you can connect your system to the mobile network.

    To be able to launch SMS voting services in your IT system you need to do some settings in Ozeki NG SMS Gateway. First, start the gateway software and login. If you login you can see the main screen of Ozeki NG SMS Gateway. On the right side of it, click on "Add new user or application" (Figure 1).

    add new user or application
    Figure 1 - Add new user or application

    Now select "Voting" user from the possible users from the list which appears. Click on "Install" next to "Voting" (Figure 2).

    install a new user
    Figure 2 - Install a new user

    Now in "Voting application installation" window you need to provide a name for your new user. In our example it is "vote01" (Figure 3). Then click on "OK".

    provide a name
    Figure 3 - Provide a name

    In the "Configuration" window you do not need to do any settings so just click on "OK" to continue (Figure 4). (Note that in this window you can set your gateway to send a response message to the sender to let him know about the arrival of his vote. The default response message is: "Thank you for the message!")

    general settings
    Figure 4 - General settings

    Now if you click on "Keywords" on the left side of the interface you can provide the necessary keywords for which people can vote (Figure 5). It means that one of these keywords should be sent in an SMS message. In this way the system will count it as one vote.

    keywords for voting
    Figure 5 - Keywords for voting

    The "User specific information" window appears. You need to type your keywords in these fields. In our example the keywords are "yellow", "red", "green". Please note, that you can provide maximum 20 keywords at together (Figure 6). If you typed your keywords click on "OK".

    provide your keywords
    Figure 6 - Provide your keywords

    If you click on "Results" on the left side of the interface, you can check the voting results (Figure 7).

    results of the voting process
    Figure 7 - Results of the voting process

    That is all the configuration steps you need to do to achieve SMS voting functionality in Ozeki NG SMS Gateway.

    To test this functionality I have sent two votes for "green" keyword. As you can see on Figure 8 the system counted them and they are displayed next to the keyword "green".

    test votes
    Figure 8 - Test votes

    To summarize the above mentioned up, SMS voting function of Ozeki NG SMS Gateway offers a fast and convenient service both to you and to your customers or partners. With the implementation of this solution you can make your company more flexible and attractive to people because you will be up-to-date about their opinions and even needs. Effectiveness also can be achieved as you can use SMS voting function for aimed marketing campaigns as well.

    If you wish to use SMS voting function of Ozeki's software to improve your business, please download Ozeki NG SMS Gateway.

    Outlook Mobile Service

    With Ozeki NG SMS Gateway, you can provide mobile messaging services to Microsoft Outlook 2007 and 2010 clients. For detailed configuration guide, please visit the following URLs:

    How to send SMS from MS Outlook 2007

    How to send SMS from MS Outlook 2010

    How to send and receive SMS messages from FTP server

    This page demonstrates how to install and configure Ozeki NG SMS Gateway to be able to send and receive SMS messages from an FTP server. Detailed instructions with screenshots will be provided on how to install and configure the FTP user and you will find further information on the various file formats that can be used, as well.

    An FTP user is an application, that allows you to send and receive messages using text files. It works as follows: if there is an incoming message, the FTP user creates a text file for this message and places it into the incoming directory on the ftp server. To send out messages you need to place a text file into the outgoing directory on the ftp server. The FTP user will periodically check this outgoing directory on the ftp server for messages to be sent. If it finds messages it will send out them as SMS messages. After sending out the messages, the FTP user place them into "Sent", "Delivered" or "Failed" folders according to their delivery status.

    When you install an FTP user, Ozeki NG - SMS Gateway will automatically create the incoming and the outgoing directory along with other directories for SMS messages related to the user. These directories can be found in a collection directory named smsTemp by default. You can rename this collection directory and the subdirectories. However, make sure you specify them correctly for the FTP user in the respective edit boxes containing the paths in the General tab of the Configuration panel (see the Configuration section below).

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure a FTP user.

    Installation

    To start installing and configuring an FTP user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels. The panel on the left contains a list of users that have been installed. In the bar at the bottom of the panel you can read how many users have been installed. The panel on the right contains a list of users that can be installed. Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets). Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To start installing a FTP user, click the Install link in the respective entry in the list (Figure 2).

    installing an ftp user
    Figure 2 - Installing an FTP user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the File user installation panel. Here, you need to enter a unique username in the Username field (Figure 3).

    provide a unique name
    Figure 3 - Provide a unique name

    General configuration

    The General tab of the Configuration panel will show up after you have specified a unique username for the FTP user.

    The upper section of the tab contains the File format dropdown menu. Select an appropriate file format: List, Simple or Verbose. (For more information, see the File formats section below.)

    Below the File format dropdown menu, there is an edit box. In this, you can specify how often the program should check the outgoing directory for messages to send. Enter the number of seconds in numerical format, representing a positive whole number. If you are content with the default specification (every 30 seconds), leave the edit box unchanged (Figure 4).

    setting the file format and the query frequency
    Figure 4 - Setting the file format and the query frequency

    The lower section of the tab contains five tabs containing paths to directories. Each path includes a different subdirectory name. As mentioned above, the installation of the File user automatically creates different directories for messages. The status of a message defines which directory it can be found in. Each path leads to a directory containing messages of a specific status (Figure 5).

    default paths
    Figure 5 - Default paths

    The first directory (INBOX) is for incoming messages, i.e., messages delivered to Ozeki NG - SMS Gateway and destined to the File user (according to inbound routing rules).

    The second directory (OUTBOX ) is for outgoing messages, i.e., messages originated by the File user for Ozeki NG - SMS Gateway to send out (according to outbound routing rules).

    The third directory (SENT) is for messages that have been successfully sent out and accepted by an SMS Center for delivery.

    The fourth directory (FAILED) is for messages that have failed to be sent out. These messages have not been accepted by the SMS Center for delivery.

    The fifth directory (DELIVERED) is for messages that have been delivered to the recipient phone. When Ozeki NG - SMS Gateway receives a delivery report from the SMS Center, a sent message will be inserted into this directory.

    On FTP Connection tab you can find FTP server section. Here, you need to provide the IP address of the FTP server, the port, your username and password (Figure 6).

    ftp server settings
    Figure 6 - FTP server settings

    File formats

    As mentioned above, Ozeki NG - SMS Gateway supports the following file formats: simple, verbose and list. You can use any of these formats to send a message. To select a particular format use the configuration form of the file user.

    The simple file format

    If you select the simple file format in the dropdown menu (see Figure 3 above), each incoming message will be saved in a separate file. The name of the file is the sender phone number, and the only line of the file contains the message. For example:

    c:\smsout\+36203105366

    Hello world

    To send messages using the simple file format, create a separate text file for each outgoing message and place these files into the smsout directory. The name of the text file has to be the recipient phone number. When the message has been sent out, the text file will be automatically deleted from the directory. Note that if you want to send more than one message to the same recipient phone number, you can only place a new message into the outgoing directory if the previous message has been sent out and is no longer there. This is because you cannot have two files with the same name in the same directory. If the previously inserted file is still in the directory (has not yet been sent out), you can only insert the new file by overwriting the previous file. Therefore, if you insert a new file with the same name (which is the telephone number of the recipient) into the outgoing directory, your previous SMS message will not be sent out at all. This is because the file containing it will be replaced with a new one. Replacing the previous file is essentially equal to deleting it.

    Accordingly, if you select the simple file format, an incoming message from a specific sender phone number will overwrite (delete) the previous message from the same number. Therefore, it is always only the latest message from a specific phone number that will be saved in the inbox. This may be inconvenient if you wish to save more than one SMS message from the same sender. Take this into consideration when you select the file format in the respective dropdown menu. On the other hand, this file format may be convenient for position tracking SMS applications. The movement of vehicles can be tracked with a GSM device transmitting the vehicle's position coordinates via SMS to the File user of Ozeki NG - SMS Gateway. In this case, it may not be problematic (or it may even be desirable) that only the latest report is saved in the inbox.

    The verbose file format

    The verbose file format is similar to the simple file format inasmuch as each message resides in a separate file. The difference is that the file contains more information than just the message text. The main advantage of this file format is that you can place into the directory more than one file containing a message to the same destination (phone number). You can give each file any name, which has to be different from the name(s) of any other files(s). Note that the extension of the file has to be .sms . The first line in the file has to contain the sender phone number, the second line contains the recipient phone number, and the message text follows these in the next line. For example:

    c:\smsout\anyname.sms

    +36203105366
    +36209937723
    The message text

    The list file format

    The list file format is a convenient way to send and receive a large number of SMS messages. In this case more than one message is stored in the same file. For outgoing messages you should create a text file in which each line contains a message with the recipient's phone number (in international format) before it. The phone number and the message text is separated by a space character. When the messages are ready to be sent, place the file into the outgoing (smsout) directory. The file name needs to have the .sml extension (sml stands for SMS list). For example:

    c:\smsout\list.sml

    +36205555366 This is the first message
    +36209937723 This is the second message
    +36307789723 Use Ozeki NG - SMS Gateway!
    

    You should place this text file into the c:tmpsmsout directory. For example you can save it as "c:\tmp\smsout\mysms.txt"

    This page demonstrates how to install and configure Ozeki NG SMS Gateway to be able to send and receive SMS messages from an FTP server through diferent protocols. You can use standard FTP protocol , FTPS (FTP over SSL/TLS) or SFTP (SSH FTP). Detailed instructions with screenshots will be provided on how to install and configure the Extended FTP user and you will find further information on the various file formats that can be used, as well.

    The Extended FTP user is an application, that allows you to send and receive messages using text files. It works as follows: if there is an incoming message, the Extended FTP user creates a text file for this message and places it into the incoming directory on the FTP server. To send out messages you need to place a text file into the outgoing directory on the FTP server. The Extended FTP user will periodically check this outgoing directory on the FTP server for messages to be sent. If it finds messages it will send out them as SMS messages. After sending out the messages, the Extended FTP user place them into "Sent", "Delivered" or "Failed" folders according to their delivery status. The Ozeki NG SMS Gateway synchronize messages between the FTP server and the local PC.

    After you install Extended FTP user you need to creat the incoming and the outgoing directory along with other directories for SMS messages related to the user. However, make sure you specify them correctly for the Extended FTP user in the respective edit boxes containing the paths in the General tab of the Configuration panel (see the Configuration section below).

    You can use the graphical user interface of Ozeki NG - SMS Gateway to install and configure an Extended FTP user.

    Installation

    To start installing and configuring an Extended FTP user, click the Add button in the top right-hand corner of the Users and Applications panel on the right of the Management Console. You can also add a user by clicking the Add user item in the Users and applications menu (Figure 1).

    adding a user
    Figure 1 - Adding a user

    This will bring up an interface consisting of two panels. The panel on the left contains a list of users that have been installed. In the bar at the bottom of the panel you can read how many users have been installed. The panel on the right contains a list of users that can be installed. Each user in the left-hand panel is listed with a unique name (and the user type stated in brackets). Each user in the right-hand panel is listed with the name of its type and a brief description of what it can be used for.

    To start installing a Extended FTP user, click the Install link in the respective entry in the list (Figure 2).

    installing an extended ftp user
    Figure 2 - Installing an Extended FTP user

    When installing a user (type), you need to give it a unique username. Clicking the Install link will bring up the File user installation panel. Here, you need to enter a unique username in the Username field (Figure 3).

    provide a unique name
    Figure 3 - Provide a unique name

    General configuration

    The General tab of the Configuration panel will show up after you have specified a unique username for the Extended FTP user.

    The upper section of the tab contains the File format dropdown menu. Select an appropriate file format: List, Simple or Verbose. (For more information, see the File formats section below.)

    Below the File format dropdown menu, there is an edit box. In this, you can specify how often the program should check the outgoing directory for messages to send. Enter the number of seconds in numerical format, representing a positive whole number.If you are content with the default specification (every 30 seconds),leave the edit box unchanged (Figure 4).

    setting the file format and the query frequency
    Figure 4 - Setting the file format and the query frequency

    The lower section of the tab contains five tabs containing paths to directories on the local PC and on the FTP server. Each path includes a different subdirectory name. The status of a message defines which directory it can be found in. Each path leads to a directory containing messages of a specific status.(Figure 5).

    file paths
    Figure 5 - File paths

    The first directory (INBOX) is for incoming messages, i.e., messages delivered to Ozeki NG - SMS Gateway and destined to the File user (according to inbound routing rules).

    The second directory (OUTBOX ) is for outgoing messages, i.e., messages originated by the File user for Ozeki NG - SMS Gateway to send out (according to outbound routing rules).

    The third directory (SENT) is for messages that have been successfully sent out and accepted by an SMS Center for delivery.

    The fourth directory (FAILED) is for messages that have failed to be sent out. These messages have not been accepted by the SMS Center for delivery.

    The fifth directory (DELIVERED) is for messages that have been delivered to the recipient phone. When Ozeki NG - SMS Gateway receives a delivery report from the SMS Center, a sent message will be inserted into this directory.

    On FTP Connection tab you can find FTP server section. Here, you need to provide the authentication mode (FTP, FTPS, STFP), the IP address of the FTP server, the port, your username and password. If the FTP server requires you can add your certificate. (Figure 6).

    ftp server settings
    Figure 6 - FTP server settings

    File formats

    As mentioned above, Ozeki NG - SMS Gateway supports the following file formats: simple, verbose and list. You can use any of these formats to send a message. To select a particular format use the configuration form of the file user.

    The simple file format

    If you select the simple file format in the dropdown menu (see Figure 3 above), each incoming message will be saved in a separate file. The name of the file is the sender phone number, and the only line of the file contains the message. For example:

    c:\SMS\outbox\+36203105366

    Hello world

    To send messages using the simple file format, create a separate text file for each outgoing message and place these files into the smsout directory. The name of the text file has to be the recipient phone number. When the message has been sent out, the text file will be automatically deleted from the directory. Note that if you want to send more than one message to the same recipient phone number, you can only place a new message into the outgoing directory if the previous message has been sent out and is no longer there. This is because you cannot have two files with the same name in the same directory. If the previously inserted file is still in the directory (has not yet been sent out), you can only insert the new file by overwriting the previous file. Therefore, if you insert a new file with the same name (which is the telephone number of the recipient) into the outgoing directory, your previous SMS message will not be sent out at all. This is because the file containing it will be replaced with a new one. Replacing the previous file is essentially equal to deleting it.

    Accordingly, if you select the simple file format, an incoming message from a specific sender phone number will overwrite (delete) the previous message from the same number. Therefore, it is always only the latest message from a specific phone number that will be saved in the inbox. This may be inconvenient if you wish to save more than one SMS message from the same sender. Take this into consideration when you select the file format in the respective dropdown menu. On the other hand, this file format may be convenient for position tracking SMS applications. The movement of vehicles can be tracked with a GSM device transmitting the vehicle's position coordinates via SMS to the File user of Ozeki NG - SMS Gateway. In this case, it may not be problematic (or it may even be desirable) that only the latest report is saved in the inbox.

    The verbose file format

    The verbose file format is similar to the simple file format inasmuch as each message resides in a separate file. The difference is that the file contains more information than just the message text. The main advantage of this file format is that you can place into the directory more than one file containing a message to the same destination (phone number). You can give each file any name, which has to be different from the name(s) of any other files(s). Note that the extension of the file has to be .sms . The first line in the file has to contain the sender phone number, the second line contains the recipient phone number, and the message text follows these in the next line. For example:

    c:\SMS\outbox\anyname.sms

    +36203105366
    +36209937723
    The message text

    The list file format

    The list file format is a convenient way to send and receive a large number of SMS messages. In this case more than one message is stored in the same file. For outgoing messages you should create a text file in which each line contains a message with the recipient's phone number (in international format) before it. The phone number and the message text is separated by a space character. When the messages are ready to be sent, place the file into the outgoing (smsout) directory. The file name needs to have the .sml extension (sml stands for SMS list). For example:

    c:\SMS\outbox\list.sml

    +36205555366 This is the first message
    +36209937723 This is the second message
    +36307789723 Use Ozeki NG - SMS Gateway!
    

    The XML file format

    The XML file format can also be used for sending SMS messages with Ozeki NG SMS Gateway. In this case you need to save the file in XML extension and you should specify the XML file in the following format:

    <messages>
      <message>
          <originator>ORINIGATOR_NUMBER</originator> 
          <recipient>RECIPIENT_NUMBER</recipient> 
          <text>Message text</text> 
          <time>2011.08.25. 7:56:31</time> 
          <messagetype>SMS:TEXT:FORMATTED</messagetype> 
      </message>
    </messages>
    

    You should place this text file into the c:\SMS\outbox\ directory. For example you can save it as "c:\SMS\outbox\mysms.txt"

    The CSV file format

    It is possible to export Excel tables into CSV file format. In this way data of the table will be structured in a table of lists form. In the created CSV file each line corresponds to a row of the original table. Within a line, fields are separated by commas, and each field belongs to one table column.

    Finally you will be able to send data in CSV file format via SMS text messages with the help of a Extended FTP user in Ozeki NG SMS Gateway. This solution allows you to send text messages in a simple file format instead of Excel tables.

    36205555366, Message Text 1, 3/30/2016 12:30
    36209937723, Message Text 2, 3/30/2016 12:30
    36307789723, Message Text 3, 3/30/2016 12:30
    

    How to setup PDF user

    On this page you will learn how you can configure Ozeki NG SMS Gateway to setup a PDF user. After you have downloaded and installed Ozeki NG SMS Gateway you can start to configure a PDF user in it with the help of Graphical User Interface. Please follow the steps below and find screenshots that are demonstrating setup instructions.

    PDF user is an application that allows you to send PDF files in an easy way. You need to do the follows to use this application effectively: you need to select a PDF file on your computer. If the PDF file has been selected, specify the path to it in Ozeki NG SMS Gateway. Then you need to configure an SMTP server in the SMS gateway.

    This solution allows users to send their e-mail address in an SMS message to a phone number provided by you. If the SMS message containing the e-mail address arrives, Ozeki NG SMS Gateway will automatically send the selected PDF file to the user. Therefore, a quick and stable communication process will be performed.

    Configure the PDF user

    First select a PDF file to be sent on your computer. In our example it is "ozeki.pdf" on the desktop (Figure 1).

    pdf file
    Figure 1 - PDF file

    On Figure 2 you can see the path to "ozeki.pdf" file.

    path to pdf file
    Figure 2 - Path to PDF file

    Start Ozeki NG SMS Gateway and click on "Add new user or application" (Figure 3).

    add new user
    Figure 3 - Add new user

    Select "SMS PDF" user in the list and click on "Install" next to it (Figure 4).

    install the user
    Figure 4 - Install the user

    Provide a name for the user to be created. In our example it is "pdf_user" (Figure 5).

    provide a name for the user
    Figure 5 - Provide a name for the user

    After you have added the user, click on "E-mail settings" on the left side of the interface (Figure 6).

    Figure 6 - E-mail settings

    In "General" tab specify the address of the SMTP server and the path to the selected PDF file (it was demonstrated on Figure 2) (Figure 7).

    general tab
    Figure 7 - General tab

    Click on "E-mail settings" tab. As the PDF file will be sent as an e-mail message, you need to compose this e-mail in this tab. Provide the follows: "From address", "Subject", "Message text" (Figure 8):

    email settings tab
    Figure 8 - Email Settings tab

    Test

    Now I will test the system. I generate an incoming SMS that contains an e-mail address (john@ozekisms.org) (Figure 9).

    incoming sms with an email address
    Figure 9 - Incoming SMS with an email address

    If you take a look at Figure 10 you can see the e-mail message containing the PDF file in Outlook Express (Figure 10).

    pdf file in outlook
    Figure 10 - PDF file in Outlook Express

    If you click on the e-mail message you can see its details and the PDF file as an attachment, as well (Figure 11).

    the attached pdf
    Figure 11 - The attached PDF file

    WCF Client User

    This guide provides information on how to install a WCF user in Ozeki NG SMS Gateway. With the help of this WCF user you will be able to forward incoming messages to a WCF service (WCF: Windows Communication Foundation) that will process the messages.

    Requirements:

    You need an installed Ozeki NG SMS Gateway: Download Ozeki NG SMS Gateway

    System architecture

    If you create a WCF user in Ozeki NG SMS Gateway the system will work as follows: This created WCF user will be able to forward all incoming messages to a WCF service. As Figure 1 demonstrates, messages from mobile phones are received and processed by the WCF user of Ozeki NG SMS Gateway. This WCF user then forwards messages to the WCF service using WSHttpBinding binding. Finally the WCF service returns a response with the same type (OZmessage object) and also via WSHttpBinding binding.

    system architecture
    Figure 1 - System architecture

    Configuration steps

    1. Start Ozeki NG SMS Gateway
    2. Create a new SMS WCF user in Ozeki NG SMS Gateway. To do so click on Add new user or application and select SMS WCF user in the list (Figure 2).

      install wcf user
      Figure 2 - Install WCF user

    3. Set the URL of the WCF service by clicking on WCF service settings and on General tab define the Service URL. In our example it is http://localhost:1165/WCFServiceForNG.svc (Figure 3).

      provide service url
      Figure 3 - Provide service URL

    If you specified the proper parameter the connection has been created with the WCF service you wish to use. From that time all the incoming messages of the user will be forwarded to the WCF service.

    Ozeki NG SMS Gateway communicates via WSHttpBinding binding with the WCF service and it uses Windows Authentication.

    Ozeki NG SMS Gateway's requirements for WCF service of third parties:

    The service needs to be described with IWCFServiceForNG interface. This interface has to include the operation contract defined by Ozeki Informatics Ltd:

    [OperationContract]
    OZmessage OnMessageReceived(OZmessage msg );

    The operation contract receives an OZmessage object as a parameter. It contains the message ID, the phone number of sender and recipient, the text of the message, and the message type. Finally it saves the received message. In our example the message has been saved to Driver C into test.txt file.

    public OZmessage OnMessageReceived(OZmessage msg )
                {
                    FileStream file = new FileStream("C:\\test.txt",
                    FileMode.OpenOrCreate | FileMode.Append, FileAccess.Write);
    
                    StreamWriter sw = new StreamWriter(file);
    
                    sw.WriteLine(msg.Recipient + ": " + msg.MessageData);
                    sw.Close();
                    file.Close();
                    return msg;
                }  

    The operation contract can be used for arbitrary functions in this way users can modify the body of the function. Please note that further operation contracts are not supported by Ozeki.

    To operate properly you need to create OZmessage that takes part in the communication process:

    Source code

    [DataContract]
    public class OZmessage
    {
        string messageID;
        string sender;
        string recipient;
        string messageData;
        string messageType;
    
        [DataMember]
        public string MessageID
        {
            get { return messageID; }
            set { messageID = value; }
        }
    
        [DataMember]
        public string Sender
        {
            get { return sender; }
            set { sender = value; }
        }
    
        [DataMember]
        public string Recipient
        {
            get { return recipient; }
            set { recipient = value; }
        }
    
        [DataMember]
        public string MessageData
        {
            get { return messageData; }
            set { messageData = value; }
        }
    
        [DataMember]
        public string MessageType
        {
            get { return messageType; }
            set { messageType = value; }
        }
    
     }

    Please note that any discrepancy from this code will result in errors.

    You can also download an operating example for WCF service: WCFServiceForNG.rar

    Forwarder user

    This guide demonstrates how to create and setup a Forwarder user in Ozeki NG SMS Gateway. This user allows to transfer text messages between two service providers. This feature helps build a cost effective SMS system. Please find below the configuration guide and the routing tables but at first you can learn how the user works.

    System architecture

    On Figure 1 you can examine how Forwarder user works: For example, User A sends an SMS text message from the phone number of +36301122334 to the phone number of User B (+36701234567). In Ozeki NG SMS Gateway, this message will be processed by SMPP1 Service Provider. Then the message is forwarded to the Forwarder user that will sent out the message to User B via SMPP2 Service Provider (Figure 1).

    system architecture
    Figure 1 - System architecture

    Configuration steps

    To create a Forwarder user in Ozeki NG SMS Gateway, click on Add new user or application option after you login. Select Forwarder user in the list and click on Install next to it (Figure 2).

    install forwarder user
    Figure 2 - Install Forwarder user

    On the Configuration pane click on Advanced tab and enable Overridable option (Figure 3). Please note that Overridable option needs to be enabled for the service providers and the Forwarder user, as well. So in this example it is enabled for SMPP1, SMPP2 and Forwarder user.

    enable overridable option
    Figure 3 - Enable Overridable option

    Routing configuration

    To ensure that the message will be forwarded to Forwarder user and then to SMPP2 service provider you need to make some routing configuration in Ozeki NG SMS Gateway.

    In Inbound routing table set SMPP1 as Source, and Forwarder as Destination (Figure 4).

    inbound routing
    Figure 4 - Inbound routing

    In Outbound routing table set Forwarder as Source, and SMPP2 as Destination (Figure 5).

    outbound routing
    Figure 5 - Outbound routing

    RSS user

    Receiving RSS feeds via SMS messages on your cellphone is a great way to keep up on your most important feeds. To achieve this SMS function you need a powerful SMS gateway such as the Ozeki NG SMS Gateway. the Ozeki NG SMS Gateway is a software product that can be installed on your computer. In this guide you will find information on how you can send RSS feeds in an SMS message.

    rss introduction diagram

    Introduction

    If any of your selected RSS feed is updated then the Ozeki NG SMS Gateway will download the RSS feed. It processes the information then sends a message about the update to a given mobile phone. The RSS to SMS service checks an RSS feed periodically and sends the contents as sms messages to a predefined phone number or to a subscription list. It has built in intelligence that makes sure that the downloaded RSS news is not sent out twice. If you decide to use the Ozeki NG SMS Gateway to send SMS notifications each time your selected topic is updated, you will find an effective way of being up-to-date in the given topic. In this article you can read more about this solution. Please follow these steps to set up this helpful solution.

    Configuration in Ozeki NG SMS Gateway

    To receive SMS which includes the contents of RSS feeds you need to make some simple configuration in Ozeki NG SMS Gateway. To apply this solution properly please follow the steps of our configuration guide. First please log into the Ozeki NG SMS Gateway with your username and password (Figure 1).

    logging into ozeki ng sms gateway
    Figure 1 - Logging into Ozeki NG SMS Gateway

    To create a new RSS user you should click on the "Add new user or application" option. Then please select the "RSS user interface" from the list and you should click on the "Install" (Figure 2). This user will read RSS feeds and send their contents as SMS.

    installing rss user
    Figure 2 - Installing RSS user

    You should provide a name for this new user. In this example it is "rssuser" (Figure 3).

    providing a name
    Figure 3 - Providing a name

    To setup the RSS feed, please click on the "RSS to SMS settings" option (Figure 4).

    setting rss to sms
    Figure 4 - Setting RSS to SMS

    After that you should select a page or website you wish to be informed about via RSS feed, then please copy the URL of the website (Figure 5).

    copy the rss feed url
    Figure 5 - Copy the RSS feed URL

    Then you should paste the selected URL into the "RSS url" field of the "General" tab in the Ozeki NG SMS Gateway software (Figure 6).

    paste the url
    Figure 6 - Paste the URL

    Finally, you need to provide the phone number of the recipient (Figure 7).

    providing a recipient
    Figure 7 - Providing a recipient

    After you set the recipient, you can check whether the connection is established. If you go to the "Events" menu in the Ozeki NG SMS Gateway software you can be informed about sent messages (Figure 8).

    events
    Figure 8 - Events

    Before you start the sending please make sure that you have already configured the outgoing routing rule to send RSS feed as SMS. After you set the routing rule you should take a look at the "Outbox" folder of the user this way you can see that which messages should be sent (Figure 9).

    sending messages
    Figure 9 - Sending messages

    Conclusion

    To summarize the above mentioned, it is the best solution to you use the Ozeki NG SMS Gateway to send SMS notifications to mobile phones on updates. With this SMS function you can be sure that all the important information about the selected topics will be sent even if the recipient is on the move and you can also forward them to further recipients if you wish.

    In this way your customers and business partners will be well-informed in real time. With the use of Ozeki NG SMS Gateway you can save valuable time and money while you get a well-functioning and effective SMS system.

    Ozeki NG SMS Gateway for Linux distributions

    Ozeki NG SMS Gateway is compatible with certain Linux distributions. This guide introduces the distributions which are compatible or not compatible with Ozeki NG SMS Gateway.

    Several Linux distributions exist, but not all can operate with Ozeki NG SMS Gateway. If the built-in package manager can install and run Mono Framework 2.6 or can be installed from other source on the Linux distributions, the Ozeki NG SMS Gateway will also be able to run within the system.

    1. Compatible distributions

    • Fedora: if you use this Linux operating system, the operation with the Ozeki NG SMS Gateway v3.15.6 is possible together with Mono Framework 2.6. after installing both programs. For further information: Contact us.
    • Ubuntu:the Linux OS is also able to operate with Ozeki NG SMS Gateway after you installed both Mono Framework 2.6 and Ozeki NG SMS Gateway v3.15.6. For further information: Contact us.

    2. Not compatible distributions

    The following Linux distributions are incapable of installing and running Mono Framework 2.6, therefore the operations with Ozeki NG SMS Gateway v3.15.6 are also impossible on them:

    • CentOS 5
    • Red Hat Enterprise Linux 5
    Note:other Linux distributions are possible to use Ozeki NG SMS Gateway v3.15.6 if Mono Framework 2.6 can be installed and run on them. For further information: Contact us.

    Ozeki NG set up guides for Linux distributions:

    Other releases:

    Ozeki NG SMS Gateway v3.15.6 for Linux

    This guide gives you the steps to install Ozeki NG on Linux. It lists the necessary prerequisites, provides access to the necessary components and explains the way you can get the Ozeki NG mobile messaging software installed as a daemon to operate in the background.

    Video: How To configure your modem

    Step 1 - Download and install Mono Framework

    It is recommended to use Mono Framework 2.6 or above. Most linux distributions have the Mono Framework included. If your Linux distribution does not have mono included, you can download and install it from the following webpage. www.mono-project.org

    For example to install the Mono Framework on Fedora 10, you should issue the following command:

    yum -y install mono-* libgdiplus-* ibm-* byte-*
    yum install wget

    Step 2 - Download and install the Ozeki NG software package

    The Ozeki NG software package can be downloaded from the following URL:

    OzekiNG_SMS_Gateway-3.15.6.tgz (3.4 Mb)

    You can use the following commands to download the package and to extract it's contents:

    cd /var/lib
    wget http://ozekisms.com/attachments/2685/OzekiNG_SMS_Gateway-3.15.6.tgz
    tar -xzvf OzekiNG_SMS_Gateway-3.15.6.tgz
    ln -s OzekiNG_SMS_Gateway-3.15.6 /var/lib/ozeking
    

    Step 3 - Configure your firewall

    Ozeki NG SMS Gateway has a built in webserver. By default this webserver runs on port 9501. You should configure your firewall to accept connections on this port.

    iptables -I INPUT -p tcp --dport 9501 -j ACCEPT

    Step 4 - Test Ozeki NG (Optional)

    Optionally you can run OzekiNG from the command line to see if it functions properly. To do this you should issue the following commands:

    cd OzekiNG_SMS_Gateway-3.15.6
    mono OzekiNG.exe /run
    

    After these command have been issued, you can open the Ozeki NG configuration webpage by typing the following URL in your browser (Replace the IP address 127.0.0.1 to the IP address of your Linux server.

    http://127.0.0.1:9501/
    

    Step 5 - Run in the background

    To run Ozeki NG in the background, you should copy the ozeking init script to your init.d directory. You can use this script to start and to stop the service

    cp /var/lib/ozeking/distributions/Fedora/init.d/ozeking /etc/init.d/
    /etc/init.d/ozeking start
    

    Ozeki NG SMS Gateway for Ubuntu Linux

    On this page you can find detailed information on how to install Ozeki NG SMS Gateway on Ubuntu Linux. Please find the prerequisites and how to access the necessary components. Finally, learn how you can get Ozeki NG SMS Gateway installed as a daemon to operate in the background.

    Video: Ozeki NG SMS Gateway for Ubuntu Linux(part 1/1, configure your system)

    Step 1 - Download and install resolve dependencies (Mono Framework)

    Since Ubuntu does not include Mono Framework, you need to install it. It is recommended to use Mono Framework 2.6 or above. To install the Mono Framework on Ubuntu, issue the following command:

    sudo apt-get install mono-*

    You also need to install winforms that is the complementary library of Mono framework. To install winforms library use the following command:

    sudo apt-get install libmono-winforms2*

    Step 2 - Download and install the Ozeki NG software package

    Ozeki NG SMS Gateway is available on the following URL: OzekiNG_SMS_Gateway-3.15.6.tgz (3.4 Mb)

    Or you can download the package and extract it's contents by providing the following commands in Terminal:

    cd /var/lib
    sudo wget http://ozekisms.com/attachments/2661/OzekiNG_SMS_Gateway-3.15.6.tgz
    sudo tar -xzvf OzekiNG_SMS_Gateway-3.15.6.tgz
    sudo ln -s OzekiNG_SMS_Gateway-3.15.6 /var/lib/ozeking
    

    Step 3 - Configure your firewall

    Ozeki NG SMS Gateway has a built-in webserver. By default this webserver runs on port 9501. You should configure your firewall to accept connections on this port. In other words you need to open a port on the firewall for the SMS gateway.

    sudo iptables -I INPUT -p tcp --dport 9501 -j ACCEPT

    Step 4 - Test Ozeki NG (Optional)

    Optionally you can run Ozeki NG SMS Gateway from the command line to see if it functions properly. To do this you should issue the following commands:

    cd OzekiNG_SMS_Gateway-3.15.6
    sudo mono OzekiNG.exe /run
    

    After these command have been issued, you can open the Ozeki NG configuration webpage by typing the following URL in your browser (Replace the IP address 127.0.0.1 to the IP address of your Ubuntu Linux server.

    http://127.0.0.1:9501/

    Ozeki NG SMS Gateway v3.14.20 for Linux

    This guide gives you the steps to install Ozeki NG on Linux. It lists the necessary prerequisites, provides access to the necessary components and explains the way you can get the Ozeki NG mobile messaging software installed as a daemon to operate in the background.

    linux sms gateway

    Video: How To configure your modem

    Step 1 - Download and install Mono Framework

    It is recommended to use Mono Framework 2.0 or above. Most linux distributions have the Mono Framework included. If your Linux distribution does not have mono included, you can download and install it from the following webpage.

    www.mono-project.org

    For example to install the Mono Framework on Fedora 10, you should issue the following command:

    yum -y install mono-* libgdiplus-* ibm-* byte-*
    yum install wget
    

    Step 2 - Download and install the Ozeki NG software package

    The Ozeki NG software package can be downloaded from the following URL:

    http://ozekisms.com/attachments/2663/OzekiNG_SMS_Gateway-3.14.20.gz (3.4 Mb)

    You can use the following commands to download the package and to extract it's contents:

    cd /var/lib
    wget http://ozekisms.com/attachments/2663/OzekiNG_SMS_Gateway-3.14.20.tgz
    tar -xzvf OzekiNG_SMS_Gateway-3.14.20.tgz
    ln -s OzekiNG_SMS_Gateway-3.14.20 /var/lib/ozeking
    mv /var/lib/ozeking/config.default /var/lib/ozeking/config
    

    Step 3 - Configure your firewall

    Ozeki NG SMS Gateway has a built in webserver. By default this webserver runs on port 9501. You should configure your firewall to accept connections on this port.

    iptables -I INPUT -p tcp --dport 9501 -j ACCEPT

    Step 4 - Test Ozeki NG (Optional)

    Optionally you can run OzekiNG from the command line to see if it functions properly. To do this you should issue the following commands:

    cd OzekiNG_SMS_Gateway-3.14.20
    mono OzekiNG.exe /run

    After these command have been issued, you can open the Ozeki NG configuration webpage by typing the following URL in your browser (Replace the IP address

    http://127.0.0.1:9501/

    Step 5 - Run in the background

    To run Ozeki NG in the background, you should copy the ozeking init script to your init.d directory. You can use this script to start and to stop the service

    cp /var/lib/ozeking/distributions/Fedora/init.d/ozeking /etc/init.d/
    /etc/init.d/ozeking start
    

    Ozeki NG SMS Gateway v3.12.12 for Linux

    This guide gives you the steps to install Ozeki NG on Linux. It lists the necessary prerequisites, provides access to the necessary components and explains the way you can get the Ozeki NG mobile messaging software installed as a daemon to operate in the background.

    linux sms gateway

    Video: How To configure your modem

    Step 1 - Download and install Mono Framework

    It is recommended to use Mono Framework 2.0 or above. Most Linux distributions have the Mono Framework included. If your Linux distribution does not have mono included, you can download and install it from the following webpage.

    www.mono-project.org

    For example to install the Mono Framework on Fedora 10, you should issue the following command:

    yum -y install mono-* libgdiplus-* ibm-* byte-* yum install wget

    Step 2 - Download and install the Ozeki NG software package

    The Ozeki NG software package can be downloaded from the following URL:

    http://ozekisms.com/attachments/2616/