You are here: Integration > Microsoft Lync / Skype for Business > Example on-prem deployment

Example deployment in an on-prem Lync / Skype for Business environment

This section explains how to integrate Pexip Infinity with an existing, on-prem Lync / Skype for Business* environment. If you want to deploy Pexip Infinity in a public DMZ deployment, see Example public DMZ deployment for remote Lync / Skype for Business environments instead.

Example on-prem deployment used in this guide

The diagram above shows the example deployment which forms the basis of the on-prem integration between Lync/SfB and Pexip Infinity. As Pexip Infinity is a truly distributed platform, it does not matter where messages arrive in the Pexip platform, as it will always ensure that the appropriate Conferencing Nodes get the message or the media for the conference.

This example deployment uses a setup where all components are geographically located in Europe. The local Lync/SfB infrastructure has two Lync/SfB Front End Servers in a Front End pool (, and a Lync/SfB Edge server. It also has three Pexip Conferencing Nodes that are all associated with the same Pexip system location (Europe), and will be set up in an application pool ( and integrated with Lync/SfB.

The example environment contains the following pools:

  • Lync/SfB FEP containing:
  • (Note that the Lync/SfB pool is assumed to be working already; this guide does not cover how to install Lync/SfB in general.)

  • Pexip Conferencing Nodes containing:

The environment also contains a Lync/SfB Edge server, and a standards-based TURN server at Note that the Lync/SfB Edge server cannot be used as a TURN server as it does not support the relevant RFC.

See Pexip Infinity configuration for an on-prem Lync / Skype for Business environment and Lync / Skype for Business server configuration for an on-prem deployment for more information.

Your actual Pexip Infinity environment may differ from the example, in which case you should make relevant adjustments accordingly. This guide covers the specifics of one geographic location. Large enterprises with multiple Lync/SfB locations would simply apply the same configuration model for the other locations towards their local Pexip Conferencing Nodes (see Adding new Front End pools (FEPs), locations and Conferencing Nodes).

* Note that where this documentation refers to "Lync/SfB", it represents both Microsoft Lync and Skype for Business unless explicitly stated otherwise.

Integration objectives

The goal with our integration is to set up a static SIP domain route for the SIP domain from the Front End pool towards a trusted application pool of local Conferencing Nodes. This provides a redundant integration environment between Lync/SfB and Pexip Infinity.

The Pexip Infinity system location that contains the Conferencing Nodes will be configured with a Lync/SfB server. Outgoing calls from Pexip Infinity to Lync/SfB clients will dial out from an appropriate Conferencing Node in that location.

Incoming calls from remote and federated Lync/SfB users will arrive at the Edge server and be routed to the Pexip Infinity Conferencing Nodes via the static SIP route on the Front End pool, similar to native, federated Lync/SfB-to-Lync/SfB calls.

For ensuring media connectivity between the internal Pexip Infinity Conferencing Nodes and external/remote and federated Lync/SfB clients, Conferencing Nodes may relay media via TURN servers located outside the enterprise firewalls in each region. However, in some deployment scenarios where the TURN server is not located outside of the enterprise firewall, you may need to configure a separate STUN server so that each Conferencing Node can discover its public NAT address. In Lync / Skype for Business deployments it is essential that a Conferencing Node can discover its public NAT address.

The following diagram illustrates the typical signaling (SIP) and media (RTP) paths for various call scenarios involving Pexip Infinity and Lync/SfB clients. Since media negotiation between Pexip Infinity and Lync/SfB involves ICE (Interactive Connectivity Establishment), media paths depend on network architecture and the presence of firewalls and NATs (Network Address Translators). Note that the actual media paths in a real deployment may differ.

Example on-prem deployment signaling and media paths