Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

 

Use the Node Status window to view the current state of SBC SWe Cloud nodes in an OpenStack cloud environment. The status summary also shows the current configuration settings for handling existing calls if the node is taken out of service. Refer to Global - System for more information on configuring those options. The Node Status window is only available on SBC SWe systems in an OpenStack cloud systemsenvironment.

From the SBC main screen, go to All > Global > System > Node Status.  The Node Status window opens.

Caption
0Figure
1Node Status (Global) Window

The following output appears for SBC SWe Cloud nodes in an OpenStack cloud environment.

Caption
0Table
1Node Status Parameters
ParameterDescription
NodeName of the SBC SWe cloud node.
State

State of the named SBC SWe cloud node. The options are:

  • In Service - The SBC accepts new calls and refreshes existing calls in accordance with standard SBC functionality.
  • Out of Service - The SBC rejects any new calls, registrations, or subscriptions. Existing calls are dealt with in accordance with the settings for the Action and Dry Up Timeout parameters.
ActionSpecifies how the SBC handles existing calls when the Mode is set to Out of Service. The following options are available:
  • Dry up - The SBC enters an "Out Of Service Pending" state and rejects any new calls. For existing calls, a timer is started and only terminated after the timer expires. The duration of that timer is determined by the Dry Up Timeout parameter.  During the dry up period, messages involved in the maintenance of existing call legs such as Re-INVITEs or UPDATEs are allowed. Out-of-session messages are rejected. Once all the existing calls/registrations/subscriptions are terminated or cleared, or the Dry Up Timeout value expires (whichever happens first), the SBC enters the Out of Service state.
  • Force - The SBC immediately enters the Out of Service state. Any existing calls are terminated immediately and the Dry Up Timeout parameter does not apply.
 
Dry Up Timeout Specifies the time interval (in minutes) the SBC allows for existing calls to complete before the SBC transitions fully to the Out Of Service state. The supported range is 15 minutes to 1440 minutes (1 day).

Info
titleNote:

The feature that facilitates a period of time to "dry up" existing calls on a node before the node is taken out of service fully is not available on M-SBC nodes.