125.1 Definitions

Station numbering plans:
The introduction of QSIG/DSS1 extends the options available for station numbering plans:
NPI = UNKNOWN: Hicom-specific station numbering plan
NPI = ISDN: ISDN-E.164 numbering plan
NPI = PRIVATE: private numbering plan (PNP) as defined in the ETSI standard.
In most cases, station number modification need only be set for numbering plan UNKNOWN. For the other NPI’s, a second method (Format Depending Modification), configured by using AMO’s TDCSU, KNFOR, KNPRE and KNDEF is normally used (see Service Manual / AMO Usage Examples).
Note:
KNMAT entries for NPI = ISDN or PRIVATE override the Format Depending Modification.
NPI is interpreted only where station numbers are modified, but not when connections are restricted. However, all the necessary information is contained in the output screens.
Originating Node Number:
Normally the Originating Node Number ONNO is taken from incoming messages of networking protocol (e.g. Cornet-NQ). If protocol is not containing ONNO (e.g. Central Office protocols), ONNO is taken from circuit configuration of incoming circuit (AMO TDCSU, parameter NNO) if this is activated by the appropriate COT parameters (see cross reference to AMO COT). For transit ONNO is passed from incoming connection (protocol or TDCSU) to outgoing connection. If the own node is originator of the connection, ONNO is the virtual node number of the calling station. All virtual node numbers of the own physical node are defined in a so called KNDEF-Table (administered by AMO KNDEF,TYPE=OWN). The assignment to the subscriber is done by the configuration AMOs (SCSU/SSCSU/SBCSU set only the default node number) or by AMO SDAT. The virtual node number of the calling station is then inserted into the appropriate protocol elements, if networking protocol allows transfer of originating node numbers (e.g. Cornet-NQ).
Destination Node Number:
The destination node number DNNO is defined by the AMOs RICHT resp. LDAT for number modification purpose; it depicts always the end node of a connection.
Levels:
The introduction of 3-level node numbers has given rise to the LEVEL parameter in KNMAT:
LEVEL = 0: Lowest level of the node number hierarchy. Only this level was available up to and including SP300 V3.4. Level 0 node numbers correspond to node numbers used in KNMAT up to and including SP300 V3.4.
LEVEL = 1: First level of the node number hierarchy; corresponds to the national level where NPI = ISDN, for example. A level 1 region number comprises all level 0 node numbers within that region.
LEVEL = 2: Highest level of the node number hierarchy; corresponds to the international level where NPI = ISDN, for example. A level 2 region number comprises all subordinated level 1 regions.
Figure 12
Example: 3-Level PBX Network
A node is identified uniquely in the network by a node number with up to three levels. This number is displayed in other AMOs (RICHT, LDAT, KNFOR etc.) in the form aa-bbb-ccc:
aa = level 2 region number
bbb = level 1 region number
ccc = level 0 node number
Node numbers are not visible at station display. Dialed and displayed are the station numbers, structured level oriented corresponding to the node numbers (see Figure 12).
In Figure 12 for example the shaded node has the number 1-20-100. Region/node codes are part of the station number in open numbered networks. The station in Figure 12 connected to node 1‑20‑100 has the phone number 7-81-911-4711.
KNMAT administers the network levels separately. For this reason, a modification point is addressed by a combination of the layer and node numbers (region numbers). One level is handled independently form another.
Figure 13
Modification Matrices and Modification Points in a 3-Level Network
Each NPI has a separate node connection matrix for each level, which means there are 9 individual node connection matrices in all (see Figure 13). The network levels are assigned individual node connection matrices, based on which reductions are applied sequentially from the highest to the lowest level and extensions from the lowest to the highest level:
•
Number reduction: Modification sequence is Modification Point 3, 2, 1 (up-down)
•
Number extension: Modification sequence is Modification Point 1, 2, 3 (down-up)
The restriction of connection is also level based. Therefore connections between regions can be allowed / denied too.
Logical nodes:
Logical nodes simplify the task of administration and result in less entries in the node connection matrix. They must not be used for the restriction of connection. The following logical nodes exist:
–
CDR: Charge Data Recording
–
OWN: Own nodes as they are specified by AMO KNDEF, TYPE=OWN
–
ROW: Rest Of World (all virtual nodes in system)
The logical node OWN is always converted into the virtual node numbers as defined by the AMO KNDEF, TYPE=OWN. This is only possible for the numbering plan UNKNOWN and LEVEL=0.
Any entry for ROW will not be converted into several entries for the existing physical nodes. The logical node ROW is only modified if the direct entry for the physical node (ONNO/DNNO) does not contain a modification. In this way, multiple modifications within one and the same level can be avoided.
Modification conditions:
Each point in the modification matrix is assigned a modification condition. These conditions describe the call processing context in which modification will take place. A modification condition can only be assigned, if a modification (NUMRED, NUMEXT) is either valid in the command or in the matrix.
Modification condition can be devided into
–
call processing context depending modification conditions (IN, OUT, TRANSI, TRANSH, ALL)
–
special modification conditions (REPEXT, RES1, RES2)
–
modification condition disable switch (NOMOD)
${DocTitle}, ID: ${DocID}
 © 02/2025 Mitel Networks Corporation. -  All rights reserved.
 Mitel and the Mitel logo are trademarks 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.