![]() |
At 10:13 AM 4/7/2001Lee Howard sez: >At 01:17 AM 4/7/01 -0700, Paul A. Franz, P.E. wrote: > >Occasionally when sending and possibly when receiving, maybe one fax in 50 > >fails with messages like the following. > > >Apr 06 21:39:31.44: [17047]: --> [39:+FNSF:00 00 6A AA AA 00 31 0D 01 B7 > 00 ] > >Apr 06 21:39:31.44: [17047]: REMOTE NSF "00 00 6A AA AA 00 31 0D 01 B7 00" > >Apr 06 21:39:31.44: [17047]: NSF remote fax equipment: unknown > >What is the make and model of the remote fax machine? I am a TPC.INT cell operator. No personal knowledge of recipients equipment. I have written several of them via FAX using a USR 56K Voice and the connection speed is often less than the normal 14,400 to these offending machines that the Telebit World Blazers cannot connect to at all. > >Apr 06 21:39:31.44: [17047]: <-- [7:AT+FDT\r] > >Apr 06 21:40:26.87: [17047]: --> [10:NO CARRIER] > >Apr 06 21:40:26.87: [17047]: MODEM No carrier > >So after communicating fine and then one minute of wating for a response to >+FDT, the remote has hung up on you. I can hear what's going on from the very load and clear Telebit Speaker. First we hear it dial, then the answer which is ofter an outgoing voice message but not always. Then you hear what sounds like one machine squealing with joy to hear the other, the other squeals back and the first tries again. This happens over and over and over for what seems like 10 or more exchanges then there is a hangup and in a couple minutes Hylafax tries again for a total of three failures.. Same thing happens. The messages always say: To: gdji@netzero.net Date: 04/06/01 21:39 Error: Communication failure during Phase B/C; Giving up after 3 attempts to send same page. This particular one failed with TypRate 9600 and TypData 1-D MR but the normal failure that follows the Phase B/C training failure is 2400 2-D MMR. What is 1-D MR and what is 2-D MMR? > >Apr 06 21:40:26.87: [17047]: <-- [6:AT+FK\r] > >Apr 06 21:40:26.99: [17047]: --> [5:ERROR] > >Apr 06 21:40:26.99: [17047]: MODEM Command error > >And, obviously +FK fails and generates an error since it's only valid when >there is a carrier. But, since the remote has already hung up the result >is the same. > > >Apr 06 21:40:27.00: [17047]: SEND: Communication failure during Phase B/C; > >Giving up after 3 attempts to send same page "docq/doc936.ps;01", dirnum 0 > >Apr 06 21:40:27.00: [17047]: <-- [5:ATH0\r] > >Apr 06 21:40:27.13: [17047]: --> [2:OK] > >Apr 06 21:40:27.13: [17047]: SESSION END > >The problem? I would guess at flow control, but I'm not sure. What are >the ModemFlowControl, ModemHardFlowCmd, ModemSoftFlowCmd, Class2HFLOCmd, >and Class2SFLOCmd settings in your config file? No apparent settings for those last two (Class2HFLOCmd, and Class2SFLOCmd). Do I need them? The config file is: (/var/spool/fax/etc/config.ttyS1) # Configuration for a Telebit WorldBlazer modem with rev LA7.01 # or newer firmware. Note that adaptive answer is only available # with firmware rev 7.20. # # The modem is setup to run at 38.4 for both sending and receiving # and RTS/CTS flow control is used by default. # # CountryCode: 1 AreaCode: 999 FAXNumber: +1.425.641.1773 LongDistancePrefix: 1 InternationalPrefix: 011 DialStringRules: etc/dialrules ServerTracing: 1 SessionTracing: 11 RecvFileMode: 0600 LogFileMode: 0600 DeviceMode: 0600 RingsBeforeAnswer: 1 SpeakerVolume: quiet GettyArgs: "-h %l dx_%s" LocalIdentifier: "Blackdog Software" TagLineFont: etc/lutRS18.pcf TagLineFormat: "From %%l|%c|Page %%P of %%T" MaxRecvPages: 25 # # # Modem-related stuff: should reflect modem command interface # and hardware connection/cabling (e.g. flow control). # ModemType: Class2 # use class 2 interface ModemRate: 38400 # rate for DCE-DTE communication ModemFlowControl: rtscts # default # ModemHardFlowCmd: ATS58=2 # full duplex hardware flow control ModemSoftFlowCmd: ATS58=3 # XON/XOFF flow control ModemSetupDTRCmd: AT&D3 # setup so DTR drop resets modem ModemSetupDCDCmd: AT&C1 # setup so DCD reflects carrier (or not) # ModemSetupAACmd: AT+FAA=1;+FCLASS=0 # enable in class 2 & reset to data ModemWaitForConnect: yes # two-part protocol for adaptive-answer # ModemResetDelay: 3200 # extra long reset timeout required # ModemSendFillOrder: LSB2MSB # as expected ModemRecvFillOrder: MSB2LSB # opposite of what makes sense # Class2DDISCmd: AT+FDIS # LA7.20N apparently requires this -------- the end----- It looks like this config file has been truncated but it is right from the distribution file called telebit-wb. Maybe I have a problem because of this? Any suggestions on how to proceed? Paul Franz PAF Consulting Engineers | 427 - 140th Ave NE (425)641-8202 voice | Bellevue, WA 98005 (801)749-8480 fax | <http://blackdog.bellevue.wa.us/>