Where Does Kamailio Store Config and Data?
Kamailio keeps its main config in /etc/kamailio on Linux packages, with users in external databases and logs through syslog by default.
Last updated
Kamailio is config plus database with no log file of its own. The main cfg anchors /etc with helpers for control tools, TLS and dispatch. Subscribers live in external databases provisioned by control utilities. Logs flow to syslog unless an admin splits them out.
That trio shapes every task. Back up the config directory whole. Manage users through database tools rather than files. Hunt logs in the system log first and custom files only after confirming a facility rule exists.
Where Kamailio stores this, by platform
/etc/kamailio/kamailio.cfg
Main routing config with control-tool, TLS and dispatcher companions in the same directory. Source installs use the local etc twin. Override per launch with the file flag.
/etc/kamailio/kamctlrc
External subscriber database under the kamailio schema with paired users from the dbctl tool. Enabled through config defines for MySQL, auth and location storage. No embedded files to back up.
Frequently asked questions
How do I back up Kamailio config?
Copy /etc/kamailio/kamailio.cfg with kamctlrc and TLS helpers beside it. Override files load through the -f flag. Dispatcher lists and local includes sit in the same directory with documented fallbacks.
Where are Kamailio subscriber accounts?
They live in MySQL or compatible databases under the kamailio schema, created by the dbctl tool with paired read-write users. The config points at them through URL settings with auth and location defines. No embedded database exists to copy.
Where are Kamailio logs?
Check the system log first. Kamailio logs to syslog by default with no fixed file of its own. Custom log files need a facility plus a syslog rule, which is admin convention rather than package behavior. Debug mode writes to stderr instead.
Notice an outdated path? Let us know.