This attribute defines whether the VISM has the capability to
negotiate the list of events either NSE (Named Signal Event)
or NTE (Named Telephony Events), using rtpmap and fmtpmap in
the SDP.
If the value is TRUE, then VISM will include / accept rtpmap
and fmtpmap in the SDP. Any events NSE / NTE not listed will
be interpreted as not supported.
If the value is FALSE, then VISM will neither include nor
accept rtpmap for X-NSE & X-NTE, and fmtpmap. For the backward
compatibility sake VISM will transmit DTMF digits using NSEs
if the value is FALSE
Parsed from file CISCO-WAN-AXIPOP-MIB.mib
Module: CISCO-WAN-AXIPOP-MIB
This attribute defines whether the VISM has the
capability to negotiate the list of events
either NSE or NTE(Named Telephony Events), using
rtpmap and fmtpmap in the SDP.
If the value is 'true(1)', then VISM will accept
rtpmap and fmtpmap in the SDP. Any events NSE/NTE
not listed will be interpreted as not supported.
If the value is 'false(2)', then VISM will neither
include nor accept rtpmap for X-NSE & X-NTE, and
fmtpmap. For the backward compatibility sake VISM
will transmit DTMF digits using NSEs if the value
is 'false(2).'
This attribute defines whether the VISM has the
capability to negotiate the list of events
either NSE or NTE(Named Telephony Events), using
rtpmap and fmtpmap in the SDP.
If the value is 'true(1)', then VISM will accept
rtpmap and fmtpmap in the SDP. Any events NSE/NTE
not listed will be interpreted as not supported.
If the value is 'false(2)', then VISM will neither
include nor accept rtpmap for X-NSE & X-NTE, and
fmtpmap. For the backward compatibility sake VISM
will transmit DTMF digits using NSEs if the value
is 'false(2).'
Parsed from file CISCO-VISM-MODULE-MIB.my.txt
Company: None
Module: CISCO-VISM-MODULE-MIB
This attribute defines whether the VISM has the
capability to negotiate the list of events
either NSE or NTE(Named Telephony Events), using
rtpmap and fmtpmap in the SDP.
If the value is 'true(1)', then VISM will accept
rtpmap and fmtpmap in the SDP. Any events NSE/NTE
not listed will be interpreted as not supported.
If the value is 'false(2)', then VISM will neither
include nor accept rtpmap for X-NSE & X-NTE, and
fmtpmap. For the backward compatibility sake VISM
will transmit DTMF digits using NSEs if the value
is 'false(2).'
vismVoIpNTECapabilityNegotiate OBJECT-TYPE SYNTAX TruthValue ACCESS read-write STATUS mandatory DESCRIPTION " This attribute defines whether the VISM has the capability to negotiate the list of events either NSE (Named Signal Event) or NTE (Named Telephony Events), using rtpmap and fmtpmap in the SDP. If the value is TRUE, then VISM will include / accept rtpmap and fmtpmap in the SDP. Any events NSE / NTE not listed will be interpreted as not supported. If the value is FALSE, then VISM will neither include nor accept rtpmap for X-NSE & X-NTE, and fmtpmap. For the backward compatibility sake VISM will transmit DTMF digits using NSEs if the value is FALSE " DEFVAL { true } ::= {vismVoIpGrp 9}
vismVoIpNTECapabilityNegotiate OBJECT-TYPE SYNTAX TruthValue ACCESS read-write STATUS mandatory DESCRIPTION "This attribute defines whether the VISM has the capability to negotiate the list of events either NSE or NTE(Named Telephony Events), using rtpmap and fmtpmap in the SDP. If the value is 'true(1)', then VISM will accept rtpmap and fmtpmap in the SDP. Any events NSE/NTE not listed will be interpreted as not supported. If the value is 'false(2)', then VISM will neither include nor accept rtpmap for X-NSE & X-NTE, and fmtpmap. For the backward compatibility sake VISM will transmit DTMF digits using NSEs if the value is 'false(2).'" DEFVAL { true } ::= { vismVoIpGrp 9 }
Vendor: Stratacom
Module: CISCO-VISM-MODULE-MIB
[Automatically extracted from oidview.com]
vismVoIpNTECapabilityNegotiate OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute defines whether the VISM has the capability to negotiate the list of events either NSE or NTE(Named Telephony Events), using rtpmap and fmtpmap in the SDP. If the value is 'true(1)', then VISM will accept rtpmap and fmtpmap in the SDP. Any events NSE/NTE not listed will be interpreted as not supported. If the value is 'false(2)', then VISM will neither include nor accept rtpmap for X-NSE & X-NTE, and fmtpmap. For the backward compatibility sake VISM will transmit DTMF digits using NSEs if the value is 'false(2).' " DEFVAL { true } ::= { vismVoIpGrp 9 }
vismVoIpNTECapabilityNegotiate OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute defines whether the VISM has the capability to negotiate the list of events either NSE or NTE(Named Telephony Events), using rtpmap and fmtpmap in the SDP. If the value is 'true(1)', then VISM will accept rtpmap and fmtpmap in the SDP. Any events NSE/NTE not listed will be interpreted as not supported. If the value is 'false(2)', then VISM will neither include nor accept rtpmap for X-NSE & X-NTE, and fmtpmap. For the backward compatibility sake VISM will transmit DTMF digits using NSEs if the value is 'false(2).' " DEFVAL { true } ::= { vismVoIpGrp 9 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.3.17.2.9.0 | vismVoIpNTECapabilityNegotiate | 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.2 | vismRtcpRepInterval | 1 | 1 | This attribute defines the RTCP(Real-time Transport Control Protocol) report interval (defined in RFC 1889). This indicates the i… |
| 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.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… |