At Jive, we are constantly looking for ways to make it simpler and easier to integrate Jive with your existing tools and workflows. In support of that goal, we're delivering the new Jive connector for Lync with Jive-n 2015.2.This new connector is built as an add-on, and can be installed to any Jive instance on demand via our add-on framework. When installed, your Jive-n users will be able to initiate Lync calls and IM chats from within the Jive community, as long as they have Lync client installed on their machine.



The add-on allows users to initiate any of the following 3 actions:

Lync Call

Lync Chat

Lync Phone Call







To facilitate quick transition from Jive to communicating with the right person or group of people, the add-on adds the appropriate actions in the following places:


Contact a specific person from his profile page...


Lync - Profile - marked.pngLync - hover - marked.png


Or start a group chat with the people that collaborate on a document or are members of a space. By clicking on the "Start Lync" action under the APP ACTIONS section, you will be able to review, add or remove people from the conversation before launching the Lync client:

Lync - document - marked.png

Installation and Configuration

Easy installation and configuration was one of our top priorities. That is one benefit for packaging this new capability as an add-on. Any Jive user with Admin or Community management privileges can install this add-on from the add-ons management screen. In addition, because it is installed as an add-on, it can be added to Cloud, Hosted and On-prem instances at any time. Updates and bug fixes can also be deployed more frequently, since apps are not tied to scheduled Cloud releases.


When it comes to configuration, the add-on has only two pieces of information it requires in order to function properly: A user's email address and a user's phone number. The email is used to initiate Lync calls and Lync Chat sessions. The phone number is required to initiate Lync phone calls. All you need to do is configure the names of the fields that contains the phone number and the email address in your Jive's instance user profiles


Lync - configuration 2.png




Q: What about the existing Jive OCS/Lync connector?

Some of you may be using our older OCS/Lync connector and are wondering why are we releasing yet another Lync connector. The new connector is meant to be a superior replacement to our current OCC/Lync connector. We encourage you to switch to this new add-on before our next release, Jive-n 2015.3, which is when we plan to stop supporting the older connector. Switching is easy - please see the question below for specifics.

The new connector provides several benefits over the older connector:

  1. Can be added to Cloud, hosted and on-prem instances with the same code base, delivering updates on-demand, thanks to it being an add-on delivered from the global registry.
  2. Easier to configure, since there is no need to provide any Lync server information.
  3. The ability to start a multi-participant chat or meeting based on the Jive context.


Q: I am on the older OCS/Lync connector, how do I switch?

Neither the old nor the new connectors store any data. As such, switching is easy. You simply disable the old OCS/Lync connector and install the new add-on. No data migration is needed.


Q: How do I install the new Jive connector for Lync?

Most customers can simply download the new add-on from the global registry and start testing the app. Notice that for production use you will need to contact your sales representative to purchase this new module.

Air-gapped customers will need to contact their PS or sales representative in order to get the appropriate installation files.


Q: What are the supported versions and configurations for the Lync add-on?

  • Jive: Cloud (Essentials, Essentials+, Enterprise), Hosted; On prem ; air-gapped
  • Lync: Lync 2013, Lync 2010, Skype for Business
  • Browser : Chrome, FF, IE9+


Q: Is there support for Mac?

Mac is currently not supported as the Lync client for Mac does not support the URL handling protocols needed.