Bit by Bit - Technology Solutions

A common question, when does support end for my version of RightFax.  Well, as of January 17th 2012, here is the product lifecycles.

RightFax 10.0 is currently supported and will enter "end-of-life" status 36 months after release of a subsequent version.

RightFax 9.4 is currently supported and will enter "end-of-life" status on June 30, 2014.

RightFax 9.3 is currently supported and will enter "end-of-life" status on December 31, 2011.

RightFax 9.0 has entered "end-of-life" status. Telephone and email technical support are no longer available effective October 1, 2009.

RightFax 8.7 has entered "end-of-life" status. Telephone and email technical support are no longer available effective September 1, 2008.

RightFax 8.5 has entered "end-of-life" status. Telephone and email technical support are no longer available effective February 17, 2006.

RightFax 8.0 has entered "end-of-life" status. Telephone and email technical support are no longer available effective September 30, 2004.

RightFax 7.2 has entered "end-of-life" status. Telephone and email technical support are no longer available effective August 31, 2003.

RightFax 7.0 has entered "end-of-life" status. Telephone and email technical support are no longer available effective October 31, 2002.

RightFax 6.0, 5.2, and 5.0 have entered "end-of-life" status. Telephone and e-mail technical support are no longer available effective June 30, 2000.

A quick note from OpenText regarding users still on Rightfax 9.3:

Just a friendly reminder that RightFax 9.3 is scheduled to go end of life at the end of December.  After this date we will still support RightFax 9.3 on a best effort basis.  Software bug fixes (hotfixes) will not be available.  To be fully supported start planning for an upgrade or migraton.

The end of life date is posted on our Patches page, and this article:

https://knowledge.opentext.com/knowledge/cs.dll/Open/16224393

To see what you would gain upgrading to RightFax 9.4, or migrating to RightFax 10.0, see these articles:

RightFax Support Matrix

https://knowledge.opentext.com/knowledge/cs.dll/Open/18470211

Bit by Bit is reconmends that clients should get on a supported version of RightFax.  Just like insurance, you wish you had it when you get sick.  It ends up costing more in the long run if you do not upgrade to a supported version of RightFax.

Here is an official press release regarding Rightfax 10 SR2

As part of our regular update schedule, OpenText is pleased to announce the release of RightFax 10.0.0 Service Release 2.

Installation of Service Release 2 is recommended for existing RightFax 10.0.0 deployments. It includes a number of important fixes which may be essential to the operating environment as well as a new feature. This includes:

• Support for RightFax 10.0.0 WebUtil on Microsoft Internet Explorer 9. 

For a complete list of fixed issues and installation instructions, refer to the Readme.

Customers and partners can download Service Release 2 and the Readme from the OpenText Knowledge Center by visiting the link below:

http://knowledge.opentext.com/knowledge/cs.dll/open/15703289

If you need assistance applying the patch, feel free to reach out to Bit by Bit's helpdesk at 212-616-3080 to provide more information.  You can also reach us via email at support@bitxbit.com. 

We had a client that was looking to integrate SAP into Rightfax and found this video very helpful!

I have a client going to Verizon Sip trunking and here is the verbiage taken out of the Sip Trunking informational regarding Fax:

Fax Machines

If your environment is heavy fax shop, or you depend on fax for your day to day operations, Verizon Sip Trunks are NOT the way to go!

As much as we want to say that OpenText is perfect, they have far missed the mark on this one.  When you apply the FP1 SR4 patch, it changes the registry path of where the SR140 driver is located.  The problem is that it changes it to a path where it does not exist!  Here is the workaround:

1. Launch registry editor

2. Navigate to HKLM\SYSTEM\CurrentControlSet\services\bostservice

3. Identify the REG_EXPAND_SZ key and you will find that the image path is set to:



"C:\Program Files (x86)\RightFax\DocTransport\Brooktrout\bostsrv.exe"



4. Change it to:



"C:\Windows\SysWOW64\bostsrv.exe"  



Note-this is for a Windows 2008 R2 Server



5. Perform a Save/Apply now in the Brooktrout Config Tool.

Once done, the SR140 will work as it is supposed to. 

Here is the list of SIP Trunking providers that I know I have had workings with.

The good:

XO

Global Crossing

So far, I have personally tested both providers, and get a good success rate. 

The Bad:

Level3

We have used Level3 for years (since the broadview days) and have never gotten outbound faxing to work.  Inbound faxing has a high success rate for our company.  With that said, we also have not tested outbound faxing in years through that circuit as well.

The Ugly:

Verizon

I have been hearing for years (since 2008) that verizon was going to support T.38 in the next couple of months.  Fast forward to today, and they are still saying that they will support T.38 in the next couple of months.  The takeaway?  If you want to FAX over SIP Trunks, do NOT use Verizon!

