Technical information

FAX ON DEMAND CONNECTOR
57
1. First of all, the fodcpgm process, which manages the FoDC devices, will wait for a TCP timeout or an
acknowledgment of receipt for 300 seconds after having sent the http request. This first delay is the standard
timeout delay for all http requests.
2. After this delay, if this process is still waiting for a TCP timeout notification, the FIM management process will
wait another 100 seconds before registering the FoDC job as failed. This 400 seconds delay is the execution
timeout.
3. If the fodcpgm process is still running 700 seconds after the initial http request was sent, in spite of the above
two timeout triggers, the VSI-FAX scheduler will kill and restart it. Once this process has been restarted, the
VSI-FAX scheduler will try to send your fax once more. This final timeout mechanism is the maximum idle
delay.
The above 300, 400 and 700 timeout delays should be suitable in most cases. However, if you are using a slow
Internet connection and notice that the timeout delays are not long enough, you can choose to adjust these timeout
delays.
Follow these steps if you wish to change the length of the above timeout delays:
1. Stop the VSIFAX server.
2. Use a text editor to edit the VSIFAX\lib\vsisrv.ini file:
• Find the [DEVICE:FoDC] and [DEVICE:FoDC-hold] sections of the file and add or alter the
following lines:
request-timeout=<request timeout value>
Where <request timeout value> is the value you wish to set for the standard timeout delay for
all http requests (by default 300 seconds).
exec-timeout=<exec timeout value>
Where <exec timeout value> is the value you wish to set for the execution timeout (by default
400 seconds).
• Find the [VFXSCHED] section of the file and add or alter the following line:
MaxFimIdle=<Freeze timeout value>
Where <Freeze timeout value> is the value you wish to set for the maximum idle delay (by
default 700 seconds).
3. Restart the VSIFAX server to apply your modifications.
Managing failover with the Fax on Demand Connector
When sending faxes, if a device fails it is interesting to redirect the jobs queue to another device. Fax failover
management depends on the type of device that fails (local device or Fax on Demand Device).
Fax on Demand device failure
A Fax on Demand device failure can occur if the main Fax on Demand server is unreachable. Fax on Demand
failover management is enabled by default.
How does it work?
By default, the FoDC device is enabled and the FoDC2 device is disabled, thus the FoDC device is the main Fax on
Demand device, and if it fails more than a certain amount of times to send a fax it will be disabled and the FoDC2
device (the failover device) will be enabled to process the faxes instead. You can configure after how many
attempts the main Fax on Demand device will be disabled.
If a failover has occurred and the FoDC device has been disabled, a script will automatically re-enable it (and by the
way will also disable the FODC2 device) every 30 minutes (by default), making the configuration back to what it was
before the failure.