Re: [hylafax-users] Duxbury (conexant-based) modem problems

["David Wilson" <dave@xxxxxxxxxxxx>]

Hi Lee,

Thanks for your reply.
What we find is that the FAX comes through with missing lines etc.

What I picked up in the receiver's side log was this:
Jun 28 10:12:53.62: [  182]: TRAINING failed

Jun 28 10:13:12.60: [  182]: --> [10:NO CARRIER]

Not sure if this is anything to be concerned about ?

I'll send you the received FAX from this session off list.

Sorry to keep bugging you with this one. I really appreciate your help.

Kind regards

David Wilson
D c D a t a
CNS, CLS, Linux+
Email/MSN: dave@xxxxxxxxxxxx
Phone: 0860-1-LINUX
Fax: 0866878971
Mobile: 0824147413
Skype: dave-wilson

Getting the most out your current PBX ?
Still paying it off ?
Want to hear how Linux & VOIP can save you money ?
Call us on 0860-1-LINUX

----- Original Message ----- 
From: "Lee Howard" <faxguy@xxxxxxxxxxxxxxxx>
To: "David Wilson" <dave@xxxxxxxxxxxx>
Cc: <hylafax-users@xxxxxxxxxxx>
Sent: Thursday, June 29, 2006 4:56 PM
Subject: Re: [hylafax-users] Duxbury (conexant-based) modem problems


> David Wilson wrote:
>
> > Hi Lee,
> >
> > Thanks for your reply and help so far - greatly appreciated !
> >
> > Interesting, because that log was from the 'senders' side - on the 
> > receiving side, which is also HylaFax with the same brand of modem, I 
> > picked up errors.
> > Please find the receiving side log below (The time is 45 or so minutes 
> > ahead on this box so please ignore that). The receivers side has just the 
> > standard config.ttyS(x) settings for Class1
> >
> > Hopefully you can provide some enlightenment on this one as I'm stuck. 
> > Thank you so much for your assistance !
>
>
> Again, there were no errors.  Well, there is (like there was shown on the 
> send-side) a TCF failure the first time, but I don't call that a modem 
> error like we'd seen before.
>
> > Jun 28 10:12:47.97: [  182]: RECV training at v.17 14400 bit/s
> > Jun 28 10:12:47.97: [  182]: <-- [11:AT+FRM=145\r]
> > Jun 28 10:12:49.68: [  182]: --> [7:CONNECT]
> > Jun 28 10:12:52.17: [  182]: RECV: TCF 0 bytes, 0% non-zero, 0 zero-run
> > Jun 28 10:12:52.17: [  182]: RECV: reject TCF (zero run too short, min 
> > 1800)
> > Jun 28 10:12:52.17: [  182]: --> [10:NO CARRIER]
>
>
> This is the only thing that you may be calling an error.  It probably 
> means that the sender fouled up somehow... not really sure.  It means that 
> for 2 seconds there the receiver used constant 1 bits rather than zeros as 
> expected.
>
> What error are you expecting there to be?
>
> Lee.
>
> ____________________ 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*
>
>
> --
> This email and all contents are subject to the following disclaimer:
> http://www.dcdata.co.za/emaildisclaimer.php


--
This email and all contents are subject to the following disclaimer:
http://www.dcdata.co.za/emaildisclaimer.php


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