class DIA-CFG-AppRouting

ManagedElement
+-MtasFunction
+-MtasSupportFunctions
+-DIA-CFG-Application
+-DIA-CFG-StackContainer
+-DIA-CFG-RoutingContainer
+-DIA-CFG-Drt
+-DIA-CFG-AuthReqContainer
+-DIA-CFG-AppRouting
ManagedElement
+-MtasFunction
+-MtasSupportFunctions
+-DIA-CFG-Application
+-DIA-CFG-StackContainer
+-DIA-CFG-RoutingContainer
+-DIA-CFG-Drt
+-DIA-CFG-AccReqContainer
+-DIA-CFG-AppRouting

This MO encapsulates routing information.
Depending on this information decision how to process (what action to be applied to and what destination to be used for routing) the incoming requests from a particular Diameter Application is made.

Attributes
dia_mim_DIA-CFG-AppRouting_action
mandatory
action
The routing action for requests from a certain realm and a given request type.
The routing action belongs to the Diameter application specified in the "requestedApp" attribute. All actions except none are valid when the isIncomingRequest is set to TRUE. Allowed values for this attribute:
0 = local: Diameter messages that resolve to a routing entry with the Local Action set to Local can be satisfied locally, and do not need to be routed to another server.
1 = relay: All Diameter messages within this category must be routed to a next hop server, without modifying any non-routing AVPs.
2 = proxy: All Diameter messages within this category must be routed to a next hop server.
3 = redirect: Diameter messages within this category must have the identity of the home Diameter server(s) appended, and returned to the sender of the message.
4 = none: Used when the isIncomingRequest field is set to FALSE, which means that the request is an outgoing message.
5 = other: Any other Diameter application, for example, Translator or any other future application.
boolean[0..1]
autoFailback = true
Flag to indicate if failback to primary destination shall be done as soon as it becomes available.
dia_mim_DIA-CFG-AppRouting_nodeIds[0..] nonUnique
nodeIds
One or more servers that the message is to be routed to.
If action=none, these servers must be defined as Peer Nodes. The nodeIds consists of an address list with an index, which is called the array index.
dia_mim_DIA-CFG-AppRouting_redirectNodeIds[0..] nonUnique
redirectNodeIds
One or more servers used for redirect agent functionality.
If action=redirect, these servers may be defined as any nodes or left empty. The redirectNodeIds consists of an address list with an index, which is called the array index.
string
key
mandatory
noNotification
restricted
requestedApp
Vendor's Diameter application whose messages are recognized by the Realm Routing Table (RRT).
The "appId" field is checked against the "supportedAuthAppIds" and the "supportedAcctAppIds" in Own Node if vendorId is 0, and against the "supportedVendorSpecificApp" in Own Node if vendorId is not 0. If it is not found, an error is issued, and the operation does not take place.
boolean[0..1]
noNotification
readOnly
secFailoverActive
Flag to indicate if failover to secondary destination has occurred.
string[0..] nonUnique
noNotification
readOnly
secFailoverDest
NodeId of the selected secondary destination.
string[0..] nonUnique
secondaryNodeIds
One or more servers for secondary destinations that the message is to be routed to.
The secondarynodeIds consists of an address list with an index, which is called the array index, and with a priority.

  class DIA-CFG-AppRouting