Network Deployment (Distributed operating systems), v8.0 > Reference > Custom properties
SIP proxy server custom properties
We can add the following custom properties to the configuration settings for the SIP proxy server.
To specify custom properties for a specific SIP proxy server, navigate to the custom properties page, and specify a value for the custom property.
The custom properties are supported as the primary method of configuration. Therefore, if a custom property is set and then you set the corresponding setting in the admin console, the custom property value is used.
- In the admin console, expand Servers > Server Types > WebSphere application servers > server_name
to open the configuration tab for the server.
- From SIP proxy server settings, expand SIP proxy settings, and click Custom properties.
- From Additional properties, select Custom properties > New .
- On the settings page, type the custom property to configure in the Name field, and type the value of the custom property in the Value field.
- Click Apply or OK.
- Click Save on the console task bar to save the configuration changes.
- Restart the server.
We can define the following SIP proxy custom properties that are provided with the product. These properties are not shown on the settings page for a proxy server.
- Overload custom properties
- burstResetFactor
- deflatorRatio
- dropOverloadPackets
- inDialogAveragingPeriod
- lsnLookupFailureResponseCode
- lsnLookupFailureReasonPhrase
- maxThroughputFactor
- numFailuresSipAdvisorRequests
- outDialogAveragingPeriod
- overloadResponseCode
- overloadResponseReasonPhrase
- perSecondBurstFactor
- proxyTransitionPeriod
- sipProxyStartupDelay
- sipAdvisorRequestTimeout
- trustedIPAddressList
The following SIP general custom properties allow you to apply a variety of settings.
- defaultTCPChainName
- defaultTLSChainName
- defaultUDPChainName
- disable.failover.suicide
- //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .connectRetryLimit
- identityAssertionHeaderRemovalEnabled
- ignore.ucf.massages.from.proxy
- isSipComplianceEnabled
- keepAliveFailures
- keepAliveInterval
- LBIPAddr
- localOutboundTCPAddress
- maxForwardsHeaderRequired
- maxWriteQueueEntries
- receiveBufferSizeChannel
- receiveBufferSizeSocket
- retryAfterValue
- sendBufferSizeSocket
- serverUDPInterface
- serverUDPPort
- SIPAdvisorMethodName
- sipClusterCellName
- tcp.IPSprayer.host
- tcp.IPSprayer.port
- tls.IPSprayer.host
- tls.IPSprayer.port
- udp.IPSprayer.host
- udp.IPSprayer.port
SIP overload protection
Load balancing with the SIP proxy server
Configure the SIP container
Create a proxy server
Overload custom properties
Several of the SIP custom properties allow you to apply proxy-managed overload protection (PMOP). The PMOP overload settings allow for real-time protection against container overload.
- burstResetFactor
- deflatorRatio
- dropOverloadPackets
- inDialogAveragingPeriod
- maxThroughputFactor
- outDialogAveragingPeriod
- perSecondBurstFactor
- proxyTransitionPeriod
- sipProxyStartupDelay
- overloadResponseCode
- overloadResponseReasonPhrase
For more information on overload controls, refer to the Information Center topic SIP overload protection.
burstResetFactor
Percentage of bursts during a given period of time. This custom property controls the amount of bursts that occur during the averaging period.
Data type Integer Default 100
deflatorRatio
Static ratio. This custom property is only used during the transition period when a transition period is specified.
Data type Integer Default 0
dropOverloadPackets
Whether or not to drop packets when the SIP container is in an overloaded state. When this value is set to False, the proxy server responds with a 503 error when overloaded, otherwise the packet is dropped.
Data type Boolean Default False
inDialogAveragingPeriod
Period of time, in seconds, during which in-dialog messages are averaged.
Data type Integer Default 180
lsnLookupFailureResponseCode
Response code when a SIP request for affinity fails. This custom property enables you to override the default 404 error response that normally displays when affinity fails.
Data type Integer value that is a valid SIP response code Default 404
lsnLookupFailureReasonPhrase
Response text to display when a SIP request for affinity fails. This custom property enables you to override the default "Not Found" error text that normally displays when affinity fails.
Data type String Default "Not Found"
maxThroughputFactor
Percentage of the maximum number of messages per averaging period set. If this value is set to 0, then the maximum throughput feature is disabled. This custom property is used to calculate the maximum number of messages allowed per second before the proxy server begins to reject requests for new sessions. This custom property should be set to the same value for each proxy server.
For transitioning users: If you are migrating from a previous version of the product, the migration tools provided with the product do not migrate the setting for this custom property when they migrate the other configuration settings for the system. If you used migration tools to migrate the configuration settings, and need to have MTF enabled, use the admin console to specify a value for the maxThroughputFactor custom property after you complete your migration. trns
Data type Integer Default 0
numFailuresSipAdvisorRequests
Indicates the number of SIP advisor requests to miss before the SIP proxy recognizes that is it not processing any data. With this custom property, the SIP proxy will notice the failure to receive load balancer advisor requests.
If you use this custom property, consider setting its value to 3.
Data type Integer Default No default value - this property is not enabled unless you specify a value.
outDialogAveragingPeriod
Period of time, in seconds, during which out-dialog messages are averaged.
Data type Integer Default 360
overloadResponseCode
Value for the response code returned from the proxy when overload occurs and SIP requests from the container are rejected. When the proxy is configured for overload protection, the SIP proxy can be configured to detect overload status. The proxy monitors the amount of traffic processed at the proxy and limits the number of new requests. If a container is overloaded, the proxy rejects requests with a 503 response code. If you prefer to use a different response code for overload protection, you can configure this custom property to return a different response code.
Data type Integer Default 503
overloadResponseReasonPhrase
The response reason phrase that the proxy server issues when overload occurs and SIP requests from the container are rejected. When the proxy is configured for overload protection, the SIP proxy can be configured to detect overload status. The proxy monitors the amount of traffic processed at the proxy and limits the number of new requests. If a container is overloaded, the proxy rejects requests with a Service Unavailable response phrase. If you prefer to use a different response phrase, you can configure this custom property to return a different response phrase.
Data type String Default Service Unavailable
perSecondBurstFactor
Percentage of bursts allowed through periodically (BTF).
Data type Integer Default 150
proxyTransitionPeriod
Period of time, in seconds, to lock the deflator after the container shuts down.
Data type Integer Default 0
sipAdvisorRequestTimeout
Specifies, in milliseconds, the amount of time the SIP proxy server waits for a DNS lookup to return from the Load Balancer.
If you do not specify a value for this custom property, the SIP proxy server waits for 2 seconds.
Specify a value of 0 to disable the monitoring of DNS lookups.
Data type Integer Default 3000 milliseconds
sipProxyStartupDelay
Period of time, in seconds, before the proxy server restarts to allow the proxy to become stable in the cluster and avoid an erroneous overloaded state.
Data type Integer Default 0
trustedIPAddressList
Colon-delimited list of IP addresses from which messages with a p-asserted identity header can flow through the SIP proxy server for WAS. If a p-asserted identity header exists in a message from an IP address that is not in this list of IP addresses, the header is removed.
The list of IP addresses must be specific, such as 192.168.0.1.
Beginning with this service release, the custom property requires a semicolon-delimited list. Also, you can specify a range of IP addresses such as 192.168.0.* instead of a list of specific IP addresses.
Data type Numerical list of IP addresses Default None
defaultTCPChainName
Default TCP chain name to use when setOutboundInterface is not called. If you are using the web collaboration feature of the Feature Pack for Communications Enabled Applications (CEA) in a multihome environment, set this variable properly so that the web collaboration component can pick up the proper interface to use when routing data.
Data type String Default None
defaultTLSChainName
Default TLS chain name to use when setOutboundInterface is not called. If you are using the web collaboration feature of the Feature Pack for Communications Enabled Applications (CEA) in a multihome environment, set this variable properly so that the web collaboration component can pick up the proper interface to use when routing data.
Data type String Default True
defaultUDPChainName
Default UDP chain name to use when setOutboundInterface is not called. If you are using the web collaboration feature of the Feature Pack for Communications Enabled Applications (CEA) in a multihome environment, set this variable properly so that the web collaboration component can pick up the proper interface to use when routing data.
Data type String Default None
disable.failover.suicide
Whether the SIP failover mechanism is active. When this mechanism is active, the SIP container to shut itself down when it detects that all proxy connections are down. If you set this property to true, the SIP failover mechanism is disabled, and the SIP container does not shut itself down even if all proxy server connections are down.
Data type Boolean Default false
//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .connectRetryLimit
Specifies how many times the WebSphere Proxy Server attempts to establish a connection with the back end server before that server is marked as down.
If you do not add this custom property to your WebSphere Proxy Server settings, whenever the WebSphere Proxy Server fails to make a connection to a back end server, that server is marked as down, and no more requests are routed to that server until the amount of time specified for the retryAfterValue custom property elapses, even if another connection attempt would have been successful. For example, the first attempt to make a connection might have failed because an ephemeral port is reused too quickly, and the prior connection is still in a TIME_WAIT state.
Data type Integer Default 0
identityAssertionHeaderRemovalEnabled
Specifies that all identity assertion related headers in SIP requests coming through the SIP Proxy to the SIP containers should be removed. If you set this property to false, the identity assertion related headers are kept as part of the requests.
Data type Boolean Default true
ignore.ucf.massages.from.proxy
Specifies that proxy detection through UCF is disabled and the SIP container should not listen to SIP proxy messages that come through UCF. If you set this property to true, only SIP startup messages, which indicate that the front-end proxy server is up and running, and SIP messages that monitor the health of SIP communication lines between a SIP proxy server and the SIP container, are used to monitor communication with a SIP proxy server.
You should set this property to true if you are using a proxy server that is installed in a DMZ because messages that come through UCF are not reliable for proxy servers that are installed in a DMZ..
Data type Boolean Default false
isSipComplianceEnabled
Whether SIP compliance checking is enabled in the SIP proxy server. SIP compliance checking ensures that the SIP messages conform to the SIP standard. When this property is set to true, SIP compliance checking is enabled. If you are running a proxy server in a z/OS WAS ND environment, and your proxy server is not part of a cluster, you can use this custom property to enable or disable SIP compliance checking for that SIP proxy server. However if you are running a stand-alone application server or your proxy server is part of a cluster, use the DisSipComplianceEnabledto generic JVM argument to enable or disable SIP compliance checking.
Data type Boolean Default true
keepAliveFailures
Number of keepalive messages that must be missed before the proxy determines that the connection with the SIP container is down.
The proxy sends a keepalive message to the container at each keepAliveInterval. If the proxy does not receive a response to the message, it considers the lack of response as a failure. If the proxy receives a specific number of consecutive failures, it considers the container down and begins forwarding messages to a different SIP container.
Data type Integer Default 0
keepAliveInterval
Interval, in milliseconds, at which keepalive messages are sent to the SIP containers. A keepalive message is sent at the specified interval. If the specified number of keepAliveFailures messages is received from the SIP container, the proxy considers the container to be down. The proxy then routes data to a back-up SIP container until the connection between the proxy and the primary container is restored.
The first keepalive message contains the interval of time between the keep alive messages and the number of failures that are required before the container is considered down. The starting values should be specified based on the high availability (HA) heartbeat configuration.
Data type Integer Default 0
LBIPAddr
Specifies the IP address, such as 192.101.1.5, of the load balancer used to load balance the SIP proxy. Multiple load balancer addresses can be configured by separating each IP address using a semicolon (;).
When SIP messages with the method configured as SIPAdvisorMethodName are received by the SIP proxy from the specified IP address, the SIP proxy responds with a success message if the SIP proxy can forward the messages to the SIP container. The SIP proxy responds with a failure message if messages cannot be forwarded to the SIP container. The load balancer then determines if the messages should be routed to the SIP proxy.
Data type String Default null
localOutboundTCPAddress
Source interface to which the proxy binds when establishing connections to back-end SIP containers. This property is used when your proxy server is multihomed and needs to be configured to use a specific interface to send SIP traffic to the SIP containers. This property applies to both Transmission Control Protocol (TCP) and Transport Layer Security (TLS) connections.
Data type String Default *
maxForwardsHeaderRequired
Whether a Max-Forwards header must be present in all SIP requests and responses. The Max-Forwards header is used to limit the number of proxies or gateways that can forward a request.
The SIP Proxy requires that the Max-Forwards header be present in all SIP requests and responses. When this property is set to true, which is the default setting, and a Max-Forwards header is not included in a request, the SIP proxy issues a warning message that sends a 400 error response to that SIP request.
If you set this custom property to false the Max-Forwards header requirement is not enforced the requirement of the Max-Forwards header being required. Even if this property is set to false the SIP proxy decrements the value of this header if it is present in the request.
Data type Boolean Default true
maxWriteQueueEntries
Number of messages that can be queued when a connection is slow or cannot be established. If the value is a large number, then more memory is consumed. A small number causes packets to be lost if the endpoint clears.
Data type Integer Default 100000
receiveBufferSizeChannel
Value, in bytes, for the maximum size of an incoming UDP packet, which is the size of the receive buffer that is allocated in the proxy server-side UDP connection.
Data type Integer Default 65535
receiveBufferSizeSocket
Value, in bytes, for the lower-level datagram buffers, which is the size of the DatagramSocket receive buffer (SO_RCVBUF) in the proxy server-side User Datagram Protocol (UDP) connection.
Use this property to buffer multiple packets in the DatagramSocket layer. If the value of the property is too small, then packets might be lost if the server is overloaded. If the value is too large, then the packets might be delayed.
Data type Integer Default 1024000
retryAfterValue
Amount of time, in seconds, before the client tries again to route a request to the proxy server. This custom property value is returned to the client in the error response if the SIP container is overloaded or if the SIP proxy cannot locate a server to which to route a request.
Data type Integer Default 5
sendBufferSizeSocket
Value, in bytes, for the lower-level datagram buffers, which is the size of the DatagramSocket send buffer (SO_SNDBUF) in the proxy server-side UDP connection.
Use this property to buffer multiple packets in the DatagramSocket layer. If the value of the property is too small, then packets might be lost if the server is overloaded. If the value is too large, then the packets might be delayed.
Data type Integer Default 1024000
serverUDPInterface
Host name or IP address used for all communications between the SIP proxy and the SIP containers when the network is segmented. This interface is the specific network interface for all UDP data that enters or exits the SIP containers. We must use this property with the serverUDPPort property.
Data type String Default *
serverUDPPort
Specifies the UDP port used for SIP container communications. When the firewall is between the SIP proxy and the SIP container, you might set this value if a specific interface is needed to communicate with the SIP containers or if a specific port is required to pass through the firewall.
Data type String Default dynamic
SIPAdvisorMethodName
String value for the method sent by the load balancer to the SIP proxy for health checks.
The format is OPTIONS or INFO. This property is used with the LBIPAddr property.
Data type String Default null
sipClusterCellName
Actual cell name that contains the cluster of SIP containers.
Set the sipClusterCellName custom property to be the cell name that contains the configured cluster of SIP containers
Data type String Default Cell name in which the proxy resides
tcp.IPSprayer.host
Specified the host name for the IP Sprayer for Transmission Control Protocol (TCP) packets.
Data type String Default None
tcp.IPSprayer.port
Specified the port for the IP Sprayer for Transmission Control Protocol (TCP) packets.
Data type String Default None
tls.IPSprayer.host
Specified the host name for the IP Sprayer for Transport Layer Security (TLS) packets.
Data type String Default None
tls.IPSprayer.port
Specified the port for the IP Sprayer for Transport Layer Security (TLS) packets.
Data type String Default None
udp.IPSprayer.host
Specified the host name for the IP Sprayer for User Datagram Protocol (UDP) packets.
Data type String Default None
udp.IPSprayer.port
Specified the port for the IP Sprayer for User Datagram Protocol (UDP) packets.
Data type String Default None