[Contents] [Prev] [Next] [Index] [Report an Error]

Using New Transaction Policies to Route SIP Requests

You can route SIP requests by specifying a next-hop action. This action controls 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 according to SIP rules. You can also configure where the request exits from the BSG by setting an egress service point.

Step-by-Step Procedure

To configure routing policy actions:

  1. Create a new transaction routing policy.
    user@host#edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tp1 term term1 then route
  2. Configure the next-hop address.

    To configure the next-hop address as a static ip (ipv4) address:

    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tp1 term term1 then route]
    user@host#set next-hop address 196.10.3.45

    To configure the next-hop address based on the input uri:

    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tp1 term term1 then route]
    user@host#set next-hop address request-uri
  3. Configure the egress service-point.
    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy tp1 term term1 route]
    user@host#set egress-service-point eserv1
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.