etherFAX will no longer be supporting TLS version 1.0 for secure communications after June 30th, 2018. In order to align with security industry best practices and changing regulatory requirements, this change will be made for all of etherFAX’s Internet facing web sites and systems.

What is TLS 1.0?
TLS stands for “Transport Layer Security.” It is a protocol that provides privacy and data integrity between two communicating applications. It is the most widely deployed security protocol used today and is used for web browsers, FTP clients, and other applications that require data to be securely exchanged over a network. TLS ensures that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification. The versions of TLS, to date, are TLS 1.0, 1.1, and 1.2.
Client web browsers, FTP clients, and connection applications may use TLS as a component of their security.
etherFAX highly recommends the use of TLS 1.2 for all communications.

What is the change?
All etherFAX API’s are requiring action to disable TLS 1.0 by June 30, 2018. On that date etherFAX will disable support for the TLS 1.0 encryption protocol, which will prevent customers from using it to access etherFAX services. This change is important to protect the security of our customer’s data while they interact with our systems.

How will customers be impacted?
After etherFAX disables TLS 1.0, any connections to/from etherFAX that rely on TLS 1.0 will fail. This may impact a number of etherFAX services including all REST and SOAP API interfaces, fax server connections, customer portals, and partner portals. After this change the minimum supported Microsoft OS is Windows Server 2008 R2. Server 2003 will cease to function. etherFAX A2E devices are not affected by this change.

How can customers avoid a service disruption?
The action required by your organization will depend on the method by which the etherFAX services are accessed and from what OS version they are being accessed from. Ingenium Customers utilizing a fax server application or etherFAX API integration should contact us for more details on any required changes or updates.

Resources:
etherFAX has made available a test tool which can validate your Windows server(s) for their ability to connect over the various TLS protocols. This tool can only tell you whether your system is capable of properly making connections post-TLS-1.0, using .NET applications. If your faxing application is hardcoded to use legacy protocols, not based on .NET 4.0 or higher, OR based on .NET but not utilizing .NET’s connection methods, we cannot determine whether it will connect to etherFAX endpoints after June 30^th, and this should be discussed with the developer or software vendor for further information. You can download the tool here: TLSTester

OpenText has identified a scenario where data corruption can occur in RightFax 10.5 and 10.6.
The tracking numbers for this issue are RF-15152 (v10.5) and RF-14462 (v10.6). 

Systems Affected

• OpenText RightFax 10.6 and all updates earlier than Feature Pack 2 Service Release 2
• OpenText RightFax 10.5 and all updates earlier than Feature Pack 1 Service Release 5 with build number 6069

Details
In OpenText RightFax 10.5 and 10.6, an error may occur when the RightFax Server module attempts to get the next available file name for a fax image from the SQL database. If the error occurs more than once, already assigned file names may be inadvertently reassigned to another file image.

Impact
Data corruption occurs because fax image files may be overwritten or content from one fax image appended to another.

Solution

This issue is resolved in:

• RightFax 10.6 Feature Pack 2 Service Release 2 (Knowledge Center log on required)
• Beta Patch 10.5.1.6.6069 for RightFax 10.5 Feature Pack 1 Service Release 5 (Please contact Ingenium Support to obtain the patch)

As a workaround, customers can manually create the folder structure for the image files (for example, 00000000.30x) in the image directory and deny permission on the fourth 00 folder for the service account running the RightFax Server Module. For more information, refer to Knowledge Base Article 62299678.

More Information
For more information, contact Ingenium Support @ Support@ingeniumsw.com with your RightFax version and SUID or call 770-936-0600

OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text SA or other respective owners. All rights reserved. For more information, visit: http://www.opentext.com/2/global/site-copyright

RightFax Upgrade from Ingenium

If you are running RightFax 10.5 or earlier, chances are we should be talking about an upgrade to a newer version of RightFax. Ingenium can remotely upgrade and migrate your fax data to the latest supported versions of RightFax 10.6. Ingenium’s enhanced support and monitoring options will greatly enhance your user experience and ensure the maximum uptime for your faxing system. Contact Ingenium to discuss our upgrade and support options for your RightFax product today.

• RightFax 10.6 – Current Version – Sustaining Maintenance November 2018
• RightFax 10.5 – Sustaining Maintenance November 11, 2016
• RightFax 10.0 – Sustaining Maintenance July 17, 2015
• RightFax 9.4 – Sustaining Maintenance May 31, 2014
• RightFax 9.0 – Sustaining Maintenance October 1, 2009
• RightFax 8.7 – Sustaining Maintenance September 1, 2008
• RightFax 8.5 – Sustaining Maintenance February 17, 2006
• RightFax 8.0 – Sustaining Maintenance September 30, 2004

Introduction:

It may come as a surprise with the ubiquity of the Internet that the Fortune 500 still rely on fax technology for mission critical applications. The nation’s largest retailers communicate between stores and distribution centers via fax technology, for example. Fax technology allows them to transmit sensitive data such as credit card (PCI) and ordering information securely between stores and distribution centers requiring without traversing the Internet or email. Other applications include HIPPA and EDI applications that the Fortune 500 relies on every day that have to be secure. Read the article on LinkedIn.
Read More

