Configuring Diameter Realm Based Peer Routes

By default, Diameter messages are processed locally. In a network with multiple Policy Management devices, messages can be routed, by realm, application, or user ID, for processing by peers or other realms.

Note: Diameter messages can be routed in either an MPE or MRA; the steps listed below can be used for either server.

Use this procedure if you have an extensive peer network or a network that includes multiple realms, user IDs, or applications.

To configure the Diameter realm based peer routes:

From the Policy Management device (either Policy Server or MRA section of the navigation pane, select Configuration.
The content tree displays a list of policy server groups.
From the content tree, select the Policy Server or MRA that needs diameter routing.
The Policy Server Administration or MRA Administration page opens in the work area.
Select the Diameter Routing tab.
The Diameter Routing configuration settings display.
Click Modify Routes.
The Modify the Diameter Route Table page opens.
Add a route to the table
1. Click Add.
  The Add Diameter Route (Realm Based Route) window opens.
2. Configure the route using the following fields.
  - Diameter Realm
    For example, Example.com.
  - Application ID
    Select Rx (default), Gq, Ty, Gx, Gxx, Sd, Sy, Gy, S9, Vzr, or All.
    
    Note: You can include only one application per route rule. For multiple applications, create multiple rules.
  - User ID type
    Select ANY (default), E.164(MSISDN), IMSI, IP, NAI, PRIVATE, SIP_URI, or USERNAME.
  - Value
    Enter the user ID to be routed (for example, an NAI or E.164 number). Separate user IDs using a comma (,); use a period followed by an asterisk (.*) as a wildcard character. To add the user ID to the list, click Add; to remove one or more user IDs from the list, select them and click Delete.
  - Evaluate as Regular Expression
    The check box allows the matching of route criteria using regular expression syntax, opposed to the previously supported matching wildcards. Regular expressions must be Java expressions; using any other language expression will result in a failed status
    
    See Examples of Java Regular Expressions for MRA Routes for more information about using regular expressions for MRA routes.
  - Action
    Select PROXY (stateful route, default), RELAY (stateless route), or LOCAL (process on this device).
  - Server ID
    Select a destination peer from the list.
    
    Note: You can define a server with a Diameter identity.
3. Click Save.
(Optional) Add, delete, modify, or order entries.
- Cloning an entry in the table
  1. Select an entry in the table.
  2. Click Clone. The Clone window opens with the information for the entry.
  3. Make changes as required.
  4. Click Save. The entry is added to the table.
- Editing an entry in the table
  1. Select the entry in the table.
  2. Click Edit. The Edit Response window opens, displaying the information for the entry.
  3. Make changes as required.
  4. Click Save. The entry is updated in the table.
- Deleting a value from the table
  1. Select the entry in the table.
  2. Click Delete. A confirmation message displays.
  3. Click Delete to remove the entry. The entry is removed from the table.
- Ordering the list.
  If you define multiple entries, they are searched in the order displayed in this list. To change the order:
  1. Select an entry.
  2. Click Up or Down. The search order is changed.
Define the default route:
1. Click Edit in the Default Route section.
2. Select the default action: PROXY, RELAY, or LOCAL.
3. Select the peer server ID.
4. Click Save.
To delete the default route, click Delete.
Click Save.

The Diameter realm based peer routes are configured.