Media Proxy
RTP relay, transcoding, and NAT traversal at carrier scale.
Media problems hide in plain sight: one-way audio, echo, clipping, and call drops that the SIP signaling logs show nothing about. Our media proxy service runs rtpengine clusters that handle RTP relay, SRTP-to-RTP transcoding, NAT traversal for endpoints behind enterprise and carrier-grade NAT, codec transcoding between G.711/G.729/Opus/AMR, and DTMF bridging across RF2833/in-band/SIP-INFO. We operate clusters in multiple regions so media hops stay minimal — a call between two users in Frankfurt shouldn't touch a server in London.
Features
SRTP ↔ RTP transcoding
Bridges encrypted and unencrypted legs transparently. Both sides see what they expect — the media proxy handles the key exchange.
NAT traversal
Symmetric RTP, STUN binding, and ICE-lite support handle enterprise and carrier-grade NAT without manual pinhole configuration.
Codec transcoding
G.711 μ/a-law, G.729, G.722, Opus, AMR-WB, and iLBC. Hardware transcoding available for high-volume deployments.
DTMF bridging
RFC 2833, in-band, and SIP INFO DTMF normalized between legs so IVRs receive digits regardless of what the endpoint sends.
Recording and tap
Per-call recording injected at the media layer without affecting call quality. Delivered to S3, GCS, or a server you specify.
Multi-region deployment
Clusters in your traffic regions so media paths stay local. Routing decisions made by the SBC based on endpoint geography.
Pricing
Custom pricing — scoped per deployment based on concurrent session count and codec mix.
Common questions
Related products & services
Ready to build on carrier-grade voice?
Talk to a VoIP engineer — not a salesperson.