---
oid: "1.3.6.1.4.1.335.1.4.24.1.9.1.9"
short-description: "nvmDialCtlPeerCfgPermission OBJECT-TYPE"
last-modified: "2018-03-12"
parent-oid: "1.3.6.1.4.1.335.1.4.24.1.9.1"
---

## OID: `1.3.6.1.4.1.335.1.4.24.1.9.1.9`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 335 products(1) micom-oscar(4) micom-isdn(24) configuration(1) nvmDialCtlPeerCfgTable(9) nvmDialCtlPeerCfgEntry(1) nvmDialCtlPeerCfgPermission(9)}
```

### Description

```asn1
nvmDialCtlPeerCfgPermission OBJECT-TYPE
SYNTAX INTEGER {
originate(1),
answer(2),
both(3),
none(5)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"NAME = ;
DESC = Applicable permissions. callback(4) either rejects the \
call and then calls back, or uses the 'Reverse charging' \
information element if it is available. \
Note that callback(4) is supposed to control charging, not \
security, and applies to callback prior to accepting a \
call. Callback for security reasons can be handled using \
PPP callback. (Configuration);
HELP = Access device ISDN does not support 'callback(4)'. The value \
'originate' is for outgoing calls. The value 'answer' is \
for incoming calls.;
CAPABILITIES = ;"
DEFVAL { both }
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

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

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.