---
oid: "1.3.6.1.4.1.335.1.4.24.1.6.1.2"
short-description: "nvmIsdnDirectoryNumber OBJECT-TYPE"
last-modified: "2018-03-12"
parent-oid: "1.3.6.1.4.1.335.1.4.24.1.6.1"
---

## OID: `1.3.6.1.4.1.335.1.4.24.1.6.1.2`

```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) nvmIsdnDirectoryTable(6) nvmIsdnDirectoryEntry(1) nvmIsdnDirectoryNumber(2)}
```

### Description

```asn1
nvmIsdnDirectoryNumber OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..131))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"NAME = ;
DESC = A Directory Number. Directory Numbers are used \
to identify incoming calls on the signaling \
channel given in nvmIsdnDirectorySigIndex. \
The format of this information largely depends on the \
type of switch or PBX the device is connected to. \
Therefore, the detailed format of this information is \
not specified and is implementation dependent. \
If possible, the agent should implement this information \
using the E.164 number format. In this case, the number \
must start with '+'. Otherwise, IA5 number digits must \
be used. (Configuration);
HELP = This ICM variable contains the remote address for which \
incoming calls are handled.;
CAPABILITIES = ;"
REFERENCE
"ITU-T E.164, Q.931 chapter 4.5.10"
```

**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.