Jump to: navigation, search

Functional Support

UC Connector supports the same features in integration with all versions of the Microsoft UC platform, be it Lync 2010, Lync 2013 or Skype for Business 2015.

The main supported functions are explained in this page.

  • Presence monitoring: UC Connector uses the Microsoft proprietary MS-PRES protocol (augmented SIP/SIMPLE) to subscribe to user presence from the Lync / Skype for Business Front End Server. This allows the users' presence to be collected by UC Connector and mapped to Genesys presence.
  • Presence push: UC Connector acts as a source of presence for its users, allowing to push useful information to Lync / Skype for Business. This way, UC Connector can push the "in a call" status to Microsoft when a user starts a call routed by Genesys, if so configured.
  • IM through SIP Server-FE Server integration: SIP Server can act as an IM endpoint for Microsoft Lync / Skype for Business, allowing both IM conversations from agents to knowledge workers (whole presence is seen by agents through UC Connector) and incoming IM sessions to a route point for help desk use cases from Lync / Skype for Business to Genesys agents.
  • Interaction preview mechanism: UC Connector pushes a pop-up browser window to users when they are targeted by an interaction preview. The browser window contains configurable information about the incoming interaction, and can be accepted or rejected by the knowledge worker.
  • Launching UC Connector if user is not logged in: UC Connector can send a special IM session to Lync / Skype for Business formatted in a way to open a conversation extension window on the Microsoft client, pointing a browser to the UC Connector main web page. This is useful if a knowledge worker is presented with an interaction preview, but she doesn't have the UC Connector window open in her browser.
  • Secure connections (TLS): UC Connector supports TLS in integration with Microsoft Lync / Skype for Business.
This page was last edited on June 27, 2016, at 22:20.
Comments or questions about this documentation? Contact us for support!