CISCO-WAN-RTP-CONN-MIB

MIB Reference — IPNetwork Monitor

All MIBsCISCO-WAN-RTP-CONN-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2005-04-12

Category: Telephony and VoIP, Vendor: Cisco Devices

Description:

Manages Cisco WAN RTP connection configuration for voice-over-IP transport on VISM media gateway cards.

Imported Objects

From CISCOWAN-SMI

ciscoWanOBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TruthValue

What Is CISCO-WAN-RTP-CONN-MIB?

CISCO-WAN-RTP-CONN-MIB is a Cisco-proprietary MIB for VISM media gateway cards, defining RTP (Real-time Transport Protocol) connections that carry voice bearer traffic between VISM endpoints in VoIP trunking applications. It exposes configuration objects for each RTP connection, including local/remote IP addressing and ports, codec type, packetization period, and voice-activity-detection (VAD) timers. Its role in monitoring is chiefly software/configuration-level: confirming a given RTP connection is correctly established end-to-end with the expected codec and QoS/ToS marking, plus (via its bearer stats group) tracking voice bearer traffic health rather than physical hardware status. It works alongside other Cisco WAN VISM MIBs (LAPD trunk, tone plan, announcement) that together implement VISM's VoIP trunking feature set. Locating vismRtpConnGrpTable and the bearer-stats objects under the CISCO-WAN-RTP-CONN-MIB OID tree is a typical first step before it is deployed on Cisco WAN switching platforms (e.g., MGX 8000 series) providing VoIP trunking for carrier telephony networks.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-WAN-RTP-CONN-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.

What Can Be Monitored

  • RTP connection endpoint/IP/port mapping
  • codec type in use per connection
  • bearer ToS/QoS marking
  • RTP bearer statistics (loss/quality indicators)
  • voice-activity-detection timer settings

Supported Devices

  • Cisco WAN switching platforms with VISM cards, e.g. Cisco MGX 8000 series

Monitoring Examples

An administrator would poll vismRtpConnGrpTable/vismRtpConnGrpEntry, indexed by vismRtpConnNum and vismRtpEndptNum, to verify vismRtpRmtIp/vismRtpRmtPort match the intended remote VISM endpoint, and that vismRtpCodecType and vismRtpBearerTos are set as expected for the trunk's QoS policy. The vismRtpBearerStatsGrp objects would be checked for packet loss or jitter symptoms on an active call path. An unexpected vismRtpConnMode or a vismRtpVadTimer misconfiguration could explain choppy audio or unexpected silence suppression on a voice trunk.

