Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mgcpncsG729AnnexBNegotiation",
"OBJECT-TYPE",
"SYNTAX",
"MxEnableState",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates if the G.729 Annex B is negotiated through the session description protocol. RFC 3555 (MIME Type Registration of RTP Payload Formats), July 2003 explains how the Annex B can be negotiated by using the session description protocol. The Annex B indicates that Annex B, voice activity detection, is used or preferred. Permissible values are 'yes' and 'no' (without the quotes); 'yes' is implied if this parameter is omitted. m=audio 5004 RTP/AVP 0 18 13 a=fmtp:18 annexb=yes disable: The G.729 Annex B is NOT negotiated through the session description protocol. In that case, the G.729 Annex B is based on the MIB variable voiceIfG729VoiceActivityDetectionEnable. When this variable is set to 'enable', the G.729 codec negotiated as payload number 18 (G729) supports the Annex B implicitly. However, when the voiceIfG729VoiceActivityDetectionEnable variable is set to 'disable', the G.729 codec negotiated as payload number 18 (G729) does NOT support the Annex B implicitly. enable: The G.729 Annex B is negotiated through the session description protocol. In that case, the G.729 Annex B is advertised in the offer. The value depends on the MIB variable voiceIfG729VoiceActivityDetectionEnable. If this variable is set to 'enable', then the Annex B is set to 'yes'; otherwise, the value 'no' is advertised. The answerer MAY not be able to support the Annex B. In that case, the answer to the Annex B can be set to 'no'. This forces the offerer not to use the Annex B in G.729. However, the opposite is not possible. The answerer can NOT force the offerer to use the Annex B if this one does not bear such capability.\"",
"DEFVAL",
"{",
"disable",
"}",
"::=",
"{",
"mgcpncsInterop",
"15",
"}"
],
"syntax_tree": [
[
"row",
"MxEnableState"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates if the G.729 Annex B is negotiated through the session description protocol. RFC 3555 (MIME Type Registration of RTP Payload Formats), July 2003 explains how the Annex B can be negotiated by using the session description protocol. The Annex B indicates that Annex B, voice activity detection, is used or preferred. Permissible values are 'yes' and 'no' (without the quotes); 'yes' is implied if this parameter is omitted. m=audio 5004 RTP/AVP 0 18 13 a=fmtp:18 annexb=yes disable: The G.729 Annex B is NOT negotiated through the session description protocol. In that case, the G.729 Annex B is based on the MIB variable voiceIfG729VoiceActivityDetectionEnable. When this variable is set to 'enable', the G.729 codec negotiated as payload number 18 (G729) supports the Annex B implicitly. However, when the voiceIfG729VoiceActivityDetectionEnable variable is set to 'disable', the G.729 codec negotiated as payload number 18 (G729) does NOT support the Annex B implicitly. enable: The G.729 Annex B is negotiated through the session description protocol. In that case, the G.729 Annex B is advertised in the offer. The value depends on the MIB variable voiceIfG729VoiceActivityDetectionEnable. If this variable is set to 'enable', then the Annex B is set to 'yes'; otherwise, the value 'no' is advertised. The answerer MAY not be able to support the Annex B. In that case, the answer to the Annex B can be set to 'no'. This forces the offerer not to use the Annex B in G.729. However, the opposite is not possible. The answerer can NOT force the offerer to use the Annex B if this one does not bear such capability."
],
null,
null,
null,
[
"DEFVAL",
"disable"
]
]
}