Error Codes
D361 16 SM
Code Meaning Suggested Cause/Action
0-32
The other terminal sent a
DCS, which contained
functions that the
receiving machine
cannot handle.
Check the protocol dump list.
Ask the other party to contact the
manufacturer.
0-52
Polarity changed during
communication
Check the line connection.
Retry the communication.
0-55
FCE does not detect the
SG3-V34.
FCU firmware or board defective.
SG3-V34 firmware or board defective.
0-56
The stored message
data exceeds the
capacity of the mailbox in
the SG3-V34.
SG3-V34 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.
To Next Page
Loading...
