Networking on KubeVoIP Docs

SIP on Kubernetes

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

SIP clients and trunks send requests to a SIPGateway. Kamailio authenticates callers, selects routes from PostgreSQL runtime data, and asks RTPengine to rewrite SDP for media relay. Calls can target registered SIP users, outbound trunks, or Asterisk application pods.

LoadBalancer networking

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

LoadBalancer mode lets Kubernetes or your infrastructure allocate addresses for SIP and RTP Services. If KubeVoIP cannot resolve an address yet, it reports a waiting condition until the Service ingress is available.

HostNetwork media mode

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

HostNetwork avoids Kubernetes Service NAT for media but binds RTPengine ports directly on selected nodes. The cluster operator must handle node selection, public addresses, firewall rules, and port conflicts.

Use this mode when media packets need to land directly on selected Kubernetes nodes instead of passing through a Service. It can be useful in environments where UDP Service behavior is hard to control, but it moves more responsibility to node placement and firewall configuration.