Integrating OCS Presence with MOSS

Matt Lawson

Linda Nevils

Out of the Box Presence

• Uses client side JavaScript and ActiveX

• Dependent on Office Communicator being logged in

OCS 2007 APIs

API Example Languages Capabilities Client/Server

Complexity

UCMA Bot that provides information to workers

Managed Low level SIP API providing access to all SIP message types

Server Hard

Office Communicator

Office uses to display presence information and launch communicator

Managed or unmanaged

Presence indicators, contact lists, can launch OC for IM, audio, or video

Client Average

UCCA Enable communications in your client application without launching Communicator

Native COM+, Managed wrapper exists

Can do anything OC does – presence, contact lists, conferencing, audio, video, IM

Client Hard

Communicator Web Access

Add communications to your own web application.

Managed or unmanaged

Most of the same features as OC, but does not support voice or video

Both Average

There are currently 10 APIs. A few pertain to Speech IVR.

More information can be found on Joe Calev’s blog:

blogs.msdn.com/jcalev

Communicator Web Access API

• This API is composed of methods and events.

• A client sends a method as a request and receives data as events from the server.

• The communication is conducted primarily as HTTP POST requests.

• Two connections are made to the server for sending and receiving.

• For documentation and sample applications download the Microsoft Office Communicator Web Access AJAX Service SDK.

• Sample apps include simple instant message clients written in JavaScript and C#.

OCS Presence Integrated Into a Workflow

Demo

• SharePoint document library with a workflow template created in Visual Studio

• Review workflow

• Review web service created to get OCS presence

Other Uses

• Get presence information in an event handler: Email received, item added, etc

• Use presence information as part of a Underwriter selection process.