Peer Routing Rule configuration elements

Table 1 describes the fields on the Peer Routing Rules View, Insert, and Edit pages. Data Input Notes only apply to the Insert and Edit pages; the View page is read-only.

Peer Routing Rules Configuration Elements
Field (* indicates required field)	Description	Data Input Notes
* Rule Name	Unique name of the Peer Routing Rule.	Format: case-sensitive; alphanumeric and underscore (_); cannot start with a digit and must contain at least one alpha Range: 1 - 32 characters
* Priority	Priority of the Rule in relation to other Rules. The priority is set from 1 (highest priority) to 99 (lowest priority).	Format: text box; numeric Range: 1 - 99
* Conditions	In order for a Diameter message to be matched by a Rule, the message must match each specified part of a condition. Each condition has three parts: Parameter Operator Value
	Parameter: Destination-Realm Destination-Host Application-Id Command-Code Origin-Realm Origin-Host	Format: Operator and Value for each Parameter
	Operator Sets the relationship between the parameter and the value. For example, if the operator is set to Equals then the Diameter message parameter must match the set value.	Format: Pulldown list Range: See Peer Routing Rule operators for a description of operators available for each parameter.
	Value The value in the Diameter message the Peer Routing Rule uses to determine a match. A Value is required if the Operator is "Equals", "Starts With", or "Ends With".	Format: text box or pulldown list Range: Application-ID: available configured Application Ids Command-Code: available configured Command Codes Destination-Realm and Origin-Realm: Realm is a case-insensitive string consisting of a list of labels separated by dots. A label may contain letters, digits, dashes (-), and underscore (_). A label must begin with a letter or underscore and must end with a letter or digit. An underscore can be used only as the first character. A label can be at most 63 characters long and a realm can be at most 255 characters long. You can specify a substring or a complete string of a valid Realm. Destination-Host and Origin-Host: FQDN is a case-insensitive string consisting of a list of labels separated by dots. A label may contain letters, digits, dashes (-), and underscore (_). A label must begin with a letter or underscore and must end with a letter or digit. An underscore can be used only as the first character. A label can be at most 63 characters long and a realm can be at most 255 characters long. You can specify a substring or a complete string of a valid FQDN. Command-Code: pulldown list of configured Command Codes, including Extended Command-Code (ECC) immediately after their parent Command-Code Note: An ECC is a Command Code that also takes into account the value of a specific AVP for that Command Code that gives the "true" command type (for example, CCR-I, CCR-U, and so on).
Action	The action that will happen if the Diameter message matches the conditions set in the Peer Routing Rule: Route to Peer: routes a message to a Peer Node using the Route List associated with this Rule. Send Answer: send and answer response that contains the Diameter answer result-code, vendor Id, and error message associated with this Rule. Abandon With No Answer: abandon message routing without sending an Answer response to external peer. Note: The Answer is sent to any applications that requested an Answer receive.	Format: selection box Range: Route to Peer, Send Answer, Abandon With No Answer Default: Route to Peer
Route List	Route List associated with this Rule. A Route List is required if the Action is set to Route to Peer. The Route List entries on the View page are links to the Diameter > Configuration > Route Lists [Filtered] page for the selected entry.	Format: pulldown list Range: configured Route Lists Default: "-Select-"
Message Priority	The priority to assign to the message. The message priority is assigned only when Action is set to Route to Peer.	Format: pulldown list Range: No Change, 0, 1, 2. 0 is lowest priority Default: No Change
Message Copy Configuration Set	Message Copy Configuration Set (MCCS) used for copying the messages to the DAS. A valid MCCS will mark the messages matched by this Peer Route Rule for copy to the DAS.	Format: pulldown list Range: Default; configured Message Copy Configuration Sets Default: "-Select-"
Answer Result-Code Value	The answer code associated with this Rule. A Diameter answer code is required if the Action is set to Send Answer.	Format: radio button for pulldown list; radio button for text box Range: pulldown list: available Diameter answer codes text box: 1000 - 5999 Default: 3002 UNABLE_TO_DELIVER
Vendor Id	The Vendor Id to place in the Vendor Id AVP of the answer message.	Format: text box; numeric Range: 0 - 4294967295
Answer Error Message	Value returned in the Error-Message AVP of the answer message.	Format: text box; alphanumeric, underscore (_), period (.) Range: 0 - 64 characters Default: Null string
* Peer Route Table	The Peer Route Table to which the Peer Routing Rule belongs	View-only