Skip to main content

Skype for Business SDN API 2.4.1 installation and configuration Part 2

Skype for Business SDN API 2.4.1 installation and configuration Part 2

This article will cover SDN and dialog listener 2.4.1 Standalone and Pool installation.
Initially, to receive messages from the SDN Manager you must provision at least one subscriber. However, you can no longer provision this subscriber in the setup. Rather, you must use the command line interface of the SDN Manager. At a minimum you need to call:

sdnmanager.exe p s some-subscriber-name submituri=http://

There are three different type of installation.

A.    Join (or create) a pool of SDN Managers using a REDIS cache. [Not covering this document]
B.    Join (or create) a pool of SDN managers using a SQL database. [Covered in this document]
C.    Set up an individual SDN Manager that does not share setting. [Covered in this document] 

1.     Set up an individual SDN Manager that does not share setting  (Known as Standalone SDN installation):
This type of installation does not need SQL database on SDN manager. This is easier for troubleshooting without SQL. I would recommend to use this option when you are installing SDN first time to eliminate SQL troubleshooting.
Also make sure to use separate VM or hardware server for SDN manager. Standard VM configuration (2-4 core CPU, 8 GB RAM and 80 GB HDD).
Follow the below steps to install SDN standalone manager.

1.     Download SDN 2.4.1 (SkypeForBusinessSDNManager.msi) and run as administrator with elevated permission. SDN1


Click Next.

2.     Check on accept license agreement and click on Next.

3.     Choose Next to install on default folder or click on Change.. if you want to  change default installation directory.

And change the log directory. Check mark “Check to activate DEBUG level of logging.” If you want to see full debug logs. And click on Next.
Note: While the number of log files is limited, for production environments it is not recommended that you activate debug logging unless investigating a particular issue, as extensive amounts of logs are written. SDN2

4.     Select “Set up an individual SDN Manager that does not share settings”. And click on Next.

5.     Click on Finish.

6.     Now time to configure SDN subscriber using command line. Configuration is same for Standalone and Pool SDN configuration. Refer configuration section.

2.     Join (or create) a pool of SDN managers using a SQL database. Using this Installation option for my installation.

Using this option you will get high availability using two or more SDN manager with individual SQL database. (You may use single SQL database).
Install SDN manager as pool with high availability mode.
1.     First install .NET 3.5 (with Service Pack 1) and 4.5 or later to separate VM server were SDN Manager going to install.

2.     Install SQL Database. –
In a pool configuration, Skype for Business SDN Interface requires a data store to share call states of concurrently ongoing calls or configuration settings among multiple SDN Managers, which can be a SQL Server or other data store.
 You can use any SQL Server edition, including the SQL Server Express edition. For my installation I am using Microsoft SQL 2014 Express edition.  


3.     Now install SQL Express on SDN Manager server (separate than Lync FE Server).

Run SQLEXPRADV_x64_ENU.exe as Administrator


Click OK to extract files.

Select “New SQL Server stand-alone installation or add features to an existing installation.”

Accept license and click on Next.

On feature selection page: Select “LocalDB”. As showed in above image.

Click on Next.

Type Instance name: as any friendly name. I have written as “sfbsdnmanager”


Click on Next:

Click on Next:

You can add any additional user as SQL server administrator and then Click on Next:

Select “Install and configure” and then Click on Next:

Here you can see the LocalDB. Now you can open SQL Studio to and see of your instance connecting or not. My SQL instance is connection correctly. 

4.     Now install SkypeForBusinessSDNManager.msi on this server where SQL Express installed and configured LocalDB.

Download and double click on  SkypeForBusinessSDNManager.msi


a.     Run SkypeForBusinessSDNManager.msi as elevated (administrator) permission to the server computer that will host the SDN Manager. Sdn1

b.    Click on Next.

c.     Accept the license and click on Next:

Note: If you check 'Check to activate DEBUG level of logging' then you may see extensive amount of logs can be written, it is recommended that this option not be activated in a production environment unless investigating a particular issue.

d.    Then change logs file path to your friendly path and install path if required. Then click on Next:

e.     Select “Join (or create) a pool of SDN Managers using a SQL database”. Then click on Next:

f.      In Skype for Business SDN Manager Database Setting’s wizard page, enter a SQL Server name in the Database Server field, and the database instance name, if appropriate, in the Database Name field. See the above image.

Example: Database Server: localhost\sfbsdnmanager and keep Database name as default.

Select either the Integrated Security or SQL Authentication to specify the credentials that the SDN Manager uses to access the database. Make sure to use the credentials with the sufficient privileges to access, create and configure the database. I am using “Integrated Security (SQL Server default)”.

Then click on Next:

g.     You can change Database data and log files directory if require. I am keeping as by default. Then click on Next:

h.    Now ready to install and click on Install.

Finally click on Finish.

You can verify your SDN manager installation using opening the SQL studio and see if you are seeing database SDNManager22. 

Now time to install Skype for Business dialog listener on each Skype for Business Front End server: (You can Lync2013 then install Dialog listener on Lync Server 2013 front end server)

1.     Download and double click on  SkypeForBusinessDialogListener.msi

Note: Remove in case you have previous LyncDialoglister installed on Skype for Business (Lync) Front end server.
Copy the SkypeForBusinessDialogListener.msi file to each Front-End server and double click on it.

Then click on Next:
Accept the License and click on Next:

Keep installation path as default (If in case you want to change path then click on “Change..” and select appropriate path) and then change log file path. Finally click on Next.

Note: While the number of log files is limited, for production environments it is not recommended that you activate debug logging unless investigating a particular issue, as extensive amounts of logs are written.

The configuration service is part of SDN Manager. You may dedicate a particular SDN Manager to serve as the configuration service, or refer to an entire pool of SDN Manager Instances by using their pool fully qualified domain name. The data store used by this SDN Manager or pool defines the settings used by this SDN Interface system, including the settings used for all Dialog Listener instances, the SDN Manager itself, and settings for all subscribers. I am using two separate SDN manager.

If you have a DNS SRV record configured, selecting the checkbox (Use the DNS SRV Record to get the URIs) will use the DNS records instead of the URL to locate the configuration service.

Click on Next: (I am using SDN manager IP address with 9333 port.) 

You may optionally select a client certificate for authentication when using an https connection. For my configuration I am not using http connection.
Then click on Next.

In Dialog Listener Service Account wizard screen, select the Network Service or Specify an Account option and the select Next:
This screen is used to specify a user account to run the Dialog Listener Windows Service or, alternatively, use the network service. The network service or the specified user account must be in the RTC Server Applications or RTC Local Administrators local group. Dialog Listener service may fails to start if it not part of RTC Server Application group.
You can simply add your service account (which you are using for starting the Dialog listener service) to RTC Server Application group in each Skype for Business front end server. See the below screen.
Open Computer Management > expand “Local Users and Groups” > Groups > double Click on “RTC Server Applications”. Refer the below image.  sdn_RTC_grp

Then select Next.

Click on Next:

On the 'Ready to Install' screen, click the Install button to start the installation.

Click on OK.
Thank you


Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: ·User name: orgname\bilag ·Password: ************
Note: is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…