- Product Manual
- Introduction
- SMS technology
- Installation Guide
- User Guide
- Quick Start Guide
- User Interface
- Configuration
- SMS Client software
- Administrator's guide
- Cluster
- Load Balancing for SMPP v3.3
- Troubleshooting
- Backup
- Manual uninstallation
- Manual upgrade
- Performance
- SMS server availabilty
- High volume SMS messaging
- Recommended computer
- Bandwidth
- Bandwidth calculation example
- Manual installation
- Failover cluster on Win2003
- Failover cluster on Win2012
- SNMP
- Migration/Hardware Replacement
- Message priorities
- Message queues
- SMPP via VPN
- Developers Guide
- Examples and Solutions
- Appendix
- SMS FAQ
- Feature list
- Commercial Information
- Search
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
Bandwidth calculation example
On this page you can find a bandwidth calculation example that allows you to see how the bandwidth capacity of Ozeki NG SMS Gateway works.
In case of SMPP connection that has a bandwidth capacity of 5 MPS
(Message Per Second), 5 MPS refers to the fact that outgoing and incoming
message capacity together will be 5 messages/sec.
SMPP connection with 5 MPS: |
Please note that in all the examples below it is assumed that there is no incoming messages and no delivery reports
If you go to "SQL for sending" tab of the Database user you can find this
option: "Check the ozekimessageout table every ... sec. for outgoing messages"
(Figure 1). By default this value is set to "10". In practice it means that
the Database user will check the "ozekimessageout" table for outgoing messages
in every 10 seconds.
Below on "SQL for sending" tab you can also find "Maximum number of messages
to send with one poll:" option. By default it is set to "10". It refers to the
maximum number of messages to be sent out with one poll. In practice it means
that 10 messages will be sent with one "Select" statement.
So with the default settings in Ozeki NG SMS Gateway 10 messages are sent in
every 10 seconds that will take 2 seconds with the 5 MPS connection.
10 messages / 5 MPS = 2 seconds |
If you set the time of checking the ozekimessageout table for outgoing messages to a lower value - for example to "5" - and you leave the default number of messages to be sent out (10 messages) it will also take 2 seconds with 5 MPS connection (Figure 2). In this case the process requires the same period of time but the user will check the "ozekimessageout" table for outgoing messages more often (in every "5" seconds instead of "10").
Assume that we want to send out 1000 messages (with 5 MPS SMPP connection).
If you use the settings of "Example 1": the user checks for outgoing messages
in every "5" minutes and maximum "10" messages can be sent out with one poll
then 100 polls are required to send out the messages. As the user checks the
"ozekimessageout" table in every "5" seconds it needs 500 seconds (8,3 minutes)
to poll and send out 1000 messages. So there is enough time to send out messages
between two polls.
500 seconds / 60 = 8,3 minutes |
More information
- Inbound SMS Routing with multiple keywords
- SMS Service Provider Connectivity
- Users and SMS Applications
- Load Balancing
- SMS alphabet