Re: [hylafax-users] hylafax-4.1_1 with, mutltiple modems -and- cid/logging (Important)

["alt" <syncope@speakeasy.net>]

Lee I'll try to keep this brief.
Since changing from "ServerTracing:          257"
to "ServerTracing:          0xFFF"

We get some new form/type cid entries which I assume are the true cid
entries skimmed from the modem ...
Nov  5 16:32:02 imani FaxGetty[118]: --> [11:DATE = 1105]
Nov  5 16:32:02 imani FaxGetty[118]: --> [11:TIME = 1632]
Nov  5 16:32:02 imani FaxGetty[118]: --> [8:NMBR = O]
Nov  5 16:32:02 imani FaxGetty[118]: --> [8:NAME = O]

Please confirm this is the 'fresh meat' you spoke of earlier.
More importantly I should and am asking, which document tells how to read
the log files?

Thanks for your patients with me on this.

Respectfully yours

Syncope

----- Original Message -----
From: "Lee Howard" <faxguy@howardsilvan.com>
Sent: Tuesday, November 05, 2002 1:54 PM
Subject: Re: [hylafax-users] hylafax-4.1_1 with, mutltiple modems -and-
cid/logging (Important)


> On 2002.11.05 10:45 alt wrote:
>
> >     I'm not sure I understand exactly what you mean when you say "the
> > ANSWER response".
>
> The "ANSWER" response is what you are showing in your logs with tracing
> 257.  Indeed, it does show CID data but only *after* it is parsed and
> digested by faxgetty.  What you are claiming: that CID data is received
> by the modem and that faxgetty haphazardly ignores or misinterprets it
> can only be substantiated by logging the CID data *as received* by the
> modem which can be done with tracing 0xFFF.
>
> > how is the CID data that's being seen/shown for pid [120] in the logs
> > getting there?
>
> That's post-chewing CID data... not the fresh meat that we want to see.
>
> 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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*