There are a couple of ways of achieving this:

First method is to write a script which will repeatedly submit a new fax job using sendfax.
If the "-h ttyS4@localhost" option is used to specify a particular sending fax device and -d <number> to specify a number, then a test run of 1000 faxes say can be queued for port1->port3, and another 1000 faxes queued for port2->port4.
These jobs will run concurrently and waiting jobs will be marked "blocked by concurrent call".

Second method (which is new to Hylafax 4.2.0) is to use the "sendfax -z <file>" option.
This allows a file to specify the destination phone numbers (a bit like multiple -d options).
Each line of the file can contain a different destination/number and these are submitted sequentially.

Some points to be aware of when sending large broadcasts:

1. Disk space - make sure that there is enough space for the sending and receiving images.
   If disk space runs out, Hylafax only reports a "protocol botch: server write error".
2. Time to live timer - by default a fax job has 3 hours from submission to be sent before the job is removed from the queue.
   Large broadcasts may take several days, so need to bump this time up using the sendfax -k option, e.g. '-k "now + 1 week" should do it.

Sample broadcast script, to run type "./broadcast "ITU-T Test Image 1.TIF" 500, to send the TIF file "ITU-T Test  Image 1.TIF" 500 times over two ports:

rm port3_list
rm port4_list
cp "$1" port1_image.tif
cp "$1" port2_image.tif
for ((a=1; a<=$2; a++))
do
echo "33333456789012" >> port3_list
echo "44444567890123" >> port4_list
done
sendfax -n -N -m -k "now + 1 week" -h ttyS4@localhost port1_image.tif -z port3_list
sendfax -n -N -m -k "now + 1 week" -h ttyS5@localhost port2_image.tif -z port4_list

< Hylafax questions
< Questions