...
| Caption |
|---|
| 0 | 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 05060. | 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 pathChecktask does not perform SRV lookup. It uses the configured port to send OPTIONS ping to the IP peer.| Note |
|---|
If hostPort is set to 0, SBC supports SRV, |
| State
| Specifies if the active pinging is enabled or not. The options are: enableddisabled (default)
| Status Update
Support
| Enable this flag to provide Options-based status update support. The options are: enableddisabled (default)
| 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: |
|---|
| Peer | Peer restarts | | Peer | Peer is manually blocked | | Peer | Peer's congestion state changes (this update is ignored by SBC) | | SBC | Peer has restarted indicating it is ready to receive calls | | SBC | Peer is manually blocked in SBC. |
|
|
...
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
hostPort is not configured in the older version, after the upgrade, the newer version displays the default value as 5060. - When
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. - When
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.