This document provides late-breaking or other information that supplements the RightFax documentation. Service packs are the means by which RightFax product updates are distributed from the Captaris Web site. A service pack may contain updates for system reliability, program compatibility, performance improvements, and more. All service packs are cumulative. Each contains new fixes plus all the fixes from previous hot fix and service pack releases.
This document describes the current update to this version of the RightFax server and fax board driver software. It provides installation instructions and a brief description of problems fixed with this release.
By
the time you receive this software, updates to other RightFax software
may be available. To obtain updates, go to http://www.captaris.com/customer_support.
This service pack should be installed on computers that are running version 8.5 of all types of RightFax server except Financial server. Follow these steps to confirm that a computer has this version of the RightFax server installed.
From the computer desktop, select Start > Settings > Control Panel. If this computer is a RightFax server, the Control Panel will include an application called RightFax Server. If this application is not present, do not run the update program RightFax Server Update 8.50 SP5 Server Patch.exe on this computer.
Double-click RightFax Server. The Server Configuration dialog box opens. The server version number and any installed service packs are displayed in the title bar of this dialog box. If the version number is anything other than 8.5 (with or without earlier installed service packs), do not run the update program RightFax Server Update 8.50 SP5 Server Patch.exe on this computer.
When you have confirmed that the version is correct, click the Feature Activation tab. The third item in the list of features is the server type. If the server type is listed as "Financial Server" do not install this service pack. Separate service packs for these server types are available. If any other type of RightFax server is listed, you should close the Server Configuration dialog box and proceed to install this service pack and the service pack for fax boards drivers.
To update your software, Microsoft Windows Installer will patch your existing RightFax installation by replacing existing files with updated files and installing new files.
Log on to the RightFax 8.5 server as an administrator.
Run the program RightFax Server Update 8.50 SP5 Server Patch.exe located on your update CD or extracted from the downloaded .zip file.
At the introductory screen, click Update. A status bar will indicate the progress of the installation.
When the installation is complete, click Finish.
If you have licensed the SNMP Alerting Module and you have not previously installed a RightFax 8.5 service pack, you must complete the installation of the SNMP Alerting Module. To do so, refer to the RightFax 8.5 SNMP Alerting Module Guide, Chapter 1, "Installing and Configuring the SNMP Alerting Module."
After completing the service pack installation for the RightFax server, you must install the service pack for the fax board drivers (described in the next section) and the Web Client, if applicable.
To update your software, Microsoft Windows Installer will patch your existing RightFax installation by replacing existing files with updated files and installing new files.
When the installation of Service Pack 5 for the RightFax Server is complete, remain logged on to the RightFax 8.5 server as an administrator.
Run the program RightFax 8.50 SP5 Hardware Patch.exe that you extracted from the downloaded .zip file.
At the introductory screen, click Update. A status bar will indicate the progress of the installation.
When the installation is complete, click Finish.
The installation program includes Brooktrout TR1034 fax board firmware. If you have one of these fax boards installed, you must run a batch file that installs the firmware to the boards. Open a command prompt window. Navigate to the folder RightFax\RFBoard\Boston and run Flashupd.bat. This step gets the firmware from the folder C:\Program Files\RightFax\RFBoard\Boston. To change the path, edit the Flashupd.bat file in any text editor. In the file, change the loader path to the correct path to the folder that contains the firmware. This command only supports short file names, so you may need to truncate folder names, such as "Program Files" to "Progra~1".
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
30687 |
BoardServer |
DTMF setting for channels in the BoardServer does not affect what the channel actually plays for TR-114 fax boards. |
In this update, the DTMF setting for channels behaves as expected. |
|
32311 |
BoardServer |
BoardServer availability index in the Enterprise Fax Manager does not update with timed ability. |
In this update, the error does not occur. |
|
32356 |
BoardServer |
All failed phone calls become failed faxes when using T1 PRI on TR1034 fax boards. |
In this update, failed phone calls do not become failed faxes. |
|
33738 |
BoardServer |
Brooktrout TR114-I2BRI and TR114-I4BRI cards install as PCI, not ISA. |
In this update, the cards install and can be configured correctly. |
|
33950 |
BoardServer |
The Enterprise Fax Manager displays this error when configuring a BoardServer module on a client machine: Error Reading Bump: |
In this update, the error does not display. |
|
34355 |
BoardServer |
When a transfer is disconnected, Smart Resume does not detect the pages sent before restarting the transfer. |
In this update, Smart Resume detects the pages sent before the interruption and sends only the remaining pages. |
|
34581 |
BoardServer |
Changing the Board Model country of origin does not affect the speed of data transfer. |
In this update, the Board Model setting is disabled and set to USA for all currently supported TR1034, TRNIC, and TR114+P8V-T1 fax boards. |
|
34622 |
BoardServer |
TR1034 series board are interpreting incoming faxes from some fax machines as binary file transfers, causing incoming faxes to be mistakenly deleted. |
In this update, the error does not occur because it includes updated firmware for TR1034 series boards. |
|
34719 |
BoardServer |
The human answered fax feature does not work correctly on Brooktrout series TR1034 fax boards if the human answering gives no response. |
In this update, a registry value is available to modify the human answered fax feature.
|
|
35261 |
BoardServer |
Bad lines on received faxes result in blank pages and an OK status when Error Correction mode is turned off the machine sending the fax. |
In this update, bad lines on a fax do not send an OK status. |
|
36585 |
BoardServer |
The Network Specific Facility option is not available in the Digital Configuration Wizard for Brooktrout series TR1034 fax boards when using PRI T1. |
In this update, the Network Specific Facility option is available for the TR1034 series boards. |
|
36667 |
BoardServer |
The TR1034 series board requires an ANI pattern match in order to pass ANI data. |
In this update, an ANI pattern match is not required. |
|
36561 |
BrookTrout Adapters |
When using a TR1034 series board, channels are unresponsive if a PPS-EOM or EOM message is received during a transmission. |
In this update, channels function correctly when the messages are received. |
|
34366 |
Database |
Duplicate cover sheet entries exist in the More Options tab of FaxUtil. |
In this update, the cover sheet entries are not duplicated. |
|
34724 |
Database |
Running a rescue with delayed faxes in the system causes the faxes to never send. |
In this update, the delayed faxes are sent. |
|
36870 |
Exchange Connector |
Multiple RightFax e-mail addresses are generated for some Exchange users. |
In this update, multiple e-mail addresses are not generated. |
|
33916 |
Exchange Gateway |
The DoNotStripPlus registry entry deletes fax numbers when set to 1. |
In this update, the fax numbers are not removed. |
|
37035 |
Exchange Gateway |
The Exchange Gateway writes unnecessary entries to the Event Viewer regularly. |
In this update, unnecessary entries are not written to the Event Viewer. |
|
32925 |
Integration Module |
Downloading TIFF files is possible if specified by manually typing a registry entry. However, manual registry entries are lost when changes were made to the Integration Module Configuration. |
In this update, a new checkbox, Download TIFF Files, was added to the Integration Module Configuration dialog box. |
|
33906 |
Integration Module |
An empty e-mail is sent when the {{Type email}} command is used in Filter mode. |
In this update, the {{Type email}} command sends an e-mail with the specified content. |
|
34728 |
Integration Module |
MQGet disconnects if it does not reach the Queue Manager immediately. |
In this update, a registry value is available to specify how long MQGet should attempt to connect until timing out.
|
|
34798 |
Integration Module |
Substitution for Courier font displays incorrectly. |
In this update, Courier font substitution displays correctly. |
|
34860 |
Integration Module |
Invalid FCL margin settings cause an exception error to occur. |
In this update, the margin settings do not cause an exception error. |
|
35023 |
Integration Module |
Running Notify in Debug Mode does not display complete debug information. |
In this update, the debug information is complete. |
|
35052 |
Integration Module |
Buffer incorrectly displays error messages on valid documents. |
In this update, errors do not display on valid documents. |
|
35057 |
Integration Module |
MapText image preview does not work when applying a text overlay, then generating the image. |
In this update, the image generates correctly. |
|
35122 |
Integration Module |
Adding new input devices via the Integration Module Configuration window removes existing input devices. |
In this update, existing input devices are not removed. |
|
35127 |
Integration Module |
Consecutive spaces in a filename or path cause errors when using FCL commands. |
In this update, FCL commands can use multiple consecutive spaces. |
|
35199 |
Integration Module |
Using Mailsend.exe with command line option -o converts the recipient's e-mail address to ASCII. |
In this update, the e-mail address is not converted to ASCII. |
|
35530 |
Integration Module |
The {{onerror}} and {{onsuccess}} FCL codes are ignored in a Business Integration environment. |
This is by design; these codes should not be available in a Business Integration environment. In this update, the ability to use the {{onerror}} and {{onsuccess}} FCL codes was removed from the Integration Module Configuration dialog box. |
|
35891 |
Integration Module |
Error logs are not produced when IBM WebSphere MQ messages are not converted. |
In this update, error logs are generated when IBM WebSphere MQ messages are not converted. |
|
36384 |
Integration Module |
The notification feature does not work when run in conjunction with the RightFax Integration Module. |
In this update, the notification feature works correctly. |
|
37347 |
Integration Module |
Faxes are not held according to the Seconds to Age configuration setting. |
In this update, the Seconds to Age setting works correctly. |
|
8249 |
Notes Gateway |
Sending faxes using Lotus Notes phone books result in square brackets around the address name and underscores instead of spaces. |
In this update, the brackets and underscores do not appear. |
|
30277 |
Notes Gateway |
The From: field is populated incorrectly on the cover sheet when a fax is sent with Lotus Notes. |
In this update, the From: field is populated correctly. |
|
33164 |
Notes Gateway |
Routing forms with Notes Native Export results in distorted images. |
In this update, the images display correctly. |
|
33197 |
Notes Gateway |
Graphics and margins display incorrectly when forwarded e-mail messages are configured with the Microsoft RTF format. |
In this update, the graphics and margins display correctly. |
|
33985 |
Notes Gateway |
The Notes Gateway displays an exception error when there are more than 2010 characters in the Subject line. |
In this update, the Notes Gateway is not affected by the number of characters in the Subject line. |
|
33445 |
RightFax server |
The "During transmission" message is sent instead of "Error encountered, fax will be abandoned." |
In this update, the error does not occur. |
|
35027 |
RightFax server |
An incorrect error message displays when automatically forwarding to a group. |
In this update, Automatic Forwarding Options do not cause incorrect error messages. |
|
35116 |
RightFax server |
Sent e-mails with native attachments do not include the attachment if forwarded. |
In this update, the attachments accompany the forwarded e-mail. |
|
35865 |
RightFax server |
RightFax is incompatible with the Microsoft SNMP Service and generates errors after installation. |
In this update, RightFax and the Microsoft SNMP Service are compatible. |
|
36307 |
RightFax server |
The ReceiveStampFormat variable ~C does not reset the page count after midnight. |
In this update, the page count is correctly reset after midnight. |
|
37059 |
RightFax server |
File conversion is unsuccessful when multiple postscript files are sent to HPFAX. |
In this update, multiple postscript files are converted successfully. |
|
37119 |
RightFax server |
Faxes that are routed into a gateway and received with a transmission error automatically change status to Scheduled to be Sent. |
In this update, transmission errors do not change the fax status to Scheduled to be Sent. |
|
37171 |
RightFax server |
Microsoft Word XP causes WorkServer to fail when a large number of faxes are sent. |
In this update, Microsoft Word does not cause the WorkServer to fail. |
|
37736 |
RightFax server |
Conversion fails when multiple PDF documents are attached to a fax. |
In this update, multiple PDF documents can be attached to a fax. |
|
33505 |
SAP |
Fax senders are specified as Administrator, instead of the default user ID, when the user is not found in RightFax. |
In this update, the default user ID is used as expected. |
|
35167 |
SAP |
The postscript data output from SAP is truncated. |
In this update, the postscript data is not truncated. |
|
35325 |
SAP |
Genmailmsg work requests are not sent to SAP as notifications. |
In this update, Genmailmsg work requests are sent to SAP as notifications. |
|
34846 |
SMTP Integration |
The SMTP Gateway is unable to log on when using the e-mail services that accompany Windows 2003 server. |
In this update, the SMTP Gateway logs on successfully. |
|
34983 |
SMTP Integration |
All fax bound e-mails formatted as RTF or HTML append the HTML codes to the end of the fax. |
In this update, RTF and HTML e-mails display correctly. |
|
35110 |
SMTP Integration |
Fax bound e-mails take a long time to process if they are larger than 1 MB. |
In this update, large faxes process in a timely manner. |
|
35111 |
SMTP Integration |
SMTP Gateway is unable to send a fax to multiple recipients. |
In this update, the SMTP Gateway can send faxes to multiple recipients. |
|
35287 |
SMTP Integration |
The SMTP Gateway creates unnecessary network traffic when checking the POP 3 server. |
In this update, unnecessary traffic is not generated when the SMTP Gateway communicates with the POP 3 server. |
|
35352 |
SMTP Integration |
Cannot send faxes via a Sun ONE server if the address line contains carriage returns or more than 76 characters. |
In this update, the address line may contain carriage returns or more than 76 characters. |
|
35896 |
SMTP Integration |
Cannot route inbound faxes to multiple recipients via the SMTP Gateway. |
In this update, the SMTP Gateway allows inbound faxes to be routed to multiple recipients. |
|
36926 |
SMTP Integration |
Embedded codes in the body of an SMTP message are not recognized by the SMTP Gateway if HTML code is in the body of the message. |
In this update, embedded codes are recognized by the SMTP Gateway. |
|
37115 |
SMTP Integration |
The SMTP Gateway writes unnecessary entries to the Event Viewer regularly. |
In this update, unnecessary entries are not written to the Event Viewer. |
|
37168, 38987 |
SMTP Integration |
Faxes cannot be sent through a user account if the username contains an underscore ( _ ). |
In this update, the username may contain an underscore ( _ ). |
|
35703 |
Standalone Fax Connector |
The Standalone Fax Connector, when configured to require and validate billing codes, sends faxes with invalid billing codes. |
In this update, the Standalone Fax Connector does not send faxes with invalid billing codes. |
|
31773 |
WorkServer |
PDF and TIFF files are not created from partially received faxes. |
In this update, the error does not occur. |
|
32779 |
WorkServer |
Phone book entries are not private for users created via synchronization from Exchange 5.5 with NT Authentication. |
In this update, the phone book entries remain private. |
|
33195 |
WorkServer |
LaserNT, the PCL conversion engine, does not word wrap text. |
In this update, a registry key is available to format the text correctly.
|
|
33278 |
WorkServer |
History pages do not print when using a Windows GDI printer. |
In this update, the History pages print as expected. |
|
33968 |
WorkServer |
An "OCR Processing Failed" status displays when the OCR configuration is set to Hebrew in the WorkServer control panel. |
The Hebrew language option is not supported and is no longer a selection. |
|
34044 |
WorkServer |
The Time Strip does not print when using a Windows GDI printer. |
In this update, the Time Strip prints correctly. |
|
34338 |
WorkServer |
Using a Windows GDI printer to auto-print cover sheets and history is inconsistent. |
In this update, the cover sheets and history auto-print as expected. |
|
34424 |
WorkServer |
Users are not deleted when Active Directory synchronization is set to Always and the user's mailbox contains one or more faxes. |
In this update, the users are deleted in this scenario. |
|
34469 |
WorkServer |
Images acquired through a TWAIN scanner are smaller than expected. |
In this update, the error does not occur. |
|
34585 |
WorkServer |
PCL files created with Macro4 fail conversion when sent as attachments. |
In this update, the PCL files convert and print correctly. |
|
34767 |
WorkServer |
Active directory synchronization fails if the permission to read an object or Organization Unit is removed from the Everyone group. |
In this update, Active Directory synchronization does not fail in this situation. |
|
34964 |
WorkServer |
Long filenames result in an incorrect Recipient Fax ID and unsent faxes when the HP NetScan Interface is enabled. |
In this update, the long filenames do not cause problems. |
|
35216 |
WorkServer |
Faxes are not archived when sent to an e-mail address. |
In this update, faxes are archived. |
|
35278 |
WorkServer |
TIFF files are not converted when generated by a Xerox machine. |
In this update, the TIFF files convert correctly. |
|
35561 |
WorkServer |
Memory usage increases during an Active Directory synchronization that is configured with a connection time of Always Run. |
In this update, memory usage does not increase during this situation. |
|
35644 |
WorkServer |
The automatic TIF naming convention does not support 8.3 file naming convention. |
In this update, a registry key is available to allow an 8.3 file naming convention.
|
|
36011 |
WorkServer |
Server-side application conversion truncates RTF documents if Microsoft Word is not installed on the server. |
In this update, RTF documents are converted correctly. |
|
37239 |
WorkServer |
Certain GIF and JPEG images are not converted. |
In this update, these GIF and JPEG images are converted. |
|
37483 |
WorkServer |
WorkServer fails to create TIFF G4 for incomplete received faxes when routing to a network directory. |
In this update, a registry key is available to convert the TIF file.
|
|
37612 |
WorkServer |
Microsoft Excel remains open when an Excel document is sent as an attachment via the SMTP Gateway. |
In this update, Microsoft Excel does not remain open after the fax is converted. |
|
37812 |
WorkServer |
Receipt of a transmission error fax causes GDI printing to stop. |
In this update, transmission errors do not affect GDI printing. |
|
37846 |
WorkServer |
Enabling automatic printing of the fax history causes a FaxPrint error. |
In this update, the FaxPrint error does not occur and the history prints successfully. |
|
40017 |
WorkServer |
Large TIF files cause conversion failure. |
In this update, the large TIF files are converted to an 8 byte gray-scale image. |
|
|
|
|
|
This update provides support for the Brooktrout TR1034 fax board for E1 and T1 ISDN Primary Rate Interface (PRI) telephone lines, and the TR1034 4-port fractional T1 fax board (TR1034+P4-T1). This update also improves the error rate of the Brooktrout TR1034 fax board.
Caution: Brooktrout TR1034 fax boards cannot be combined in the same computer with Brooktrout TR114 fax boards. Combining these board types will prevent the RightFax BoardServer service from starting.
Decreasing FaxUtil load time
The time required for each user to load the FaxUtil client application depends largely on the number of RightFax users configured on the RightFax server that FaxUtil is accessing. If the RightFax server contains a large number of users, FaxUtil may be noticeably slow to load.
If the number of users configured on the RightFax server results in slow FaxUtil load times, you can create a registry entry on client computers that disables the automatic loading of users when FaxUtil is run. The loading of user records will occur only if a user performs actions in FaxUtil that require it.
You can disable the loading of two types of user: administered users and unprotected users.
Administered users are users that appear in a RightFax administrators or group administrators FaxUtil mailbox.
Unprotected users are users who have the Unprotected mailbox permission set in their user profiles. These users appear in all other FaxUtil user lists as though they had delegated everyone else to allow them to access their fax mailboxes.
For RightFax administrators, disabling the loading of both administered and unprotected may be necessary. For all other FaxUtil users, it is only necessary to disable the loading of unprotected users.
To disable the loading of administered users
To disable the loading of administered users in FaxUtil on startup, close FaxUtil and then add a REG_DWORD value called LoadAdministeredUsers to HKEY_CURRENT_USER\Software\RightFAX Client\FUW32 and set the value data to 0 (zero).
To disable the loading of unprotected users
To disable the loading of unprotected users in FaxUtil on startup, close FaxUtil and then add a REG_DWORD value called LoadUnprotectedUsers to HKEY_CURRENT_USER\Software\RightFAX Client\FUW32 and set the value data to 0 (zero).
To automatically disable user loading for new FaxUtil users
These REG_DWORD values can also be applied for all new FaxUtil users on a particular computer. Modify the Windows Registry to add the REG_DWORD values described above to HKEY_LOCAL_MACHINE\Software\RightFAX Client\FUW32. When users run FaxUtil for the first time, they will be automatically configured to disable the loading of users.
This update provides support for the Brooktrout TR1034 fax board for E1 and T1 ISDN Primary Rate Interface (PRI) telephone lines, and the TR1034 4-port fractional T1 fax board (TR1034+P4-T1). This update also improves the error rate of the Brooktrout TR1034 fax board.
Caution: Brooktrout TR1034 fax boards cannot be combined in the same computer with Brooktrout TR114 fax boards. Combining these board types will prevent the RightFax BoardServer service from starting.
A new icon
(
) will be displayed in FaxUtil for received faxes that
were routed to an e-mail client through an e-mail gateway.
The command-line version of Rescue.exe has been restored to the RightFax\AdmUtils folder for purposes of backward-compatibility. For documentation on running Rescue.exe from the command line, execute the command Rescue /?.
To use the rescue utility's functions without performing the database recovery function (which may take several hours on very large databases), add the REG_DWORD value DisableRecovery to HKEY_LOCAL_MACHINE\SOFTWARE\RightFax\Faxserver and set the data value to 1.
Users can import phonebooks in FaxUtil by selecting Phonebook Import on the Tools menu. With this update, the Phonebook Import option in FaxUtil can be enabled or disabled for a group of users.
To disable the import of phonebooks:
Edit the user group in Enterprise Fax Manager.
In the Group Edit dialog box, click the Fax Dialog Customization tab. Select the Phonebook Import Main Menu Option check box.
In the RightFax Integration Module, the Bar33 font has been replaced with a new version. If your FCL documents use the Bar33 font, verify that the documents are formatted as expected.
The RightFax server now supports the following models of the Xerox multifunction products:
WorkCentre Pro 32/40
WorkCentre Pro 65/75/90
WorkCentre Pro 35/45/55
For information on updating an existing Xerox integration see the section entitled Updating the RightFax Integration with Xerox Multifunction Products.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
31588 |
AutoReply |
The AutoReply service will stop if more than 27 users are monitored for automatic responses. |
In this update, the service will not stop. |
|
9291 |
BoardServer |
Fax audit logs (.csv files) with logging level 3 included a line break every 51 lines. |
In this update, line breaks are not inserted in the fax audit log. |
|
11439 |
BoardServer |
With Brooktrout TR114+P8V-T1 and TR114+P16V fax boards, fax channels hang in a status of "Training" until the BoardServer Module is stopped and restarted. |
In this update, the error does not occur. |
|
11666 |
BoardServer |
If the BoardServer module is stopped and started and faxes are sent immediately thereafter, then the Server module repeatedly sends the faxes. The sent faxes remain in scheduled-to-be-sent status. |
In this update, the error does not occur. |
|
11865 |
BoardServer |
When setting up the RightFax Docs-On-Demand Module, the Require Dialing Rule Match on Fax Server check box could not be cleared. |
In this update, the check box can be cleared. |
|
12299 |
BoardServer |
With a Dialogic
CP2400CT-T1 fax board, while receiving a multipage fax and a transmission
error occurs, the BoardServer module reports the following error even
though the TIFF image properties indicate a width of 1728: |
In this update, the error does not occur. |
|
30094 |
BoardServer |
With Brooktrout TR1034 fax boards, fax channels are not being disconnected after transmission. |
In this update, the error does not occur. |
|
30113 |
BoardServer |
With Intel Dialogic DM3 fax boards, the Dialogic system service hangs on reboot. |
In this update, the error does not occur. |
|
31077 |
BoardServer |
With Intel Dialogic DM3 fax boards, Enterprise Fax Manager shows a state of "Sending" when the channel is configured to receive. |
In this update, the error does not occur. |
|
31704 |
BoardServer |
With Brooktrout TR1034 fax boards, sending a fax to 954-677-1011 causes a fatal exception error. |
In this update, the error does not occur. |
|
31769 |
BoardServer |
The human answered fax feature does not work on Brooktrout TR1034 series fax boards. |
In this update, the human answered fax feature works on the Brooktrout TR1034 series fax boards. |
|
31831 |
BoardServer |
Cannot assign a dialing prefix for each channel in the Windows Registry. |
In this update, a dialing prefix can be set for each channel via the Windows registry. |
|
32105 |
BoardServer |
With BRI or PRI ISDN fax boards and the Windows Registry key ISDN_InboundSelect set to use the redirected number (RN), inbound routing fails to select the redirected number. |
In this update, the error does not occur. |
|
32143 |
BoardServer |
Brooktrout TR114 fax boards error in transmission when receiving from HP3100 fax machines. |
Updated firmware from HP is included in this update, and the error does not occur. |
|
32159 |
BoardServer |
With Brooktrout TR114+P8V-T1 and TR114+P16V fax boards, fax channels hang in a status of "Training" until the BoardServer module is stopped and then restarted. The parameter "max_timeout" does not reset the hung channels. |
In this update, the error does not occur. |
|
32182 |
BoardServer |
Intel Dialogic fax boards do not support the Quick Headers feature, described in the RightFax Administrator's Guide. |
In this update, this option has been removed from the configuration dialog box for Dialogic fax boards. |
|
32228 |
BoardServer |
With call grouping enabled in the global fax board settings, audit levels 3 and 4 do not provide the correct level of report details. |
In this update, the BoardServer audit logs report the correct level of data. |
|
32355 |
BoardServer |
If the RightFax server name is 13 characters or longer, bump information is not read. |
In this update, a long RightFax server name does not prevent bump information from being read. |
|
32387 |
BoardServer |
The Disable Loop Current Detection option is not available for Intel Dialogic CPi-series fax boards. |
In this update, the Disable Loop Current Detection option is enabled for CPi-series fax boards. |
|
32589 |
BoardServer |
Using PRI-PCI32V and TR114+P16V fax boards on a PRI-E1 line during a broadcast of 200 or more faxes, some fax channels fail to reset. |
In this update, fax channels will reset properly. All TR1034 service packs must be installed. |
|
32755 |
BoardServer |
RightFax fails to properly detect CPi/400B2 fax board. |
In this update, the CPi/400B2 is properly detected. |
|
33384 |
BoardServer |
Brooktrout TR114-P8V-T1 and TR114-P16V fax boards receiving multi-page faxes from remote devices whose line is disconnected during transmission report the fax transmission as "OK." |
In this update, the transmission status is correctly detected and reported. |
|
34370 |
BoardServer |
Dialing rules in which a specific number is set to "disallow" are displayed incorrectly during a "Route Trace" test. |
In this update, dialing rules of this type are displayed correctly during a "Route Trace" test. |
|
12245 |
E-mail Gateway |
The debug log file SMTPDump.txt is created in the RightFax\Gateway folder. The file occupies disk space and cannot be canceled. |
In this update, the debug log is not generated. You can delete SMTPDump.txt. |
|
10655 |
ETransport |
E-mail messages sent from the RightFax server included bare line feeds, which caused the messages to be discarded by recipient servers on the Internet. |
In this update, bare line feeds are not sent in e-mail messages. |
|
8917 |
Exchange Connector |
After removing, recreating, or modifying an SMTP e-mail address in Microsoft Exchange, the E-mail Address field in RightFax fails to populate after user synchronization. |
In this update, the E-mail Address field will populate as expected. |
|
9570 |
Exchange Connector |
Changing user notification settings in Exchange does not properly update RightFax after user synchronization. |
In this update, the user notification settings are updated in RightFax as expected. |
|
31176 |
Exchange Connector |
Faxes fail when they are sent from Outlook 2000 using the Outlook e-mail form and the FAX addressing format. |
In this update, faxes can be sent from Outlook 2000 using the Outlook e-mail form and the FAX addressing format. |
|
11802 |
Exchange Gateway |
When faxes are sent from Outlook, message files (M*.tmp) are left in the folder RightFax\Gateway\Out. |
In this update, message files do not remain in the folder RightFax\Gateway\Out. |
|
12223 |
Exchange Gateway |
If default billing codes are defined for users and faxes are sent from Outlook using the Outlook e-mail message form, the billing codes are not captured. |
In this update, the billing codes are captured. |
|
11605 |
Install |
With Brooktrout TR1034 fax boards, the installation of the firmware to the fax boards fails. |
In this update, the installation succeeds. |
|
30020 |
Install |
A component of the RightFax SNMP Alerting Module was not installed with RightFax 8.5. |
In this update, the RightFax SNMP Alerting Module can be fully installed. Refer to the installation instructions in this readme file for more information. |
|
11715 |
Integration Module |
Invalid FCL tags do not generate error messages. |
In this update, invalid FCL tags generate error messages. |
|
30322 |
Integration Module |
In the Integration Module, the Bar33 font does not print the numbers 1 and 2. |
In this update, the Bar33 font includes the number 1 and 2 and displays them as expected. |
|
30335 |
Integration Module |
In the Integration Module, Notify.exe, Parse.exe, and Buffer.exe generate memory exception errors when the Integration Module service is stopped. |
In this update, the errors do not occur. |
|
30388 |
Integration Module |
When a MIME document is sent through the Integration Module on a Windows NT 4.0 system, an application error occurs. |
In this update, the error does not occur. |
|
30776 |
Integration Module |
With the Integration Module, a problem occurred in FCL documents that contain the {{MoveTo}} command and that are generated on a Unix system. If the text after the {{MoveTo}} command is on a new line, then the text was not captured for the document. |
In this update, a new Windows registry entry can be used to capture the text on a new line. If you are using the {{MoveTo}} command in a Unix system that generates FCL documents, you must add a value to the Windows registry in order to support the command. On the RightFax server, edit the Windows registry. Navigate to the subkey HKEY_LOCAL_MACHINE\Software\RightFax\Parse. Add the REG_MULTI_SIZE registry value UnixSpecials. Enter the string "MoveTo" in the multi-string editor. |
|
31657 |
Integration Module |
In the Integration Module, a document with a {{SetTab FCL}} command of 20 or higher causes a memory exception error. |
In this update, the error does not occur. |
|
31753 |
Integration Module |
With the Integration Module and the InternetLink Module, a document can be sent to multiple to e-mail addresses. A defect caused the document to be sent multiple times to the first e-mail address. |
In this update, the document is correctly sent to several e-mail addresses. |
|
31762 |
Integration Module |
With the Integration Module, documents that can be sent using directory scanning and the program Bufdir.exe. Files with dates in the future caused the program Bufdir.exe to stop. This could occur with documents created on systems in different time zones. |
In this update, Bufdir.exe does not stop. Documents with dates in the future are processed and sent when the date and time on the local system matches the date and time in the document. |
|
32026 |
Integration Module |
With the Integration Module, PCL documents that contain {{OnError E-mail}}, {{OnError Mime}}, {{OnSuccess E-mail}}, or {{OnSuccess Mime}} fail conversion in the RightFax WorkServer. |
In this update in the Integration Module, PCL documents that contain {{OnError E-mail}}, {{OnError Mime}}, {{OnSuccess E-mail}}, or {{OnSuccess Mime}} are successfully converted in the RightFax WorkServer. |
|
32108 |
Integration Module |
With the Integration Module, if the {{Attach}} FCL command is used and the attached file does not exist, no errors are recorded and the fax is recorded as successful. |
In this update in the Integration Module, if the {{Attach}} FCL command is used and the attached file does not exist, correct errors are logged. |
|
31419 |
Mimesend |
If the SMTP mail server uses SMTP service extensions (ESMTP), e-mail messages could not be sent. |
In this update, a new check box appears in the Server Configuration dialog box on the eTransport tab. Select the "SMTP service extensions" check box if your system uses SMTP service extensions. |
|
31576 |
Mimesend |
With the Integration Module, when a fax is sent as a type MIME document and an overlay form is used, the fax image is distorted. |
In this update, the fax image is rendered correctly without distortion. |
|
31916 |
MQ Series |
In the Integration Module, MQGet.exe and MQPut.exe are not designed to work with the WebSphere MQ Application Programming Reference Version 2. The module does not provide a method for specifying the codeset name for the language in WebSphere MQ. |
In this update, MQGet.exe and MQPut.exe work with the WebSphere MQ Application Programming Reference Version 2 by default. A command line option has been added that allows you to specify version 1 of the WebSphere MQ API: -1 Selects
Version 1 of the WebSphere MQ API. |
|
31693 |
OCR |
OCR routing fails due to OCR library initialization error. |
In this update, OCR routing performs as expected. |
|
31649 |
Paging Service |
CSID does not appear in pager notifications if first character is "+". |
In this update, an initial "+" character in a CSID is supported for pager notifications. |
|
33325 |
Paging Service |
Pager alert for "Probable Line Failure" is never sent. |
In this update, the "Probable Line Failure" alert is sent as expected. |
|
12365 |
PostScript |
PDF files fail to convert to fax format properly. Symptoms may include failed conversion, partial conversion, all-black pages, or distorted text. |
In this update, PDF files convert to fax format without displaying these symptoms. |
|
32504 |
PostScript |
PDF/PostScript Module converting with ASCII85 compression converts last character on a line incorrectly. Last character is incremented by 1. |
In this update, the last character in a line is converted correctly. |
|
12405 |
Production Notifications |
In the Integration Module, the syntax "hf -s 12345 c:\boot.ini cis-rf80" returns a syntax error. |
In this update, the error does not occur. |
|
30793 |
Production Notifications |
In the Integration Module, the error "hlpisend: Unknown command line argument -^" occurs when the following command line is run from the Production/Bin directory: "hlpisend -s A -l C:\Program Files\RightFax\Production\Include\login.inc" -H 1 -d -v <file>". |
In this update, the error does not occur. |
|
32580 |
Production Notifications |
In the Integration Module, if you create an FCL document to send through InternetLink and specify the notification channel of mailsend, when a fax is sent the notification continues to retry every 5 seconds. |
In this update, the error does not occur. |
|
11216 |
Rescue.exe |
The database rescue utility always retains deleted faxes regardless of option setting. |
In this update, the option to purge deleted faxes in the database rescue utility works as expected. |
|
2088 |
RightFax server |
No notification is being returned to a fax sender when a fax is abandoned due to a "scheduling failed" error for a fax number that is disallowed by dialing rules. |
In this update, the fax sender now receives notification when outgoing faxes fail to send due to the fax number being disallowed by a dialing rule. |
|
6185 |
RightFax server |
If the Disallow Editing of Billing Codes permission is set for a user, and Billinfo1 is a required field for sending faxes, the Billinfo1 information is not populated when using the print-to-fax function. |
In this update, the Billinfo1 information is populated as expected. |
|
9419 |
RightFax server |
When an outbound fax is sent with a delay time specified, and is then released prior to the specified time, the fax is immediately sent and then sent again at the specified delay time. |
In this update, the fax is sent only when released. The delay time is cancelled. |
|
9676 |
RightFax server |
The custom RTI line variable ~4 (the name of the receiving fax server) does not display on the RTI line. |
In this update, the variable ~4 displays on the RTI line as expected. |
|
10635 |
RightFax server |
The print-to-fax function fails when specifying a RightFax user ID if NT login does not match an existing RightFax user account. |
In this update, the print-to-fax function works as expected when specifying a valid RightFax user ID regardless of NT account login. |
|
10698 |
RightFax server |
Faxes get "Info Incomplete" error when multiple contacts are chosen from the RightFax phonebook and billing codes are required fields. |
In this update, faxes to multiple contacts send as expected . |
|
11436 |
RightFax server |
Setting the User Notify Time option is the Server configuration to a number less than 6 disables user notification. |
In this update, the User Notify Time option cannot be set to a number less than 6. Enter a value of 1-5 will automatically reset the User Notify Time option to 9999. |
|
31048 |
RightFax server |
Using the Human Answered Fax feature, if the call recipient selects [9] to cancel the fax, an incorrect notification is returned to the fax sender. |
In this update, cancelled faxes generate accurate notifications to the fax sender. |
|
31082 |
RightFax server |
Delayed faxes are sent immediately after stopping and restarting the Server Module. |
In this update, stopping and restarting the RightFax Server module does not immediately send delayed faxes. Delayed faxes are sent at the time specified. |
|
31664 |
RightFax server |
If a fax is sent immediately after stopping and restarting the BoardServer Module, the server will repeatedly schedule the fax to send but never send it. |
In this update, stopping and restarting the BoardServer Module does not prevent faxes from sending. |
|
31869 |
RightFax server |
Fax Reporter incorrectly reports the send date and time for delayed faxes. |
In this update, Fax Reporter reports the send time and date correctly for delayed faxes. |
|
32269 |
RightFax server |
CSID information in the CSID.tbl routing table assumes the * wildcard at the end of the CSID, allowing for incorrect or unexpected CSID routing. |
In this update, if no wildcard is present in the CSID routing table, an exact match must be made in order to route to the specified mailbox. Wildcard characters are still supported. |
|
32807 |
RightFax server |
Configuring the notification settings so that the User Notify Time and the Admin Once Only options are not selected results in thousands of notifications to be sent to the Group Administrator. |
In this update, the notifications occur only as configured. |
|
8858 |
SAP |
Auto-printing does not work for faxes sent via the Gateway for SAP R/3. |
In this update, faxes sent via the Gateway for SAP R/3 will auto-print as expected. |
|
11872 |
SAP |
When ten or more SAP gateways are present, sapgate.exe attempts incorrect connection due to incorrect file naming scheme in saprfc.ini. |
In this update, sapgate.exe successfully connects regardless of the number of SAP gateways. |
|
31097 |
SAP |
The RightFax 8.5 Connector for SAP R/3 Guide provides incomplete instructions on how to test the connection between SAP and the RightFax server after installation and configuration. |
The documentation should instruct you to clear the Trace check box before selecting the Test Connection option. If the Trace check box is selected, the SAP connector will fail. |
|
31393 |
SAP |
The RFSAP_FROMGENFAXNUM, RFSAP_FROMGENPHONE, and RFSAP_FROMFAXNUM embedded codes are not recognized. |
In this update, the RFSAP_FROMGENFAXNUM, RFSAP_FROMGENPHONE, and RFSAP_FROMFAXNUM function as expected. |
|
30623 |
SecureDocs/ |
After being bumped for SecureDocs, the Create PDF Image option is unavailable when sending to an e-mail address. |
In this update, bumping the SecureDocs module does not disable the Create PDF Image option. |
|
32555 |
SecureDocs/ |
Carriage returns and line feeds in the altmime.txt file for SecureDocs do not appear in the e-mail notification. |
In this update, carriage returns and line feeds in the altmime.txt file for SecureDocs appear in the e-mail notification as expected. |
|
30896 |
SMTP Integration |
The SMTP gateway drops diacritical characters in the From Name field. |
In this update, diacritical characters are retained in the From Name field. |
|
30904 |
SMTP Integration |
SMTP gateway notifications display incorrectly if From Name or Subject fields contain diacritical characters. |
In this update, SMTP gateway notifications display correctly. |
|
31167 |
SMTP Integration |
If the To Name or From Name fields contain diacritical characters, the SMTP gateway displays the names incorrectly. |
In this update, diacritical characters appear as expected. |
|
30470 |
Utilities |
Selecting the Auto-Delete Control option in the Fax Dialog Customization tab of the Group Edit dialog box does not disable the Automatic Deletion field on the Sending tab of the Options dialog box in FaxUtil. |
In this update, selecting the Auto-Delete Control option in the Fax Dialog Customization tab of the Group Edit dialog box does disable the Automatic Deletion field in FaxUtil. |
|
32530 |
Utilities |
Impuser.exe fails to import e-mail address from last entry in file unless the last entry is followed by a carriage return. |
In this update, the last item is imported from the Impuser.exe file without requiring a subsequent carriage return. |
|
9160 |
WorkServer |
An Excel spreadsheet with data only in the cell A1 is not faxed. |
In this update, an Excel spreadsheet with data only in cell A1 is faxed successfully. |
|
9803 |
WorkServer |
If an HPFAX print driver is not installed on the RightFax server, the event log fails to tell the administrator what the problem is. |
In this update, an error message is logged in the event log if an HPFAX print driver is not installed on the RightFax server. |
|
11088 |
WorkServer |
If special characters or symbols are used in a service account password, the WorkServer logon fails. |
In this update, special characters or symbols can be used in a service account password. |
|
11154 |
WorkServer |
Normal resolution landscape PDF files that are sent as attachments are distorted. |
In this update, normal resolution landscape PDF images are not distorted. |
|
11556 |
WorkServer |
Faxes fail that are created with overlay forms that call other forms (for example, a letterhead is the first page overlay, and a different overlay form that should follow for subsequent pages.) The WorkServer module reports the error "DPC:Error (2) in overlay of fax 0x20002C9." |
In this update, the error does not occur. |
|
11737 |
WorkServer |
Pages that contain embedded images in Excel spreadsheets are dropped from the fax when sent as an attachment from FaxUtil. |
In this update, pages in Excel spreadsheets that contain embedded images are not dropped from the fax. |
|
11950 |
WorkServer |
If a fax is received with a corrupt image or if the image is not written to the image directory and the user is set to auto-print using a Windows GDI printer, an application error occurs in the WorkServer module. The following error message appears: "The instruction at '0x1021ecb1' referenced memory at '0x00000014'. The memory could not be 'read'." |
In this update, the error does not occur. |
|
12205 |
WorkServer |
The file RFcomapi.dll in RightFax 8.0 Server Hot Fix 2 (dated 1/29/02) is an evaluation version and expires after 90 days. The following message appears in the WorkServer module configuration program: "The evaluation version of this software will expire in XX day(s). Please update the RFCOMAPI.DLL." |
In this update, the software license does not expire. |
|
12323 |
WorkServer |
When archive is enabled in the WorkServer Module and faxes are sent using embedded codes via the Hpfax print queue, the archive image file is overwritten. Unique files for each fax are not created. |
In this update, archive image files are correctly named and are not overwritten. |
|
30087 |
WorkServer |
Some .PCL files attached in FaxUtil or submitted via Java or the Integration Module convert to fax format with extra space at the top of the page. |
In this update, .PCL file attachments convert correctly. |
|
30530 |
WorkServer |
When a printer is defined in the RightFax server that uses a Xerox printer driver and a fax is printed, a memory exception error occurs. |
In this update, the error does not occur. |
|
30711 |
WorkServer |
PDF files with document security fail to convert. |
In this update, PDF files with document security are correctly converted. |
|
30976 |
WorkServer |
The WorkServer fails to create TIFF G4 files for certain received faxes when routing to network directory. |
In this update, routing to a network directory using the TIFF G4 format works as expected. |
|
31411 |
WorkServer |
With the Integration Module, InternetLink documents that contain the {{ImageType pdf}} FCL command and PCL codes do not convert. |
In this update, InternetLink documents that contain the {{ImageType pdf}} FCL command and PCL codes are correctly converted to fax images. |
|
31838 |
WorkServer |
The WorkServer module is unable to convert PCL files. |
In this update, the WorkServer converts PCL files. |
|
31920 |
WorkServer |
Faxes cannot be sent from the Xerox Document Centre 555. |
In this update, the Xerox integration has been enhanced. See (instructions for installing the Xerox integration) elsewhere in this document. |
|
32115 |
WorkServer |
In Web Client, when a Word document is attached to a fax, the client application creates .up.doc files in the Outgoing directory on the RightFax server, and the files are never deleted. |
In this update, up.doc files are properly deleted when a fax is sent. |
|
32412 |
WorkServer |
Text file fax attachments are truncated after the 80th character. |
In this update, text file attachments automatically word-wrap to fit all text on the resulting fax image. |
|
32768 |
WorkServer |
Documents that are printed to the fax printer (using print-to-fax) cause jobs to fail in the WorkServer module. |
In this update, documents that are printed to the fax printer do not cause jobs to fail in the WorkServer. |
|
30530 |
Xerox |
When printing to a RightFax printer using a Xerox print driver, a memory exception error occurs. |
In this update, the error does not occur. |
|
30531 |
Xerox |
When faxing to an international telephone number from a Xerox Document Centre, the RightFax server strips the first six digits of the number. |
In this update, the Xerox integration has been enhanced. For more information, see Updating the RightFax Integration with Xerox Multifunction Products. |
|
31130 |
Xerox |
Faxes sent from the Xerox Document Centre 545 do not convert. |
In this update, the Xerox integration has been enhanced. For more information, see Updating the RightFax Integration with Xerox Multifunction Products. |
The additions
and corrections listed here apply only to the RightFax 8.5 version of
the documentation.
Gateway for Microsoft Exchange Guide
|
Chapter |
3, "Configuring the WorkServers" |
||
|
Section |
"To add a remote WorkServer" |
||
|
Page |
65 |
||
|
Error |
The instructions for configuring a remote WorkServer are incomplete. |
||
|
Resolution |
The remote WorkServer must have an HP LaserJet 4 printer driver installed so that the print queues needed can be automatically set up. In addition, you must complete the following steps: Copy Files to the Remote WorkServer Computer
Edit the Lasernt.cfg File
|
||
|
Chapter |
3, "Configuring the WorkServers" |
||
|
Section |
"Select service account" |
||
|
Page |
45 |
||
|
Error |
Warning omitted. |
||
|
Resolution |
If you manually type a name in the Domain or Workgroup field that is longer than 15 characters, you may encounter errors in services performed by the WorkServer. To avoid this, you should select the user by clicking the Load Users button when the desired user account resides on a domain whose name is longer than 15 characters. |
||
|
Chapter |
4, "Configuring the BoardServer" |
||
|
Section |
"Audit settings" |
||
|
Page |
73 |
||
|
Error |
The description of audit level 4 is incorrect. |
||
|
Resolution |
If you set the audit level to 4, a new file is created each hour containing that hour's fax events. Because a separate file is created for each hour's fax events, do not specify a file name in the File box. You can optionally specify a path to a folder where the log files, which are given default names, will be saved. |
||
|
Chapter |
4, "Configuring the BoardServer" |
||
|
Section |
"Dialing settings" |
||
|
Page |
77 |
||
|
Error |
The definition for Prefix incorrectly states that if no value is specified, RightFax automatically sets the Prefix to "W". |
||
|
Resolution |
If the Prefix option is left blank, RightFax will not assign any default value. |
||
|
Chapter |
4, "Configuring the BoardServer" |
||
|
Section |
"Inbound routing" |
||
|
Page |
85 |
||
|
Error |
The definition for Initial Speech incorrectly notes that a license for a separate voice module must be acquired from Brooktrout. |
||
|
Resolution |
No separate voice module license is required. |
||
|
Chapter |
6, "Installing the RightFax Client Applications" |
||
|
Section |
"System Requirements" |
||
|
Page |
117 |
||
|
Error |
Windows ME is not listed as a supported operating system for the RightFax client applications. |
||
|
Resolution |
The RightFax client applications can be installed on Windows ME computers. The minimum system requirements are the same as for the operating system. |
||
|
Chapter |
18, "Generating Reports of Fax Activity" |
||
|
Section |
"Running Fax Reporter from a command line" |
||
|
Page |
255 |
||
|
Error |
The definition of the -r option is incorrect. |
||
|
Resolution |
The -r option is the report file name. The file should be located in the folder \RightFax\AdmUtils\Faxrpt2\Reports. |
||
|
Chapter |
19, "Routing Inbound Faxes" |
||
|
Section |
"Channel Routing" |
||
|
Page |
264 |
||
|
Error |
The statement "CSID routing is not available for analog fax boards." is incorrect. |
||
|
Resolution |
CSID routing can be used with analog fax boards. |
||
|
Chapter |
20, Responding to Inbound Faxes with AutoReply" |
||
|
Section |
"Before You Begin" |
||
|
Page |
275 |
||
|
Error |
An additional step is required for the AutoReply installation to work as expected.. |
||
|
Resolution |
If the user does not have any RightFax client applications installed:
If the user already has any RightFax client applications installed:
|
||
|
Chapter |
24, "Using RightFax E-mail Gateways" |
||
|
Section |
N/A |
||
|
Page |
N/A |
||
|
Error |
Guide fails to document that UTF-8 encoding (unicode) is required for the Euro symbol (¬) and some other special characters to appear properly in RightFax documents created in e-mail clients. |
||
|
Resolution |
To support documents with the Euro symbol, your e-mail client must be configured for UTF-8 (unicode) encoding. Refer to the documentation for your e-mail client for information on enabling UTF-8 encoding. |
||
|
Chapter |
24, "Using RightFax E-mail Gateways" |
||
|
Section |
N/A |
||
|
Page |
N/A |
||
|
Error |
Guide fails to document that UTF-8 encoding (unicode) is required for the Euro symbol (¬) and some other special characters to appear properly in RightFax documents created in e-mail clients. |
||
|
Resolution |
To support documents with the Euro symbol, your e-mail client must be configured for UTF-8 (unicode) encoding. Refer to the documentation for your e-mail client for information on enabling UTF-8 encoding. |
||
|
Chapter |
24, "Using RightFax E-mail Gateways" |
||
|
Section |
"Using RightFax E-mail Gateways" |
||
|
Page |
329 |
||
|
Error |
Guide fails to document that required information for outbound faxes does not apply to faxes sent via the e-mail gateways. |
||
|
Resolution |
Added important note stating that required information for outbound faxes does not apply to faxes sent via the e-mail gateways. If you have configured RightFax to require that the To Name field be completed before a fax can be sent, faxes may still be transmitted via the e-mail gateways without a recipient name specified. |
||
|
Chapter |
25, "Backing Up and Maintaining RightFax" |
||
|
Section |
"Running ImpUser.exe" |
||
|
Page |
377 |
||
|
Error |
Two command line options are omitted from the list of options in Table 25L. |
||
|
Resolution |
-uUserID: This is a required parameter that specifies the RightFax user ID to use to log on to the RightFax server specified with the -f parameter. -pPassword: This specifies the password for the user ID specified with the u parameter. Omit this parameter to use NT authentication. |
||
|
Chapter |
25, "Backing Up and Maintaining RightFax" |
||
|
Section |
"Running PhnPrint.exe" |
||
|
Page |
381 |
||
|
Error |
Two command line options are omitted from the list of options in Table 25N. |
||
|
Resolution |
-gOption: Optionally print phonebook groups from the specified users phonebooks. Specify option 0 or 1 where: 0 = Include phonebook groups 1 = Do not include phonebook groups (default) -q: Lists the field definitions for all of the output formats. This option overrides all other options. |
||
|
Chapter |
1, "Installing and Configuring Docs-on-Demand" |
||
|
Section |
"Configuring Fax-on-Demand" |
||
|
Page |
6 |
||
|
Error |
The definition for Routing Code/Channel Ext. incorrectly states that "If you have only analog channels you must dedicate one of your fax channels to Fax-on-Demand." |
||
|
Resolution |
You must dedicate one of your fax channels to Fax-on-Demand only if you have channel routing configured on POTS (plain-old-telephone system). |
||
|
Chapter |
3, "Customizing Fax-on-Demand" |
||
|
Section |
"Automatically Sending a Fax With One-Document Poll" |
||
|
Page |
50 |
||
|
Error |
The definition for the keyword ODP_InitialPrompt is incorrect. |
||
|
Resolution |
To specify a message file to play before the fax is sent, add this Fax-on-Demand registry keyword entry: ODP_InitialPrompt(file), where file is the name (without the file extension) of the message file to play. |
||
|
Appendix |
B, "Voice Prompt Files" |
||
|
Section |
N/A |
||
|
Page |
47 |
||
|
Error |
The keyword NumRetries is incorrect. The description of the 999.vox and 998.vox message files is incomplete. |
||
|
Resolution |
The correct keyword is Retries. The file 999.vox contains the message We will now send the documents you requested. If your fax machine is busy, we will retry three times to send you your documents. You may hang up now. By default, message file 999.vox plays to announce that a fax will be sent in the next call. You can define the number of retry attempts with the "Retries" keyword in the Fax-on-Demand Windows registry configuration, described in the RightFax 8.5 Docs-On-Demand Guide, Appendix C, Fax-on-Demand Registry Configuration. If you change the number of retries, you have the following message options:
|
||
|
Appendix |
C, "Fax-on-Demand Registry Configuration" |
||
|
Section |
N/A |
||
|
Page |
51 |
||
|
Error |
The description for the Retries registry setting is incomplete. |
||
|
Resolution |
The number of retries in this setting overrides the retry settings that are defined for the RightFax Server module. |
||
|
Chapter |
2, "Brooktrout Digital Fax Boards" |
||
|
Section |
"Supported Network Interface Cards" |
||
|
Page |
19 |
||
|
Error |
Brooktrout NetAccess ISA network interface cards is incorrectly listed with other supported cards. |
||
|
Resolution |
Brooktrout NetAccess ISA network interface cards are not supported. |
||
|
Chapter |
3, "Dialogic Digital Fax Boards" |
||
|
Section |
"Installing Dialogic Digital Fax Boards" |
||
|
Page |
27 |
||
|
Error |
The CPi/200BRI PCI and CPi/400BRI PCI fax boards are not included in the list of supported fax boards. |
||
|
Resolution |
The CPi/200BRI PCI and CPi/400BRI PCI fax boards are supported in RightFax 8.5. |
||
|
Chapter |
4, "Dialogic Digital Fax Boards" |
||
|
Section |
"Installing Dialogic Digital Fax Boards" |
||
|
Page |
27 |
||
|
Error |
The CPi/2400 and CPi/3000 fax boards are incorrectly described as ISA fax boards. |
||
|
Resolution |
The CPi/2400 and CPi/3000 fax boards are PCI fax boards. |
||
|
Chapter |
4, "Dialogic Digital Fax Boards" |
||
|
Section |
"Install the fax board hardware drivers" |
||
|
Page |
28 |
||
|
Error |
Steps 2 and 3 are incorrect. |
||
|
Resolution |
Delete steps 2 and 3 from this procedure. |
||
|
Chapter |
4, "Dialogic Digital Fax Boards" |
||
|
Section |
"Install the fax board firmware" |
||
|
Page |
29 |
||
|
Error |
In step 7, MuLaw coding is not required in Europe. |
||
|
Resolution |
If you are configuring fax board firmware in Europe, MuLaw coding is not required. |
||
|
Chapter |
3, "Installing the RightFax Connector for Microsoft Exchange 2000" |
||
|
Section |
"Installing the RightFax Connector on Microsoft Exchange 2000 Servers" |
||
|
Page |
24 |
||
|
Error |
A step is missing from the instructions for installing the RightFax connector |
||
|
Resolution |
After step 8, the Microsoft Exchange server must be restarted. Once the computer restarts, proceed to step 9. |
||
|
Chapter |
5, "Configuring Outlook Users to Send and Receive Faxes" |
||
|
Section |
"Installing the RightFax Forms for Outlook" |
||
|
Page |
38 |
||
|
Error |
A step is missing from the instructions for installing the forms to all Outlook client computers |
||
|
Resolution |
The following steps are required after completing step 1 in the guide:
|
||
|
Chapter |
5, "Configuring Outlook Users to Send and Receive Faxes" |
||
|
Section |
"Sending Faxes" |
||
|
Page |
41 |
||
|
Error |
Guide fails to document that UTF-8 encoding (unicode) is required for the Euro symbol (¬) and some other special characters to appear properly in RightFax documents created in the client for Microsoft Outlook. |
||
|
Resolution |
To support documents with the Euro symbol, Outlook must be configured for UTF-8 (unicode) encoding. Refer to the documentation for Microsoft Outlook for information on enabling UTF-8 encoding. |
||
|
Chapter |
5, "Configuring Outlook Users to Send and Receive Faxes" |
||
|
Section |
"Customizing the subject lines of Exchange user notifications" |
||
|
Page |
47 |
||
|
Error |
The definitions for the registry setting for ExchangeMsgs_0 are incorrect. |
||
|
Resolution |
The following table lists the correct definitions of the variables. ~1 = CSID of the originating fax machine. ~2 = Part of the fax (if the fax is broken into multiple parts). ~3 = Total fax parts (if the fax is broken into multiple parts). ~4 = The number of the fax channel that received the fax. ~5 = The unique ID of the fax, assigned by the RightFax server. ~6 = ANI information. |
||
|
Chapter |
1, "Hardware and Software Requirements" |
||
|
Section |
"Fax Server Requirements" |
||
|
Page |
11 |
||
|
Error |
The disk space requirement of about 150 MB for the RightFax software is incorrect and the minimum requirement for Microsoft Internet Explorer version 5.5 is incorrect. |
||
|
Resolution |
The disk space that is required for the RightFax software is about 610. The minimum requirement for Microsoft Internet Explorer is version 5.0. |
||
|
Chapter |
3, "Installing the RightFax Software" |
||
|
Section |
"Updating to RightFax Version 8.5 from a Previous Version" |
||
|
Page |
19 |
||
|
Error |
The first bullet point incorrectly instructs you to uninstall the RightFax Fax Board Drivers before upgrading to RightFax 8.5 from any previous version. |
||
|
Resolution |
The drivers you must uninstall are named RightFax Hardware Module and not RightFax Fax Board Drivers. Also, uninstalling these drivers is only required when upgrading from RightFax version 8.0. No uninstall is necessary when upgrading from any version prior to 8.0. |
||
|
Appendix |
A, "Installing RightFax in a Windows NT 4.0 or Windows 2000 Cluster" |
||
|
Section |
"Installing RightFax on the two cluster nodes" |
||
|
Page |
44 |
||
|
Error |
Steps 3 and 8 incorrectly state that after RightFax is installed on the primary node, clicking OK in the BoardServer configuration program starts the RightFax BoardServer service on the primary node. |
||
|
Resolution |
This action creates the BoardServer service, but does not start it. |
||
|
Chapter |
1, "Installing the SecureDocs Module" |
||
|
Section |
"Activating the Web Client Software on the RightFax Server" |
||
|
Page |
9 |
||
|
Error |
Reference to the Web Client application is incorrect. |
||
|
Resolution |
The reference to the Web Client application should refer to the SecureDocs Module. |
||
|
Chapter |
1, "Installing and Configuring the SNMP Alerting Module" |
||
|
Section |
"Configuring the Network Monitor Application" |
||
|
Page |
6 |
||
|
Error |
Instructions for running Rfhpov.bat are incomplete. |
||
|
Resolution |
On the Network Node Manager computer, you must first map a drive to the server where the SNMP Module is installed. Then, you can run the Rfhpov.bat file from a command line on the Network Node Manager computer. |
||
|
Appendix |
B, "FCL Commands" |
||
|
Section |
"PRINTNOW" |
||
|
Page |
277 |
||
|
Error |
The syntax for the {{PRINTNOW}} command is incorrect.. |
||
|
Resolution |
Use the following syntax for PRINTNOW: {{printnow print copies}} Where copies is the number of copies to print. |
||
|
Appendix |
B, "FCL Commands" |
||
|
Section |
"SETTAB" |
||
|
Page |
283 |
||
|
Error |
Documentation does not state the maximum number of tabs that can be set with {{settab}}. |
||
|
Resolution |
Up to 20 sets of tabs can be set, numbered from 0 to 19. |
||
|
Chapter |
1, "Creating FCL Documents with InternetLink Commands" |
||
|
Section |
"Example FCL for InternetLink documents that have attachments" |
||
|
Page |
8-10 |
||
|
Error |
The documentation incorrectly states that the {{uniqueid}} code specifies the file name of the attached PDF file. |
||
|
Resolution |
The name of the attached file is generated automatically by the system. The {{uniqueid}} code does not set the attached file's name. |
||
|
Chapter |
1, "Activating and Using the Teleconnect Module" |
||
|
Section |
"RightFax user setup" |
||
|
Page |
6 |
||
|
Error |
The documentation incorrectly states that the user's RightFax ID must be numeric. |
||
|
Resolution |
The RightFax user's ID may contain both letters and numbers. |
||
With the RightFax server and the Xerox family of multifunction products, users can scan and fax documents from a Xerox device, making it convenient to fax printed pages when no electronic version is available. Users also can scan documents and send them to his or her RightFax mailbox or to the mailbox of another RightFax user in the network.
The RightFax server supports the following models of the Xerox multifunction devices:
WorkCentre Pro 32/40
WorkCentre Pro 65/75/90
WorkCentre Pro 35/45/55
DCS 265
DCS 460
DCS 470
DCS 480
DCS 490
DC 425
DC 432
DC 440
DC 535
DC 545
DC 555
The Document Centre sends job files to a Xerox Fax Repository that resides on a network directory. Each Document Centre must be configured with a Fax Repository. The RightFax WorkServer module scans the Fax Repository periodically for jobs to process. Each job is a new fax. To define a Fax Repository, refer to the documentation provided by Xerox.
In order to integrate RightFax with the Xerox Document Centre, at least one WorkServer module must be configured to process documents from the Fax Repository. You can configure more than one WorkServer module to process documents.
Before you
configure the WorkServer module, determine how you want users to send
faxes from the Document Centre and the RightFax server. You have the following
options.
|
Sending Option |
Notes |
||
|
Send faxes
to an external number from the Document Centre, or |
If the user sends the document to his RightFax mailbox, he can add cover sheets, overlay forms, and use the other options available in the RightFax client application. The user has the option to add billing codes at the Document Centre. |
||
|
Only send faxes to RightFax mailboxes. |
The user must type his voice mail subscriber ID preceding the fax number. For example, 70295551212. The fax will appear in his mailbox in FaxUtil with his voice mail extension stripped from the fax number. In FaxUtil, the fax appears with the status Information Not Complete. The user can send the fax to the fax number and use the other features of FaxUtil, such as cover sheets and overlay forms. The user has the option to add billing codes at the Document Centre. |
||
|
Only send faxes to an external number from the Document Centre. |
The user has the option to add billing codes at the Document Centre. |
||
For Service Pack 4, the Xerox configuration options in the RightFax WorkServer module have been enhanced. After installing the updated software, you must launch the WorkServer control panel applet and edit the settings for the Xerox integration.
From the RightFax Server desktop, select Start > Control Panel to open the Windows Control Panel.
Double-click RightFax WorkServer. This opens the WorkServer Configuration dialog box.
Click Xerox Configuration under the selected WorkServer. The Xerox configuration options appear in the right pane.
Verify the settings by referring to the configuration instructions in the next section.
When finished, you must click OK in the WorkServer Configuration dialog box to save the settings.
In the WorkServer Configuration dialog box, click Xerox Configuration under the selected WorkServer. The Xerox configuration options appear in the right pane.
Select the check box Enable Xerox Document Centre Interface.
In
the Scan Directories box, you
must create a list of Fax Repository directories that the WorkServer module
will scan for documents. You can define up to 32 directories for each
WorkServer module. Click Add.
The Xerox Document Centre Repository
Configuration dialog box opens.

