131.2.1 ADD-LDAT

For the features
(i) LCR and
(ii) LCR with closed numbering (NWLCR),
the LCR routes that were predefined using the AMO RICHT are assigned data for the device search.
For the LCR with its LCR digit patterns, the trunk groups that were assigned to a specific LCR route for one or more services using the AMO RICHT must be arranged according to specific (i.e. usually economical) considerations for path selection purposes.
The LCR route to be processed is specified with the parameter LROUTE.
The Parameter LSVC specifies the services (VCE, DTE or ALL) for which the route is installed.
If the route is defined in AMO RICHT using LSVC=ALL, only one maingroup will be installed for both services (check: DISP-RICHT;). All subsequent operations on this route using AMO LDAT must specify LSVC=ALL. If the services of the route have been defined separately from each other (1. using TYPE=LRTNEW, 2. using TYPE=LRTEXT), 2 different maingroups will be installed for this route. As the 2 maingroups may content different trunk groups, all LDAT operations must handle the services separately (except for DEL-LDAT:TYPE=LRTG).
LSVC=ALL is used, if the parameter is not entered.
Each LCR route is made up of individual LCR route elements, each of which constitutes a routing alternative.
The number of possible route elements per LCR route is unlimited.
EXCEPTION:
The maximum number of route elements per system (DIMSU parameter LRTEL) has been reached.
The route elements within an LCR route are prioritized (to ensure, for instance, that the cheapest routing alternative, the satellite or optical-fiber link etc. is used first) by assigning an LCR priority to every route element (parameter LVAL / LVALNEW).
Priority 1 is given the cheapest route element(s) within the LCR route.
The route elements are sorted in ascending order according to their priority. The priorities must be numbered consecutively; gaps are not allowed and will be prevented by the AMO, i.e. two adjacent route elements will always have either the same priority or a priority that differs by a factor of 1.
If the parameter LVAL/LVALNEW has not been specified, the AMO will use the LCR priority of the last element (i.e. 1 if no route element has been specified as yet). If the parameter LVAL has been specified, the specified route element is inserted after the last route element with the same LCR priority.
If, at a later stage, it becomes necessary to insert a route element with a "new" LCR priority, not the above-described parameter LVAL but the parameter LVALNEW should be used. In this case, the new route element will be inserted before the first route element with the same LCR priority; at the same time, the LCR priority of all subsequent route elements is incremented by 1.
Only one of the two parameters LVAL or LVALNEW must be used at any given time.
Each LCR route element (parameter LRTEL) is either assigned a trunk group (parameter TGRP) which has previously been defined for this LCR route using the AMO RICHT or gateway entries (up to 5) consisting of gateway number and sector path number.
EXCEPTION :
It is not allowed to create a route element which is assigned neither a trunkgroup nor a gateway element.
It is possible to assign the same trunk group to several LCR route elements so that it can be used more than once for a device search within the same (LCR) route.
Each LCR route element must be assigned an outdial rule previously defined by means of the AMO LODR parameter ODR. This outdial rule must be terminated with an END command.
To enable or disable a specific route element for a particular user, each route element must be assigned at least one LCR authorization (using the parameter LAUTH). It is possible to assign more than one authorization to a route element.
Only users whose active LCR class of service contains this LCR authorization will be able to seize this route element.
The 8 LCR schedules can be locked or marked as expensive for each LCR route element using parameter LSCHED. Each schedule may be marked as expensive or locked exclusively. if the parameter is missing, all schedules are unlocked and not marked as expensive.
Each LCR route may assigned a network carrier (parameter CARRIER) and a corresponding zone (parameter ZONE). Both parameters must be entered together. If the parameters are missing, CARRIER=1 and ZONE=EMPTY is used. If a value different from EMPTY has been specified for a zone, WCHREG (parameter LATTR) will automatically be set and the advisory H15 will be displayed.
Each LCR route may be assigned a Destination Node Number (parameter DNNO), which will override the DNNO set for the route in AMO RICHT for number modification purposes.
Each LCR route may be assigned a maximum number of compression/decompression cycles (parameter VCCYC). The value of VCCYC will be without effect, if the value VOICO of parameter LATTR is not set.
The value VOICO of parameter LATTR can not be set if the service of the route is not only VOICE.
Each LCR route element may be assigned a country- or network-specific LCR attribute (parameter LATTR). If LATTR is missing, no LCR attribute is assigned to this route.
To each LCR route element a central byte manipulation attribute (parameter CBMATTR) may be assigned, which specifies echo cancellation and a-law/m-law conversion.
To each LCR route element a specialized common carrier identifier (parameter SCCID) may be assigned, which is required to designate the specialized common carrier that point to a PRI trunk group. When OUTWATS is assigned as a call-by-call voice calling service and the LCR route element points to a NI-2 PRI trunk, a non-null SCCID value (0000-9999) must be assigned.
 
