Feature activation and deactivation, as well as subscriber-controlled input 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.
If the media server is available to provide announcements, subscribers will hear an announcement indicating, "Your request cannot be processed at this time. Please try later."
System Specific Information
Activation and deactivation of the following services are blocked:
Anonymous call rejectionNote:
Selective call rejection
Selective call acceptance
Selective call forwarding list editing
Simultaneous ringing, including remote activation and list editing
Lotus Sametime Unified Telephony-based call forwarding features, including remote activation
Lotus Sametime Unified Telephony-based do not disturb
Hunt group features (activate, make busy, stop hunt, toggle)
Personal identification number (PIN) validation
Call completion services (CCBS/CCNR)
If a callback is activated before standalone secondary service begins, but is executed after it begins, the StandAlone Primary node does not know the callback has happened. Consequently, the callback may execute a second time when the cluster is re-established and standalone service ends.
However, features or activities that don't need database writes are still functional—for example:
Call holdParent topic: Cluster Redundancy