Configuring Diameter Host Based Peer Routes

Host based diameter routes are when messages are intended for a specific destination-host or a list of destination-hosts and must be routed to an intermediary peer because the destination-host cannot be reached.
Note: The routing table can be used with a stateful SCEF-FE server by creating a route with an action of LOCAL. To use routes in tandem with a stateful SCEF-FE server, you must create a route with an action of LOCAL.

Use this procedure if you have a very wide network where direction Destination-Host connections must be routed through an intermediary peer.

To configure the Diameter host based peer routes table:

  1. From the MRA section of the navigation pane, select Configuration.

    The content tree displays a list of policy server/MRA groups.

  2. From the content tree, select the MRA server.

    The MRA Administration page opens in the work area.

  3. Select the Diameter Routing tab.

    The Diameter Routing configuration settings are displayed for that server or device.

  4. Click Modify Routes.

    The Modify the Diameter Route Table page opens.

  5. Click Add and select Host Based Route.

    The Add Host Based Route window opens.

  6. Enter a name for the destination host.

  7. Add destination host identities.
    1. Enter the number of host identities in the Value field.

      Note: You can use the wildcards * (match any number of characters) and ? (match only one character).

    2. (Optional) Select Evaluate as a Regular Expression.

      When selected, enabled the matching of route criteria using regular expression syntax, opposed to the previously supported matching wildcards. (See Examples of Java Regular Expressions for MRA Routes for examples of using JAVA Regular Expressions.)

    3. Click Add

      This adds the host identities to the field.
      Note: Clicking Delete deletes a selected host identity.

    4. (Optional) Repeat to add additional destination host identities.
    5. Select the Origin.

      The default is ANY. Enables a message to be routed based on the origin-host of the message. For example, if MPE is selected, then it is an MPE originated message (meaning that any messages that originated from any managed MPE are applied to this route).

      Note: If topology hiding is enabled, the message is processed based on the original Origin-Host in the routing table, since topology hiding processing takes place after the routing table.

  8. Define the filter.
    1. Select the Application ID.

      The default is Rx.

      Note: You can include only one application per route rule. For multiple applications, create multiple rules.

    2. Select the User ID type.

      ANY is the default.

    3. Enter the user ID to be routed (for example, an NAI or E.164 number) in the Value field. Separate user IDs using a comma (,); use an asterisk (*) as a wildcard character.
    4. Click Add to add to the list.

      Note: To remove one or more user ID from the list, select the ID and click Delete.

    5. (Optional) Repeat to add additional destination host identities.
    6. Click Save.
  9. Define the next hop.
    1. Select the action.
    2. Select the server.
  10. Click Save.
  11. 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.

      Note: You can define a server with a Diameter identity.

    4. Click Save.

    Note: To delete the default route, click Delete next to the route.

  12. Click Save.
The Diameter routes are configured with the Realm/Host Identities column displaying the Realm or Host name for the configured route.