Effects on Calls in Progress When Server Status Changes
When the status of a Cisco Unity Connection server changes, the effects on calls in progress depend on the final status of the server that is handling a call and on the condition of the network. Table 3-3 describes the effects.
Table 3-3 Effects on Calls in Progress When Server Status Changes
Status Change
|
Effects
|
|---|---|
Primary to Secondary
|
When the status change is initiated manually, calls in progress are not affected.
When the status change is automatic, effects on calls in progress depend on the critical service that stopped.
|
Secondary to Primary
|
When the status change is initiated manually, calls in progress are not affected.
When the status change is automatic, effects on calls in progress depend on the critical service that stopped.
|
Secondary to Deactivated
|
Calls in progress are dropped.
To prevent dropped calls, on the Cluster Management page in Cisco Unity Connection Serviceability, click Stop Taking Calls for the server, wait until all calls have ended, and deactivate the server.
|
Primary or Secondary
to Replicating Data |
Calls in progress are not affected.
|
Primary or Secondary
to Split Brain Recovery |
Calls in progress are not affected.
|
