Manuals+

EPIC Communication Error Codes

Document Version: VM-0001-09

About this book

This book describes system messages that are issued to the EPIC User & Administrator and system messages that are recorded in the EPIC log files.

Who this book is for

This book is intended for people who need to understand and make use of system messages issued by EPIC.

What you need to use this book

You should be familiar with using EPIC and you should be familiar with the business processes within your organization and with basic computer operation.

Related Publications

1 Communication Error Codes

1.1 OFTP Cause and Diagnostic Codes

1.1.1 ESID Error Codes

The ESID (End session ID) error codes are set by the OFTP protocol at session termination.

Code (Decimal) Problem Description
00 Normal Session Termination No problem has occurred.
01 Command not recognised An exchange buffer was received, containing an invalid OFTP command. The OFTP monitor at the remote does not conform correctly to the OFTP standard. Get your trading partner to correct the problem at their end.
02 Protocol violation An OFTP command has been received that is invalid at this point in the protocol flow. e.g. an SSID was received inside a file transmission. Get your trading partner to correct the problem at their end.
03 User code not known to system A Start Session (SSID) command contains an unknown or invalid Identification Code. Make sure you and your partner have the EDI codes of the sender and recipient set up correctly.
04 Invalid password A Start Session (SSID) command contains an invalid password. Make sure you and your partner have the Send and Receive passwords set up correctly.
05 Local site emergency close down There is an emergency shutdown in process and sessions are being terminated.
06 Command contained invalid data An OFTP command contained invalid data, e.g. a field that should contain a 'Y' or 'N' contained something else; or a numeric field contained alphabetic characters.
07 Exchange Buffer size error An exchange buffer has been received that has an invalid size. If the exchange buffer contains an OFTP data command, then the exchange buffer size exceeds that negotiated at session start-up. If the exchange buffer contains an OFTP command then the size of the exchange buffer is inconsistent with the size of the OFTP command.
08 Resources not available While processing an OFTP command, resources needed within the computer system could not be made available. e.g. memory allocation for the processing of a received OFTP exchange buffer could not be allocated. This type of problem is machine dependent and can normally be overcome by retrying the communications.
09 Time-out An OFTP command has not been acknowledged for a significant period of time. Normally this is caused by computer overload at the remote end or an invalid configuration, either locally or remotely.
10 Mode or capabilities This situation can occur when both OFTPs specify 'incoming only' or both specify 'outgoing only' for the direction of file transfer. Clearly it is not practical to continue in such an event.
11 Invalid challenge The Authentication Response (AURP) to an Authentication Challenge (AUCH) command was not correctly signed. This is probably because the wrong certificate has been used.
12 Secure authentication required In the Start Session (SSID) command, the caller has requested authentication but the trading partner does not support it. Agree between yourselves whether authentication is to be used.
99 Unspecified abort code An error or event occurred for which no specific code is defined.

1.1.2 SFNA/EFNA Error Codes

These codes are set during communications by the OFTP protocol at the start of a file (SFNA = Start File Negative Acknowledgement) and end of a file (EFNA = End File Negative Acknowledgement).

Code (Decimal) Problem Description
00 File successfully processed No problem has occurred.
01 Invalid filename The virtual filename does not contain valid ODETTE characters. Ensure that only upper case alphabetic characters, numbers 0 to 9 and characters & ()-./ are used.
02 Invalid destination The destination EDI code (file or message node) is not profiled in the Comms Manager section of the Administrator.
03 Invalid origin The origin EDI code (file or message node) is not profiled in the Comms Manager section of the Administrator.
04 Storage record format not supported The storage format for the virtual file cannot be supported by the destination. This would occur if, for example, a Variable length record was sent to a machine that could only handle Fixed length records.
05 Maximum record length not supported The maximum record length that the destination machine can handle has been exceeded.
06 File size is too large The file is too large for either the OFTP or the remote site to handle.
10 Invalid record count The 'Number of records' field, stored on the EFID, does not match the number counted during the transmission.
11 Invalid byte count The 'Number of bytes' field, stored on the EFID, does not match the number counted during the transmission.
12 Access method failure The remote site has had a problem storing the virtual file. This is often caused by the receiver running out of disk space.
13 Duplicate file identity The Virtual filename, Date, and Time should be unique. This message states that a second virtual file has been transmitted with exactly the same name, date and time as an existing file.
14 File direction refused A sender only cannot receive a file and vice versa.
15 SFNA: Cipher suite not supported EFNA : Invalid signature If present in a SFNA, the algorithm used to sign/encrypt the file is not supported. Agree with your trading partner which cipher suite you will use. If present in an EFNA, the signature failed verification. The file has become corrupted.
16 SFNA: Encrypted file not allowed EFNA : Decryption failed If present in a SFNA, the receiver does not want files to be encrypted. If present in an EFNA, the file could not be decrypted. It has become corrupted.
17 SFNA: Unencrypted file not allowed EFNA : Decompression failed If present in a SFNA, the receiver requires files to be encrypted. If present in an EFNA, the file could not be decompressed. It has become corrupted.
18 Compression not allowed The receiver does not support advanced OFTP compression.
99 Unspecified reason code There has been an error that does not fit into any of the above categories.

