Response group experience in Lync Server 2013 during pool failure

 

Topic Last Modified: 2012-10-30

This section describes in detail how response group activity is affected in the following stages:

• An outage occurs in the primary pool, but failover is not yet initiated.

• Service is failed over to the backup pool.

• Service is failed back to the primary pool.

User Experience When Outage Occurs

When a pool or site outage occurs, but the administrator has not yet initiated failover, response group activity is handled as described in the following table.

Note

During disaster recovery, calls behave differently depending on whether the primary pool response groups were imported to the backup pool during recovery. In the following table, references to imported response groups mean that primary pool response groups were imported to the backup pool during disaster recovery mode.

Outage Occurs

Type of call or user action	During outage
Calls connected to an agent	Regular calls remain connected. Anonymous calls are disconnected.
In progress calls not yet connected to an agent	Calls are disconnected.
New calls	Calls are disconnected. If response groups were imported, calls connect to backup pool, but agents homed in primary pool are unreachable.
Agent calls on behalf of response group	Feature is disabled during this stage.
Agent sign-in and agent information	Agent groups owned by the primary pool can be viewed on agent console but agents cannot sign in. Agent groups owned by the backup pool can be viewed on agent console and agents can sign in. Imported agent groups are not displayed on agent console.
Response group configuration	Response groups owned by the primary pool can be viewed, depending on the availability of the primary pool’s back-end database, but cannot be modified. Response groups owned by the backup pool can be viewed and modified. Imported response groups cannot be viewed with Lync Server Control Panel or the Response Group Configuration Tool, but can be configured by using Lync Server Management Shell cmdlets.

User Experience During Failover

When an administrator invokes failover to a backup pool, response group activity is handled during and after the failover as described in the following table. The first column describes the type of activity that might be taking place. The middle column describes how each activity is handled during the brief time that it takes to fail over to the backup pool. The last column describes how the activity is handled for the duration, after the failover process is complete and the backup pool is standing in for the primary pool.

Note

During disaster recovery, calls behave differently depending on whether the primary pool response groups were imported to the backup pool during recovery. In the following table, references to imported response groups mean that primary pool response groups were imported to the backup pool during disaster recovery mode.

Failover Is Initiated

Type of call or user action	During Failover	After Failover Completes
Calls connected to an agent	Regular calls remain connected. Anonymous calls are disconnected.	Regular calls remain connected. For imported response groups, anonymous calls that have reached the backup pool remain connected.
In progress calls not yet connected to an agent	Calls are disconnected.	If response groups were not imported, no calls are in this status. For imported response groups, calls that have reached the backup pool remain connected.
New calls	Calls are disconnected. For imported response groups, calls connect to the backup pool, but agents homed in the primary pool are unreachable.	If response groups were not imported, calls are disconnected. For imported response groups, calls connect to the backup pool.
Agent calls on behalf of response group	Feature is disabled during this stage	If response groups were not imported, calls fail. For imported response groups, calls succeed.
Agent sign-in and agent information	Agent groups owned by the primary pool can be viewed on agent console but agents cannot sign in. Agent groups owned by the backup pool can be viewed on agent console and agents can sign in. Imported agent groups are displayed on agent console and agents can sign in.	Agent groups owned by the primary pool can be viewed on agent console but agents cannot sign in. Agent groups owned by the backup pool can be viewed on agent console and agents can sign in. Imported agent groups are displayed on agent console and agents can sign in.
Response group configuration	Response groups owned by the primary pool can be viewed, depending on the availability of the primary pool’s back-end database, but cannot be modified. Response groups owned by the backup pool can be viewed and modified. Imported response groups cannot be viewed with Lync Server Control Panel or the Response Group Configuration Tool, but can be configured by using Lync Server Management Shell cmdlets.	Response groups owned by the primary pool can be viewed, depending on the availability of the back end database, but cannot be modified. Response groups owned by the backup pool can be viewed and modified. Imported response groups cannot be viewed with Lync Server Control Panel or the Response Group Configuration Tool, but can be configured by using Lync Server Management Shell cmdlets.

User Experience During Failback

When an administrator invokes failback to the primary pool, response group activity is handled during and after the failback as described in the following table.

Note

During disaster recovery, calls behave differently depending on whether the primary pool response groups were imported to the backup pool during recovery. In the following table, references to imported response groups mean that primary pool response groups were imported to the backup pool during disaster recovery mode.

Call Handling in Failback

Type of call or user action	During Failback	After Failback Completes
Calls connected to an agent	Regular calls remain connected. If response groups were not imported, no anonymous calls are in this status. For imported response groups, anonymous calls remain connected.	Regular calls remain connected. If response groups were not imported, no anonymous calls are in this status. For imported response groups, anonymous calls remain connected.
In progress calls not yet connected to an agent	If response groups were not imported, no calls are in this status. For imported response groups, calls will be disconnected.	If response groups were not imported, no calls are in this status. For imported response groups, calls will be disconnected.
New calls	Calls connect to the primary pool, but agents homed in the primary pool are unreachable.	Calls connect to the primary pool.
Agent calls on behalf of response group	Feature is disabled during this stage.	Calls succeed.
Agent sign-in and agent information	Agent groups owned by the primary pool can be viewed on agent console but agents cannot sign in. Agent groups owned by the backup pool can be viewed on agent console and agents can sign in. Imported agent groups are displayed on agent console and agents can sign in.	Agent groups owned by the primary pool can be viewed on agent console and agents can sign in. Agent groups owned by the backup pool can be viewed on agent console and agents can sign in. Imported agent groups are not displayed on agent console.
Response group configuration	Response groups owned by the primary pool can be viewed, depending on the availability of the primary pool’s back-end database, but cannot be modified. Response groups owned by the backup pool can be viewed and modified. Imported response groups cannot be viewed with Lync Server Control Panel or the Response Group Configuration Tool, but can be configured by using Lync Server Management Shell cmdlets.	Response groups owned by the primary pool can be viewed and modified. Response groups owned by the backup pool can be viewed and modified. Imported response groups cannot be viewed with Lync Server Control Panel or the Response Group Configuration Tool, but can be configured by using Lync Server Management Shell cmdlets.