![]() |
Lee Howard wrote: > I'd need to see your logging at a higher setting (to show the actual Thank you for your response. How can I change that? I have searched through the documentation and I assume the SessionTracing parameter should be changed, what into what value? Accually I haven't found the maximum value of that parameter. > modem data) and try to parse through it to know for certain, but this is > generally and indication that the sender's modulator, the receiver's > modulator, or both are not in a usable state. Generally they "come out > of it" after a couple of attempts, but in this case it did not happen. > My bet is on the USR modem being the culprit here. > > > >>sie 12 14:42:44.62: [ 4277]: RECV recv CTC (continue to correct) >>sie 12 14:42:44.62: [ 4277]: <-- [9:AT+FRS=7\r] >>sie 12 14:42:44.78: [ 4277]: --> [2:OK] >>sie 12 14:42:44.78: [ 4277]: <-- [9:AT+FTH=3\r] >>sie 12 14:42:44.90: [ 4277]: --> [7:CONNECT] >>sie 12 14:42:46.11: [ 4277]: --> [2:OK] >>sie 12 14:42:46.11: [ 4277]: RECV send CTR (confirm continue to correct) >>sie 12 14:42:46.11: [ 4277]: <-- [11:AT+FRM=121\r] >>sie 12 14:42:47.99: [ 4277]: --> [7:CONNECT] > > > ... > > >>sie 12 14:42:50.55: [ 4277]: RECV recv DCN (disconnect) > > > It's too bad the sender didn't drop down to V.29 before giving up (DCN) > because that probably would have recovered things. > > You *may* be able to work around your USR problems by disabling V.17. > You do that with Class1RMQueryCmd. Search the archives for examples. I put the following lines at the and of my config.ttyS0 file: Class1TMQueryCmd: "!3,24,48,96" Class1RMQueryCmd: "!3,24,48,96" I have to wait some time to see the results. ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*