Now that Fall is officially here, we can look forward to cooler weather, the leaves changing in the south and free RightFax Training classes from Ingenium. If you are an Ingenium RightFax supported customer, you are entitled to receive free online training for RightFax. We have just published our online fall training classes. To register for a free training class, just visit our RightFax Training page and reserve your spot today! Classes are limited to 25 people.

The latest Feature Pack (FP) for RightFax 10.6 has been released and is ready for download.  Included in the FP2 release is the FP itself, an updated Client Install package and updated documentation.  We’ll post the links to everything at the bottom of this post.

Here is a rundown on the new features added to RightFax 10.6 with this FP:

•  New Feature Pack Installer
  • The installer can update an existing OpenText RightFax 10.6 or later server or install a fresh OpenText RightFax 10.6 Feature Pack 2 server.
• New RightFax Web Client
  • Web Client is supported on the most recent version of popular browsers.
  • Admin can configure a list of RightFax servers that users can select from when they sign on.
  • Users can view web client online help.
• FaxUtil
  • Admin can hide the change password option on the FaxUtil sign-in window.
  • Users can show a DID/DNIS column in the fax list.
  • Users can show a completed time column in the fax list.
  • Users can view and print a confirmation page.
  • Users can submit faxes for archiving.
  • Users can delete their custom delegate role templates.
  • Users can see a coversheet preview.
  • Fax History
    • Fax history includes a more detailed OCR record.
    • Fax history is updated when users initiate “send via email” from the viewer.
    • Users can view delegate activities in the fax history.
  • Viewer
    • Improved pagination controls.
    • Users can place an image on a fax page.
    • Users can make freehand annotations on a fax page.
    • Users can re-size Annotations before they are saved.
    • Users can view SMS messages.
    • Fax images are copied before annotations are saved.
• Enterprise Fax Manager
  • Users can be prevented from creating or editing phonebooks.
  • Users can be restricted from granting delegate access.
  • User accounts have a new description field.
  • Archive options can be set at the user level.
  • Groups can have up to nine alternate administrators.
  • The RightFax server list can be reordered, exported, and imported for consistent management in multiple locations.
  • Admin can copy server settings between nodes in a shared services environment.
  • Admin can include ISDN Calling Party information with SIP or h.323 FoIP calls.
  • Fax database threads are managed automatically.
  • Outdated low disk space display has been deprecated.
• Connector for Microsoft Exchange
  • The Exchange Web Services Connector can be run remotely.
• Sync Module
  • Disabled users can be automatically moved into a RightFax group or deleted.
  • Disabled users with Exchange mailboxes can be imported into RightFax.
  • Users with changed AD IDs can be updated automatically in RightFax.
  • Admin can choose to not create new RightFax users when AD IDs change for the same GUID.
  • Blank routing codes can be replaced with the Default user’s routing code.
• Notifications
  • Group administrators can be notified about faxes needing approval.
  • Users can be notified when their fax transmissions are started or in progress.
  • Print notifications include a thumbnail image and metadata.
• RightFax Connect
  • Admin can choose to ignore RightFax Connect certificate errors.
  • RightFax Connect works with a proxy server.
• MFP Connector
  • The following fax addressing restrictions can be enabled for HP, Ricoh, and Xerox MFP Connectors:
    • MFP users can be required to enter the fax number twice.
    • MFP users can be required to select recipients from the phonebook.
• Other Administrative Enhancements
  • SSL connection to SQL.
  • Call blocking supports multiple numbers.
  • Admin can set up multiple auto-reply templates.
  • Connector for SharePoint uses the same whitelist as RightFax.
  • Web Delivery links support https.
  • FCL commands can control retries on a per-job basis.
  • Conversion engine includes an improved method for converting HTML and MHTML documents.
  • Admin can specify how to handle errors when faxing without Error Correction Mode.
  • Smart Fax Distribution can automatically forward a fax to all members of a group.
  • Changes to delegate settings are tracked in the Audit report.
  • Admin can specify a duplicate image directory.
  • Users can save RightFax Web Reporter reports to a file.
  • Advanced Audit Report shows who adds, modifies, or deletes RightFax user accounts.
• RightFax Web API SDK
  • Windows Authentication
  • Retrieve and attach library documents
  • Retrieve and attach billing codes

As you can see there are a lot of new features in this FP2 release and the download file size shows it.  This patch (with the client install package) ISO download comes in at a whopping 2.21 GB Download.

To get your patch, please follow these links:
*You will need your Open Text KC login information for these downloads

• RightFax 10.6 Feature Pack 2 ISO (2.21 GB)
• RightFax 10.6 Feature Pack 2 Client Install package
• RightFax 10.6 Feature Pack 2 Readme
• RightFax 10.6 Feature Pack 2 Documentation (Not uploaded at the time of writing)
  • Main RightFax 10.6 Documentation

If you have any questions about RightFax 10.6; FP2; or any Secure Document Delivery solution, please contact your Ingenium Account manager or email Info@Ingeniumsw.com

