| Description | string | SAActionInRule aggregates SAActions into SARules In SAActionInRule, the combination of the ActionOrder value and the FallbackOrder value MUST be unique so as to specify a deterministic execution strategy. An ActionOrder value specifies a set of actions to be attempted and the order in which to attempt the set with respect to other ActionOrder sets. The FallbackOrder specifies the order in which to attempt the actions within the set.
For example, {ActionOrder=1,FallbackOrder=1} is the backup action for {ActionOrder=1,FallbackOrder=0} and {ActionOrder=2,FallbackOrder=1} is the backup action for {ActionOrder=2,FallbackOrder=0}. In this example, {1,0} will be attempted and, if it fails or is otherwise inappropriate, {1,1} is then attempted. Regardless of which of these, if any, succeeds, {2,0} is then attempted, and so on.
In an initiator role, if there is more than one action in the rule, the ActionOrder identified sets are executed as described above using the FallbackOrder to determin ethe order in which to attempt actions within a set, i.e., the additional actions with the same ActionOrder value are 'backup' actions in the event that the first action is not able to be completed successfully. Within each ActionOrder identified set. they are tried in the FallbackOrder until the list is exhausted or one completes successfully.
In a responder role, it is an error to have more than one ActionOrder set in the rule however, there may be more than one action each identified by a unique FallbackOrder value. The additional actions provide alternative actions depending on the received proposals. For example, the same rule may be used to handle aggressive mode and main mode message flows with different actions. The first appropriate action in the list of actions is used by the responder. | None | TRANSLATABLE= true |