5.36.3.1. Tasks Involved in Switching to VNR 
- The system must be regenerated before changeover to VNR. A detailed
customer network analysis with DPLN planning for the stations of the
VNR system is strongly recommended.
- Each virtual node must be assigned a unique node code. This cannot
be changed. All node codes must feature DAR =OWNNODE in the AMO
WABE.
- The station terminals are generated with node codes in the relevant
AMOs (SBCSU, SCSU, etc.).
- After activating the VNR feature, SIP and HFA terminals must log
back on (LOGON) with node code and station number. The terminals should
be provided with the new LOGIN data for this purpose.
- Each virtual node must be assigned a unique E.164 station number.
- LCR routes must be set up with reroute internal to ensure internal
availability via the E.164 station number. If all virtual nodes are located
in one LAN, this can be implemented using three basic "reroute internal"
LCR routes (subscriber, national and international) for which the complete
E.164 station number is mirrored. However, if a breakout to another location
is expected in the future, we advise changing over to a two-level LCR.
The associated depends on the ISDN station numbers in the VNR system.
- All station numbers assigned before feature activation in OpenScape
4000 must be expanded to include the virtual node code for all features
(for example, AMO ACTDA, AMO ZIEL). (Impact on the use of DLS, PCDACON,
OpenScape 4000 Manager, etc.)
- If the internal E.164 station number display (AMO ZANDE, parameter
DISPMOD=ISDN) is used, the shortest ISDN station number possible
is displayed for connections across virtual nodes such as in networking.
Using the AMO KNFOR, the shortest station number display can be restricted
to National or International. Within the local virtual node, only the
station number without the node code is shown as usual.
- If a shared trunk connection is used to reach multiple virtual nodes,
an explicit E.164 station number must always be sent by the CO. In this
case, the parameter DFNN must not be set in the AMO TDCSU.
- Connections between virtual nodes can only be restricted with ITR.
Existing KNMAT restrictions must be converted to ITR restrictions.
- The virtual node code is a component of the CHRGEE in call data recording.