Re: [hylafax-users] Hylafax DB integration (postgresql) and/or API

[Adam Tauno Williams <awilliam@xxxxxxxxxxxxx>]

On Thu, 2004-08-12 at 02:26, doktora v wrote:
> Well maybe it's just me but I haven't found any scripts. 

They get invoked for every job.

> Anyway I tend
> to dislike scripts (just personal), and I want to give my
> application/database access to hylafax information.

There is no reason you can't replace the scripts with binaries,  we've
considered writing replacements in C#.  But just inserting the extra
bits you want seems to work well, and the fax-to-pdf sections of the
script are well tested since basically everyone uses them.


For anyone interested, HylaFAX uses the following shell scripts every
time it receives a job or attempts a send operation:

Recieve -
faxrcvd {file} {devID} {commID} {error-msg} {cidnumber} {cidname}
{file} - File name of recieved document
{devID} - The device name (ttyS0, etc...) on which document was
recieved.
{commID} - The communication identifier of the inbound call.
{error-msg} - An error message if reciept failed in any way.
{cidnumber} & {cidname} - Caller ID information if supported by both the
modem and the inbound line.

Send -
notify {file} {why} {jobtime} {commid} [ next try ]
{file} - The job description file
{why} - One of: done | failed | rejected | blocked | requeued | removed
| killed | timedout | format_failed |no_formatter | poll_rejected |
poll_no_document  poll_failed 
{jobtime} - Connect or transmission time
{commid} - PID of daemon that processed job
[ next try ] - If why == requeued then this is when the job is scheduled
to be tried again

The job description file contains the sent-to number:
...
number:9999999999
...
 and a reference to the postscript document
...
!postscript:0::docq/doc1.ps
... where docq is relative to the root of the HylaFAX spool area.


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