When RightFax talks to a voice gateway to send a fax call and fails, you may see “RightFax transmission error phase B”. Rightfax transmission error phase b usually means that the next hop, typically the carrier, is not returning dial tone to your call setup. Make sure that you run a wireshark trace between RightFax and your gateway that you can provide to your carrier for analysis. Your carrier should also generate a trace with you on their side of their gateway to see why the error is occurring. Most of the time the carrier will have you setup to route thru a SIP path, and may be able to reroute you thru TDM to make the error go away. If you have still have trouble, then you may want to look at our cloud based carrier, etherFAX. etherFAX uses “fax cards in the cloud”, powered by an all TDM network over DS3’s. etherFAX uses a software connector that is installed on your RightFax server and eliminates physical gateways, SIP and T.38 troubleshooting forever.

For a truly awesome fax experience that’s PCI Level 1 with 999.9% reliability, ask us about etherFAX today and say good bye to fax transmission errors.

In RightFax 9.0 and later, RightFax stores its database in SQL server. If the RightFax database log (.LDF) file becomes too large, SQL performance may deteriorate. You should keep your transaction log files to less than 4 GB to avoid performance issues. The following steps will help you shrink the size of your RightFax log file. For more technical tips on RightFax, renew your RightFax Support with Ingenium to gain access to our FAQ Database. Get a quote today.

Prerequisites:

•There are SQL db_owner permissions for the RightFax database.
•RightFax services are all stopped.
•Sufficient free space is available to perform this task. If the transaction log file (.LDF) is 20 GB, for example, verify that you have at least 20 GB free.
•There is sufficient time to perform this task. The size of the log file determines how long the process takes. If the RightFax transaction log file (.LDF) is larger than 10 GB, shrinking it may take 30 minutes or more.
Steps:

Microsoft SQL Server uses the transaction log file (.LDF) for each transaction. The log file is useful for data recovery. To recover data, you can restore a known good backup of the database, and then apply any transactions that took place since your last backup was taken by applying the log file.

Before shrinking the SQL Server database, back up the log file to mark all transactions as committed so they are freed up during the shrink operation.

Step 1: Back Up the SQL Server Transaction Log (.LDF) File:

1. Open Microsoft SQL Server Management Studio.

2. Expand the Databases node.

3. Right-click the RightFax database, and then click Tasks > Backup.

4. For Backup Type, select Transaction Log.

5. Click OK to start the backup operation.

Step 2: Shrink the RightFax Transaction Log File (.LDF):

Now that the log file is backed up, you can shrink it. Shrinking the log file removes white space and committed transactions.

You can shrink your SQL Server transaction log file using SQL Server Management Studio or at the OSQL command prompt. Instructions for both methods are provided below.

Using Microsoft SQL Server Management Studio (Express):

If you do not have SQL Server Management Studio installed, you can download it from the Microsoft website or install it using the Fax Server 9.4 DVD.

1. Open SQL Server Management Studio, and log on.

2. Expand Databases.

3. Right-click your RightFax database, and then click Tasks > Shrink > Files.

4. Ensure that the file type is Log and the file name is correct.

5. Click OK when you are ready to make the changes.

From an OSQL Command Prompt:

1. At a command prompt, type:

osql -S -U<username> -P<password>

For example, to connect to SQL Server as the “sa” user with a password of “password,” enter the following:

osql -SSQLServerRightFax -Usa -Ppassword

At the >1 prompt , type the following, and press ENTER after each line:

USE rightfax
DBCC SHRINKFILE(“RightFax_Log”, 1)
BACKUP LOG RightFax WITH TRUNCATE_ONLY
DBCC SHRINKFILE(“RightFax_Log”, 1)
GO

NOTE: In SQL Server 2008 and 2012 the BACKUP LOG as TRUNCATE_ONLY feature was depreciated and is not recognized as a backup option. The simple recovery model should be used to automatically truncate the transaction log.

Preventing the Transaction Log File (.LDF) from Growing Too Large:

As previously mentioned, for best performance, you should ensure that the RightFax transaction (.LDF) log file remains smaller than 4 GB. The larger it grows over 4 GB, the more likely you are to experience performance issues.

To keep the log file in check, perform regular backups of both the RightFax database (.MDF) file and transaction log (.LDF) file, and then shrink the transaction log file.

You can use the SQL Server Agent to schedule backups. However, the free version of SQL Server Management Studio (the Express version) does not include SQL Server Agent. You require a paid version of SQL Server to schedule backups.

For more information on SQL Server backups, see the References field below.

References: See the following Microsoft Support articles:

“A transaction log grows unexpectedly or becomes full on a computer that is running SQL Server”

http://support.microsoft.com/kb/317375

“How to stop the transaction log of a SQL Server database from growing unexpectedly”

http://support.microsoft.com/kb/873235

“Considerations for the ‘autogrow’ and ‘autoshrink’ settings in SQL Server”

http://support.microsoft.com/kb/315512

“How to schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005”

http://support.microsoft.com/kb/930615

In addition, consult the Microsoft documentation on MSDN and TechNet.