Skip to content
Platform Documentation

Call Logs Database

The Call Logs Database settings (System Preferences) define the MySQL database used for communications logs (pbxlogs): credentials services use to write call detail records, queue activity, and related events, and the connection the Manager UI uses to read that data for reports, grids, CRM timelines, and analytics.

Write path

The write fields (host, database name, user, password) are what recording services use to store data in MySQL. Queue log data uses the same connection. Use Test Connection to verify reachability and credentials from the Manager host.

Reporting (read) path

By default, reporting uses the same MySQL server and credentials as the write path. This is appropriate for most deployments.

Choose Separate MySQL host or replica when you want the Manager to run reporting against another host (for example a read replica) so heavy reporting does not compete with write load on the primary database server. Enter the reporting host, database name, user, and password, then use Test Connection for that path before saving.

When reporting is set to the same database as writes, the product keeps the stored reporting parameters aligned with the write credentials on save.

Ports and remote hosts

If the database listens on a non-default port, include it in the host field (for example db.example.com:3307) where your deployment expects host:port format.

See CDR for CDR retention and reporting practices.