- Device configuration:
number (subscriber_A) = 4711
number (subscriber_B) = 4712
subscriber A,B in same source group
- What are the main goals ?
The main goal is, to reach the subscribers, that are in APE
situation to the calling device, via public trunk loop in their own APs.
Another
goal may be, to reach the subscriber via its individual mobile phone number.
- What is possible ?
All other alternate routing destination numbers, that lead to a valid
internal or external phone number, are possible.
The alternate routing destination
number can be designed as outgoing public trunk access or tie trunk access followed
by an
incoming trunk access to reach an AP. In case of a partly routing via public trunk,
in
order to avoid possible loops in public network, it would be a good option to enlarge
the
alternate routing destination number with that number, that will be evaluated in the
target OpenScape 4000 switch to the result "ALTRTAPE"
The alternate routing
destination number can be designed as a subscriber individual alternate routing number
or
as a source group related incomplete alternate routing number (with supplementation
request).
If the alternate routing destination number is designed as a source group
related incomplete number, the supplementation can only be done with the identical
subscribers extension number (parameter EXTNO = length of subscribers extension
number).
If the alternate routing destination number leads to a outgoing trunk
access, only those route elements will be used for alternate routing, that are defined
as
with " no internal rerouting ".
- What You want is: Calls subscribers A,B, that are in an APE situation to the calling
device,
should be routed to the called subscribers in its AP via public trunk loop.
In case of
APE, in the AP of the calling devices, it can not be verified, whether the called
subscribers in their own AP are in a seizable situation or not. Therefore, it makes
sense,
to alternate route the call to the originally called subscribers in their own APs
via
public trunk loop. The incoming trunk at target AP, then can verify for sure the real
state of the called subscribers.
For type = APE, You have to administer either
subscriber individual alternate routing numbers of type = APE for subscriber A and
B or
incomplete source group related alternate routing numbers of type = APE for the source
group(s), the subscriber A,B are members of.
If You are sure, You don't need
different alternate routing destinations for type = OOS, You also can administer the
mentioned alternate routing destination numbers for type = OOS for use of APE.
An
incomplete alternate routing destination number will be supplemented at time of usage
with
the extension number of the called subscriber A,B and with the administered length
(parameter EXTNO). This makes it possible to reach individual subscribers in other
switches.
If You use subscriber individual alternate routing destination numbers,
You have to administer a subscriber individual alternate number for the subscribers
A and
B with outgoing trunk access to public network (004989), with incoming trunk access
to
reach the OpenScape 4000 ( 723 ) and with the individual subscriber numbers of
subscriber_A and subscriber_B. If You use the option for loop avoidance, You have
to
enlarge the alternate routing destination number with that digit string, that will
be
evaluated in the target OpenScape 4000 switch to the result 'ALTRTAPE"
(99)
AEND-SDAT:STANO=<no_subscriber_A>, TYP=DATA1, STNOOOS=<004989-723-(99)- 4711;
AEND-SDAT:STANO=<no_subscriber_B>, TYP=DATA1, STNOOOS=<004989-723-(99)-4712;
If You use only source group related incomplete alternate routing destination numbers,
You
have to administer the source group related alternate destination number with outgoing
trunk access to public network (004989) and with incoming trunk access ( 723 ) to
reach
the AP of the called subscriber (A,B) in OpenScape 4000.
If You use the option for
loop avoidance, You have to enlarge the alternate routing destination number with
that
digit string, that will be evaluated in the target OpenScape 4000 switch to the result
'ALTRTAPE" (99).
Furthermore, You must set the supplementary length (parameter
EXTNO) to the length of the subscriber number in the OpenScape 4000, which is = 4.
In this
case, You must not use a different value for EXTNO than the length of the subscriber
number of subscriber A or
B.
ADD-APRT:TYP=ALTERR, SRCGRP=<srcgrp_subscriber_A, ALRTTYPE=APE, ALTRTNR=004989-723-(99), EXTNO=4;
- What You want is: Calls to not ready subscribers of source group 1, that are in an
APE situation
to the calling device, should be routed to the attendant console. Calls to not ready
subscriber_A, of source group 1, that is in an APE situation to the calling device,
should
be routed to a subscriber individual mobile phone number.
For type = APE, You must define
a source group related complete alternate routing destination number for the source
group
=
1.
ADD-APRT:TYP=ALTERR, SRCGRP=1, ALTRTYPE=APE, ALTRTNR=<no_melden>;
For
type = APE and for subscriber_A, You must set the subscriber individual alternate
routing
number to the individual mobile phone number.
AEND-SDAT:STANO=<no_subscriber_A>, TYP=DATA1, STNOAPE=<0-0049-1712272123;
If
You are sure, You will not use different alternate routing destination numbers for
OOS and
APE situations, it may be enough to define only alternate routing destination numbers
for
the type =
OOS.
ADD-APRT:TYP=ALTERR, SRCGRP=1, ALRTTYPE=OOS, ALTRTNR=<no_melden>;
AEND-SDAT:STANO=<no_subscriber_A>, TYP=DATA1, STNOOOS=<0-0049-1712272123;
