What it does
When Diameter Rf charging is in use, the Rhino VoLTE TAS communicates with a CDF to deliver interim CDRs using Accounting Request (ACR) messages. If the communication with the CDF fails, ACR messages are held locally until it is restored.
Interim CDRs must be enabled to use Diameter Rf offline charging.
Configuration
The example for sentinel-volte-gsm-config.yaml and
example for sentinel-volte-cdma-config.yaml show example configuration
relevant to Diameter Rf offline charging in the sentinel-volte/charging/rf-charging section.
What you need
- 
❏ The release version of Diameter Rf to use with the offline charging system.
 - 
❏ The origin realm to use when sending Diameter Rf messages. This is the TAS’s realm.
 - 
❏ The destination realm to use when sending Diameter Rf messages. This is the offline charging system’s realm.
 - 
❏ The CDF peers' hostnames, ports, and transport protocols.
 
Setting up Diameter Rf based offline charging
I want to…
Use Diameter Rf offline charging
In the charging section,
add an rf-charging section with:
        rf-charging:
            diameter-rf:
                diameter-rf-release: Vcb0
                origin-realm: metaswitch.com
                destination-realm: metaswitch.com
                destination-peers:
                    -   destination-hostname: peer.metaswitch.com
                        port: 3868
                        protocol-transport: sctp
                        metric: 1
- 
The
diameter-rf-releaseto use. - 
The Diameter
origin-realmfor the Rhino VoLTE TAS. - 
The Diameter
destination-realmfor the offline charging system. - 
A Diameter
destination-peerslist that correspond to CDF servers. There must be at least one entry, and for each entry the following values must be set:- 
the
destination-hostnamefor the CDF - 
the
portfor the CDF - 
the
protocol-transportto use with the CDF. - 
the
metricto use for this CDF peer. 
 - 
 
You must ensure that all per-node-diameter-rf sections in the MMT cluster configuration are present and not commented out. The sections are located:
- 
for GSM deployments, in
mmt-gsm-vmpool-config.yaml - 
for CDMA deployments, in
mmt-cdma-vmpool-config.yaml 
          # Remove this if diameter-rf is disabled
          per-node-diameter-rf:
              diameter-rf-origin-host: mmt1.mmt.site1.mnc123.mcc530.3gppnetwork.org
Disable Diameter Rf offline charging
In the charging section,
remove or comment out the entire rf-charging section:
#        rf-charging:
#            diameter-rf:
#                diameter-rf-release: Vcb0
#                origin-realm: metaswitch.com
#                destination-realm: metaswitch.com
#                destination-peers:
#                    -   destination-hostname: peer.metaswitch.com
#                        port: 3868
#                        protocol-transport: sctp
#                        metric: 1
You must comment out any per-node-diameter-rf sections in the MMT cluster configuration, which are located:
- 
for GSM deployments, in
mmt-gsm-vmpool-config.yaml - 
for CDMA deployments, in
mmt-cdma-vmpool-config.yaml 
          # Remove this if diameter-rf is disabled
#          per-node-diameter-rf:
#              diameter-rf-origin-host: mmt1.mmt.site1.mnc123.mcc530.3gppnetwork.org
