![]() |
Hi, The new version seems to have fixed the problem!
Cheers, Andrew
Andrew wrote:Aug 28 02:12:11.82: [ 4185]: <-- [11:AT+FRM=146\r]
Aug 28 02:12:13.50: [ 4185]: --> [7:CONNECT]
*Aug 28 02:12:13.50: [ 4185]: RECV: begin page*
Aug 28 02:21:41.86: [ 4185]: RECV: 2268 total lines, 0 bad lines, 0 consecutive bad lines
Aug 28 02:21:41.86: [ 4185]: RECV: end page
Aug 28 02:21:41.96: [ 4185]: --> [10:NO CARRIER]
I have a difficult time understanding how the delay here is at all related to the receiver. During non-ECM Phase C (all of that time there) the receiver should be completely silent. And even if the receiver were to make some kinds of noise the sender should be ignoring it.
HylaFAX's protocol handling here is completely correct.
I understand that you're experiencing this with multiple senders, but unless you have a broken T.38 service interfering in the communication here I have very little capacity to understand how this has anything to do with HylaFAX (or even the modem).
Thanks,
Lee.
____________________ 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*
____________________ 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*