- Product Manual
- Introduction
- SMS technology
- Installation Guide
- User Guide
- Quick Start Guide
- User Interface
- Configuration
- SMS Client software
- Administrator's guide
- Cluster
- Live cluster setup 1
- Live cluster setup 2
- Failover cluster
- Load Balancing for SMPP v3.3
- Troubleshooting
- Backup
- Manual uninstallation
- Manual upgrade
- Performance
- SMS server availabilty
- High volume SMS messaging
- Recommended computer
- Bandwidth
- 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
Live cluster with two live Ozeki NG SMS Gateway Nodes "Setup 1"
In a live cluster setup both Ozeki NG SMS Gateway nodes are operational. One node serves one set of clients, the other node serves another set of clients. Both nodes have a set of active and a set of passive configurations. The passive configurations are in "Not connected" state. Passive configurations are defined for both: users and clients and service provider connections.
In this setup both system must have live accounts registered at the SMS service providers. These accounts are called "Account A1, Account A2, ..." on Figure 1.
During normal operation both Ozeki NG SMS Gateway nodes are connected to the SMS service providers.
Normal operation
During normal operation, the load of the two nodes are balanced. Each node serve a configured set of clients.
System down operation
When one of the nodes of the cluster goes down because of hardware failure, the configurations on the other node can be activated. This way the other node can take over all the operations: all service provider connections and all client connections.
Failover switching
In this setup failover switching can be performed manually or automatically. If manual switching takes place, the system administrator must login to the live system, and activate the passive configurations by hand.
Automatic switching can be performed by Ozeki's cluster extension. In this case the Ozeki Cluster checks both nodes availability periodically (once every minute). If it detects, that one of the nodes is down, it activates the passive configuartions using HTTP requests.
We recommend manual switching, because short network outages or unintended service transfers can be avoided this way.
More information
- Ozeki Cluster software
- Failover clustering (Windows Server 2012 R2)
- Live cluster setup "1"
- Live cluster setup "2"
- Failover cluster
- Backup
- Automated backup