The Managed SIP Application API enables you to write server-side SIP applications using a managed code supported in .NET Framework.
Writing a server-side managed SIP application involves the following:
-
Use classes defined in the Microsoft.Rtc.Sip namespace.
-
Register the application with Microsoft Lync Server 2010 using the new-CCSServiceApplication Windows PowerShell command
-
Create at least one ServerAgent instance by calling the class constructor and supplying an ApplicationManifest object that contains a compiled application manifest.
This section provides an overview of the Lync Server 2010 Managed SIP Application API and describes the basic tasks for creating, registering, installing, debugging and deploying a managed SIP application.
 Note
|
|---|
|
In Lync Server 2010, all Server API applications must be compiled with the 64-bit version of the SDK. |
In This Section
|
Topic |
Description |
|---|---|
|
Describes the logic behind two types of proxy applications that Lync Server 2010 supports, including the required SIP objects. |
|
|
Describes the process of creating a SIP proxy application for Lync Server 2010. |
|
|
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. |
|
|
Details the process for registering a SIP application with Lync Server 2010. |
|
|
Details specific WMI classes used for managing a SIP application installed on Lync Server 2010. |
See Also
