![]() |
On 2002.11.11 03:16 Francesco wrote: > Nov 11 08:39:20.73: [ 977]: RECV recv MPS (more pages, same document) > Nov 11 08:39:20.73: [ 977]: <-- [9:AT+FRS=7\r] > Nov 11 08:39:20.84: [ 977]: --> [2:OK] > Nov 11 08:39:20.84: [ 977]: <-- [9:AT+FTH=3\r] > Nov 11 08:39:50.84: [ 977]: MODEM <Timeout> > Nov 11 08:39:50.84: [ 977]: RECV send MCF (message confirmation) > Nov 11 08:39:50.84: [ 977]: RECV FAX (00000162): from remotecsid, > page 1 in > 0:47, INF, 3.85 line/mm, 2-D MR, 14400 bit/s > Nov 11 08:39:50.84: [ 977]: <-- data [3] > Nov 11 08:39:50.84: [ 977]: <-- data [2] > Nov 11 08:39:53.39: [ 977]: --> [5:��] <---------- HERE IS THE > PROBLEM, I THINK! > Nov 11 10:24:52.89: [ 977]: CLOSE /dev/ttyS1 > > > What happened? Can i solve it by chainging my receiving-modem? Your modem firmware appears to have disliked something with the +FRS=7, +FTH=3 sequence, reset itself and returned garbage to the MCF data. Yes, it most likely wouldn't be a problem with a different modem (not the same model). Have you tried the patch I sent you? > I want also to indicate you i have configured this modem as Class1. This particular problem probably wouldn't occur with Class 2.0 - although you'd likely see others. You could also try changing Class1SwitchingCmd. 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@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*