Error type 1: Reports the registration status of the endpoint. If the Communication Manager software claims the endpoint is registered and receives keep-alive handshakes from the endpoint, the test passes. If keep-alive handshaking has failed, the test fails. If the user has intentionally un-registered from the Duplicated server, the station is now basically an AWOH station and is no longer being maintained. No tests are run for this station.
Error type 18: The port/station is busied out by maintenance personnel. Ensure the port/station is released from busy via releaseport|station (IP terminal only).
Error type 257: Tracks failures of the signaling path PING test. The test attempts to send a PING packet to the endpoint IP address, as reported during registration. The PING packet originates with the C-LAN board through which the endpoint is registered. If the PING response packet is received, the test passes. If the PING response packet times out, the test fails.
Error type 513: Indicates that the terminal failed to respond to the ID Query request. This implies that there is something wrong with the terminal or the communication path. (IP terminal only).
Error type 1281: Indicates that the terminal is reporting a bad state of health (IP terminal only).
Error type 1537: Indicates that the link has gone down between the terminal and its gateway to the switch. This likely means that the terminal has unregistered (IP terminal only).
Error type 1793: Indicates the IP station has registered with a Survivable Remote Server. Follow standard practices to repair the primary server, or network failure.
Error type 2305: Indicates that there was an unsolicited Link Reset even though switch software believed the terminal to be functional and in service. This error can be ignored if no user complaints are received (IP terminal only).
Error type 2817: Tracks failures of the port hyperactivity counter. If a port generates more than 50 uplink CCMS messages within 10 seconds, the port is taken out-of-service for 30 seconds. Even though the softphone actually signals over a TCP/IP link, DCP CCMS messages received over the TCP link are counted as regular CCMS uplinks and can cause the station to be marked as hyperactive.