mgetty+sendfax and zoom 56k

mgetty+sendfax and zoom 56k

Post by Dan Tage » Sat, 27 Feb 1999 04:00:00



I seem to be having problems getting an external Zoom 56Kx dualmode modem to
work with mgetty+sendfax.  The init strings that are being sent seem to be
correct.
running mgetty 1.0.0 and kernel 2.0.35.

02/26 08:49:24 yS2  lowering DTR to reset Modem
02/26 08:49:25 yS2  send: \dATQ0V1H0[0d]
02/26 08:49:25 yS2  waiting for ``OK'' ** found **
02/26 08:49:44 yS2  send: ATS0=0Q0&D3&C1[0d]
02/26 08:49:44 yS2  waiting for ``OK''
02/26 08:50:04 yS2  timeout in chat script, waiting for `OK'
02/26 08:50:04 yS2  init chat timed out, trying force-init-chat
02/26 08:50:04 yS2  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
02/26 08:50:08 yS2  waiting for ``OK''
02/26 08:50:28 yS2  timeout in chat script, waiting for `OK'
02/26 08:50:28 yS2  init chat failed, exiting...: Interrupted system call
02/26 08:50:28 ##### failed in mg_init_data, dev=ttyS2, pid=6195

Thanks!

--Dan


 
 
 

mgetty+sendfax and zoom 56k

Post by Timothy Murp » Sat, 27 Feb 1999 04:00:00



>I seem to be having problems getting an external Zoom 56Kx dualmode modem to
>work with mgetty+sendfax.  The init strings that are being sent seem to be
>correct.
>running mgetty 1.0.0 and kernel 2.0.35.
>02/26 08:49:24 yS2  lowering DTR to reset Modem
>02/26 08:49:25 yS2  send: \dATQ0V1H0[0d]
>02/26 08:49:25 yS2  waiting for ``OK'' ** found **
>02/26 08:49:44 yS2  send: ATS0=0Q0&D3&C1[0d]
>02/26 08:49:44 yS2  waiting for ``OK''
>02/26 08:50:04 yS2  timeout in chat script, waiting for `OK'

I'm not an expert on modems, and I don't have a Zoom modem,
but it seems to me that your modem is not responding "OK" when expected.
If I were in that position, I would try sending these codes to the modem,
eg using "cu", and see how it responds.

--
Timothy Murphy  

tel: +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

 
 
 

mgetty+sendfax and zoom 56k

Post by William R. Matti » Sat, 27 Feb 1999 04:00:00



> I seem to be having problems getting an external Zoom 56Kx dualmode modem to
> work with mgetty+sendfax.  The init strings that are being sent seem to be
> correct.
> running mgetty 1.0.0 and kernel 2.0.35.

> 02/26 08:49:24 yS2  lowering DTR to reset Modem
> 02/26 08:49:25 yS2  send: \dATQ0V1H0[0d]
> 02/26 08:49:25 yS2  waiting for ``OK'' ** found **
> 02/26 08:49:44 yS2  send: ATS0=0Q0&D3&C1[0d]

Check your modem manual and see which one of these tells the modem to not
prduce result codes (or numeric codes).

Quote:> 02/26 08:49:44 yS2  waiting for ``OK''

Just a guess ... but :^)

Quote:

> 02/26 08:50:04 yS2  timeout in chat script, waiting for `OK'

Script never gets an "OK" from the modem. This is where your problem is.
Check the init string.

> 02/26 08:50:04 yS2  init chat timed out, trying force-init-chat
> 02/26 08:50:04 yS2  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
> 02/26 08:50:08 yS2  waiting for ``OK''
> 02/26 08:50:28 yS2  timeout in chat script, waiting for `OK'
> 02/26 08:50:28 yS2  init chat failed, exiting...: Interrupted system call
> 02/26 08:50:28 ##### failed in mg_init_data, dev=ttyS2, pid=6195

> Thanks!

> --Dan



Hope this helps

Regards
Bill

--
William R. Mattil       | Fred Astaire wasn't so great.

(972) 256-3219          | and... in high heels.

 
 
 

mgetty+sendfax and zoom 56k

Post by Dan Tage » Tue, 02 Mar 1999 04:00:00




>>I seem to be having problems getting an external Zoom 56Kx dualmode modem
to
>>work with mgetty+sendfax.  The init strings that are being sent seem to be
>>correct.
>>running mgetty 1.0.0 and kernel 2.0.35.

>>02/26 08:49:24 yS2  lowering DTR to reset Modem
>>02/26 08:49:25 yS2  send: \dATQ0V1H0[0d]
>>02/26 08:49:25 yS2  waiting for ``OK'' ** found **
>>02/26 08:49:44 yS2  send: ATS0=0Q0&D3&C1[0d]
>>02/26 08:49:44 yS2  waiting for ``OK''
>>02/26 08:50:04 yS2  timeout in chat script, waiting for `OK'

