This documentation is archived and is not being maintained.

SIP Application Manifest Example

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.

Following is an example of a basic application manifest that handles only SIP INVITE and MESSAGE requests.

<?xml version="1.0" ?>

<!-- Set the application URI, the namespace prefix, and the namespace name -->

    <!-- Define properties of the application -->
    <lc:requestFilter methodNames="INVITE,MESSAGE"
                      domainSupported="true"/ >
    <lc:responseFilter reasonCodes="NONE" />
    <lc:proxyByDefault action="true" />
    <lc:scriptOnly />

    <!-- The message filtering script -->
      if (sipRequest) {
        if (sipRequest.Method == StandardMethod.Invite) {
        else if (sipRequest.Method == StandardMethod.Message) {


In this example, the appUri attribute of the applicationManifest element specifies the URI that uniquely identifies the application to Office Communications Server. The xmlns attribute specifies the namespace alias. The namespace alias identifies the XML elements in the manifest that are specific to the application. In this example, the namespace alias is set to "lc" and is separated from each element name using a colon.

The requestFilter and responseFilter elements set the basic filters for SIP request and response messages, respectively. These settings control the types of messages that the application processes. In the preceding example, only requests with a SIP method type of INVITE or MESSAGE are dispatched to the application. SIP reason codes from responses are not passed to the application.

The presence of the scriptOnly element indicates that the application has no managed code component, and that all message handling is performed solely within the Microsoft SIP Processing Language (MSPL) script. For SIP managed code applications, this element must be absent from the manifest.

The message filtering script itself is defined in the CDATA section that is contained in the splScript element.

See Application Attribute Elements for descriptions of all of the possible application manifest elements.