7 Setting Up RADIUS Mediation for Accounting

This chapter describes the steps required to install, configure, administer, and use Oracle Communications Service Broker to act as a Remote Authentication Dial In Service (RADIUS) Manager and support RADIUS accounting with Oracle Communications Billing and Revenue Management (BRM).

About RADIUS Accounting Mediation

Service Broker can translate RADIUS accounting requests to PCP requests that BRM understands.

Figure 7-1 shows the Service Broker interworking modules that you need to set up and configure to apply the BRM offline charging services in a network that supporting offline charging with RADIUS.

Figure 7-1 Service Broker Interworking Modules for Offline Charging

Configuring RADIUS Accounting

To set up Service Broker to perform RADIUS Authentication and Authorization mediation to PCP, you need to configure the following Service Broker components:

• RADIUS SSU

• PCP SSU

• R-IM-OFCF RADIUS

• IM-OFCF PCP

• Orchestration Engine

Deploying RADIUS Accounting Mediation

To set up Service Broker to perform RADIUS Accounting mediation to PCP, you need to deploy and configure the following Service Broker components:

• IM-OFCF PCP and R-IM-OFCF RADIUS

  See the chapters "Configuring the IM-OFCF PCP" and "Configuring the R-IM-OFCF RADIUS" in Oracle Communications Service Broker Processing Domain Configuration Guide for more information.

• Orchestration Engine

  See the chapter "Configuring the Orchestration Engine" in Oracle Communications Service Broker Processing Domain Configuration Guide for more information.

• RADIUS SSU and PCP SSU

  See "Configuring the RADIUS SSU" and "Configuring the PCP SSU" in Oracle Communications Service Broker Signaling Domain Configuration Guide for more information.

Configuration WorkFlow

To create an end-to-end configuration for RADUIS accounting:

1. Configure the RADIUS SSU. See "Configuring the RADIUS SSU".

2. Configure the PCP SSU to connect to BRM. See "Connecting to BRM Through PCP".

3. Create an instance of R-IM-OFCF RADIUS and configure it. See "Creating and Configuring an R-IM-OFCF RADIUS Instance".

4. Configure the Orchestration Engine to route the request. See "Creating Orchestration Logic for RADIUS Accounting".

5. Configure the IM-OFCF PCP the interworking module to connect to your BRM installation. See "Configuring the IM-OFCF PCP".

6. Activate the interworking modules. See "Activating the R-IM-OFCF RADIUS and IM-OFCF-PCP Instances".

Configuring the RADIUS SSU

Configure the RADIUS SSU for accounting requests as described in “Configuring the RADIUS SSU” in Oracle Communications Service Broker Signaling Domain Configuration Guide. Use the following configuration data, specifically:

1. Create a new incoming routing rule.

2. Set the parameter Name to the rule name to use.

3. Set Local Realm to any. This is a case-sensitive field.

4. Set Alias to the instance name that you are going to use for the R-IM-OFCF RADIUS instance. This instance is create later in the process. See "Creating and Configuring an R-IM-OFCF RADIUS Instance". We will refer to this name as rimocfradius. Set the type of IM instance to RIMOCFRADIUS and the domain id to ocsb.com. The complete string to enter in the Alias fields is:

   ssu:[e-mail]

Connecting to BRM Through PCP

To connect Service Broker to Oracle Communications BRM:

1. Create BRM connection pools in the PCP SSU, as described in "Defining Connection Pools" in the chapter "Configuring the PCP Signaling Server Unit" in Oracle Communications Service Broker Signaling Domain Configuration Guide.

   See also "About Connection Pooling" in Oracle Communications Billing and Revenue Management System Administrator's Guide.

2. Secure the BRM connection pools that you created in step 1, as described in "Securing Connection Pools" in the chapter "Configuring the PCP Signaling Server Unit" in Oracle Communications Service Broker Signaling Domain Configuration Guide.

   In the Administration Console:

   1. In the navigation tree, expand the OCSB node, and then the Signaling Tier node.

   2. Select the SSU PCP node.

   3. In the PCP tab, select the Credential Store tab.

   4. In the Password area, in the Key field, enter the ID of the connection pool that you want to secure. This should be the Pool ID that you assigned to the connection pool when you created the connection pool in step 1.

   5. In the Password area, in the Password field, enter the password of the Oracle Communications BRM client application account used by the connection pool to access the BRM. This should be the password of the account that you configured in the BRM CM Login ID field when you initially defined the connection pool.

   6. In the Password area, uncheck the one-way checkbox.

   7. In the Password area, click the Set Password button.

   8. Repeat steps d through f for each connection pool that you want to secure.

3. Define destination BRM applications, as described in "Defining PCP Network Entities" in the chapter "Configuring the PCP Signaling Server Unit" in Oracle Communications Service Broker Signaling Domain Configuration Guide.

Creating and Configuring an R-IM-OFCF RADIUS Instance

Create and configure the R-IM-OFCF RADIUS instance for accounting requests as described in “Configuring R-IM-OFCF Radius” in Oracle Communications Service Broker Processing Domain Configuration Guide. Use the following configuration data, specifically:

1. Give the IM a name that matches the Alias used when creating the incoming routing rule in the RADIUS SSU. See "Configuring the RADIUS SSU".

Creating and Configuring an IM-OFCF PCP Instance

Create and configure the IM-OFCF PCP instance for accounting requests as described in “Configuring IM-OFCF PCP” in Oracle Communications Service Broker Processing Domain Configuration Guide. Use the following configuration data, specifically:

• Give the IM a name that will be used by the Orchestration Engine when routing requests. We will refer to this name as imofcfpcp.

Creating Orchestration Logic for RADIUS Accounting

Configure the Orchestration Studio to route RADIUS accounting requests to the IM-OFCF PCP instance. See Oracle Communications Service Broker Orchestration Studio User's Guide. Use the following configuration data, specifically:

• Route the requests to sip:[e-mail]

  Where imofcfpcp is the IM name you gave for the IM-OFCF PCP instance. See "Creating and Configuring an IM-OFCF PCP Instance".

Activating the R-IM-OFCF RADIUS and IM-OFCF-PCP Instances

To activate the newly created R-IM-OFCF RADIUS and IM-OFCF-PCP instances:

1. In the Domain Navigation pane, expand OCSB.

2. Expand Processing Tier and then expand Interworking Modules.

3. Select IM Management.

4. Click on the R-IM-OFCF RADIUS instance. The instance name is the same as you gave when you created it. See "Creating and Configuring an R-IM-OFCF RADIUS Instance".

5. Click Activate.

6. Click on the IM-OFCF-PCP instance. The instance name is the same as you gave when you created it. See "Creating and Configuring an IM-OFCF PCP Instance".

7. Click Activate.

Configuring the IM-OFCF PCP

Configure the IM-OFCF-PCP IM for accounting requests as described in “Configuring IM-OFCF PCP” in Oracle Communications Service Broker Processing Domain Configuration Guide. Use the following configuration data, specifically:

1. Set the field Destination Alias to brm.

Extending RADIUS Accounting Support

You can extend the accounting functionality by adding support for custom RADIUS AVPs. You do that by adding custom AVPs to the RADIUS dictionary in the RADIUS SSU. See “Configuring the RADIUS SSU" in Oracle Communications Service Broker Signaling Domain Configuration Guide for more information.

If you add custom AVPs to the RADIUS dictionary in the RADIUS SSU, you also need to implement custom mappers from RADIUS to Rf (deployed in R-IM-OFCF RADIUS), and from Rf to PCP (deployed in IM-OFCF PCP).