1.1.3 ISDN Clearing Cause Codes

These codes appear as a result of an ISDN call clearing.

Code (Hex) Code (Dec) Description
00 00 No cause available.
01 01 Unassigned (unallocated) number.
02 02 No route to specified transit network.
03 03 No route to destination.
06 06 Channel unacceptable.
07 07 Call awarded and being delivered in an established channel.
10 16 Normal call clearing.
11 17 User busy.
12 18 No user responding.
13 19 User alerting, no answer.
15 21 Call rejected.
16 22 Number changed.
1A 26 Non-selected user clearing.
1B 27 Destination out of order.
1C 28 Invalid number format.
1D 29 Facility rejected.
1E 30 Response to status enquiry.
1F 31 Normal, unspecified.
22 34 No circuit/channel available.
26 38 Network out of order.
29 41 Temporary failure.
2A 42 Switching equipment failure.
2B 43 Access information discarded.
2C 44 Requested channel not available.
2F 47 Resource unavailable.
31 49 Quality of service unavailable.
32 50 Requested facility not subscribed.
39 57 Bearer capability not authorised.
3A 58 Bearer capability not available.
3F 63 Service or option not available.
41 65 Bearer capability not implemented.
42 66 Channel type not implemented.
45 69 Channel type not implemented.
46 70 Only restricted digital info capability available.
4F 79 Service or option not implemented.
51 81 Invalid call reference value.
52 82 Identified channel does not exist.
53 83 A suspended call exists, but not this id.
54 84 Call identity in use.
55 85 No call suspended.
56 86 Call with this id has been cleared.
57 87 Incompatible destination.
5B 91 Invalid transit network selection.
5F 95 Invalid message specified.
60 96 Mandatory information element missing.
61 97 Message type non-existent.
62 98 Message not compatible with call state.
63 99 Info element non existent.
64 100 Invalid info element contents.
65 101 Message not compatible with call state.
66 102 Recovery on time expiry.
6F 111 Protocol error, unspecified.
7F 127 Interworking, unspecified.

1.2 CAPI Errors

These codes indicate problems in CAPI communications.

Code Description
0x0001 NCPI not supported by current protocol, NCPI ignored
0x0002 Flags not supported by current protocol, flags ignored
0x0003 Alert already sent by another application
0x1001 Too many applications
0x1002 Logical block size too small, must be at least 128 bytes
0x1003 Buffer exceeds 64 Kbytes
0x1004 Message buffer size too small, must be at least 1024 bytes
0x1005 Max. number of logical connections not supported
0x1006 Reserved
0x1007 The message could not be accepted because of an internal busy condition
0x1008 OS Resource error (e.g. no memory)
0x1009 COMMON-ISDN-API not installed
0x100a Controller does not support external equipment
0x100b Controller does only support external equipment
0x1101 Illegal application number
0x1102 Illegal command or subcommand or message length less than 12 octets
0x1103 The message could not be accepted because of a queue full condition
0x1104 Queue is empty
0x1105 Queue overflow, a message was lost
0x1106 Unknown notification parameter
0x1107 The message could not be accepted because of an internal busy condition
0x1108 OS resource error (e.g. no memory)
0x1109 COMMON-ISDN-API not installed
0x110a Controller does not support external equipment
0x110b Controller does only support external equipment
0x2001 Message not supported in current state
0x2002 Illegal Controller/PLCI/NCCI
0x2003 Out of PLCI
0x2004 Out of NCCI
0x2005 Out of LISTEN
0x2006 Out of FAX resources (protocol T.30)
0x2007 Illegal Message parameter coding
0x3001 B1 protocol not supported
0x3002 B2 protocol not supported
0x3003 B3 protocol not supported
0x3004 B1 protocol parameter not supported
0x3005 B2 protocol parameter not supported
0x3006 B3 protocol parameter not supported
0x3007 B protocol combination not supported
0x3008 NCPI not supported
0x3009 CIP Value unknown
0x300a Flags not supported (reserved bits)
0x300b Facility not supported
0x300c Data length not supported by current protocol
0x300d Reset procedure not supported by current protocol
0x3301 Protocol error layer 1 (broken line or B-channel removed by signalling protocol)
0x3302 Protocol error layer 2
0x3303 Protocol error layer 3
0x3304 Another application got that call
0x3311 Connecting not successful (remote station is no FAX G3 machine)
0x3312 Connecting not successful (training error)
0x3313 Disconnected before transfer (remote station does not support transfer mode, e.g. resolution)
0x3314 Disconnected during transfer (remote abort)
0x3315 Disconnected during transfer (remote procedure error, e.g. unsuccessful repetition of T.30 commands)
0x3316 Disconnected during transfer (local tx data underrun)
0x3317 Disconnected during transfer (local rx data overflow)
0x3318 Disconnected during transfer (local abort)
0x3319 Illegal parameter coding (e.g. SFF coding error)
0x3481 Unallocated (unassigned) number
0x3482 No route to specified transit network
0x3483 No route to destination
0x3486 Channel unacceptable
0x3487 Call awarded and being delivered in an established channel
0x3490 Normal call clearing
0x3491 User busy
0x3492 No user responding
0x3493 No answer from user (user alerted)
0x3495 Call rejected
0x3496 Number changed
0x349a Non-selected user clearing
0x349b Destination out of order
0x349c Invalid number format
0x349d Facility rejected
0x349e Response to STATUS ENQUIRY
0x349f Normal, unspecified
0x34a2 No circuit / channel available
0x34a6 Network out of order
0x34a9 Temporary failure
0x34aa Switching equipment congestion
0x34ab Access information discarded
0x34ac Requested circuit / channel not available
0x34af Resources unavailable, unspecified
0x34b1 Quality of service unavailable
0x34b2 Requested facility not subscribed
0x34b9 Bearer capability not authorized
0x34ba Bearer capability not presently available
0x34bf Service or option not available, unspecified
0x34c1 Bearer capability not implemented
0x34c2 Channel type not implemented
0x34c5 Requested facility not implemented
0x34c6 Only restricted digital information bearer capability is available
0x34cf Service or option not implemented, unspecified
0x34d1 Invalid call reference value
0x34d2 Identified channel does not exist
0x34d3 A suspended call exists, but this call identity does not
0x34d4 Call identity in use
0x34d5 No call suspended
0x34d6 Call having the requested call identity has been cleared
0x34d8 Incompatible destination
0x34db Invalid transit network selection
0x34df Invalid message, unspecified
0x34e0 Mandatory information element is missing
0x34e1 Message type non-existent or not implemented
0x34e2 Message not compatible with call state or message type non-existent or not implemented
0x34e3 Information element non-existent or not implemented
0x34e4 Invalid information element contents
0x34e5 Message not compatible with call state
0x34e6 Recovery on timer expiry
0x34ef Protocol error, unspecified
0x34ff Interworking, unspecified

1.3 X.25 Clearing Cause Codes

These codes appear in the X.25 Clear packet.

