14.4.2.1. Global configuration for trunk searching (SMEO) 
Activate SMEO feature for trunk searching:
CHANGE-ZANDE:TYPE=MLPP,GSCR=METHODE2;
|
METHODE1
|
- means in fact no SMEO trunk selection,
|
|
METHODE2
|
- means GSCR methode 1 for SMEO trunk selection
|
If METHODE1 is set (default) the old MLPP / MUF functionality will remain unchanged.
For each subscriber the highest allowed precedence level and the service domain have
to be
configured. The customer must specify the precedence level for each subscriber. PRECLEVL
is
the parameter used to set the allowed level. SVCDOM is the service domain, use 0-0-0-0-0
as
default unless otherwise specified by the customer. The first two digits are for network
identification and the last three digits are for the service domain.
CHANGE-SDAT:STNO=<stno>,TYPE=DATA1, SVCDOM=0-0-0-0-0; CHANGE-SDAT:STNO=<stno>,TYPE=DATA1, PRECLEVL=FLASHOV; [V2.0 only] CHANGE-SDAT:STNO=<stno>,TYPE=ATTRIBUT, PRECLEVL=FLASHOV; [V1.0 only]
Activate MLPP/SMEO on trunks:
CHANGE-COT:COTNO=<cotnr>,COTTYPE=COTADD, PAR=MLPR; CHANGE-COT:COTNO=<cotnr>,COTTYPE=COTDEL, PAR=PROV&EODL&NMLT;
If the trunk is dedicated for DATA service:
CHANGE-COT:COTNO=<cotno>,COTTYPE=COTADD, PAR=DATA; /* For VOICE trunks, no parameter is necessary */
Set the service domain for the trunks using the following commands. The first two
digits are
for network identification and the last three digits are for the service domain.
CHANGE-TDCSU:PEN=X,DEV=S2CONN,BCGR=1, SVCDOM=0-0-0-0-0; CHANGE-TACSU:PEN=X,DEVTYPE=TT, SVCDOM=0-0-0-0-0;
LCR configuration must be carried out as follows (LDAT):
+------------------------------------------------------------------------------+ | LROUTE = 255 LDPLN NAME = FP07 S2 7GR SERVICE = ALL | | TYPE = LCR DNNO OF ROUTE = 802 | | SERVICE INFO = | +------+-----+-----+----+-----+----------+-----------+----------+------+-------+ | | | | | | SCHEDULE | CARRIER | | | | |LRTEL | LVAL|TGRP | ODR|LAUTH| ABCDEFGH | ZONE| LATTR | LDSRT|COTIDX | +------+-----+-----+----+-----+----------+-----------+----------+------+-------+ | 1| 1| 51| 2| 1 | ******** | 1 EMPTY| RTINEP | | 0 | +------------------------------------------------------------------------------+ | 2| 1| 52| 2| 1 | ******** | 1 EMPTY| RTINE | | 0 | +------------------------------------------------------------------------------+ | 3| 1| 53| 2| 1 | ******** | 1 EMPTY| PRTY | | 0 | +------------------------------------------------------------------------------+ | 4| 1| 54| 2| 1 | ******** | 1 EMPTY| IMMED | | 0 | +------------------------------------------------------------------------------+ | 5| 1| 55| 2| 1 | ******** | 1 EMPTY| FLASH | | 0 | +------------------------------------------------------------------------------+ | 6| 1| 56| 2| 1 | ******** | 1 EMPTY| FLASHOV | | 0 | +------------------------------------------------------------------------------+ | 7| 1| 57| 2| 1 | ******** | 1 EMPTY| NOLEV | | 0 | +------------------------------------------------------------------------------+ | 8| 1| 58| 2| 1 | ******** | 1 EMPTY| ALTTGR | | 0 | +------------------------------------------------------------------------------+
This is the correct configuration for the customer requirements. The B-channel with
the
lowest priorities will be used first.
Please note that with any other configuration there is the risk that the desired result
may
not be obtained for the SMEO search routine!
Important notes about SMEO trunk searching:
- The search routine is carried out for both voice and non-voice (data) trunk groups. The hunting sequence is capable of searching all trunks. For data calls, only data-grade trunks will be searched. For voice calls, all trunks will be searched.
- The route selection is based on precedence level and service domain (SD) classmarks. If domain check is activated in the system (CHA-ZANDE:TYPE=MLPP,DOMCHECK=YES;) then a call with a certain SD can use only a trunk with the same SD.
- The dimensioning of the LCR routes is very important. Note that for routine protected calls, only the corresponding classmarked trunks can be used. The trunk groups should be dimensioned according to the client traffic conditions. For example, if most of the calls are routine calls, the corresponding trunk group should contain the biggest part of the allocated B-channels. On the other hand, if just a small part of the calls are FLASHOV, there is no need to allocate too many B-channels for this level.
- The above LCR configuration is mandatory in order to have the full SMEO capabilities. If the MLPP classmarked trunks are not in the specified order, problems can occur: there is the possibility that MLPP calls will use alternative routes before using the dedicated ones; or, what is more dangerous, at the preemption point, a call with a higher priority (lower than the call being processed) will be disconnected instead of the one with the lowest priority.