Technical information

EVENT NOTIFY PROCEDURES
109
Next, the system looks for a site LNP. If it finds one, it runs it.
Similarly, the system checks the fax command for a user LNP. If a user LNP was specified, the system runs it.
Note
User LNPs must be specified on a fax-by-fax basis. This is typically done via the -t lnp=<LNP_file> tag.
Similar vfx tags are also provided for other user notify procedures.
See also
Refer to Tag Reference in the Reference Addendum
documentation for additional information about using vfx tags
to run user notify procedures.
The LNP notification point is the same for both normal (non-group) and group faxes.
Transmit notify procedures (TNPs)
Transmit Notify Procedures (TNPs) are typically only run for normal (non-group) faxes. As the Normal (Non-Group)
Send Notification Flow Diagram shows, they are run after each fax attempt until the fax job is done. Again, note the
hierarchical behavior: the system TNP is automatically run and if the system finds site or user TNPs, it runs them in
that order.
Look at the final decision block, Fax Done? This can mean one of two things:
The fax was successfully sent.
The maximum number of retries was attempted but the fax was not successfully sent.
Notice also that if the fax job is not done, that it returns to the scheduler for a retry. This loop continues until the fax is
successfully sent or until the maximum number of retries has been attempted (regardless of outcome).
For this reason, most site and user TNPs contain logic that generates one response for a successful fax attempt (i.e.,
fax job completes successfully), another response for an unsuccessful fax attempt and yet another response for a fax
job completing unsuccessfully.
This figure shows the notification mechanism for group sent faxes: