Response from USR to "Sportster +FHS:25 problem"

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

comment from USR/3com (truncated to hide a few things that might be NDA).

----- Forwarded message -----

The trouble came from the fact that the modem does not negociate properly
the scan line time buffering when it is SPECIFIED in the +FCC command. In
this particular session below the string

09/24 12:25:16 yS3  mdm_send: 'AT+FCC=0,5,0,2,0,0,0,0'

should not specify the ST parameter, hence should appear like :

09/24 12:25:16 yS3  mdm_send: 'AT+FCC=0,5,0,2,0,0,0,'

When done this way, the modem should negociate the scan line time
correctly.

----- End forwarded message -----

I flatly refuse, though, to add this workaround to my code -- I think it's
broken.

On the other hand, there already IS a workaround for USR-misinterpretations 
of AT+FCC parameters, #define FAX_USRobotics.  It does even more, that
is, specify nothing but the first "0" (or 1) of AT+FCC, so should help
here as well.

Since about 1.1.17 or so, FAX_USRobotics has completely disappeared, and 
you can set it at run-time by setting "modem-quirks 0x20" in
sendfax.config.

Could all of you who have been bitten by USR Sportsters and +FHS:25
(or +FHS:27) error codes please test "modem-quirks 0x20" will fix this and
report to me or to the list?

Thanks!

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de