AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | IoT | IT Service | Network/System | Infra | Performance | Protocol | SaaS | Security | Service Level | Storage | Linux | VMware | VoIP | Web | Wireless | SNMP

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Stratacom » CISCO-WAN-RTP-CONN-MIB » Objects

CISCO-WAN-RTP-CONN-MIB.mib object view, vendor Stratacom

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CISCO-WAN-RTP-CONN-MIB and use it to monitor vendor specific OID's.

CISCO-WAN-RTP-CONN-MIB file content

Object view of CISCO-WAN-RTP-CONN-MIB:

Scalar Object
vismRtpConnGrpEntry .1.3.6.1.4.1.351.150.20.1.1.1.1
An 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.
vismRtpBearerStatsEntry .1.3.6.1.4.1.351.150.20.1.2.1.1
An entry is implicitly created when a RTP connection is established. All the counters in this table can not be modified by user.
Tabular Object
vismRtpConnNum .1.3.6.1.4.1.351.150.20.1.1.1.1.1
This is the connection number in vismRtpConnGrpTable.
vismRtpEndptNum .1.3.6.1.4.1.351.150.20.1.1.1.1.2
This 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).
vismRtpLocPort .1.3.6.1.4.1.351.150.20.1.1.1.1.3
This 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.
vismRtpRmtIp .1.3.6.1.4.1.351.150.20.1.1.1.1.4
This object determines the remote VISM's IP address. For every RTP connection the remote port and remote IP pair needs to be unique.
vismRtpRmtPort .1.3.6.1.4.1.351.150.20.1.1.1.1.5
This 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.
vismRtpConnMode .1.3.6.1.4.1.351.150.20.1.1.1.1.6
This 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.
vismRtpBearerTos .1.3.6.1.4.1.351.150.20.1.1.1.1.7
This 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.
vismRtpCodecType .1.3.6.1.4.1.351.150.20.1.1.1.1.8
This 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
vismRtpPktPeriod .1.3.6.1.4.1.351.150.20.1.1.1.1.9
This 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
vismRtpVadTimer .1.3.6.1.4.1.351.150.20.1.1.1.1.10
This 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.
vismRtpEcanEnable .1.3.6.1.4.1.351.150.20.1.1.1.1.11
This 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.
vismRtpTriRedundancy .1.3.6.1.4.1.351.150.20.1.1.1.1.12
This 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)'.
vismRtpDtmfTransport .1.3.6.1.4.1.351.150.20.1.1.1.1.13
This attribute defines whether the DTMF (Dual Tone Multi Frequency) digits need to be transported to the other end-point.
vismRtpCasTransport .1.3.6.1.4.1.351.150.20.1.1.1.1.14
This 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)'.
vismRtpVad .1.3.6.1.4.1.351.150.20.1.1.1.1.15
This 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.
vismRtpICSEnable .1.3.6.1.4.1.351.150.20.1.1.1.1.16
This 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.
vismRtpConnAlarmState .1.3.6.1.4.1.351.150.20.1.1.1.1.17
This 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'.
vismRtpRowStatus .1.3.6.1.4.1.351.150.20.1.1.1.1.18
This 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.
vismRtpLcn .1.3.6.1.4.1.351.150.20.1.1.1.1.19
This object is used to indicate the RTP related LCN (Logical channel number). Only the primary PVC (Permanent virtual circuit) is used for this object.
vismRtpFailReason .1.3.6.1.4.1.351.150.20.1.1.1.1.20
This 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.
vismRtpPayloadType .1.3.6.1.4.1.351.150.20.1.1.1.1.21
This 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.
vismRtpPktsSent .1.3.6.1.4.1.351.150.20.1.2.1.1.1
This object shows the number of packets sent to network side.
vismRtpPktsRcv .1.3.6.1.4.1.351.150.20.1.2.1.1.2
This object shows the number of packets received from network side.
vismRtpOctsSent .1.3.6.1.4.1.351.150.20.1.2.1.1.3
This object shows the number of octets sent to network side.
vismRtpOctsRcv .1.3.6.1.4.1.351.150.20.1.2.1.1.4
This object shows the number of octets received from network side.
vismRtpPktsLost .1.3.6.1.4.1.351.150.20.1.2.1.1.5
This object shows the number of RTCP packets lost due to invalid connection mode.
vismRtpCntsCleared .1.3.6.1.4.1.351.150.20.1.2.1.1.6
This object is used to clear all the above objects.
Table
vismRtpConnGrpTable .1.3.6.1.4.1.351.150.20.1.1.1
This 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.
vismRtpBearerStatsTable .1.3.6.1.4.1.351.150.20.1.2.1
This table contain the RTP bearer counters.
Object Identifier
ciscoWanRtpConnMIB .1.3.6.1.4.1.351.150.20
The 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.
ciscoWanRtpConnMIBObjects .1.3.6.1.4.1.351.150.20.1
vismRtpConnGrp .1.3.6.1.4.1.351.150.20.1.1
vismRtpBearerStatsGrp .1.3.6.1.4.1.351.150.20.1.2
vismRtpConnNotificationPrefix .1.3.6.1.4.1.351.150.20.2
vismRtpConnNotifications .1.3.6.1.4.1.351.150.20.2.0
vismRtpConnMIBConformance .1.3.6.1.4.1.351.150.20.3
vismRtpConnMIBCompliances .1.3.6.1.4.1.351.150.20.3.1
vismRtpConnMIBGroups .1.3.6.1.4.1.351.150.20.3.2
Group
vismRtpConnGroup .1.3.6.1.4.1.351.150.20.3.2.1
This group contains objects related to configuration of RTP connections.
vismRtpBearerStatsGroup .1.3.6.1.4.1.351.150.20.3.2.2
This group contains counters for each RTP connection.