Below is a table of the preferred and required ping times between various components.

Since Clarity Connect uses resources spread around the network infrastructure and deals extensively with real-time communication, the latency between network components is critical to the application performing well.

Note: Outlook 2010 is supported with limited functionality.

Agents that will be using this feature are running Outlook 2013.

Note: Microsoft Exchange 2010 is supported, albeit with limited functionality.

You are running Microsoft Exchange 2013 SP1.

If you plan to take advantage of the Clarity Connect Message Router functionality, please ensure:

The November 2016 cumulative update for Skype for Business is required for Clarity Connect 4.1.

The Skype for Business Server topology must be one that is supported by Microsoft.Ĭoexistence environments (where Lync Server 2010 or 2013 servers are also present in the environment) are supported however, all application servers for Clarity Connect must be in the Skype for Business Server 2015 portion of the topology, and the next hop must be a Skype for Business Server Front End pool.Īgents may be homed on Front End pools running any version of Lync Server or Skype for Business Server.

The Skype for Business Server topology must be one that is supported by Microsoft.Ĭlarity Connect is native to Skype for Business and therefore must be installed in a Skype for Business Server 2015 environment. Please contact Clarity Connect support for additional guidance.Ĭlarity Connect is native to Skype for Business and therefore must be installed in a Skype for Business Server 2019 environment. This content is for informational purposes only.

Latency requirements for skype