26 Configuring R-IM-OCF Ro

The following sections describe how to configure R-IM-OCF Ro using the Service Broker Administration Console and Java MBeans.

Configuring R-IM-OCF Ro with the Administration Console

This section describes how to configure the R-IM-OCF Ro module instances using the Service Broker Administration Console.

To access the R-IM-OCF Ro Configuration screen:

In the domain navigation pane, expand OCSB.
Expand Processing Tier.
Select Interworking Modules.

A list of currently deployed Interworking Modules is displayed.
From the module list, select the module instance that you want to configure.

The R-IM-OCF Ro configuration screen contains the subtabs described in Table 26-1.

Table 26-1 R-IM-OCF Configuration Subtabs

Subtab	Description
Call Handling	Enables you to define how R-IM-OCF Ro handles calls. See "Configuring Call Handling Parameters" for more information.
Diameter Credit Control Application	Enables you to configure parameters specific to the R-IM-OCF Ro DCCA interface. See "Configuring Diameter Credit Control Application Parameters" for more information.
Monitoring	Enables you to define how Runtime MBeans and notifications should operate. See "Configuring Monitoring Parameters" for more information.

Subtab

Description

Call Handling

Enables you to define how R-IM-OCF Ro handles calls.

See "Configuring Call Handling Parameters" for more information.

Diameter Credit Control Application

Enables you to configure parameters specific to the R-IM-OCF Ro DCCA interface.

See "Configuring Diameter Credit Control Application Parameters" for more information.

Monitoring

Enables you to define how Runtime MBeans and notifications should operate.

See "Configuring Monitoring Parameters" for more information.

Configuring Call Handling Parameters

The Call Handling subtab enables you to define how R-IM-OCF Ro handles calls.

Table 26-2 describes configuration parameters on the Call Handling subtab.

Table 26-2 R-IM-OCF Ro Call Handling Parameters

Name	Type	Description
Result-Code AVP Value on Session Disconnection by AS	STRING	Specifies the value that R-IM-OCF Ro sets in a CCA Result-Code AVP when a session is disconnected by the charging application. Note: when the application disconnects a session, R-IM-OCF Ro generates a CCA only as a response to CCR. If R-IM-OCF Ro does not receive CCR to which it can respond in a reasonable time period, R-IM-OCF Ro abnormally disconnect the session.
Default Session Type	STRING	Specifies how R-IM-OCF Ro marks new sessions internally. Possible values: Orig Stands for an outgoing call Term Stands for an incoming call Default value: Orig
Initial CCR Mode	STRING	Specifies whether incoming initial CCRs (Request-Type AVP set to Initial) are considered ECUR or SCUR.
Result-Code AVP on No Response from AS	STRING	Specifies the value that R-IM-OCF Ro sets in a CCA Result-Code AVP in a case when the charging application is not responding (that is a response timer expires). Default value: 5012
Result-Code AVP on SAL 4XX	STRING	Specifies the value that R-IM-OCF Ro sets in a CCA Result-Code AVP when receiving an internal Service Broker SAL 4XX error. Default value: 4010 This parameter does not apply for 402, 403 and 404. In that case, the Result-Code AVP is set to 4012, 4010 and 5030 respectively.
Result-Code AVP on SAL 5XX	STRING	Specifies the value that R-IM-OCF Ro sets in a CCA Result-Code AVP when receiving an internal Service Broker SAL 5XX error. Default value: 4010 This parameter does not apply for 503. In that case, the Result-Code AVP is set to 3002.
Result-Code AVP on SAL 6XX	STRING	Specifies the value that R-IM-OCF Ro sets in a CCA Result-Code AVP when receiving an internal Service Broker SAL 6XX error. Default value: 4010
Default Result-Code AVP	STRING	Specifies the value that R-IM-OCF Ro sets in a CCA Result-Code AVP when receiving an internal Service Broker SAL error and non of the previous parameters apply.

Configuring Diameter Credit Control Application Parameters

The Diameter Credit Control Application tab enables you to configure parameters related to the IM-OCF Ro Diameter Credit Control Application (DCCA) interface. The Diameter Credit Control Application tab contains subtabs described in Table 26-3.

Table 26-3 R-IM-OCF Diameter Credit Control Application Subtabs

Subtab	Description
General	Enables you to set up a DCCA dialect. See "Configuring General Parameters" for more information.
AVPs	Enables you to specify Attribute-Value Pairs (AVPs) to be set in CCAs. See "Configuring AVPs Parameters" for more information.

Subtab

Description

General

Enables you to set up a DCCA dialect.

See "Configuring General Parameters" for more information.

AVPs

Enables you to specify Attribute-Value Pairs (AVPs) to be set in CCAs.

See "Configuring AVPs Parameters" for more information.

Configuring General Parameters

The General subtab enables you to set up a DCCA dialect. Table 26-4 describes the parameter you can configure.

Table 26-4 R-IM-OCF DCCA General Subtab Parameter

