Skype for Business Video Interop Server – Part 2


In Part-1 I made an introduction about Skype for Business new server role the Video Interop server, this part will be a step by step guide on defining a VIS in the topology, installing the VIS server and configuring it.

Adding VIS to the Topology

Before starting the steps below make sure you have added A-records to your DNS server for the following

  • FQDN of the VIS Pool
  • FQDN of the Video gateway (usually the CUCM or VCS)

Defining VIS Pool

Log in to your admin machine or frontend server where you have Skype for business admin tools installed and start the Skype for Business topology Builder

  • Expand your Skype for Business server 2015 folder
  • Right click on “Video Interop Server Pool” and select “New Video Interop Server Pool…”

  • Define a name for your VIS Pool or if you deploying only one VIS then put the FQDN of it, and select the type of pool
    • “This Pool has multiple servers” >> if you deploying a pool with more than one VIS inside it.
    • “This Pool has one server” >> if you deploying only one server
  • In my case I’m deploying a Pool with multiple VIS server and will call it “vis-pool01.lyncdude.local”

  • If you deploying a pool with multiple VIS server, then you need to add the FQDN of the VIS servers member of this pool, my pool for now will consist of one VIS server called SFB-VIS01.lyncdude.local

  • Associate a primary frontend pool with it ( the frontend pool must be a Skype for Business frontend pool)

  • Associate an Edge Pool with your VIS pool, in my deployment I have no Edge pool but it will be same like last step

  • Click Finish you should now see your VIS pool in the topology

Enabling TCP Ports

By default VIS will be using TLS port for communication, you can enable the TCP port by following those steps:

  • Right click the VIS pool and select “Edit properties”

  • From the left menu click on “Ports”, then check the box “Enable TCP port”

  • Click OK

Adding a Video Gateway to the Topology

This part you will add your Cisco Video gateway weather it is a CUCM or a VCS to the topology under the “Shared Components” folder

  • Right click the “Video Gateways” and select “New Video Gateway…”

  • Enter the FQDN of the video gateway, click next

  • Select the IP-addressing option you want, keep it to IPv4 and click next

  • Change the SIP transport protocol to TCP because according to Microsoft, TLS had some issues that they are working on fixing, also associate a VIS pool with the Video gateway.

  • · Click finish

  • · Now publish the topology

  • · One done successfully click finish.

Installing VIS

Now that you have completed adding a VIS pool to the topology and published it successfully, it is time to install the VIS server I assume you installed all required prerequisites.

  • Login to the VIS server and load the installation media of Skype for Business server.
  • Chose the location you would like to install Skype for Business, or leave it to default and click “Install”

  • Accept the agreement and click “Ok”

  • · Let it check for update and then click “Next”

  • · Once the Skype for Business deployment wizard start click on “Install or Update Skype for Business Systems”

  • · Start with Step -1 “Install Local Configuration Store”

  • · Retrieve from the CMS and click Next

  • · Once done click “Finish”

  • · Start Step-2 “Setup or Remove Skype for Business Server Components”

  • · Once done Click “Finish”

  • · Last but not least we “Request, Install or Assign Certificate”

  • · Click on Request

  • · You should just fall in love with the new “Certificate Request” wizard 🙂 , fill the required information and click Next

  • · Click Next again

  • · Once done, Click Next to start assigning the certificate

  • · Click Finish

  • · Click Next

  • · Now click Next till you assigned the Certificate

  • · Once done click finish and you should see green tick indicating the certificate is assigned

  • · Click “Close”
  • · Finally you can start the services

Using service.msc you can check the status of the services

Configuring VIS

When you installed VIS, a global Video Trunk has been created, you should create a new VIS trunk configuration with name of your Video Trunk

:\> New-CsVideoTrunkConfiguration -Identity “Trunk name”

You get this warning message that you can ignore it or disable it by using the following command line

:\>Set-CsVideoTrunkConfiguration -Identity “Trunk name” -EnableSessionTimer $true

By default, Media encryption is enabled which so far from testing causes unexpected behavior with CUCM, if you face the same you should disable

:\> Set-CsVideoTrunkConfiguration -identity “Trunk name” -EnableMediaEncryptionForSipOverTls $false

Creating Dial Plans

Next we create a Dial plan and associate it with the Video Trunk

:\> New-CsDialPlan -identity “Video Trunk name” -SimpleName “Video_Trunk_dialplan”

You can create a Normalization rule and associate it with the dial plan so that when users dial the number of the cisco conference room it is translated to the E.164 format

In my case I created a rule that whenever a user dial exactly 4 digits number that starting with 3 it add the prefix +491234567 to it.

  • · My pattern to match 4 digits number starting with the number 3 is: ^(1d{3})$
  • · Translation rule is: +491234567$1

Now adding the Normalization rule to the Dial plan this can be done using PowerShell or by using the Skype for business control panel

  • · Open the control panel and go to “Voice Routing” then under “Dial plans” double click the new Dial plan created for the Video Trunk

  • · Scroll down to “Associate Normalization Rules” and click on “New”

  • · Add the Normalization rule you want and click “Ok” when finished
  • · Move the new Normalization rule to be first in order

  • · Click Ok, then click Commit to apply the changes

By this you have configured the VIS, but still you are not finished, you need to configure the other end of the trunk (the Cisco end) to work with VIS, and because I’m not a cisco expert I advise to use this article from Microsoft TechNet

I hope it helped 🙂

Author: Lyncdude

A Senior Service Engineer with more than 9 years of experience in Microsoft Exchange and Microsoft Lync Server / Skype for Business. Egyptian guy lives and works in Frankfurt - Germany. what is written in this blog is my own opinion and thoughts, not my employer and does not reflect their opinion

3 thoughts on “Skype for Business Video Interop Server – Part 2”

  1. Hi Mostafa, Thank you for your great guidance. Last week I have upgraded our infrastructure to S4B and my problem is that I do not see how can I route the video calls to the VIS server. I have modified the topology, deployed the VIS server and created a gateway/trunk between CUCM and VIS.
    Either your post or the Technet guide ( contains dial plan and normalization rule only, but nothing about call routing. I tried to configure it same way as voice calls, but unfortunately the Skype Control Panel – Voice Routing – Route page does not show the Video Gateway, only the PSTN.
    Since the opposite way (from Cisco to Skype) works well, the trunk and the Cisco side configuration seems ok. What did I miss?
    Thanks again,

    1. Hi Olah,
      you did not miss anything, it is a limitation for the time being, you can initiate Video calls only from Cisco to SFB and not the other way around, i hope i understood your question right

      1. This is a huge step backwards… I spent about 2 weeks figuring out why video wouldn’t interop and got VIS working with one way video…. However, since you can’t route calls towards the video trunk you also can’t use Cisco Expressway’s Lync Gateway anymore. Sad I installed this prior to Lync 2013 =/

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: