In this section:
The Call Accounting Manager (CAM) generates Call Detail Records (CDRs) and supports accounting events logging to the
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
/var/log/sonus/sbx/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.
SBC may insert non-ASCII characters in CDRs when messages are parsed in the initial INVITE.
Various
For GW-GW calls on the populateRemoteGsxInfoState
flag is enabled, the SBC logs billing information from the termination node.
For more information on known limitations, refer to the applicable release notes at SBC Release Information page.
Addtional references:
The CAM version of
Sonus Networks, Inc.00000000FF6000005C0000000000000128V08.00.00A020 0000000000000000000000000000ACT2019041215270400000000000000
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:
File Header Details
Field Offset | Field Length | Field Content |
---|---|---|
0 | 20 | ASCII OEM string, blank padded, (for example "Sonus Networks, Inc.") |
20 | 8 | Reserved |
28 | 2 | Old CAM File Version. Always "FF". |
30 | 2 | Hex offset to the Event Log Type, or the number of bytes from the beginning of the record to the beginning of the Event Log Type field (in the above example, "60"). |
32 | 2 | Reserved |
34 | 8 | New CAM File Version. This value is 005C0000, and consists of:
|
42 | 8 | Reserved |
50 | 4 | Hex offset to start of data. In this example, "0128". |
54 | 13 | Unable to show "metadata-from": No such page "_space_variables" software revision. In this example, "V08.00 .00". |
67 | 29 | Reserved |
96 | 3 | Event Log Type (same as file extension). In this example, "ACT". |
99 | 16 | File creation time. |
115 | 12 | Reserved |
127 | 1 | Header terminator (carriage return) |
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
typeAdmin
acct rolloverAction
...) and automatic roll-overs when maximum file size is reached.
When an uncontrolled file closure occurs, such as an
If the CDR server is configured, the
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>
An example to show the CDR server configuration and check the configuration is as follows:
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):
> show table oam eventLog typeAdmin MESSAGE ROLLOVER FILE RENAME DISK SYSLOG FILE FILE QUEUE SAVE FILTER START ROLLOVER ROLLOVER WRITE SYSLOG OPEN THROTTLE EVENT LOG SERVER REMOTE TYPE STATE COUNT SIZE SIZE TO LEVEL TIME INTERVAL ROLLOVER TYPE ACTION MODE STATE FILES LIMIT VALIDATION NO HOST ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- system enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled 5000 disabled server1 0.0.0. debug enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled server1 0.0.0. trace enabled 32 2048 10 disk info - 0 nonrepetitive stop default disabled disabled - disabled server1 0.0.0. acct enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled server1 0.0.0. security enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled server1 0.0.0. audit enabled 32 2048 10 disk info - 0 nonrepetitive stop default disabled disabled - disabled server1 0.0.0. packet enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled server1 0.0.0. memusage enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled server1 0.0.0. [ok]
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.
An example of the configuration and display of the accounting file rollover and ftp is as follows:
% set oam eventLog typeAdmin acct rolloverStartTime 2018-09-13T06:30:00 rolloverInterval 500 rolloverType repetitive rolloverAction start [ok][2018-08-13 12:58:11] [edit] admin@SBXUK11-1% commit Commit complete. [ok][2018-08-13 12:58:14] [edit] admin@SBXUK11-1% exit > show table oam eventLog typeAdmin MESSAGE FILE RENAME DISK FILE FILE QUEUE SAVE FILTER ROLLOVER ROLLOVER WRITE SYSLOG OPEN THROTTLE EVENT LOG TYPE STATE COUNT SIZE SIZE TO LEVEL ROLLOVER START TIME INTERVAL ROLLOVER TYPE ACTION MODE STATE FILES LIMIT VALIDATION ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- system enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled 5000 disabled debug enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled trace enabled 32 2048 10 disk info - 0 nonrepetitive stop default disabled disabled - disabled acct enabled 32 2048 10 disk major 2018-09-13T06:30:00-00:00 500 repetitive start default disabled disabled - disabled security enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled audit enabled 32 2048 10 disk info - 0 nonrepetitive stop default disabled disabled - disabled packet enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled memusage enabled 32 2048 10 disk major - 0 nonrepetitive stop default disabled disabled - disabled [ok]
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
Allowed Standard Attributes
Attribute Name | Attributes description |
---|---|
NAS-IP-Address | The IP Address of the Unable to show "metadata-from": No such page "_space_variables" generating accounting request. |
NAS -Identifier | The configured NAS Identifier for a given Unable to show "metadata-from": No such page "_space_variables" . When sending RADIUS accounting messages, the NAS-Identifier field is populated with the corresponding value configured for the RADIUS server to which message is sent. |
Acct-Status-Type | The type of accounting message sent by the Unable to show "metadata-from": No such page "_space_variables" . The Unable to show "metadata-from": No such page "_space_variables" uses the appropriate value of Acct-Status-Type corresponding to the CDR type to be generated.
|
Acct-Session-Id | Uniquely identifies accounting records for a given call. It is possible to match all accounting records for a given call when correlating call records. |
Acct-Session-Time | The number of seconds during which the user received service (duration of the call). |
Acct-Terminate-Cause | The class of termination cause. This value is derived from the disconnect reasons class value. |
The
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
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.
RADIUS Client-Server Diagram
To configure up to three RADIUS servers per
To configure the
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”.
For configuration details, refer to:
The
The
For more details, refer to Rf Interface Support page in the SBC Core Billing Guide section.
The
ACT
) to the CDR server through a user configured port. The The following parameters are added in CDR server configuration to set remote port and ssh key based authentication:
cdrPort
useSshKeyFile
generateSshPublicKeys
User can either use the existing username/password or the SSH public key to authenticate with the remote CDR server. The parameter useSshKeyFile
must be enabled to generate the SSH public key.
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.
The configured user must have access to /home/<user>/.ssh
for reading the public 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 /home/<user>/.ssh/authorized_keys
.
For configuration details, refer to Accounting - CLI.