This attribute defines the RTCP report interval (
defined in RFC 1889). This indicates the interval at which
the RTCP reports should be sent to the participating members. The
value is expressed in units of milliseconds. The RTCP reports are not
sent at a fixed rate at this interval. Rather, this value is used as
a base value to arrive at a random number between 0.5 and 1.5 times
this value.
This interval timer also serves the purpose of RTP packets receive
timer. At every 'vismRtcpRecvMultiplier' times this interval, where
'vismRtcpRecvMultiplier'is specified in the MIB object below, a check
is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP
modes) to see if any RTP packets have been received. If not,
gateway-initiated DLCX should be sent to the Call Agent.
Currently, this interval timer is a card-specific value, which means
the value is configurable on a per card basis and not on a per call
basis.
This value is applicable for VoIP adaptation only.
From vism 2.0.3 release onwards this object can be configured in any
mode/adaptations, but will be applicable only in voip adaptation.
Parsed from file CISCO-WAN-AXIPOP-MIB.mib
Module: CISCO-WAN-AXIPOP-MIB
This attribute defines the RTCP(Real-time Transport
Control Protocol) report interval (defined in RFC
1889). This indicates the interval at which the RTCP
reports should be sent to the participating members.
The RTCP reports are not sent at a fixed rate at this
interval. Rather, this value is used as a base value
to arrive at a random number between 0.5 and 1.5 times
this value.
This interval timer also serves the purpose of RTP
packets receive timer. At every vismRtcpRecvMultiplier
times this interval, where vismRtcpRecvMultiplier
is specified in the MIB object below, a check is made
on a VoIP connection (which is in SENDRECV or RECVONLY
xGCP modes) to see if any RTP packets have been
received. If not, gateway-initiated DLCX should be
sent to the Call Agent.
Currently, this interval timer is a card-specific
value, which means the value is configurable on a per
card basis and not on a per call basis.
This value is applicable for VoIP adaptation only.
This attribute defines the RTCP(Real-time Transport
Control Protocol) report interval (defined in RFC
1889). This indicates the interval at which the RTCP
reports should be sent to the participating members.
The RTCP reports are not sent at a fixed rate at this
interval. Rather, this value is used as a base value
to arrive at a random number between 0.5 and 1.5 times
this value.
This interval timer also serves the purpose of RTP
packets receive timer. At every vismRtcpRecvMultiplier
times this interval, where vismRtcpRecvMultiplier
is specified in the MIB object below, a check is made
on a VoIP connection (which is in SENDRECV or RECVONLY
xGCP modes) to see if any RTP packets have been
received. If not, gateway-initiated DLCX should be
sent to the Call Agent.
Currently, this interval timer is a card-specific
value, which means the value is configurable on a per
card basis and not on a per call basis.
This value is applicable for VoIP adaptation only.
Parsed from file CISCO-VISM-MODULE-MIB.my.txt
Company: None
Module: CISCO-VISM-MODULE-MIB
This attribute defines the RTCP(Real-time Transport
Control Protocol) report interval (defined in RFC
1889). This indicates the interval at which the RTCP
reports should be sent to the participating members.
The RTCP reports are not sent at a fixed rate at this
interval. Rather, this value is used as a base value
to arrive at a random number between 0.5 and 1.5 times
this value.
This interval timer also serves the purpose of RTP
packets receive timer. At every vismRtcpRecvMultiplier
times this interval, where vismRtcpRecvMultiplier
is specified in the MIB object below, a check is made
on a VoIP connection (which is in SENDRECV or RECVONLY
xGCP modes) to see if any RTP packets have been
received. If not, gateway-initiated DLCX should be
sent to the Call Agent.
Currently, this interval timer is a card-specific
value, which means the value is configurable on a per
card basis and not on a per call basis.
This value is applicable for VoIP adaptation only.
vismRtcpRepInterval OBJECT-TYPE SYNTAX INTEGER (500..15000) ACCESS read-write STATUS mandatory DESCRIPTION " This attribute defines the RTCP report interval ( defined in RFC 1889). This indicates the interval at which the RTCP reports should be sent to the participating members. The value is expressed in units of milliseconds. The RTCP reports are not sent at a fixed rate at this interval. Rather, this value is used as a base value to arrive at a random number between 0.5 and 1.5 times this value. This interval timer also serves the purpose of RTP packets receive timer. At every 'vismRtcpRecvMultiplier' times this interval, where 'vismRtcpRecvMultiplier'is specified in the MIB object below, a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. Currently, this interval timer is a card-specific value, which means the value is configurable on a per card basis and not on a per call basis. This value is applicable for VoIP adaptation only. From vism 2.0.3 release onwards this object can be configured in any mode/adaptations, but will be applicable only in voip adaptation. " DEFVAL {5000} ::= { vismVoIpGrp 2 }
vismRtcpRepInterval OBJECT-TYPE SYNTAX INTEGER(500..15000) ACCESS read-write STATUS mandatory DESCRIPTION "This attribute defines the RTCP(Real-time Transport Control Protocol) report interval (defined in RFC 1889). This indicates the interval at which the RTCP reports should be sent to the participating members. The RTCP reports are not sent at a fixed rate at this interval. Rather, this value is used as a base value to arrive at a random number between 0.5 and 1.5 times this value. This interval timer also serves the purpose of RTP packets receive timer. At every vismRtcpRecvMultiplier times this interval, where vismRtcpRecvMultiplier is specified in the MIB object below, a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. Currently, this interval timer is a card-specific value, which means the value is configurable on a per card basis and not on a per call basis. This value is applicable for VoIP adaptation only." DEFVAL { 5000 } ::= { vismVoIpGrp 2 }
Vendor: Stratacom
Module: CISCO-VISM-MODULE-MIB
[Automatically extracted from oidview.com]
vismRtcpRepInterval OBJECT-TYPE SYNTAX Integer32 (500..15000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute defines the RTCP(Real-time Transport Control Protocol) report interval (defined in RFC 1889). This indicates the interval at which the RTCP reports should be sent to the participating members. The RTCP reports are not sent at a fixed rate at this interval. Rather, this value is used as a base value to arrive at a random number between 0.5 and 1.5 times this value. This interval timer also serves the purpose of RTP packets receive timer. At every vismRtcpRecvMultiplier times this interval, where vismRtcpRecvMultiplier is specified in the MIB object below, a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. Currently, this interval timer is a card-specific value, which means the value is configurable on a per card basis and not on a per call basis. This value is applicable for VoIP adaptation only. " DEFVAL { 5000 } ::= { vismVoIpGrp 2 }
vismRtcpRepInterval OBJECT-TYPE SYNTAX Integer32 (500..15000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute defines the RTCP(Real-time Transport Control Protocol) report interval (defined in RFC 1889). This indicates the interval at which the RTCP reports should be sent to the participating members. The RTCP reports are not sent at a fixed rate at this interval. Rather, this value is used as a base value to arrive at a random number between 0.5 and 1.5 times this value. This interval timer also serves the purpose of RTP packets receive timer. At every vismRtcpRecvMultiplier times this interval, where vismRtcpRecvMultiplier is specified in the MIB object below, a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. Currently, this interval timer is a card-specific value, which means the value is configurable on a per card basis and not on a per call basis. This value is applicable for VoIP adaptation only. " DEFVAL { 5000 } ::= { vismVoIpGrp 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.3.17.2.2.0 | vismRtcpRepInterval | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.3.17.2.1 | vismBearerTos | 1 | 1 | This object is used to provision the bitmask used for the TOS (Type Of Service) octet for cells carrying VoIP bearer (RTP ) traff… |
| 1.3.6.1.4.1.351.110.3.17.2.3 | vismRtpReceiveTimer | 1 | 1 | This object defines whether the RTP packets receive timer on the VISM needs to be enabled or not. For some VoIP applications if a… |
| 1.3.6.1.4.1.351.110.3.17.2.4 | vismPacketizationPeriod | 1 | 1 | This object is used to provision the packetization period to be applied and is applicable for VoIP only. For VoAAL2 adaptations, … |
| 1.3.6.1.4.1.351.110.3.17.2.5 | vismVoIpDtmfRelay | 1 | 1 | This attribute defines whether the DTMF (Dual Tone Multi-Frequency) digits need to be transported to the other endpoint via NSE(Na… |
| 1.3.6.1.4.1.351.110.3.17.2.6 | vismVoIpCasTransport | 1 | 1 | This attribute defines whether the CAS(Channel Associated Signaling) bits need to be transported to the other endpoint via NSE pa… |
| 1.3.6.1.4.1.351.110.3.17.2.7 | vismVoIpTripleRedundancy | 1 | 1 | This attribute defines whether triple redundancy is enabled or not. With triple redundancy, NSEs are sent three times at 20 ms in… |
| 1.3.6.1.4.1.351.110.3.17.2.8 | vismVoIpVADTimer | 1 | 1 | This attribute defines the hangover time for VAD(Voice Activity Detection) in milliseconds. Once the voice inactivity is detected… |
| 1.3.6.1.4.1.351.110.3.17.2.9 | vismVoIpNTECapabilityNegotiate | 1 | 1 | This attribute defines whether the VISM has the capability to negotiate the list of events either NSE or NTE(Named Telephony Even… |
| 1.3.6.1.4.1.351.110.3.17.2.10 | vismVoIpSIDPayloadType | 1 | 1 | This attribute sets the payload type of a RTP packet carrying SID(Silence Insertion Descriptor) which is sent to the other end wh… |
| 1.3.6.1.4.1.351.110.3.17.2.11 | vismVoIpDPvcOamCellGap | 1 | 1 | This attribute defines the inter cell gap for dual PVC OAM cells. The value represents the time in milliseconds. |
| 1.3.6.1.4.1.351.110.3.17.2.12 | vismVoIpDPvcRetryCnt | 1 | 1 | This attribute defines the threshold for failure of a PVC. If the number of consecutive OAM cells sent for which no ack was rece… |
| 1.3.6.1.4.1.351.110.3.17.2.13 | vismVoIpDPvcRecoverCnt | 1 | 1 | This attribute defines the threshold for recovery of a PVC. If the number of consecutive OAM cells sent for which ack was receiv… |
| 1.3.6.1.4.1.351.110.3.17.2.14 | vismRtcpRecvMultiplier | 1 | 1 | The object vismRtcpRepInterval specified above defines an approximate RTCP report interval (defined in RFC 1889) which indicates … |
| 1.3.6.1.4.1.351.110.3.17.2.15 | vismVoIpLapdTrunkPVC | 1 | 1 | This object should be used for VoIP Trunking applications and only if the signalling type is configured to be CCS. By default th… |
| 1.3.6.1.4.1.351.110.3.17.2.16 | vismVoIpEventNegotiationPolicy | 1 | 1 | This attribute defines whether or not the VISM should advertise the event codecs, NSE, NTE, or Cisco-rtp, in addition to the list… |