Hi Lee and the list
I guess you are referring to this message
http://www.hylafax.org/archive/1998-09/msg00061.php
I don't see a resolution of the problem there, however.
If I understand you correctly, Hylafax received a hexadecimal value
which it didn't understand. Does this mean that hylafax has a bug and
needs to understand this hexadecimal value, or is this an error on the
sender side which violates a protocol and should send the value, maybe
in decimal form? In other words, can I do anything or is there a no go?
Thanks a lot for your reply.
Erich
-----Original Message-----
From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx]
Sent: Monday, October 17, 2005 2:26 PM
To: erich.iseli@xxxxxxxxxxxxxxxx
Cc: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] Error following AT+FDT command
erich.iseli@xxxxxxxxxxxxxxxx wrote:
>Okt 14 17:54:33.08: [25094]: <-- [7:AT+FDT\r]
>Okt 14 17:55:28.42: [25094]: --> [7:+FHS:1B]
>Okt 14 17:55:29.72: [25094]: --> [2:OK]
>
It's the same as this:
Sep 09 21:39:19.91: [ 690]: <-- [7:AT+FDT\r]
Sep 09 21:39:21.55: [ 690]: --> [7:+FHS:27]
Sep 09 21:39:21.55: [ 690]: REMOTE HANGUP: Failure to train at 2400 bps
or +FMINSP value (code 27)
HylaFAX just didn't interpret the hexadecimal value correctly.
Lee.