Error Codes
D0CK 24 SM
Code Meaning Suggested Cause/Action
0-52 Polarity changed during
communication
• Check the line connection.
Retry communication.
0-55 FCU (PCB2) does not detect the SG3.
• FCU (PCB2) firmware or board defective.
• SG3 firmware or board defective.
0-56 The stored message data exceeds
the capacity of the mailbox in the
SG3.
• SG3 firmware or board defective.
0-70 The communication mode specified in
CM/JM was not available
(V.8 calling and called terminal)
• The other terminal did not have a compatible
communication mode (e.g., the other terminal
was a V.34 data modem and not a fax modem.)
• A polling TX file was not ready at the other
terminal when polling RX was initiated from the
calling terminal.
0-74 The calling terminal fell back to T.30
mode, because it could not detect
ANSam after sending CI.
• The calling terminal could not detect ANSam
due to noise, etc.
• ANSam was too short to detect.
• Check the line connection and condition.
• Try making a call to another V.8/V.34 fax.
0-75 The called terminal fell back to T.30
mode, because it could not detect a
CM in response to ANSam (ANSam
timeout).
• The terminal could not detect ANSam.
• Check the line connection and condition.
• Try receiving a call from another V.8/V.34 fax.
0-76 The calling terminal fell back to T.30
mode, because it could not detect a
JM in response to CM
(CM timeout).
• The called terminal could not detect a CM due
to noise, etc.
• Check the line connection and condition.
• Try making a call to another V.8/V.34 fax.
0-77 The called terminal fell back to T.30
mode, because it could not detect a
CJ in response to JM
(JM timeout).
• The calling terminal could not detect a JM due
to noise, etc.
• A network that has narrow bandwidth cannot
pass JM to the other end.
• Check the line connection and condition.
• Try receiving a call from another V.8/V.34 fax.
0-79 The called terminal detected CI while
waiting for a V.21 signal.
• Check for line noise or other line problems.
• If this error occurs, the called terminal falls back
to T.30 mode.
0-80 The line was disconnected due to a
timeout in V.34 phase 2 – line probing.
• The guard timer expired while starting these
phases. Serious noise, narrow bandwidth, or
low signal level can cause these errors.
0-81 The line was disconnected due to a
To Next Page
Loading...
