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.
来源
- 内容摘要
- sha256:0457bf114748999273e7f053a4837b34cf5b5971d95d6e7229d44054551f06c4
- 发布时间
- 2026-11-10T10:12:26Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/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
此版本的引用
oci://hub.aggrega.ai/component/core/messaging/livekit-sip:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| metrics_enabled | boolean | false | 否 | 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. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| sip_port | integer (min 1024, max 65535) | 5060 | 否 | 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 | 否 | 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 | 否 | 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 | 否 | 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 | 否 | Bridge log verbosity. |
| engine_version | string | v1.12.0 | 否 | Bridge container image tag. Selects the image tag on container targets. |
| compute | object | — | 否 | — |
| overrides | object (open) | — | 否 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | 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 | — | 是 | 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 | — | 否 | How the published address is spoken to — `sip`, so a consumer directs call signalling at it rather than an HTTP request. |
| metrics_endpoint | string | — | 否 | 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 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
media_server
- 选择器
- component.aggrega.ai/category=messaging, component.aggrega.ai/type=server
- 注入
- env
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | 是 | env | 是 | 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
- 选择器
- component.aggrega.ai/category=datastore, datastore.aggrega.ai/engine=kv
- 注入
- env
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | 否 | file | 是 | 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. |
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
未声明附加槽位。
自注入允许列表
env
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- 使用使用套接字 «media_server»
component.aggrega.ai/category=messaging, component.aggrega.ai/type=server
附加槽位:credential
- 使用使用套接字 «state_store»
component.aggrega.ai/category=datastore, datastore.aggrega.ai/engine=kv
附加槽位:server_ca
被使用
使用套接字 «media_server»
使用套接字 «target_messaging»
使用套接字 «upstream»
使用套接字 «forward_target»
使用套接字 «scrape_target»
使用套接字 «store»
适用于
适用于
适用于
适用于
适用于
适用于
适用于
实现