Collapse AllExpand All

5.2.7. Frequently Asked Questions (FAQs) Previous topic Parent topic Child topic Next topic

  • Question: Why do we need ARoE and what does it do?
    • If a call is made to an unavailable (OOS or AP Emergency mode) station or a personal attendant console (AC), the call is routed to an alternate destination if this has been administered appropriately.
    • If a call to an attendant console group is made from an AP in AP Emergency mode, if an individual AC or an night station cannot be called, the call is routed to the HHS/AP where the AC is physically installed, if the source group = 0 has been administered appropriately.
    • If CCM paging or a page attempt is initiated from an AP in AP Emergency mode when CCM is unavailable (perhaps because it was configured in the HHS), the call can be routed to the relevant HHS/AP if the CCM source group can be administered.
  • Question: In which scenarios is ARoE used?
    • For calls to stations or personal attendant consoles that are in "NOT_READY" mode.
    • For calls to attendant console groups for which there are no available consoles or night stations.
    • For CCM paging and page attempts when CCM is unavailable.
    The following different scenarios exist:
    1. The station/personal AC is in NOT_READY mode due to a device/module error.
    2. The station/personal AC is in NOT_READY mode because it was deactivated using an AMO command. Concurrently a privilege for ARoE is set by AMO command when the station/personal AC is deactivated.
    3. The station is an HFA_IP telephone with Move_ Logon privilege in NOT READY mode. It has deregistered from the OpenScape 4000 due to an IP error and has registered to a backup node (OpenScape Business/HiPath 3000).
    4. The station/personal AC is in NOT READY mode because its access point (AP) which connects to the AP of the calling station is in AP Emergency (APE) mode.
    5. The station is an HFA IP telephone and is inactive.
    6. Due to AP Emergency, none of the AC group stations are available.
    7. Due to AP Emergency, CCM paging and page attempts are not possible.
    The NOT_READY scenarios 1, 2, 3 and 5 are classed as OOS while scenarios 4, 5 and 6 are classed as APE.
  • Question: Which alternate numbers can be administered?
    • In principle, more alternate numbers can be administered for each implementation scenario than is practical. The syntax checks for the AMOs SDAT, ACSU and APRT are very rudimental.
      Call Processing checks the usability of the alternate numbers for the relevant call scenario much more precisely and rejects the number if necessary. For example, CP does not permit an internal station number to be used as an alternate phone number for HFA_IP Move_logoff/Logon.
  • Question: Which alternate numbers are practical for each of the following implementation scenarios?
  1. OOS due to device/module error:
    Mobile number/paging number/attendant code/hunt group/etc.
  2. OOS due to deactivation via AMO:
    Mobile number/paging number/attendant code/hunt group/etc.
  3. OOS due to logon of HFA IP telephones to an alternate node
    An external phone number to the alternate node with the station number.
  4. APE scenario between the caller and the called station.
    A public network phone number with the station number.
  5. An HFA IP telephone is inactive.
    Mobile number/paging number/attendant code/hunt group/etc.
  6. Due to AP Emergency, there are no attendant group devices available.
    An external phone number to the HHS/AP where the AC is physically installed.
  7. Due to AP Emergency, CCM paging and page attempts are not possible.
    An external phone number to the HHS/AP where CCM is physically installed.
  • Question: How are alternate phone numbers configured?
    • Station-specific alternate phone numbers can be configured for OOS and/or APE using the AMO SDAT or ACSU.
    • Source-group (destination source group) related alternate phone numbers can be configured for OOS and/or APE using the AMO APRT.
  • Question: Can the configuration of nonsensical phone numbers cause problems for the switching system?
    • The AMO syntax checks for administering the alternate phone numbers are very rudimental. Call Processing, however, checks the suggested alternate phone numbers carefully before executing ARoE and rejects all nonsensical numbers.
  • Question: How often can a call be routed to an alternate destination?
    • ARoE in response to OOS should be performed once only internally and network-wide. After ARoE in response to APE, ARoE can be performed again for OOS.
  • Question: How do calling and called parties know when ARoE has been performed?
    • The alternate routing is not displayed to the calling or the called party. However, a different number to that dialed is shown on the calling party's display. This is the alternate number.
  • Question: Why are there station-specific alternate numbers and additional source group-relevant alternate numbers?
    • In principle, it should be possible to assign an individual phone number to each station for both OOS and APE. However, this is memory-intensive.
      If you can manage with a single alternate phone number for an entire source group, then it is sufficient to administer this number for the relevant source group using APRT instead of providing each station in the source group with the same individual alternate phone number.
      This number can be composed of a cascade of trunk access codes followed by a station number supplement.
      If both number variants are available, the station-specific alternate number is always used first. This procedure ensures that specific stations (VIPs) in a source group can be treated differently to the rest of the stations in that group.
  • Question: What is supplementing?
    • If you administer the alternate number on a source group basis, you can configure the number so that it contains several trunk access codes that provide a loop to the called party AP via the public network. In this case, the actual station number is not part of the alternate number to be administered but is automatically added to the alternate number by Call Processing in accordance with the specifications for supplementing.
      The same procedure is applied to ARoE for CCM. In this case the CCM code is the alternate number to be administered and the station number is the part to be supplemented.
      It is also possible to define a supplement with fewer digits than the called party number. This is practical, for example, if the numbering scheme for the alternate node at which the HFA IP telephones registers in the event of an error, has a different station number length.
      If the number is to be supplemented with a number shorter than that of the station number, the corresponding section of the station number is truncated. With ARoE to CCM, the number is truncated from the right. In all other cases, it is truncated from the left.
  • Question: Is there a means of avoiding loops in OpenScape 4000 or the public network?
    • Yes. This is performed automatically when ARoE is executed in an OpenScape 4000/HiPath 4000 network.
    • Yes. When ARoE is executed via the public network and the alternate number contains a supplement which produces a valid ARoE-relevant digit analysis result in the end node (ALTRTOOS/ ALTRTAPE).
    Note: This supplementary number should only be part of the alternate phone number if you have ensured that the digit analysis result has been configured.
    • Yes, if the gateway IP address of the alternate node was administered for the HFA IP telephones. In this case, the system checks if the call originated from the node to which alternate routing should be performed.
  • Question: Is there anything in particular that must be observed when ARoE is configured for analog phonemail?
    • Yes. In order for the phonemail to play the correct announcement, it requires the phone number of the unavailable station. This is only possible by converting "ARoE to the phonemail" to "CFU to the phonemail". To do this, the following administration tasks must be performed: ADD-ZIEL: TYPE = EVMTAB, SZTYPE = FWD, CD = <no_phonemail>;
  • Question: Is there anything in particular that must be observed when ARoE is configured for digital phonemail?
    • Yes. In order for the digital phonemail to play the correct announcement, it requires the phone number of the unavailable station. This is only possible by converting "ARoE to the phonemail" to "CFU to the phonemail".
      For trunks that are characterized by the COT parameter LRPM, this conversion is performed automatically when an outgoing line is seized.
      If the COT parameter LRPM is not set, the COT parameter ARCF should be set (see next question).
  • Question: Are there other scenarios in which ARoE should be converted to CFU?
    • Yes, for carriers which do not permit calls whose calling number does not belong to the system to which the carrier is connected. In the case of ARoE, the carriers request a redirection number. Again, this is only possible by converting ARoE to CFU. To ensure automatic conversion while seizing an outgoing trunk line, the COT parameter ARCF must be set for the outgoing seized line.
  • Question: Is ARoE performed for direct calls to a station in NOT_READY mode?
    • No, due to a device error or deactivation via AMO.
    • Yes, in response to log off/on of HFA IP telephones and APE.
  • Question: Is ARoE performed if a console makes a consultation call to a station in NOT_READY mode?
    • That depends on the Zand setting. (ZAND / ATND /ACEXTWFT). If this flag is set, then yes.
  • Question: Is ARoE performed if the destination Exec in an executive/secretary configuration is in NOT_READY mode?
    • That depends on the status of the RNGXFER key.
      If the RNGXFER key is not pressed, then ARoE is only performed if the secretary is also in NOT_READY mode.
      If the RNGXFER key is pressed, ARoE is performed immediately.
      The alternate number must be configured for this for the executive and the executive source group.
  • Question: Is ARoE performed for hotline after timeout on a station in NOT_READY mode?
    • Yes.
  • Question: Is ARoE performed for a hotline call on a station in NOT_READY mode?
    • Yes.
  • Question: Is ARoE performed if the destination is a hunt group member in NOT_READY mode?
    • No. In the case of hunt groups, no attempt is made to seize a member in NOT_READY mode. ARoE is therefore not performed.
  • Question: Is ARoE performed for on-hook MCC paging when the paged party is in NOT_READY mode?
    • No, due to a device error or deactivation via AMO.
    • Yes, in response to the log off/on of HFA IP telephones and APE.
  • Question: Is ARoE performed if, during third-party monitoring, the third party is in NOT_READY mode?
    • No, due to a device error or deactivation via AMO.
    • Yes, in response to log off/on of HFA IP telephones and APE. In the case of APE, the system checks that the alternate number actually contains the destination number. If the third party is a device in another node, ARoE is treated in the same way as for normal calls since there is no knowledge of the existence of remote third-party monitoring network-wide.
  • Question: When performing ARoE, is an ITR check performed between the called party and the alternate destination (if this is a station)?
    • No. This type of test is purposely not performed.
  • Question: Is there any interplay between ARoE and Call Forwarding?
    • YES in an AP Emergency scenario. If there is an AP Emergency between the calling station AP and the called station AP, it is assumed that the CF data for the destination in the calling station AP is not up to date. CF is therefore not performed if a valid number is available for ARoE for APE.
      If there are no valid numbers available for ARoE for APE, CF is performed with the aim of reaching an alternate destination.
  • Question: Is there any interplay between ARoE and Trace?
    • Yes. In the diagnosis printouts, the number of the station that invoked ARoE is recorded as with call forwarding.
  • Question: Are there any special requirements for LCR?
    • Yes, if the alternate number is an external number. In this case, only route elements that do not include internal reroutes are accepted.
      The caller's LCR class-of-service is upgraded. ZAND / LCR/ LCRCOSUP
  • Question: Is ARoE performed for Call Forwarding - No Reply after a Timeout?
    • No, not for general CFNR.
    • Yes, for quick CFNR on a station in NOT_READY mode.
    • Yes, for individual night service on a station in NOT_READY mode.
  • Question: Is AR0E activated for No Answer Recall?
    • No, not for normal No Answer Recall.
    • Yes, for No Answer Recall on a night station.
  • Question: Is ARoE performed for calls to a phantom station (without physical connection) that is in NOT_READY mode?
    • No, not for APE.
      Since the deregistered station cannot be assigned a physical line, an AP Emergency cannot be determined.
    • Yes, for OOS. For example, if the station was deactivated via AMO command.
      The alternate number may be administered on a station-specific or source-group-specific basis. Because there is no physical connection (source group = 0), the alternate number is determined in this case using source group = 0.
  • Question: Is ARoE performed for Callback, if the callback destination is in NOT_READY mode?
    • No. The callback entry is retained and can be executed once NOT_READY mode is quit.
  • Question: Can the alternate numbers for OOS also be used for APE?
    • Yes, if alternate numbers are not already configured for APE or are unusable.
      This does not apply to HFA IP telephones, which are set for automatic logoff/logon in the event of an error.
  • Question: Is ARoE performed in response to OOS for HFA IP telephones with Logoff/Logon functionality, if these devices were deactivated via AMO command?
    • No, since it must be assumed that in this scenario the HFA IP telephones are not registered to alternate nodes. This also applies if the COS for ARoE was set using the AMO SDAT.
  • Question: What type of additional diagnosis can be performed to detect ARoE malfunctions?
    • If you set flag 7 using DIAGS in CC or CP2, advisory messages with diagnostic information are output in the case of incorrect administration or situation-dependent unusability.
  • Question: Is ARoE performed for Autoset Relocate?
    • Yes, if the station is deregistered.
  • Question: Who bears the costs if ARoE is performed via public trunks?
    • The costs are borne by the station, for which ARoE was performed.
  • Question: Which number is being paged when suffix-dialing is performed after ARoE to CCM?
    • The number that appears on the caller's display is the number being paged. In other words, the alternate number.
  • Question: Is there any interplay between ARoE and synchronized announcement?
    • The announcement type is selected on the basis of the ITR number of the dialed destination. In the case of call forwarding, the ITR of the first destination dialed is the announcement type. If ARoE is performed for the first station number dialed, the ITR for that station is used for selecting the announcement type.
  • Question: Is ARoE performed when there are no available consoles or night stations?
    • If, for example, an attendant intercept is to be activated in an AP that is in AP Emergency mode and there are no physical consoles or night stations available in the AP, it is impractical to perform source-group-specific ARoE. If the call were to follow the alternate routing number assigned to the source group of the last checked night station, the call would end up at the AP where the night station is physically installed.
      Source group-independent routing is performed if an alternate routing number is administered for source group = 0 using the AMO APRT of the type APE. In this case, calls should generally be routed to the HHS.
      The solution is as follows:
      With this type of administration, the loop avoidance code for OOS must be included in the alternate routing number (ALTRTOOS).
  • Question: Is ARoE performed if CCM is not available due to AP Emergency?
    • If, for example, a station configured in an AP that is in AP Emergency mode cannot reach CCM because it is configured in the HHS, ARoE is performed if the following conditions are fulfilled:
      • A source_group-based alternate routing number for the CCM source_group is configured as an incomplete number. The value of the extension number is irrelevant in this case as long as it is greater than 0.
      • The CCM code should not contain any special characters as these cannot be transported via the public exchange.
        Likewise, ARoE is performed if a station configured in an AP that is in AP Emergency mode wants to respond to a paging call from the CCM in HHS. The attendant code used here should also not contain any special characters.
        It is not possible to perform on-hook paging from an AP in AP Emergency mode.
  • Question: Is there an administration tool for assisting in creating the alternate routing number?
    • Yes. Specially-authorized devices (auth_test_equipment) can dial the access code for ALTRTOOS or ALTRTAPE followed by the station number.
      If a valid alternate routing number is administered, it is this number that is called. If there is no valid alternate routing number, the station is called as normal.
      This method can also be used for attendant intercept calls with the attendant code. This applies to APE scenarios only (ALTRTAPE).
  • Question: Are there other means of adjusting the ARoE GUI?
    • Yes. There is a range of default settings that can be inversed using customer-specific patches. These settings include:
      • The administered alternate numbers for OOS can also be used for alternate routing for APE if the alternate numbers administered for APE cannot be used for the scenario in question (Default = TRUE).
      • The administered alternate numbers for OOS may also be used for alternate routing for APE if no alternate numbers are administered for APE (Default = TRUE).
      • ARoE is only performed if the alternate destination is in READY mode (Default = TRUE). An alternate destination can only be accepted in NOT READY mode if no other alternate destinations are configured. Alternate routing is also performed if the alternate destination is a device in NOT READY status. The advantage of this is that the call forwarding configured for this device can be used in this case if necessary. In addition, ARoE is possible for OOS, if the current ARoR is an APE.
      • More thorough plausibility check of the alternate number (Default = TRUE).
      • For testing/configuration purposes, it is possible to activate ARoE for APE for calls to stations in NOT READY mode even if there is no Access Point Emergency between the calling and destination stations (Default = FALSE). Calls to stations in NOT READY mode are always classed as AP Emergency between the caller and the destination.
  • Question: Is ARoE possible for SIP stations?
    Yes.
${DocTitle}, ID: ${DocID}
© 03/2026 Mitel Networks Corporation. All rights reserved. Mitel and the Mitel logo are trademark(s) 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.