XMediusFAX Overview

Outbound Faxing

XMediusFAX processes outbound faxes submitted by back-end applications, e-mail systems, networked multi-function devices and desktop applications.  Faxes can be submitted to XMediusFAX a myriad of ways including print driver, SMTP mail, XML file drop and Web Services API.

Inbound Faxing

Inbound faxes can be delivered via e-mail to one or more recipients, pushed into downstream business and workflow applications, printed on a network printer or MFD device, archived to a network share or any combination of these tasks.  




Once again the architecture of XMediusFAX provides tremendous flexibility in defining outbound and inbound fax workflows.  For example:

• A business or clinical application could generate an outbound fax and pass important information about the fax recipient such as customer or patient number, invoice or transaction number, etc.  to XMediusFAX.  When XMediusFAX completes the fax transmission it can write a TIF or PDF file of the fax along with an XML metadata file that contains the important recipient information to a network share.  A back-end workflow or document management application can pick up the image file and use the metadata to index the fax image.

• You may have XMediusFAX configured to print inbound faxes received at a specific internal fax number to a network printer.  However if the CSID (Caller Subscriber Identification) of the company that sent the fax is one of your major customers, a copy of the fax can also be e-mailed to the Account Manager responsible for the customer.

• Finally, you may contract with an outside firm to handle after-hours transactions such as customer service calls, etc.  XMediusFAX can be configured with a simple Python script so that faxes received between the hours of 5:00 PM and 8:00 am are redirected to the outside firm for immediate handling.  Faxes received between 8:00 am and 5:00 PM are automatically delivered by XMediusFAX to the appropriate internal staff.