| 
     Hylafax Mailing List Archives
 | 
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] capi4hylafax (again) take 2 :)
Am 2004.10.29 10:23 schrieb(en) Gavin Hamill:
The two interesting values are 0:36, the jobtime, and 0:24 the
conntime;
...
Should there really be as much as 12 seconds logged for setup and
cleanup?
...
Oct 29 08:51:34.34: [ 7600]: Try to connect to fax number 01618399336
in
Hylafax mode on controller 1.
Oct 29 08:51:34.34: [ 7600]: Dial and starting transfer of TIFF-File
docq/doc21.ps;00 with normal resolution.
Oct 29 08:51:46.30: [ 7600]: Connection established.
Oct 29 08:51:46.30: [ 7600]:    StationID =          01618399336
Oct 29 08:51:46.30: [ 7600]:    BaudRate  = 14400
Oct 29 08:51:46.30: [ 7600]:    Flags     = HighRes, MMR_compr
Oct 29 08:51:56.61: [ 7600]: Page 1 was sended. - Last Page!
Oct 29 08:51:56.61: [ 7600]: Fax file completely transfered to CAPI.
Oct 29 08:52:10.38: [ 7600]: Connection dropped with Reason 0x3491
(User busy).
Oct 29 08:52:10.38: [ 7600]: SESSION END
The 12 seconds correspond to the time from "Dial and starting  
transfer..." to "Connection established".
capi4hylafax must have completed the initial fax negotiation when it  
reports "Connection established" since it immediately knows StationID  
and other parameters. After the phone line is connected it would take  
the fax stations some seconds to negotiate connection speed, resolution  
etc. and exchange their station IDs I think the connection time you  
will get charged for starts immediately or at most a few seconds after  
"Dial and starting transfer...".
If you have messages like
kernel: kcapi: appl 1 up
kernel: kcapi: appl 1 down
in /var/log/messages, you can compare the time stamps in the job's  
logfile with these messages.
With isdnlog you may be able to see more details about the ISDN  
connection like CONNECT and HANGUP time.
That 'connection dropped' line worries me - User busy? That doesn't
make a lot of sense...
I don't know what your ISDN card (or the telco) reports if the  
connected station hangs up. Maybe capi4hylafax was waiting for  
something and the remote machine hung up first. (Though I would not  
expect a "User busy" message in this case.)
isdnlog might show some useful information.
Bodo
____________________ 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*