Code (Hex) Code (Dec) Problem Description
00 00 DTE Clearing The remote cleared the session. If the associated diagnostic code is non zero, then the remote is abnormally terminating the session.
01 01 Number busy All incoming logical channels at the remote are busy. The call should be tried again later.
03 03 Invalid call Invalid call.
05 05 Number unknown An NUA has been specified that does not exist.
09 09 Out of order The equipment at the remote end is not active. Either their computer is powered off or their X.25 link level 2 protocol has not been activated.
0B 11 Access barred The remote is part of a Closed User Group to which you do not belong.
0D 13 Not obtainable Not obtainable.
11 17 Remote procedure error A problem exists between the remote DTE and the network. This is a remote problem and is normally as a result of an invalid remote configuration.
13 19 Local procedure error A problem exists between the local DTE and the network. This is a local problem and is normally as a result of an invalid local configuration.
15 21 RPOA out of order Recognised Public Operating Agency.
19 25 Reverse charging not subscribed Reverse charging not subscribed.
21 33 DTE incompatible call DTE incompatible call.
29 41 Fast select not subscribed Fast select not subscribed.
39 57 Ship absent Ship not in port (offshore).

1.4 X.25 Diagnostic Codes

These codes appear in the X.25 Clear packet as the X.25 clearing diagnostic.

Code (Hex) Code (Dec) Description
00 00 No additional information.
01 01 Invalid P(S).
02 02 Invalid P(R).
10 16 Packet type invalid.
11 17 Packet type invalid for state R1.
12 18 Packet type invalid for state R2.
13 19 Packet type invalid for state R3.
14 20 Packet type invalid for state P1.
15 21 Packet type invalid for state P2.
16 22 Packet type invalid for state P3.
17 23 Packet type invalid for state P4.
18 24 Packet type invalid for state P5.
19 25 Packet type invalid for state P6.
1A 26 Packet type invalid for state P7.
1B 27 Packet type invalid for state D1.
1C 28 Packet type invalid for state D2.
1D 29 Packet type invalid for state D3.
20 32 Packet not allowed.
21 33 Unidentifiable packet.
22 34 Clear or Call packet received on a PVC.
23 35 Incoming call received on one-way channel.
24 36 Packet on unassigned logical channel.
25 37 Reject not subscribed to.
26 38 Packet received too short.
27 39 Packet received too long.
28 40 Invalid GFI.
29 41 Restart packet on LCN zero.
2A 42 Illegal fast select packet.
2B 43 Unauthorised Interrupt CONF packet received.
2C 44 Unauthorised Interrupt packet received.
30 48 Timer expired : on Clear request.
31 49 Timer Expired; Incoming Call.
32 50 Timer Expired; Clear Indication.
33 51 Timer Expired; Reset Indication.
34 52 Timer Expired; Restart Indication.
40 64 Unspecified Call Set-Up Problem.
41 65 Facility code not allowed.
42 66 Invalid facility parameter.
43 67 Invalid Called Address.
44 68 Invalid Calling Address.
70 112 Inter network problem.
80 128 Reserved for network.
90 144 DTE/DCE congestion.
91 145 Received fast select CLEAR request.
92 146 Line restarting fast select CLEAR request.
93 147 Invalid RESTART conf in state R3.
94 148 Loop trunk lines detected.
95 149 Invalid length trunk restart.
96 150 Call quota distribution clear.
97 151 Reconnect multiple race.
98 152 Reconnect time-out.
9F 159 Network table overflow.
A0 160 Non-zero RESET cause from DTE.
A1 161 Data packet too long.
A2 162 INTERRUPT packet too long.
A2 162 DTE not operational.
A3 163 INT. packet too short, no user data.
A4 164 INT. confirmation packet too long.
A5 165 RR packet too long.
A5 165 RNR packet too long.
A7 167 RESET packet too long.
A8 168 RESET confirmation packet too long.
A9 169 Invalid Q bit in data packet.
AA 170 Packet window range exceeded.
AB 171 Invalid P(S).
AC 172 Invalid P(R)
AF 175 RESET packet to short, no cause.
B0 176 REJECT packet too long.
B5 181 Bad data transfer state in reconnect.
B6 182 Packet format invalid.
B7 183 FACILITY byte count too large.
B8 184 Invalid packet detected.
B9 185 FACILITY/UTILITY field byte count > 63.
BA 186 Outgoing calls barred.
BB 187 Incoming calls barred.
BC 188 Clearing of PVC.
BD 189 Called address too long.
BE 190 Called address too short.
BF 191 Calling address too short.
C3 192 User data field too long.
C4 193 No buffer available.
C6 194 FACILITY negotiation invalid.
C7 195 Mandatory utility not input.
C8 196 Buffer not available for TNIC.
C9 197 Overflow of TNIC in buffer.
CA 198 DTE line congested.
CB 199 Table error in packet procedures.
CC 200 Insert table overflow.
CD 201 Delete table overflow.
D3 211 Invalid event in state D1.
D4 212 Call collision on trunk line.
D5 213 No buffer available in end control block.
D6 214 Call collision on DTE line.
D7 215 DTE restart.
D8 216 Call request to trunk line time-out.
D9 217 Reconnect set-up timed out.
DA 218 Invalid output side state.
DB 219 Error detected in blind packet Q proc.
DC 220 RESET ind. re transmission count expired.
DD 221 Invalid output side state.
DE 222 Blind buffer queue overflow in state D4.
DF 223 Blind buffer queue overflow in state C1.
E0 224 Blind buffer queue overflow in state C2.
E1 225 CLEAR packet byte count invalid.
E2 226 Non-zero CLEAR cause.
E4 228 Call collision.
E5 229 Invalid TP load request call packet.
E7 231 Routing loop detected.
E8 232 PVC call request failure.
E9 233 Reconnect call request failed.
EC 236 Call redirection CLEAR.
ED 237 No path to route call.
EE 238 Call routed to DTE line.
EF 239 Call cannot be re-routed.
F0 240 Address not in routing tables.
F1 241 Routing table change during call routing.
F2 242 No LC available on fake trunk.
F3 243 Remote DTE down on a PVC.
F4 244 Invalid control block event detected.
F5 245 Invalid packet received : state D4.
F6 246 Invalid packet received : state D5.
F7 247 Invalid packet received : state P8.
F8 248 Internal processing failure.
F9 249 Invalid RESTART indication received.
FA 250 Line status change in state R5.
FB 251 Invalid packet received : state R5.
FC 252 Invalid packet received : state R4.
FD 253 Line status change in state R3.
FE 254 Line status change in state R2.
FF 255 Line status change in state R1.

