Add or Edit Static Route

Use this dialog box to configure a new static route or modify an existing static route to use for outbound connections.

Matching URI

Specifies the uniform resource identifier (URI) that an incoming network connection must use in order for the static route to be applied to the subsequent outbound connection. You can use the asterisk (*) symbol to specify wildcard characters in a URI. For example, *.contoso.com is a valid match pattern for sub-domains of contoso.com, such as asia.contoso.com.

Domain

Specifies the fully qualified domain name (FQDN) that will use this static route for outbound connections.

Phone URI

To specify that the URI of an incoming message must be a phone URI in addition to matching the domain in order to use this static route, select this check box.

Next hop

Specifies the computer that is the next hop in the route.

FQDN

The FQDN of the computer that is the next hop in the route.

Note: For security reasons, you can only specify the next hop server's FQDN if you configure the route to use Transport Layer Security (TLS) as the transport.

IP address

The IP address of the computer that is the next hop in the route.

Note: You can only specify the next hop server's IP address if you configure the route to use Transmission Control Protocol (TCP) as the transport.

Transport

Use this list to specify the transport protocol to use to send messages to the next hop computer. There are two choices:

  • TCP

    Specifies that the message sent to the next hop computer will use TCP.

  • TLS

    This specifies that the message sent to the next hop computer will use the TLS protocol.

    Port

This specifies the port on the next hop computer to which messages will be sent.

Replace host in request URI

To specify that the host part of the request URI in the incoming message be replaced with the address of an Internet Protocol public switched telephone network (IP-PSTN) gateway, select this check box.

Learn More Online

Click to expand or collapse

A static route is created to direct traffic to a specific entity. For example, you create a static route to handle messages with phone URIs. According to the 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 IP-PSTN gateway that routes the call so that the phone number associated with the phone URI receives a call.

If you create a static route, but messages are not routed as you expect, ensure that the static route is configured properly. You can edit an existing static route so that it better matches the incoming messages that you want to route using the static routing rules. If a message that you expect to use the static routing rules does not use it, confirm that the routing rule is not too restrictive regarding the domain name. Also, confirm that the next hop computer can be reached by all the servers in the pool.

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

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×