Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Office Communications Server Application API Overview

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The Office Communications Server 2007 Server SDK Application API enables developers to develop custom applications that run on Office Communications Server 2007. The documentation for the Application API includes information regarding application manifests, and information regarding both script-based and managed code-based application components.

Start by reviewing the topics in the section SIP Application Manifests. All applications require an application manifest, regardless of whether they implement any managed components. The three major purposes of the application manifest are to:

  1. Specify the location of your application and its namespace information.

  2. Specify the types of SIP messages on which your application performs routing and filtering processes.

  3. Contain the script that performs the actual message processing and/or dispatches the message to a managed code component.

The SIP Message Routing and Filtering Tools section discusses how to write a basic message filter script and describes the script functionality provided by the Microsoft SIP Processing Language (MSPL).

The section About the SIP Managed Application API includes sample code that illustrates various SIP managed code application concepts, and also includes the reference documentation for the Microsoft.Rtc.Sip Namespace namespace.

Show:
© 2015 Microsoft