Sometimes RightFAX is not perfect, and will sometimes not convert a file correctly.  This can lead to creating a very large fax (over 100 pages) that will be stuck sending out of your server.  No one wants this, it costs money and annoys the recipient of said fax.  Here is how you would go about limiting the amount of pages that RightFAX can send:

1) Enterprize Fax Manager

2) Click on Doctransport Service

3) Click Configure Brooktrout

4) Click BT Call Parameters

5) click Show Advanced

6) Maximum Number of Pages change

Once this number is set, anything over that amount would not be able to be sent out of that server. 

As of August 17th, OpenText is changing their policy on the usage of MFP connectors.  See Product Bulletin 1061 below:

Overview
OpenText is pleased to announce the ability for customers with the OpenText RightFax MFP connectors to exchange those connectors at no cost when switching MFP devices. This allows customers additional flexibility in deploying MFP devices connected to RightFax servers, and protects customer investments in those connectors going forward.

Process
To request an exchange of MFP connectors, please download the OpenText RightFax MFP Connector Exchange Request form from the RightFax Downloads area of the OpenText Knowledge Center. Complete the form with contact information and the names and quantities of the MFP devices that are being exchanged. When the form is submitted, OpenText will adjust the system configuration to reflect the new configuration. Customers running RightFax 9.3 or RightFax 9.4 and migrating to the Ricoh MFP Connectors will need to download the replacement connectors from the OpenText Knowledge Center. All RightFax 9.3 and 9.4 customers and will need to call OpenText Support to have the replacement connectors activated. Customers running RightFax 10 will need to reactivate their RightFax system through the Product Licensing Utility, but no additional downloads or activations are required.

Notes
1. When exchanging MFP connectors only the same quantity level of connectors can be exchanged. As an example if a customer has a Xerox MFP Connector 10-49 Connectors, it can only be exchanged for another connector with the 10-49 designation. If the customer wishes to add or remove connectors from their configuration, please contact their OpenText Authorized reseller or OpenText Sales.
2. The customer is not required to exchange all of their connectors of a particular type at the same time. OpenText realizes that many customers will migrate their MFP fleets in stages, and will need to exchange their connectors over a period of time.
3. Customers requesting exchanges must have their system and connectors covered by a current OpenText support plan. Customers without support requesting exchanges will be required to come back onto support prior to any exchange.
4. If requesting multiple MFP connector exchanges, please submit multiple forms.
5. Normal time to perform an exchange is 2-3 business days.
6. A reminder that starting with RightFax version 10, the Canon and Sharp MFP connectors have been discontinued. Customers running these connectors are strongly encouraged to migrate to the RightFax SMTP MFP connector at their earliest convenience.

I had a client that installed the web client on a IIS 6 web server and everything seemed fine.  When he tried to login, he received the error: Keyword not supported: 'iuser id'.  For the life of me, I was unable to figure out what was causing this issue.  I looked in the Rightfax Remoting services and verified that the proper username and password was entered correctly.  Everything seemed right, but it was not.

Here is an example of the string that the Remoting service was using:

data source=SERVER\RightFax;password=PASSWORD;iuser id=sa;initial catalog=RightFax

Here is an example of a WORKING Remoting service string:

data source=SERVER\RightFax;password=PASSWORD;user id=sa;initial catalog=RightFax

Now, when looking at this, everything looks identical and correct.  When looking closer, the non-working string has iuser instead of user.  Once I changed the username to user, everything worked without a hitch!

Bit by Bit is performing a training session next week, and I would love to have you there!

The training is taught by a certified Rightfax trainer (me :)) with over 8 years of hands on Rightfax experience.  Here are some of the topics that the course will cover:

-Configuration of Core RightFax services

-Troubleshooting RightFax Server issues

-Permissions Needed for Administration

-Registry Keys

-RightFax Boardservers / DocTransport options

-Running services in debug mode

-Troubleshooting Phone Line Problems

-Brooktrout Diagnostic Utilities

-Dialoigic Fax over IP SR140 Installation / Configuration Troubleshooting

-RightFax v9.4 SQL Database

-Optimizing RightFax Services

-Troubleshooting Email Gateway Issues

-Advanced Load Balancing / LCR Rules

-Fax Reporter / Fax Dump

-Creating RightFax Coversheets

-Customizing Active Directory Sync Profiles

-Routing Faxes to things other than EMail or FaxUtil

-RightFax Shared Service Module - “Collective” / Load Balancer

-WebUtil / WebEFM Clients

-Silent Client Install

If you have any questions, feel free to contact me at wvenezia@bitxbit.com.  I would be happy to answer any questions regarding rightfax training!

Yesterday, while trying to demo how to create a PCL coversheet, I had a problem with the "printer" fonts to display.  These are the fonts with the printer icon instead of the TT icon.  When creating PCL code, you NEEED (Cannot stress this enough) to use printer fonts.  After a bit of digging, I came across this webiste:

