In this section:
This profile specifies the configuration for OPTIONS PING.
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.
The Edit Path Check window is displayed.
The following fields are displayed:
Parameter | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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. If | ||||||||||||
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. If When set to When If | ||||||||||||
| Specifies if the active pinging is enabled or not. The options are:
| ||||||||||||
| Enable this flag to provide Options-based status update support. The options are:
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.
|
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
This option provides local admin state and remote admin state for a peer.
The following options are displayed:
Parameter | Description |
---|---|
| Specifies the local admin state of the peer. The options are:
|
remoteAdminState | Specifies the remote admin state of the peer. The options are:
|
Select the required command and click Select. A pop window appears seeking your preference for the selected Path Check Command.
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.
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:
hostPort
is not configured in the older version, after the upgrade, the newer version displays the default value as 5060
.hostPort
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.hostPort
is configured to any other value in older version, after upgrade, the newer version continues to use the same value and SRV is skipped.