Re: [hylafax-users] FaxNotify, sendfax,

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

joea wrote:

> Isn't there a way to make notifications a default behavior?

The purpose of the job notifications (notify, FaxNotify) is foremost and 
primarily to notify the user of job status, failure, completion, 
rescheduling, whatever.  The purpose in FaxNotify is foremost and 
primarily to customize the notifications themselves, or to perform some 
kind of scripted-in function that belongs within the context of 
notifying the user of job status (like sending a pager message as well).

The default notification will very likely depend on the client software, 
anyway.  And no, there's not a feature on the server to override the 
particular notification type request made by the client.

Normally people have asked the question that you have asked just now 
when they want to script-in some kind of event at the time of 
job's-end... and usually those events are accouting-related.  The truth 
is, however, that relying on FaxNotify for purposes outside the scope of 
notifications to the user of job status is not a very good approach to 
these kinds of needs.

After all, if the user requests no notification at all - and they 
certainly want no notification at all (imagine a fax broadcast) - then 
it is important that we honor that request... and in so doing it may 
throw off the statistical process that is being triggered by FaxNotify 
(if that's where we have scripted it in).  Likewise, if a user wants 
notifications on every requeuing of the job, then if the destination is 
frequently busy then this could cause another accounting nightmare.

If the data within the xferfaxlog is sufficient for what you want, then 
running a cron job that watches the xferfaxlog and takes actions on 
certain events may suit your requirements... however, if you need to 
script-in some kind of extended accounting feature - if you need to 
modify data on an SQL table immediately when these kinds of events 
occur, then HylaFAX 4.2.5 (and 4.3.0) really have no suitable place for 
that scripting hook, IMO.

If what you're looking for is a sure-fire scripting hook for end-of-job 
or end-of-call events, then let me know.

Thanks,

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*