---
oid: "1.3.6.1.4.1.4935.99.100.1.5.5"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4935 mediatrixExperimental(99) mgcpncsExperimentalMIB(100) mgcpncsExperimentalMIBObjects(1) mgcpncsInterop(5) mgcpncsAnswerStreamFormat(5)}"
description: "mgcpncsAnswerStreamFormat OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2024-09-24"
---

## OID : `1.3.6.1.4.1.4935.99.100.1.5.5`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4935 mediatrixExperimental(99) mgcpncsExperimentalMIB(100) mgcpncsExperimentalMIBObjects(1) mgcpncsInterop(5) mgcpncsAnswerStreamFormat(5)}
```

### Description

```asn1
mgcpncsAnswerStreamFormat OBJECT-TYPE
SYNTAX INTEGER {zeroAnswerStream(1), removeAnswerStream(10)}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The answer to an offered session description is based on
the offered session description.
RFC 3264 stipulates that to reject an offered stream,
the port number in the corresponding stream in the
answer MUST be set to zero.
However, some gateways prefer to remove the unwanted
stream from the answer.
zeroAnswerStream:
The port number is set to zero if the corresponding
stream in the answer is unwanted. This behaviour
follows the RFC 3264 best practice.
removeAnswerStream:
The unwanted stream is removed from the answer and
returned to the offerer. This behaviour is kept
for backward compatibility issue."
DEFVAL {zeroAnswerStream}
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
