You are here: Integration > Microsoft Lync / Skype for Business > Configuring Infinity as a Lync/Skype gateway

Configuring Pexip Infinity as a Lync / Skype for Business gateway

Pexip Infinity can act as a gateway between Lync / Skype for Business* and standards-based endpoints. This enables Lync/SfB clients to:

  • invite H.323/SIP endpoints and registered Infinity Connect clients into a Lync/SfB meeting
  • use the Pexip Distributed Gateway service to route incoming calls directly into an ad hoc or scheduled Lync/SfB meeting
  • when dialed into a Pexip VMR conference, invite other Lync/SfB or external contacts into that same Pexip VMR (this creates a new Lync/SfB meeting which is merged with the existing Pexip VMR)
  • receive and initiate person-to-person calls with standards-based devices.

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

Using the Pexip Distributed Gateway service

The Pexip Distributed Gateway is configured as a series of Call Routing Rules that specify which calls should be interworked and to where.

Incoming calls received by Pexip Infinity are routed as follows:

  1. Pexip Infinity receives an incoming call via one of its Conferencing Nodes.
  2. It checks whether the destination alias belongs to a Pexip Infinity Virtual Meeting Room, Virtual Auditorium, Virtual Reception or Test Call Service; if so, it directs the call to that service.
  3. If the alias does not belong to any of the above services, Pexip Infinity checks the Call Routing Rules to see if the alias matches any rules specified there for incoming calls. If so, it places an outgoing call to the destination alias according to the rule's call target settings (which protocol and call control system to use, whether to route to registered devices only, etc).

This means that if an alias matches both a Virtual Meeting Room and a Call Routing Rule, the former will always take precedence and the call will be routed to the Virtual Meeting Room. You must therefore ensure that any regular expressions used in a Call Routing Rule do not unintentionally overlap with any aliases used by Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions or Test Call Services.

If you configure your Pexip Distributed Gateway to support all of the Lync/SfB scenarios described here, you will have Call Routing Rules similar to those shown below:

Example routing rules