In the Directory box, type the path to the Xerox Fax Repository directory, and then click OK.
In
the Xerox Document Centres box,
you must create a list of the Document Centres that the WorkServer module
will support. You can define up to 32 Document Centres for each WorkServer
module. Click Add. The Xerox
Document Centre Configuration dialog box opens.

In
the Xerox Document Centre IP Address
box, enter the IP address of the Document Centre.
Note: Jobs in the Fax Repository are tied to a Document Centre
by the IP address. If a defined IP address is not found with a document,
the job will be deleted.
In the Default User ID box, enter the RightFax user ID that is the default for faxes that are sent from the Document Centre. The default is Walkup. If the user profile is not already defined on the RightFax server, it will be created for you. To further define this user, refer to the RightFax Administrators Guide, Chapter 8, Creating RightFax Users.
In the Default address name on cover sheet box, enter a generic recipient name that will appear on the cover sheet of faxes sent from the default user (defined in the previous step). The default is "To whom it may concern".
Under Routing Faxes to a User ID, select one of the following options.
|
If you want users to |
Select |
|
Notes |
||
|
Be able to send faxes only to RightFax mailboxes. |
Forced |
If the voicemail subscriber ID is not valid, the fax job will be deleted and no errors will be reported. To assure that faxes are not lost, select the check box Route Faxes with an Invalid Subscriber ID to the Default User ID. |
None. |
||
|
Be able to send faxes to external numbers at the Document Centre, or send faxes to RightFax mailboxes. |
Optional |
In the Routing Prefix box, enter a number that should precede the voice mail subscriber ID when users send faxes to a RightFax mailbox. For example, the user may enter 007029 to send a fax to his RightFax mailbox. 00 is the routing prefix and 7029 is the voice mail subscriber ID. |
If the user sends a fax to a RightFax mailbox and the routing prefix is not found or the voicemail subscriber ID is not valid, then the fax will be sent from the default user's mailbox (Walkup). |
||
|
Be able to send faxes only to external numbers at the Document Centre. |
Disabled |
|
None. |
||
If you selected Optional or Forced routing, then in the Voice Mail Subscriber ID Length box, enter the length of voice mail subscriber ID codes. The voice mail subscriber ID will be used for routing by the RightFax server. For more information on voice mail subscriber ID codes, refer to the RightFax Administrators Guide, Chapter 8, Creating RightFax Users.
Click OK to save the configuration and close the Xerox Document Centre Configuration dialog box.
Users send faxes from the Document Centre by typing in a fax number and then scanning one or more documents. To enter a fax number, the user has the following options:
Send to a RightFax mailbox.
Send to an external fax number.
Send to a recipient in the RightFax phonebook.
Include billing codes with the fax number.
Documents can be scanned and routed to a RightFax mailbox from the Document Centre. This feature is useful for previewing a fax before it is sent; for adding a cover sheet, overlay forms, and other options in the RightFax client applications; or for sending a fax to any RightFax user in your system.
If you have defined Optional routing for this Document Centre, enter the routing prefix followed by the voice mail subscriber ID. For example, enter 007029, where 00 is the routing prefix, and 7029 is the voice mail subscriber ID.
If you have defined Forced routing for this Document Centre, type your voice mail subscriber ID followed by the fax number. For example, 70295551212, where 7029 is your voice mail subscriber ID and 5551212 is the fax number. The fax will appear in FaxUtil with the voice mail subscriber ID stripped from the fax number. The fax appears with the status Information Not Complete. You can send the fax to the fax number and use the other features of FaxUtil, such as cover sheets. To send the fax from FaxUtil, on the Fax menu, click Status > Release.
If you have defined Optional or Disabled routing for the Document Centre, documents can be faxed to external fax numbers from the Document Centre. The faxes will be sent from the default user that is defined for the Document Centre. To enter the fax number at the Document Centre, enter the destination fax number.
From the Document Centre, a fax can be sent to a recipient in the RightFax phonebook. This is done by entering a backslash (\) and then the phonebook ID. The phonebook ID must be numeric, and the backslash is entered as a group dial character on the Document Centre user interface.
The sequence for entering the phonebook ID with the fax number string depends on the routing method.
If you are sending from a RightFax voice mail subscriber ID, the phonebook ID must immediately follow it. For example, 7029\5511, where 7029 is the voice mail subscriber ID and 5511 is the phonebook ID. With this method, the fax will include the recipient's address information from the users RightFax phonebook and information about the user from his or her RightFax user profile and user settings in FaxUtil, such as name and contact information.
If you are sending from the default user ID that is defined for the Document Centre, then the phonebook ID must be defined in the default users RightFax phonebook. The phonebook ID must be entered as the fax number string. For example, \4343, where 4343 is the phonebook ID. The default user is described earlier in this document.
To add billing codes, enter the billing codes with the fax number using this format:
FaxNum*BillingCode1*BillingCode2
where FaxNum is the destination fax number
string, BillingCode1 is the first
billing code, and BillingCode2
is the second billing code.