Collapse AllExpand All

5.36.2.3. Special Features and Restrictions Previous topic Parent topic Child topic Next topic

Special Features

The following special features arise due to the use of VNR:
  • Station numbers should be configured as DPLN-dependent with VNR The stations can only be assigned to the DPLN groups specified in the KNDEF parameter ADPLN. For the example in Figure 78, the stations are assigned to the DPLN groups as follows:
    Station number
    WABE
    95,96,97,98
    All
    10,20
    1
    100,200
    2
    1007,1008
    3
    Examples:
    • If station 96200 dials extension 100, it reaches STN 96100.
    • If station 951007 dials extension 1008, it reaches STN 951008.
  • Features, such as PU group, hunt group, CHESE, direct station selection, and COM group, can be configured for stations in different virtual nodes.
  • The network-wide Team CHESE feature becomes redundant if the CHESE stations are located in a single system after the startup of a VNR node. In this case, use of the standard CHESE function can be resumed.
  • The node code is required for unique identification with the Autoset Relocate and Mobile HFA features.
  • Closed numbering within one system between VNR nodes.
    Feature Description
    Any station number (including personal attendant console) is reachable via its extension number (short number, without VNAC in front).
    Different VNR nodes can be grouped under one VNR group via AMO KNDEF (parameter VNRGRP). Inside this VNR group closed numbering is possible, considering also the right display and ACL interface.
    Please be aware that one station number can be configured in more than one virtual node. If the same number is configured in more virtual nodes inside of a VNR group, only the first found one in the data base will be used!
    Service Information
    • Only stand alone system with VNR is considered. Only the stations belonging to one physical system can use closed numbering.
    • The feature is released for any kind of device (anate, digite and functional devices). HFA and SIP subscribers are considered too, but note that no changes have been done in the login phase / HFA mobility.
    • The VNR closed numbering applies to internal and external calls to stations (only for service VOICE, not for DTE or FAX).
    • This feature considers only basic call and the following basic features related to this:
      • consultation,
      • conference,
      • transfer,
      • centralized AC-features (blind transfer / single step transfer from AC, recall from Hold),
      • call completion (call back) on busy / free,
      • Call forwarding execution,
      • integrated OpenScape 4000 Call log and CLIR.
    • The display presents only the short number inside one VNR group (on calling and called side).
    • Only DISPMOD = UNKNOWN & ISDN are considered.
    • CCBS from CO is only working with its own ISDN number.
    IMPORTANT:
    The service technicians should be aware at configuration to assure that VNR Closed Numbering makes sense for the VNR nodes that are part of a certain VNR group (considering DPLN, ITR restrictions, number overlapping).
    Generation (Example):
    CHANGE-ZANDE:TYPE=ALLDATA,DISPMOD=UNKNOWN;
 
CHANGE-ZANDE:TYPE=ALLDATA,DISPMOD=ISDN;
    Activation of the feature in the system:
    CHANGE-ZANDE:TYPE=ALLDATA,VNRCN=YES;
    Group different VNR nodes under one VNR group:
    CHANGE-KNDEF:NNO=<number>,VNRGRP=<number>;
    The AMO KNDEF parameter VNRGRP allows to group different VNR nodes under one VNR group. Within this group closed numbering is possible between stations belonging to different VNR nodes.
    Changing the value for VNRGRP is only allowed when "VNR Closed Numbering'" is activated in the system (with AMO ZANDE).
    Default: VNRGRP=0. This means no membership to a certain VNR group; any other value means that the VNR node is part of the specified VNR group.

Restrictions

The following restrictions must be observed:
  • Keysets with lines via different virtual nodes are not supported. This restriction also applies for the network-wide Team CHESE function.
  • The members of the one number service must be located within a virtual node. Otherwise false information is displayed.
  • A code hunt group cannot be assigned to a virtual node. It should always be considered for the entire physical node. A workaround is possible with floating stations as a master hunt group.
${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.