3.Troubleshooting
Code
0-23
Too many errors during reception
0-30
The other terminal did not reply to
NSS(A) in AI short protocol mode
0-32
The other terminal sent a DCS, which
contained functions that the receiving
machine cannot handle.
0-33
The data reception (not ECM) is not
completed within 10 minutes.
0-52
Polarity changed during communication
0-55
FCU does not detect the SG3.
0-56
The stored message data exceeds the
capacity of the mailbox in the SG3.
0-70
The communication mode specified in
CM/JM was not available
(V.8 calling and called terminal)
0-74
The calling terminal fell back to T.30
mode, because it could not detect ANSam
26
Meaning
Suggested Cause/Action
bits 0 and 1
•
Check the line connection.
•
Replace the FCU.
•
Defective remote terminal
•
Check for line noise or other line problems.
•
Try asking the other end to adjust their tx level.
•
Try adjusting the rx cable equalizer setting and/or rx
error criteria.
Cross reference
•
Rx cable equalizer - G3 Switch 07 (PSTN)
•
Rx error criteria - Communication Switch 02, bits 0
and 1
•
Check the line connection.
•
Try adjusting the tx level and/or cable equalizer
settings.
•
The other terminal may not be compatible.
Cross reference
•
Dedicated tx parameters - Section 4
•
Check the protocol dump list.
•
Ask the other party to contact the manufacturer.
•
Check the line connection.
•
The other terminal may have a defective
modem/FCU.
•
Check the line connection.
Retry communication.
•
FCU firmware or board defective.
•
SG3 firmware or board defective.
•
SG3 firmware or board defective.
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.
•
The calling terminal could not detect ANSam due to
noise, etc.