Skip to main content

LiveKit SIP (livekit-sip)

SIP gateway that brings phone calls into LiveKit rooms (inbound INVITE, outbound CreateSIPParticipant, transfer TransferSIPParticipant by SIP REFER). It talks to LiveKit Server through Redis only; Navin Enterprise creates its trunks and dispatch rules through the LiveKit API.

Generated from catalog/services/livekit-sip.yaml: do not edit by hand.

Summary​

Version1.22.0
Useinstall and configure
Layerfunctional (AI catalog)
CategoryAI serving
Installation methodspodman
External connectionno
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentlivekit-sip

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
container imagedocker.io/livekit/sipv1.22.0Apache-2.0image key sip, used by livekit-sip, digest sha256:ccca91b38e57b0565d965ee8e7db698f0d7fd1a44a4018c4cacae14eb95bed10

Images are pinned by tag in the descriptor, and by digest when the descriptor declares one (the offline bundle then refuses a pulled image that does not carry it); the digest is recorded in the mirror of the Manager when the offline bundle is imported, and every pull or load is checked against it.

Supported systems and architectures​

MethodOperating systemsArchitectures
podmanRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64, aarch64 (not restricted by the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

  • at least 2 CPU (warning, cpu).

Network and ports​

ComponentPort namePortOpened in the host firewall
livekit-sipsip5090/udpyes
livekit-sipsip-tcp5090/tcpyes
livekit-siprtp20000-29999/udpyes
livekit-siphealth8590/tcpno
livekit-sipmetrics6790/tcpyes

Kernel parameters​

ParameterValue
net.core.rmem_max5000000
net.core.wmem_max5000000

Services and connections needed​

Details and resolution: see Dependencies.

Installation methods and modes​

MethodDefaultWhat the method uses
podmanyesthe container images of the descriptor, run by Podman under systemd

Components​

ComponentKindInstallation methodsPorts
LiveKit SIP (livekit-sip)workerpodman5090/udp, 5090/tcp, 20000-29999/udp, 8590/tcp, 6790/tcp

Single instance (single) (default)​

One SIP gateway.

What the mode deploys:

ComponentPlacement
livekit-sipmin 1, max 1

Redundant (redundant)​

Several SIP gateways on the same Redis, Kamailio spreads the calls between them.

What the mode deploys:

ComponentPlacement
livekit-sipmin 2, recommended 2

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select LiveKit SIP. The card shows the licence Apache-2.0 and the dependencies the installation needs.

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: single (default), redundant. Each mode deploys the components listed in Installation methods and modes.

  4. Bind the dependencies. On the Bindings step, choose for each dependency (livekit, redis) Install with the platform or Use an existing connection; an optional dependency can stay on No binding.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters). Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services.

High availability​

Clusternative (native)
High availabilityredundancy (redundancy)
Failoverclient side (client)
Replicationshared store (shared-store)
Quorumnone (none)
Discoveryregistry (registry)
Entry pointany node (any-node)
Official documentationhttps://docs.livekit.io/transport/self-hosting/sip-server/
Referenceshttps://github.com/livekit/sip

Prerequisites​

PrerequisiteMust be highly availableModesDescription
redisyesredundantHighly available Redis shared with LiveKit Server.

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
singlestandalone (standalone)single (single)-1One gateway, no fault tolerance.
redundantha (ha)active-active (active-active)-2Several gateways registered on the Redis bus; Kamailio sends each new call to a gateway its OPTIONS probe sees up.

Notes​

  • A call lives on one gateway: the loss of that gateway cuts its calls in progress; new calls go to the other gateways.

Configuration parameters​

Network​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
SIP port (sip_port)port5090-nonoyesSIP signalling port, UDP and TCP (reached by Kamailio and Asterisk).
First RTP port (rtp_port_start)port20000-nonoyesStart of the UDP media range.
Last RTP port (rtp_port_end)port29999-nonoyesEnd of the UDP media range (keep the firewall rule in line).
Health port (health_port)port8590-nononoHTTP health endpoint (200 ready, 429 under load, 503 down), local to the host.
Metrics port (metrics_port)port6790-nononoPrometheus port.
NAT external address (external_ip)string(empty)^$|^[0-9]{1,3}(\.[0-9]{1,3}){3}$nonoyesPublic IPv4 address announced in SIP and SDP when the host is behind a one to one NAT (nat_1_to_1_ip); empty: the address of the host.
LiveKit URL (livekit_url)string(empty)-nononows:// or wss:// URL of LiveKit Server (its load balancer in the distributed mode); empty: the first server of the livekit binding.

Security​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Hide from scanners (hide_inbound_port)booltrue-nononoDrop an INVITE that no trunk or dispatch rule accepts instead of answering it.

Capacity​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Calls per instance (max_active_calls)int0min 0, max 100000nononoCalls an instance accepts before it reports itself loaded; 0: CPU only (max_cpu_utilization 0.9).

Dependencies​

For each active dependency the Manager takes the first of: the binding chosen in the wizard; a service of the same installation that provides it; a service already installed in the cluster; the only connection of the expected type. Otherwise an optional dependency stays unbound, and a required one is added to the installation in its default mode (the column below names the catalog service added).

BindingProvided byConnection typeEndpointOptionalWhen nothing is boundDescription
livekitlivekit-signalnolivekit is added to the installationLiveKit Server of the rooms: API key pair and WebSocket URL (its redis_bus must be on).
redisredisredisredisnoredis is added to the installationThe Redis of LiveKit Server: message bus and SIP session state.

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
sipsiplivekit-sip5090 (sip_port)-----

Commands​

CommandComponentTargetDescription
Health (health)livekit-sipevery hostHealth of every gateway (OK, under load or down).
Recent logs (logs)livekit-sipchosen hostLast lines of the gateway journal.

Health checks​

Liveness (per instance)​

ComponentCheckDetails
livekit-sipHTTP http://127.0.0.1:{{ config.health_port }}/Expected 200, 429; 30 retries; interval 2 s; timeout 3 s

Preflight checks​

CheckTypeMeaningSeverityComponents
sip_port_freeport_free {"param": "sip_port"}port 5090 free on the hostblockingevery component
cpucpu_count {"min": 2}at least 2 CPUwarningevery component

Uninstall​

Paths removed when the data is purged: {{ paths.log }}.

  • Metrics: http://{{ host.fqdn }}:{{ config.metrics_port }}/metrics

Upstream documentation​