Collapse AllExpand All

17.30. LINO - Line with implicit number Previous topic Parent topic Child topic Next topic

Feature:

Display modification

Function:

The COT parameter LINO should always be used if old systems or external systems only understand implicit, i.e. dialable, calling numbers and return an undefined or incorrect NPI/TON combination for a sent number. Because, in practice, this cannot be ascertained without major effort, it is recommended that the LINO should be used as standard in the COT or trunks for old systems or external systems.
LINO applies to both incoming and outgoing lines. On the incoming side, the NPI and TON of each calling number is overwritten with UNKNOWN as standard. On the outgoing side, LINO causes all calling numbers with the breakout code and NPI = UNKNOWN and TON = UNKNOWN to be transferred.
The LINO parameter may not be set for CO trunk circuits.
If an explicitly signaled, external node (e.g. trunk) can be reached by means of a trunk with this number, then an entry for this node must exist with AMO KNFOR.
However, if a KNFOR entry (NPI = ISDN or Private) exists for the same route from which the LINO was set, then LINO is ignored and the display modification is controlled with NPI and TON of the incoming signal.
IMPORTANT:
The "Calling Number" refers to every number that is not the "Called Number" (e.g. the number of subscriber A, the number of the answering subscriber, the number of the diverting subscriber, etc.). NPI ... Numbering Plan Identifier ), TON .... Type Of Number

AMO Interrelationships:

IMPORTANT:
LINO and LINC may not be set together!
AMO KNFOR Set up node format table: <DNNO= ... , NPI=ISDN, TON=...>

Device types:

Digital tie trunk circuits

Network protocols:

For example, ECMAV2 (CorNet-NQ Issue 2.1 Dec.96 Basic ETSI), PSS1V2 (CorNet-NQ Issue 2.1 Dec.96 Basic ISO/IEC)