Use the Routing tab to define static routes for outbound traffic on this server. A static route includes a fixed Uniform Resource Identifier (URI) or telephone number for an outbound network connection, along with the fully qualified domain name (FQDN) and IP address of the next hop server along the route.
Lists static routes used by this Proxy Server for outbound connections. Each entry in the list includes the URI that must be matched to use the static route, and the next hop server, port, and transport for this route.
The domain name that an incoming network connection must use in order for the static route to be applied to the subsequent outbound connection.
The address of the computer to which matching incoming network connections on this Proxy Server will be routed.
The port on the next hop computer to which matching incoming network connections on this Proxy Server will be routed.
The transport that will be used to route connections to the next hop computer.
Creates a new static route for outbound connections for this Proxy Server.
Redefines the selected static route in the Routing list.
Removes the selected static route from the Routing list.
Learn More Online
Click to expand or collapse
You can create multiple static routes, but in order 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 Proxy Server 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.