Ask a Question related to Linux Setup, Configuration & Administration, Design and Development.
-
tb #1
mgetty+sendfax = BUSY
Running SuSE 8.0 mgetty+sendfax worked perfectly (out of the box) so I
never tinkered with it. I have upgraded to SuSE 8.2 and cannot make it
work - please help.
Am running mgetty 1.1.30-43 as shipped with SuSE 8.2. professional.
The system communicates with the modem but always returns BUSY for the
remote fax machine - after dialing and attempting handshaking. Please
see the attached sendfax log.
I installed Hylafax to see if this cured the problem but it didn't.
The modem is a SmartLink 5634TS. Since this was working I am confident
that the modem is OK.
thanks in advance
Ted
--
08/30 21:43:01 sendfax: experimental test release 1.1.30-Dec16
08/30 21:43:01 sendfax.c compiled at Mar 17 2003, 14:49:17
08/30 21:43:01 sending fax to 01242258172
08/30 21:43:01 checking /etc/hosts
08/30 21:43:01 makelock(ttyS0) called
08/30 21:43:01 do_makelock: lock='/var/lock/LCK..ttyS0'
08/30 21:43:01 lock made
08/30 21:43:01 tss: set speed to 38400 (017)
08/30 21:43:01 tio_set_flow_control( HARD )
08/30 21:43:01 yS0 fax_open_device succeeded, ttyS0 -> 4
08/30 21:43:01 yS0 reading specific data for port 'ttyS0'
08/30 21:43:01 yS0 reading /etc/mgetty+sendfax/sendfax.config...
08/30 21:43:01 yS0 conf lib: read: 'verbose y'
08/30 21:43:01 yS0 conf lib: read: 'debug 5'
08/30 21:43:01 yS0 conf lib: read: 'fax-devices ttyS0'
08/30 21:43:01 yS0 conf lib: read: 'fax-id 44 1684 275064'
08/30 21:43:01 yS0 conf lib: read: 'dial-prefix ATD'
08/30 21:43:01 yS0 conf lib: read: 'max-tries 3'
08/30 21:43:01 yS0 conf lib: read: 'max-tries-continue y'
08/30 21:43:01 yS0 key: 'fax-devices', type=1, flags=4, data=(ignored)
08/30 21:43:01 yS0 key: 'modem-init', type=1, flags=0, data=(empty)
08/30 21:43:01 yS0 key: 'modem-handshake', type=1, flags=0, data=(empty)
08/30 21:43:01 yS0 key: 'modem-type', type=1, flags=1, data=auto
08/30 21:43:01 yS0 key: 'modem-quirks', type=0, flags=0, data=(empty)
08/30 21:43:01 yS0 key: 'fax-send-flow', type=4, flags=1, data=7
08/30 21:43:01 yS0 key: 'fax-rec-flow', type=4, flags=1, data=7
08/30 21:43:01 yS0 key: 'max-tries', type=0, flags=3, data=3
08/30 21:43:01 yS0 key: 'max-tries-continue', type=3, flags=3, data=TRUE
08/30 21:43:01 yS0 key: 'speed', type=0, flags=1, data=38400
08/30 21:43:01 yS0 key: 'switchbd', type=0, flags=1, data=0
08/30 21:43:01 yS0 key: 'open-delay', type=0, flags=0, data=(empty)
08/30 21:43:01 yS0 key: 'ignore-carrier', type=3, flags=1, data=TRUE
08/30 21:43:01 yS0 key: 'dial-prefix', type=1, flags=3, data=ATD
08/30 21:43:01 yS0 key: 'fax-id', type=1, flags=3, data=44 1684 275064
08/30 21:43:01 yS0 key: 'poll-dir', type=1, flags=1, data=.
08/30 21:43:01 yS0 key: 'normal-res', type=3, flags=1, data=FALSE
08/30 21:43:01 yS0 key: 'fax-min-speed', type=0, flags=1, data=0
08/30 21:43:01 yS0 key: 'fax-max-speed', type=0, flags=1, data=14400
08/30 21:43:01 yS0 key: 'debug', type=0, flags=3, data=5
08/30 21:43:01 yS0 key: 'verbose', type=3, flags=3, data=TRUE
08/30 21:43:01 yS0 key: '', type=3, flags=1, data=FALSE
08/30 21:43:01 yS0 key: 'page-header', type=1, flags=0, data=(empty)
08/30 21:43:01 yS0 key: '', type=3, flags=1, data=FALSE
08/30 21:43:01 yS0 key: '', type=3, flags=1, data=FALSE
08/30 21:43:01 yS0 key: '', type=1, flags=1, data=
08/30 21:43:01 yS0 tss: set speed to 38400 (017)
08/30 21:43:01 yS0 mdm_send: 'ATV1Q0'
08/30 21:43:01 yS0 mdm_command: string 'ATV1Q0'
08/30 21:43:01 yS0 mdm_command: string 'OK' -> OK
08/30 21:43:01 yS0 mdm_send: 'ATI'
08/30 21:43:01 yS0 mdm_gis: string 1: '5601'
08/30 21:43:01 yS0 mdm_identify: string '5601'
08/30 21:43:01 yS0 USR Courier/Sportster 56k detected
08/30 21:43:01 yS0 mdm_send: 'ATI3'
08/30 21:43:01 yS0 mdm_gis: string 1: 'Texas Instruments RK 56000 Voice Fax Rev. 10.A.29'
08/30 21:43:01 yS0 additional info: 'Texas Instruments RK 56000 Voice Fax Rev. 10.A.29'
08/30 21:43:01 yS0 mdm_send: 'AT+FCLASS=2.0'
08/30 21:43:01 yS0 mdm_command: string 'AT+FCLASS=2.0'
08/30 21:43:01 yS0 mdm_command: string 'OK' -> OK
08/30 21:43:01 yS0 mdm_send: 'AT+FLI="44 1684 275064"'
08/30 21:43:01 yS0 mdm_command: string 'AT+FLI="44 1684 275064"'
08/30 21:43:02 yS0 mdm_command: string 'OK' -> OK
08/30 21:43:02 yS0 mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0'
08/30 21:43:02 yS0 mdm_command: string 'AT+FCC=1,5,0,2,0,0,0,0'
08/30 21:43:02 yS0 mdm_command: string 'OK' -> OK
08/30 21:43:02 yS0 mdm_send: 'AT+FBO=0'
08/30 21:43:02 yS0 mdm_command: string 'AT+FBO=0'
08/30 21:43:02 yS0 mdm_command: string 'OK' -> OK
08/30 21:43:02 yS0 mdm_send: 'AT+FNR=1,1,1,0'
08/30 21:43:02 yS0 mdm_command: string 'AT+FNR=1,1,1,0'
08/30 21:43:02 yS0 mdm_command: string 'OK' -> OK
08/30 21:43:02 yS0 mdm_send: 'AT+FLO=2'
08/30 21:43:02 yS0 mdm_command: string 'AT+FLO=2'
08/30 21:43:02 yS0 mdm_command: string 'OK' -> OK
08/30 21:43:02 yS0 fax_send: 'ATD01242258172'
08/30 21:43:02 yS0 fax_wait_for(OK)
08/30 21:43:02 yS0 fax_wait_for: string 'ATD01242258172'
08/30 21:43:08 yS0 fax_wait_for: string 'BUSY'
08/30 21:43:08 yS0 ABORTING: line='BUSY'
08/30 21:43:08 ##### failed dialing, phone="01242258172", +FHS:-2, dev=ttyS0, time=6s, acct=""
08/30 21:43:08 yS0 fax_send: 'AT+FCLASS=0'
08/30 21:43:08 yS0 removing lock file
tb Guest
-
Busy cursor does not go away
I am calling a webservice operation by creating a webservice object. The busy cursor functions fine If I make single calls. But If I make multiple... -
I would like a few first impressions if your not busy, thanks.
Hi, being a bit riske with this site i'm doing, i havent seen another one thats similar (though i havent really been looking) so if anyone knows of... -
mgetty AutoPPP failing
Hi! On Fri Jul 18, 2003 at 02:28:50PM -0700, Ian Eure wrote: I think you should apply the noauth option to the pppd on the client side. The... -
processor is busy
In a home netwoking setup under XP, I notice that my processor spends considerable time in a process called <svchost.exe> user name: SYSTEM, and... -
sendfax parameters for HylaFax
John Zoetebier wrote: HylaFAX command lines are order sensitive: take a look at what the "sfax" utility puts out as an example of how to best... -
Bill Unruh #2
Re: mgetty+sendfax = BUSY
tb <fuzzies@madasafish.com> writes:
]This is a multi-part message in MIME format.
]--------------090803010503020305060608
]Content-Type: text/plain; charset=us-ascii; format=flowed
]Content-Transfer-Encoding: 7bit
]Running SuSE 8.0 mgetty+sendfax worked perfectly (out of the box) so I
]never tinkered with it. I have upgraded to SuSE 8.2 and cannot make it
]work - please help.
]Am running mgetty 1.1.30-43 as shipped with SuSE 8.2. professional.
]The system communicates with the modem but always returns BUSY for the
]remote fax machine - after dialing and attempting handshaking. Please
]see the attached sendfax log.
Might I suggest that the remote system is busy? It is the modem which is
sending back the response "BUSY". So, eitehr your modem is defective or
the remote site actually is busy. Have youtried dialing it on the phone?
Have you tried leaving the modem volume control on while it is dialing
so you can hear what happens at the other end?
]08/30 21:43:02 yS0 fax_wait_for: string 'ATD01242258172'
]08/30 21:43:08 yS0 fax_wait_for: string 'BUSY'
]08/30 21:43:08 yS0 ABORTING: line='BUSY'
]08/30 21:43:08 ##### failed dialing, phone="01242258172", +FHS:-2, dev=ttyS0, time=6s, acct=""
Bill Unruh Guest
-
tb #3
Re: mgetty+sendfax = BUSY
Bill Unruh wrote:
I have dialed in a number of times by phone and get a fax tone in> tb <fuzzies@madasafish.com> writes:
>
> ]This is a multi-part message in MIME format.
> ]--------------090803010503020305060608
> ]Content-Type: text/plain; charset=us-ascii; format=flowed
> ]Content-Transfer-Encoding: 7bit
>
> ]Running SuSE 8.0 mgetty+sendfax worked perfectly (out of the box) so I
> ]never tinkered with it. I have upgraded to SuSE 8.2 and cannot make it
> ]work - please help.
>
> ]Am running mgetty 1.1.30-43 as shipped with SuSE 8.2. professional.
>
> ]The system communicates with the modem but always returns BUSY for the
> ]remote fax machine - after dialing and attempting handshaking. Please
> ]see the attached sendfax log.
>
> Might I suggest that the remote system is busy? It is the modem which is
> sending back the response "BUSY". So, eitehr your modem is defective or
> the remote site actually is busy. Have youtried dialing it on the phone?
> Have you tried leaving the modem volume control on while it is dialing
> so you can hear what happens at the other end?
response. Listening to the modem it appears not to actually ring the fax
machine. The modem works fine for data, am using it to read the news
groups. I suspect that I requre a different initialisation string for
the modem. reading the manual and trying various settings have proved
futile :(. Does anyone have a working SmartLink modem tht could pass on
the initialisation string?
tks>
>
>
> ]08/30 21:43:02 yS0 fax_wait_for: string 'ATD01242258172'
> ]08/30 21:43:08 yS0 fax_wait_for: string 'BUSY'
> ]08/30 21:43:08 yS0 ABORTING: line='BUSY'
> ]08/30 21:43:08 ##### failed dialing, phone="01242258172", +FHS:-2, dev=ttyS0, time=6s, acct=""
>
>tb Guest
-
tb #4
Re: mgetty+sendfax = BUSY
Looking at the data connection it uses ATDT as the dial string rather
than ATD. This certainly seems to make a difference and the modem
deffinately dials. However, it still fails to connect - doesn't
recognise the fax and negotiate. Since I have tried it under W2K using
the software supplied as well as my older OS/2 box (where it was
working) and it fails on both so I suspect that the modem has given up.
Many thanks for the input - am sure I'll be back with questions. So far
VERY impressed with the available software.
thanks & cheers
Ted> tb <fuzzies@madasafish.com> writes:
>
> [...]
>
>>>>08/30 21:43:02 yS0 fax_send: 'ATD01242258172'
>
> This is the string sent to _your_ modem...
>
>>>>08/30 21:43:02 yS0 fax_wait_for(OK)
>
> ...and it waits for an OK.
>
>>>>08/30 21:43:02 yS0 fax_wait_for: string 'ATD01242258172'
>
> --which it never receives; instead, it gets "BUSY".
>
> The problem is either
>
> - an incorrect INIT string;
> - incorrect permissions on the device, or
> - incorrect setup of the mgetty lockfiles.
>
> Since you wrote that data connections work fine, check
> that very command (ATD01242258172) with minicom, or
> with sendfax but with modem speaker turned on. I am
> pretty sure that the modem doesn't dial at all.
>
> Michaeltb Guest



Reply With Quote

