In this section:
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 using SIP OPTIONS Ping for additional feature details.
Note
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.
Command Syntax
% set profiles services pathCheckProfile <profile name> failureResponseCodes <400-699 | all |all4xx | all5xx | all6xx> protocol sipOptions recoveryCount <1-10> replyTimeoutCount <1-10> sendInterval <1-600> transportPreference <preference1 | preference2 | preference3 | preference4>
Command Parameters
The Path Check Profile parameters are defined below:
Table : Path Check Profile Parameter
Parameter | Length/Range | Description |
---|---|---|
| 1-23 |
|
| 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:
|
| N/A | The ping protocol type used.
|
| 1-10 | The number of consecutive successful responses to occur before removing the endpoints from the Blacklist. (default = 6) |
| 1-10 | The number of consecutive timeouts to occur before adding the endpoints to the Blacklist. (default = 6) |
| 1-600 | Specifies interval (in seconds) in which the PING request will be sent out to the endpoints. (default = 60) |
transportPreference | N/A | 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. Possible completions:
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). |
Command Examples
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".
% set profiles services pathCheckProfile PCP-1 protocol sipOptions recoveryCount 7 sendInterval 120 % show profiles services pathCheckProfile PCP-1 protocol sipOptions; sendInterval 120; recoveryCount 7; % set addressContext default zone defaultSigZone ipPeer PEER-1 ipAddress 10.20.120.21 pathCheck profile PCP-1 state enabled % show addressContext default zone defaultSigZone ipPeer PEER-1 ipAddress 10.20.120.21; pathCheck { profile PCP-1; state enabled; }
To configure a single failureResponseCodes
value for a Path Check Profile:
% set profiles services pathCheckProfile PCP_1 failureResponseCodes 404
To set multiple failureResponseCodes
values:
% set profiles services pathCheckProfile PCP_1 failureResponseCodes [ 404 503 all6xx ]
To delete a single failureResponseCodes
value:
% delete profiles services pathCheckProfile PCP_1 failureResponseCodes all6xx
To delete all failureResponseCodes
values:
% delete profiles services pathCheckProfile <pathCheckProfile_name> failureResponseCodes []