SALIX-RTP-MIB

All MIBs › SALIX-RTP-MIB

Organization: SALIX Technologies

Last Updated: 1998-10-13

Category: SALIX Technologies Media Gateway, SIP and VoIP Protocol, VoIP and Media Gateway

Description: Monitors SALIX Technologies RTP stream statistics including packet loss, jitter, and delay.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is SALIX-RTP-MIB?

The SALIX-RTP-MIB is a vendor-specific SNMP module from SALIX Technologies, a VoIP/media gateway vendor, used to describe and monitor Real-time Transport Protocol (RTP) sessions on its devices. It exposes objects covering active RTP session state and associated quality metrics such as packet loss, jitter, and delay for voice/media streams. From a monitoring standpoint this MIB is focused on real-time software/service health rather than chassis hardware - it lets an operator track the operational quality and status of ongoing media sessions carried by the device, which is a proxy for the health of the voice/media processing software. The MIB includes its own conformance/compliance objects alongside the runtime session objects, and it implicitly builds on the standard RTP/RTCP protocol concepts defined by IETF RFC 3550. It is typically deployed on SALIX media gateways or VoIP session border elements in carrier or enterprise voice networks, where SALIX-RTP-MIB SNMP monitoring provides real-time call quality assurance.

IPNetwork Monitor allows you to monitor SNMP objects defined in SALIX-RTP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

SALIX Technologies VoIP/media gateway
RTP-capable voice/media processing device

Monitoring Examples

An administrator would poll the RTP session table (indexed per active session) to retrieve per-call jitter, packet loss, and delay values, correlating spikes in loss or jitter with reported call quality degradation. The salixRtpGroups and salixRtpCompliances objects are conformance definitions used by agent implementers rather than live data, so they would not be polled for monitoring. A sudden increase in RTP packet loss across many sessions on the same interface could indicate upstream network congestion or a failing physical link.

What Can Be Monitored

RTP session count/status
packet loss per session
jitter per session
delay per session
media stream quality

Imported Objects

From RFC1213-MIB

DisplayString

From SALIX-MIB

platform1

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
salixRtpMIB	1.3.6.1.4.1.2158.5.1.1			The SALIX-RTP-MIB containts objects for describing RTP Sessions.
salixRtpMIBObjects	1.3.6.1.4.1.2158.5.1.1.1
salixRtpStatsTable	1.3.6.1.4.1.2158.5.1.1.1.1		not-accessible	Table to hold statistics on RTP sessions. For each active RTP Session, there will be one entry in the table. NOTE: Retrieval of RTP statistics is an expensive operation. Please use with care.
salixRtpStatsEntry	1.3.6.1.4.1.2158.5.1.1.1.1.1		not-accessible	This entry lists statistics on a given RTP session. The session is uniqely identified by the source Ip Address and port, along with the destination Ip Address and UDP Port.
IP salixRtpStatsSrcIpAddress	1.3.6.1.4.1.2158.5.1.1.1.1.1.1	IpAddress	not-accessible	The Ip Address for the source side of the RTP session. Along with the source UDP Port, these objects identify the RTP session on the source side. Complete identification of the RTP session also requires a unique identification on the destination side
INT salixRtpStatsSrcPort	1.3.6.1.4.1.2158.5.1.1.1.1.1.2	INTEGER	not-accessible	The UDP Port for the source side of the RTP session. Along with the source Ip Address, these objects identify the RTP session on the source side. Complete identification of the RTP session also requires a unique identification on the destination side
IP salixRtpStatsDestIpAddress	1.3.6.1.4.1.2158.5.1.1.1.1.1.3	IpAddress	not-accessible	The Ip Address for the destination side of the RTP session. Along with the destination UDP Port, these objects identify the RTP session on the destination side. Complete identification of the RTP session also requires a unique identification on the source side
INT salixRtpStatsDestPort	1.3.6.1.4.1.2158.5.1.1.1.1.1.4	INTEGER	not-accessible	The UDP Port for the destination side of the RTP session. Along with the destination Ip Address, these objects identify the RTP session on the destination side. Complete identification of the RTP session also requires a unique identification on the source side
C32 salixRtpStatsPktsSent	1.3.6.1.4.1.2158.5.1.1.1.1.1.5	Counter32	read-only	The total number of RTP packets sent during the specified session
C32 salixRtpStatsPktsRecv	1.3.6.1.4.1.2158.5.1.1.1.1.1.6	Counter32	read-only	The total number of RTP packets recieved during the specified session
C32 salixRtpStatsPktsDropped	1.3.6.1.4.1.2158.5.1.1.1.1.1.7	Counter32	read-only	The total number of RTP packets dropped during the specified session
C32 salixRtpStatsBytesSent	1.3.6.1.4.1.2158.5.1.1.1.1.1.8	Counter32	read-only	The total number of bytes sent during the specified session
C32 salixRtpStatsBytesRecv	1.3.6.1.4.1.2158.5.1.1.1.1.1.9	Counter32	read-only	The total number of bytes received during the specified session
C32 salixRtpStatsBytesDropped	1.3.6.1.4.1.2158.5.1.1.1.1.1.10	Counter32	read-only	The total number of bytes dropped during the specified session
C32 salixRtpStatsSignalPktsSent	1.3.6.1.4.1.2158.5.1.1.1.1.1.11	Counter32	read-only	The number of signalling packets sent for the RTP session
C32 salixRtpStatsSignalPktsRecv	1.3.6.1.4.1.2158.5.1.1.1.1.1.12	Counter32	read-only	The number of signalling packets received for the RTP session
C32 salixRtpStatsSignalPktsDropped	1.3.6.1.4.1.2158.5.1.1.1.1.1.13	Counter32	read-only	The number of signalling packets dropped for the RTP session
C32 salixRtpStatsSignalBytesRecv	1.3.6.1.4.1.2158.5.1.1.1.1.1.14	Counter32	read-only	The number of signalling bytes received for the RTP session
C32 salixRtpStatsAudioPktsRecv	1.3.6.1.4.1.2158.5.1.1.1.1.1.15	Counter32	read-only	The number of audio packets received for the specified RTP session
C32 salixRtpStatsAudioBytesRecv	1.3.6.1.4.1.2158.5.1.1.1.1.1.16	Counter32	read-only	The number of audio bytes received for the specified RTP session
I32 salixRtpStatsEstimatedAvgLatency	1.3.6.1.4.1.2158.5.1.1.1.1.1.17	Integer32	read-only	The Estimated Average Latency for the RTP session
salixRtpMIBTraps	1.3.6.1.4.1.2158.5.1.1.2
salixRtpMIBTrapPrefix	1.3.6.1.4.1.2158.5.1.1.2.0
salixRtpMIBCompliance	1.3.6.1.4.1.2158.5.1.1.3
salixRtpGroups	1.3.6.1.4.1.2158.5.1.1.3.1
salixRtpGroup	1.3.6.1.4.1.2158.5.1.1.3.1.3			Stats Statistics for Rtp Sessions
salixRtpCompliances	1.3.6.1.4.1.2158.5.1.1.3.2
salixRtpCompliance	1.3.6.1.4.1.2158.5.1.1.3.2.1			The basic implementation requirements for the SALIX-RTP-MIB.

RFC description

Vendor-private SALIX Technologies MIB for managing RTP (Real-Time Transport Protocol) in their network products.

Start monitoring SALIX Technologies VoIP/media gateway, RTP-capable voice/media processing device (session quality) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SALIX-RTP-MIB

What Is SALIX-RTP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description