Advanced Features of facsBridge™ T37FSP - Windows Desktop Fax Driver
The table below contains a summary of T37FSP configuration settings for Cisco fax-enabled routers
|Gateway||Faxmail Outbound Gateway||The T.37 fax gateway that will be appended to the destination fax number to compose a destination faxmail address in the format fax_number@fax_gateway.|
|Gateway||Prefix for Destination Email Address||Defaults to FAX=|
|Gateway||This is Cisco gateway||On|
|Miscellaneous||Use Different SMTP for inbound routing||Set to On when using real-time outbound faxing with Workstation version and when Forward Inbound faxes is On.|
Note. If you do not have a dedicated offramp fax port (it is shared with voice calls or onramp fax) MS Fax needs to be configured for retries. By default it is configured for 3 retries.
See Sample Cisco Configuration Script for onramp/offramp T.37 faxing.
facsBridge™ SMTP Server is designed to receive faxmail from Cisco T.37 gateway. If Receive is enabled, T37FSP0 device (channel) is always enabled for receive. In Enterprise version where multiple channels are supported T37FSP0 channel is not enabled for send. Please be aware that facsBridge™ SMTP Server will also receive all Delivery Status Notifications (DSN) generated by Cisco outbound gateway. As outbound transmission is syncronised, those DSN messages are not essential. However, in rare cases they might assist in troubleshooting. DSN mail is saved into a temporary directory. Please check Application Event Log for the name of this directory. Please ensure to configure firewall to allow appropriate source (Cisco) IP addresses to connect to the facsBridge SMTP Server.
Fax Console displays inbound faxes in the Inbox, where Routing Information field displays called number, as specified in the subject field of the fax-mail in the format DNIS=#### by Cisco ISR, Caller ID field displays calling party number as specified in the subject field of the fax-mail in the format ANI=####.
In Windows XP, select Forward inbound faxes to Master Email Address check box to forward inbound fax-mail to the Master Email Address. In Windows Server, proceed with f2eRouter Configuration below. T37FSP must be activated in order to use this feature after the evaluation period expires.
Unless Only Master Email is used for outbound faxing check-box is selected, T37FSP will attempt to obtain an individual email addresses for each outbound fax. If individual email address is not available, the Master's Email Address will be used. To use the individual email addresses your T.37 gateway must be sensitive to the From field in the email header (derived from the individual email addresses, as opposite to the Sender field derived from the SMTP Account Name and Password, presumably linked to the Master Email Address). If gateway is sensitive to the From field then it will send notifications to the individual email addresses, not to the Master's Email Address.
To specify individual email address in Windows 2003, each user should navigate to Start - Programs - Accessories - Communication Tools - Fax - Fax Console - Tools - Sender Information and fill in the E-mail field.
Due to enhanced security in Windows 2008 and above this approach does not work, T37FSP will not be able to extract the email address linked to the Sender Information from the outbound fax job. Proceed with facsBridge.xml below, and fill in facsBridge.xml as appropriate.
There is a supplementary T37FSPSuppDetails service to facilitate T37FSP in Windows Server 2003 and above. For Windows Server 2003, navigate to Control Panel - Administrative Tools - Services - T37FSPSuppDetails, in T37FSPSuppDetails properties select Log On tab and fill in "This account" as the Administrator's account. In Windows Server 2008 and above, the default (Local System) account will do.
Consider Microsoft page on Fax Server as a useful resource.
Make sure the Fax Printer is shared, otherwise domain users will not be able to print on the shared fax printer and use the Fax Service (and T37FSP) that runs on the server computer.
To configure inbound fax routing, proceed with f2eRouter Configuration below.
In Windows Server, facsBridge T37FSP extracts an email address from the sender name if Only Master Email Address check box on the Gateway page of the Configuration Application is off. The SenderName in the XML file must match to the Full Name field from the Sender Information as seen in the Fax Console (Windows Fax and Scan). It could be different to the name from the Active Directory.
The facsBridge.xml file must be located in 'C:\Program Files(x86)\Sandler Consulting Pty Ltd\facsBridge T37FSP\' on x64 Windows or in 'Program Files\Sandler Consulting Pty Ltd\facsBridge T37FSP\' on x32 Windows; make sure the Network Service account has at least read access to this directory.
The xml file must be compliant with facsBridge XML schema, facsBridge.xsd.
MSXML 4.0 Service Pack 2 or MSXML 6.0 (Microsoft XML Core Services) is required for T37FSP and/or facsBridge4Exchange to parse facsBridge.xml file. MSXML 6.0 is installed with Windows Server 2008 or above. MSXML 4.0 can be downloaded from Microsoft.
After installation, rename or copy facsBridgeSample.xml as facsBridge.xml and modify it as appropriate.
The facsBridge.xml and the schema facsBridge.xsd are similar to f2eRouter.xml and f2eRouterSchema.xsd. Generate XML button from f2eRouter tab of Configuration Application can be used to generate the XML file from the Active Directory; facsBridge.xml can be based on this file.
Run the script ValidateFacsBridgeXML.js installed in the same directory to validate the facsBridge.xml file after modifying it. If ValidateFacsBridgeXML.js produces the error Automation Server can't create object, MSXML 4.0/MSXML 6.0 is not installed on your computer.
An application that produces a form and adds an entry into facsBridge.xml for the current user is available on request.
The f2eRouter inbound routing extension is designed for Windows Server 2003 or above and integrates with the Windows Fax Service. It forwards received faxes to an appropriate email address based on called fax number (available from Direct Inward Dialing DID or ISDN PRI).
f2eRouter is not limited to route inbound faxes received by the T37FSP fax device. Any fax device that reports called number as Routing Information can take advantage of f2eRouter routing (e.g. T.38 device, Brooktrout FSP for Dialogic Brooktrout TR1034 / TruFax boards or SR140 virtual module). Use Fax Service Manager (Start->Programs->Accessories->Communications->Fax->Fax Service Manager) to associate fax devices with the inbound routing extension. In case of facsBridge T37FSP, only T37FSP0 device can be used for receiving faxes and should be associated with f2eRouter.
f2eRouter sends emails with the received TIFF file attached having the Master Email Address as the sender address. Hence all the routed fax-mail delivery status notifications will be sent to the Master Email Address.
Use f2eRouter TAB of the Configuration Application to control f2eRouter options. If DefaultRouting check box is on, all inbound faxes that are not associated with the CalledIDs specified in the XML table will be routed to the Master Email Address, otherwise they will not be routed. If PDF attachment check box is on, fax-mail will be generated with a PDF (as opposite to TIFF) attachment. A content class for the fax-mail can be specified.
If f2eRouter fails to send an email, an error message will be added to the Applications Events Log and the fax job will be pending in the Incoming folder of the Fax Console (with the status routing). Check the Applications Events Log and the Incoming folder of the Fax Console periodically.
facsBridge™ product must be activated in order to use f2eRouter after the evaluation period expires.
The f2eRouter.xml file is designed to facilitate inbound routing (by extracting email address from the DID fax number).
The file contains the routing table. Each entry contains CalledID (called number), Email Address and Sender Name.
Configuration Application is integrated with the Active Directory by XML-generator (capable to generate f2eRouter.xml file automatically). The button to generate the file is available on the f2eRouter TAB of Configuration application.
The f2eRouter.xml file must be compliant with f2eRouter XML schema, f2eRouterschema.xsd. The button to validate the file is available on the f2eRouter TAB of the Configuration Application.
System Requirements for facsBridge™ f2eRouter are listed in f2eRouter documentation. Make sure the f2eRouter.XML file has at least read access for the Network Service account.
To install and configure f2eRouter as part of facsBridge4Exchange™ Connector refer to f2eRouter Installation section of facsBridge™ 4Exchange User Guide document.
To install and configure f2eRouter as a stand-alone product or as a part of facsBridge™ T37FSP Enterprise refer to f2eRouter documentation.