In this section:

The SBC, which continuously captures encrypted signaling packets of SIP over TLS at layer 2, has been enhanced to to capture decrypted signaling packets as well.

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.

A profile attached to the signaling port is a trigger for this feature. All feature-related configuration can be set in this profile.

Terminology

The following terminology and acronyms are used in this documentation:

TLSTransport Layer Security
 SIPSession Initiation Protocol
 UNIUser Network Interface 
 NNINetwork-Network Interface 
 TCPTransmission Control Protocol


Command Syntax

The command syntax to configure a Monitoring Profile is shown here:

%set profiles services monitoringProfile <monitoring profile name> 
    additionalInformation
    filter <transport | trunkgroup>
    header
    headerPresence <disabled | enabled>
    mgmtInterfaceGroup <ip | mgmtGroup>
    monitoringIpAddress
    monitoringIpPort <int | 0 .. 65535>
    signalingPackets
    state <disabled | enabled>
    transport <tcp | udp>
    type <IP | mgmt>


Command Parameters


Command Parameters for monitoringProfile

ParameterLength/RangeDefaultDescriptionM/O

additionalInformation

256

Additional information in the header sent towards the monitoring server.

O

date



Date in YYYY-MM-DDThh:mm:ss+offset format.

O

destinationIpPort



Destination Ip/Port of the SIP PDU.


displayLevel

Depth to show.

  • unsignedLong –
  • 1 .. 64 –
 O

filter



This table contains filters for the profile. Filter is displayed only when no signalingPackets are selected.

  • transport – Transport type used to filter the packets
  • trunkgroup – IP TG filter used to filter the packets.
O

header



Identifies headers which need to be encapsulated with SIP PDUs.


headerName



Specifies name of the header sent towards the monitoring server.


headerPresence


disabled

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

  • disabled
  • enabled
O

mgmtInterfaceGroup


mgmtGroup

The Management Interface Group to use for communicating with monitoring server.

O

monitoringIpAddress



IP address of the monitoring server.

M

monitoringIpPort



TCP/UDP port for the monitoring server.

  • int –
  • 0 .. 65535
M
monitoringProfileName24
Name of Monitoring Profile used for this SIP Signaling Port.O

signalingPackets



Specifies if all signaling packets, or only decrypted TLS packets, are sent towards monitoring server from all TGs.

O

sourceIpPort



Source Ip/Port of the SIP PDU.


state


disabled

Administrative state of this Monitoring Profile.

  • disabled
  • enabled

timeStamp



Timestamp as seconds.microseconds since 1.1.1970 UTC.

O

transport


udp

Select the transport type for the monitoring server.

  • tcp – Transmission Control Protocol
  • udp – User Datagram Protocol
O

type


mgmt

Interface type supported by monitoring server. 

    • ip – When selected, two fields are suppoorted: addressContext and ipInterfaceGroup.
    • mgmtGroup – When selected, mgmtInterfaceGroup is supported.
O
vlanTag
disabled

Adds VLAN ID of the interface on which the monitored message is sent/received. When this parameter is enabled, the "vlanTag" field of the LIFs on which the SIP message are received/sent, is added to X-header. The enhancement helps in better segregation of signaling traffic.

  • disabled (default)
  • enabled
O

 


The command syntax to set a Monitoring Profile Name per SigPort is shown here:

Example
% set addressContext <address_context> zone <zone_name> sipSigPort 1 monitoringProfileName <monitoring_profile_name>

In general, you can configure monitoringProfile as shown below:

% set profiles services monitoringProfile test_monitoring_profile monitoringIpAddress 10.54.21.25 monitoringIpPort 80 headerPresence enabled header 1 headerName To sourceIpPort enabled destinationIpPort enabled additionalInformation enabled date enabled timestamp enabled vlanTag enabled


294013471


Command Parameters for monitoringProfile

ParameterLength/RangeDefaultDescriptionM/O
monitoringProfileName24
Name of Monitoring Profile used for this SIP Signaling Port.O