Accounting Settings
The Oracle Enterprise Communications Broker offers support for RADIUS, an accounting, authentication, and authorization (AAA) system. In general, RADIUS servers are responsible for receiving user connection requests, authenticating users, and returning all configuration information necessary for the client to deliver service to the user.
You can configure your Oracle Enterprise Communications Broker to send call accounting information to one or more RADIUS servers. This information can help you to see usage and QoS metrics, monitor traffic, and even troubleshoot your system.
Configure an Accounting Server
Use the following procedure to configure an accounting server to receive accounting detail from the Oracle Enterprise Communications Broker (OECB). You can also edit and delete existing accounting servers with this procedure,.
- Network Access Server (NAS) IP address (the IP address of the OECB SIP proxy).
- NAS ID. If you enter a value, the OECB sends the NAS ID to the remote server.
If you have more than one OECB pointing to the same accounting server, you can use the NAS ID to identify which OECB generated the record.
Configure Accounting
You can configure the Oracle Enterprise Communications Broker (OECB) to perform accounting tasks and send the information to multiple FTP push servers and accounting servers. Accounting information can help you to see usage and QoS metrics, monitor traffic, and troubleshoot the system.
FTP Push
In addition to local and RADIUS server storage, the Oracle Enterprise Communications Broker (OECB) can send accounting files to an FTP server. The information sent to the FTP server is the same as that stored locally.
Use FTP push to copy local CDR files to a remote FTP server on a periodic basis. You configure FTP push by defining push receivers with the login and FTP server credentials of the remote server. At the specified time interval (file rotate time), the OECB closes the current file and pushes the files that are complete and have not yet been pushed, including the just-closed file to the FTP server.
Push receiver configurations must include:
- Enabling the FTP push server
- The server’s IP address and port
- Remote path to the upload destination
- File name prefix
- Account login credentials
Multiple Push Receivers
OECB (OECB) supports up to five CDR push receivers for use with the local file storage and FTP push feature. For each receiver you configure, you can set the file transfer protocol that you want to use. (FTP or SFTP). The system uses the push receivers according to the priorities you assign by setting a 0 through 4 priority number to the server. 0 is the highest priority, and 4 (default) is the lowest.
Based on the priority level you set, the OECB uses the strategy that you set to select a CDR push receiver. If the highest priority push receiver selected using the strategy becomes unavailable, the OECB uses the strategy (hunt, round robin) to select another.
This feature is dynamically configurable. When you change the configuration, the OECB updates the list of push receivers if it has changed.
Secure FTP Push Configuration
You can configure the Oracle Enterprise Communications Broker (OECB) to securely log on to a push receiver using one of the following methods that creates a secure connection.
- Set the protocol parameter on the push receiver to SFTP.
- Configure a username and password.
- Leave the public-key parameter blank.
- Import the host key from the SFTP server to the OECB as a known-host key.
See "SSH Key Management" in the Configuration Guide.
- Set the protocol parameter on the push receiver to SFTP.
- Configure the username.
- Leave the public-key parameter blank, regardless of authentication type.
- Export the OECB's public key
with the
show security public-host-key rsa
command. - Append the OECB's public-key to the SFTP server's authorized_keys file.
- Import the host key from the SFTP server to the OECB as a known-host key.
See "SSH Key Management" in the Configuration Guide.
It is often difficult to determine whether the SFTP server uses its RSA key or its DSA key for its server application. For this reason, Oracle recommends that you import both the RSA key and the DSA key to the OECB to ensure a successful FTP Push.
It is also common for the SFTP server to run the Linux operating system. For Linux, the command ssh-keygen -e creates the public key that you need to import to the OECB. The ssh-keygen-e command sequence requires you to specify the file export type, as follows.
[linux-vpn-1 ~]# ssh-keygen -e
Enter file in which the key is (/root/.ssh/id_rsa/): /etc/ssh/ssh_host_rsa_key.pub
If you cannot access the SFTP server directly, but you can access it from another Linux host, use the ssh-keyscan command to get the key. An example command line follows.
root@server:~$ ssh-keyscan -t rsa sftp.example.com
Add an FTP Push Receiver
The Oracle Enterprise Communications Broker (OECB) supports configuring up to five FTP push servers to receive accounting files. Use the Push Receiver Add dialog located on the account-config page to access the parameters for creating a list of FTP push receivers.
- If you plan to use a public key for authentication to the push receiver, create public key profile. See "Configure Secure FTP Push with Public Key Authentication."
- Configure accounting. See "Configure Accounting."