Re: [hylafax-users] Courier I-Modem ISDN/V.34 Problem

[Cédric Bole-Richard <c.bolerichard@fabi.fr>]

My version of HylaFAX is 4.1beta2.
My modem is new, i have received it wednesday.
I have tested :
ModemResetCmds: ATZ\nAT
ModemResetCmds: ATZ
ModemResetCmds: AT&F1
ModemResetCmds: ""

In minicom, all command are OK. If i type the same sequence that faxgetty in
minicom, it's OK !

Always the same problem ...
I'm desperate :-(

My modem :
    USRobotics Courier I-Modem with ISDN/V.34
        Product type : France External
        Options : HST,V32bis,Terbo,V.FC,V34+,x2
        Fax Options : Class 1/Class 2.0
        Clock Freq : 20.16Mhz
        Eprom : 768k
        Ram : 256k
        Supervisor date : 10/10/97
        DSP date : 09/29/97
        Supervisor rev : 2.2.2
        DSP rev : 2.2.2

My config:
CountryCode:  33
AreaCode:  04
FAXNumber:  0381000000
LongDistancePrefix: 0
InternationalPrefix: 00
DialStringRules: etc/dialrules
ServerTracing:  0x0f
SessionTracing:  11
RecvFileMode:  0600
LogFileMode:  0600
DeviceMode:  0600
RingsBeforeAnswer: 0
SpeakerVolume:  off
GettyArgs:  "-h %l dx_%s"
LocalIdentifier: "XXX"
TagLineFont:  etc/lutRS18.pcf
TagLineFormat:  "From %%l|%c|Page %%p of %%t"
PercentGoodLines: 85
MaxRecvPages:  25
#
ModemType:  Class2.0
ModemRate:  38400
ModemFlowControl: rtscts
ModemNoFlowCmd:  AT&H0&I0&R1
ModemHardFlowCmd: AT&H1&I0&R2
ModemSoftFlowCmd: AT&H2&I2&R1
ModemSetupDTRCmd: ATS13=1&D2
ModemSetupDCDCmd: AT&C1
ModemSetupAACmd: AT+FAA=1
ModemSetVolumeCmd: "ATM0 ATL0M1 ATL1M1 ATL2M1 ATL3M1"
Class2BUGCmd:  AT+FBU=0
Class2CQQueryCmd: !(0),(0)
Class2NRCmd:  AT+FNR=1,1,1,0

# Ajoute par CBR

#JobReqBusy:  180
#JobNoanswer:  180
#JobNoCarrier:  180
#JobReqOther:  180
#NoCarrierRetrys: 1
#Use2D:   yes

ModemDialCmd:  ATDT%s
ModemResetCmds:  ""
ModemAnswerCmd:  ATA
ModemNoAutoAnswerCmd: ATS0=0
ModemEchoOffCmd: ATE0
ModemVerboseResultsCmd: ATV1
ModemResultCodesCmd: ATQ0X4
ModemOnHookCmd:  ATH0
ModemSoftResetCmd: ATZ
ModemWaitTimeCmd: ATS7=60
ModemCommaPauseTimeCmd: ATS8=2
ModemRecvFillOrder: LSB2MSB
ModemSendFillOrder: LSB2MSB

Class2Cmd:  AT+FCLASS=2.0
Class2APQueryCmd: ""
Class2BORCmd:  AT+FB0=0
Class2CQCmd:  ""
#Class2CQCmd:  AT+FCQ=0,0
Class2AbortCmd:  AT+FKS
Class2DCCQueryCmd: AT+FCC=?
Class2TBCCmd:  AT+FPP=0
Class2CRCmd:  AT+FCR=1
Class2PHCTOCmd:  AT+FCT=60
Class2LIDCmd:  AT+FLI
Class2DCCCmd:  AT+FCC
Class2DISCmd:  AT+FIS
Class2DDISCmd:  ""
Class2CIGCmd:  AT+FPI
Class2PIECmd:  AT+FIE=0
Class2PTSCmd:  AT+FPS
Class2SPLCmd:  AT+FSP
Class2NFLOCmd:  AT+FLO=0
Class2SFLOCmd:  AT+FLO=1
Class2HFLOCmd:  AT+FLO=2

My log :
Oct 24 17:54:22 Srv_Fabi02 FaxGetty[13358]: OPEN /dev/ttyS0
Oct 24 17:54:22 Srv_Fabi02 FaxGetty[13358]: MODEM set DTR OFF
Oct 24 17:54:22 Srv_Fabi02 FaxGetty[13358]: DELAY 2600 ms
Oct 24 17:54:25 Srv_Fabi02 FaxGetty[13358]: MODEM set DTR ON
Oct 24 17:54:25 Srv_Fabi02 FaxGetty[13358]: MODEM set baud rate: 19200 baud,
input flow RTS/CTS, output flow RTS/CTS
Oct 24 17:54:25 Srv_Fabi02 FaxGetty[13358]: MODEM flush i/o
Oct 24 17:54:25 Srv_Fabi02 FaxGetty[13358]: <-- [17:ATE0V1Q0X4S0=0H0\r]
Oct 24 17:54:30 Srv_Fabi02 FaxGetty[13358]: MODEM TIMEOUT: reading line from
modem
Oct 24 17:54:30 Srv_Fabi02 FaxGetty[13358]: MODEM <Timeout>
Oct 24 17:54:30 Srv_Fabi02 FaxGetty[13358]: MODEM set DTR OFF
Oct 24 17:54:30 Srv_Fabi02 FaxGetty[13358]: DELAY 2600 ms
Oct 24 17:54:32 Srv_Fabi02 FaxGetty[13358]: MODEM set DTR ON
Oct 24 17:54:32 Srv_Fabi02 FaxGetty[13358]: MODEM set baud rate: 19200 baud,
input flow RTS/CTS, output flow RTS/CTS
Oct 24 17:54:32 Srv_Fabi02 FaxGetty[13358]: MODEM flush i/o
Oct 24 17:54:32 Srv_Fabi02 FaxGetty[13358]: <-- [17:ATE0V1Q0X4S0=0H0\r]
Oct 24 17:54:37 Srv_Fabi02 FaxGetty[13358]: MODEM TIMEOUT: reading line from
modem
Oct 24 17:54:37 Srv_Fabi02 FaxGetty[13358]: MODEM <Timeout>
Oct 24 17:54:37 Srv_Fabi02 FaxGetty[13358]: MODEM set DTR OFF
Oct 24 17:54:37 Srv_Fabi02 FaxGetty[13358]: /dev/ttyS0: Can not initialize
modem.

My syslog:
Oct 24 17:54:37 Srv_Fabi02 FaxGetty[13358]: MODEM /dev/ttyS0 appears to be
wedged

Dmitry Bely <dbely@mail.ru> on Tuesday, Oct 24, 2000 10:27 PM wrote:
> Christoph Scheeder <christoph.scheeder@scheeder.de> writes:
>
> > Hi again,
> > in this situation i would try two things in this order:
> > 1.) look if i can find a firmware-update for the modem, often
> > modems with old firmware get delivered.
> > If this does not fix the problem I would guess it is damaged.
> > 2.) go to your dealer and let him replace the modem.
> > Either by transport or it is one of those devices dieing after
> > a very short period of time due to bad components.
> > This happens more often than many people imagine.
>
> No. The real pronlem is that older Hylafax version just do not propely
> reset the modem :-)
>
> To Cédric:
>
> try to add the following to your config.modem:
>
> ModemResetCmds: "ATZ\nAT"
>
> That is not needed for newer Hylafax versions, because they issue ATZ
> themselves (ModemSoftResetCmd).
>
> Hope to hear from you soon,
> Dmitry
>

____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null