vism Vo Ip Dtmf Relay

1.3.6.1.4.1.351.110.3.17.2.5

This attribute defines whether the DTMF (Dual Tone Multi-Frequency) digits need to be transported to the other endpoint via NSE(Named Signal Event) packets. DEFVAL { true } ::= { vismVoIpGrp 5 } SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION This attribute defines whether the CAS(Channel Associated Signaling) bits need to be transported to the other endpoint via NSE packets. DEFVAL { false } ::= { vismVoIpGrp 6 } SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION This attribute defines whether triple redundancy is enabled or not. With triple redundancy, NSEs are sent three times at 20 ms intervals. For reliable channels, triple redundancy can be disabled in order to save the bandwidth and the processing overheads. DEFVAL { false } ::= { vismVoIpGrp 7 } SYNTAX Integer32(250..65535) UNITS "milliseconds 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. DEFVAL { 250 } ::= { vismVoIpGrp 8 } 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 } SYNTAX Integer32(0..255) MAX-ACCESS read-write STATUS current DESCRIPTION This attribute sets the payload type of a RTP packet carrying SID(Silence Insertion Descriptor) which is sent to the other end when silence is detected. The default value is in accordance to RFC-3551. DEFVAL { 13 } ::= { vismVoIpGrp 10 } SYNTAX Integer32(10..5000) UNITS "milliseconds This attribute defines the inter cell gap for dual PVC(Permanent Virtual Circuit) OAM (Operational and management) cells. DEFVAL { 500 } ::= { vismVoIpGrp 11 } SYNTAX Integer32(1..20) MAX-ACCESS read-write STATUS current DESCRIPTION This attribute defines the threshold for failure of a PVC. If the number of consecutive OAM cells sent for which no ack was received equals this number then the connection is considered failed. DEFVAL { 3 } ::= { vismVoIpGrp 12 } SYNTAX Integer32(1..20) MAX-ACCESS read-write STATUS current DESCRIPTION This attribute defines the threshold for recovery of a PVC. If the number of consecutive OAM cells sent for which ack was received equals this number then the connection is considered recovered from failure. DEFVAL { 5 } ::= { vismVoIpGrp 13 } SYNTAX Integer32 (1..10) UNITS "milliseconds The object vismRtcpRepInterval specified above defines an approximate RTCP report interval (defined in RFC 1889) which indicates the interval in milliseconds at which the RTCP reports should be sent to the participating members. The object vismRtcpRecvMultiplier defines how many times the RTCP reports may fail before exception condition activity may be done. The number of times specified in this MIB object times the RTCP Report Interval, 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 multiplier 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.