6 Configuring Node Chain Routing

This chapter contains information on the requirements for configuring the node chain routing for Oracle Communications Offline Mediation Controller IMS CDF/CGF cartridge pack.

This section explains the supported routing configurations for the IMS node chain. Both Multicast and Directed routing are supported in specific parts of the IMS node chain. The purpose for using Directed routing is to route records with particular attributes to one node or node stream, and route records with other specific attributes to a different node or node stream.

Default Configuration

Directed routing is supported between the Diameter Parser EP and the two Session Sequencing EPs. For the directed routing connection between the Diameter Parser EP and the first Session Sequencing EP (with the IMS R6 Event De-Duplication rule file), select the "Accounting-Record-Type" attribute and set the value equal to one. For the directed routing connection between the Diameter Parser EP and the second Session Sequencing EP (with the IMS R6 Sequence Processing rule file), select the "Accounting-Record-Type" attribute and set the value not equal to one.

Figure 6-1 shows the default configuration for the node chain routing.

Figure 6-1 Node Chain Routing - Default Configuration

Description of Figure 6-1 follows
Description of "Figure 6-1 Node Chain Routing - Default Configuration"

Alternate Configuration

In addition to the default node chain configuration, you can add another 3GPP IMS ASN.1 DC, and use Directed routing from the IMS Session Aggregation AP to each DC. For example, you can configure Directed routing on the "RecordType" attribute, and send S-CSCF records to one DC and P-CSCF records to the other DC. When configuring Directed routing for the S-CSCF record stream, select the "RecordType" attribute, and set the value equal to 63. When configuring Directed routing for the P-CSCF record stream, select the "RecordType" attribute, and set the value not equal to 63.

Figure 6-2 shows the alternate configuration for the node chain routing.

Figure 6-2 Node Chain Routing - Alternate Configuration

Description of Figure 6-2 follows
Description of "Figure 6-2 Node Chain Routing - Alternate Configuration"

Supported Routing Attributes

The supported routing attributes between the Diameter Parser EP and the Session Sequencing EP are:

  • Session-Id

  • Origin-Host

  • Origin-Realm

  • Destination-Realm

  • Accounting-Record-Type

  • Accounting-Record-Number

  • Acct-Application-Id

  • User-Name

  • Acct-Interim-Interval

  • Origin-State-Id

  • Role-of-Node

  • User-Session-Id

  • Calling-Party-Address

  • Called-Party-Address

  • Application-server

  • Application-provided-called-party-address

  • IMS-Charging-Identifier

  • Authorized-QoS

  • Service-Id

  • Node-Functionality

  • Retransmitted

The supported routing attributes between the Session Aggregation AP and the 3GPP IMS ASN.1 DC are:

  • Accounting-Record-Number

  • TimeStamp

  • RecordType

  • Retransmission

  • SIP_Method

  • Role_of_Node

  • Session_Id

  • PrivateUserID

  • LocalRecordSequenceNumber

  • RecordSequenceNumber

  • CauseForRecordClosing

  • ServiceDeliveryFailureReason