I think HylaFAX+ could record the Com port or the tty that a fax was received on in the metadata of the fax file. This can be useful for fax routing or sorting on the client side, and be used as an alternative to the existing server-side fax routing feature for clients that want to handle the job themselves.
In my particular case this need arises from the fact that clients communicating solely over the HylaFAX protocol can specify a tty or modem group to send fax jobs to but cannot reliably collect faxes from those logical groupings, without resorting to the current out-of-band fax routing functionality available in HylaFAX.
A workaround would be to do some post processing in faxrcvd script by using tools such as exiftool to add the missing metadata. But this could be done more efficiently and reliably in the HylaFAX code.
Last edit: aminmo 2016-05-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think HylaFAX+ could record the Com port or the tty that a fax was received on in the metadata of the fax file. This can be useful for fax routing or sorting on the client side, and be used as an alternative to the existing server-side fax routing feature for clients that want to handle the job themselves.
In my particular case this need arises from the fact that clients communicating solely over the HylaFAX protocol can specify a tty or modem group to send fax jobs to but cannot reliably collect faxes from those logical groupings, without resorting to the current out-of-band fax routing functionality available in HylaFAX.
A workaround would be to do some post processing in faxrcvd script by using tools such as exiftool to add the missing metadata. But this could be done more efficiently and reliably in the HylaFAX code.
Last edit: aminmo 2016-05-08