Related articles:
- Ribbon DSC Routing Tables Standard Rules
- Configuring Incoming ADN Routing Tables and Records
- Configuring Command Code Routing Tables and Records
- Configuring Application ID Routing Tables and Records
- Configuring Attribute Value Pair (AVP) Routing Tables and Records
- Configuring Result Tables and Records
- Configuring Modification Tables and Records
- Configuring Topology Mapping Tables and Mapping Record
- Configuring a Topology Mapping Table and Mapping Record
- Using the DSC Routing Search Utility
- Configuring Routing Tables to Modify AVP Values in Grouped AVPs
The DSC Routing Tables contain routing and processing information of all incoming Diameter request messages (see the following figure).
Routing using configured Routing Tables involves passing the message through the provisioned Routing Tables, starting with an entry table name configured in the DSC Node object, (refer to Configuring DSC Nodes) and proceeding through the chained Routing Tables until:
- a Result Table is reached
- the default routing is defined (dsc_default)
- the message is explicitly rejected (dsc_error or dsc_error<errorCode>)
For more information about routing Diameter messages using configured routing tables, refer to Routing of Diameter Signaling Traffic using Routing Tables.
For information about configuring Realm Routing Tables, AVP Alias Definitions and other Records, refer to DSC Configuration Examples.
For information in the order the advanced routing tables are applied on a DSC node, refer to Configuring Realm Routing Tables and Records.
Message Flow Through the Routing Tables (Example)
Modification Tables can modify the message in externally visible ways (for example, add/remove/modify AVPs), or add information that affects how the message is handled (for example, message tracing).
The following figure shows an example message flow through Routing Tables including the Modification Table.
Message Flow Through the Routing Tables with Optional Modification Tables (Example)
Overview
Content Tools