Autoset Relocate / Mobile HFA

The node code is needed for unique identification.

CMI

All stations and the extension connections associated with an SLC board must be assigned to the same virtual node.

The CMI instructions on upgrading to VNR must be followed.

DTENO/FAXNO & STN

DAR=DTENO/FAXNO can no longer be used in CPS 6, 10, 11, and 12 to prevent interception for stations (faxes and modems) because, in contrast to stations, the node code is not appended to the DAR DTENO & FAXNO. This is why it is not possible to assign a node to them.

As a workaround, we recommend configuring all station numbers as DAR=STN and setting up system forwarding to the DAR= DTE + own station number or FAX + own station number.

DNIT

DNIT station numbers are not modified on the basis of the node code. It is thus impossible to uniquely assign them to a virtual node or even to use individual numbers repeatedly. Moreover, a number can only be configured as a DNIT number if it is configured for DPLN=0 or ALL DPLN groups.

We therefore recommend configuring six-digit DNIT numbers in a free number range. Known station numbers are configured as a floating station and routed to the associated DNIT station number via system forwarding.

Call data recording

The node code + extension are always sent by default to call data recording. Changes are possible with the AMO GEFE.

Internal E.164 dialing

An appropriate LCR configuration is needed for this.

KNDEF

ISDN and node codes must be unique.

DPLN is used for the DIAL operation in this node. If multiple DPLN groups are needed for the station, then the "allowed DPLN groups" should be entered under ADPLN, otherwise we recommend setting the ADPLN as equal to the DPLN to avoid configuration errors.

KNMAT

As station numbers are automatically modified with ITR, KNMAT should not be used in a VNR system.

Call data modification should be performed with the AMO GEFE.

PUBNUM in AMO SDAT should be used instead of the replacement extension (REPEXT).

KNMAT / ITR

Connections cannot be restricted in a physical system with KNMAT. Restrictions are only possible with ITR.

Cross node features

PU, HT, CHESE, DSS, COM group.

The relevant stations can be distributed across multiple nodes.

LCR / two-stage LCR

We recommend using two-stage LCR for a better overview of the LCR process, especially in the event of breakout in different locations or countries and to simplify expansion. Please note that a number of functions cannot be performed with RERTEINT, such as REMAC in AUN and ONS. These should be entered as international numbers in this case.

Features within a virtual node

Keysets => network-wide Team/Chese - The relevant station numbers must be located within a virtual node.

ONS

The members of an ONS group must belong to the same virtual node.

RCG / ACD

RCG station numbers can only be configured as DPLN-independent. This means they conflict with the VNR numbering plan. We therefore recommend configuring six-digit RCG numbers in a free number range. Old RCG numbers should then be replaced in applications by the new RCG station numbers.

RUFNUM

We strongly recommend against using the AMO RUFUM in the VNR system. A station number that is converted with the AMO RUFNUM cannot be assigned to a virtual node because the node code is not appended to it. We recommend replacing the RUFUM with a floating station with system forwarding.

Call numbers

Every virtual node must be assigned a unique node code and ISDN station number. The node code is part of the station code, the attendant console code, and the attendant code. These codes are needed to activate features (AMO ACTDA, AMO ZIEL, etc.)

Closed calling is no longer possible between stations with different E.164 station numbers.

HT (code)

Node codes are not appended to the station number of a hunt group code. This number is therefore valid system-wide. You cannot assign a virtual node to it.

Workaround: Change the hunt group code into a master hunt group using a floating station. PC-DACON supports this change.

HT (master)

The node code is part of the master hunt group's station number. It is therefore assigned a virtual node.

SIP /HFA

The node code is part of the station number. This station number should be signaled to the SIP and HFA terminals for logon at the gateway.

TDCSU / VNNO (CO)

A trunk connection can be assigned to a virtual node using the parameter VNNO in the AMO TDCSU if the carrier does not send a unique called party number, for example, only the DID number (extension).

Network with closed numbering

Please note the following if using a OpenScape 4000 numbering plan and closed numbering:

The relevant KNMAT entries that are needed to integrate an openly numbered node into an openly numbered network should be made network-wide.

It is important to ensure that the node code is part of the called party in the directly connected systems.

VFGKZ

The ATNDID and ATND codes should be assigned node codes in the AMO VFGKZ.

DPLN

To avoid restrictions in expansions, these station numbers should be configured as DPLN-dependent. As this significantly increases the number of DPLNCD and DPLNGR memory blocks used in the AMO DIMSU, attention should be paid to block formation in the DPLN configuration (always 0-9, 00-99, 000-999, etc.).

Example: 10&&19, 100&&159, 100&&199, 1000&&1199, 1000&&1999, 10000&&12999 etc.

DPLN / KNDEF

A DPLN group can be used for multiple virtual nodes.

DPLN - DAR

The following digit analysis results cannot be configured as DPLN-dependent:

RCG, SIGNON, SIGNOFF, DSNR, PRTY, IMMED, FLASHOV, FLASH, OWNNODE, INCALTRT, FRCALTRT

It is important to ensure that these codes do not conflict with the numbering scheme.

XPRESSION, DAKS etc.

In future, all connected applications that were previously switched with closed numbering must use a unique station number (E.164 or a prefixed node code).

Sole exception: The application only dials stations within a virtual node. In this case, the target node code can, where applicable, be preceded by DGTPR/VNNO.

ZANDE

You can use the AMO ZANDE to set the number format for internal number display. The same number format should be used for networking.