|Sonus Documentation Portal|
The Path Check Profile specifies the conditions that constitute a connectivity failure, and in the event of such a failure, the conditions that constitute a connectivity recovery. This section describes the CLI syntax, parameter descriptions and command examples.
Refer to Path Check Support for additional feature details.
After updating a Path Check Profile, you must disable and re-enable the profile for the change to take effect.
From 6.2.0 release onward, the SBC determines the SRS reachability only through the SIP ARS status. The
pathCheckProfile must be configured to determine the reachability of the SRS peers and treat failure response such as 501 as OPTIONS failure.
Sonus recommends to not configure Path Check Profile and SIP ARS Profile on the same peer to avoid unexpected results. As a general rule, the Path Check Profile is configured on the access leg where there is less traffic, and the ARS Profile is configured on the peer leg where there is continuous traffic.
The Path Check Profile parameters are defined below:
|400-699, or |
(all, all4xx, all5xx, all6xx)
Use this parameter to define one or more response codes to treat as failure responses. The options include the following:
INFO: When you use more than one value, enclose the values in square brackets [ ], separating each value with a space. Entering a value without using brackets appends the value to the existing configuration.
The ping protocol type used.
NOTE: Create a user ACL for ICMP if there are more than 50 sessions to support.
NOTE: Configure static routes to reach the target IP from interface through which the ICMP pings are generated.
The number of consecutive successful responses to occur before removing the endpoints from the Blacklist. (default = 6)
The time interval (in seconds) to elapse after which the ICMP PING request times out. (default = 1)
NOTE: This parameter applies when
The number of consecutive timeouts to occur before adding the endpoints to the Blacklist. (default = 6)
Specifies interval (in seconds) in which the PING request will be sent out to the endpoints. (default = 60)
Transport preference for sending OPTIONS method.
Note: A good practice is to configure separate pathCheckProfiles for each transport type; each profile having only preference1 set. By assigning a pathcheck profile with a transport type matching an ipPeer's transport type, you will ensure that SBC will not send SIP OPTIONS ping over a protocol that a particular ipPeer does not support.
Defaults by preference:
Note: Ensure that the SIP Sig Port transportProtocolsAllowed setting is configured to support the chosen transport preference (see zone sipSigPort - CLI page).
This example creates a patch check profile named "PCP-1" with the default ping protocol type "sipOptions", a recovery count of "7" and a send interval of "120" seconds. The reply timeout count is left at the default of "6". Next, the PCP is assigned to "defaultSigZone" zone for default address context using IP address "10.20.120.21".
To configure a single
failureResponseCodes value for a Path Check Profile:
To set multiple
To delete a single
To delete all