Section 5.2.1.5. Implausible conditions for supplementation

5.2.1.5. Implausible conditions for supplementation

The administered source group related alternate routing destination number leads to WABE result unequal trunk or PSM/PSE and the parameter EXTNO was set > 0.
- It makes no sense, to supplement a source group related alternate routing destination number, that leads to a destination unequal trunk or PSM.
This will be rejected by syntax check of AMO APRT.
In case of routing type APE, the administered source group related alternate routing destination number, leads to a public trunk access.
- If the value of parameter EXTNO is administered smaller than the length of the called subscribers extension number, the related subscriber can not be reached.
  The implausibility of the source group related alternate routing destination number for this OOS scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage.
  
  The result is, that this alternate routing destination number can not be used for routing type APE.
- If the value of parameter EXTNO is administered bigger than the length of the called subscriber extension number, it will be ignored.
  In order to avoid wrong or misleading displays, the supplementation then will be done only up to the real length of the called subscribers extension number.
- If the value of parameter EXTNO is administered bigger than the maximum length of subscribers extension number, the command will be rejected by syntax check of AMO APRT.
- If the administered source group related alternate routing destination number contains only a trunk access into public network and the value of parameter EXTNO = 0, neither an alternate destination nor the called subscriber in its AP can be reached.
  A supplementation is necessary in this situation and a value of parameter EXTNO = length of called subscriber must be set.
  
  The implausibility of the source group related alternate routing destination number for this routing scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage.
  
  The result is, that this alternate routing destination number can not be used for routing type APE.
In case of alternate routing type = OOS because of device/board error or manual deactivated by AMO, the administered source group related alternate routing destination number leads to WABE result = trunk.
- If the value of parameter EXTNO is > 0, a supplementation with the called subscribers extension number is requested. This makes no sense in general, as this subscriber is in OOS state and cannot be seized successfully, even if doing a loop over public or tie trunk.
  The implausibility of the source group related alternate routing destination number for this routing scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage.
  
  The result is, that this alternate routing destination number can not be used for this routing scenario
In case of alternate routing type = APE or OOS because device/board error or deactivated by AMO, the administered source group related alternate routing number contains the access code for PSM/ PSE
- If the PSM/ PSE is designed with search length = 0, a supplementation is necessary with the length of called subscribers number.
  - If the administered parameter EXTNO is smaller than length of called subscriber, a PSM search cannot be successful. The implausibility of the source group related alternate routing destination number for this routing scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage. The result is, that this alternate routing destination number can not be used for this routing scenario
  - If the administered parameter EXTNO is bigger than length of called subscriber, a PSM search is possible. The supplementation will done with the real length of the subscribers extension number.
  - If the administered parameter EXTNO is bigger than maximum extension number length, the command will be rejected by syntax check of AMO APRT
- If the PSM is designed with search length = x, a supplementation is necessary with this length x
  - If the administered parameter EXTNO is smaller than search length x, a PSM search cannot be successful. The implausibility of the source group related alternate routing destination number for this routing scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage.
  - If the administered parameter EXTNO is bigger than search length x, a PSM search is possible. The supplementation will done up to the search length x.
In case of alternate routing type = OOS because HFA move logon from OpenScape 4000 to OpenScape Business/HiPath 3000, the administered source group related alternate routing destination number has to be designed in that way, that is possible to reach the moved subscriber in its new switch location via trunk access.
- If the administered parameter EXTNO = 0, the source group related alternate routing destination number is designed as a complete number.
  As it is not possible, to reach individual HFA IP phones with a unique unsupplemented alternate routing destination number, this number cannot be used for this routing scenario.
  
  The implausibility of the source group related alternate routing destination number for this routing scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage.
- If the value of parameter EXTNO is bigger than the length of the called subscriber number in OpenScape 4000, the supplementation will be done up to the real extension number length of the HFA IP phone in OpenScape 4000.

${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.