Using Pexip Infinity as a Skype for Business gateway

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

  • invite H.323/SIP endpoints and registered Infinity Connect clients into a SfB/Lync meeting via manual dialout or drag and drop from the contacts list
  • use the Infinity Gateway to route incoming calls directly into an ad hoc or scheduled SfB/Lync meeting
  • when dialed into a Pexip VMR conference, invite other SfB/Lync or external contacts into that same Pexip VMR (this creates a new SfB/Lync meeting which is merged with the existing Pexip VMR)
  • receive and initiate person-to-person calls with standards-based devices, and then optionally add other participants (to escalate to a multipoint SfB meeting).

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

Using the Infinity Gateway

The Infinity 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 Virtual Meeting Room, Virtual Auditorium, Virtual Reception, scheduled conference, Media Playback Service, 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 Infinity Gateway call to the destination alias according to the rule's call target settings (which protocol, location 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 a Virtual Meeting Room, Virtual Auditorium, Virtual Reception, scheduled conference, Media Playback Service, or Test Call Service.

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

Example routing rules