![]() |
This is just as a note for the archives. We use topic chipset modems (don't ask why). ati3 TP560 Data/Fax/Voice 56K Modem They didn't support AT+FTS (using FTS would cause an ERROR during fax sending causing failure) === ati1 External Controller Ver1.20, CheckSum=2FF2 OK ati4 DSP Ver1.10 CheckSum=7A64 OK ati7 Controller Ver1.20 Date:Feb 17 18:35 OK at+fclass=1 OK at+fts=? ERROR at+fts=7 ERROR <================== === so that the HylaFAX modem prototype correctly avoids using +FTS A new batch of modems arrived with a new firmware: === ati1 External Controller Ver3.00, CheckSum=14CC ati4 DSP Ver3.00 CheckSum=B46B ati7 Controller Ver3.00 Date:Aug 27 19:02 2001 OK at+fclass=1 OK at+fts=? ERROR at+fts=7 OK <=============== Note this === But note this also (this was due to a misconfigured system where a config file was used that was not meant for topic, so that +FTS got used): === May 20 15:28:51.39: [ 7863]: --> [2:OK] May 20 15:28:51.39: [ 7863]: <-- [9:AT+FTS=7\r] May 20 15:28:51.41: [ 7863]: --> [2:OK] <=== OK, but 70 ms have not elapsed ... May 20 15:32:30.26: [ 7863]: SEND end page May 20 15:32:33.87: [ 7863]: --> [2:OK] May 20 15:32:33.87: [ 7863]: <-- [9:AT+FTS=9\r] May 20 15:32:33.89: [ 7863]: --> [2:OK] <=== OK, but 90 ms have not elapsed May 20 15:32:33.89: [ 7863]: SEND send EOP (no more pages or documents) May 20 15:32:33.89: [ 7863]: <-- [9:AT+FTH=3\r] May 20 15:32:33.94: [ 7863]: --> [7:CONNECT] === So, modem prototype is still correct because, even if +FTS gives OK, it seems it does not really work (it just says OK), but it may be confusing. -- giulioo@pobox.com ____________________ 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@hylafax.org < /dev/null