>I'm not an expert on modems, and I don't have a Zoom modem,
>but it seems to me that your modem is not responding "OK" when expected.
>If I were in that position, I would try sending these codes to the modem,
>eg using "cu", and see how it responds.

Tried it with minicom and I get an "OK" just fine, instantaneously.
Something I noticed is that the first "OK" takes about 30 seconds to be
"**found**".
I looked up the codes in the book and compared them with the USR modems that
work, and they are the same.
Anything else?

--Dan

 
 
 

mgetty+sendfax and zoom 56k

Post by Clifford Ki » Tue, 02 Mar 1999 04:00:00


: Tried it with minicom and I get an "OK" just fine, instantaneously.
: Something I noticed is that the first "OK" takes about 30 seconds to be
: "**found**".

That's not the way it looked in your first post.  That kind of respose
time usually means that the IRQ configured in Linux is not the same
as the IRQ that the modem actually uses.  I can't reconcile that with
an instant respose by minicom though.

--

/* Microsoft is a great marketing organization.
 * It _has_ to be */

 
 
 

mgetty+sendfax and zoom 56k

Post by Duane Elmer Smecker » Wed, 03 Mar 1999 04:00:00


This could be a timeout issue or an IRQ issue.
Can you verify that the modem is set for Com3 IRQ4?

It is essential that a serial mouse NOT be on Com1 (cua0)
(This is going to be my guess at the problem.)
because the IRQ would always take time to process
mouse data even when you don't care.

Next, check the TIMEOUT value in the chat script.
Bump it up a second or two.




>>>I seem to be having problems getting an external Zoom 56Kx dualmode modem
>to
>>>work with mgetty+sendfax.  The init strings that are being sent seem to
be
>>>correct.
>>>running mgetty 1.0.0 and kernel 2.0.35.

>>>02/26 08:49:24 yS2  lowering DTR to reset Modem
>>>02/26 08:49:25 yS2  send: \dATQ0V1H0[0d]
>>>02/26 08:49:25 yS2  waiting for ``OK'' ** found **
>>>02/26 08:49:44 yS2  send: ATS0=0Q0&D3&C1[0d]
>>>02/26 08:49:44 yS2  waiting for ``OK''
>>>02/26 08:50:04 yS2  timeout in chat script, waiting for `OK'

>>I'm not an expert on modems, and I don't have a Zoom modem,
>>but it seems to me that your modem is not responding "OK" when expected.
>>If I were in that position, I would try sending these codes to the modem,
>>eg using "cu", and see how it responds.

>Tried it with minicom and I get an "OK" just fine, instantaneously.
>Something I noticed is that the first "OK" takes about 30 seconds to be
>"**found**".
>I looked up the codes in the book and compared them with the USR modems
that
>work, and they are the same.
>Anything else?

>--Dan

 
 
 

1. mgetty-sendfax problem with ZOOM modem.

Hi Guys,

I was wondering if any of you are using mgetty-sendfax with a ZOOM Vbis32.
14.4K modem (external).

I set it up yesterday, and when I send fax using faxspool and faxq,
the logfile shows as if everything went fine, but in fact only an empty
page comes out of the other end.

So if you have a worknig setup, would you please mail it to me?

Thanks,
        Tamas

2. Apache Module: For Post reading method

3. Does mgetty-sendfax work with Zoom Faxmodem?

4. Hi, perl or java

5. Problem with Zoom/sendfax and page status

6. xterm resize indicators

7. Looking for someone who has setup sendfax only or mgetty also

8. problem: devfs scsi tape permissions

9. Using mgetty+sendfax

10. mgetty+sendfax.recompile

11. mgetty+sendfax printing incoming faxes to HP LaserJet

12. mgetty sendfax

13. mgetty+sendfax problems