Learn about Microsoft Lync Server 2013 SDK managed SIP applications.
A managed SIP application in a Microsoft Lync Server 2013 scenario includes an application manifest, a Microsoft SIP Processing Language (MSPL) script, and a .NET Framework application that uses at least the Microsoft.Rtc.Sip namespace. The application manifest is used to specify message types to be processed by the managed SIP application. The MSPL script is used to dispatch the to-be-processed SIP messages to the managed message handler.
Managed SIP application, instead of a script-only message filter, development scenarios include:
Secure proxy applications that specifically authenticate and validate users, or perform additional encryption of specific message data.
Applications that can reference other external sources of information, besides the registrar, to determine proxy behavior. For example, a local database or Active Directory.
The basic classes for a managed SIP application include the ServerAgent type and the base Transaction type (which has two specific child types: ServerTransaction and ClientTransaction ). The ServerAgentobject is the interface between the application and the Lync Server 2013 computer. The Transaction objects are the managed code encapsulation of the Transaction class that is exposed in the MSPL built-in functions. To improve efficiency, the lifetimes of Transaction objects can be managed programmatically within the application.
The Microsoft.Rtc.Sip namespace also supports two kinds of proxy applications:
In Lync Server 2013, all server API applications must be compiled with the 64-bit version of Lync Server 2013 SDK.