Collapse AllExpand All

5.2.1.1. Main goals for the alternate routing destination numbers in respect to OOS scenario Previous topic Parent topic Child topic Next topic

  • Device/ board error
    The goal is, to reach the called subscriber either with its mobile phone number, with an alternate number, via PSM or to lead the call to attendant, voice mail, phonemail or something else.
  • Manual deactivated (by AMO) with activated authorization for alternate routing
    If subscribers are manually deactivated by AMO command, alternate routing will only be performed, if the subscribers are authorized for requesting alternate routing when called after a manual deactivation.
    The goal are identical as for device/ board errors.
  • APE situation between APs of calling device and called subscriber/ personal attendant.
    In case of an APE situation between APs of calling device and called subscriber/personal_attendant, the involved APs act as single switches.
    The goal is, to reach the called subscriber in its AP via public trunk access. As a precondition, a public trunk access has to be administered between the related APs with routing elements without internal rerouting possibilities.
    Routing elements, that are defined as with internal rerouting, will not be used for alternate routing on error in general.
  • Deregistered HFA IP phones (OpenScape 4000 --> OpenScape Business/HiPath 3000).
    Special authorized HFA IP phones can move their logon location from OpenScape 4000 to OpenScape Business/HiPath 3000 in case of IP errors.
    The goal is, to reach this HFA IP phones in their new logon location via public trunk access under their individual (modified) extension numbers.
    TSC setups with service MWI to a unregistered HFA IP subscriber will be alternate routed to that switch, where the HFA IP phone is actually registered.
    This is a special usage of the feature, as in this scenario, alternate routing only will be started, if the administered alternate routing destination number points to a tie trunk (no public trunk).
    The reason for this is, that it is not possible to transport a MWI service via public network.
  • Deregistered HFA IP phones (OpenScape 4000 --> OpenScape 4000).
    HFA IP phones are normally registered at a OpenScape 4000 node with Xpressions. Special authorized HFA IP phones can move their logon location from OpenScape 4000 to another OpenScape 4000 node in case of system failure.
    The goal is, to reach this HFA IP phones in their new logon location via tie trunk access under their individual (modified) extension numbers and the HFA IP phones will be supplied with MWI update information of the Xpressions server.
    The MWI led will be switched on or switched off at the HFA subscriber. The HFA subscriber now has the possibility to call the Xpression server from the alternate OpenScape 4000 via tie trunk access in order to pick up its voice messages.
    If the HFA subscriber has different numbers in default node and alternate node, it may be necessary to use the mailbox number of the default node also when picking up the voice messages out of alternate node.
    Alternate Routing on Error via tie trunks to another OpenScape 4000 should be used very restrictive. Furthermore, the administration should only be done subscriber individual and not source group related.