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.
Using the SIP Managed Application API
The following documentation provides material and example code useful to Office Communications Server application developers, from creating the initial application manifest to installing and managing the finished SIP application.
Topic |
Description |
|---|---|
Describes the logic behind two types of proxy applications that Office Comunications Server supports, including the required SIP objects. |
|
Creating a SIP Managed Application for Office Communications Server |
Describes the process of creating a SIP proxy application for Office Communications Server. |
Decribes how to thread dispatched SIP messages for efficient service by an application. |
|
Describes the classes that manage various types of transactions. |
|
Describes how to dispose of objects whose lifetimes are dictated by a server agent. |
|
Describes how to configure garbage collection to optimize application performance. |
|
Details how to synchronize thread access to SIP transaction objects. |
|
Describes approaches for successfully debugging SIP applications created with this API suite. |
|
Registering a SIP Application with Office Communications Server |
Details the process for registering a SIP application with the Office Communications Server. |
Details specific WMI classes used for managing a SIP application installed on the Office Communications Server. |