Section 5.21.2.3.2. Heterogeneous network with nodes that already modify

5.21.2.3.2. Heterogeneous network with nodes that already modify

In this case, an OpenScape 4000/HiPath 4000 network (surrounded by a dotted line in Figure 56) is networked with nodes of the older versions Hicom 300 E V2.0 or Hicom 300 V3.4.

For all trunks leading to systems of the versions Hicom 300 V3.4, the COT parameter LINO (line with implicit numbers, see Section 41.1.2.2, "Explicit and implicit phone numbers") must be set. You must set the COT parameter LWNC (line without node number) for tie trunks TT1/2 only if the Hicom 300 V3.3/Hicom 300 V3.4 network has already used the same node number (in a one-level network) or always in a multi-level network.

Figure 54. Example: Heterogeneous one-level or multi-level network with nodes that already modify

Multi-level OpenScape 4000 network or one-level network with ambiguous node numbers
1. Configuration in physical node PNNO=1 (or 1-1 for in case of two levels):
  In OpenScape 4000 node PNNO=1 (1-1 for multi levels), define a COT:
```
ADD-COT:COTNO=12,PAR=LWNC&LINO&...;
```
  Set up a route to Hicom 300 V3.4, e.g. in the multi-level network in this case. Node 2 must also be adapted to two levels in the same manner as Node 1-1, i.e. the fictive node number obtains a value of 2-0 ( 1-2 is also possible).
```
ADD-RICHT:MODE=LRTENEW,LRTE=101,LSVC=ALL,
NAME=UNKNOWN,TGRP=74,DNNO=2-0; 
```
2. Configuration in physical node NNO=2:
  In node NNO=2, you define a COT and a route. The fictive destination node 444 designates e.g. the "real" Node 1 in case, for example, Node 1 already exists in the Hicom 300 V3.4 subnet or, in case of multi levels, Node 1-1. Node number 444 may not exist in the Hicom 300 V3.4 subnet.
```
ADD-COT:COTNO=12,PAR=LWNC&...;
```
```
ADD-RICHT:MODE=LRTENEW,LRTE=233,LSVC=ALL,
NAME=UNKNOWN,TGRP=44,DNNO=444; 
```
One-level network with unambiguous node numbers:
1. Configuration in physical node PNNO=1:
  In OpenScape 4000 node NNO=11, you define a COT and a route:
```
ADD-COT:COTNO=12,PAR=LINO&...;
```
```
ADD-RICHT:MODE=LRTENEW,LRTE=101,LSVC=ALL,
NAME=UNKNOWN,TGRP=74,DNNO=2;
```
2. Configuration in physical node NNO=2:
  In node NNO=2, no particular COT parameter is required. As usual, you set up a route to destination node 1 (via LCR here):
```
ADD-RICHT:MODE=LRTENEW,LRTE=233,LSVC=ALL,
NAME=UNKNOWN,TGRP=44,DNNO=1; 
```
Setting the tie trunks:

The COT (class of trunk) number is to be set in TT1/2. You do not enter a fictive node number.
```
ADD-TDCSU:OPT=NEW,DEV=S2CONN,COTNO=12,...;
```
IMPORTANT:

The COT parameter LWNC always functions in an outgoing direction. If the parameter is set, no node numbers are sent to the partner node. In this case, the source node number, however, can be reconstructed using the digit analysis. Reconstruction reduces the performance. For this reason, multi-level networks should be configured only if absolutely necessary.

${DocTitle}, ID: ${DocID}

© 03/2026 Mitel Networks Corporation. All rights reserved. Mitel and the Mitel logo are trademark(s) of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH & Co. KG. All other trademarks herein are the property of their respective owners.

5.21.2.3.2. Heterogeneous network with nodes that already modify

Figure 54. Example: Heterogeneous one-level or multi-level network with nodes that already modify

IMPORTANT: