Code #

Description of event causing Code # display

Action to take if any

0

Normal Disconnect (V.42 shutdown)

Informational.

1

No Dial Tone detected

Check your telephone line connections. Make sure the port selected is connected to an active line. No dial tone was detected within timeout period.

2

No Answer to Dial Sequence. Dial Tone has been detected and the Dial sequence has been completed. Either a maximum number of rings have occurred or the call did not set up because of a bad dial sequence.

Check the accuracy of the telephone number dialed. If dialing via a PBX make sure that an outside access code such as the digit 9 is dialed before the telephone number of the remote modem.

3

Line Station Busy Signal detected

Remote end is busy. Wait or select another access number.

4

Incoming Call Not Accepted by Protocols

Make sure that RAS is started. It this has, then make sure that at least one of the TCP/IP, NetBEUI, IPX/SPX, DLC, or PPTP protocols are installed in the Operating System. Check the "Protocols" Tab in the Network Icon found on the Control Panel for installed protocols.

5

Sequence Error Detected in the Driver. A program check designed to assure the accurate sequencing of output frames has detected a break in the internal sequence number assignment.

Should not happen. If this condition is repeatable, contact the SrDAPOP vendor via the web page.

6

Data Pump failed to reset after several tries.

Hardware failure. Data Pump most likely requires replacement. Polling for ring indications has been suspended.

7

Ring Indication IGNORED

A Ring has been detected but the line is not enabled to receive calls. Be sure the RAS Server is started for all lines that can received calls. The EQM field in SrDALOG should not be zero and the DeviceState should be OPEN to accept calls.

8

Dial Operation received the answer tone from the remote modem but timed out in the training sequence.

Telephone number /V34 or /V32.

9

Answer Operation timed out in the training sequence.

This may result from unfavorable line conditions or one of the modems may not be configured properly. Tell the remote location to retry the operation.

10

Check for Hang found EQM > 7000h and disconnected the link.

This can result if someone disconnects a line jack during an active connection or the call is dropped at the remote without performing a normal shutdown sequence.

11

A retraining sequence has exceeded timeout limits

Retry connection. Sometimes a retrain or rate renegotiation can get into an endless loop.

12

For a Data call, the call was disconnected because the EQM was greater than 7000h. For a Voice call, the call was disconnected because a network dial tone was detected from the remote side.

This can result if someone disconnects a line jack during an active connection or the call is dropped at the remote without performing a normal shutdown sequence.

13

The XID sequence was not received after answering a call and negotiating a HDLC framing state.

Retry operation. Possible software or hardware problems with the remote modem.

14

TDBIA detected in SrDA Idle state

Make sure the BIOS is set to allow the selected IRQ to be assigned to the SrDAPOP ISA bus. Reboot and reset the BIOS if necessary. Also make sure the jumper on the IRQ Share pins on the SrDAPOP adapter card is in place. If this jumper is missing then the driver will not recognize interrupts. If this still fails to fix the problem, then try another available IRQ setting. Refer to the Hardware Jumper Locations section in the User's Manual.

15

RDBIA detected in SrDA Idle state

Make sure the BIOS is set to allow the selected IRQ to be assigned to the SrDAPOP ISA bus. Reboot and reset the BIOS if necessary. Also make sure the jumper on the IRQ Share pins on the SrDAPOP adapter card is in place. If this jumper is missing then the driver will not recognize interrupts. If this still fails to fix the problem, then try another available IRQ setting. Refer to the Hardware Jumper Locations section in the User's Manual.

16

NSIA detected in SrDA Idle State

Make sure the BIOS is set to allow the selected IRQ to be assigned to the SrDAPOP ISA bus. Reboot and reset the BIOS if necessary. Also make sure the jumper on the IRQ Share pins on the SrDAPOP adapter card is in place. If this jumper is missing then the driver will not recognize interrupts. If this still fails to fix the problem, then try another available IRQ setting. Refer to the Hardware Jumper Locations section in the User's Manual.

17

NCIA detected in SrDA Idle State

See description for code 16.

18

NEWS detected in SrDA Idle State

See description for code 16.

19

RLSD was unexpectedly dropped and was detected via a normal interrupt condition.

This can result if someone disconnects a line jack during an active connection or the call is dropped at the remote without performing a normal shutdown sequence.

20

Receiving HDLC flags while in an Asynchronous mode

Retry call. The remote modem is transmitting HDLC flags without performing a proper V.42 ODP/ADP negotiation or has some other software problem.

21

DM frame received

Informational. Some modem V.42 software use this frame to perform a normal shutdown sequence.

22

An answer V.42 XID response was sent but an expected V.42 SABME frame was not received within a timeout period.

Retry call. Line conditions may have caused this missing frame or the remote modem may have a configuration or software problem.

23

A dial side has exchanged XID sequences with a remote and has sent several SABME response frames without receiving a required UA acknowledgment.

Retry call. Line conditions may have caused this missing frame or the remote modem may have a configuration or software problem. Attach /MIN parameter to phone number to reduce the initial receive speed.

24

An answer side has exchanged XID sequences with a remote and has received at least one required SABME and has sent several UA frames but has not received any I frame data within a timeout period.

Informational. In this case, a remote has established and negotiated a V.42 connection, but for some reason has not transmitted any data within the allotted timeframe.

25

A dial side has sent one or more XID sequences and has not received the required XID response from the remote.

Retry call. Line conditions may have caused this missing frame or the remote modem may have a configuration or software problem. Attach /MIN parameter to phone number to reduce the initial receive speed.

26

An answer side has exchanged XID sequences with the dial side but has not received the required SABME frame within the timeout period.

Retry call. Line conditions may have caused this missing frame or the remote modem may have a configuration or software problem.

27

A dial side has exchanged XID sequences and has sent the required SABME frame several times but has not received the UA acknowledgment within the timeout period.

Retry call. Line conditions may have caused this missing frame or the remote modem may have a configuration or software problem. Attach /MIN parameter to phone number to reduce the initial receive speed.

28

REJ response not received. A retransmission request has not been satisfied within the timeout period.

Retry call. Line conditions may have caused this missing frame or the remote modem may have a configuration or software problem.

29

An answer side has exchanged XID sequences with the dial side but has not received the required SABME frame within the timeout period.

Retry call. Line conditions may have caused this missing frame or the remote modem may have a configuration or software problem.

30

V.42 shutdown sequence not completed

The remote shut down prematurely.

31

Unable to send V.42 DISC shutdown frame

The remote shut down prematurely.

32

Unable to send V.42 XID frame

Congestion due to retrain or line failure prevented the dispatch of this frame.

33

Attempted to Dial when DataPumpState is not Idle

Retry call. SrDAPOP could still be performing the previous shutdown sequence.

34

Attempted Send Packet with no Packet Descriptor assigned

Internal audit failure.

35

Unable to launch LapM XID Sequence (Answer Side)

Congestion due to retrain or line failure prevented the dispatch of this frame.

36

Unable to launch LapM SABME sequence

Congestion due to retrain or line failure prevented the dispatch of this frame.

37

Unable to launch LapM UA Sequence

Congestion due to retrain or line failure prevented the dispatch of this frame.

38

Unable to launch Cr Lf in Generic Log on Sequence

Congestion due to retrain or line failure prevented the dispatch of this frame.

39

Unable to launch RR_RESP Seq

Congestion due to retrain or line failure prevented the dispatch of this frame.

40

Unable to launch LapM RR_RESP Seq

Congestion due to retrain or line failure prevented the dispatch of this frame.

41

Unable to launch LapM REJ Seq

Congestion due to retrain or line failure prevented the dispatch of this frame.

42

Unable to launch RR RESP to RR

Congestion due to retrain or line failure prevented the dispatch of this frame.

43

Unable to launch LapM RR Seq

Congestion due to retrain or line failure prevented the dispatch of this frame.

44

Unable to launch RR RESP to RNR

Congestion due to retrain or line failure prevented the dispatch of this frame.

45

Unable to launch RR RESP to REJ

Congestion due to retrain or line failure prevented the dispatch of this frame.

46

Unable to launch LapM UA sequence

Congestion due to retrain or line failure prevented the dispatch of this frame.

47

Unable to launch LapM UA sequence

Congestion due to retrain or line failure prevented the dispatch of this frame.

48

Unable to launch LapM SABME sequence in response to a FRMR.

Congestion due to retrain or line failure prevented the dispatch of this frame.

49

Unable to launch LapM RR sequence

Congestion due to retrain or line failure prevented the dispatch of this frame.

50

Unable to launch LapM UA sequence in response to a DISC.

Congestion due to retrain or line failure prevented the dispatch of this frame.

51

Unable to launch LapM UA sequence in response to a SABME.

Congestion due to retrain or line failure prevented the dispatch of this frame.

52

Unable to launch LapM SABME sequence in response to a FRMR.

Congestion due to retrain or line failure prevented the dispatch of this frame.

53

Unable to launch LapM FRMR sequence.

Congestion due to retrain or line failure prevented the dispatch of this frame.

54

Unable to launch LapM RR sequence in response to hardware OE condition.

Congestion due to retrain or line failure prevented the dispatch of this frame.

55

Reset State pending the closing of all calls.

Special condition for debug version of SrDAPOP.

56

Unable to launch LapM XID sequence again.

Congestion due to retrain or line failure prevented the dispatch of this frame.

57

Unable to launch LapM SABME sequence again.

Congestion due to retrain or line failure prevented the dispatch of this frame.

58

Unable to launch LapM SABME sequence again.

Congestion due to retrain or line failure prevented the dispatch of this frame.

59

Unable to launch LapM UA sequence again.

Congestion due to retrain or line failure prevented the dispatch of this frame.

60

Unable to launch LapM XID sequence again. (Dial Side)

Congestion due to retrain or line failure prevented the dispatch of this frame.

61

Unable to launch LapM XID sequence again. (Answer Side)

Congestion due to retrain or line failure prevented the dispatch of this frame.

62

Unable to launch LapM SABME sequence in Dial Side after XID exchange.

Congestion due to retrain or line failure prevented the dispatch of this frame.

63

Unable to launch LapM RR Sequence after timeout waiting for a RR RESP frame.

Congestion due to retrain or line failure prevented the dispatch of this frame.

64

LapMTimer Unable to launch LapM RR Seq after timeout waiting for a REJ RR RESP frame.

Congestion due to retrain or line failure prevented the dispatch of this frame.

65

Unable to launch LapM SABME sequence again

Congestion due to retrain or line failure prevented the dispatch of this frame.

66

Unable to launch LapM RR sequence in normal CONNECTED state.

Congestion due to retrain or line failure prevented the dispatch of this frame.

67

Unable to launch LapM DISC sequence again.

Congestion due to retrain or line failure prevented the dispatch of this frame.

68

The negotiated speed was less than 1200. The call was dropped.

The Rockwell Data Pump will sometimes accept an otherwise failed call with an RLSD up indication. This is an error. To prevent this, SrDAPOP will not accept any negotiated speeds less than 1200.

69

Undefined LapM Send Packet command

Internal audit failure.

70

Data Pump Failed to reconfigure

Hardware failure. May require replacement of Data Pump device.

71

Initial Dial Tone Detection Failed.

Dial Tone was not detected after first two seconds of off hook time. Program retries after another two seconds. After three retries, this code will change to a 1 if dial tone is still undetected.

72

PPP negotiation time out

PPP negotiation did not complete within timeout limits. Redial the connection. If Call Back is being used, then do not delay the entry of the Call Back telephone number. You can override the timeout period by appending parameter /PPP to the telephone number dialed.

73

Data Pump Failed to Reset

Hardware failure. May require replacement of Data Pump device. After repeated failures this code will be reset to the value 6.

74

Unidentified Frames Dropped during V.42 XID exchange.

Possible software error on remote side or unusual line errors. If connection fails - retry again.

75

A SrDAPOP Data Pump device is either not Installed or is not working properly.

Possible serious hardware failure. Usually this is simply a problem with the assignment of Base IO address or Interrupt Number for this SrDAPOP adapter.

76

V.42bis Negotiation Error - Either the negotiated number of codewords or maximum string length ended up equal to zero.

Possible remote software error. System will attempt to connect without V.42bis

77

A Tapi Drop Call was received after a Tapi Close Call

Informational. Microsoft warns that this may happen.

78

A ClearDown sequence was received on a modulation scheme other than K56Flex/ V.34/V.32/V.22

Informational

79

Reset NSIE in Connected State

Internal audit failure.

80

Remote side answered dialing sequence but the calling side did not detect the correct answer tone within a specific timeout period.

Check the telephone number for accuracy and redial. The remote end may not have the telephone line connected to an answering modem. Manually place the call and determine if an answer tone is set or someone answers.

81

Data Pump Controller part number does not match a list of valid part numbers.

During initial startup, the Rockwell Data Pump Controller and DSP part numbers are read from the device and compared to a list of valid part numbers. Sometimes these values will not be read properly on a restart other than a full power off and on restart. Next time the system is rebooted first shut off the power and perform a full power on reboot. The part number displayed in the MASK field on the SrDAlog panel is the actual number read if valid or is the default number used for further processing. If this is not the correct number then power down and reboot.

82

Data Pump DSP part number does not match a list of valid part numbers.

Startup code failed to read a valid DSP part number during startup. Informational – may be important if other failures occur.

83

Interrupt Assignment Not Available

The assigned Interrupt Number for this SrDAPOP Adapter is not available because it is not reserved for Legacy ISA use by the System BIOS or it is also assigned to another device on this system. Shut down your computer, reboot, inspect the BIOS setup and make sure the assigned Interrupt Number is reserved for Legacy ISA use and not included in the Plug & Play category.

84

Runaway Count Expired on Data Pump Start Up

Warning – This may indicate a malfunctioning Data Pump. If the Data Pump fails on subsequent calls replace the Data Pump on the indicated port.

85

The remote Rate Mask does not support the requested rate renegotiation rate.

Informational. For some reason the remote indicated that it did not support the requested rate.

86

An NSIA interrupt occurred and no reason was provided to the DPC routine.

Internal audit failure.

87

LapM Information Length Exceeded in LapM processing

Informational. For some reason the length of the LapM packet exceeded the negotiated max length.

88

BRKD detected in synchronous mode

BRKD = Synchronous Break sequence.

89

V.42bis Decode Dictionary Update Error Detected

Possible software error on remote side. Try redial without specifying V42+ on Dial Input

90

V.42bis Decode Dictionary Audit Error

Possible SrDA Software error. Try redial without specifying V42+ on Dial Input.

91

V.42bis Decode Escape Sequence Error

Possible software error on remote side. Try redial without specifying V42+ on Dial Input

92

V.42bis Decode Maximum String Length Exceeded

Possible software error on remote side. Try redial without specifying V42+ on Dial Input

93

HDLC Packet Size exceeds LAPM parameter.

Possible software error on remote side. The HDLC FCS checks out but the data length exceeds the negotiated LAPM packet size.

94

Decode Input Buffer Overrun. There are more than 1500 characters between PPP flag bytes.

Possible software error on remote side. Try redial without specifying V42+ on Dial Input if using V42+.

95

V.42bis Decode Dictionary Recovery Error - Child Count is incorrect

Possible software error. Try redial without specifying V42+ on Dial Input.

96

An Asynchronous connection was dropped because no data was exchanged within the timeout period

Redial or reconnect and send data.

97

CTS is down after a V.42 T400 timeout expired

Line dropped during V.42 initial negotiation. Retry call attempt.

98

Packet Count Maximum Exceeded

Internal audit failure.

99

Remote answering end responded with V.42bis parameters when not requested by the originating dialing end.

The originating end did not request V.42bis on XID exchange but the answering end responded as if it was requested and thus accepted. This response is ignored.

100

Modem Clear Down Operation

Informational. Normal Asynchronous shutdown.

101

V.42bis Decode search exceeds child count.

Internal audit failure

102

V.42bis Decode dictionary chain invalid

Internal audit failure

103

V.42bis Encode search exceeds child count.

Internal audit failure

104

V.42bis Encode dictionary chain invalid

Internal audit failure

105

V.42bis Encode Encode Count > Max String Length

Internal audit failure

106

V.42bis Encode Encode Count > Max String Length during Flush operation

Internal audit failure

107

V.42bis Encode TxData Buffer overrun

Internal audit failure

108

V.42bis Encode Invalid string code less than 3

Internal audit failure

109

V.42bis Encode No Leaf nodes remain in dictionary for dictionary recovery.

Internal audit failure

110

V.42bis Encode A Leaf node has a Start Chain pointer

Internal audit failure

111

V.42bis Encode A Parent node has an invalid pointer to a single child node.

Internal audit failure

112

V.42bis Encode A Leaf node has a Start Chain pointer

Internal audit failure. Same as 110 but different audit location

113

V.42bis Encode Child Count exceeded while updating the Child Chain

Internal audit failure

114

V.42bis Decode Parent Node has no Start Chain pointer

Internal audit failure

115

V.42bis Decode No Leaf nodes remain in dictionary for dictionary recovery

Internal audit failure

116

V.42bis Decode A Leaf node has a Start Chain pointer

Internal audit failure

117

V.42bis Decode A Parent node has an invalid pointer to a single child node

Internal audit failure

118

V.42bis Decode A Leaf node has a Start Chain pointer

Internal audit failure. Same as 114 but different audit location

119

V.42 LapM frame recovered

A run on HDLC frame has been recovered from the input data stream.

120

Data Pump HDLC processing - Dropped SYNCD recovered

Successful data recovery operation

121

Data Pump HDLC processing - Negotiated V.42 frame length exceeded

Informational – Sometimes these conditions are recovered in later processing.

122

Asynchronous Processing Frame buffer exceeded

A line condition during asynchronous transmission can create extra data between PPP flag bytes that will cause a buffer overrun.

123

V.42bis Unable to allocate space for Decode dictionary

Windows NT has run out of unpaged memory

124

V.42bis Unable to allocate space for Encode dictionary

Windows NT has run out of unpaged memory

125

V.42bis Software PPP CRC error

Informational - This can either be caused by a software problem at the remote end or the V.42bis dictionaries are out of synchronization.

126

Unidentified keyword data found in Dial String

Check Dial string for invalid Keywords and remove any extraneous leading spaces.

127

Attempted to Dial using a disabled port

Select another port

128

Attempted to Dial on a port that is not completely reset and in DataPump Idle state

Wail a bit and redial.

129

No Dial String (Length is zero)

Check Dial String on RAS dialer box

130

Dial String Maximum exceeded

Maximum used. Check the Dial Input data

131

Dial was entered via the Phone Dialer - Ring Simulated

For testing purposes. A single character # dialed using the Phone Dialer can simulate a Hayes ATA command on a selected line.

132

V.42bis receiving strings that are already defined by a codeword in the decode dictionary

Informational – remote software is not doing its job. This error could be followed by a dictionary mismatch condition.

133

V.42bis V42+=Codewords*MaxStringlength

Codewords parameter not within limits default used

134

V.42bis V42+=Codewords*MaxStringlength

MaxStringlength parameter not within limits default used.

135

LAPM = PacketSize*SendWindow

PacketSize parameter must be 128 to 1500.

136

LAPM = PacketSize*SendWindow

SendWindow parameter must be 2 to 15.

137

This data pump does not support parameter on telephone number input line - ignored

K56 option requires a K56Flex SrDAPOP adapter. VFC option requires a NON K56flex SrDAPOP adapter.

138

Completed Board Noise Test.

The values in the LAPM column of the SrDAlog panel contain the result of the Board Noise Test. The values contained in the Rx column contain the number of Noise samples measured.

139

Unidentified Dsp Ram Post Action code.

Internal SrDAPOP audit failure.

140

Invalid modulation symbol rate negotiated during modem training.

Redial. If this error is persistent then try using VFC or V32 dialing parameters to change the negotiation attempt.

141

Duplicate Login: request received in the Generic Log on sequence from the remote.

The second occurrence is ignored. If the call setup is not successful, then retry attempt. For some reason the remote is sending a duplicate.

142

Duplicate Password: request received in the Generic Log on sequence from the remote.

The second occurrence is ignored. If the call setup is not successful, then retry attempt. For some reason the remote is sending a duplicate.

143

Unable to send a response to the Login: request

Retry the call attempt. Try using the MIN parameter to obtain a cleaner connection.

144

Unable to send a response to the Password: request

Retry the call attempt. Try using the MIN parameter to obtain a cleaner connection.

145

RLSD signal received unexpectedly

Active at an unexpected time. Informational.

146

Timeout condition ignored

A timeout occurred during a connected state and was ignored. This may occur just after a retrain or rate renegotiation sequence has completed.

147

Received Unidentified data frame while expecting V.8bis CL message

Most likely caused by line noise, which corrupted the received CL message. If this continues, then the line is not likely to support good K56Flex or V.90 connections. Add /V34 or /V32 after the telephone number on the dial string.

148

Received Unidentified frame while expecting V.8bis MS message

Most likely caused by line noise, which corrupted the received MS message. If this continues, then the line is not likely to support good K56Flex or V.90 connections. This occurs on received calls only.

149

Unable to send V.8bis frame

Unable to send an ACK NAK CL or MS V.8bis data frame. Most likely the connection was disrupted during the call setup.

150

Received V.8bis NAK(1)

The remote informed that a timeout occurred before receipt of an expected V.8bis frame

151

Received V.8bis NAK(2)

The remote informed that it was temporarily unable to invoke the requested V.8bis mode

152

Received V.8bis NAK(3)

The remote informed that it does not support or has disabled the requested V.8bis mode

153

Received Unexpected V.8bis NAK(1)

Most likely data errors early in the V.8bis negotiation sequence caused a frame to drop and the NAK(1) was sent because of a timeout condition.

154

Download Code Keyword DRAM not found

Possible serious program problem or data corruption. Reinstall previous SrDA.SYS driver and rerun. Classifying the datapump as non-downloadable prevents future downloading.

155

Requested Module not present in the data pump download code library

The Module ID is displayed in the CRC field of the SrDALOG monitor. Classifying the datapump as non-downloadable prevents future downloading.

156

A timeout occurred while waiting for the data pump to acknowledge a request to download a Module.

Possible software problem or unusual condition of the data pump. Retry connection. The Module ID is displayed in the CRC field of the SrDALOG monitor. Use V34 or V32 option if this persists.

157

A timeout occurred while waiting for the data pump to provide the check sum CRC of the down loaded Module

Possible software problem or unusual condition of the data pump. Retry connection. The Module ID is displayed in the CRC field of the SrDALOG monitor

158

CRC of the downloaded data pump Module does not match the CRC of the module sent

Possible software problem or unusual condition of the data pump. Retry connection if the call setup failed to complete as expected.

159

A V.8bis CL or MS message is not formatted correctly. The non-standard information field length is not correct.

The remote is not formatting the CL or MS message as expected. This may prevent K56flex connections.

160

The Server does not support Rockwell Version 1.1 level or greater K56Flex.

Some early Rockwell K56Flex servers were released with Version 1.0 code which does not interoperate with LUCENT or SrDAPOP K56Flex Client code.

161

Reconfiguration incomplete. A download Module failed to initialize and continue a training sequence.

Possible software problem or unusual condition of the data pump. Retry connection. If problem persists, then add /V34 or /V32 to the end of the dial string.

162

A requested download Module not available to load from library.

Software problem or unusual condition of the data pump. Classifying the datapump as non-downloadable prevents future downloading.

163

The calculated CRC of the downloaded module does not match the Descriptor CRC

Internal audit failure. The Descriptor CRC module number appears in the FE field.

164

RAM Version Numbers do not match

Internal audit Failure

165

Failed to complete a K56flex connection

Even though the remote confirmed that it was K56flex capable, SrDAPOP was unable to negotiate K56flex because of line impairments. If problem persists, then add /V34 or /V32 to the end of the dial string.

166

K56flex successfully negotiated but the connection was not good enough to sustain a connection.

SrDAPOP falls back to V.34 mode and continues automatically. If problem persists, then add /V34 or /V32 to the end of the dial string.

167

Unidentified V.8bis HDLC data frame received in the current state of the datapump. Data frame is ignored.

Possible V.8bis programming error on the remote or V.8bis options have been implemented which are not meaningful or required.

168

Timeout LINECALLSTATE_DISCONNECTED

Internal audit Failure..

169

A timeout occurred while waiting for the data pump to set RAM_adrcnt to 0xFFFF after requesting a specific module to download.

Possible software problem or unusual condition of the data pump. Retry connection. The Module ID is displayed in the CRC field of the SrDALOG monitor. Use V34 or V32 option if this persists.

170

The remote did not send a Close Call. The driver assummed a Close Call condition and will proceed with ring detection or new calls.

The remote did not conform to published TAPI specifications and close the call as required.

171

Call was rejected by the Operating System

The Microsoft Telephony Service Provider rejected the call. The occurs on the second call for Win 98 systems because Microsoft has limited this operating system to receive only one call. A multilink call counts as one call.

172

No telephone number or unrecognized dial digit was found in the telephone number string

Check the telephone number in the phonebook entry being dialed. If using Win 98, do NOT use area code and dialing properties. Reference the User’s Manual for dialing options.

173

PPP framing error encountered.

FF03 Missing as the first two bytes of the PPP packet. Packet is dropped.

174

PPP protocols refused LCP packet

Voice Call is automatically disconnected. Retry.

175

PPP LCP protocol type code not recognized.

Unrecognized code. Packet is discarded.

176

Voice call PPP PAP failed.

The VoiceUserId and VoicePassword is not accepted by PAP. Set up this account in the proper security data base using User Manager for Domains. This account must have Administrator Priviledges.

177

IP protocol header checksum failure.

Checksum failed. Packet is discarded.

178

ICMP protocol header checksum failure

Checksum failed. Packet is discarded.

179

Received LCP Terminate Request

The operating system sent an LCP Terminate Request command and terminated the LCP link for voice operations. Retry the operation.

180

Unrecognized IP Version and Header Length byte

A value other than a hex 45 or hex 46 was encountered in the IP Version and Header Length fields. Packet is discarded.

181

Dial String Parameter /MAX=MaxSpeed

Error - MaxSpeed must be a number between 9600 and 56000 with no commas. Correct number and redial.

182

V8bis MS Receive Timeout

V.8bis CRd was detected, CL was sent but MS was not received within timeout requirements. This can be caused by poor line conditions or the remote end has software problems. If this persists, try add /V34 after the the dial string telephone number.

183

Training Timed out in Rate Renegotiation

If the circuit connection drops, then reestablish the connection and proceed.

184

Unable to dispatch a timer operation during a retrain operation.

Internal audit error. If the connection drops then reestablish the connection and proceed.

185

Unidentifed packet error status cleared

Internal audit error. If this condition occurs consistently report the circumstances to the vendor.

186

Not assigned

Last entry in the Table.