Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

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.

Message proxy and routing behaviors are configurable for Microsoft Office Communications Server 2007 through the following classes.

  • MSFT_SIPProxySetting defines the basic properties and behaviors of all message proxy services running on Office Communications Server, including third-party proxy applications installed on Standard Edition servers, in Enterprise Edition pools, or on Proxies or Access Proxies. The properties exposed by this class govern such behaviors as:

    • Data compression on incoming connections

    • Message size

    • Number of outgoing TLS connections

    • Internal routes to Access Proxies

    • Whether servers expect clients to send white-space (that is, empty) messages to indicate they are still alive (yes for internal clients; no for outside and federated clients).

  • MSFT_SIPRoutingSetting defines the transport type used for routing messages. Currently, there are two choices: TCP and TLS. For TLS routing, certificate information must be supplied in the configuration.

  • MSFT_SIPRoutingTableData (Updated) defines the configuration for an entry in the SIP message routing table for the Office Communications Server. Instances of this class define URI patterns that, when matched by the URI in the "Request-URI" header of a SIP request message, route the message to the host specified in the class instance. The routing table consists of all instances of this class available on Office Communications Server.

    If the Request-URI header of an incoming SIP message is matched by more than one instance of MSFT_SIPRoutingTableData (Updated), the more specific instance is chosen. For example, if there are two routing rules, "examp*.com" and "e*.com", the routing rule for "examp*.com" is chosen for the user "someone@example.com."


© 2015 Microsoft