OIDs
OID symbolicOID numericTypeAccessDescription
ciscoWanRtpConnMIB1.3.6.1.4.1.351.150.20The MIB module is defined for establishing connection between an endpoint and another endpoint on a remote VISM in the case of VoIP(Voice over IP) trunking application.
ciscoWanRtpConnMIBObjects1.3.6.1.4.1.351.150.20.1
vismRtpConnGrp1.3.6.1.4.1.351.150.20.1.1
vismRtpConnGrpTable1.3.6.1.4.1.351.150.20.1.1.1not-accessibleThis table defines attributes used to set up a static trunked VoIP connection between an endpoint and another endpoint on a remote VISM. The maximum number of RTP connections that can be established is based on the current codec template, which is vismAppliedTemplate(defined in CISCO-VISM-MODULE-MIB MIB) object. Before establishing the connection, endpoints on either VISM's should have been created and the line signaling type needs to be configured.
vismRtpConnGrpEntry1.3.6.1.4.1.351.150.20.1.1.1.1not-accessibleAn entry in the vismRtpConnGrpTable. This table applies to VoIP trunking applications. The configuration is retained after VISM card reboots. vismRtpCodecType, vismRtpPktPeriod, vismRtpBearerTos, vismRtpConnMode, vismRtpVad, vismRtpVadTimer, vismRtpDtmfTransport, vismRtpCasTransport, vismRtpTriRedundancy, and vismRtpICSEnable can be modified after a connection is established. The rest cannot be modified after a connection is created.
I32 vismRtpConnNum1.3.6.1.4.1.351.150.20.1.1.1.1.1Integer32not-accessibleThis is the connection number in vismRtpConnGrpTable.
I32 vismRtpEndptNum1.3.6.1.4.1.351.150.20.1.1.1.1.2Integer32read-createThis object defines the endpoint number to which the RTP connection associated. It is the same as mgEndpointNumber object in mgEndpointTable(defined in CISCO-WAN-MG-MIB MIB).
I32 vismRtpLocPort1.3.6.1.4.1.351.150.20.1.1.1.1.3Integer32read-createThis object determines the static local RTP port (UDP) that this connection is using. Only even numbers are allowed as odd numbers are used for RTCP(Real-time transport control protocol) port. The local RTP port has to be unique as only one connection is allowed per port.
IP vismRtpRmtIp1.3.6.1.4.1.351.150.20.1.1.1.1.4IpAddressread-createThis object determines the remote VISM's IP address. For every RTP connection the remote port and remote IP pair needs to be unique.
I32 vismRtpRmtPort1.3.6.1.4.1.351.150.20.1.1.1.1.5Integer32read-createThis object determines the static remote RTP port (UDP) that this connection is using. Only even numbers are allowed as odd numbers are used for RTCP port. The combination of remote ip and remote port needs to be unique for a connection.
INT vismRtpConnMode1.3.6.1.4.1.351.150.20.1.1.1.1.6INTEGERread-createThis object defines the packet transfer mode on the connection. 'sendOnly' - indicate send packet only. 'rcvOnly' - indicate receive packet only. 'sendAndRcv' - indicate send and receive packet. 'inactive' - indicate it cannot send nor receive any packet.
I32 vismRtpBearerTos1.3.6.1.4.1.351.150.20.1.1.1.1.7Integer32read-createThis object is used to provision the bitmask used for the Type Of Service (TOS) octet for cells carrying VoIP bearer (RTP) traffic. The first 3 bits denotes the precedence while the other bits denotes the TOS. Default value 160 = 0xA0 => Precedence = 5 and TOS nibble = 0. The bitmask can be only a byte value.
INT vismRtpCodecType1.3.6.1.4.1.351.150.20.1.1.1.1.8INTEGERread-createThis object is used to define what codec is used to transport voice packets on a RTP connection. 1 represents G.711u 2 represents G.711a 3 represents G.726 at rate 32 kbps 4 represents G.729a 5 represents G.729ab 6 represents clear channel 7 represents G.726 at rate 16 kbps 8 represents G.726 at rate 24 kbps 9 represents G.726 at rate 40 kbps 10 NOT USED 11 represents G.723.1-H 12 represents G.723.1a-H 13 represents G.723.1-L 14 represents G.723.1a-L 15 represents Lossless
INT vismRtpPktPeriod1.3.6.1.4.1.351.150.20.1.1.1.1.9INTEGERread-createThis object gives the packetization period for a particular codec in milli secs. for G.711a allowed values are 10 & 20 for G.711u allowed values are 10 & 20 for G.726 at rate 32 kbps allowed values are 10 ,20 30 & 40 for G.729a allowed values are 10, 20 ,30 & 40 for G.729ab allowed values are 10, 20, 30 & 40 for clear channel allowed values are 10 and 20 for G.726 at rate 16 kbps allowed values are 10 ,20 30 & 40 for G.726 at rate 24 kbps allowed values are 10 ,20 30 & 40 for G.726 at rate 40 kbps allowed values are 10 ,20 30 & 40 for G.723 family allowed values are 30 & 60. Default is 30. for Lossless allowed values are 10 and 20
I32 vismRtpVadTimer1.3.6.1.4.1.351.150.20.1.1.1.1.10Integer32read-createThis attribute defines the hangover time for VAD (Voice Activity Detection) in milliseconds. Once the voice inactivity is detected, the gateway will wait for this duration before activating silence suppression.
T/F vismRtpEcanEnable1.3.6.1.4.1.351.150.20.1.1.1.1.11TruthValueread-createThis attribute defines whether Echo Cancellation has to be enabled on this connection. If it is set to 'true(1)', echo cancellation is enabled. If it is set to 'false(2)', echo cancellation is disabled.
T/F vismRtpTriRedundancy1.3.6.1.4.1.351.150.20.1.1.1.1.12TruthValueread-createThis object tells whether the packets need to be sent in triplicates or not. If it is set to 'true(1)' the packets will be sent three times else will only be sent once (this is used for reliable links to save bandwidth). This object will override the card level object configuration vismVoIpTripleRedundancy(defined in CISCO-VISM-MODULE-MIB MIB). The default value is 'true(1)' if vismRtpDtmfTransport or vismRtpCasTransport is true, else 'false(2)'.
T/F vismRtpDtmfTransport1.3.6.1.4.1.351.150.20.1.1.1.1.13TruthValueread-createThis attribute defines whether the DTMF (Dual Tone Multi Frequency) digits need to be transported to the other end-point.
T/F vismRtpCasTransport1.3.6.1.4.1.351.150.20.1.1.1.1.14TruthValueread-createThis attribute defines whether the CAS(Channel Associated Signaling) bits need to be transported to the other endpoint. In the case of switching application, the CAS bits are backhauled to the Call Agent through xGCP-CAS protocol. Note that if the line signaling type is CAS the default value is 'true(1)', else the default value is 'false(2)'.
T/F vismRtpVad1.3.6.1.4.1.351.150.20.1.1.1.1.15TruthValueread-createThis attribute defines whether the VAD has to be applied on this channel, upon detection of silence. For algorithms that do not have VAD standards, Cisco-proprietary VAD can be applied and the generic SID (Silence Information Descriptor) packet as specified in I.366.2 standards can be sent to the other end. When the codecType is clearChannel VAD has to be off.
T/F vismRtpICSEnable1.3.6.1.4.1.351.150.20.1.1.1.1.16TruthValueread-createThis attribute is used to enable or disable the ICS(Idle Channel Suppression) for a connection. This can be specified while adding the connection and cannot be modified. When the ICS is enabled the DSP will look for the idle CAS (ABCD bits) pattern specified in ds0IdleCode in dsx0 MIB. If the idle pattern is present the DSP stops generating voice packets towards network side. By default the ds0IdleCode will be zero unless the user has configured it before adding the cid. If the ds0IdleCode is changed after the connection is added it will have no affect unless the card is reset.
INT vismRtpConnAlarmState1.3.6.1.4.1.351.150.20.1.1.1.1.17INTEGERread-onlyThis attribute shows the alarm state of this connection. It is set to 'failed' if the connection is in alarm else will be set to 'active'.
ROW vismRtpRowStatus1.3.6.1.4.1.351.150.20.1.1.1.1.18RowStatusread-createThis object is used to create, modify or delete an entry. An entry can be created using the 'createAndGo' option. Before creating a RTP connection, the endpoint should have already been created. And the line signaling type should have been configured. For creating a RTP connection, vismRtpEndptNum, vismRtpLocPort, vismRtpRmtPort, vismRtpRmtIp and vismRtpCodecType need to be provided. For the other objects the default will be applied. The RowStatus would be set to 'active' by the agent while creating a RTP connection. While deleting a RTP connection the RowStaus will be set to 'destroy'. The RTP connection won't be deleted if there are still call going on the connection.
INT vismRtpLcn1.3.6.1.4.1.351.150.20.1.1.1.1.19INTEGERread-onlyThis object is used to indicate the RTP related LCN (Logical channel number). Only the primary PVC (Permanent virtual circuit) is used for this object.
INT vismRtpFailReason1.3.6.1.4.1.351.150.20.1.1.1.1.20INTEGERread-onlyThis object is used to indicate the RTP failure reason. 'self' : fail because of non-PVC alarm. 'highLevel' : fail because of PVC alarm. 'both' : fail because of both PVC and non-PVC alarm. 'notFail' : no failure.
I32 vismRtpPayloadType1.3.6.1.4.1.351.150.20.1.1.1.1.21Integer32read-createThis object specifies the payload type to be used, when adding connection(s) in VoIP Trunking. IANA (Internet assigned number Authority) values (0..95) are static payload and (96..127) are dynamic payload type. The values (128..255) are define here to accomodate any future extension, also 256 is chosen as a default value to avoid payload conflict bewteen gateways. The value of 256 indicate the DSP should use a assigned payload value for the codec.
vismRtpBearerStatsGrp1.3.6.1.4.1.351.150.20.1.2
vismRtpBearerStatsTable1.3.6.1.4.1.351.150.20.1.2.1not-accessibleThis table contains the RTP bearer statistics.
vismRtpBearerStatsEntry1.3.6.1.4.1.351.150.20.1.2.1.1not-accessibleAn entry is implicitly created when a RTP connection is established. All the statistics in this table can not be modified by user.
C32 vismRtpPktsSent1.3.6.1.4.1.351.150.20.1.2.1.1.1Counter32read-onlyThis object shows the number of packets sent to network side.
C32 vismRtpPktsRcv1.3.6.1.4.1.351.150.20.1.2.1.1.2Counter32read-onlyThis object shows the number of packets received from network side.
C32 vismRtpOctsSent1.3.6.1.4.1.351.150.20.1.2.1.1.3Counter32read-onlyThis object shows the number of octets sent to network side.
C32 vismRtpOctsRcv1.3.6.1.4.1.351.150.20.1.2.1.1.4Counter32read-onlyThis object shows the number of octets received from network side.
C32 vismRtpPktsLost1.3.6.1.4.1.351.150.20.1.2.1.1.5Counter32read-onlyThis object shows the number of RTCP packets lost due to invalid connection mode.
T/F vismRtpCntsCleared1.3.6.1.4.1.351.150.20.1.2.1.1.6TruthValueread-writeThis object is used to clear all the above objects.
U32 vismRtpInterArrivalJitter1.3.6.1.4.1.351.150.20.1.2.1.1.7Unsigned32read-onlyThis object provides the average interarrival jitter value between packets during a VoIP call.
U32 vismRtpLatency1.3.6.1.4.1.351.150.20.1.2.1.1.8Unsigned32read-onlyThe round trip delay for a voice packet to travel from the originating end of a VoIP call to the terminating end and back.
vismRtpConnNotificationPrefix1.3.6.1.4.1.351.150.20.2
vismRtpConnNotifications1.3.6.1.4.1.351.150.20.2.0
vismRtpConnMIBConformance1.3.6.1.4.1.351.150.20.3
vismRtpConnMIBCompliances1.3.6.1.4.1.351.150.20.3.1
vismRtpConnMIBCompliance1.3.6.1.4.1.351.150.20.3.1.1The complaince statement for RTP connection group which implements vismRtpConnGrp MIB.
vismRtpConnMIBComplianceRev11.3.6.1.4.1.351.150.20.3.1.2The complaince statement for RTP connection group which implements vismRtpConnGrp MIB.
vismRtpConnMIBGroups1.3.6.1.4.1.351.150.20.3.2
vismRtpConnGroup1.3.6.1.4.1.351.150.20.3.2.1This group contains objects related to configuration of RTP connections.
vismRtpBearerStatsGroup1.3.6.1.4.1.351.150.20.3.2.2This group contains counters for each RTP connection.
vismRtpBearerStatsGroupSup11.3.6.1.4.1.351.150.20.3.2.3This group is a supplement for vismRtpBearerStatsGroup and contains statistics for each RTP connection.

RFC description

Cisco WAN MIB for managing Real-time Transport Protocol (RTP) connection parameters and statistics in Cisco WAN environments.

Start monitoring Cisco MGX 8000 series with VISM cards (legacy) 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 CISCO-WAN-RTP-CONN-MIB