SIP Routing Overview

The BSG uses SIP routing to determine the next-hop and exit point of SIP messages. You define SIP routing in policies. Each incoming SIP request is matched to a policy that specifies how the SIP request is routed.

You can configure the policy to match incoming SIP requests to the:

• Contact field in the SIP message
• Request URI field in the SIP message
• SIP method in the SIP message
• Source address and mask fields in the SIP message

You can specify the following actions to be taken on SIP requests that match the policy:

• Next-hop—You can specify the next-hop as a request URI or as a static IP address.
• Egress service point—You can specify the IP address of the interface from which SIP requests exit the router and set a port number and transport protocol used to route the request.

You can alternatively specify that server clusters be used as routing destinations. In this case, you cannot specify next-hop and egress-service point.

Related Topics

• SIP Routing with Server Clusters Overview
• Using New Transaction Policies to Route SIP Requests (next-hop)
• Using New Transaction Policies to Route SIP Requests Using Server Clusters