Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles / All-Topics

An introduction to Sending an IM with UCWA

0.00/5 (No votes)
1 Feb 2015CPOL1 min read 7K  
li { margin-bottom: -0.2em; } This is part 3 of a 4 part series.
<style type="text/css"> li { margin-bottom: -0.2em; } </style>

 

Microsoft's Unified Communications Web API (UCWA) is a RESTful API that exposes Lync Server's Instant Messaging and Presence capabilities. This tutorial focuses on creating an Application and sending an Instant Message (IM), one of many activities enabled by UCWA, but by far the most commonly used.

This tutorial assumes you are familiar with HTTP APIs, RESTful concepts, OAuth and JSON.

The content in these articles are based on my own observations, references and examples from Microsoft's Lync Web Developer site, http://ucwa.lync.com, and demonstrates the techniques that form the foundation of my application Lync Agent.

Support Topologies

UCWA is only available on Lync Server 2013 on-premises deployments. In my world, on-premises can mean both within a corporate network, or hosted in a 3rd party Data Centre.

However, UCWA can deliver message to any Lync deployment, including:

  • The local deployment
  • External, On-Premises*
  • Externally hosted*
  • Lync Online/Office 365*

Lync Server 2013 UCWA Supported Topologies

*Where Instant Messages are destined for non-local deployment of Lync Server, the external environment must be Federated with the local environment.

Microsoft has a great tutorial on how to Configure support for allowed external domains in Lync Server 2013.

 

 

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)