ERR9000 - 9099
| ERR9000 | C T A NAS routing is incorrectly configured. The routing tables should contain DNs to reach remote attendants on the network. The configuration error was noticed by the software while processing CUST c customer number TEN t tenant number ALT a alternative The previous alternative route is probably badly defined, for example as a local DN. |
| ERR9004 | TN Horizon terminals must be defined with a display. |
| ERR9005 | TN Invalid input for Horizon terminal type. |
| ERR9006 | Invalid ESRT configuration. ACCD intercept treatment has been given to the set. Action: Correct the database. |
| ERR9007 | Invalid OSDN configuration, caller information is not linked. Action: Correct the database. |
| ERR9008 | Station set specified by OSDN is not configured with an OSN key. Caller information is
not linked. Action: Correct the database. |
| ERR9009 | Undefined CLID entry is configured for the originating DN of an ESA call. Calling
number is set to customer's DFCL. Action: Correct the database. |
| ERR9012 | ESA CLID configuration error detected. Calling number for ESA call is set to
customer's DFCL. Action: Correct the database. |
| ERR9013 | TN N data Parsing of QSIG Diversion Informations received failed, or QSIG Diversion
informations sent have been answered unexpectedly. Incorrect QSIG Diversion informations
are dropped. Output parameters: TN = TN from which information is received. N = error number data = dependent on error number (N) Action: Report the problem and the output parameters to your technical support group. |
| ERR9016 | x NON PROVISION SERVICE y An incoming SETUP with NSF IE message is received from the NI-2 CBC master route and the service specified in the facility coding field cannot be found in service route associating with the master route. The call was terminated as public call. Where: x = Master route number y = NSF IE in Hex format Action: Configure a service route. |
| ERR9017 | x INVALID CODING y |
| ERR9019 | A TN was found without a defined port type. The default will be assigned. TN and invalid port type are displayed. |
| ERR9020 | A TN was found without a valid card index. No transmission will be applied to this TN. The TN is printed. |
| ERR9021 | Type 5A PAD messages were specified for an unknown trunk card type. The TN is printed. Action: Contact your technical support group. |
| ERR9021 | Type 5B PAD messages were specified for an unknown trunk card type. The TN is printed. Action: Contact your technical support group. |
| ERR9022 | Type 5B PAD messages were specified for an unknown trunk card type. The TN is printed. Action: Contact your technical support group. |
| ERR9023 | Incorrect database configuration encountered. CNUS class of service conflicts with
CNAA class of service. Action: Correct the database configuration in LD 10. |
| ERR9027 | WARNING: Cannot use the B-channel or the ISL trunk because the STATEPM of the trunk is
not idle. The B-channel or ISL trunk is put in a maintenance busy state. Action: Manually restart the given B-channel or the ISl trunk. |
| ERR9030 | XMI failure. Cannot send PPM message to DPI card. |
| ERR9032 | Channel is put in lockout state. |
| ERR9033 | tn x y An incoming SETUP was received on a busy channel. Where: tn = terminal number x = time y = call reference of existing call |
| ERR9034 | x y z Cannot send an ISRM containing a Message Waiting NSI string. There is no NORTEL message waiting NSI string configured in Overlay 15 (for Notification (NOTI) or Cancellation (CNC). (Procedure FORMAT_MWI_NSI. Module DIO). |
| ERR9036 | The TMDI output buffer is not allocated. Ensure that some unprotected memory is available then use LD 17 and CHG CEQU (no real changes required to rebuild the output buffer). |
| ERR9044 | The ANI data should be retrieved from an ANI Entry but the specified Enr does not
exist in the Customer Data Block. Action: Configure the ANI Entry that is needed (Overlay 15). |
| ERR9048 | AUDIT turned on Analog CLI. |
| ERR9049 | AUDIT turned off on Analog CLI. |
| ERR9050 | RAN/MIRAN channel is not available. |
| ERR9051 | The CAC conversion data must be retrieved from a CAC conversion entry but the
specified entry does not exist in the Customer Data Block. The default table is used
instead. Action: Configure the CAC conversion entry that is needed (Overlay 15). |
| ERR9052 | VNS does not support Backup D-channel signalling. Action: VNS call made using BDCH. |
| ERR9056 | The XCT card is the only card supported by TWR1. The MFS card is not supported. The
call cannot be completed. Action: Contact your technical support group. |
| ERR9057 | The length of FLEN in LD 86 and LD 90 is not configured. The call cannot be completed. Action: Contact your technical support group. The FLEN must be configured. |
| ERR9058 | The supervision is not of the expected type. |
| ERR9059 | The data received for INS-J is more than 128 bytes. |
| ERR9060 | An invalid parameter type has been received. |
| ERR9061 | INS-J data was not expected. |
| ERR9062 | No DID digits were received in the INS-J data. |
| ERR9063 | An ACLI SSD message was unexpectedly received. |
| ERR9064 | The father CR is nil for the ACLI son call register. |
| ERR9065 | Parsing of QSIG Transfer information received failed. Action: Contact your technical support group. |