Operations on KubeVoIP Docs

PostgreSQL

Mon, 01 Jan 0001 00:00:00 +0000

KubeVoIP requires a PostgreSQL database and a standard connection Secret with host, port, dbname, user, and password.

The operator runs forward database migrations automatically during reconciliation. PostgreSQL stores route data, dial policies, subscriber hashes, registrations, trunk metadata, and digest HA1 values. HA1 is credential-equivalent for its SIP realm.

Secrets

Mon, 01 Jan 0001 00:00:00 +0000

KubeVoIP reads Secrets only in the operator installation namespace. SIP user passwords, trunk digest credentials, caller ID values, and database credentials should stay out of Git and ConfigMaps.

Rendered ConfigMaps, statuses, Events, and logs must not expose raw passwords or digest HA1 values.

Production setup

Mon, 01 Jan 0001 00:00:00 +0000

The quickstart is small on purpose: it creates a test PostgreSQL Deployment, two demo users, one internal dial policy, and two routes. In production, keep the same resource model, but replace the demo pieces with durable infrastructure and real credentials.

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Start with resource status:

kubectl -n telephony get networkprofile,sipgateway,mediarelay,asteriskpool,sipuser,siptrunk,callscope,dialpolicy,callroute
kubectl -n telephony describe sipgateway main
kubectl -n telephony logs deployment/kubevoip-kubevoip

For one-way audio, check RTPengine Service addresses, firewall rules, and RTP port forwarding. SIP and RTP public ports must match the private ports.