In this section:
The Call Accounting Manager (CAM) generates Call Detail Records (CDRs) and supports accounting events logging to the . The provides the ability to map CDR fields and other input parameters to Remote Authentication Dial In User Service (RADIUS) attributes (standard as well as vendor-specific attributes) and send to the appropriate RADIUS server.
supports to configure one remote server per for the purpose of authenticating users from this server using RADIUS protocol. The username and encrypted password are sent to the remote RADIUS server in an ACCESS_REQUEST packet. The user is allowed/denied access to the SBC based on the response from the RADIUS server.
users are currently segregated into the following groups which define the privileges of each user. Access to data/commands is allowed/prevented based on the group of the user who is trying to acquire the access.
Since the RADIUS protocol does not provide a means to assign users to a group, the implementation currently hard codes every RADIUS authenticated user to the Administrator group.
For detailed information on RADIUS authentication, refer to Configuring SBC for RADIUS Authentication.
As calls traverse the , Call Detail Records (CDRs) are generated and stored in
/var/log/sonus/evlog/evlog directory. You can view these CDR by looking at files with the “.ACT” extension. It is useful to view these ACT logs during call debugging (to get the originating trunk group, calling and called numbers, codec used, etc.).
You may also view billing records (and other logs) from the EMA Platform Mode. Refer to Administration - Accounting and Logs for more information.
When downloading billing records (or other logs), you must use port 2024 to SFTP files off of the .
This section describes the ASCII and streaming Call Detail Record (CDR) format.
Various elements such as GSX 9000, PSX, and use many of the same CDR fields. Because of this, some fields in the “Accounting Records” table below do not apply to call details, but instead simply indicate pass-though type messages (for example, ISUP and PSTN fields).
|The “Service Group” object is not applicable to . Any references to “Service Group” must be mapped to “Trunk Group”.|
For more information on known limitations, refer to the applicable release notes at SBC Release Information page.
The CAM version of release V06.00.00 is 85.00.00 (major CAM version is 85, minor CAM version is 0, special CAM version is 0). The associated hex format of the CAM file version is "00550000" as shown in below header example.
Sonus Networks, Inc.00000000FF600000550000000000000060V06.00.00 00000000000000000000000000000000000ACT2014112715113200000000000000.
Every event log file, including accounting logs, contains a file header. This header consists of a 128-character string terminated by a carriage return. Each field in the event log file header is defined in the following table:
The one line footer, below, is appended to each log file (including accounting logs) when the file is closed under controlled conditions.
DDMMYYYY HHMMSS: File administratively closed.
Controlled conditions include CLI commands (for example,
set oam eventLog
acct rolloverAction...) and automatic roll-overs when maximum file size is reached.
When an uncontrolled file closure occurs, such as an switch-over or system failure, this footer may not be present.
If the CDR server is configured, transfers the files through SFTP to the configured destination.
To create the CDR server, use the following command syntax:
% set oam accounting cdrServer admin [primary | secondary] connectionTimeout <numeric: 15 to 600 seconds> filePrefix <name of SBC> ipAddress <ip address> password <password for ftp user> path <directory to ftp to> transferTimeout <numeric: 15 to 600 seconds> username <username of ftp user>
admin@SBC01> config admin@SBC01% set oam accounting cdrServer admin primary connectionTimeout 15 filePrefix SBC01 ipAddress 10.10.211.10 password sonus path /export/home/SBC01ACTrecs/ transferTimeout 15 username root admin@SBC01% commit admin@SBC01% quit admin@SBC01> show table oam accounting cdrServer admin FILE CONNECTION TRANSFER TYPE IP ADDRESS USERNAME PASSWORD PATH PREFIX TIMEOUT TIMEOUT -------------------------------------------------------------------------------------------------------------- primary 10.10.211.10 root $3$qaO71mBy8l8= /export/home/SBC01ACTrecs/ SBC01 15 15 [ok][2013-10-02 06:14:49] admin@SBC01>
Initially, the accounting field is not set to ftp or automatically roll over. Use the following command to view Rollover setting for accounting (See "acct" row in the example):
To create the accounting file rollover and ftp, use the following command syntax:
% set oam eventLog typeAdmin acct rolloverStartTime <CCYY-MM-DDTHH:MM:SS> rolloverInterval <number of seconds between each file rollover> rolloverType repetitive rolloverAction start where 'T' in 'DDTHH' is a constant used to indicate the Time follows.
View CDR Server status using the following command:
admin@SBC01> show table oam accounting cdrServer status SUCCESSFUL FAILED PENDING TYPE STATE PROGRESS TRANSFERS TRANSFERS TRANSFERS ------------------------------------------------------------- primary active done 3 0 0 [ok][2013-10-02 07:27:19]
Verify that the files were transferred to the FTP server by logging in to the CDR server and executing the following command:
ftp server: root@hostname # pwd /export/home/SBC01ACTrecs root@hostname # ls -l total 708 -rw-r--r-- 1 root other 346730 Oct 2 06:45 SBC01.20131002064500.1000022.ACT -rw-r--r-- 1 root other 175 Oct 2 07:00 SBC01.20131002070000.1000023.ACT -rw-r--r-- 1 root other 175 Oct 2 07:15 SBC01.20131002071500.1000024.ACT root@hostname #
Execute the following command to view the successful and failed CDR file transfer:
% show table oam accounting cdrServer status SUCCESSFUL FAILED PENDING TYPE STATE PROGRESS TRANSFERS TRANSFERS TRANSFERS --------------------------------------------------------- primary active done 2 0 0 secondary standby idle 0 7 0
The RADIUS application uses standard attributes from the RADIUS when possible. For CDR fields that cannot be mapped to the standard attributes, vendor-specific attributes are defined. The allows instances of the standard attributes in Accounting request message as per following table:
accounting records may be sent to three different locations:
The application maintains a configurable maximum of up to 1024 accounting files. Once the configured limit of files is reached, the application deletes the oldest files first to accommodate the new files.
When accounting file names reach the maximum value of 1FFFFFF.ACT, the next file name rolls over to 1000001.ACT. Use the “Rename Open Files” flag to rename the most recent accounting file with the ”ACT.OPEN” extension. This flag is accessible from the EMA at “System Configuration” > “CDR and Servers” tab.
The Global Charge Reference (GCR) feature allows correlation of calls across networks where the calls are originated from and terminated at different third-party devices. The GCR field is populated in the CDRs of the SBC if the GCR is received in a gateway protocol message from a GSX9000.
The GSX9000 receives or generates the GCR parameter through an ISUP parameter. The GCR is used in conjunction with SIP call-id’s to associate calls that interwork between SIP and ISUP protocols across multiple network devices.
RADIUS is a standardized protocol for supporting Authentication, Authorization, and Accounting (AAA) management in a distributed client-server architecture. The acting as a RADIUS client can send call-accounting records to an external RADIUS server. For a description of Sonus CDR to RADIUS VSA field mapping, refer to Managing Billing Records.
The following message types are supported by RADIUS protocol:
The accounting request and its response for a transaction methodology is described below.
The accounting-request contains the Accounting-Status-Type with the value "Stop". The primary purpose of this data is to bill the user. The data is also used for statistical purposes and for general network monitoring.
To configure up to three RADIUS servers per , refer to Accounting - CLI.
To configure the for RADIUS authentication, refer to Configuring SBC for RADIUS Authentication.
The SBC includes the ability to rename a currently-open accounting file using a known suffix to make it easily identifiable by external applications. To activate this feature, simply enable the flag “Rename Open Files” using EMA GUI or CLI.
CLI syntax example:
% set oam eventLog typeAdmin acct renameOpenFiles enable
Once this flag is enabled, on the next accounting file open activity, the suffix .OPEN is appended to the filename using the format <shelf><sequence number>.ACT.OPEN (currently open files are not affected).
For example, as accounting file 1000099 is created with this feature already enabled, the file is named “1000099.ACT.OPEN”.
|If a file closes due to a rollover, logging shutdown or system shutdown, it is renamed to the original format: <shelf><sequence number>.ACT.|
For configuration details, refer to:
The acting as a P-CSCF or IBCF supports Rf interface-based offline billing in compliance with standard IMS as well as file-based and stream-based CDRs. The SBC can select either CDR/streaming-based charging or Rf Interface depending on whether the system-wide flag, enableRfApp, is enabled or not. Refer to Signaling - Global - CLI or Signaling - Diam Sig Controls for configuration details.
The Diameter node supports both Rf application along with the existing Rx application. The Diameter node uses "Route Table" to find peer for outbound request based on destination realm and application.
The supports transferring the call accounting files (.
ACT) to the CDR server through a user configured port. The also supports using the Secure Shell (SSH) public keys instead of password to authenticate with the remote CDR server.
The following parameters are added in CDR server configuration to set remote port and ssh key based authentication:
User can either use the existing username/password or the SSH public key to authenticate with the remote CDR server. The parameter
To generate a new SSH public key, execute the following command:
% request oam accounting cdrServer admin primary generateSshPublicKeys
The generated SSH public key must be installed on CDR server to use ssh key based authentication from SBC. The SSH public key must be copied to the remote CDR server file
/home/<user>/.ssh/authorized_keys. If the private key is compromised, the key must be re-generated. Once the key is re-generated, the CDR server must be updated with the new key.
% set oam accounting cdrServer admin primary cdrPort 2024
Use the SSH public key for CDR server authentication to accomplish the following actions:
To enable SSH key based authentication, execute the following command:
% set oam accounting cdrServer admin primary useSshKeyFile Enable
To generate a new SSH public key, execute the following command:
% request oam accounting cdrServer admin primary generateSshPublicKeys result success reason ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDclSOlVfVmmhatw5bDQRk7AaYvCRUUfHHbSvkCBb4T8zYdJ8JNw15rMSKk9hEkVdtEEZRJU4Q97C+3LbPknZrIMM+zmSRYmh2/LkGAlydSJ+sPe9i7zWFOLYeA3gitaKJSPgSjdb4WGgDq686Ei4yup9xYDbT8wAcosQsf3tfbqH2GetNJ8tAs3KjRi7FPhH1hHdXVyH0yW1mdGlMYvoFUeFCRjhE81oJhy2jMTJD9T3eQiJo4NZQZYOgALMQPi8fxaAgnuWmvrejNTn/PgRyGpQEs7HFHkX5zHW5M74PU/Z3S3Y2uSZlYrCQRf9Y2mUiK5R40bjsKz4TqIP5LfzhX [ok]
The SSH public key is copied to the remote CDR server file
For configuration details, refer to Accounting - CLI.