In this section:

The Result Table may identify either  a candidate destination for a message based on the loadshare algorithm or it may identify a server pool for the continuation of routing.

Result records are cost-based and the table’s lowest available record is chosen to route the message. If more than one record has the lowest available cost, the result is load shared.

Note

Relay, redirect result records and realm redirect records cannot share the same cost.

Any record of higher cost than the initial redirect result record is ignored for routing.

To create a Result Table

Click to read more... 

To view a Result Table

Click to read more... 

To create a Result Record

Click to read more... 

To configure a Result Record

Click to read more...