- Product Manual
- Introduction
- SMS technology
- Installation Guide
- User Guide
- Developers Guide
- Examples and Solutions
- Appendix
- SMS FAQ
- 1.1 SMS basics
- 1.2 Why is SMS so successful?
- 1.3 Example applications of SMS messaging
- 1.4 SMS number formats
- 1.5 Mobile message types
- 1.6 SMSC
- 1.7 SMS Gateway
- 1.8 Two way SMS systems
- 2.1 Prerequisites
- 2.2 Network requirements
- 2.3 General Information
- 2.4 Message routing
- 2.5 Message types
- 2.6 Delivery reports
- 3.1 GSM modem
- 3.2 SMPP
- 3.3 CIMD2
- 3.4 UCP/EMI
- 3.5 HTTP
- 3.6 SMTP
- 4.1 API
- 4.2 SQL to SMS
- 4.3 HTTP to SMS
- 4.4 E-mail to SMS
- 4.5 Autoreply database
- 5.1 Performance
- 5.2 Logging
- 5.3 Errors
- 5.4 Reporting
- 6.1 Trial version
- 6.2 Licensing
- Feature list
- Commercial Information
- Search
SMS FAQ
Performance and scalability
![]() |
How can I configure the system for best performance? |
The most important in tuning the system for performance
is to disable functionality that requires disk operations. The two most obvious
things to do are to disable persistent message queues and to disable detailed
logging. Also it is a good option to limit the number of outgoing and incoming
routes to the minimum and to disable other unnecesary functionality, such as
accounting, unused user and application configurations etc. | |
![]() |
How can I handle unreliable service provider connections? |
The software has a built in loadbalancing
functionality that is useful for two reasons. It can be used to handle
unreliable service provider
connections and to increase the message capacity. To handle unreliable service
provider connections we recommend to setup two simultaneous connections to the
same service provider and configure the software to do loadbalancing between
them. | |
More information is available at:
SMS load balancing page
| |
![]() |
How can I increase the capacity of an IP-SMS service provider connection? |
We
recommend to open two connections to the same service provider and configure
the SMS gateway to perform loadbalancing between them. | |
More information is available at:
SMS load balancing page
| |
![]() |
How can I increase the reliability of this SMS gateway? |
First, we should mention that this SMS gateway was
designed to work 24/7. It is very reliable. However, it might be possible that
there is a power outage, the hardware fails, or the network goes down or some
other external problem occurs (for example, the hard disk becomes full, the
memory becomes exhausted, etc.). To overcome these issues we suggest to run
two instances of the software on two different PCs in two different locations.
This way you can make the system more tolerant for failures. | |
![]() |
How do you set daily and monthly message throughput limits for SMPP Clients and other users (SQL user, E-mail users, etc)? |
You can use the credit limit handling feature for
this, but you must decide which period you would like to use. You can have
daily or monthly limits, but you cannot have both at the same time.
| |
![]() |
If you have 1000 SMPP Clients or other users (SQL users, E-mail users) connected, how do you control the various message queues? For instance, how many messages to send from each queue in turn? |
The algorithm is round robin.
This means that in every round one message is taken
from each user's outbox. This way the users share the
sending capacity evenly. | |
![]() |
What is the scalability schema of the software? |
The software's core performance
depends on the underlying hardware. The scalability method we recommend depends
on the way the software is used. If a relatively small amount of users generate
a high volume of traffic, the hardware should be replaced to a more powerful one.
If the number of users is great and the amount of traffic generated by the users
is small, we recommend adding more PCs to the system. | |
![]() |
Does the SMS gateway support clustering over multiple servers and how does it occur? |
Clustering is required
if a large number of users need to connect to the service. An Ozeki
SMS Gateway cluster is a set of independent computers. Each computer
has Ozeki NG installed on it. Each Ozeki NG connects to the appropriate SMS
service providers independently and serves users independently of other members
of the cluster. Customer connections are distributed among the members of the
cluster in two ways: DNS based server selection or preselecting router.
| |
![]() |
I cannot send more then 6 messages per second, although I have a 10 MPS license. What can be the problem? |
Possible reasons:
To give you some details. First check the size of your outbox. If you have an
outbox
filled with 100-2000 messages it means that you are able to provide messages
for sending at a sufficient rate. If the outbox size is between 0-100 it means
that the Ozeki SMS Gateway system is often waiting for messages to be
transmitted. If you have a significantly larger outbox queue size, it means the
message source overloads your system.
|
Most popular
If you are insterested in how to setup automated SMS notifications, you should apply one of the following configurations:
SMS through HTTP requests
SMS from E-mail
SMS from the command line
SMS using txt files
If you are a software developer you can proceed to adding SMS functionality to your source code by clicking on one of the following links:
PHP SMS example
C# SMS example
ASP SMS example
SQL SMS example
Delphi SMS example
If you would like to send and receive SMS messages from MS Office applications, please check out the following links:
Send SMS from MS Excel
Send SMS from MS Outlook
Check out Ozeki SMS Client