![]() |
Quoting Lee Howard <faxguy@xxxxxxxxxxxxxxxx>: > On 2004.08.18 09:12 Daniel Moreda García wrote: > > This is a session of the same fax, but with Hylafax v4.2.0beta2: > > > > Aug 18 17:38:03.46: [ 3015]: <-- data [10] > > Aug 18 17:38:03.46: [ 3015]: <-- data [2] > > Aug 18 17:38:06.68: [ 3015]: --> [2:OK] Notice the 3.22 seconds delay before the modem response. > Here's the same segment from the 4.2.0 session that you sent: > > > Aug 18 11:37:45.64: [ 6052]: <-- data [10] > > Aug 18 11:37:45.64: [ 6052]: <-- data [2] > > Aug 18 11:37:48.19: [ 6052]: --> [0:] > > Aug 18 11:37:48.19: [ 6052]: MODEM <Empty line> > > Aug 18 11:37:48.19: [ 6052]: MODEM TIMEOUT: sending DIS/DCS frame > > Notice that HylaFAX is waiting for the modem to respond OK and gives up > at 11:37:48.19. Notice that HylaFAX gave up after 2.55 seconds. > It looks like a different modem (perhaps just modem firmware) to me. > The modem is behaving differently in your 4.2.0beta2 installation than > it does in your 4.2.0 installation. If the modem were to behave the > same in latter as in the first then it would be fine. I believe the change in sendRawFrame() causes this. That change where putModemDLEData was called with a timeout value of 60 seconds replacing the 2.55 seconds timeout already set before the call to sendFrame(). Now, is our 2.55 seconds delay not long enough or is the sender non-compliant with T.30? -- Patrice Fournier ____________________ 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*