The standalone service option is available beginning with V4. If it is enabled, the node that does not get the permission to take over from the Survival Authority stays active. Standalone service is available to duplex server configurations and is intended for geographically separated installations. These geographically separated installations can be layer-3 network separated or geo-separated with layer-2 connectivity (both nodes of the layer-2 configuration are on the the same IP networks but at different locations) . In case of a virtual Telephony Control Server cluster standalone service is only allowed for a layer-3 network separated installation.
It is advisable to consider both the benefits and drawbacks of enabling standalone service.
Feature provisioning is blocked in standalone secondary mode. This is necessary because the database of the standalone secondary node is overwritten with the database of the primary node when the cluster is re-established. All provisioning requests from the CMP/Assistant (SOAP interface) or from the command line interface (CLI) are rejected.
Parent topic: Cluster Redundancy
Standalone Service Subscriber Feature Impacts
Standalone Service Other Network Elements Impacts
Standalone Service TLS Connection Impacts