Creating custom properties for load balancing on a WebSphere SIP proxy server

Create an additional set of custom properties on each IBM® WebSphere® proxy server to enable it to work with a Load Balancer. Create the complete set of properties on each WebSphere proxy server.

Procedure

  1. On the WebSphere proxy server, log in to the Integrated Solutions Console as the WebSphere administrator.
  2. Click Servers > Server Types > WebSphere proxy servers.
  3. In the proxy servers table, click the name of the server that you want to configure.
  4. On the Configuration page, under Proxy Settings, expand SIP Proxy Server Settings, and then click SIP proxy settings.
  5. In the Additional Properties section, click Custom Properties.
  6. Create the custom properties, using the information from the table:
    Table 1. Custom properties and values for load balancing on a SIP proxy server
    Property name Value
    tcp.IPSprayer.host Cluster address/virtual address This is the virtual address configured on the Load Balancer for that cluster.
    tcp.IPSprayer.port SIP port for TCP that is configured on the Load Balancer for that cluster.
    udp.IPSprayer.host See tcp.IPSprayer.host
    udp.IPSprayer.port SIP port for UDP that is configured on the Load Balancer for that cluster. TCP and UDP ports must be the same.
    tls.IPSprayer.host See tcp.IPSprayer.host
    tls.IPSprayer.port SIP port for TLS that is configured on the Load Balancer for that cluster.
    forceRport TRUE
    ipForwardingLBEnabled TRUE
    enableMultiClusterRouting TRUE
    disableAllHostNameLookups TRUE
    disableTraceHostNameLookup TRUE
    contactRegistryEnabled FALSE
    useViaSentByForOutboundConnections TRUE
    1. In the custom properties table, click New.
    2. Type a Name and a Value for the new custom property.
    3. Click OK to save the new property.
    4. Repeat this procedure for each additional custom property.
  7. Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
  8. Repeat for each WebSphere proxy server.