PDF preview unavailable. Download the PDF instead.

VM-0001-09 Communications Error Codes Microsoft Office Word 2007 Microsoft Office Word 2007

Related Documents

Preview EPIC ES-L200 Series Intelligent Smart Locker User Manual
Comprehensive user manual for the EPIC ES-L200 and ES-L200C intelligent smart lockers, detailing product components, safety, user modes, PIN and card management, master settings, specifications, warranty, troubleshooting, and additional features.
Preview EPIC ER82W | ER82SS 7.5 cu.ft. Refrigerator User Manual and Installation Guide
Comprehensive guide for the EPIC ER82W and ER82SS 7.5 cu.ft. refrigerator, covering installation, operation, care, troubleshooting, and warranty information from Stirling Marathon Limited.
Preview EPIC Horizontal Rim Lock Installation Guide (100 & 300 Series)
Step-by-step installation guide for the EPIC Horizontal Rim Lock, covering models in the 100 and 300 Series. Includes parts identification and assembly instructions.
Preview The One Big Beautiful Bill: Impact on Employer-Sponsored Health & Welfare Programs
Analysis of the 'One Big Beautiful Bill' signed into law on July 4, 2025, detailing its key provisions and impacts on employer-sponsored health and welfare programs, including changes to HSAs, ICHRAs, telehealth, and ACA premium tax credits.
Preview EPIC ES-K70 Digital Door Lock User Manual
User manual for the EPIC ES-K70 Digital Door Lock, covering installation, operation, PIN registration, RFID card management, and troubleshooting.
Preview EPIC ES-T153 Digital Door Lock User Manual - Installation, Registration, and Deletion Guide
Comprehensive user manual for the EPIC ES-T153 Digital Door Lock. Learn how to register and delete PIN numbers and RFID cards, product specifications, and safety precautions.
Preview EPIC EasyScan™ M10 Handheld 3D Laser Scanning System User Manual
Comprehensive user manual for the EPIC EasyScan™ M10 handheld SLAM 3D laser scanning system, covering product overview, technical specifications, installation, operation, data collection, and maintenance.
Preview EPIC ES-7000K Digital Door Lock User Manual
User manual for the EPIC ES-7000K Digital Door Lock, covering RFID card registration, guest PIN registration, remote control registration, deletion, and various security and notification settings.