Managing a SIP Application on Live Communications Server

The Live Communications Server WMI provides two classes specifically used to install and manage applications developed with the Live Communications Server Management API suite:

The MSFT_SIPApplicationSetting class must be instantiated whenever you want to register an application on the Live Communications Server. For more information on creating an instance of this class for your application, see Registering a SIP Application with Live Communications Server.

The MSFT_SIPApplicationPriorityList class defines the order in which applications are executed whenever a SIP message is received. The first application instance in the list will have the first opportunity to handle an incoming request; if the request is proxied or forked, it will be sent to the next application, and so on. Conversely, responses are handled in reverse order, with the last application in the list handling the response first, the next-to-last subsequently handling it on proxy, and so on. This is necessary because the last application in the list has the most immediate relevance to the response returned by the client transaction, having handled it last.

Applications are added to the execution order as they are registered with MSFT_SIPApplicationSetting, and they are removed when their corresponding MSFT_SIPApplicationSetting instance is removed from the WMI repository.

An application cannot be directly added to or deleted from the execution order; however, this list can be reordered by the user. As long as the elements in the execution order do not change, it can be updated as needed, allowing the user to place newer applications at the top of the list.