Ascend Progress and Disconnect Codes

This chapter contains the following sections:

Ascend progress codes

Ascend disconnect-cause codes

Ascend progress codes
Ascend disconnect-cause codes

Ascend progress codes

Table 3-1 explains the Ascend progress codes.

Table 3-1. Ascend progress codes

Code

Explanation

0

No progress.

1

Not applicable.

2

The progress of the call is unknown.

10

The call is up.

30

The modem is up.

31

The modem is waiting for DCD.

32

The modem is waiting for result codes.

40

The terminal-server session has started up.

41

The MAX TNT is establishing the TCP connection.

42

The MAX TNT is establishing the immediate Telnet connection.

43

The MAX TNT has established a raw TCP session with the host. This code does not imply that the user has logged into the host.

44

The MAX TNT has established an immediate Telnet connection with the host. This code does not imply that the user has logged into the host.

45

The MAX TNT is establishing an Rlogin session.

46

The MAX TNT has established an Rlogin session with the host. This code does not imply that the user has logged into the host.

50

Active modem outdial call.

60

The LAN session is up.

61

LCP negotiations are allowed.

62

CCP negotiations are allowed.

63

IPNCP negotiations are allowed.

65

LCP is in the Open state.

66

CCP is in the Open state.

67

IPNCP is in the Open state.

Codes 69 through 77 are LCP progress codes. Refer to the RFC 1331 state transition table.

69

LCP is in the Initial state.

70

LCP is in the Starting state.

71

LCP is in the Closed state.

72

LCP is in the Stopped state.

73

LCP is in the Closing state.

74

LCP is in the Stopping state.

75

LCP is in the Request Sent state.

76

LCP is in the ACK Received state.

77

LCP is in the ACK Sent state.

80

IPXNCP is in the Open state.

81

AT NCP is in the Open state.

101

ID Authentication failed.

102

During ID Authentication the RADIUS server did not respond.

120

Frame Relay LMI negotiations in progress.

121

Frame Relay link has end-to-end connectivity and PVCs can pass data.

Code	Explanation
0	No progress.
1	Not applicable.
2	The progress of the call is unknown.
10	The call is up.
30	The modem is up.
31	The modem is waiting for DCD.
32	The modem is waiting for result codes.
40	The terminal-server session has started up.
41	The MAX TNT is establishing the TCP connection.
42	The MAX TNT is establishing the immediate Telnet connection.
43	The MAX TNT has established a raw TCP session with the host. This code does not imply that the user has logged into the host.
44	The MAX TNT has established an immediate Telnet connection with the host. This code does not imply that the user has logged into the host.
45	The MAX TNT is establishing an Rlogin session.
46	The MAX TNT has established an Rlogin session with the host. This code does not imply that the user has logged into the host.
50	Active modem outdial call.
60	The LAN session is up.
61	LCP negotiations are allowed.
62	CCP negotiations are allowed.
63	IPNCP negotiations are allowed.
65	LCP is in the Open state.
66	CCP is in the Open state.
67	IPNCP is in the Open state.
Codes 69 through 77 are LCP progress codes. Refer to the RFC 1331 state transition table.
69	LCP is in the Initial state.
70	LCP is in the Starting state.
71	LCP is in the Closed state.
72	LCP is in the Stopped state.
73	LCP is in the Closing state.
74	LCP is in the Stopping state.
75	LCP is in the Request Sent state.
76	LCP is in the ACK Received state.
77	LCP is in the ACK Sent state.
80	IPXNCP is in the Open state.
81	AT NCP is in the Open state.
101	ID Authentication failed.
102	During ID Authentication the RADIUS server did not respond.
120	Frame Relay LMI negotiations in progress.
121	Frame Relay link has end-to-end connectivity and PVCs can pass data.

Ascend disconnect-cause codes

Table 3-2. Ascend disconnect-cause codes


Code	Description
0	No reason.
1	The event was not a disconnect.
2	The reason for the disconnect is unknown. This code can appear when the remote connection goes down.
3	The call has disconnected.
4	ID authentication has failed.
5	RADIUS timeout during ID authentication.
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.
9	No modems available.
10	The modem never detected DCD.
11	The modem detected DCD, but became inactive.
12	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	The user exited normally from the terminal server.
21	The user exited from the terminal server because the idle timer expired.
22	The user exited normally from a Telnet session.
23	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	The user exited normally from a raw TCP session.
25	The login process ended because the user failed to enter a correct password after three attempts.
26	The raw TCP option is not enabled.
27	The login process ended because the user typed Ctrl-C.
28	The terminal-server session has ended.
29	The user closed the virtual connection.
30	The modem outdial virtual connection has ended.
31	The user exited normally from an Rlogin session.
32	The user selected an invalid Rlogin option.
33	The MAX TNT has insufficient resources for the terminal-server session.
35	The MAX TNT did not receive an MP+ keepalive packet, and closed down the session.
The following codes concern PPP connections.
40	PPP LCP negotiation timed out while waiting for a response from a peer.
41	There was a failure to converge on PPP LCP negotiations.
42	PPP PAP authentication failed.
43	PPP CHAP authentication failed.
44	Authentication failed from the remote server.
45	The peer sent a PPP Terminate Request.
46	LCP got a close request from the upper layer while LCP was in an open state. This is a normal, graceful LCP closure.
47	LCP closed because no NCPs were open.
48	LCP closed because it could not determine to which MP bundle it should add the user.
49	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	The Raw TCP or Telnet internal session tables are full.
51	Internal resources are full.
52	The IP address for the Telnet host is invalid.
53	The MAX TNT could not resolve the hostname.
54	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	The host reset the TCP connection.
61	The host refused the TCP connection.
62	The TCP connection timed out.
63	A foreign host closed the TCP connection.
64	The TCP network was unreachable.
65	The TCP host was unreachable.
66	The TCP network was administratively unreachable.
67	The TCP host was administratively unreachable.
68	The TCP port was unreachable.
The following are additional disconnect codes.
100	The session timed out because there was no activity on a PPP link.
101	The session failed for security reasons, such as an invalid incoming user.
115	Far-end device has hung up.
120	One end refused the call because the protocol was disabled or unsupported.
150	RADIUS requested the disconnect.
151	Call disconnected by local administrator.
152	Call disconnected by local SNMP command.
170	PPP authentication has timed out.
180	The call disconnected as the result of a local hangup.
185	The call disconnected because the remote end hung up.
190	The call disconnected because the T1 line that carried it was quiesced.
195	The call disconnected because the call duration exceeded the maximum amount of time allowed by Max-Call-Duration.

Table 3-2 explains the Ascend disconnect-cause codes.

techpubs@eng.ascend.com

Ascend Progress and Disconnect Codes

Ascend progress codes

Code

Explanation

Ascend disconnect-cause codes

Code

Description