In this section:

This profile specifies the configuration for OPTIONS PING.

To View and Edit Path Check

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

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


IP Peer - Path Check Edit Window


Parameter Descriptions:

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 the 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 the 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 Path Check task performs SRV lookup to resolve the port numbers. The resolved port numbers are used to send OPTIONS ping to the IP Peer.

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

Note

To use SRV, enable the IPSP flag No Port Number5060.

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:
PeerThe peer restarts.
PeerThe peer is manually blocked.
PeerThe peer's congestion state changes (this update is ignored by the SBC).
SBCThe peer has restarted indicating it is ready to receive calls.
SBCThe peer is manually blocked in the SBC.



Make the required changes and click Save.


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.

IP Peer - Path Check Commands


Parameter Descriptions:

Parameter

Description

Local Admin State

Specifies the local admin state of the peer.

  • Block
  • Unblock 
Remote Admin State

Specifies the remote admin state of the peer.

  • Block
  • Unblock 

 

Select the required command and click Select. From the pop-window, choose your preference for the selected Path Check Command.

IP Peer - Path Check Command pop up window

Select the desired option and click the "Command Name" button to implement the option.

Click OK to exit.

LSWU Behavior

There are three LSWU scenarios when you upgrade the SBC from an older version that does not support DNS SRV path check to a new version that supports DNS SRV path check:

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