123 KNFOR - Administration of Node Format table

 
AMO checks
Functions of the AMO
Error messages and advisories
Interrelationships
Parameter description
 
If an external node requires that the “calling number” (e.g. number of the A-subscriber) be changed to a specific format (type of number, TON) or if a specific check attribute (screening indicator, SCRE) is expected for the “calling number”, an entry must be created for this destination node in the node format table.
The TON is splitted into TONIN for the incoming end traffic and TONOUT for the outgoing traffic.
In this context node numbers are defined as "virtual node numbers". The own virtual node numbers are defined at own node by AMO KNDEF,TYPE=OWN. For DNNO both kind of nodes are allowed: Own virtual nodes and foreign virtual nodes. The foreign (remote) nodes can but need not be defined by AMO KNDEF. Therefore DNNO is not checked against the KNDEF-Entries (but advisory H03).
When an own virtual node number is entered into the format table, the display format for the “calling number” is controlled on all the terminals of the local virtual node. If more virtual nodes share the own physical node, it is possible to have individual display formats at each virtual node.
As a rule, no entries are required in the node format table.
In this case:
–
The “calling number” is always transmitted in the highest format (e.g. international);
–
The “calling number” is displayed in the lowest possible format (e.g. only the direct inward dialing number) on all the terminals of the local node;
–
The value of SCRE is set to NOT DEFINED in the source node;
–
In transit nodes, SCRE is passed transparently.
Note:
The “calling number” is any number that is not the “called number”
(e.g.: number of the A-subscriber, number of the answering subscriber, forwarding number).
DNNO parameter:
The destination foreign (remote) node numbers are defined by the AMOs RICHT resp. LDAT (Parameter DNNO), they depict always the end nodes of connections. In AMO KNFOR also the own node numbers are allowed (AMO KNDEF, TYPE=OWN, parameter NODECD).
TONIN / TONOUT parameters:
The TON parameters TONIN and TONOUT define the conversion by call processing of an explicit “calling number” to a desired format before the number is transmitted to a destination node (TONOUT) or displayed on the terminals of the local node (TONIN).
If a virtual destination node number extends over the own and foreign physical nodes, TONIN and TONOUT may both be set for the same virtual destination node whereby TONIN and TONOUT may be set to different values.
For the format dependent calling number modification, which is based on the numbering plans ISDN and PRIVATE of the ETSI-E.164/189 standard, the corresponding codes of the KNDEF-Table (AMO KNDEF) and the prefixes defined in node prefix table (AMO KNPRE) are used.
Note: The former circuit specific TDCSU-Codes are no longer configured by AMO TDCSU. They are now subscriber specific and assigned by AMO KNDEF, TYPE=OWN (in special cases also TYPE=FOREIGN). KNPRE-Entries must always be configured!
NPI parameter:
The numbering plan of a calling number is always derived from LCR-Outdial Rules (AMO LODR) and is valid both for calling and called numbers. This determines which branch in AMO KNFOR is to be used for modification.
The parameter values for TONIN / TONOUT depend on the particular NPI and have the following effect on the format of the “calling number”:
NPI = ISDN
(ISDN exchange numbering plan to ETSI-E.164)
 
Values of TONIN / TONOUT parameter
’Calling number’ format
 
(’Calling number’ comprises:)
INTERNAT
(International number)
Country code (CC)
+ area code (AC)
+ local subscriber number
e.g. 49 89 72232386
 
Display always includes trunk access code and prefix:
e.g. 0 00 49 89 72232386
INTERPRE
(International number with prefix)
International prefix
+ Country code (CC)
+ area code (AC)
+ local subscriber number
e.g. 00 49 89 72232386
 
Display always includes trunk access code:
e.g. 0 00 49 89 72232386
NATIONAL
(National number)
Area code (AC)
+ local subscriber number
e.g. 89 72232386
 
Display always includes trunk access code and prefix:
e.g. 0 0 89 72232386
NATIOPRE
(National number with prefix)
National prefix
+ Area code (AC)
+ local subscriber number
e.g. 0 89 72232386
 