To each LCR route element a facility number (parameter FACILITY) must be assigned when the call-by-call PRI calling service is FX (Foreign Exchange Access) or TTA (Tie Trunk Access) (parameters SVCVCE and SVCNVCE). FACILITY value can be associated with only one service, SVCVCE or SVCNVCE. If for SVCVCE and SVCNVCE the values other than FX or TTA are entered, the FACILITY parameter is ignored if it is specified. Otherwise, it is set to empty.
 
To each LCR route element a service voice capability (parameter SVCVCE) may be assigned to designate the call-by-call voice capable PRI calling service to be used when the call being routed is a voice (speech) or voice-band call. This parameter is applicable only for LCR route elements that point to a PRI or CorNet-NQ trunk group. If FX or TTA is assigned to SVCVCE then FACILTY parameter must also be set. Parameter SVCVCE can be set if LSVC is VCE or ALL.
 
To each LCR route element a non-voice capability (parameter SVCNVCE) may be assigned to designate the call-by-call non-voice capable PRI calling service to be used when the call being routed is a digital data (UDI) call. This parameter is applicable only for LCR route elements that point to a PRI or CorNet-NQ trunk group. If FX or TTA is assigned then the FACILTY parameter must also be set. Parameter SVCNVCE can be set if LSVC is DTE or ALL.
One of the values OUTWATS, WB0..WB9, FX and TTA for SVCVCE and one of the values OUTWATS, FX and TTA for SVCNVCE can not be entered together.
 
LCR digit string restriction tables (parameter LDSRT) may be assigned to each LCR route element which contain the dial numbers to be restricted for the route element. These tables are administered via AMO LDSRT.
A Class of trunk index may be assigned to each LCR route element (parameter COTIDX).
Procedure Overview
 
Command Code
Parameter
ADD-LDAT
LROUTE=<number>, [LSVC=<param>]
 
{,(max 1)[LVAL =<number>] ,[LVALNEW =<number>] }
 
,TGRP =<number> ,ODR =<number>
 
,LAUTH =<number> ,[LSCHED=<param>],
 
{CARRIER = <number>, ZONE=<param> }
 
,[LATTR = <param>], [DNNO=<number>]
 
,[VCCYC=<number>], [CBMATTR=<param>]
 
,[SCCID=<key-num>], [FACILITY=<key-num>]
 
,[SVCVCE=<param>],[SVCNVCE=<param>]
 
,[LDSRT=<number>],[COTIDX = <number>], [GW1=<number>]
 
,[GW2=<number>], [GW3=<number>], [GW4=<number>]
 
,[GW5=<number>];
Examples
Input:
ADD-LDAT:21,,,,71,1,1; OR ADD-LDAT:21,,1,,71,1,1;
ADD-LDAT:21,,,,71,21,1; OR ADD-LDAT:21,,1,,71,31,1;
ADD-LDAT:21,,,,71,21,3; OR ADD-LDAT:21,,1,,71,31,3;
ADD-LDAT:21,,2,,71,1,3; OR ADD-LDAT:21,,2,,71,1,3;
ADD-LDAT:21,,2,,71,21,2; OR ADD-LDAT:21,,2,,71,31,2;
ADD-LDAT:21,ALL,1,,71,1,1,,1,EMPTY,NONE,,4,,,,,,,,1-8;
Display result:
Input:
DISPLAY-LDAT:LCR,21;
Output:
+------------------------------------------------------------------------------+
| LROUTE = 21 NAME = AMT S2 NAT. SERVICE = ALL |
| TYPE = LCR DNNO OF ROUTE = 1 -1 -8 |
| SERVICE INFO = |
+------+-----+-----+----+-----+----------+-----------+----------+------+-------+
| | | | | | SCHEDULE | CARRIER | | | |
|LRTEL | LVAL|TGRP | ODR|LAUTH| ABCDEFGH | ZONE| LATTR | LDSRT|COTIDX |
+------+-----+-----+----+-----+----------+-----------+----------+------+-------+
| 1| 1| 71| 1| 1 | ******** | 1 EMPTY| NONE | | 0 |
+------------------------------------------------------------------------------+
| 2| 1| 71| 21| 1 | ******** | 1 EMPTY| NONE | | 0 |
+------------------------------------------------------------------------------+
| 3| 1| 71| 21| 3 | ******** | 1 EMPTY| NONE | | 0 |
+------------------------------------------------------------------------------+
| 4| 1| 71| 1| 1 | ******** | 1 EMPTY| NONE | | 0 |
| +-----------------------------------------------------------------------+
| | GW1 = 1-8 GW2 = GW3 = |
| | GW4 = GW5 = |
+------------------------------------------------------------------------------+
| 5| 2| 71| 1| 3 | ******** | 1 EMPTY| NONE | | 0 |
+------------------------------------------------------------------------------+
| 6| 2| 71| 21| 2 | ******** | 1 EMPTY| NONE | | 0 |
+------------------------------------------------------------------------------+
OpenScape 4000 V10, Volume 1: AMO Descriptions, Service Documentation, Issue 5, ID: P31003H31A0S107057620
 © 09/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.