Hylafax Mailing List Archives

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] Regarding USR5610 Modem



On 2005.02.22 08:31 Philip Walls wrote:

Feb 22 11:22:52.43: [26950]: <-- [9:AT+FRS=7\r]
Feb 22 11:22:55.98: [26950]: --> [2:OK]
Feb 22 11:22:55.99: [26950]: <-- [9:AT+FTH=3\r]
Feb 22 11:22:56.18: [26950]: --> [7:CONNECT]
Feb 22 11:22:56.18: [26950]: RECV send MCF (message confirmation)
Feb 22 11:22:56.18: [26950]: RECV FAX (000000181): from FaxModem1,
page 1 in 0:10, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s
Feb 22 11:22:57.35: [26950]: --> [2:OK]
Feb 22 11:22:57.35: [26950]: <-- [11:AT+FRM=146\r]
Feb 22 11:23:04.46: [26950]: --> [2:OK]

Your logging isn't nearly set high enough for me to say this with any certainty, but...


See that AT+FRM=146 ? It is supposed to result in "CONNECT". It could also conceivably result in "+FCERROR" or "ERROR", but "OK" is an undefined response. What probably happens, and what is common to USR modems is that this happened (but we can't see it because your logging is messed up):

<-- AT+FTH=3
--> CONNECT
<-- MCF signal
--> OK
<-- AT+FRM=146
(modem messes up, resets baud rate, at least)
--> garbage (CONNECT at the wrong baud rate)
<-- CAN (to cancel)
--> OK

I haven't worked with USR modems long enough to figure out if there is a workaround for that garbage. However, if my guesses in that illustration are correct, it may be possible to work around the error by storing the faxgetty initialized state as the soft-reset state. So, you would allow faxgetty to initialize the modem, and then you'd run 'minicom -o <devid>' where <devid> is the device name that was used with faxgetty and where 'minicom -s' was used to create a profile for that device. Once in minicom you would enter "AT&W" or perhaps "AT&W0" or perhaps "AT&W1" (doing all of them probably would not be a problem, either). This stores the faxgetty-initialized state (including baudrate) in to the soft-reset profile for the modem. That way, if the modem does reset itself at inopportune times such as this, at least there is the possibility that it would recover.

Again, that's a guess, a stab, a possible fix. The error you're seeing is common, though, to USR modems, and is exactly one of the reasons why it isn't recommended to use them for faxing.

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*



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services