Display always includes trunk access code:
e.g. 0 0 89 72232386
SUBSCR
Local subscriber number
e.g. 72232386
 
Display always includes trunk access code:
e.g. 0 72232386
UNKNOWN
Implicit number, can be dialed
e.g. 32386, 0 72232386, 0 0 89 72232386,
0 00 49 89 72232386
In the examples above:
Trunk access code=0, international prefix=00, national prefix=0, country code=49,
area code=89, address of main station=722
 
NPI = PRIVATE
(private numbering plan to ETSI-E.189)
 
Values of TONIN / TONOUT parameter
’Calling number’ format
 
(’Calling number’ comprises:)
LEVEL2
Level 2 code (L2C)
+ level 1 code (L1C)
+ local subscriber number
e.g. 9 8 732386
 
Display always includes trunk access code and prefix:
e.g. 1 3 9 8 732386
LEVEL1
Level 1 code (L1C)
+ local subscriber number
e.g. 8 732386
 
Display always includes trunk access code and prefix:
e.g. 1 2 8 732386
LOCAL
Local subscriber number
e.g. 732386
 
Display always includes trunk access code:
e.g. 1 732386
UNKNOWN
Implicit number, can be dialed
e.g. 32386, 1 732386, 1 2 8 732386,
1 3 9 8 732386
In the examples above:
Trunk access code=1, level 2 prefix=3, level 1 prefix=2, level 2 code=9,
level 1 code=8, local code=7
SCRE parameter:
If an external node requires a specific SCRE, it can be defined in the node format table for this destination node.
A SCRE entry for the local node number has no meaning.
Values of SCRE parameter
 
NETWPROV
The station number is generated by network
TRANSP
The screening indicator remains unchanged (transparent)
USERNSCR
The station number is not checked by user
USERVF
The station number is checked by user - the result was negative
USERVP
The station number is checked by user - the result was positive
Parameter SENDCALL:
This parameter controls how to send the Calling Number:
Values of SENDCALL parameter
 
SEND0
No Calling Number will be send.
SEND1
The available Calling Number will be send.
SEND2
"Two Number Delivery Option"
In case of this option the Calling Number and the Calling Node Number will be send.
Parameter SENDCONN:
This parameter controls how to send the Connected Number:
Values of SENDCONN parameter
 
SEND0
No Connected Number will be send.
SEND1
The available Connected Number will be send.
Parameter OVRDCAT:
With Override Category it’s possible to control the presentation of restricted Calling- or Connected Numbers (Presentation Indicator (PI) = RESTRICTED).
Values of OVRDCAT parameter
 
YES
Calling Numbers with PI=RESTRICTED will be send nevertheless to the Called Party.
Called Numbers with PI=RESTRICTED will be send nevertheless to the Calling Party.
NO
Restricted Calling- and Called Numbers will be not send. They will stay restricted.
Parameter ERROPT:
By configuring the Error Options the format of the Calling / Connected Numbers is affected in the special case, that the desired format, configured by parameter TONOUT, cannot be built up properly. This can occur for example, if the Country Code which is part of the calling number is not known in the system (e.g. call forwarding of an external international call to another .terminal in the local area). Usually the default value IGNOR should be chosen. This avoids inconsistencies between Calling / Connected Number and the correlated Type of Number (TON)..
 
Values of ERROPT parameter
 
IGNOR
If the desired format of the Calling / Connected Number as configured by parameter TONOUT cannot be built up, TONOUT is ignored.
DOMIN
If the desired format of the Calling / Connected Number as configured by parameter TONOUT cannot be built up, the Type of Number is nevertheless overwritten by TONOUT, i.e. TONOUT is dominant. This equals the "old" functionality before HiPath4000.
IMPL
If the desired format of the Calling / Connected Number as configured by parameter TONOUT cannot be built up, an implicit number (TON=UNKNOWN) with prefixes is sent.
${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.