Ascend Disconnect-Cause Codes & Explanations
Code Number | Code Description |
0 | No-Reason. There was no reportable reason for the disconnect. |
1 | Not-Applicable. The event was not a disconnect. |
2 | Unknown. The reason for the disconnect is unknown. This code can appear when the remote connection goes down. |
3 | Call-Disconnected. The call has disconnected. |
4 | CLID-Authentication-Failed. ID authentication has failed. |
5 | CLID-RADIUS-Timeout. RADIUS timeout during ID authentication. |
6 | No description available. |
7 | The Send Disconnect timer in the Line profile has been triggered. |
The following codes can appear if a disconnect occurs during the initial modem connection. | |
8 | No description available. |
9 | No modems available. |
10 | Modem-No-DCD. The modem never detected DCD. |
11 | DCD-Detected-Then-Inactive. The modem detected DCD, but became inactive. |
12 | Modem-Invalid-Result-Codes. The result codes could not be parsed. |
The following codes are related to immediate Telnet and raw TCP disconnects during a terminal-server session. | |
20 | TermSrv-User-Quit. The user exited normally from the terminal server. |
21 | TermSrv-Idle-Timeout. The user exited from the terminal server because the idle timer expired. |
22 |
TermSrv-Exit-Telnet. The user exited normally from a Telnet session. |
23 | TermSrv-No-IPaddr. The user could not switch to SLIP or PPP because the remote host had no IP address or because the dynamic pool could not assign one. |
24 | TermSrv-Exit-Raw-TCP. The user exited normally from a raw TCP session. |
25 | TermSrv-Exit-Login-Failed. The login process ended because the user failed to enter a correct password after three attempts. |
26 | TermSrv-Exit-Raw-TCP-Disabled. The raw TCP option is not enabled. |
27 | TermSrv-CTRL-C-In-Login. The login process ended because the user typed Ctrl-C. |
28 | TermSrv-Destroyed. The terminal-server session has ended. |
29 | TermSrv-User-Closed-VCon. The user closed the virtual connection. |
30 | TermSrv-VCon-Destroyed. The modem outdial virtual connection has ended. |
31 | TermSrv-Exit-Rlogin. The user exited normally from an Rlogin session. |
32 | TermSrv-Bad-Rlogin-Option. The user selected an invalid Rlogin option. |
33 | TermSrv-Not-Enough-Resources. The MAX TNT has insufficient resources for the terminal-server session. |
34 | No description available. |
35 | MPP-No-NULL-Msg-Timeout. The MAX TNT did not receive an MP+ keepalive packet, and closed down the session. |
The following codes concern PPP connections. | |
40 | PPP-LCP-Timeout. PPP LCP negotiation timed out while waiting for a response from a peer. |
41 | PPP-LCP-Negotion-Failed. There was a failure to converge on PPP LCP negotiations. |
42 | PPP-PAP-Auth-Failed. PPP PAP authentication failed. |
43 | PPP-CHAP-Auth-Failed. PPP CHAP authentication failed. |
44 | PPP-Rmt-Auth-Failed. Authentication failed from the remote server. |
45 | PPP-Rcv-Terminate-Req. The peer sent a PPP Terminate Request. |
46 | PPP-Rcv-Close-Event. LCP got a close request from the upper layer while LCP was in an open state. This is a normal, graceful LCP closure. |
47 | PPP-No-NCPs-Open. LCP closed because no NCPs were open. |
48 | PPP-MP-Bundle-Unknown. LCP closed because it could not determine to which MP bundle it should add the user. |
49 | PPP-LCP-Close-MP-Add-Fail. LCP closed because the MAX TNT could not add any more channels to an MP session. |
The following codes are related to immediate Telnet and raw TCP disconnects, and contain more specific information than the Telnet and TCP codes listed earlier in this table. | |
50 | Session-Table-Full. The Raw TCP or Telnet internal session tables are full. |
51 | Out-Of-Resources. Internal resources are full. |
52 | Invalid-IP-Address. The IP address for the Telnet host is invalid. |
53 | Hostname-Resolution-Failed. The MAX TNT could not resolve the hostname. |
54 | Bad-Or-Missing-Port-Number. The MAX TNT detected a bad or missing port number. |
The TCP stack can return the following disconnect codes during an immediate Telnet or raw TCP session. | |
60 | Host-Reset. The host reset the TCP connection. |
61 | Connection-Refused. The host refused the TCP connection. |
62 | Connection-Timeout. The TCP connection timed out. |
63 | Connection-Closed. A foreign host closed the TCP connection. |
64 | Network-Unreachable. The TCP network was unreachable. |
65 | Host-Unreachable. The TCP host was unreachable. |
66 | Network-Unreachable-Admin. The TCP network was administratively unreachable. |
67 | Host-Unreachable-Admin. The TCP host was administratively unreachable. |
68 | Port-Unreachable. The TCP port was unreachable. |
The following are additional disconnect codes. | |
100 | Session-Timeout. The session timed out because there was no activity on a PPP link. |
101 | Invalid-Incoming-User. The session failed for security reasons, such as an invalid incoming user. |
102 | Callback enabled and required. |
103 | Callback validation failure. |
105 | ses-teimout-enaps-neg. |
106 | MP-Session-Timeout. |
115 | Far-end device has hung up. |
120 | Proto-Disabled-Or-Unsupported. One end refused the call because the protocol was disabled or unsupported. |
150 | Disconnect-Req-By-RADIUS. RADIUS requested the disconnect. |
151 | Disconnect-Req-By-Local-Admin. Call disconnected by local administrator. |
152 | Call disconnected by local SNMP command. |
160 | V110-Timeout-Sync-Retry-Exceed. |
170 | PPP-Auth-Timeout-Exceeded. PPP authentication has timed out. |
171 | TAOS-disc-PPP-release. |
180 | User-Executed-Do-Hangup. The call disconnected as the result of a local hangup. |
181 | call-cleared-by-TAOS. |
185 | Remote-End-Hung-Up. The call disconnected because the remote end hung up. |
190 | Resource-Has-Been-Quiesced. The call disconnected because the T1 line that carried it was quiesced. |
195 | Max-Call-Duration-Reached. The call disconnected because the call duration exceeded the maximum amount of time allowed by Max-Call-Duration. |
210 | TAOS-modem-card-bad. |