Method 1: Install a default printer
If your fonts are missing in Word 2007, make sure that a printer driver is installed. You must have a printer driver installed even if there is no printer physically connected to the computer. The fonts that Word 2007 displays in the Font list are based on the specific printer that is installed in Microsoft Windows.

To install a default printer driver, follow these steps:
1. Exit all instances of Word 2007. If you use Word 2007 as your e-mail editor, exit Microsoft Office Outlook 2007.
2. Click Start, and then click Printers and Faxes.
3. Click Add a printer.
4. In the Add Printer Wizard, click Next.
5. Click Local Printer, click to clear the Automatically detect and install my Plug and Play printer check box, and then click Next.
6. If you receive a message that prompts you whether you want to install a printer manually, click Next.
7. Click the port that you want to use, and then click Next.
8. In the Manufacturer list, select the appropriate printer manufacturer. In the Printers list, click the printer model that you want, and then click Next.
9. Select any options that you want, and then click Next. Repeat this procedure for each page of the wizard until you reach the end. Then, click Finish.

Method 2: Select an appropriate printer driver
If the fonts are missing in Word 2007, make sure that an appropriate printer driver is selected. An appropriate printer driver may be installed in Windows. However, an inappropriate printer driver may be selected. For example, a fax driver or a generic/text only driver may be set as the default printer. To make sure that you have an appropriate printer driver selected in Word 2007, follow these steps:
1. Click the Microsoft Office Button, and then click Print.
2. In the Name box, click a printer that is installed on the computer.

Note For Word 2007 to correctly display the available fonts on a computer, a printer must be selected even if a printer is not physically connected to the computer.
3. Click Close to close the Print dialog box.

So, in order to get around this, I created a HP LaserJet 4 printer (required anyways) and set this as the default printer.  When done, the proper fonts would appear!

FAXING FROM PHYSICAL KONICA BIZHUB 751 MACHINES:

Press the Fax/Scan button

Press the 3^rd tab – Direct Input

 Click on the Fax button:

Enter the fax number with a 1, the area code, and the number (ex. 12125555555) THEN PRESS OK:

Place the document(s) in the manual tray face up

Press the start button on the control panel :

FINISHED!  You have sent a fax!

NOTE: When written, Service Release 3 for 9.4 was the latest service pack.  Service pack 4 for 9.4 can be obtained here: https://knowledge.opentext.com/knowledge/llisapi.dll/Open/18922469

As far as the inplace upgrade, a few things need to occur.

1. Make sure existing environment is on 9.3 FP2 SR6

2. Make backup of SQL database prior to running upgrade

3. Backup rightfax directory prior to inplace upgrade

4. Make sure server has access to internet prior to inplace upgrade

Once done: perform the following:

NOTE: In order to download the files form the links, you need to have a knowledge base account issued by Open Text.  Feel free to contact Bit by Bit at support@bitxbit.com if you need assistance with getting this.

Run Rightfax 9.4 Setup.exe on Rightfax 9.3 server. Media can be downloaded here (once form is completed)
32 bit install: http://mimage.opentext.com/support/ecm/secure/software/capture/rightfax/94nax64/rf94nax64.iso
64 bit install: http://mimage.opentext.com/support/ecm/secure/software/capture/rightfax/94na/rf94na.iso

Run through install.
Click OK on licensing utility.  Ensure that proper license information is met (it will inform you if there is a conflict) Install FP1.  Media can be downloaded here: https://knowledge.opentext.com/knowledge/llisapi.dll/RightFax940_FP1.exe.bin?func=doc.Fetch&nodeid=17264660&docTitle=RightFax940_FP1%2Eexe

Install FP1 SR3. Media can be downloaded here:  https://knowledge.opentext.com/knowledge/llisapi.dll/RightFax940_FP1SR3.exe.bin?func=doc.Fetch&nodeid=18236044&docTitle=RightFax940_FP1SR3%2Eexe

Updated version of the rightfax client can be downloaded here: https://knowledge.opentext.com/knowledge/llisapi.dll/RightFaxClientNA941SR3.zip?func=doc.Fetch&nodeid=18236599&docTitle=RightFaxClientNA941SR3

I had a client that was looking to automate uninstalling/reinstall rightfax client, and needed to delete the registry keys created by rightfax after the automatic uninstall took place.  Faxutil generates registry keys in two hives as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Rightfax Client

HKEY_CURRENT_USER\Software\Rightfax Client

 **NOTE: For 32 bit clients, remove the Wow6432Node folder.**

Since it was automated, he did not have access to the Current User registry, but removing the HKLM keys seemed to do the trick for his process.  Once these keys were also deleted, he was able to perform the uninstall/reinstall.