...

The Diameter Routing profile is loaded when you start a workflow that depends on it. Changes to the profile become effective when you restart the workflow. It is also possible to make changes effective effectively while a workflow is running. For more information about this, see the section below, To Dynamically Update the Diameter Routing Profile.

To define a Diameter Routing profile, click on the New Configuration button and then select Diameter Routing profile in the menu.

Routing Tab

Image RemovedImage Added
The Diameter Routing profile configuration - Routing tab

Peer Table

A Diameter Stack agent A Diameter Stack agent that uses the Diameter Routing profile maintains transport connections with all the hosts that are defined in the Peer table list. Connections and handshakes of hosts that are not in this list are rejected with the appropriate protocol errors.  Note that will Note that the system will actively try to establish connections to any hosts that are included in this list, unless the  Do Not Create Outgoing Connections option is checked in the Diameter Stack agent.

To Add a Host

1. In the Diameter Routing Profile , click on the Add button beneath the Peer Table .

   The Add Host dialog opens.

   

   The Diameter Routing Profile - Adding a Host
   

   
   

2. Enter the host name and port for the host in the Hostname and Port fields.

   
   

3. Select protocol in the Protocol drop-down-list.

   
   

4. If you want to enable throttling for the peer, select the Enable Throttling check box, and then enter the maximum number of request UDRs per second you want the Diameter Stack agent to transmit to the peer in the Throughput Threshold (UDR/s) field.

   Note
   title Note!
   Ensure that you handle the throttled UDRs in your APL code in the workflow in order to not loose any UDRs.

   
   

5. Click on the Add button and the host will be added in the Peer Table , and then click on the Close button to close the dialog when you are finished adding hosts. 

Anchor
RealmRoutingTable RealmRoutingTable

Realm Routing Table

Realm-based routing is performed when the Destination-Host AVP is not set in a Diameter message. All realm-based routing is performed based on lookups in the Realm Routing Table.

...

...

1. In the Diameter Routing Profile, click on the Add button beneath the Realm Routing Table.
   The Add Route dialog opens.
   
    
   The Diameter Routing profile Profile - Adding a Realm
    

2. Enter the realm name in the Realm text box.
    

3. If the realm serves specific applications, click on the Add button beneath the Applications list box and specify the Application Id. Repeat this step for each application.
    

4. You should only perform this step if Peer Discovery is set to Static and the peer hosts are to be specified in the Realm Routing Table. Click on the Add button beneath the Hostname list box and select a host from the drop-down list. Repeat this step for each host in the realm.
    

5. If you specified the peer hosts of the realm in the previous step, select Static from Peer Discovery. If you want to use dynamic peer discovery instead, select Dynamic from this drop-down list.
    

6. Click on the Add button and the realm will be added to the Realm Routing Table, and then click on the Close button to close the dialog when you are finished adding realms.

...

For information about how to configure your DNS for dynamic peer discovery, see the Diameter Base Protocol (RFC 6733).

...

The setting Enable Dynamic Peer Discovery in the Routing tab and the settings in the DNS tab are is not read from the Diameter Routing table at refresh. To make changes to these settings effective, you must restart the workflow(s).

The routing table can be refreshed from the Workflow Monitor or from the Command Line Tool.  In In the Workflow Monitor, double-click the Diameter Stack agent to open the Workflow Status Agent configuration.
 In In the Command tab, select the Update Routing Table button to refresh the routing table.

...

initialize {
    //Note the space between the angle brackets!
    map<string, map<string, list<string> > > realmTable = (map<string, map<string, list<string> > >) mimGet("Stack1", "Realm Routing Table");
    //Check the size of the table
    if (mapSize(realmTable) != 2)
       abort("Realm table incorrect size");
    //Check that realms are included
    if (mapKeys(realmTable) != listCreate(string, "dr", "*"))
       abort("Wrong realms");
    //Get the inner map for realm name "dr"
    map<string, list<string> > drMap = mapGet(realmTable, "dr");
    //Get the inner map for realm name "*" (unspecified realm)
    map<string, list<string> > starMap = mapGet(realmTable, "*");
    //Any Application Id
    debug(mapGet(drMap, "*"));
    //Application Id 100
    debug(mapGet(starMap, "100"));
    //Any Application Id
    debug(mapGet(starMap, "*"));
}

12:11:40: [peer1, peer2]
12:11:40: [peer3, peer4]
12:11:40: [peer5, peer6]

...