![]() |
Benoit.Y wrote: > Jun 06 16:31:11.55: [ 1853]: --> [7:CONNECT] > Jun 06 16:31:11.55: [ 1853]: RECV send MCF (message confirmation) > Jun 06 16:31:11.56: [ 1853]: RECV FAX (000000071): from , page 1 in > 0:17, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s > Jun 06 16:31:11.56: [ 1853]: <-- data [3] > Jun 06 16:31:11.56: [ 1853]: <-- data [2] > Jun 06 16:31:12.73: [ 1853]: --> [2:OK] > Jun 06 16:31:12.73: [ 1853]: <-- [11:AT+FRM=146\r] > Jun 06 16:31:19.73: [ 1853]: <-- data [1] > Jun 06 16:31:19.84: [ 1853]: --> [2:OK] > Jun 06 16:31:19.84: [ 1853]: <-- [9:AT+FRS=7\r] > Jun 06 16:31:22.17: [ 1853]: --> [2:OK] > Jun 06 16:31:22.18: [ 1853]: RECV FAX (000000071): from , page 2 in > 0:11, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s > Jun 06 16:31:22.18: [ 1853]: RECV FAX (000000071): > recvq/fax000000066.tif from , route to <unspecified>, 2 pages in 0:37 > Jun 06 16:31:22.18: [ 1853]: RECV FAX: Failed to properly detect > high-speed data carrier. Basically this means that the sender told us that there was another page coming, but when HylaFAX told the modem to look for the high-speed carrier that communicates the image data for that next page the modem did not detect that carrier for at least 7 seconds. There could be lots of reasons for this to happen. One possibility is that the sender may not have gotten the MCF signal properly, and if that's the case then the sender will likely retransmit PPS-MPS, and this will cause the situation above. In order to determine if this is the case you should upgrade to current HylaFAX CVS HEAD or 4.2.2 - whichever is sooner. Then see if the problem reocurrs. 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*