Rf Control Resource Adaptor configuration

The Rf Control Resource Adaptor (Rf Control RA) has 2 types of configuration:

  1. General Resource Adaptor configuration

  2. Additional configuration, which includes the Diameter configuration that extends the general Diameter Resource Adaptor configuration

Configuration of an Rf Control RA Entity

The Rf Control RA has the following configuration parameters.

Parameter Description Default value 
ConfigurationProfile

The diameter configuration profile. See Configuring Diameter Resource Adaptors

RfControlDiameterConfiguration/client

 
ConfigurationProfilePollTime

The time (milliseconds) between checking for configuration changes in the diameter configuration profile (as indicated by the ConfigurationProfile parameter). Value may be 0 (don’t poll) or at least 1000L.

30000L

 
3GPPVersion

The diameter version used for messages between the Rf Control RA and the CDF. See Diameter 3GPP configuration properties.

Vcb0

 
ExtensionAvpSet

The diameter extension AVP configuration profile. See Configuring Extension AVPs for more information on how to add extension AVPs.

DiameterExtensions/Charging

 
ExtensionAvpSetPollTime

The time (milliseconds) between checking for configuration changes in the extension AVP profile (as indicated by the ExtensionAvpSet parameter). Value may be 0 (don’t poll) or at least 1000L.

0L

 
IOClientWorkers

Number of IO threads serving outgoing connections. 0 use value of Runtime.getRuntime().availableProcessors()

0

 
ConnectTimeout

Timeout (milliseconds) to wait for an outgoing transport connection to be established

30000L

 
RequestTimeout

Timeout (milliseconds) to wait for a response before firing a Timeout event

2000L

 
ReconnectDelay

Delay (milliseconds) before reconnecting (RFC6733 timer Tc)

5000L

 
ForceReconnectAfterDPR

if true, always attempt to reconnect even if the server sent a DPR with Disconnect-Cause set to DO_NOT_WANT_TO_TALK_TO_YOU

false

 
ThreadPoolSize

Size of thread pool for decoding incoming diameter messages. -1 disable thread pool and use IO threads and 0 use value of Runtime.getRuntime().availableProcessors()

-1

 
DestinationRealm

Destination realm to use for sending messages, if not already set by client.

'opencloud'

 
DestinationHost

Destination host to use for sending messages, if not already set by client.

empty
Tip See Configuring Diameter Resource Adaptors for details on the Diameter configuration.

Rf Control RA Diameter Configuration

The ConfigurationProfile configuration parameter identifies the profile that contains additional configuration for the Rf Control RA and includes the Diameter configuration. The default value of the ConfigurationProfile parameter (RfControlDiameterConfiguration/client) means the client profile in the RfControlDiameterConfiguration profile table is used. The profile has the following fields.

Field Name Description Default Value 
OnDiskBufferDirectoryName

Name of directory that the SQLite database will store the records in when no CDF is reachable. The Rf Control RA requires write permission on the path specified and the path has to be present in the security-permissions in the resource-adaptor-jar.xml file.

'${rhino.dir.home}/rf-control'

 
MaxRecordsInMemoryQueue

Maximum number of records waiting to be written in the in-memory queue. 0 indicates the queue is limited by the memory available.

34000L

 
MaxDbCommitIntervalInMs

The interval (milliseconds) the Persist thread will wait, after successfully writing all records from the memory queue to the disk buffer.

5000L

 
DbErrorRetry

The interval (milliseconds) the Replay thread and the Persist thread will wait, before trying to access the disk buffer, after a previous access failure.

30000L

 
ReplayRunInterval

The time (milliseconds) the replay thread will wait, before trying to access the disk buffer, after sending all previous records to the CDF.

30000L

 
Product

The product name

OpenCloud Diameter

 
ProductVendorID

Vendor ID; must be 0 for IETF-specified applications, or an IANA-assigned private enterprise number.

19808L

 
ApplicationId

Diameter Application ID

3L

 
ApplicationVendorID

Diameter Application ID.

19808

 
Version

Version number to use in all Firmware-Revision AVPs generated by the Diameter Rf stack. Version must be a positive integer.

1

 
Host

Host to use in all Origin-Host AVPs. Host must be resolvable.

diameterclient

 
Realm

Realm to use in all Origin-Realm AVPs.

example

 
Peer Table

A valid XML document for peer table configuration.

 
<![CDATA[<?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE peer-table PUBLIC "-//Open Cloud Ltd.//DTD Diameter Peer Table Configuration 1.1.0//EN" "http://www.opencloud.com/dtd/diameter-peer-table-1.1.0.dtd">
     <peer-table>
     <default-options>
         <option>
             <option-name>TCP_NODELAY</option-name>
             <option-type>java.lang.Boolean</option-type>
             <option-value>true</option-value>
         </option>
     </default-options>
     <peer connectAtStartup="true">
         <uri>aaa://RfCDF:5898;transport=tcp</uri>
         <address>127.0.0.1</address>
         <option>
             <option-name>TCP_NODELAY</option-name>
             <option-type>java.lang.Boolean</option-type>
             <option-value>false</option-value>
         </option>
     </peer>
 </peer-table>]]>
 
Realm Table

A valid XML document for realm table configuration.

 
<![CDATA[<?xml version="1.0" encoding="UTF-8"?>
         <!DOCTYPE realm-table PUBLIC "-//Open Cloud Ltd.//DTD Diameter Realm Table Configuration 1.0//EN" "http://www.opencloud.com/dtd/diameter-realm-table-1.0.dtd">
         <realm-table>
             <realm>
                 <realm-name>opencloud</realm-name>
                 <application-route>
                     <application>
                         <application-id>3</application-id>
                         <vendor-id>0</vendor-id> <!-- optional, default is zero -->
                     </application>
                     <action>LOCAL</action>
                     <peer-ref>
                         <hostname>RfCDF</hostname>
                         <metric>1</metric>
                     </peer-ref>
                 </application-route>
             </realm>
             <default-route>
                 <peer-ref>
                     <hostname>RfCDF</hostname>
                     <metric>1</metric>
                 </peer-ref>
             </default-route>
         </realm-table>]]>
 
PeerPort

Port of remote Diameter peer

5898

 
PeerHost

Host of remote Diameter peer

CDF

 
PeerConnectAtStartup

Whether to connect to the remote peer at startup. must be true or false

true

 
Action

Must be LOCAL for this version of the RA

LOCAL

 
Transports

Transport(s) to listen on. Values can be tcp, sctp, or tcp,sctp

tcp

Configuration for Multiple CDF Nodes

Failover between CDF nodes is supported by the Diameter Rf stack. You configure the Rf Control RA by creating realm and peer tables in the Rf Control RA Diameter Configuration appropriate for your deployment. For further information on configuration and diameter stack routing see:

Previous page Next page