Diameter Configuration for CPA

Several Diameter Configuration components must be configured before the CPA can be configured and enabled.

All Diameter Configuration components are configured using the SOAM GUI.

Use the explanations and procedures in the Diameter Configuration help and the Diameter User's Guide to complete the configuration of the Diameter Configuration components for the system, including the following Diameter Configuration components for use with CPA.
  1. Application Id

    Use the Diameter > Configuration > Application Ids [Insert] page to define an Application Id for the Rf Accounting Diameter interface (3).

    From the Application Id Value pulldown list, select 3 - Diameter base accounting.

  2. CEX Parameters

    Use the Diameter > Configuration > CEX Parameters [Insert] page to define the Capability Exchange parameters for the Application Id that was configured for use by CPA.

    For the Application Id, select or enter:
    • Application Id Type - Accounting
    • Vendor Specific Application Id, if the Application Id and Vendor Id will be grouped in a Vendor-specific Application Id AVP
    • Vendor Id - if Vendor Specific Application Id is selected
  3. CEX Configuration Sets

    Use the Diameter > Configuration > Configuration Sets > CEX Configuration Sets [Insert] page to configure a CEX Configuration Set to be used in connections with CTF Peer Nodes.

    In the CEX Configuration Set, move 3-"Diameter base Accounting"-Accounting- from the Available CEX Parameters to the Selected CEX Parameters field.

  4. Local Nodes

    Use the Diameter > Configuration > Local Nodes [Insert] page to configure Virtual CDF and Virtual CTF Local Nodes.

    To accomplish Topology Hiding, the Charging Proxy Function appears as one large CDF to the CTFs and as one large CTF to the CDFs. The Charging Proxy Function modifies the Origin-Host and Origin-Realm AVPs in each message being routed to a CTF or CDF. The configuration of this capability is done using Virtual CDF and Virtual CTF Local Nodes.

    At least one Virtual CDF Local Node must be provisioned, but two are recommended to provide each CTF Peer a redundant connection to the DSR.

    At least one Virtual CTF Local Node must be provisioned on the DSR.

    The Realm and FQDN values will be substituted in the Origin-Realm and Origin-Host AVPs.

  5. Use the Diameter > Configuration > Peer Nodes [Insert] page to configure Peer Nodes for every CDF, CTF, and Diameter Application Server (DAS).

    For CDF Peer Nodes, the Replace Dest Realm and Replace Dest Host options must be enabled.

    Do not configure an Alternate Implicit Route List. The Peer Route Table will be defined such that there is a Peer Routing Rule for every CDF Peer, so that routing will always be done using a Route List.

  6. Connections
    Use the Diameter > Configuration > Connections [Insert] page to configure Connections to CTFs, CDFs, and Diameter Application Servers.
    • At least one Connection must be configured to each CTF, CDF, and DAS.
    • Connections communicating with a CTF Peer Node must be associated with a Virtual CDF Local Node.
    • Connections communicating with a CTF Peer Node must select a CEX Configuration Set that has the Diameter base accounting Application Id (3) configured.
    • Connections communicating with a CDF Peer Node must be associated with a Virtual CTF Local Node.
    • On Connections communicating with a CDF Peer Node, enable the Remote Busy Usage option, and set the Remote Busy Abatement Timeout value to the desired length of time that messages will stop being sent on the CDF connection after the receipt of a DIAMETER_TOO_BUSY response.
  7. Application Route Tables

    Either use the default Application Route Table (always available), or use the Diameter > Configuration> Application Route Tables > [Insert] page to configure one or more Application Route Tables in addition to the default. Application Route Tables contain Application Routing Rules that direct messages to CPA and other DSR Applications.

  8. Application Routing Rules

    On the Diameter>Configuration >Application Route Tables page, select an Application Route Table Name and click View/Edit Rules.

    Use the Viewing Rules for Application Route Table page to insert or edit an Application Routing Rule so that messages with Diameter Application ID = 3 are directed to the CPA.

    When defining the Application Routing Rule:

    • In the Conditions field, set the Application-Id Operator to Equals and the Value to 3 - Diameter base accounting. For all other Parameters, set the Operator to Always True.
    • Set the Application Name to CPA.
  9. Route Groups

    Use the Diameter > Configuration > Route Groups [Insert] to configure CDF Peer Route Groups and DAS Peer Route Groups.

    • Only Peer Route Groups are used in the Offline Charging Solution.
    • Configure a CDF Pool Peer Route Group that contains all of the CDF Peer Nodes, with each CDF Peer Node having the same Provisioned Capacity.
    • For each CDF Peer Node, configure a Peer Route Group containing just this CDF Peer Node. Also configure an alternate Peer Route Group containing all CDF Peer Nodes except this one with each CDF Peer Node having the same Provisioned Capacity.
    • For each DAS Peer Node, configure a Peer Route Group containing just this DAS Peer Node.
    • Configure a DAS Pool Peer Route Group that contains all of the DAS Peer Nodes, with each DAS Peer Node having the same Provisioned Capacity.
  10. Route Lists

    Use the Diameter > Configuration > Route Lists [Insert] to configure CDF Route Lists and DAS Route Lists.

    • For each Route List configured for the Charging Proxy Function, the Route Across Route Groups option should be set to Enabled to allow messages to be routed to alternate CDFs if the preferred CDF fails.
    • Configure a CDF Pool Route List containing just the CDF Pool Route Group.
    • For each CDF, configure a CDF Route List, containing the corresponding CDF Peer Route Group with a priority of 1 and the corresponding alternate CDF Peer Route Group with a priority of 2.
    • Configure a DAS Pool Route List containing just the DAS Pool Route Group.
    • For each DAS, configure a DAS Route List containing the corresponding DAS Peer Route Group.
  11. Peer Route Tables

    Use the Diameter > Configuration > Peer Route Tables [Insert] page to configure a Peer Route Table for the Charging Proxy Function.

    Then create Peer Routing Rules to route ACR-Interim and ACR-Stop messages to the preferred CDF peer, or if the preferred CDF Peer is unavailable, then to load balance the message routing to the other CDF Peers.

    Within the Charging Proxy Peer Route Table, for each CDF, create a Peer Routing Rule as follows:
    • In the Conditions field:
      • Set the Destination-Host Operator to Equals and the Value to the FQDN of the CDF Peer Node.
      • Set the Application-Id Operator to Equals and the Value to 3 - Diameter base accounting.
      • For all other Parameters, set the Operator to Always True.
    • Action is set to Route to Peer.
    • Route List is set to the corresponding CDF Route List.
    • Message Priority is set to 1.
    Also create a Peer Routing Rule to load balance the routing of ACR-Start and ACR-Event Request messages across all CDF Peers.
    • In the Conditions field:
      • Set the Destination-Host Operator to Absent.
      • Set the Application-Id Operator to Equals and the Value to 3 - Diameter base accounting.
      • For all other Parameters, set the Operator to Always True.
    • Action is set to Route to Peer.
    • Route List is set to the corresponding CDF Pool Route List.
    • Message Priority is set to 0.
  12. Application Id (edit)

    Use the Diameter > Configuration > Application Ids [Edit] page to assign the Charging Proxy Peer Route Table to the Diameter base accounting Application Id.

  13. Reroute On Answer
    Use the Diameter > Configuration > Reroute on Answer [Insert] page to configure Reroute On Answer to perform alternate routing when a DIAMETER_TOO_BUSY Answer Result-Code is received from a CDF Peer.
    • Set the Answer Result-Code AVP Value to 3004.
    • For the Application Id, select 3 - Diameter base accounting from the pulldown list.
Parent topic: Pre-Configuration Activities