Component
core/messaging/livekit-sip
A LiveKit SIP bridge — the service that carries a telephone call into and out of a realtime room. It answers SIP signalling on one port, which it binds for datagram and stream transport alike, negotiates the call there, and then carries the call audio over RTP on a contiguous range of UDP ports it draws a per-call socket from. The room side of the call runs over the bridge's own client session with the media server, and the state of a call in progress lives in the Redis-compatible store the bridge and that server share, which is also how the requests that set a call up pass between them. Wire here when a SIP trunk is terminated inside the cluster and those calls are joined to rooms it already runs, rather than routing the conversation through a carrier's own application platform. Consumers receive the bridge's in-cluster host, its signalling port and the protocol that port speaks; the token-signing secret is the credential the connection to the media server carries and is never published on the topology, and the public key identifier arrives over that same edge, so the halves of one key pair cannot drift apart. Realized by a Helm Recipe that synthesizes a Deployment and a ClusterIP Service over the upstream image and declares no volume: the bridge holds no durable disk. The RTP range carries call audio only where the pod uses the node's own network and the range is open to the trunk on the node's firewall. With `values.metrics_enabled` true the Recipe turns on the bridge's metrics, on a port of their own that checks no caller, and publishes their address as `metrics_endpoint`; false, that key is empty.
Köken
- İçerik özeti
- sha256:0457bf114748999273e7f053a4837b34cf5b5971d95d6e7229d44054551f06c4
- Yayımlanma
- 2026-11-10T10:12:26Z
- İmzalama kimliği
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
İmza
- Resmiapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:40b012f2a7a1df4b3aff4b1b10192d6463192e84f4d2debf2ded1caf7123f082
Bu sürümdeki referans
oci://hub.aggrega.ai/component/core/messaging/livekit-sip:1.0.0Geliştirici parametreleri
Geliştiricinin Aggregate'te ayarladığı değerler.
| Ad | Tip | Varsayılan | Zorunlu | Açıklama |
|---|---|---|---|---|
| metrics_enabled | boolean | false | hayır | Turns on the bridge's own metrics, in the Prometheus format, on a port of their own, 6789, and publishes their address as `metrics_endpoint`; while false that key is empty. The metrics port checks no caller, so anything that reaches it can read them. |
Operatör boyutlandırması
Operatörün her ortam için ayarladığı altyapı boyutlandırması.
| Ad | Tip | Varsayılan | Zorunlu | Açıklama |
|---|---|---|---|---|
| sip_port | integer (min 1024, max 65535) | 5060 | hayır | SIP signalling port. The bridge binds it for UDP and for TCP together and announces it in the SIP headers it sends, so both transports of the trunk arrive on one number. Most operators should omit this and let the Recipe assign the default (5060). |
| health_port | integer (min 1024, max 65535) | 8080 | hayır | Port carrying the bridge's own health endpoint, which answers with the load state of the process. The Recipe probes it, so leaving it at the default keeps the readiness and liveness checks working; it is a container port and the Service does not publish it. |
| rtp_port_start | integer (min 1024, max 65535) | 10000 | hayır | First port of the contiguous UDP range the bridge draws a per-call RTP socket from. The range sizes how many calls one replica carries at once, since each call holds a socket in it for its duration. The ports in it are configuration the bridge reads rather than ports the component declares — they are not container ports and no Service fronts them — so they carry call audio where the pod uses the node's own network and the range is open to the trunk on the node's firewall. |
| rtp_port_end | integer (min 1024, max 65535) | 20000 | hayır | Last port of the contiguous UDP RTP range, inclusive, and greater than rtp_port_start. Narrow the range to the number of concurrent calls a replica is sized for rather than leaving the full default span open on the node. |
| log_level | string (debug | info | warn | error) | info | hayır | Bridge log verbosity. |
| engine_version | string | v1.12.0 | hayır | Bridge container image tag. Selects the image tag on container targets. |
| compute | object | — | hayır | — |
| overrides | object (open) | — | hayır | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Çıktı sözleşmesi
Bu bileşenin uses topolojisi üzerinden tüketicilere yayımladığı değerler.
| Ad | Tip | Varsayılan | Zorunlu | Açıklama |
|---|---|---|---|---|
| host | string | — | evet | In-cluster DNS name of the Service carrying SIP signalling. A consumer directs call signalling at this name together with `port`; the RTP range is a separate path and is not published here. |
| port | integer | — | evet | Port the bridge answers SIP signalling on. It carries the signalling port an operator set, never the health port or one of the RTP ports. |
| protocol | string | — | hayır | How the published address is spoken to — `sip`, so a consumer directs call signalling at it rather than an HTTP request. |
| metrics_endpoint | string | — | hayır | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:6789/metrics`. Empty while values.metrics_enabled is false. |
Uses soketleri
Bu bileşenin üzerinden bağlandığı bağımlılık soketleri. Bir soket üzerinden kurulan her bağlantının hedefi, soketin etiket seçicisini karşılamalıdır ve her bağlantı, soketin bildirdiği yuvalarda bir ek taşıyabilir. Aggregate'in veya Release'in soket üzerinden kurduğu her bağlantı, zorunlu bir yuvayı doldurmakla yükümlüdür.
media_server
- Seçici
- component.aggrega.ai/category=messaging, component.aggrega.ai/type=server
- Enjeksiyon
- env
Bu soket üzerinden kurulan her bağlantının doldurabileceği yuvalar
| Yuva | Seçici | Zorunlu | Enjeksiyon | Hassas | Açıklama |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | evet | env | evet | Signing secret paired with the api_key identifier this connection carries. Attach the same credential the media server holds: the bridge authenticates to that server with this pair, so two different secrets leave the bridge unable to open a session. |
state_store
- Seçici
- component.aggrega.ai/category=datastore, datastore.aggrega.ai/engine=kv
- Enjeksiyon
- env
Bu soket üzerinden kurulan her bağlantının doldurabileceği yuvalar
| Yuva | Seçici | Zorunlu | Enjeksiyon | Hassas | Açıklama |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | hayır | file | evet | Optional authority the bridge checks the store's certificate against while the store publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and names the file in the bridge's store settings. The build halts on a server_ca publishing no Secret name, and on one wired to a store served without TLS. Fill it with core/referenced-secret. |
Ekleme yuvaları
Bir Feature'ın bu bileşene eklendiği adlandırılmış bağlama noktaları. Bir yuvanın seçicisi, onu hangi Feature'ın doldurabileceğini sınırlar ve inject listesi, Feature'ın malzemesinin nasıl iletilebileceğini belirtir. Zorunlu bir yuva, her örnekte, örnek üzerindeki veya onun üstündeki bir kapsamdaki bir ek aracılığıyla bağlanmalıdır, hassas bir yuva ise gizli malzemeyi işlemek üzere bildirilmiştir. Bir Feature, hiçbir yuvanın bildirmediği bir ad altında da eklenebilir.
Ekleme yuvası bildirilmemiş.
Kendi kendine enjeksiyon izin listesi
env
İlişkiler
Diğer yayımlanmış varlıklara giden ve onlardan gelen tipli kenarlar. Yayımlanmış bir hedefi olmayan bir başvuru, bağlantı yerine kopuk bir kenar olarak gösterilir.
Kullanır
- kullanır«media_server» soketini kullanır
component.aggrega.ai/category=messaging, component.aggrega.ai/type=server
Ekleme yuvaları: credential
- kullanır«state_store» soketini kullanır
component.aggrega.ai/category=datastore, datastore.aggrega.ai/engine=kv
Ekleme yuvaları: server_ca
Kullananlar
«media_server» soketini kullanır
«target_messaging» soketini kullanır
«upstream» soketini kullanır
«forward_target» soketini kullanır
«scrape_target» soketini kullanır
«store» soketini kullanır
uygulanır
uygulanır
uygulanır
uygulanır
uygulanır
uygulanır
uygulanır
uygular