Server-to-server routing routes faxes between two or more AccuRoute Servers thus reducing the cost of sending faxes long distance over phone lines.
Note: You must install a connector on each server that will route messages.
-
You can add an SSR connector for sending messages or receiving messages only or for both sending and receiving.
-
Before you create the routing rules, review the flow of traffic in your company before you create the routing rules to ensure that all routing situations are covered, and that each server has all of the rules required to route and receive messages via server-to-server routing.
-
For each SSR connector in a server, you must create outbound routing rules.
Outbound routing rules are necessary on all servers that will route messages to other SSR connectors. For each routing rule, use the Destination routing condition to specify all area codes you want routed to a particular server. When you add multiple area codes to the Destination condition for a single rule, they become an OR statement; a fax's destination fax number only has to match one of the area codes to match that rule
Server-to-Server routing example
The following example illustrates server-to-server routing and processing of fax message.
Note: In this example, AccuRoutefax is formerly known as Genifax.
-
A user in Boston sends a fax.
-
The fax goes from the user's desktop to the AccuRoute Server in Boston (AccuRoutefaxBoston). The fax is intended to go to a recipient in Los Angeles whose fax number matches an SSR outbound routing rule on AccuRoutefaxBoston.
-
AccuRoutefaxBoston routes the fax to its SSR connector, which connects to the SSR connector on the AccuRoutefaxLA AccuRoute Server, as specified in the routing rule.
Note: If the connection fails, AccuRoutefaxBoston fails the fax and notifies the sender. If the connection is successful, the fax is routed to the SSR connector on AccuRouteLA.
-
When AccuRoutefaxLA receives the entire message, it notifies AccuRoutefaxBoston that it has successfully received the message.
-
On AccuRoutefaxBoston, the record of the message in the In Process folder moves to the Deliver Pending state. It begins to track the length of time the message spends in this state (for the configured message timeout value). If the configured message timeout value is reached, AccuRoutefaxBoston fails the message and moves it to the History folder on AccuRoutefaxBoston.
-
The SSR connector on AccuRoutefaxLA submits the fax to AccuRoutefaxLA for processing. AccuRoutefaxLA processes it and sends it out according to the routing rules on that server.
-
AccuRoutefaxLA sends AccuRouteFax a notification of the final status (success or failure) of the fax.
-
If the message timeout period is not reached, AccuRoutefaxBoston moves the fax to the History folder with the appropriate final status (Successful or Failed).
-
If the message is delivered after the timeout period is reached, AccuRoutefaxBoston shows the message delivery status as failure while AccuRoutefaxLA shows the message delivery status as successful.
-