Name	Type	Description
DCCA Dialect	STRING	Specifies the DCCA dialect that R-IM-OCF Ro should use. Possible values: STANDARD_DCCA Standard DCCA dialect BRM Oracle Communications Billing and Revenue Management DCCA dialect Default value: STANDARD_DCCA

Name

Type

Description

DCCA Dialect

STRING

Specifies the DCCA dialect that R-IM-OCF Ro should use.

Possible values:

STANDARD_DCCA

Standard DCCA dialect
BRM

Oracle Communications Billing and Revenue Management DCCA dialect

Default value: STANDARD_DCCA

Configuring AVPs Parameters

The AVPs subtab enables you to specify Attribute-Value Pairs (AVPs) to be set in CCAs. Table 26-5 describes the AVPs that you can specify.

Table 26-5 R-IM-OCF DCCA AVPs Subtab Parameters

Name	Type	Description
SCUR AVPs	STRING	Specifies AVPs that IM-OCF Ro place inside CCAs when constructing an SCUR CCA. This parameter is useful when Service Broker is required to accommodate non-standard and vendor specific AVPs when interacting with Diameter CTF entities. The specification is given in XML format which is described below this table. Note: AVPs specified by this parameter are given lowest priority. That is, if an AVP is already available inside either: Internal Service Broker SAL message or XML carried on internal Service Broker SAL message or Other IM-OCF configuration then all the other values prevail the value defined in this XML.
ECUR AVPs	STRING	Specifies AVPs that IM-OCF Ro places inside CCAs when constructing an ECUR CCA. This parameter is useful when Service Broker is required to accommodate non-standard and vendor specific AVPs when interacting with Diameter CTF entities. The specification is given in XML format which is described below this table. Note: AVPs specified by this parameter are given lowest priority. That is, if an AVP is already available inside any of the following: Internal Service Broker SAL message or XML carried on internal Service Broker SAL message or Other IM-OCF Ro configuration then all those values have a higher priority than the value defined in this XML.
IEC AVPs	STRING	This parameter is useful when Service Broker is required to accommodate non-standard and vendor specific AVPs when interacting with Diameter CTF entities. The specification is given in XML format which is described below this table. Note: AVPs specified by this parameter are given lowest priority. That is, if an AVP is already available inside the following: Internal Service Broker SAL message or XML carried on internal Service Broker SAL message or Other IM-OCF Ro configuration then all those values have a higher priority than the value defined in this XML.

Name

Type

Description

SCUR AVPs

STRING

Specifies AVPs that IM-OCF Ro place inside CCAs when constructing an SCUR CCA.

This parameter is useful when Service Broker is required to accommodate non-standard and vendor specific AVPs when interacting with Diameter CTF entities.

The specification is given in XML format which is described below this table.

Note: AVPs specified by this parameter are given lowest priority. That is, if an AVP is already available inside either:

Internal Service Broker SAL message or
XML carried on internal Service Broker SAL message or
Other IM-OCF configuration

then all the other values prevail the value defined in this XML.

ECUR AVPs

STRING

Specifies AVPs that IM-OCF Ro places inside CCAs when constructing an ECUR CCA.

This parameter is useful when Service Broker is required to accommodate non-standard and vendor specific AVPs when interacting with Diameter CTF entities.

The specification is given in XML format which is described below this table.

Note: AVPs specified by this parameter are given lowest priority. That is, if an AVP is already available inside any of the following:

Internal Service Broker SAL message or
XML carried on internal Service Broker SAL message or
Other IM-OCF Ro configuration

then all those values have a higher priority than the value defined in this XML.

IEC AVPs

STRING

This parameter is useful when Service Broker is required to accommodate non-standard and vendor specific AVPs when interacting with Diameter CTF entities.

The specification is given in XML format which is described below this table.

Note: AVPs specified by this parameter are given lowest priority. That is, if an AVP is already available inside the following:

Internal Service Broker SAL message or
XML carried on internal Service Broker SAL message or
Other IM-OCF Ro configuration

then all those values have a higher priority than the value defined in this XML.

You need to specify values of the SCUR AVPs, ECUR AVPs and IEC AVPs parameters in an XML format. This format enables you to specify AVPs that R-IM-OCF must place inside CCAs when R-IM-OCF Ro constructs a CCA.

In the XML format in which you specify AVPs, you need to define the following parameters:

Command name
AVP group
AVP

The following XML code shows an example of how you can cause R-IM-OCF Ro to add the CC-Time AVP into CCAs that R-IM-OCF generates.

<dcca>
   <command name="CCA" code="272">
      <gavp name="Multiple-Services-Credit-Control" code="456" vendor-id="0"    type="GROUPED">
         <gavp name="Granted-Service-Units" code="431" vendor-id="0" type="GROUPED">
            <avp name="CC-Time" code="420" vendor-id="0" type="INTEGER">10</avp>
         </gavp>
        </gavp>
   </command>
</dcca>

The XML code that you provide for AVPs, must conform to the following XML schema:

