Incoming faxes are normally sent to a User's Inbound History folder and, by default, to their email inbox with the fax as an attachment. XMediusFAX Cloud offers several additional methods of delivering faxes to your premises that could respond to different integration needs.
- A Notification Destination, that will represent the mean to reach the targeted application/device (see Creating a Notification Destination).
- A Routing Rule, that will direct the fax to the proper notification destination according to specific criteria (see Routing a Fax to a Destination using the Incoming Routing Table).
XMediusFAX Cloud also offers a feature-rich Web Service (SOAP) interface so that a remote application can programatically poll the fax folders of specific users (see Polling faxes using the XMediusFAX Web Services).
Finally, the XMediusFAX Cloud Professional Services team can be contacted if you have specific integration needs that are not covered by the above methods (see Enabling Custom Fax Delivery Scenarios).
Creating a Notification Destination
- For email delivery (to email addresses that are not necessarily associated to users), you need to add a Mail notification destination.
- For delivery to a remote file system (e.g. FTP server), you need to add a Folder notification destination.
- For delivery to a printer, you need to add a Printer notification destination (see an example scenario: Automatically Printing Faxes on Printers).
Routing a Fax to a Destination using the Incoming Routing Table
The Incoming Routing Table can route incoming faxes to a variety of destinations by using routing rules (Fax Settings from your cloud faxing service portal navigation bar, then select Incoming Routing Table).
Here are described the typical rule types you may use to achieve your needs. For more information on how to configure these rules, refer to Incoming Routing Table in the online Administration Guide ().
Directories Lookup Rule
With a Direct rule, you can route some incoming faxes to a specific set of destinations. This routing depends on the destination(s) selected and the matching criteria defined in the rule.
The matching criteria are used to narrow the routing based on called numbers (Match DNIS/DID) and caller numbers (Match ANI). These matching criteria can use wildcards, so that you can easily meet your business requirements of routing all faxes (*) to a remote folder or printing to a specific remote printer all faxes sent to a specific number.
By checking or unchecking the If this routing entry matches, continue processing the routing table box in any rule, you can fully control how the logic of routing faxes is executed.
It is possible to add a Default rule to the Incoming RoutingTable. It is always at the bottom of the list and cannot be moved, as it must close the routing table process. If none of the Incoming Routing Table rules selects a destination, the incoming fax will be automatically routed to the destination(s) specified in this rule.
Polling faxes using the XMediusFAX Web Services
XMediusFAX Cloud offers a programmatic Web Services (SOAP) interface to its fax queues. It can be used to retrieve faxes from 3rd party applications with a SOAP request. Such requests could be invoked through the most popular programming languages (Python, Ruby, C++, Java, .NET, ...) or even using command line applications such as cURL.
Enabling Custom Fax Delivery Scenarios
If your business process includes special fax routing requirements, the XMediusFAX Cloud Professional Services team can be contacted to develop a solution that meet your needs.
The provided solutions may include Python scripts in Notification Destinations or in Routing Rules; however these scripts cannot be modified by yourself (only by the Professional Services team).