RTPTRANS(1)
π RTPTRANS(1) β the rtptrans girlies' edition π
okay so this is the manual page for rtptrans, a General Commands Manual situation, and honestly? she's niche but she serves. here's everything, no gatekeeping. π«Ά
β¨ NAME β¨
rtptrans β translate RTP between unicast and multicast networks
like, she's a translator. for networks. multilingual icon behavior fr fr π
β¨ SYNOPSIS β¨
rtptrans [-h] address/port[/ttl] address/port[/ttl] [...]
bestie the whole invocation is just a lil list of address/port[/ttl] situations and you can keep stacking them, and there's a -h in there too β the page does not elaborate on -h and I'm not gonna make stuff up, so that's all we're saying about it π
β¨ DESCRIPTION β¨
okay so the entire personality of rtptrans is this: it takes RTP/RTCP packets that arrive from one of the addresses you specified, and translates them out to all the other addresses you specified. that's it, that's the job. she's a little switchboard with a heart of gold π
the addresses can be multicast or unicast β both are welcome here, no dress code πΈ
and those optional TTL values? ignored for unicast addresses. like, she sees them, she just doesn't care. it's giving "read at 4:47 PM." π¦
π§ bonus behavior: the VAT situation (iykyk)
additionally β and this is the part that makes her interesting β the translator can translate VAT packets into RTP packets. not me being multifunctional π
so here's the lore: VAT control packets get translated into RTCP SDES packets with a CNAME entry and a NAME entry. cute, right? BUT β and this is a big but β
β οΈ this is only intended to be used in one very specific configuration, so don't get creative. this is not a "do whatever" feature, this is a "do exactly this" feature.
the configuration in question: VAT packets arriving on a multicast connection are translated into RTP and sent over a unicast link. that's the whole allowed vibe.
and just so we're clear, because someone will ask:
- RTP packets are not yet translated into VAT packets. not yet. she's working on it. π
- packets arriving on unicast links are not changed at all. zero edits. hands off. β
because of all that, only one topology is supported, and it's directional, so pay attention bestie:
- on the way in: βmulticast VAT -> translator -> unicast RTPβ
- on the way back: βmulticast VAT <- translator <- unicast VATβ
which means the audio agent on the unicast link should be able to use both VAT and RTP. she's bilingual, she just needs you to respect the arrangement π
β¨ AUTHORS β¨
credits time, we love to see it π
rtptranswas written by Henning Schulzrinne<hgs@cs.columbia.edu>- with enhancements by Dorgham Sisalem
<sisalem@iptel.org>and Steve Casner
three icons, one command. no cap. π₯
π asides corner: this page is the Debian flavor of the manual, and it was dated November 23, 2017 β so yes, she's an elder Gen Z but she still ate and left no crumbs. periodt. β
okay ily, go translate some packets, mwah πβ¨
π¦ where this page comes from
- nixos 26.05: rtptools 1.22
- nixpkgs unstable: rtptools 1.22
- π the page's license: BSD-3-Clause
- (c) 1998-2018 by Columbia University; all rights reserved
- (c) 2017-2018 by Jan Stary <hans@stare.cz>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms