Multiple levels of node numbers

Virtual node numbers

Physical node numbers

Nnumbering plans

• Several E.164/PNP numbering plan ranges/codes per physical node
  This feature allows for example, a move while keeping the fully qualified phone number (E.164 with local destination code, national code, international code), which may make sense in a collocated system with several nodes (and thus several CO numbers) in one location. Stations, however, must still remain unique for each PABX. It is also possible to configure the phone numbers 49 89 722 4711 and 49 89 636 4712 to one PABX, but not 49 89 722 4711 and 49 89 636 4711. This must be taken into consideration in case of moves. If the subscriber 49 89 722 4711 is moving from node 1 to node 2, the station number cannot be retained if a subscriber already has extension 4711 (**) e.g.: 49 89 636 4711) on node 2.
  This feature is also of interest for IPDA numbering plans.

  IMPORTANT:

  For format-dependent number modification, only the assignment of the subscriber to a virtual node = numbering plan range is relevant! The assignment of the subscriber to a virtual node (AMO SDAT) and the numbering plan data defined to this node (AMO KNDEF) is also relevant.
• Overlapping phone numbers:
  Phone numbers (extensions) can overlap in the node code/local destination code of the E.164 number/local code of the PNP number. This feature is used if the required number of public phone numbers is not available in a consecutive range for a private network.
  Provided that the private network requires 1800 CO numbers, but cannot obtain any four-digit DID ranges from the public numbering plan (assigned or too expensive). In this case, two three-digit DID ranges can be used, e.g. the local destination codes 723 and 724 that result in CO numbers 723 xxx and 724 xxx. Since the internal phone numbers must be unique, however, the three-digit numbers xxx may not be used as internal numbers. One solution is a "double use" of the last digit of the local destination code as the first digit of the internal number, the "overlapping". This results in four-digit internal numbers ranging from 3000 to 4999, so more than enough.
  None up to all of the digits of the local destination code/local code/node code may overlap. The non-overlapping digits are the skip digits, that is, the digits that have to be removed to form the internal number. The number of skip digits must be configured (AMO KNDEF). The default here is "no overlapping", all digits are skip digits.
  In the example above, we have a three-digit local destination code and an overlapping digit (Digit 3 or 4), the number of skip digits is thus two.
• Modification for external nodes:
  If an OpenScape 4000 system networks with systems that do not have number modification and, for example, that can send only extension numbers as "calling numbers", the OpenScape 4000 can modify the external nodes. The administration of the modification with E.164 or PNP codes has been improved:
  External nodes for which the OpenScape 4000 (in its place) should modified are entered in the AMO KNDEF table under TYPE=EXTERNAL together with their codes. Phone numbers supplied by these external nodes are thus supplemented by the specified codes so that they appear delivered in the correct format. After this external modification, they are subject to the standard modification rules.

  IMPORTANT:

  Standard partner nodes that supply valid numbers must not be included in AMO KNDEF!
  The standard assignment is one physical node = one virtual node. In order for you to have to make as few changes as possible in the configuration of partner nodes when upgrading a OpenScape 4000 node within a network, we recommend using the original node number as the virtual node number and defining a new node number for the physical node number. Partner nodes must not change the configuration for routes (RICHT, LDAT) and number modification (KNMAT, KNFOR).