Response Group Service redirects incoming call to the queue overflow call action in a Lync Server 2010 environment
Consider the following scenario:
- You deploy the Response Group Service (RGS) in a Microsoft Lync Server 2010 environment.
- You create a response group queue that has queue overflow enabled. Additionally, you configure the call action settings for when the queue overflow threshold is met.
- Some users call into the RGS.
- The RGS successfully transfers the incoming calls to some agents.
- The queue overflow threshold is not met.
Note The expected action is that the new incoming call either waits in the queue or is transferred to an available agent.
This issue occurs because of a race condition in the RGS. The race condition prevents a successfully-handled call by the RGS from being deleted from the database. When multiple calls are not deleted, the queue overflow threshold is exceeded. Therefore, the queue overflow call action is triggered.
To resolve this issue, install the following cumulative update:
2847888 Description of the cumulative update for Lync Server 2010, Unified Communications Managed API 3.0 Runtime: July 2013
For more information about how to create a response group queue, go to the following Microsoft website:
Article ID: 2861308 - Last Review: 07/12/2013 22:22:00 - Revision: 1.0
Microsoft Lync Server 2010 Enterprise Edition, Microsoft Lync Server 2010 Standard Edition, Microsoft Unified Communications Managed API v3.0 Core Runtime
- kbqfe kbfix kbsurveynew kbexpertisebeginner KB2861308