5.2.1.4. Philosophy of supplementation (parameter EXTNO) 
If You administer a source group related incomplete alternate routing
destination number, You also have to define the number of the called
subscribers digits for the supplementation.
If You administer the source group related alternate routing destination
number as a complete number, You have to set the parameter EXTNO = 0;
If You administer the source group related alternate routing destination
number as a incomplete number, You have to set the parameter EXTNO to
the number of the called subscribers digits, that are requested for supplementation.
The plausibility of a supplementation (design and usage) depends from
WABE result of the source group related alternate routing destination
number as well as from the alternate routing type.
The plausibility checks of the AMO APRT allow the input of EXTNO >
0 only for those alternate routing destination numbers, that do not lead
to WABE result = subscriber. But there are a lot of other possibilities
that are not restricted by the AMO, but cannot be executed at the time
of usage for special alternate routing scenarios.
A switch can be devided into several virtual switches. In every virtual
swich, subscribers can have numbers, that are also allocated in other
virtual switches. It is only possible, to distinquish this numbers with
help of their virtual node access code, which is a part of the subscribers
number.
When administering the parameter EXTNO, You must be aware of this.
- Usage of supplementation for APE
If You want to reach the subscribers, that are in APE situations, via public trunk loop in their own APs under their individual subscriber numbers, You must administer a source group related incomplete alternate routing destination number for type = APE, that contains a trunk access code for going public network and a incoming trunk access code to reach the APs, where the subscribers are located in, and as an option the digit string, that leads to DAR = "ALTRTOOS".The missing subscribers extension numbers will be supplemented at time of call execution by call processing.You have to administer, how many digits of the subscribers extension numbers should be used for supplementation with setting the parameter EXTNO > 0.In this example, it is obvious, that EXTNO has to be set to the length of the subscribers extension numbers.If You set the parameter EXTNO bigger than the length of the subscribers extension numbers, it is tolerated and will be decremented to the real length.If You set the parameter EXTNO smaller than the length of the subscribers extension numbers, this alternate routing destination number can not be used for that case.
Example 3:
Outgoing public trunk access = 004989, incoming trunk access = 722,
Number (subscriber_A) = 54321, digit_string, that leads to DAR "ALTRTAPE"
= 99
Administered source_group related alternate routing number = 004989-(99)-722
|
EXTNO = 5
|
-->
|
supplementation done / result = 004989-722-(99)-54321
|
|
EXTNO = 6
|
-->
|
supplementation done / result = 004989-722-(99)-54321
|
|
EXTNO = 4
|
-->
|
supplementation not possible
|
|
EXTNO = 0
|
-->
|
supplementation not requested / the number 004989722(99)
do not lead to a valid destination, but neither by AMO nor at time of
usage, this can be verified.
|
- Usage of supplementation for OOS (device/ board error or deactivated
by AMO)
If you want to reach the subscribers, that are in OOS situation, with searching via PSM under their individual search numbers, You must administer a source group related alternate routing destination number for type = OOS, that contains the PSM access code.The missing subscribers extension numbers will be supplemented at time of call execution by call processing.You have to administer, how many digits of the subscribers extension numbers should be used for supplementation with setting the parameter EXTNO > 0.If the PSM is designed with search length = 0, the parameter EXTNO has to be set to the length of the called subscriber numbers.If the PSM is designed with search length = x, the parameter EXTNO has to be set to that value (x). The normal situation is, that the search length is smaller than the length of called subscribers. In this case, the supplementation result leads to a cut search number. The cutting will be done from right hand side.
Example 4:
PSM access code = #77
Number (subscriber_A) = 54321
Administered source group related alternate routing number = #77
Search length = 3
|
EXTNO = 3
|
-->
|
supplementation done / result = #77-543
|
|
EXTNO = 4
|
-->
|
supplementation done / result = #77-543
|
|
EXTNO = 2
|
-->
|
supplementation not possible
|
|
EXTNO = 0
|
-->
|
supplementation not requested / invalid
|
Example 5:
PSM access code = #77
Number (subscriber_A) = 54321
Administered source group related alternate routing number = #77
Search length = 0
source group related alternate routing number = #77
|
EXTNO = 5
|
-->
|
supplementation done / result = #77-54321
|
|
EXTNO = 6
|
-->
|
supplementation done / result = #77-54321
|
|
EXTNO = 2
|
-->
|
supplementation not possible
|
|
EXTNO = 0
|
-->
|
supplementation not requested / invalid
|
- Usage of supplementation for OOS in case of moved logon
If You want to reach the HFA IP phones, that have moved their logon location from OpenScape 4000 to OpenScape Business/HiPath 3000 in their new logon switch under their individual extension number, You have to administer a source group related incomplete alternate routing destination number for type = OOS, that contains a trunk access code for outgoing public network and an incoming trunk access code, to reach the OpenScape Business/HiPath 3000.The missing subscriber extension numbers will be supplemented at time of call execution by Call processing.You have to administer, how many digits of the subscribers extension numbers should be used for supplementation with setting the parameter EXTNO > 0.It may be possible, that OpenScape Business/HiPath 3000 works with a different number scheme than OpenScape 4000.If the HFA IP phone extension numbers are identically in both switches, You have to set the parameter EXTNO to the identical extension number length of the HFA IP phones.If the HFA IP phone extension numbers in OpenScape Business/HiPath 3000 are smaller than in OpenScape 4000 (see example 4), You have to set the parameter EXTNO to the smaller HFA IP phone extension number length. in OpenScape Business/HiPath 3000. The later performed supplementation then will cut the HFA IP phone extension numbers from left hand side on.If the HFA IP phone extension numbers in OpenScape Business/HiPath 3000 are bigger than in OpenScape 4000 (see example 5), You have to set the parameter EXTNO to the length of the HFA IP phone extension number in the OpenScape 4000. As the extension numbers in OpenScape Business/HiPath 3000 starts with an additional digit (9), You must add this as a prefix to the source group related alternate routing number.
Example 6:
Outgoing public trunk access = 004989,
Incoming trunk access for OpenScape Business/HiPath 3000 = 865
Number (HFA IP phone_A in OpenScape 4000) = 54321
Number (HFA IP phone_A in OpenScape Business/HiPath 3000) = 4321
Administered source group related alternate routing number = 004989-865
|
EXTNO = 4
|
-->
|
supplementation done / result = 004989-865-4321
|
|
EXTNO = 5
|
-->
|
supplementation done / result = 004989-865-54321
In
OpenScape Business/HiPath 3000 -, the correct HFA IP phone can not be
reached.
No kind of syntax check can avoid this malfunction.
|
|
EXTNO = 3
|
-->
|
supplementation done / result = 00498986-5321
In
OpenScape Business/HiPath 3000 -, the correct subscriber can not be reached.
No kind of syntax check can avoid this malfunction.
|
|
EXTNO = 0
|
-->
|
supplementation is not requested / invalid
|
Example 7:
Outgoing public trunk access = 004989,
Incoming trunk access for OpenScape Business/HiPath 3000 = 865
Number (HFA IP phone_A in OpenScape 4000) = 54321
Number (HFA IP phone in OpenScape Business/HiPath 3000) = 9-54321
Administered source group related alternate routing number = 004989-865-9
|
EXTNO = 4
|
-->
|
supplementation possible / result = 004989-865-9-4321
In
OpenScape Business/HiPath 3000, the correct subscriber can not be reached
No kind of syntax check can avoid this malfunction.
|
|
EXTNO = 5
|
-->
|
supplementation done / result = 004989-865-9-54321
|
|
EXTNO = 6
|
-->
|
supplementation done / result = 004989-865-9-54321
|
|
EXTNO = 0
|
-->
|
supplementation is not requested / invalid
|