A general definition of the node numbers can be found in the "Networking Terms" chapter. Here, the role of the node numbers during number modification is described.

Since an individual number is not assigned to every node in an OpenScape 4000/HiPath 4000 network (e.g. several nodes are hidden behind the main station 089 7007), physical node numbers are used in a network as the unique address of a node. These node numbers are entered in various AMOs (ZAND, RICHT, etc.) and transported according to the number in the network protocol.

Based on the ISDN or PRIVATE numbering plan, a node number also has a hierarchical structure. It has Levels 0, 1, and 2. Just like the numbers, the individual levels of the node number define the respective number ranges. All nodes of a company in Munich, for example, may differ in Level 0, all cities of the company in Germany in Level 1, and all company countries in Level 2. It must be observed here that the node number is uniquely assigned to a node only in Level 0. The other levels describe ranges of subordinate nodes or levels. The ranges described in this manner must always be coordinated with the number ranges (e.g. the number area 89 for Munich should be precisely assigned an area number in Level X).

RULE:

A physical node number must be assigned to each node with AMO ZAND, parameter PNNO, which may be assigned only once within the network.

Node number 0 is not valid.

RULE:

All OpenScape 4000/HiPath 4000 networks can continue to be operated with one-level node numbers. If multiple levels are desired, however, the node number ranges should be adapted to those of the phone numbers!

RULE:

When multi-level node numbers are used, all node numbers must be kept at the same level within the network! If this is not possible, for example, since external nodes do not understand node numbers the COT parameter LWNC (line without node number) must be set in the respective set and a corresponding multi-level node number entered as destination node for this system in RICHT. If the other system already has one-digit node numbers, LWNC must also be set there.

RULE:

Systems that do not understand node numbers should always be assigned COT parameter LWNC in the trunks leading to them. LWNC always functions in an outgoing direction.

RULE:

The COT parameter DFNN should be used only in exceptional cases. The effect of DFNN is that the TDCSU node number is used for the modification when incoming and the reconstruction of the node number from the number is prevented. The disadvantage here is that a node-specific modification is prevented. A certain advantage results from an improvement in performance through the prevention of the reconstruction. You should use DFNN only for lines to external systems or if a node number reconstruction is not necessary due to the simplicity of the network. DFNN must always be used in combination with the TDCSU parameter NNO.