The homogeneous OpenScape 4000/HiPath 4000 network in this example has a three-level structure. It consists of four physical nodes (system) and three fictive virtual nodes (trunk access points). The subscribers of all nodes can be reached through all three numbering plans; i.e. they have individual numbers for each numbering plan. This configuration can be preset when the OpenScape 4000/HiPath 4000 network is to be set up as the central office. Figure 55 shows the network topology.

In this example, the setup of three numbering plans is shown parallel. In practice, ISDN and PRIVATE are usually not configured together. The commands belonging to the unconfigured numbering plan are simply omitted.

ZAND PNNO should be configured in line with the KNDEF node (i.e. same domain levels, but a different node ID), this is needed because ZAND PNNO is used as a reference point for number modification under some circumstances.

For example:

Redirection numbers will be modified with AMO KNMAT for all levels when the number is equal to the DAR length e.g. PSE/PSM codes - here number modification assumes the call forward is made to a local service so all levels will be modified with AMO KNMAT using ZAND PNNO as a reference point, to ensure the correct full redirection number is returned. Redirection numbers that are un-equal to a DAR result e.g. TIE+CODE, will only be modified for levels where there is a KNMAT entry match, here number modification assumes the user has programmed the call forward to a correct number meaning not all levels need to be modified.