In this section:

This profile specifies the configuration for OPTIONS PING.

To View and Edit Path Check

On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > IP Peer > Path Check. The Path Check window is displayed.

The Path Check can be checked for each Address Context, for each Zone, for each IP Peer created or for all the Address Contexts, Zones and IP Peers created. Use the drop-down box to select the desired Address Context, Zone and IP Peer.

Figure 1: IP Peer - Path Check Main Fields

The Edit Path Check window is displayed.

Figure 2: IP Peer - Path Check Edit Window

The following fields are displayed:

Table 1: IP Peer - Path Check

Parameter

Description

Profile

Specifies the path check profile name used for OPTIONS ping.

Host Name

Specifies the FQDN value of the peer. It will be resolved using DNS and the resulting servers will be pinged using SIP OPTIONS requests. The value ranges up to 63 characters.

Note

If  IP Address is configured and Path Check needs to be enabled for that IP Address, ensure Host Name is not configured.

Host Port

Specifies the TCP/UDP port number of the peer. The peer's servers will be pinged using SIP OPTIONS requests at this port. The value ranges from 0 to 65535 and the default value is 5060.

Note

If IP Port is configured and Path Check needs to be enabled for that IP Port, ensure Host Port is not configured.

When set to 0, the pathCheck task performs SRV lookup to resolve the port numbers. The resolved port numbers are used to send OPTIONS ping to the IP Peer.

When hostPort is set to value other than the value 0, the pathCheck task does not perform SRV lookup. It uses the configured port to send OPTIONS ping to the IP Peer.

Note

If Host Port is set to 0, the SBC supports SRV.

State

Specifies if the active pinging is enabled or not. The options are:

  • disabled (default)
  •  enabled

Status Update
Support

Enable this flag to provide OPTIONS-based status update support. The options are:

  • disabled (default) - The SBC does not include Allow and Accept headers while generating OPTIONS ping request towards the peer.
  • The SBC includes Allow and Accept headers while generating OPTIONS ping request towards the peer.
Note

Status Updates only apply when new calls are sent to a peer. They do not impact messages belonging to existing calls or new calls received from the peer.

Status Update is Seen By:When:
PeerPeer restarts
PeerPeer is manually blocked
PeerPeer's congestion state changes (this update is ignored by SBC)
SBCPeer has restarted indicating it is ready to receive calls
SBCPeer is manually blocked in SBC.



Make the required changes and click Save at the right hand bottom of the panel to save the changes made.


Note

Ribbon 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. 


Path Check Commands

This option provides local admin state and remote admin state for a peer.

Figure 3: IP Peer - Path Check Commands

The following options are displayed:

Table 2: IP Peer - Path Check Commands Parameters

Parameter

Description

Local Admin State

Specifies the local admin state of the peer. The options are:

  • block
  • unblock 
Remote Admin State

Specifies the remote admin state of the peer. The options are:

  • block
  • unblock 

 

Select the required command and click Select. A pop window appears seeking your preference for the selected Path Check Command.

Figure 4: IP Peer - Path Check Command pop up window

Select the desired option and click the "Command Name" button to implement the option. The result of the action is displayed.

Click OK to exit.

LSWU Behavior

There are following three LSWU scenarios when SBC is upgraded from an older version which does not support DNS SRV pathCheck to a new version which supports DNS SRV pathCheck:

  • When Host Port is not configured in the older version, after the upgrade, the newer version displays the default value as 5060.
  • When Host Port is configured as 0 in the older version (default value in the older version), after upgrade, the newer version continues to use the same value (0) and SRV query is invoked.
  • When Host Port is configured to any other value in older version, after upgrade, the newer version continues to use the same value and SRV is skipped.