The following events are generated by the SW application and indicate a switch integration problem:
This event indicates a process failure on the platform. Call transfers to an extension and message-waiting indicator (MWI) updates might fail.
This event indicates that there has been a process failure on the platform and that MWI updates might not occur.
This event indicates that there has been a process failure on the platform or that all channels were continuously busy while the switch integration software was trying to perform MWI updates. MWI updates will not occur.
The messaging software has stopped sending data until it receives an acknowledgment. If this condition persists, the link goes down, and the system issues either the SW OVERLAN 1 or SW OVERLAN 2 Major alarm.
This event might indicate network delay.
The oehs process is ready to handle telephone calls. The initialization is completely healthy, and the system has created the sockets. This is a sanity event that indicates the successful installation of the package.
The messaging software received an abort disconnect message from the switch. This message can indicate that the switch is either going down or resetting itself.
The messaging software received a normal disconnect message from the switch. This event can be a part of a normal switch shutdown.
The messaging software received an unexpected control message from the switch that can indicate that:
If this condition continues, it eventually leads to a link down message that indicates that the messaging software will drop the link and attempt to re-establish the link.
The messaging software received an invalid sequence number in a data acknowledgment message from the switch. The system sent out data, and the acknowledgment message from the switch did not match the sent data. This message can indicate LAN problems.
The call information cannot be sent to the Switch Integration Data Interface Process (SWINDIP) for parsing. SWINDIP is a background process for parsing received call information. This event results in telephone calls receiving nonintegrated call answer. Subscribers might also be reporting inconsistent MWI updates.
This event is related to interprocess communication (IPC) problems that are occurring on the system. Subscribers might be reporting inconsistent MWI updates.
The system could not parse switch information. Some or all of the telephone calls might receive nonintegrated call answer. Usually, this error happens only when the switch might be under a heavy load, and only some subset of calls will fail.
The system is not correctly performing MWI updates for a particular extension. Subscribers might be reporting inconsistent MWI updates. This event is related to IPC problems that are occurring on the system.
The system is not correctly performing MWI updates for a particular extension. Subscribers might be reporting inconsistent MWI updates. This event is related to IPC problems that are occurring on the system.
The system is not correctly performing MWI updates for a particular extension. Subscribers might be reporting inconsistent MWI updates. This event is related to IPC problems that are occurring on the system.
The system is not correctly performing MWI updates for a particular extension. Subscribers might be reporting inconsistent MWI updates. This event is related to IPC problems that are occurring on the system.
The system is not correctly performing MWI updates for a particular extension. Subscribers might be reporting inconsistent MWI updates. This event is related to IPC problems that are occurring on the system.
The system failed to write to the serial port. The event message will indicate if the problem is being caused by hardware or by administration. MWI updates will not occur.