Technical Documentation

Using New Transaction Policies to Route SIP Requests (next-hop)

You can route SIP requests by specifying a next-hop action. This action selects the SIP entity towards which SIP requests are sent. You can configure the next-hop as a static IP address or an address extracted from the SIP request URI. You can also configure the interface, IP address, and port number from which the request exits the BSG by setting an egress service point.

To configure a new transaction policy to route SIP requests:

  1. Access the configuration of a new transaction policy.
    [edit services border-signaling-gateway gateway bsg-1 sip]user@host# edit new-transaction-policy emergency-call-route
  2. Configure a term for the policy.
    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy new-transaction-policy emergency-call-route]user@host# edit term t1
  3. Configure match conditions for the policy. For example, to match incoming traffic based on the contents of the request URI:
    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy emergency-call-route term t1]user@host# set from request-uri regular-expression “sip:911@.+ | tel:911”
  4. Configure actions to be taken on messages that match the term conditions. For example:
    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy emergency-call-route term t1]user@host# set then route next-hop address 196.10.3.45 port 5060
  5. Configure an exit point of SIP requests from the BSG. This is a service point that you configure with the service-point statement.
    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy emergency-call-route term t1]user@host# set then route egress-service-point sip-udp-5060

Published: 2010-04-22