Re: [hylafax-users] ERR No receiver protocol (T.30 T1 timeout)

[Jan Kalcic <jandot@xxxxxxxxxxxxxx>]

Andrew Rinaldi wrote:
> Jan,
>
> Think hard about your decision to use 'cheap modems'... if you value your
> time and want to keep your user problems to a minimum invest in a quality
> fax board.
>
> Our PCI Express boards use the latest LSI (Agere) chipset and run fax
> firmware developed by Mainpine.  We have many HylaFAX customers and our
> products are readily available from resellers such as iFAX;
>
> http://shop.ifax.com/-c-31_1_23.php?filter_id=12&sort=products_sort_order
>
>   
I thank you once again for your advice and I hope it will be useful in
the future working in high-level IT projects. I'll keep it in mind.

What I'm looking now is a cheap solution for very small environments,
some of them "send-only" and installed on very old hardware. Business is
actually not involved. That would be enough to explain the reason why a
cheap and possibly external serial modem is preferred.

Regards,
Jan
> Regards
>
> ANDREW RINALDI
> Mainpine Developer Support
> USA +1 503 822 9944 | UK +44 8458 909438  
> andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com
>
> -----Original Message-----
> From: hylafax-users-bounce@xxxxxxxxxxx
> [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of Jan Kalcic
> Sent: 31 August 2007 10:37
> To: Lee Howard
> Cc: hylafax-users@xxxxxxxxxxx
> Subject: Re: [hylafax-users] ERR No receiver protocol (T.30 T1 timeout)
>
> Lee Howard wrote:
>   
>> Jan Kalcic wrote:
>>
>>     
>>> Aug 31 19:10:33.98: [ 8000]: <-- [18:ATX3DT00000000000\r]
>>> Aug 31 19:10:51.23: [ 8000]: --> [7:CONNECT]
>>> Aug 31 19:10:51.31: [ 8000]: --> [3:FE 10 03]
>>> Aug 31 19:10:51.31: [ 8000]: --> [5:ERROR]
>>> Aug 31 19:10:51.31: [ 8000]: MODEM Command error
>>> Aug 31 19:10:51.31: [ 8000]: FCS error
>>> Aug 31 19:10:51.31: [ 8000]: DELAY 70 ms
>>> Aug 31 19:10:51.38: [ 8000]: <-- [9:AT+FTH=3\r]
>>> Aug 31 19:10:51.43: [ 8000]: --> [7:CONNECT]
>>> Aug 31 19:10:51.43: [ 8000]: <-- HDLC<3:FF C8 D8>
>>> Aug 31 19:10:51.43: [ 8000]: <-- data [3]
>>> Aug 31 19:10:51.43: [ 8000]: <-- data [2]
>>> Aug 31 19:10:52.73: [ 8000]: --> [2:OK]
>>> Aug 31 19:10:52.73: [ 8000]: SEND send CRP (command repeat)
>>> Aug 31 19:10:52.73: [ 8000]: <-- [9:AT+FRH=3\r]
>>> Aug 31 19:10:59.74: [ 8000]: --> [0:]
>>> Aug 31 19:10:59.74: [ 8000]: MODEM <Empty line>
>>> Aug 31 19:10:59.74: [ 8000]: MODEM TIMEOUT: waiting for v.21 carrier
>>> Aug 31 19:10:59.74: [ 8000]: <-- data [1]
>>> Aug 31 19:10:59.79: [ 8000]: --> [2:OK]
>>>
>>>       
>> Well, from this I would guess that the fax features on this modem are
>> worthless.  Does this happen only when faxing to a specific
>> destination?  Or does this happen when faxing to all destinations?
>>
>> Thanks,
>>
>> Lee.
>>
>>
>>     
> Unfortunately my guess was right then. :-( Actually I tried with  two
> different destinations only and it didn't work on both. I could try
> again but I would say that this is enough to make me put aside this
> modem and try with a different one. The luck is that I bought only one
> of this modem even if I need almost a dozen of them. The good thing is
> that at least we can now update the documentation with an advice against
> this model.
>
> The words of Andrew Rinaldi is appreciated as any other advice will come
> in the list. What I basically need is a cheap and easily catchable modem
> available on the web. No particular performance are required.
>
> Thanks to all,
>
> Jan
>
>
> ____________________ 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*
>
>
>
>
>   


____________________ 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*