The following Diameter configuration must be done before RBAR configuration can be performed.
All Diameter Configuration is done using the SOAM GUI in a 3-tiered DSR topology.
Diameter Application Ids must be configured prior to making them available for use in an RBAR Address Resolution. Use the page to configure Diameter Application Ids.
The Application Ids that need to be configured depend on the types of Diameter Servers being supported, including HSS, PCRF, OFCS, and OCS.
Diameter Command Codes must be configured prior to using them in an RBAR Address Resolution. Use the page to configure Diameter Command Codes.
Configure any Command Codes that need to be handled by RBAR. The Command Codes are associated with the Diameter Applications supported by the Diameter Servers (for example, HSS, PCRF, OCFS, or OCS) which are the destination of Diameter Requests being routed by RBAR. For example, the combination of Application Id = S6a and Command Code = ULR/ULA might be relevant for HSS.
Either use the default Application Route Table (always available), or use the Diameter > Configuration> Application Route Tables > [Insert] page to configure one or more Application Route Tables in addition to the default. Application Route Tables contain Application Routing Rules that direct messages to RBAR and other DSR Applications.
On the Diameter>Configuration >Application Route Tables page, select an Application Route Table Name and click View/Edit Rules.
Use the Viewing Rules for Application Route Table page to insert or edit an Application Routing Rule so that messages are directed to RBAR.
Set the Application Name to RBAR.
If the RBAR application and the DM-IWF application will be "chained" so that both of them can process the same Request message, insert or edit a second Application Routing Rule with the Application Name set to DM-IWF.
Set the Priority in each of the two Application Routing Rules to indicate which application will process the message first (the higher priority processes first).