Show summary of options.

Send every RTP packet twice in sessions that use low-bitrate codecs. Only packets that are smaller than 128 bytes will be sent twice. This option can improve audio quality on lossy links.

rtpproxy will stay in foreground mode if this option is set.

Show version of program.

Show supported rtpp command protocol revisions.

IPv4 listen IP address(es). This option can be specified multiple times. Bridging mode can be enabled when the first IPv4 (or first IPv6) listen argument is specified as addr1/addr2.

Additional labeled listen addresses use the separate format [label@]address[=advertized_address]. The /addr2 form is not valid for labeled entries.

When multiple listen addresses are configured, all addresses after the first must have unique labels. Such labels are accepted by the l{label} argument in U and L commands.

IPv6 listen IP address(es). This option can be specified multiple times. Two argument formats are supported: addr1[/addr2] and [label@]address[=advertized_address].

This parameter configures rtpproxy control socket. The control socket is used by the call controller for the purpose of creating, modifying, and deleting RTP sessions. The control socket can also be used to fetch stats from the rtpproxy process, or about specific media sessions. Format of ctrl_socket is <type>:<socket>. Following types are supported:

Default value is unix:/var/run/rtpproxy.sock.

Set ToS (Type of Service) in the outgoing IP header. Default value is 0xB8. Setting this parameter to -1 disables setting ToS resulting in operating system default ToS being used instead.

Directory to write recorded RTP sessions.

Spool directory for recording of RTP streams. When the session is stopped, the recording will be moved from the spool directory to the rec_dir directory as specified by the -r option.

Prevent rtpproxy from recording RTCP when recording RTP. rtpproxy records RTCP by default when RTP recording is enabled.

This parameter configures the name of the file where PID of running rtpproxy will be stored. Default is /var/run/rtpproxy.pid.

Specify the RTP inactivity timer. Defaults to 60 seconds.

If the rtpproxy does not receive any RTP packets for more than max_ttl it will then delete the session.

Set the default per-stream packet-per-second limit for newly created RTP/RTCP streams. The first value applies to RTP streams. The optional second value applies to RTCP streams; if omitted, the RTP value is used for RTCP as well. A value of 0 disables the default limit, which is the default behavior. The limit can be changed for an existing session using the S pps= control sub-command.

Set the default maximum allowed incoming packet size in bytes for newly created RTP/RTCP streams. The first value applies to RTP streams. The optional second value applies to RTCP streams; if omitted, the RTP value is used for RTCP as well. Packets larger than the configured size are dropped. A value of 0 disables the default limit, which is the default behavior. The limit can be changed for an existing session using the S mps= control sub-command.

Set the maximum number of open file descriptors per process. The default maximum is set by the operating system, and can be overridden using the -L flag.

The rtpproxy requires four file descriptors per session to ensure that it can reliably identify where each stream is coming from in a NAT firewall scenario.

Set advertised address of rtpproxy. Useful if the rtpproxy is behind a NAT firewall. (Amazon EC2) When the rtpproxy receives a session request from a SIP controller it will return the IP address(es) specified by the -A option.

This option configures the legacy bridge internal/external address pair. For per-address advertised overrides with multiple -l/-6 entries, use =advertized_address inside each listen address argument.

Set lower limit on UDP ports range that the rtpproxy uses for RTP/RTCP sessions to min_port. Default is 35000.

Set upper limit on UDP ports range that the rtpproxy uses for RTP/RTCP sessions to max_port. Default is 65000.

Switch rtpproxy to UID identified by the uname and optional GID identified by gname when proxy is up and running.

Set access mode for the controlling UNIX-socket (if used). Only applies if rtpproxy runs under a different GID using -u option.

By default the rtpproxy will warn user if running as superuser (UID 0) in local control mode and refuse to run in remote control mode at all. This switch removes the check.

Enable independent RTP activity timeout mode. By default, a timeout (which results in automatic destruction of the session) can only occur if no RTP packets are received on any of the session's ports. This option, if set, varies that behaviour, such that a timeout will occur if packets are still being received on one port but not the other. The option should be used with caution since in some cases it's perfectly fine to have packets coming from only one side of conversation (i.e. when the second party has muted its audio).

This parameter specifies permitted notification sockets only. The listening socket must be created by another application, preferably before starting rtpproxy.

Timeout notifications must be enabled by the SIP controller when setting up the session. The SIP Controller must specify the timeout_socket, and a notify_tag, which is expected to be an arbitrary string that can be used by the SIP controller to identify which session a received time out notification relates to.

If a SIP Controller specifies a notification socket for a session, and that socket is not specified using the -n flag, the rtpproxy will not send a notification, and will not produce an error. It will ignore the notification request.

Format of timeout_socket is <type>:<socket>. Following types are supported:

There is no default value, notifications are not sent and not permitted unless a value is specified explicitly. Multiple notification sockets can be provided by specifying the -n flag more than once.

Record sessions using libpcap file format instead of non-standard ad-hoc format. The libpcap format, which is the de-facto standard for packet capturing software, has the advantage of being compatible with numerous third-party tools and utilities, such as tcpdump or Wireshark. The drawback of libpcap is slightly larger overhead (extra 12 bytes for every saved RTP packet for IPv4).

Record all sessions going through the rtpproxy unconditionally. By default rtpproxy expects the SIP controller to enable recording on a per-session basis.

Configures the verbosity level of the log output. Possible log_level values in the order from the most verbose to the least verbose are: DBUG, INFO, WARN, ERR and CRIT.

The optional log_facility parameter sets syslog(3) facility assigned to log messages.

Example: -d WARN:LOG_LOCAL5

The default level in foreground mode is DBUG, in background - WARN and facility is LOG_DAEMON.

Treat all RTP/RTCP sessions as "asymmetric", i.e. disable any NAT traversal features unconditionally.

Specify the inactivity timer for sessions that have not been fully set up yet, i.e. before the rtpproxy has received the matching L command. Defaults to the value of -T.

Allocate UDP ports for new sessions sequentially instead of randomly. Mostly intended for debugging, to make the behaviour more predictable.

Switch the rtpproxy process to the SCHED_FIFO (fifo) or SCHED_RR (rr) real-time scheduling policy, at the maximum priority for that policy.

Set the scheduling priority (nice value) of the rtpproxy process to level.

Do not change the working directory to / when switching into the background mode.

Do not redirect the standard output and the standard error to /dev/null when switching into the background mode.

Print the name of the monotonic clock used by the rtpproxy and exit.

Read the configuration of the loadable modules from config_file, in the UCL format. An example is provided in doc/rtpproxy.conf.sample in the source tree.

Load module, specified as a path to the shared object of a dynamically loadable module, or as a name of a module compiled in statically. This option can be specified multiple times. Modules that require configuration cannot be loaded this way, use --config instead.

In the bridging mode, do not treat all sessions as asymmetric, which is the default in that mode for historical reasons.

Only accept numeric IP addresses, in the command line arguments and in the control commands, instead of resolving host names.