Re: [hylafax-users] mis-interpreted send

[bill.allison@xxxxxxxxx]

Lee

I'm willing to help with this but don't want to switch on verbose session   
tracing for a whole day - can I switch it on in, say, /etc/FaxAccounting   
conditional on caller id? Or if not, I would be willing to recompile with   
a patch somewhere to do it conditionally. We're on 3.0.12 here.

Regards
Bill

 -----Original Message-----
From: faxguy@xxxxxxxxxxxxxxxx
Sent: 07 December 2006 19:19
To: Bill Allison
Cc: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] mis-interpreted send


   

 --------------------------------------------------------------------------  
 --
bill.allison@xxxxxxxxx wrote:

>For info this also happens with USRs in Class 1. We see it with a few
>different senders (don't know what machines they use) and (apparently
>only when the TSI is null?) we sometimes see one or two random chars
>after the 0q e.g. 0q], 0qc, 0qw, 0qYr
>

It certainly would help me to see a session log where this occurs and
where the HDLC frame is being logged (with SessionTracing at 0xFFF).

I've looked at the code - and I can't reproduce the problem regardless
of the length of the TSI string.

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*