Symptoms

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.

In this scenario, RGS redirects a new incoming call to the queue overflow call action unexpectedly.

Note The expected action is that the new incoming call either waits in the queue or is transferred to an available agent.

Cause

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.

Resolution

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

More Information

For more information about how to create a response group queue, go to the following Microsoft website:

How to create a response group queueFor more information about how to manage response group workflows, go to the following Microsoft website:

How to manage response group workflows

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×