News

OCS Gains New Developer Hooks

Microsoft Office Communications Server 2007 adds new APIs and integration with Visual Studio.

• By Jeffrey Schwartz
• 11/01/2008

The new release of Office Communications Server (OCS) 2007 is an incremental upgrade, though it offers some noteworthy new capabilities for .NET developers looking to add conferencing-, presence- and telephony-oriented capability to business applications.

Dubbed OCS R2 and available for private beta testing, the updated release comes with new APIs and features integration with the latest release of Microsoft's Visual Studio. Microsoft plans to officially launch a new OCS release in February, the company said at the VoiceCon Conference last month in Amsterdam, Netherlands.

Since it was released one year ago, thousands of organizations began using OCS 2007 as their primary voice-communications platform, said Stephen Elop, president of Microsoft's business division, in a video statement released at the VoiceCon show.

Tom Nolle, president of the Voorhees, N.J.-based telecommunications consulting firm CIMI Corp., says OCS has gotten off to a respectable start in Microsoft-centric shops.

"Those with SharePoint, for example, seem to be adopting it almost completely, at least in my experience," Nolle says in an e-mail. "There aren't any issues in terms of negatives that I'm aware of with respect to adoption, but it will be important for enterprises to review their overall voice, UC [unified communications] and collaboration strategies given the new release and the directions. [But it looks] promising."

New and Improved
Among the new features in OCS 2007 R2 are built-in audio teleconferencing, desktop sharing and what Microsoft calls "persistent group chat." The new chat feature is aimed to let teams participate in specific topic-based chat sessions that persist over periods of time.

On the voice side, the new release will allow for improved call management, including response groups that manage incoming calls based on predefined workflows; call delegation; and VoIP-based call trunking.

There are two key new capabilities for the developer experience, says Anand Ramakrishna, principle group manager for Microsoft's Office Communications Server Developer Experience. First, the object model will allow developers to tweak behaviors and do more advanced kind of scenarios so they "can get down and write code," Ramakrishna says. The other key developer capability centers around improvements to the API set called the Universal Communications Management API. The new API addresses support for presence, teleconferencing and call controls.

Developers will be able to integrate these new and existing features into their applications with Visual Studio 2008 using the latest capabilities in .NET Framework, Ramakrishna says.

One such example is Windows Workflow Foundation. "We created Windows Workflow activities that you can drag and drop onto your workflow agent or your designer, and then model it using those APIs," Ramakrishna explains. "You can bring up your workflow canvas and drag and drop the UC activities onto your workflow -- in conjunction with your other workflow activities."

For instance, this will let developers build UC into their workflow models in SharePoint, while taking into account human latency in business processes. "We're bringing [UC] and integrating that so that you can do intelligent routing and intelligent notification from Windows Workflow," Ramakrishna says. Applications can range from the routing and approval of forms to integration with CRM-type apps, he adds.

In addition to call management, presence and teleconferencing, Ramakrishna points out that the new API set supports speech recognition and notification.