1. Range Based Address Resolution User Guide
  2. Configuration of RBAR
  3. RBAR Configuration
  4. Exceptions configuration

3.2.2 Exceptions configuration

The RBAR, and then Configuration, and then Exceptions page allows you to specify the routing exception action to take when RBAR is unable to resolve an address to a destination for each supported Diameter application and routing exception type.

There are three (3) routing exception entries (No Address Match, No valid Routing Entity Address, and Unknown Command Code) automatically inserted with the Routing Exception Action set to Forward Unchanged as the default action for a supported Diameter application entry when that application entry is added. Similarly, these Routing Exceptions that are associated with an application entry are automatically deleted when that application entry is deleted.

From the RBAR, and then Configuration, and then Exceptions page, you can:
  • Filter the list of exceptions to display only the desired exceptions.
  • View a list of supported Diameter applications and their associated routing exception types and routing exception actions.
  • Edit the routing exception action and its associated attributes for a supported Diameter application.