Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Lync Server 2013 RGS incorrectly redirects a call to the queue overflow call action


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You deploy the Response Group Service (RGS) in a Microsoft Lync Server 2013 environment.
  • You configure an RGS queue, enable queue overflow, and configure the queue overflow call action.
  • Users call the RGS.
  • The RGS transfers the incoming calls to agents.
  • The queue overflow threshold is not met.
In this scenario, the RGS may incorrectly redirect a new incoming call to the queue overflow call action instead of putting the call into the queue or transferring the call to an available agent.

↑ Back to the top


Cause

The issue occurs because of a race condition in RGS. When the race condition occurs, a call that is successfully handled by the RGS is not deleted from the database. When multiple calls are not deleted, the queue overflow threshold can be exceeded. Therefore, the queue overflow call action is triggered.

↑ Back to the top


Resolution

To resolve this issue, install the cumulative update that is described in the following article in the Microsoft Knowledge Base:
2835438 Description of the cumulative update 5.0.8308.420 for Lync Server 2013, UCMA 3.0 Workflow APIs: July 2013

↑ Back to the top


References

For information about how to create or modify a queue in Lync Server 2013, visit the following TechNet website: For information about how to manage Response Group workflows in Lync Server 2013, visit the following TechNet website:

↑ Back to the top


Keywords: kbqfe, kbfix, kbentirenet, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2846489
Revision : 1
Created on : 1/7/2017
Published on : 7/1/2013
Exists online : False
Views : 227