Go to primary content
Diameter Signaling Router Policy and Charging Application
Release 8.2
E89000
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Suspect Binding Removal Rules elements

Table 6-25 describes the elements on the Policy and Charging > Configuration > Policy DRA > Suspect Binding Removal Rules page on the SO GUI.

Table 6-25 Suspect Binding Removal Rules Elements

Field (* indicates a required field) Description Data Input Notes
* Rule Name A name that uniquely identifies the Suspect Binding Removal Rule

Format: Text box

Default: N/A

Range: A 32-character string. Valid characters are alphanumeric and underscore. Must contain at least one alphabetic character and must not start with a digit.

* Application Name The Diameter Application name and Id to which this Suspect Binding Removal Rule applies. Session initiation answer messages including the Application-Id are candidates to match this rule.

Format: Pull-down list

Default: N/A

Range: Supported P-DRA Application-Ids

* Command Code The Diameter Command Code or Extended Command Code name and value to which this Suspect Binding Removal Rule applies. Session initiation answers messages including this Command Code are candidates to match this rule.

Format: Pull-down list

Default: N/A

Range: Supported P-DRA session initiation answer messages

* Error Scenario Category

The error category to which the Suspect Binding Removal Rule applies.

Category Unable to Route is for when no session initiation answer is received from the PCRF (possibly because the request could not be routed). If Unable to Route is chosen, the (Experimental) Result Code sent to the policy clients is the one configured on the Policy and Charging > Configuration > Error Codes screen for the specific interface.

Category External Result is for when a specified session imitation error answer is received from the PCRF. If External Result is chosen, a Result Code must be specified, otherwise no Result Code is necessary.

Format: Pull-down list

Default: N/A

Range: External Result, Unable to Route

Result Code The session initiation error answer (Experimental) Result Code to which this Suspect Binding Removal rule applies if the Error Scenario Category is External Result. This field is not applicable when Error Scenario Category is set to Unable to Route.

Format: Text box

Default: N/A

Range: 1-9999

Vendor ID If a Result Code is entered in the Result Code field and that Result Code is an experimental result code, enter a Vendor-Id in this field. Otherwise, leave the field blank.

Format: Text box

Default: N/A

Range: 1-4294967295

Remove Suspect Binding Immediately

Check this box if a single occurrence of this rule match means that the binding should be removed. Uncheck this box if multiple occurrences of this rule match are required before the binding should be removed.

If this box is unchecked, the Suspect Binding Removal Events Threshold field in Policy and Charging > Configuration > Policy DRA > Network-Wide Options on the NOAM controls how many Suspect Binding Removal Events must occur before a Session-Release RAR will be sent to the policy client to request removal of the binding.

Format: Check box

Default: No (Unchecked)

Range: Yes (Checked), No (Unchecked)

Comments An optional comment to describe this suspect binding removal rule

Format: Text box

Default: N/A

Range: 0-64 characters