Managing Applications

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

In the Office Communications Server 2007 administrative tools, you can see the current state of MSPL (Microsoft SIP Processing Language) applications that are running on each server in your Office Communications Server environment and control the availability of applications.

Managing applications includes the following:

  • Viewing and Configuring Applications

  • Adding Script-Only Applications

Viewing and Configuring Applications

On the Applications tab, you can see the current state of Microsoft SIP Processing Language (MSPL) applications that are running on each server in your Office Communications Server environment. You can also move an application up or down in the list, enable or disable it, specify it as critical, or edit it.

Available applications lists the applications that are available on this server, shows whether they are running, and displays the uniform resource identifier (URI) for each one. The applications run in the order they are listed. These applications include the following:

  • ClientVersionFilter provides the administrator with a way to specify the version of clients that are supported by a pool. The client version filter checks the client version and can then either prevent the client from logging on or present the user with a message that indicates he or she is using a client that is not supported. The client version filter can also be configured to display a message to the user that contains the URL of the latest downloadable version of the client.

  • TranslationService translates a number that a user dials to an E.164 number according to the normalization rules defined by the administrator.

  • UserServices is the SIP registrar, presence, and conferencing component of a Front End Server. It provides closely integrated IM, presence, and conferencing features built on top of the SIP Proxy.

  • IIMFilter (Intelligent IM Filter) blocks messages that contain clickable URLs or that attempt to initiate file transfers. IIMFilter also checks the client version on behalf of the server. IIMFilter affects both file transfers that are initiated by using either Office Communicator or the Live Meeting 2007 client. By default, clickable links are disabled by adding an underscore character before the first character of the link. An administrator can change this behavior so that the link is blocked, in which case messages that contain clickable URLs or that attempt to initiate a file transfer are blocked by the server from reaching their intended destinations. IIMFilter is installed on all Office Communications Servers except Proxy Servers and Archiving and CDR Servers.

  • DefaultRouting is the default routing application for Office Communications Server servers. It is enabled by default. The routing application is installed on all Standard Edition and Enterprise Edition servers.

  • ExumRouting routes calls to Exchange Server Unified Messaging. ExumRouting determines the appropriate Exchange Unified Messaging server to route the call to when there is a new voice mail message to deposit. ExumRouting also handles some other Unified Messaging integration aspects, including routing to Auto Attendant and Subscriber Access.

  • OutboundRouting determines the gateway that routes a call to a phone number according to the dialed number and the users dialing authorization. OutboundRouting also handles rerouting of calls if a gateway cannot process a call.

You can also add a script-only application.

You can move each application up or down in the list to control when it runs. The applications run in order, starting at the top of the list.

If you specify that an application is critical, the application must start during system startup, or Office Communications Server will not start. If the application fails while Office Communications Server is running, the server does not shut down, but it stops sending traffic to the application, and it writes errors in the event log.

For more information about MSPL applications, see the Microsoft SIP Processing Language topics in the SDK documentation for Office Communications Server 2007 at https://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=SDK.

Adding Script-Only Applications

A script-only application is one that uses the MSPL (Microsoft SIP Processing Language) scripting language instead of the Office Communications Server API (Application Programming Interface). MSPL provides more granular control over filtering and proxy behaviors, as well as a facility for dispatching specific messages to transaction-based SIP applications. MSPL is used specifically for filtering and routing SIP messages. MSPL applications run in the same process as the UserServices module, while a program that is based on the RTC API runs in a separate process. To add a script-only application, you specify the following:

  • Script path. This is the location of the script-only application.

  • Application name. This is the name of the application. This name need not relate to the URI (uniform resource identifier) of the script in any way. Multiple script applications can have identical application names.

  • URI. This is the URI that is used in the script to identify the application. For the application to run, the URI listed must match the one in the script. The URI must begin with http://.

For more information, see the Microsoft Office Communications Server 2007 SDK.