Peer Routing Rules configuration

Peer Routing Rules are prioritized lists of user-configured routing rules that define where to route a message to upstream Peer Nodes. Routing is based on message content matching a Peer Routing Rule's conditions. Peer Routing Rules are contained in Peer Route Tables.

Note:

When a Redirected Request is processed, if redirect PRT instance is not configured, the PRT instance used to Process the redirected Request is selected similar to an ingress request.

There are six Peer Routing Rule parameters:

• Destination-Realm
• Destination-Host
• Application-ID
• Command-Code
• Origin-Realm
• Origin-Host

When a Diameter message matches the conditions of a Peer Routing Rule then the action specified for the rule occurs. If you choose to route the Diameter message to a Peer Node, the message is sent to a Peer Node in the selected Route List based on the Route Group priority and Peer Node configured capacity settings. If you choose to Send an Answer, then the message is not routed and the specified Diameter Answer Code is returned to the sender.

Peer Routing Rules are assigned a priority in relation to other Peer Routing Rules. A message is handled based on the highest priority routing rule that it matches. The lower the number a Peer Routing Rule is assigned, the higher priority it has. (1 is the highest priority and 99 is the lowest priority.)

If a message does not match any of the Peer Routing Rules and the Destination-Host parameter contains a Fully Qualified Domain Name (FQDN) matching a Peer Node, then the message is directly routed to that Peer Node if it has an available Connection.

If there is not an available Connection or all routing attempts (per Peer Node configuration) to the implicit route are exhausted, the message is routed using the alternate implicit route configured for the Peer Node.

A Message Copy Configuration Set can be assigned to a Peer Routing Rule to provide information for sending a copy of the message to a DAS.

On the Viewing Rules for Peer Route Table: {Peer Route Table Name} page, you can perform the following actions:

• Filter the list of Rule Names to display only the desired Rules.

• Sort the list entries in ascending or descending order by column (except Conditions) by clicking the column heading.

  By default, the list is sorted by Priority in ascending ASCII order. The lowest Priority value indicates the highest priority. For Rules with the same Priority, the Rule Name is used for sorting.

• Select a blue Route List entry to open the Diameter > Configuration > Route Lists [Filtered] page for the selected entry.

• Click Insert.

  On the Inserting Rule for Peer Route Table: {Peer Route Table Name} page, you can add a new Peer Routing Rule and its values. See Adding a Peer Routing Rule.

  If the maximum number of Peer Routing Rules (10000) already exists for the Peer Route Table, the Inserting Rule for Peer Route Table: {Peer Route Table Name} page does not open and an error message displays.

• Select the Rule Name of a Peer Routing Rule in the list and click Edit.

  On the Editing Rule for Peer Route Table: {Peer Route Table Name} page, you can edit the selected Peer Routing Rule. See Editing a Peer Routing Rule.

  If the selected Peer Routing Rule has been deleted by another user, the Editing Rule for Peer Route Table: {Peer Route Table Name} page does not open.

• Select the Rule Name of a Peer Routing Rule in the list and click Delete to remove the selected Peer Routing Rule. See Deleting a Peer Route Rule.