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.

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
AUTH1UserResourceIdentifier{userKey=2c909b309109945b01912fd89e540006, userName='null'}
JIRAIDAUTHSBX-133947
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=2c909b309109945b01912fd89e540006, userName='null'}
REV1UserResourceIdentifier{userKey=2c909b309109945b01912fd89e540006, userName='null'}


Panel

In this section:

Table of Contents


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

Info
titleNote

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.

To View Monitoring Profile

  1. To view the list of Monitoring Profiles, navigate to All > Profiles > Services > Monitoring Profile. The Monitoring Profile window displays, containing 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. For field descriptions, see this table.

  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.


    Anchor
    Field Descriptions - Create New Monitoring Profile
    Field Descriptions - Create New Monitoring Profile


    Table 1: Field Descriptions - Create New Monitoring Profile

    ParameterLength/RangeDefaultDescriptionM/O
    Name
    		1-24 charactersN/AThe name of the Monitoring Profile.M
    State
    		N/ADisabled

    Specifies the state of the Monitoring Profile.

    • Disabled (default)
    • Enabled
    		O
    Monitoring IP Address
    		N/AN/AIP address and port of the monitoring server.M
    Monitoring IP Port
    		0 - 65535N/APort of the monitoring server.M
    TransportN/AUDP

    Transport protocol used to send packets to the monitoring server.

    • UDP (default)
    • TCP
    Info
    titleNote

    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/AMgmt
    Interface type supported by

    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/AN/AThe name of the Interface Group for the Mgmt IP.O
    Signaling Packets

    N/A

    		None

    Adds VLAN ID of the interface on which the monitored message is sent/received.

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

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

    Specifies if X header presence towards monitoring server is enabled or not.

    • Disabled (default)
    • Enabled
    		O

    Additional Information

    (displays only in edit and copy screens)

    		N/AN/AAny additional information to be sent 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.