In this section:
The Ribbon DSC supports ingress filtering for inter-realm relay validation. This feature can be enabled when configuring a Ribbon DSC Node (refer to To configure a DSC Node (General Configuration). The Realm Routing Table that is associated with a Ribbon DSC Node provides the rules for valid inter-realm routes.
Ingress filtering compares information about the realm of the incoming ADN against the contents of the Origin-Realm AVP in the request message. If the Origin-Realm is the same as incoming Realm or if there is a matching Realm Routing Record, the message passes ingress filtering. A matching Realm Routing Record associates the Origin-Realm to the incoming Realm. If a message fails ingress filtering, a log is generated with message details and this message is returned as an ERROR_UNABLE_TO_DELIVER. Also, a dynamic data measurement is generated to indicate that a message was discarded due to ingress filtering. For information about data measurements, refer to Diameter Data Measurement.
Note
The advanced routing tables configured on a DSC node are applied in a specific order that depends on the Initial Routing Table configured as the Default Routing Table. If the Initial Routing Table is configured as the Default Routing Table, the Topology Mapping Routing Table is implemented first, the Initial Routing Table second, and finally the Realm Routing Table. If the Initial Routing Table is not configured as the default, the Topology Mapping Table is implemented followed by the Initial Routing Table. Depending on the network configuration, the Realm Routing table may not be implemented when the Initial Routing Table is not the default.
To create a Realm Routing Table
To view a Realm Routing Table
To create a Realm Routing Record
To configure a Realm Routing Record
Overview
Content Tools