Administration Rules

1. Setting the home physical node number:
   An network-wide unambiguous physical node number must be set in each network node by means of the AMO ZAND, parameter PNNO. (The node number of the virtual node is configured in the AMO KNDEF.)
2. Setting the home physical node code:
   The Route Optimization feature is based on the physical node codes. These must be unambiguous throughout the network. This also applies to networks with closed numbering schemes.
   The home physical node codes must be assigned by means of AMO ZAND, parameter PNODECD, and applied to digit analysis result OWNNODE by means of the AMO WABE. (The node code of the virtual node is configured in the AMO KNDEF.)

   IMPORTANT:

   If route optimization is performed, the node code contained in the route optimization messages is subject to the station number modification which must be correctly configured.
3. Configuring routes to remote network nodes:
   The remote node codes must be configured by means of AMO WABE (DAR "TIE") for both open and closed numbering schemes and assigned to the trunk groups as route codes with AMO RICHT.

   IMPORTANT:

   Note that in spite of the closed numbering scheme the node codes for route optimization must have open numbering.
4. Identification of routes suitable for route optimization:
   The routes must be marked as being suitable for route optimization by means of AMO RICHT, parameter ROUTOPT=Y. The lines of all routes with ROUTOPT=Y must lead to nodes which also support route optimization (see 5). This cross reference is not verified in the AMOs!
   Identification of lines leading to adjoining nodes that support route optimization:
   A class of trunk must be defined by means of AMO COT, parameter PAR=ROPT. This class of trunk must be assigned, by means of the AMO TDCSU, to those circuits which lead to an adjoining node that support route optimization. This ensures that the standard route and the alternative route only pass via nodes that support route optimization.
5. Setting protocol variant:
   The AMO TDSCU, parameter PROTVAR should be used in variant Hicom 300 V3.3 or higher to set the value CORNV33 (or the value ECMA2 in Hicom 300 V3.5 or higher) in all digital tie trunk circuits to nodes to ensure transmission of the ROPT-specific messages in the network protocol.
   Cross checks: AMO RICHT checks whether a route to be set up with ROPT capability contains at least one trunk group of the type S0/S2 and whether the "voice" service has been configured.

   IMPORTANT:

   Standards and alternative routes do not restart-safe during the optimization process. In addition, all station services are disabled for the duration of the optimization process. An attempt to activate features in this phase is acknowledged on the display with "PLEASE REPEAT" or "NOT POSSIBLE". Attempts to activate a feature are ignored in the case of analog stations.