Table 1 describes the fields on the Exceptions View and Edit pages.
Field | Description | Data Input Notes |
---|---|---|
Application ID (Read only) | Application ID in a Diameter message | N/A |
Application Name (Read only) | Name of the application | N/A |
Routing Exception Type (Read only) | The routing exception that prevented address
resolution. This field displays one of the following values:
|
N/A |
Routing Exception Action | Action that RBAR takes associated with the Routing Exception Type | Format: Radio buttons Range:
|
Destination | Destination to where the message is forwarded associated with the Routing Exception Type. This field is enabled when the Routing Exception Action is set to Forward to Destination. | Format: Pulldown list Range: Available user-configured destinations |
Result-Code Value | Result code associated with this Routing Exception Type. This field is enabled when the Routing Exception Action is set to either Send Answer with Result-Code AVP or Send Answer with Experimental-Result AVP. | Format:
Range:
|
Vendor-ID | Value returned in the Vendor-ID AVP of the answer message associated with this Routing Exception Type. This field is enabled when the Routing Exception Action is set to Send Answer with Experimental-Result AVP. | Format: Text box; numeric Range: 1–4294967295 |
Error Message | Value returned in the Error-Message AVP of the answer message. This field is enabled when the Routing Exception Action is set to either Send Answer with Result-Code AVP or Send Answer with Experimental-Result AVP. |
Format: Alphanumeric, underscore (_), period (.) Range: 0–64 characters Default: Null string |