RTPSEND(1)

🎀 RTPSEND(1) 🎀

from the General Commands Manual — okay bestie, this is rtpsend, and she is literally here to generate RTP packets from a textual description. main character energy fr fr. 💅✨

🌸 NAME 🌸

rtpsend — generate RTP packets from textual description. no cap, that's the whole vibe. 💖

✨ SYNOPSIS ✨

rtpsend [-ahlv] [-f infile] [-s port] address/port[/ttl]

💖 DESCRIPTION 💖

rtpsend sends a stream of RTP and RTCP packets with configurable parameters. the packets are sent to the given address/port, optionally with a time-to-live value of ttl. this is intended to test the RTP features of the receiving end. slay, honestly. 🦋

by default, rtpsend reads the packets from standard input. the RTP or RTCP headers are expected in a format written by rtpdump(1) -F ascii. yes, that exact flag, bestie. 🎀

within the input, each entry starts with a time value, in seconds, relative to the beginning. the time value must appear at the beginning of a line, without white space. within an RTP or RTCP packet description, parameters may appear in any order, without white space around the equal sign. lines are continued with initial white space on the next line. comment lines start with #. strings are enclosed in quotation marks. RTP and RTCP entries look like this, bestie:

       <time> RTP
          v=<version>
          p=<padding>
          x=<extension>
          m=<marker>
          pt=<payload type>
          ts=<time stamp>
          seq=<sequence number>
          ssrc=<SSRC>
          cc=<CSRC count>
          csrc=<CSRC>
          data=<hex payload>
          ext_type=<type of extension>
          ext_len=<length of extension header>
          ext_data=<hex extension data>
          len=<packet size in bytes(including header)>

       <time> RTCP (SDES v=<version>
                     (src=<source> cname="..." name="...")
                     (src=<source> ...)
                   )
                   (SR v=<version>
                     ssrc=<SSRC of data source>
                     p=<padding>
                     count=<number of sources>
                     len=<length>
                     ntp=<NTP timestamp>
                     psent=<packet sent>
                     osent=<octets sent>
                       (ssrc=<SSRC of source>
                        fraction=<loss fraction>
                        lost=<number lost>
                        last_seq=<last sequence number>
                        jit=<jitter>
                        lsr=<last SR received>
                        dlsr=<delay since last SR>
                       )
                   )

💅 OPTIONS 💅

the options are as follows, bestie:

• -a — include a router alert IP option in RTCP packets. this is used by the YESSIR resource reservation protoccol. (yes, that spelling is in the original, don't come for me 😭💀)
• -f infile — read the packets from the given infile instead of standard input.
• -h — display a short usage summary and exit.
• -l — send the same sequence of packets again and again. this only works if the input is read from a regular file instead of the standard input. see the -f option.
• -s port — send the packets from the given port. by default, rtpsend chooses a random port.

tiny heads-up, bestie: -v appears in the synopsis [-ahlv], but the page gives no description for it, so I'm not inventing one. periodt. 💀✨

🌈 SEE ALSO 🌈

• rtpdump(1)
• rtpplay(1)

👑 AUTHORS 👑

rtpsend was written by Henning Schulzrinne <hgs@cs.columbia.edu>, with enhancements by Ping Pan and Akira Tsukamoto <akira.tsukamoto@gmail.com>. iconic collaboration, honestly. 🫶

---

💖 sign-off: brought to you by Debian, dated November 23, 2017, and this is the RTPSEND(1) manual page — mwah, bestie. 💋🎀