Faxback NET SatisFAXtion 9.0 - Fax Server Manual Manual de usuario descargar pdf (Pagina 148)

the CLASS1 driver buffers. This would only occur if the calling application was extremely slow and the                

pageswereverysmall.Errortype:NON_RETRYABLE.



1111 Invalid endofpage signal: After receiving page data, the remote unit should send 1 of 6               

differentendofpagecommands.Itsentsomethingelse.Errortype:NON_RETRYABLE.



1112Busy:Abusytonewasdetected.Errortype:BUSY.



1113 No dial tone: By default, the modem will listen for dial tone before trying to place an outbound                  

call. The most common cause of this error is not having a working phone line plugged into this port. If                   

the phone lines do not provide dial tone, the modem must be configured to not detect dial tone before                  

dialing(seedial_progress_mode).Errortype:NO_DIAL_TONE.



1114 Modem did not detect fax device on answering side: The modem returned something other              

than CONNECT, BUSY or NO DIALTONE while dialing. This usually indicates the answering side was not a                

faxmachine.Errortype:NO_ANSWER.



1115 No Answer, remote device did not respond to handshake: The call connected but the              

remote device failed to respond to repeated attempts to handshake. The timer is 35 seconds. Error               

type:RETRYABLE.



1116 Remote fax cannot receive: The remote fax device is configured to not receive faxes. Error               

type:NON_RETRYABLE.



1117 Can’t agree on bit rate: The modem and the remote unit couldn’t fall back to or agree upon                  

anybitrate.Thisismostoftencausedbypoorlinecondition.Errortype:RETRYABLE.



1118 Wrong response after training: After sending 1.5 seconds of training data, the remote unit              

shouldhavesentaCFRorFTTframe.Itsentsomethingelse.Errortype:RETRYABLE.



1119 No FTT or CFR received after 3 DCS/training sequences: The call connected and fax              

communication was established. The receiving and sending devices exchanged CSI/DIS and          

TSI/DCS/training signals. After that, the receive side is expected to send a CFR (confirmation) or FTT               

(failure to train), it did neither. Handshaking was attempted and failed twice more, at which point IPFax                

terminatedthecall.Errortype:RETRYABLE.



1120 No response after sending 3 end of page commands: After reaching the end of the page,                

an endofpage command (MPS) is sent and an acknowledgment (MCF) is expected from the remote              

device. The MCF was not received. The MPS was attempted twice more. After the third failure to                

respond,the call was terminated. This can be caused by the remote device hanging up, line impairment               

such that the modem could not detect and encode the MCF command, or line noise such that our MPS                  

wasnotdetectedbytheremotedevice.Errortype:RETRYABLE.



1121 Invalid response after endofpage: After sending the end of page command to the remote,              

the remote should have sent a MCF, PIP, RTP, PIN, or RTN response. It sent something else. Error                 

type:RETRYABLE.



1122 Receiver sent DCN: Normally, the receiver should never send a DCN disconnect signal. This              

could be due to line impairment causing a timeout on the receive side, or a user manually pressing a                  

cancelbuttononthereceivingfaxmachine.Errortype:RETRYABLE.



1123 Modem does not support any of the configured receive baud rates: The driver has been               

setup to allow only a certain number of allowed send baud rates, but the modem does not support any                  

of them. An example would be where a user does not want to send a fax slower than 12000 baud, but                    

themodemonlysupports9600baudasitshighestbaudrate.Errortype:NON_RETRYABLE.



1127 Remote device does not support fax: The remote modem indicated it is not capable of faxing.                

Errortype:NON_RETRYABLE.



1128 Invalid response to ECM block: The valid responses from the remote following the             

transmission of an ECM block should be RNR, PPR or MCF. Some other signal was received. Error type:                 

RETRYABLE.



1129 Remote fax not ready for next page: The T5 timeout (60 seconds ± 5 seconds) occurred                

whileexchangingRRandRNRsignalsforanECMsend.Errortype:RETRYABLE.



1130 No response to ECM endofpage: The sender had received a RNR at which time it responds                

with an RR signal. It then expects the remote to send either a RNR or an MCF within T4 seconds. There                    

ProprietaryFaxBack,Inc.2014 148

1 2 ... 143 144 145 146 147 148 149 150 151 152 153 ... 202 203

Comentarios a estos manuales

Sin comentarios

Faxback NET SatisFAXtion 9.0 - Fax Server Manual Manual de usuario Pagina 148

Comentarios a estos manuales

Relacionado con productos y manuales para Software Faxback NET SatisFAXtion 9.0 - Fax Server Manual