<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xsd:element name="dcca">
   <xsd:complexType>
      <xsd:sequence minOccurs="1" maxOccurs="1">
         <xsd:element ref="command" />
      </xsd:sequence>
   </xsd:complexType>
</xsd:element>

<xsd:element name="command">
   <xsd:complexType>
      <xsd:sequence>
         <xsd:element ref="avp" maxOccurs="unbounded" />
         <xsd:element ref="gavp" maxOccurs="unbounded" />
      </xsd:sequence>
      <xsd:attribute ref="name" use="required" />
      <xsd:attribute ref="code" use="required" />
   </xsd:complexType>
</xsd:element>

<xsd:element name="gavp">
   <xsd:complexType>
      <xsd:choice>
         <xsd:element ref="avp" maxOccurs="unbounded" />
         <xsd:element ref="gavp" maxOccurs="unbounded" />
      </xsd:choice>
      <xsd:attribute ref="name" use="required" />
      <xsd:attribute ref="code" use="required" />
      <xsd:attribute ref="vendor-id" use="optional" />
      <xsd:attribute ref="type" use="required" />
   </xsd:complexType>
</xsd:element>

<xsd:element name="avp">
   <xsd:complexType>
      <xsd:attribute ref="name" use="required" />
      <xsd:attribute ref="code" use="required" />
      <xsd:attribute ref="type" use="required" />
      <xsd:attribute ref="vendor-id" use="optional" />
   </xsd:complexType>
</xsd:element>

<xsd:attribute name="name" type="xsd:string" />
<xsd:attribute name="code" type="xsd:int" />
<xsd:attribute name="vendor-id" type="xsd:int" />

<xsd:attribute name="type">
   <xsd:simpleType>
      <xsd:restriction base="xsd:string">
         <xsd:enumeration value="STRING" />
         <xsd:enumeration value="INTEGER" />
         <xsd:enumeration value="LONG" />
         <xsd:enumeration value="BYTES" />
         <xsd:enumeration value="GROUPED" />
      </xsd:restriction>
   </xsd:simpleType>
</xsd:attribute>
</xsd:schema>

Configuring Monitoring Parameters

The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an R-IM-OCF Ro. For more information about configuring monitoring, see "Configuring Monitoring with the Administration Console".

Configuring R-IM-OCF Ro with Java MBeans

Service Broker provides a set of MBeans that provide attributes and operations for configuring the R-IM-OCF Ro through JMX. Figure 26-1 shows the hierarchy of the R-IM-OCF MBeans.

Figure 26-1 R-IM-OCF Ro MBean Hierarchy

The following sections provide reference information for the R-IM-OCF Ro configuration MBeans.

Note:

MBeans described in this guide may include additional advanced attributes, which are not described in the guide. Advanced attributes are reserved for internal use. Do not change these attributes.

The following MBeans are common for all components of Service Broker and described in "Configuring Monitoring with Java MBeans":

MonitoringGeneralMBean
ThresholdCrossedNotificationRulesMBean
ThresholdCrossedNotificationRuleMBean
StateChangedNotificationRulesMBean
StateChangedNotificationRuleMBean

RimocfMBean

RimocfMBean is a root MBean for the R-IM-OCF Ro configuration.

Factory Method

Created automatically

Attributes

None

Operations

ObjectName getCallHandling()

Gets a reference to the instance of CallHandlingMBean

ObjectName getDiameterCreditControlApplicationGeneral()

Gets a reference to the instance of DiameterCreditControlApplicationGeneralMBean

ObjectName getDiameterCreditControlApplicationAvps()

Gets a reference to the instance of DiameterCreditControlApplicationAvpsMBean

ObjectName getMonitoringGeneral()

Gets a reference to the instance of MonitoringGeneralMBean

ObjectName getThresholdCrossedNotificationRules()

Gets a reference to the instance of ThresholdCrossedNotificationRulesMBean

ObjectName getStateChangedNotificationRules()

Gets a reference to the instance of StateChangedNotificationRulesMBean

CallHandlingMBean

CallHandlingMBean enables you to configure how the R-IM-OCF Ro handles calls.

Factory Method

Created automatically

Attributes

ResultCodeAvpValueOnSessionDisconnectionByAs
DefaultSessionType
InitialCcrMode
ResultCodeAvpOnNoResponseFromAS
ResultCodeAvpOnSal4xx
ResultCodeAvpOnSal5xx
ResultCodeAvpOnSal6xx
DefaultResultCodeAvp
CallingPartyNumber
CalledPartyNumber

For more information on these attributes, see Table 26-2.

Operations

None

DiameterCreditControlApplicationGeneralMBean

DiameterCreditControlApplicationGeneralMBean enables you to set up a DCCA dialect and enable monitor call duration.

Factory Method

Created automatically

Attributes

DccaDialect

For more information on these attributes, see Table 26-4.

Operations

None

DiameterCreditControlApplicationAvpsMBean

DiameterCreditControlApplicationAvpsMBean enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs.

Factory Method

Created automatically

Attributes

EcurAvps
ScurAvps
IecAvps

For more information on these attributes, see Table 26-5.

Operations

None