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:
| TLS | Transport Layer Security |
|---|---|
| SIP | Session Initiation Protocol |
| UNI | User Network Interface |
| NNI | Network-Network Interface |
| TCP | Transmission Control Protocol |
Command Syntax
The command syntax to configure a Monitoring Profile is shown here:
%set profiles services monitoringProfile <monitoring profile name>
additionalInformation <string>
filter <transport | trunkgroup>
headerPresence <disabled | enabled>
mgmtInterfaceGroup <ip | mgmtGroup>
monitoringIpAddress (IP address>
monitoringIpPort <int | 0 .. 65535>
signalingPackets <all | none | tls>
state <disabled | enabled>
transport <tcp | udp>
type <IP | mgmt>
Command Parameters
Command Parameters for monitoringProfile
| Parameter | Length/Range | Description | M/O |
|---|---|---|---|
additionalInformation | string: 256 characters | Additional information in the header to send towards the monitoring server. This parameter is available when | O |
| N/A | This table contains filters for the profile. The
| O |
| N/A | Specifies if X header presence towards monitoring server is enabled or not.
| O |
| N/A | The Management Interface Group to use for communicating with monitoring server.
| O |
| <IP address format> | IP address of the monitoring server. | M |
| 0-65535 | TCP/UDP port for the monitoring server. | M |
monitoringProfile | 1-23 characters | The name of the Monitoring Profile. | M |
| N/A | Specifies if all signaling packets, or only decrypted TLS packets, are sent towards monitoring server from all TGs. | O |
| N/A | Administrative state of this Monitoring Profile.
| |
| N/A | Choose the transport protocol to use for sending packets to the monitoring server.
| O |
| N/A | Interface type supported by monitoring server.
| 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
Command Parameters
Command Parameters for monitoringProfile
| Parameter | Length/Range | Default | Description | M/O |
|---|---|---|---|---|
monitoringProfileName | 24 | Name of Monitoring Profile used for this SIP Signaling Port. | O |
Overview
Content Tools