|
Table 12-7
|
HiPath 3000 Class B Error Messages
|
|
|
HiPath 3000/5000 Manager E: Event Log Entry
|
|
|
|
|
| Error Class 01 - General Messages
|
|
|
|
|
| Hard restart (reset) of entire system with current CDB.
|
|
|
|
|
|
|
| Hard restart of entire system via SNMP.
|
|
|
|
|
|
|
| "On site" changes to the database.
|
|
|
|
|
|
|
| "Remote" changes to the database.
|
|
|
|
|
|
|
| APS transfer acknowledgement message via SNMP.
|
|
|
|
|
|
| !SNMP authentication fail
|
|
| Unauthorized access attempt.
|
|
| Check firewall settings in HiPath 3000/5000 Manager E (Network - Firewall).
|
|
|
|
|
| !SNMP 80 % high watermark of log-file
|
|
| Changes logged internally in the system: 80 % of write capacity used.
|
|
| Read out data using HiPath 3000/5000 Manager E (Transfer - Security - Protocol).
|
|
|
|
|
|
| Temperature in HiPath 3500/HiPath 3300 19" housing is too high.
|
|
| Check the fan and air supply in the 19" housing. Note the ambient temperature.
|
|
|
|
|
| !CDR buffer limit reached
|
|
| Overflow in the CDR buffer (CDR information).
|
|
| Check that the interfaces (V.24, LAN), ports and the connection are functioning or read out call data.
|
|
|
|
|
|
| Unauthorized access attempt.
|
|
| Check firewall settings in HiPath 3000/5000 Manager E (Network - Firewall).
|
|
|
|
|
|
|
|
| APS transfer possible again.
|
|
|
|
|
|
| Perform hard restart (reset).
|
|
|
|
|
| !unauthorized application
|
|
| Attempted access via an unauthorized application.
|
|
| Check firewall settings in HiPath 3000/5000 Manager E (Network - Firewall).
|
|
|
|
|
| !manual switchback from HiPath Manager
|
|
|
|
|
| Error Class 02 - License Management Messages
|
|
|
|
|
| HiPath License Management: Start of grace period.
|
|
|
| The remaining license validity period is shown on the display.
|
|
|
|
|
| HiPath License Management: Start of regular licensing.
|
|
|
|
| Error Class 09 - Hardware Module Messages
|
|
|
|
| !microprocessor fault on, common
|
|
|
| Check power at the power supply unit.
|
| If this error persists, replace the central control board.
|
|
|
|
|
| !microprocessor fault off, common
|
|
| The microprocessor error has been corrected.
|
|
|
|
|
|
| !loadware memory fault on, common
|
|
| Error in loadware memory.
|
|
| Replace the board if necessary.
|
|
|
|
|
| !loadware memory fault off, common
|
|
| Error in loadware memory has been corrected.
|
|
|
|
|
|
| !line interruption (error on)
|
|
|
| Check the line and terminal.
|
|
|
|
|
| !short circuit (error on)
|
|
| Short circuit on the board specified.
|
|
| Check the line, terminal, and port.
|
|
|
|
|
| !under voltage (error on)
|
|
|
| Check the power and line at the terminal's power supply unit.
|
|
|
|
|
| !thermal overload (error on)
|
|
| The specified board is overheated.
|
|
| Check the fan and air supply in the 19" housing. Note the ambient temperature.
|
|
|
|
|
|
| A bit slip has occurred on an ISDN line.
|
|
| If necessary, reload the board or perform a hard restart.
|
| If the error persists, set up an ISDN trace.
|
|
| The problem may be caused by asynchronous internal and external clock rates.
|
| Data loss possible/connection may be terminated.
|
|
|
|
| !slip detected off (STMD)
|
|
| The bit slip on the ISDN line has been corrected.
|
|
|
|
|
|
| !alarm indication signal error on (TMS2M)
|
|
| Alarm display: An S2M error has occurred.
|
| Physical line/board problem (too many CRC/SLIP errors).
|
|
| Check the S2M line and board.
|
| Replace the board if necessary.
|
| If the error persists, set up an ISDN trace.
|
|
|
|
|
| !alarm indication signal error off(TMS2M)
|
|
| Alarm display: The S2M error has been corrected.
|
|
|
|
|
|
| !no signal error on (TMS2M/STMD)
|
|
| Alarm display: An S2M error has occurred.
|
| No physical connection available.
|
|
| Check the S2M line and board.
|
| If necessary, reload the board or perform a hard restart.
|
| If the error persists, set up an ISDN trace.
|
|
|
|
|
| !no signal error off (TMS2M/STMD)
|
|
| Alarm display: The S2M error has been corrected.
|
|
|
|
|
|
| !receive remote alarm error on (TMS2M)
|
|
| Alarm display: An S2M error has occurred.
|
| Physical problem with the communication partner (too many CRC/SLIP errors).
|
|
| Check the board and partner system or arrange for a technician to do so.
|
|
|
|
|
| !receive remote alarm error off (TMS2M)
|
|
| Alarm display: The S2M error has been corrected.
|
|
|
|
|
|
| !bitslip error on (TMS2M)
|
|
| A bit slip has occurred on an ISDN line.
|
|
| If necessary, reload the board or perform a hard restart.
|
| If the error persists, set up an ISDN trace.
|
|
| The problem may be caused by asynchronous internal and external clock rates.
|
| Data loss possible/connection may be terminated.
|
|
|
|
| !bitslip error off (TMS2M)
|
|
| The bit slip on the ISDN line has been corrected.
|
|
|
|
|
|
| !loss of synchronization error on (TMS2M)
|
|
| A synchronization error has occurred.
|
|
| If necessary, reload the board or perform a hard restart.
|
| If the error persists, set up an ISDN trace.
|
|
| The problem may be caused by asynchronous internal and external clock rates.
|
| Data loss possible/connection may be terminated.
|
|
|
|
| !loss of synchronization error off (TMS2M)
|
|
| The synchronization error has been corrected.
|
|
|
|
|
|
| !Self test error on (SLMO)
|
|
| Error while self-testing the specified SLMO board.
|
|
| If necessary, replace the board or change the slot.
|
|
|
|
|
| !Self test error off (SLMO)
|
|
| Error while self-testing the specified SLMO board has been corrected.
|
|
|
|
|
|
| !Overcurrent on power controller on (SLMO)
|
|
| Overcurrent on the specified SLMO board.
|
|
| Check the power and line on the terminal and power supply unit.
|
| Replace hardware if necessary.
|
|
|
|
|
| !Overcurrent on power controller off (SLMO
|
|
| Overcurrent on the specified SLMO board has been corrected.
|
|
|
|
|
|
| !Out of buffers for card error on
|
|
| Insufficient pool capacity on the specified SLMO board.
|
|
| Check lines and terminals. Set up a default trace.
|
|
•
|
High traffic load: -> Distribute load to several boards.
|
|
•
|
Board is faulty: -> Replace board.
|
|
|
|
|
| !Out of buffers for card error off
|
|
| Insufficient pool capacity on the specified SLMO board has been corrected.
|
|
|
|
| Error Class 11 - General Messages
|
|
|
|
|
|
| Check the lines, terminal, and port.
|
| A short circuit may have occurred.
|
|
|
| Error Class 12 - Processor Exceptions
|
|
|
|
|
| Reset: Initial Stack Pointer
|
|
|
|
|
|
|
| Reset: Initial Program Counter
|
|
|
|
|
|
|
|
| In the case of HiPath 3550 or HiPath 3500, this problem may be caused by a software error -> Upgrade required.
|
|
|
|
|
|
|
|
|
|
|
|
| Interrupt Illegal Instruction
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TRAPcc, TRAP V Instructions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Reserved Coproc. Violation
|
|
| Reserved Coprocessor Violation
|
|
|
|
|
|
| Format Error Uninit. Inter.
|
|
| Format Error Uninitialized Interrupt
|
|
|
|
|
|
| Format Error Uninit. Inter.
|
|
| Format Error Uninitialized Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x0100, Critical Input Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x0200, Machine Check Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x0300, Data Storage Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x0400, Instruction Storage Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x0600, Alignment Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x0700, Program Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x0C00, System Call Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x1020, Watchdog Timer Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x1100, Data TLB Interrupt
|
|
|
|
|
|
| Instruction TLB interrupt
|
|
| HiPath 3800, Offset 0x1200, Instruction TLB Interrupt
|
|
|
|
|
|
|
| HiPath 3800, Offset 0x2000, Debug Interrupt
|
|
|
|
| Error Class 15 - Messages Concerning APS Transfer and Saving on Flash
|
|
|
|
| !Req to switch over APSXF
|
|
| Request for APS transfer.
|
|
|
|
|
|
| !APS switched over KDS ok
|
|
| APS transfer was successful.
|
|
|
|
|
|
| !APS switched over def. KDS
|
|
| APS transfer was not successful.
|
|
|
|
|
|
|
|
| If the error persists, replace the MMC module.
|
|
|
|
|
| !APS switched back def. KDS
|
|
| APS transfer was not successful.
|
|
| Load stored CDB onto the system.
|
| Provide snapshot and stack dump for analysis.
|
| Restart APS transfer or perform a speed upgrade.
|
| If the error persists, replace the MMC module.
|
|
| An error occurred while starting up the new APS. The system has switched back to the old APS. As a result, the CDB was set to "Default".
|
|
|
|
| !APS switched back old KDS
|
|
| APS transfer was not successful.
|
|
| Load stored CDB onto the system.
|
| Provide snapshot and stack dump for analysis.
|
| Restart APS transfer or perform a speed upgrade.
|
| If the error persists, replace the MMC module.
|
|
| An error occurred while starting up the new APS. The system has switched back to the old APS.
|
|
|
|
| !APS Transfer disconnected
|
|
| APS transfer interrupted.
|
|
| Check the transmission link and interface.
|
|
|
|
|
| !Country-text transferred
|
|
| Country-specific texts successfully transferred.
|
|
|
|
|
|
|
| Shadow APS cannot be deleted.
|
|
| If the error persists, replace the MMC module.
|
|
|
|
|
| !Blck_length err apsxf/ctxt
|
|
| Block length error during country-specific text transfer.
|
|
| Check the transmission link and interface.
|
|
|
|
|
| !Rest_length err apsxf/ctxt
|
|
| Remaining length error during country-specific text transfer.
|
|
| Check the transmission link and interface.
|
|
|
|
|
|
| Speed upgrade was successful.
|
|
|
| Software was updated. Previous CDB is still used.
|
|
|
|
|
| APS transfer was manually stopped.
|
|
|
|
| Error Class 16 - Operating System Messages
|
|
|
|
| GET-POOL xx, xx from=xx addr=xxxxxxxx
|
|
| Error in system pool administration.
|
|
| Set up a trace using information from BLS (Back Level Support).
|
|
|
|
|
| RELPL xxxxxxxxx len=xxxx, from=xx
|
|
| Error in system pool administration.
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| COSMOS send error (software message transmission).
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| COSMOS timer error (software timer administration).
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| COSMOS receive error (software message receipt).
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
| COSMOS ID=xx opcode=0xnnnn ercode=0xnnnn
|
|
| COSMOS error during restart
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| Overload or continuous loops during software operation.
|
| System watchdog restarted the system.
|
|
| Set up a trace using information from BLS.
|
|
| The system was un able to reach idle status within approximately ten minutes.
|
|
|
|
|
| Hard restart (reset) was manually triggered.
|
|
|
|
|
|
|
|
|
| The CDB is reset to default status.
|
|
|
|
|
|
|
|
|
|
| !KDS backup not performed
|
|
| Customer data was not backed up to MMC.
|
|
| Check the MMC module and replace if necessary.
|
|
|
|
|
| RESTARTED: unknown rest. HW-ind. mismatched
|
|
| Hardware reports an unknown reset reason.
|
|
| Check environmental influences (for example, grounding).
|
| Central control board problem: -> Replace board.
|
|
|
|
|
|
| Error while writing the log file to the MMC module.
|
|
| Check the MMC module and replace if necessary.
|
|
|
|
|
|
| Country-specific texts cannot be applied.
|
|
| Retransfer country-specific texts and change the language again.
|
|
|
|
|
| !CSTA: length out of range
|
|
| CSTA interface: Required length exceeds the permitted range. Incorrect internal parameters.
|
|
| Use the CSTA browser (application emulation) to check the CSTA interface.
|
| Set up a CSTA trace and a default system trace.
|
| Check whether or not the application has been released.
|
|
|
|
|
|
| CSTA interface: Allocation fails.
|
|
| Use the CSTA browser (application emulation) to check the CSTA interface.
|
| Set up a default trace with CSTA.
|
|
|
|
|
|
| Startup acknowledgement after speed upgrade.
|
|
|
|
|
|
| !idle arrived after restart
|
|
| System has reached idle status after restart.
|
|
|
|
|
|
| !exceed. of CSTA mon. pts
|
|
| Number of CSTA monitor points exceeded.
|
|
| Check the number of subscribers, lines, and ACD groups configured.
|
|
|
| Error Class 18 - Messages Concerning Database Handling and License Management
|
|
|
|
|
| HiPath License Management: Grace period was started.
|
|
| If necessary, load license from the CLS and relicense the system.
|
|
| The remaining license validity period is shown on the display.
|
|
|
|
| HLM:Feat-ID: xxx expiration started
|
|
| HiPath License Management: The specified feature is still valid for up to 30 days.
|
|
| If the customer still requires this feature, a new license file must be ordered and loaded to the system.
|
|
| The remaining license validity period is shown on the display.
|
|
|
|
|
| HiPath License Management: The validity period of the specified feature has expired.
|
|
| If the customer still requires this feature, a new license file must be ordered and loaded to the system.
|
|
|
|
|
| HLM: set license to default
|
|
| HiPath License Management: All licenses were deleted.
|
|
| Load license from the CLS and relicense the system.
|
|
| This error only occurs in combination with the following error messages:
|
| 1. HLM: Invalid license data.
|
| 3. HLM: Lic failure period stopped default lic.
|
| 4. HLM: Grace period stopped, default license.
|
| All licenses are deleted in each of these cases.
|
|
|
|
| HLM: Invalid license data
|
|
| HiPath License Management: The license file is invalid or has been manipulated.
|
|
| Load the original license file from the CLS and relicense the system.
|
|
|
|
|
| HLM:Lic failure period started
|
|
| HiPath License Management: The system is no longer connected to HiPath 5000 RSM.
|
|
| Check and reestablish the connection to HiPath 5000 RSM.
|
|
| The system was licensed in a network and is now no longer connected to HiPath 5000 RSM.
|
| You have 30 days to reestablish the connection. All system licenses will be deleted after this period.
|
|
|
|
| HLM:Lic failure period stopped license ok
|
|
| HiPath License Management: The connection between the system and HiPath 5000 RSM is reestablished.
|
|
|
|
|
|
| HLM: Lic failure period stopped default lic
|
|
| HiPath License Management: The connection between the system and HiPath 5000 RSM was not reestablished within 30 days. All licenses were deleted.
|
|
| Check and reestablish the connection to HiPath 5000 RSM.
|
| Load license from the CLS and relicense the system.
|
|
|
| Error Class 19 - Network Services Messages
|
|
|
|
| !SNTP-Server not responding
|
|
| No connection to the SNTP server.
|
|
| Check the application and the connection.
|
|
|
| Error Class 20 - Call Processing Messages
|
|
|
|
|
| The RS232/V.24 interface is out of order.
|
|
| Check the interface, the line, and the application.
|
|
|
|
|
|
| The RS232/V.24 interface is now operational.
|
|
|
|
|
|
|
| The maximum number of connection paths permitted has been exceeded.
|
|
| Use the project planning tool to test the system configuration.
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| Internal call data memory overflow.
|
|
| If the error persists, check the call data application interface.
|
|
|
|
|
| !Forced trunk disconnection
|
|
| Manual line release (for U.S. only).
|
|
|
|
|
|
|
| Advanced call data memory cannot be created.
|
|
|
•
|
System with MMC module: MMC module is faulty. Replace the MMC.
|
|
•
|
HiPath 2000: File system in flash is full or faulty.
|
|
|
|
|
|
| Read cache for reading out CDR data cannot be created.
|
|
| Perform a hard restart (normally occurs automatically).
|
|
| This is caused by insufficient system memory capacity.
|
|
|
|
|
| Error while writing CDR data to the advanced call data memory.
|
|
| MMC module: If necessary, read out call data via TFTP. The internal administration structure is also corrected, if this is required.
|
|
|
|
|
|
| Error while writing the administration structure to the advanced call data memory.
|
|
| MMC module: If necessary, read out call data via TFTP. After this, replace the MMC module.
|
|
|
|
|
|
| Error while reading CDR data from the advanced call data memory.
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| Error while reading administration structure from the advanced call data memory.
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| An advanced call data memory was found during system startup.
|
|
|
|
|
|
|
| The advanced call data memory is full.
|
|
|
|
|
|
|
| The advanced call data memory was successfully created.
|
|
|
|
|
|
|
| The advanced call data memory was temporarily released.
|
|
|
| This message is issued after the call data memory has been completely read out. It must be followed by the "CDR Mem. allocated" message.
|
|
|
|
|
| Output of MMC module size
|
|
|
| During system startup, the size of the MMC module is read out and hexadecimally output in bytes 1 and 2 of the info bytes. Value "00 10" describes the 16-MB MMC, value "00 40" describes the 64-MB MMC.
|
| This does not apply to HiPath 2000.
|
|
|
|
|
| Memory on the MMC module or in the HiPath 2000 file system is insufficient for creating the advanced call data memory.
|
|
|
|
| Error Class 21 - Device Handler Messages
|
|
|
|
|
|
| Use headset to check dial tone.
|
| Replace port or terminal if necessary.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Check that the clock is available on the S0/S2M line.
|
| If necessary, use HiPath 3000/5000 Manager E to correct the clock's allowed/denied numbers list (Trunk - Clock parameters).
|
| If necessary, perform a hard restart (reset).
|
|
|
|
|
|
|
| Check the fan and air supply in the 19" housing. Note the ambient temperature.
|
|
|
|
|
|
| The fan error has been corrected.
|
|
|
|
|
|
| !no ack from temp. sensor
|
|
| No response from temperature sensor.
|
|
|
|
|
|
| !overload at code receiver
|
|
| Not enough DTMF receivers.
|
|
|
|
|
|
| !overload at code transmit.
|
|
| Not enough DTMF transmitters.
|
|
|
|
|
|
| !Shorten Msg not successful
|
|
| Internal error: An overlong ISDN message could not be shortened by deleting Facility IEs.
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| Emergency battery operation due to power outage.
|
|
|
|
|
|
|
|
|
|
| Error Class 23 - Messages from the Device Handler Network
|
|
|
|
| !system hold, no buffer available
|
|
| System hold, no more free buffer available.
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
| !Check config rules for TMDID
|
|
| For U.S. only: TMDID boards incorrectly configured.
|
|
| Check TMDID board configuration using information from Seite 4-48 and correct if necessary.
|
|
|
| Error Class 26 - Board Administration Messages
|
|
|
|
|
|
| System does not support the board type. Replace the board with a valid board type or remove it from the system.
|
|
| The board may be too old or too new for the system.
|
|
|
|
|
| The specified board is out of order.
|
|
|
|
|
|
| !More than allowed amount of cards
|
|
| The maximum number permitted for a certain board type is exceeded.
|
|
| Reduce the number of boards of this board type. Note the maximum configuration.
|
|
|
|
|
| !other card type than old card type
|
|
| Incompatible board type. The slot is already pre-assigned with a different board type.
|
|
| Replace the board or use Assistant T to delete the preassigned board type so that the new board is recognized.
|
|
|
|
|
|
| The specified board is operational.
|
|
|
|
|
|
| !Reload after load-LW-Code error
|
|
| The specified board has been reloaded due to a startup error.
|
|
| If this error persists, replace the board.
|
|
| The board is reloaded due to a load error (length, checksum error) or a missing or delayed acknowledgement during startup.
|
|
| Error Class 28 - Recovery Messages
|
|
|
|
| !not possible to send a message
|
|
| Error while transmitting message via COSMOS (insufficient resources).
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| SLC LW trace transferred to trace memory.
|
|
| Trace memory can now be read out.
|
|
|
|
|
| --- tttttttt -> hh:mm:ss --- DD.MM.YY ---
|
|
| Time stamp set in event log B memory.
|
|
|
| A time stamp (current time and date) is entered when the event log B memory is copied. This facilitates analysis.
|
|
|
|
| --- APS: Hexxxxx.xx.xxx:xx xxx ----
|
|
| Current APS version entered in event log B memory.
|
|
|
| The current APS version is entered when the event log B memory is copied. This facilitates analysis.
|
|
| Error Class 29 - Messages Concerning Board Communication
|
|
|
|
|
|
| Set up a trace using information from BLS.
|
|
|
|
|
|
| Receive buffer is not free.
|
|
| Set up a trace using information from BLS.
|
|
| The board receive buffer cannot receive messages from the system (performance problems).
|
|
|
|
|
|
|
|
|
|
|
| The specified board has malfunctioned.
|
|
| If this error persists, check the board and the slot.
|
|
|
|
|
| !card ist present-LW has reset itself
|
|
| Loadware of specified board restarted.
|
|
| If this error persists, check the board and the slot.
|
|
|
|
|
| !ELIC deadlock no Interrupt from ELIC
|
|
| ELIC clock supply malfunction.
|
|
| Check central control board.
|
|
|
•
|
Environmental influences
|
|
| Error Class 30 - Board Software Messages
|
|
|
|
|
| PBC or ELIC error on the specified board.
|
|
|
|
|
|
|
| Temperature in HiPath 3550/HiPath 3350 wall housing is too high.
|
|
| Check the fan kit and the air supply in the wall housing. Note the ambient temperature.
|
|
|
|
|
|
| Temperature in HiPath 3550/HiPath 3350 wall housing is normal.
|
|
|
|
|
|
| !short circuit on Upoe Port SLMC on
|
|
| Short circuit in base station line.
|
|
|
|
|
|
| !short circuit on Upoe Port SLMC off
|
|
| Short circuit in base station line has been corrected.
|
|
|
|
| Error Class 32 - Messages Concerning IVM (HiPath Xpressions Compact) and EVM (Entry Voice Mail)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| !TIMEOUT during server-msg
|
|
|
|
|
|
|
| !IVM: Exception (unexpected error)
|
|
| IVM: An unexpected error has occurred.
|
|
|
|
|
|
|
| IVM: A software error has occurred.
|
|
| Upgrade IVM if necessary.
|
|
|
|
|
| !IVM: HD assignment of memory space 80%
|
|
| IVM: 80% of hard disk used.
|
|
| Search IVM statistics for mailboxes with too many undeleted messages.
|
|
|
|
|
|
|
| Search IVM statistics for mailboxes with too many undeleted messages.
|
|
|
|
|
| !IVM: Mailbox not available
|
|
| IVM: Mailbox is not available.
|
|
| Check whether the subscriber in question is available in the event log.
|
| Set up IVM system mailbox if necessary.
|
|
|
|
|
| !IVM: SW_Upgrade not possible
|
|
| IVM: Software upgrade is not possible.
|
|
| Reload the board if necessary.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| !IVM: HD assignment of memory space <70 %
|
|
| IVM: Hard disk load less than 70%.
|
|
|
|
|
|
| !IVM: Unauthorized call attempt
|
|
| IVM: Unauthorized call attempt.
|
|
| If the attempt is unintentional, deactivate the station number length.
|
| If the attempt is intentional, create an IVM trace to determine the subscriber who made the attempt.
|
|
|
|
|
|
| EVM: Command response timeout.
|
|
| If the error persists, replace the board.
|
|
|
|
|
|
| EVM: 80 % of memory used.
|
|
| Check EVM mailboxes for too many undeleted messages.
|
|
|
|
|
|
| EVM: Presence Event from EVM.
|
|
|
|
|
|
|
| EVM: Message limit reached.
|
|
| Check EVM mailboxes for too many undeleted messages.
|
|
|
|
|
|
| EVM: No language file available.
|
|
| Check available languages on the EVM.
|
| Load a language if necessary.
|
|
|
|
|
|
| EVM: VMM buffer overflow.
|
|
|
|
|
|
|
| EVM: EVM error during Data Mode.
|
|
|
|
|
|
|
| EVM: System - DH_EVM -> reset EVM.
|
|
|
|
|
|
|
| EVM: AM Command during Data Mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
| EVM: No Pill File Selected.
|
|
| Check available languages on the EVM.
|
| Load a language if necessary.
|
|
|
|
|
|
|
|
|
|
|
|
| EVM: I2C failure detected.
|
|
|
|
| Error Class 40 - Messages Concerning MMC Module Access
|
|
|
|
| !MMC not plugged or defective
|
|
| MMC module cannot be accessed during startup.
|
|
|
•
|
MMC module is not connected: -> Connect the MMC.
|
|
•
|
MMC module is faulty: -> Replace the MMC.
|
|
|