[an error occurred while processing this directive][an error occurred while processing this directive]

Using New Transaction Policies to Route SIP Requests Using Server Clusters

Before creating a new transaction policy that provides routing using server clusters, you must define availability profiles for servers, define the servers that can be used in server clusters, and define clusters, assigning each server in the cluster a priority and weight. Server clusters can be used in the route option of a new transaction policy instead of individual next-hop destinations.

This topic consists of the following sections:

Creating Availability Profiles for Servers

To create an availability profile for servers:

  1. Access the availability check option under SIP routing destinations and assign a profile name.
    edit services border-signaling-gateway gateway bsg-1 sip availability-check-profiles avail-profile-1
  2. Assign one of the following keepalive strategies:
    • Check all servers, whether they are currently up or down.

      [edit services border-signaling-gateway gateway bsg-1 sip routing-destinations availability-check-profiles avail-profile-1]user@host# set keepalive-strategy send-always failures-before-unavailable 2 successes-before-available 2
    • Check only servers that are unavailable.

      [edit services border-signaling-gateway gateway bsg-1 sip routing-destinations availability-check-profiles avail-profile-1]user@host# set keepalive-strategy send-when-unavailable successes-before-available 2
    • Do not check servers. Establish a blackout period after which a server that is down is removed from the blacklist.

      [edit services border-signaling-gateway gateway bsg-1 sip routing-destinations availability-check-profiles avail-profile-1]user@host# set keepalive-strategy do-not-send blackout-period 15
  3. Set a time interval for sending ping messages to check server availability.
    • To assign a time interval for sending messages to servers that are up:

      user@host# set keepalive-interval available-server 5
    • To assign a time interval for sending messages to servers that are down:

      user@host# set keepalive-interval unavailable-server 5
  4. Set the number of seconds with no response following a ping, after which the ping is considered to have failed.
    user@host# set transaction-timeout 5

Configuring Servers for Use in Server Clusters

To configure a server for use in server clusters:

  1. Access the server configuration option in the SIP routing destinations hierarchy and name the server.
    user@host# edit services border-signaling-gateway gateway bsg-1 sip routing-destinations servers server-1
  2. Specify an IP address for the server and, optionally, a port and transport protocal.
    user@host# set address 62.17.56.28
  3. Specify the service point used when traffic is routed to this server as part of a destination server cluster.
    user@host# set service-point sip-tcp-5060
  4. (Optional) Specify the admission control profile to use for transactions using this server.
    user@host# set admission-control acprofile1
  5. (Optional) Specify the profile used to check the availability of this server.
    user@host# set availability-check-profile avail_profile1

Configuring Server Clusters

You configure server clusters as routing destinations by including the individual servers that constitute the cluster and assigning each a priority and weight. To configure server clusters:

  1. Access the server cluster configuration option in the SIP routing destinations hierarchy and assign a name to the server cluster.
    user@host# edit services border-signaling-gateway gateway bsg-1 sip routing-destinations clusters scl_1
  2. Assign a server to the cluster.
    [edit services border-signaling-gateway gateway bsg-1 sip routing-destinations clusters scl_1user@host# edit servers server_1
  3. Set the priority and weight for the server.
    [edit services border-signaling-gateway gateway bsg-1 sip routing-destinations clusters scl_1 server server_1user@host# set priority 5 weight 5
  4. Repeat Step 2 and Step 3 until you have included all the servers for the cluster.

Routing SIP Requests to Server Clusters

You can route SIP requests by specifying a defined server cluster in the route statement.

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 a server cluster as the target of the route action for this policy.
    [edit services border-signaling-gateway gateway bsg-1 sip new-transaction-policy emergency-call-route term t1]user@host# set then route cluster scl_1

Published: 2010-04-13

[an error occurred while processing this directive]