Install > Install Service Manager Collaboration > Deploy Service Manager Collaboration with HTTP > Task 15: Integrate with Microsoft Skype for Business

Task 15: Integrate with Microsoft Skype for Business

Service Manager Collaboration provides an out-of-the-box Skype plugin and a Skype agent to integrate with Microsoft Skype for Business. When you start a conversation in Service Manager Collaboration, the Skype plugin that is embedded in the Openfire server monitors all the messages. If a participant does not log on to the Openfire server, the Skype plugin will use the participant’s email address as his/her Skype account and then send the message to the Skype server. If the user is available to chat, the Skype agent will launch a conversation with the right user, and then forward the message to him/her on Skype. After the Skype user replies, the Skype Agent will push this message back to the Skype plugin. Consequently, the Skype plugin will poll the in-coming Skype message and then forward it to all the other users in the Collaboration conversation.

The following diagram illustrates a sample message exchange architecture between Service Manager Collaboration and the Skype server:

Note

Lync users cannot start a conversation with Service Manager Collaboration. Instead, they can be invited to Collaboration conversations only.

In this task, you will integrate Service Manager Collaboration with Microsoft Skype for Business.

Follow these steps:

  1. Download and install Microsoft .NET Framework 4.5 from Microsoft Download Center.

  2. Download and install Microsoft Skype for Business 2016 from Microsoft Download Center. Service Manager Collaboration integrates with Microsoft Skype for Business 2016 only.

  3. Sign in to Skype by using an IT operator's Skype account. This account transfers the communication between the Openfire server and the Skype server, and hence must be effective and timely.
  4. Click Microsoft Skype Options > Personal, and then select None from the Personal information manager drop-down menu. Save your changes and then sign out.
  5. Create the new UISuppressionMode Windows Registry value.

    1. Open Windows Registry Editor, and then navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync.

      Note Create the "15.0\Lync" sub-key if it does not exist.

    2. Right-click Lync, and then click New > DWORD (32-bit) value to create a new registry value.

    3. Set the new value name to UISuppressionMode, and then set the value data to 1.

    4. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync.

    5. Right-click Lync, and then click New > DWORD (32-bit) value to create a new registry value.

    6. Set the new value name to UISuppressionMode, and then set the value data to 1.

    7. Click OK, and then close the Windows Registry Editor.
  6. Encrypt the Skype account and update the openfire.xml file.

    1. Stop the Openfire server.
    2. Navigate to the C:\Program Files (x86)\Micro Focus\Service Manager x.xx\ChatServer\conf directory, and then open openfire.xml with a text editor.
    3. Locate the <lyncIntegration> section.

    4. Update the <lyncIntegration> section as follows:

      <lyncIntegration>
      <enabled>true</enabled>
      <auth>
      <!-- Put plain lync user name and password here, it will be automatically encrypted
      after server startup and encrypted="true" will be added to the userName and password 
      elements. When you change your Lync userName or password, you must remove 
      encrypted="true" and replace the encrypted string with the new plain string. -->
      <userName><YourLyncAccountName></userName>
      <password><YourLyncPassword></password>
      </auth>
      <startLyncAgent>true</startLyncAgent>
      </lyncIntegration>										

      Note You need to enable Skype integration first, and then replace <YourLyncAccountName> and <YourLyncPassword> with the user account with which you signed in to Skype in step 3.

      Caution

      • When the IT operator's Skype password is changed, the <YourLyncPassword> value in openfire.xml must be changed accordingly.
      • You must not sign out the IT operator's Skype account which transfers the communication between the Openfire server and the Skype server. Otherwise, Service Manager Collaboration does not work.

    5. Save and close this file.
    6. Start the Openfire server.

      See the following screenshot for an example of the encrypted <lyncIntegration> section in openfire.xml:

  7. Enable Service Manager Collaboration to communicate with the Skype server.

    1. Log on to Service Manager as a system administrator.
    2. Click System Administration > Ongoing Maintenance > Collaboration > Configuration to open the Collaboration Settings form.
    3. Select the Enable ESS Skype User check box so that the Service Manager Skype users can join Collaboration conversations by using Skype.

Now you can communicate with the Skype users in a Service Manager Collaboration conversation.

Caution To integrate with Microsoft Skype for Business, follow these steps to specify the log on account for the chat server service before starting it as a standard Windows service:

  1. Right-click the Openfire service in the Windows Services window, and then select Properties.
  2. Click the Log On tab.
  3. Select This account, and then specify the same account that you use to log on to the Windows system to do step 5.
  4. Click Apply and OK.