---
oid: "1.3.6.1.4.1.335.1.4.24.1.2.1.3"
short-description: "nvmIsdnSignalingCallingAddress OBJECT-TYPE"
last-modified: "2018-03-12"
parent-oid: "1.3.6.1.4.1.335.1.4.24.1.2.1"
---

## OID: `1.3.6.1.4.1.335.1.4.24.1.2.1.3`

```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) nvmIsdnSignalingTable(2) nvmIsdnSignalingEntry(1) nvmIsdnSignalingCallingAddress(3)}
```

### Description

```asn1
nvmIsdnSignalingCallingAddress OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..131))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"NAME = ;
DESC = The ISDN Address to be assigned to this signaling \
channel. More specifically, this is the 'Calling Address \
information element' as being passed to the switch \
in outgoing call setup messages. \
It can be an EAZ (1TR6), a calling number (DSS1, \
ETSI)or any other number necessary to identify a \
signaling interface. If there is no such number defined \
or required, this is a zero length string. It is represented \
in DisplayString form. \
Incoming calls can also be identified by this number. \
If the Directory Number, i.e. the Called Number in \
incoming calls, is different to this number, the \
isdnDirectoryTable has to be used to specify all \
possible Directory Numbers. \
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 = ;
CAPABILITIES = ;"
REFERENCE
"ITU-T E.164, Q.931 chapter 4.5.10"
DEFVAL { "" }
```

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