RTP Relays Made Container Boundaries Easier to Control

Anchoring media at a deliberate boundary reduced the number of private addresses that leaked into SDP and simplified firewall policy.

By Reaz Romen✓ Site verified

Lab period October 2025 Published 2024-05-07 1 min read

Lab Note. Reconstructed in 2026 as a technical lab note from the 2025 voice, telecom and infrastructure study period. The archive date indicates the period covered; the current site publication date is shown separately.

Containerized PBX stacks become confusing when every component advertises an address from its own network namespace. SIP can be fixed with header rewriting and still leave RTP pointed at an unreachable private address.

A media relay gives the architecture a deliberate anchor. Endpoints send media to addresses owned by the relay, and the relay forwards between legs. That makes the SDP path predictable and keeps media policy in one place.

The trade-off is that the relay now sits directly in the media path, so capacity, port ranges and monitoring matter. It also does not fix signalling mistakes automatically. I still need correct dialog routing and a consistent view of which addresses are public, private and container-internal.

The value was not that relaying is always better. It was that the network boundary became explicit instead of being discovered accidentally through broken audio.