What Is UCMA 3.0 Core

Microsoft Unified Communications Managed API (UCMA) 3.0 is used primarily to build middle-tier applications that work with Microsoft Lync Server 2010.

UCMA 3.0 provides a flexible managed-code platform for unified communication and collaboration that allows developers to implement communication- and collaboration-enabled services against Lync Server 2010.

UCMA 3.0 Core Features

• The platform contains a managed code endpoint API that is based on Session Initiation Protocol (SIP), and is written in Visual C#.

• The platform is multilayered, with different levels of abstraction, as shown in the following illustration. The components that make up the platform are shown in the blue blocks.

  • UCMA 3.0 Workflow activities are available in Microsoft Unified Communications Managed API (UCMA) 3.0 Workflow SDK.

  • Unified Communications and Collaboration protocol layer (UCMA 3.0 Core). The classes in this layer are exposed in the Microsoft.Rtc.Collaboration namespace. The protocols include Enhanced Presence, Centralized Conference Control Protocol (C3P), Contacts and Groups, and Call Control.

    The Microsoft.Speech namespace can be used to provide speech recognition and speech synthesis capabilities in UCMA 3.0 applications.

    Interactive Voice Response (IVR) applications that can optionally use Voice XML can be created from classes contained in the Microsoft.Rtc.Collaboration.AudioVideo.VoiceXml and Microsoft.Speech.VoiceXml namespaces (Microsoft.Rtc.Collaboration.AudioVideo.VoiceXml.dll and Microsoft.Speech.VoiceXml.dll, respectively). For more information, see VoiceXML Support in UCMA 3.0 Core.

  • Signaling layer. This layer provides access to the SIP/SIMPLE infrastructure. The classes in this layer are exposed in the Microsoft.Rtc.Signaling namespace.

    The Audio stack is used by some classes in UCMA 3.0 Core, but does not expose any public classes.

  Note

  UCMA 3.0 Core is contained in a single assembly, Microsoft.Rtc.Collaboration.dll.

  

• The platform is highly scalable.

  The platform is able to support thousands of endpoints and concurrent communications and collaborations. The platform is designed for server operating systems (the recommended operating systems are Microsoft Windows Server 2008 SP2 64-bit or Windows Server 2008 R2), and is multi-threaded.

• The platform provides high availability.

  The deployment model permits multiple, load-balanced application instances that allow for server-grade load balancing and fail-over. Dialog resiliency is built in to update the route set in the event of intermediate hop failures.

• The platform is extensible.

  New modalities can be added to the existing communication framework, and extension headers and URI parameters can be supplied and consumed through the APIs.