Where Does OpenSIPS Store Config and Data?
OpenSIPS keeps its main config in /etc/opensips on Linux packages, with subscribers in external databases and logs through syslog by default.
Last updated
OpenSIPS mirrors its proxy sibling in storage philosophy. Config anchors the package etc tree with control-tool credentials beside it. Subscribers live in external databases provisioned by CLI schema commands. Logs default to syslog with file splits as local custom.
Prefix installs shift the whole tree under local etc while keeping internal shape. The CLI owns database creation with schema paths varying by prefix. Config check flags catch path mistakes before they reach production traffic.
Where OpenSIPS stores this, by platform
/etc/opensips/opensips.cfg
Main routing config with control-tool rc for credentials and engines. Prefix installs mirror under local etc. Validate with the config checker before restarts.
/etc/opensips/opensipsctlrc
External subscriber store under the opensips schema provisioned by CLI database commands. Connection URLs in config select the backend. Schemas ship in the share tree per prefix.
Frequently asked questions
How do I back up OpenSIPS config?
Copy /etc/opensips/opensips.cfg with the control-tool rc beside it. Prefix installs mirror the tree under local etc instead. The config checker validates paths before restarts, catching prefix mistakes early.
Where are OpenSIPS subscriber accounts?
They live in MySQL or Postgres under the opensips schema, provisioned by the CLI database commands with schemas from the share tree. Connection URLs in the config name the backend. No embedded store exists to archive.
Where are OpenSIPS logs?
Check syslog first. Logging defaults to the daemon facility with no fixed file of its own, matching its sibling proxy closely. Custom files need a facility split in syslog config, which is local convention rather than package default.
Notice an outdated path? Let us know.