Ozeki Phone System XE VoIP PBX software
is an advanced PBX built for automated voice calls and 2 way SMS messaging. It
has outstanding APIs for software developers. It can be used for:
Live cluster with two live Ozeki NG SMS Gateway Nodes. "Setup 1"
Recommended reading:
If you wish to protect your service against hardware failure and reach higher
availability of your Ozeki NG SMS Gateway software, we recommend you to try
our Ozeki Cluster software product.
Ozeki Cluster automatically moves any
service to another computer in case of a hardware failure. You can
download it from:
Ozeki Cluster Site
Description
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.
