Pages Menu
TwitterRssFacebook

Posted by on Apr 29, 2015 in Learn Skype Web SDK | 5 comments

Learn Skype Web API Day -2 : Server Prerequisites

Learn Skype Web API Day -2 : Server Prerequisites

This is one post in a series of more than 30, devoted to helping you get up to speed quickly with the new Skype Web SDK. Each lesson comes with source code (in GitHub) and a working demo page so you can see what it does. Check out the full list of posts on the Skype Web SDK page.

As at the time of writing, the Skype Web SDK doesn’t impose any additional requirements on the server, over and above those required for UCWA. So, if you’re already accessing your Skype for Business environment using the Unified Communications Web API, you should find that you’ll be able to start using the Skype Web API straightaway (as long as you host your code on the same domain, see below).

For the rest of us, however, you’ll need to do the following steps before you can begin to use Microsoft’s latest API for Skype for Business:

Step 1 – Upgrade your Servers

You need to be running at least Lync Server 2013 CU 1 on all Front End, Edge & Director servers.

Step 2 – Bootstrap

You need to run the Bootstrapper on each of the aforementioned servers. To do this, run: %ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe on each server.

Step 3 – Set-CsWebServiceConfiguration

As a security measure you need to tell your Lync / Skype for Business servers which domains to trust connections from. You do this by running Set-CsWebServiceConfiguration.

First, run Get-CsWebServiceConfiguration to find the identities you have. If you only have one, make a note of it. If you have more than one, pick one and make a note of it.

To add a new domain for UCWA, create the domain using New-CsWebOrigin and then add it to the CrossDomainAuthorizationList:

$x = New-CsWebOrigin -Url “{https://thoughtstuff.co.uk}”
Set-CsWebServiceConfiguration -Identity “{YOUR_IDENTITY}” -CrossDomainAuthorizationList @{Add=$x}

This is the domain where your Skype for Business code will be running. In a pinch, or if you have a test environment, you can specify localhost as the domain and then host your code locally. However, this is a security risk for public-facing systems as it means anyone can access your server (as long as they host on localhost)

You have to add separate entries for http and https, and any specific port numbers (ie thoughtstuff.co.uk is different to thoughtstuff.co.uk:8080)

You need to do this on every FE, Edge and Director server. (the same list as steps 1 and 2)

5 Comments

  1. Hi, can the SDK samples be hooked up to work against Office 365 Lync/Skype? If so, what are the steps involved there? I’m just getting DNS lookup and permission failures at the moment (trying multiple different production and demo accounts).

    Many thanks,
    James.

  2. Hi – currently Skype Web SDK is for on-premise installations only.

  3. Hi, for running the Powershell command are there any pre-requisites? I seem to be getting Command Not Found Exception everytime.

  4. Tom,

    Where to setup this servers?,i am bit confused and how to point to this servers?

  5. Hi,

    How to install Lync Server 2013 CU 1 in my windows 10 OS and also tell me i am little bit confused for to configure all server prerequisites.

    please tell me which credentials are used for login.

Trackbacks/Pingbacks

  1. How to: Skype Web SDK Development without having all the server pre-requisites in place | thoughtstuff | Tom Morgan - […] thing I’ve found – if you look at normal server pre-requisites for using Skype Web SDK you’ll see that…
  2. SkypeDevQ: Using Skype Web SDK with on-premise Skype for Business | The thoughtstuff Blog - […] more information about adding a new domain for access using Skype Web SDK on the Learn Skype Web SDK…

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses cookies to help make this website better. By continuing to use this site we’ll assume you’re OK with that (implied consent).