Skype for Business

Content

About

Tested Version

Integration Description

Configuration with Mediation Server

Configuration with Video Interop Server

Used Symbols

About

Skype for Business (SfB) is a platform formerly known as Microsoft Lync Server. It is a unified communication (UC) solution that integrates common channels of business communication including instant messaging (IM), VoIP (voice over IP), file transferWeb conferencing, voice mail and email.

 

Tested Versions

Version Mediation Server Video Interop Server
6.0.9319.0 (green star) (tick)
6.0.9319.259 (green star) (green star)* (with disabled video codecs)
6.0.9319.277** (green star) (green star)* (with disabled video codecs)

*) With this latest version there are problems present when setting up the H.264 video stream. When video codecs are disabled on the intercom, audio calls are working without any issues. This may change with future updates.

**) Video Interop Server was not updated with this release, therefore there is no change to its functionality.

Integration Description

There are two ways to interconnect Skype for Business and 2N Helios IP intercoms. First way is to use a Skype for Business Mediation Server. Unfortunately only an audio stream from a SIP device can be sent through the SfB Mediation Server. To be able to show video from 2N Helios IP intercoms on client's PC we are using our software 2N® Helios IP Eye. Door opening can be done via a button in 2N® Helios IP Eye pop-up window or by sending a DTMF code from SfB client keypad (default settings of 2N Helios IP is 00* - Hardware / Switches / Switch X / Switch Codes / ... ).

(Configuration of 2N® Helios IP Eye is not described on this web page, nevertheless, all these information you can find in this FAQ: 2N® Helios IP Eye - How to set)

The second way is to use a Skype for Business Video Interop Server. Using this component it is possible to make video calls using the Skype for Business client, but only when the call is made from the intercom directing to the client. It is not possible to make a call from the client to the intercom.

Example of configuration with Mediation Server

  2N Helios IP

2N Helios IP uses SIP direct call via TCP protocol for communication with Skype for Business. We strongly recommend using a static IP address for 2N Helios IP.

SIP Settings

In this section, a phone number, SIP transport protocol and local SIP port must be set.

Directory settings

SIP direct format with a prefix+line number, SfB domain and communication port will be used (see the configuration of SfB below). To show a pop-up window of 2N® Helios IP Eye the IP address of the PC must be set in the field "Helios IP Eye Address".

  Skype for Business

First of all, we need to create a user in Skype for Business Server which will receive calls from 2N Helios IP. Line number with a prefix is defined in "Line URI" field. The prefix (country code in our case) is not necessary, however, if you won't use it, do not forget to modify the configuration in 2N Helios IP directory and the configuration of Voice Routing in SfB described below.

Just be sure a mediation pool is defined in the SfB Server.

Create a new PSTN Gateway. The IP address set in FQDN field must be IP address of 2N Helios IP.

Create a new Trunk with IP address and listening port of 2N Helios IP.

To accept the new topology of the SfB Server click right mouse button on your server and then choose: "Topology / Publish".

Update the system with "Run again" button.

Route, PSTN and trunk must be set in "Voice Routing" menu.

In Management Shell of SfB a new analog device must be added. You can use exactly the same command only the IP address of the Gateway have to correspond with IP address of your 2N Helios IP intercom.

To verify that the new device has been successfully added to the system you can use following command.

Required licenses

  • Enhanced Security for SRTP and SIP over TLS

Example of configuration with Video Interop Server

  2N Helios IP

2N Helios IP SIP configuration is similar to the previous option. Make sure you have TCP enabled for at least one SIP account.

There is one difference in the Directory configuration. Instead of the Mediation server address, you need to provide the address of your deployed Video Interop Server. In this example there is "sip:+4201027@vis.experimental.local:6001/2" as a phone number in the Directory, because Video Interop Server is located at a machine named vis.experimental.local and is listening on port 6001. Number 2 after the slash denotes SIP account number 2, which is configured to use TCP as a transport protocol.

  Skype for Business

For this configuration to work, you need a deployed Video Interop Server in your Skype for Business installation. Make sure it is listening on a TCP port.

Next step is to add your intercom as a Video Gateway.

Enter IP address or domain name of your intercom.

Select TCP as a transport protocol and enter the correct port number which you have set up in the intercom configuration.

In SfB Management Shell add a new Video Trunk Configuration. Use the SIP trunk name you have created in the previous step as a value of the Identity parameter as in the example below. Make sure to disable media encryption using the EnableMediaEncryptionForSipOverTls parameter.

Last step is to add a new dial plan for the Video Gateway.

Now you should be able to make video calls from your intercom to the Skype for Business client.

Required licenses

  • Enhanced Security for SRTP and SIP over TLS

Used Symbols

(tick) - Verified with video

(green star) - Verified with audio only

(warning) - Work with limitation

(error) - Incompatible