The latest version of FF240-IP Software is 5.0.5. This was released in June of 2017.
The process for updating your FF240-IP is initiated from the unit itself. The unit will
download updates from our update server (or a user defined update server) when instructed.
This is in contrast to how updates are performed with the FFx30 model FaxFinders.
As the system administrator, you do not upload firmware upgrade files to the FF240-IP.
To view a list of software changes and to update the software of your FF240-IP fax server,
log into the WEB Administration menu of your unit and navigate to System Configuration >
Software Update menu. The "Update Source" is the URL your FF240-IP will navigate to,
when checking for software updates. Clicking on the "Check for Updates" button will
cause the FF240-IP FaxFinder to check the designated site for a newer version of software.
If an update is available it will be listed as such along with an Upgrade button and a
README document about the new version. The software update is downloaded from the Update
Source when the Update button is clicked. If the update is downloaded successfully the
unit will apply the update and reboot the unit.

Important: Do not power off the FF240-IP during the update process.

Version 5.0.5

Changes since version 4.1.2:

Features:
- Added support for hybrid mode allowing connecting an analog expansion box
- Added wildcard support for extensions in the Inbound Routing

Bug Fixes:
- Fixed Internal Server Error from inbound_status API call if there is an inbound fax
- Added hover help when adding an inbound route to help avoid mis-configuration
- Fixed issue when using etherFAX unit could continously reboot
- Updated SIP/T.38 Stack
- Fixed issue with comma in To field
- Fixed issue with registration 

Version 4.1.2

Changes since version 4.0.0.3:

Bug Fix:
- Addressed numerous security issues
- Added etherFAX channel support
- No longer rejects pdf attachments that come in as application/octet stream when using T.37
- Fixed issue with AD turning "-" to " "
- Added caller name/number to call_log and inbound_log API calls
- Increased the number of simultaneous connections to 150. It was 50
- Updated SIP/T.38 Stack 
  > Added a 100 mSec delay after SIP registration and authentication challenges to improve interoperability
  > SSRC changes in RTP streams were ignored, causing fax failure in G.711
  > Calling-side re-invites were ignored when received by Bladeware
  > Transmit side CSIDs that exceed 21 characters would cause system to crash


Changes since version 4.0.0:

Bug Fix:
- The number of channels will now stay the same when switching between SIP/T.38 and etherFax.


Changes since version 3.5.2:

Features:
- Added option to set the fax page size for the inbound and outbound faxes.
- Added etherFAX support.

Bug Fixes:
- Added calling # to the call log and call log details web pages.
- Fixes issue with the inability to disable "Allow simultaneous faxing to same number".
- Fixes issue where the failure reason did not match between call log and fax receipt.
- Added support for AD attributes without a "-".
- RC4 ciphers are no longer supported.

Updated SIP/T.38 Stack:
- Large CSeq numbers may cause the FF to reboot.
- Very large SDP session ID's were not parsed correctly.
- Large jumps and/or resets of RTP sequence numbers may cause fax failure.
- No response to INVITES where the "FROM" field was malformed.
- SIP Registration requests do not honor the value of Registration Period.
- Some transmitted (ECM) faxes may report a false "successful".
- Sometimes not sending RTP.