Pool Front End Properties: Routing

Use the Routing tab to define the static routes to be used by the servers in this pool. A static route is composed of a fixed Uniform Resource Identifier (URI) for an outbound network connection and the fully qualified domain name (FQDN) or IP address of the next hop computer on the route.

Routing

Specifies the static routes used by this pool for outbound connections.

Matching URI

This is the domain name that an incoming network connection must use in order for the static route to be applied to the subsequent outbound connection. If this is a phone URI, select the Phone URI check box.

Next Hop

This is the address of the computer to which matching incoming network connections on the servers in this pool are to be routed.

Port

This is the port on the next hop computer to which matching incoming network connections on the servers in the pool are to be routed.

Transport

This is the transport that will be used to route connections to the next hop computer.

Add

Create a new static route for outbound connections for the servers in this pool.

Edit

Modify the selected static route in the Routing list.

Remove

Remove the selected static route from the Routing list.

Learn More Online

Click to expand or collapse

You can create multiple static routes, but to avoid routing conflicts, static routes cannot include the same matching URI.

A static route is created to direct traffic to a specific entity. For example, you can create a static route to handle messages with phone URIs. According to such a static route, all inbound messages to this pool that contain a phone URI will be sent to the address specified as the next hop computer in the static route. That next hop computer can be an Internet Protocol public switched telephone network (IP-PSTN) gateway that routes the call so that the phone number associated with the phone URI receives a call.

For details, see the Operations section of the Office Communications Server Technical Library.