In this section:

Overview

Use the Monitoring Profile (associated with the signaling port) to configure the monitoring server, filters, header names, and select from the fixed set of information.

Note

The SBC captures encrypted and decrypted signaling packets of SIP over TLS at layer 2. The SIP PDUs (Protocol Data Units) are captured at the application layer and continuously streamed to the monitoring server. Configurable Headers are included in SIP PDUs to enable the monitoring server to decode SIP signaling properly. Headers have source and destination IP address/Port information along with additional information which is configurable – this information is needed by the monitoring server in order to correlate the stream received.

The packet is captured at ingress leg without SMM applied and with SMM applied on egress leg, which is essentially what is being sent on the wire. To lessen performance impact, all socket-management activities to the monitoring server use a separate SIPSM (SIP Signaling Monitor ) process receives all signaling packets from the SIP Signaling Gateway (SIPSG) and streams to the configurable external monitoring server either over UDP or TCP.

SIP Load Balancer (SLB): Enhanced Monitoring Interface

An enhanced monitoring interface on the SIP Load Balancer (SLB) is available on the SBC Cloud-Native Edition (CNe) and SBC SWe. The SLB is enhanced to stream TLS encrypted signaling packets as decrypted signaling packets to a downstream monitoring system.

SBC Cloud-Native Edition (CNe) specific configuration

On the SBC CNe, decrypted signals are sent by the SLB pod using only the PKT port. The MGMT port is not supported by the SBC CNe. As well, the monitoring profile for the SBC CNe only allows the "ip" type. The "mgmt" monitoring profile type is not configurable in the SBC CNe. Lastly, only the "IpInterfaceGroup" interface type is supported by the SBC CNe. The "MgmtInterfaceGroup" interface type is not supported by the SBC CNe.

On the SBC SWe, the enhanced monitoring interface is not affected by the limitations listed in the previous paragraph. 

To View Monitoring Profile

  1. To view the list of Monitoring Profiles, navigate to All > Profiles > Services > Monitoring Profile. The Monitoring Profile window displays the table Monitoring Profile List.

  2. To edit, copy, or delete a Monitoring Profile, select the corresponding row from the table Monitoring Profile List using the radio button at the start of the row.

To Edit Selected Monitoring Profile

  1. To edit a Monitoring Profile, select a profile from the list.

  2. Modify the fields in the Edit Selected Monitoring Profile screen. See the Field Descriptions table below.

  3. Click Save.

To Copy Selected Monitoring Profile

  1. To edit a Monitoring Profile, select a profile from the list.

  2. Click the Copy Monitoring Profile button. The Copy Selected Monitoring Profile screen displays.

  3. Modify the fields in the Copy Selected Monitoring Profile screen. For field descriptions, see this table.
  4. Click Save.

To Create New Monitoring Profile

  1. Click the +New Monitoring Profile button. The Create New Monitoring Profile screen displays.

  2. Enter values for the fields in the Create New Monitoring Profile screen.




    Field Descriptions - Create New Monitoring Profile

    ParameterLength/RangeDescriptionM/O
    Name
    		1-24 charactersEnter the Monitoring Profile name.M
    State
    		N/A

    Choose the Monitoring Profile state.

    • Disabled (default)
    • Enabled
    		O
    Monitoring IP Address
    		IP address formatEnter monitoring server IP address.M
    Monitoring IP Port
    		0-65535Enter the monitoring server IP port.M
    TransportN/A

    Choose the transport protocol used to send packets to the monitoring server.

    • UDP (default)
    • TCP
    Note

    The maximum size of SIP PDUs sent to the monitoring server over UDP protocol is 4096 bytes. SIP PDUs exceeding 4096 bytes will get dropped. Ribbon recommends using the TCP protocol if PDUs of a size greater than 4096 bytes are sent to the monitoring server.

    		O
    TypeN/A

    Use this object to define the interface type to use when sending the monitoring data to the monitoring server.

    • Mgmt (default) – Note that when you choose this object, the Mgmt Interface Group parameter is available to configure.
    • IP – Note that when you choose this object, two additional parameters are available to configure: Address Context and IP Interface Group.
    		O
    Mgmt Interface Group
    		N/AThe name of the Interface Group for the Mgmt IP.O
    Signaling Packets

    N/A

    Use this object to define the types of signaling packets to send to the monitoring server. 

    • All - All signaling packet types are monitored.
    • None (default) - No signaling packets are monitored.
    • TLS - Only decrypted TLS signaling packets are monitored.
    		O
    Header PresenceN/A

    Use this object to specify if the X header presence towards monitoring server is enabled.

    • Disabled (default)
    • Enabled
    		O

    Additional Information

    (This field only displays in the Edit and Copy screens)

    		N/AOptionally add any additional information to send to the monitoring server.O
  3. Click Save.

To Delete Selected Monitoring Profile

  1. To delete a Monitoring Profile, select it from the Monitoring Profile List table, and click the delete icon at the end of the selected row.
  2. Confirm the delete prompt.