A Routing Option Set is a collection of Routing Options that are used when a Request message is received. This functionality controls the number of times an application forwards the request message and the processing error delivery situations.
You can perform these tasks on an Active System OAM (SOAM).
A Routing Option Set can be associated with the Peer Node that the Request is received from, or with the Diameter Application ID contained in the Request message header. If Routing Option Sets are associated with both the Peer Node and the Application ID, the one associated with the Peer Node takes precedence. If neither the Peer Node nor the Application ID have an associated Routing Option Set, then the Default Routing Option Set is used.
Users can assign Routing Option Set (ROS) to Diameter messages based on Application ID and (Extended) Command Codes by configuring Transaction Configuration Rule (TCR) with Application ID plus (E)CC as a key in Transaction Configuration Sets.
On the
page, you can add a new Routing Option Set.The
page does not open if the maximum number of Routing Option Sets (50) already exists in the systemOn the
page, you can edit the selected Routing Option Set.If the selected Routing Option Set has been deleted by another user, the
page does not open.