Faxback NET SatisFAXtion 9.0 - Fax Server Manual Bedienungsanleitung PDF herunterladen (Seite 163)



30088Theportserverisbusy.Errortype:BUSY.



30089Theportserverisbusy.Errortype:BUSY.



4.1.1330209–30266PortafaxDriver

30209 Timed out waiting for a command: During phase B, the T1 timer expired while waiting for                

commandsfromthesendingfaxmachine.Thistimeris35seconds.Errortype:NON_RETRYABLE.



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

type:NON_RETRYABLE.



30211 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:NON_RETRYABLE.



30212 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.



30213 No FTT or CFR received after 3 DCS/training sequences: The call connected and T.38              

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.



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

IPFax sends an endofpage command (MPS) and expects to receive an acknowledgment (MCF) from the              

remote device. IPFax did not receive the MCF and attempted to resend it twice more. After the third                 

failure to respond, IPFax terminated the call. This can be caused by the remote device hanging up                

without notifying the TDM network (POTS lines lack such notification), line impairment such that the              

gateway could not detect and encode the MCF command, line noise such that our MPS was not detected                 

by the remote device, or packet loss such that either the MPS or the response MCF was lost, or latency                   

such that the MCF or MPS was delayed. In the case of packet loss, insure that lowspeed redundancy is                  

enabled.Errortype:RETRYABLE.



30215 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.



30216 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.



30217 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:                 

NON_RETRYABLE.



30218 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.



30219 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                    

wasnoresponsereceived.Errortype:RETRYABLE.



30220 No more baud rates to try: After a 4th ppr signal is received, a CTC signal is sent so as to step                      

down the baud to the next configured baud rate. All configured baud rates have been exhausted. Error                

type:RETRYABLE.



30221NoresponsetoCTC:NoresponseafterCTC.Errortype:RETRYABLE.



30222 Invalid response to CTC: The expected signal after CTC is CTR. Some other signal was               

received.Errortype:RETRYABLE.



30223 Invalid response after ECM block: After receiving an ECM block, the expected signals are              

PPS,CTCorRR.Someothersignalwasreceived.Errortype:NON_RETRYABLE.



30224 Unexpected DCN: During receive, a DCN signal was received at a point where it is not                

ProprietaryFaxBack,Inc.2014 163

1 2 ... 158 159 160 161 162 163 164 165 166 167 168 ... 202 203

Kommentare zu diesen Handbüchern

Keine Kommentare

Faxback NET SatisFAXtion 9.0 - Fax Server Manual Bedienungsanleitung Seite 163

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Software Faxback NET SatisFAXtion 9.0 - Fax Server Manual