---
oid: "1.3.6.1.4.1.4935.20.40.1.1.50.10.1.90"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4935 mediatrixIpTelephonySignaling(20) corNet(40) corNetSystemMIB(1) corNetSystemMIBObjects(1) corNetSystemData(50) corNetSystemDataIfTable(10) corNetSystemDataIfEntry(1) corNetSystemDataRfc2833DefaultPayloadType(90)}"
description: "corNetSystemDataRfc2833DefaultPayloadType OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2024-09-24"
---

## OID : `1.3.6.1.4.1.4935.20.40.1.1.50.10.1.90`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4935 mediatrixIpTelephonySignaling(20) corNet(40) corNetSystemMIB(1) corNetSystemMIBObjects(1) corNetSystemData(50) corNetSystemDataIfTable(10) corNetSystemDataIfEntry(1) corNetSystemDataRfc2833DefaultPayloadType(90)}
```

### Description

```asn1
corNetSystemDataRfc2833DefaultPayloadType OBJECT-TYPE
SYNTAX Unsigned32 (96..127)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable sets the payload type of the RFC 2833 events that is supported
by the unit. This value will be inserted in the dynamicRTPPayloadType field
in the H.225 TerminalCapabilitySet message.
For example,
CASE 1:
1) If corNetSystemDataRfc2833DefaultPayloadType = 98
2) If dynamicRTPPayloadType = 101
The unit will send RFC 2833 events with payload type 101. Also, the unit
will decode a RFC 2833 event with payload type 98.
CASE 2:
1) If corNetSystemDataRfc2833DefaultPayloadType = 98
2) If dynamicRTPPayloadType is not found in the received H.225
TerminalCapabilitySet message.
The RFC 2833 will be disabled in the unit."
DEFVAL {98}
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

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