Collapse AllExpand All

5.5.3.3. What Information Does the Feature Provide? Previous topic Parent topic Child topic Next topic

By means of the AMO KNTOP, manual entries can be created in the partner table. Manual and automatic entries are displayed and can also be deleted. Output can be realized both in short and long output formats. In short output format, only the most important information of the partner is displayed, while long output format also displays additional information concerning the own node. Furthermore, a third format is available for diagnostic purposes. This is the query format START (see Section 25.3.4, "Diagnostic options"). The following section briefly explains the KNTOP outputs of the long output format:
  • NNO: This is the physical node number, as configured individually in the PNNO parameter of the AMO ZAND in every node. In the KNTOP output mask, the NNO of the own node is displayed in the left column beneath the heading "OWN NODE" and that of the partner in the right column beneath the heading "PARTNER NODE" (see Figure 15, Output mask of the AMO KNTOP with overwritten MANAUT entry)
  • NWTOPTIM: Polling Timer configured by AMO ZAND (see Section 25.3.2)
  • NODECD: This is the physical node access code as configured individually in every node in the PNODECD parameter of the AMO ZAND. In the KNTOP output mask, the NODECD of the own node is displayed in the left column beneath the heading "OWN NODE" and that of the partner in the right column beneath the heading "PARTNER NODE" (see Figure 15, Output mask of the AMO KNTOP with overwritten MANAUT entry). NODECD can also be designated as a node number, making it a number that is thus interpreted by the "Least Cost Routing" mechanism.
    IMPORTANT:
    If the feature is activated, an open numbered LCR route and a dialing pattern with its physical node access code must be configured in every network node for every partner node (adjacent node). The LCR bundle (AMO LDAT) need only be specified for formal reasons and is not evaluated. Please check whether the physical node figures are already configured in the LCR for the "Route Optimization" feature. If so, no further settings are necessary.
  • PEN: The PEN of the tie trunk circuit leading to the partner node is displayed under the heading "OWN NODE". Under the heading "PARTNER NODE", the PEN configured as an own node is displayed in the partner. This is always the output in the case of automatic entries (see description of the AUT field); the output field may be blank in the case of manual entries, as the PTPEN parameter is freely selectable in the add branch.
  • BCGR: The B-channel group of the tie trunk circuit leading to the partner node is displayed under the heading "OWN NODE". Although the BCGR field is also available under the heading "PARTNER NODE", it is only valid in the case of manual entries for digital circuits. In the case of automatic entries, no value is displayed, regardless of the configuration in the partner node. This is because the answering mechanism is handled via the D-channel protocol. However, there is only 1 D-channel for all B-channel groups, meaning that no assignment can be determined in this context. The field remains blank in the case of manual entries for analog circuits and of automatic entries.
  • TGRP: The number of the trunk group to which the tie trunk circuit or the B-channel group belongs in the own node.
  • OVRD: 3 possibilities:
    1. Display field is blank: This can only involve an automatic entry (see description of the AUT field) that was never based on a manual entry.
    2. MANONLY: The entry marked as such is manual, i.e. is realized with the AMO KNTOP. It cannot be overwritten automatically.
    3. MANAUT: Although the entry marked as such was originally made manually, it can be overwritten automatically. Whether or not this is the case can be derived from the AUT display field (if checked, it has been overwritten).
  • AUT: If this display field is checked, it involves an automatically created entry. All information regarding the partner node has been provided by the node itself. The partner node is actually connected and "live", i.e. it responds to the messages sent at the polling intervals. Automatic entries can also be deleted by the AMO KNTOP.
    If the partner node fails to respond repeatedly, it is automatically deleted and no longer displayed, even if it was originally created with MANAUT.
${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.