SIPP(1)

πŸ’– NAME πŸ’–

sipp β€” bestie, it's a SIP testing tool and traffic generator. that's the whole personality. πŸ¦‹


🌸 DESCRIPTION 🌸

okay so here's literally how you use it:

sipp remote_host[:remote_port] [options]

and here's a lil example because we love a demo πŸ’…

Run SIPp with embedded server (uas) scenario:

./sipp -sn uas

On the same host, run SIPp with embedded client (uac) scenario:

./sipp -sn uac 127.0.0.1

Available options: (grab a snack, this list is long πŸ“)


πŸŽ€ Scenario file options πŸŽ€

  • -sd β€” Dumps a default scenario (embedded in the SIPp executable).
  • -sf β€” Loads an alternate XML scenario file. Wanna learn more about XML scenario syntax? Use the -sd option to dump embedded scenarios β€” they contain all the necessary help, no cap.
  • -rxsf β€” Loads an alternate receive xml scenario file as the second scenario β€” enabling a mixture of originating and terminating calls to be executed. If this is included then the second scenario MUST be a server mode scenario, and the first scenario (specified in -sf / -sn) MUST be a client-mode scenario. If both -snrx and -sfrx are omitted then only a single scenario is executed.
  • -oocsf β€” Load out-of-call scenario.
  • -oocsn β€” Load out-of-call scenario.
  • -sn β€” Use a default scenario (embedded in the SIPp executable). If this option is omitted, the Standard SipStone UAC scenario is loaded. Available values in this version:
    • 'uac' β€” Standard SipStone UAC (default).
    • 'uas' β€” Simple UAS responder.
    • 'regexp' β€” Standard SipStone UAC - with regexp and variables.
    • 'branchc' β€” Branching and conditional branching in scenarios - client.
    • 'branchs' β€” Branching and conditional branching in scenarios - server.
    • Default 3pcc scenarios (see -3pcc option):
      • '3pcc-C-A' β€” Controller A side (must be started after all other 3pcc scenarios)
      • '3pcc-C-B' β€” Controller B side.
      • '3pcc-A' β€” A side.
      • '3pcc-B' β€” B side.
  • -rxrn β€” Use a default scenario (embedded in the sipp executable) for the second scenario β€” enabling a mixture of originating and terminating calls to be executed. If this is included then the second scenario MUST be a server mode scenario, and the first scenario (specified in -sf / -sn) MUST be a client-mode scenario. If both -snrx and -sfrx are omitted then only a single scenario is executed.

🌈 IP, port and protocol options 🌈

  • -t β€” Set the transport mode:
    • u1: UDP with one socket (default)
    • un: UDP with one socket per call
    • ui: UDP with one socket per IP address. The IP addresses must be defined in the injection file.
    • t1: TCP with one socket
    • tn: TCP with one socket per call
    • c1: u1 + compression (only if compression plugin loaded)
    • cn: un + compression (only if compression plugin loaded)
heads up bestie: this plugin is not provided with SIPp. πŸ’€
  • -i β€” Set the local IP address for 'Contact:', 'Via:', and 'From:' headers. Default is primary host IP address.
  • -p β€” Set the local port number. Default is a random free port chosen by the system.
  • -bind_local β€” Bind socket to local IP address, i.e. the local IP address is used as the source IP address. If SIPp runs in server mode it will only listen on the local IP address instead of all IP addresses.
  • -bind_to_device β€” Bind socket to the specified network device. Requires superuser permissions.
  • -ci β€” Set the local control IP address
  • -cp β€” Set the local control port number. Default is 8888.
  • -max_socket β€” Set the max number of sockets to open simultaneously. This option is significant if you use one socket per call. Once this limit is reached, traffic is distributed over the sockets already opened. Default value is 50000
  • -max_reconnect β€” Set the the maximum number of reconnection.
  • -reconnect_close β€” Should calls be closed on reconnect?
  • -reconnect_sleep β€” How long (in milliseconds) to sleep between the close and reconnect?
  • -rsa β€” Set the remote sending address to host:port for sending the messages.

πŸ’œ SIPp overall behavior options πŸ’œ

  • -v β€” Display version and copyright information.
  • -bg β€” Launch SIPp in background mode.
  • -nostdin β€” Disable stdin.
  • -plugin β€” Load a plugin.
  • -sleep β€” How long to sleep for at startup. Default unit is seconds.
  • -skip_rlimit β€” Do not perform rlimit tuning of file descriptor limits. Default: false.
  • -buff_size β€” Set the send and receive buffer size.
  • -sendbuffer_warn β€” Produce warnings instead of errors on SendBuffer failures.
  • -lost β€” Set the number of packets to lose by default (scenario specifications override this value).
  • -key keyword value β€” Set the generic parameter named "keyword" to "value".
  • -set variable value β€” Set the global variable parameter named "variable" to "value".
  • -tdmmap β€” Generate and handle a table of TDM circuits. A circuit must be available for the call to be placed. Format: -tdmmap {0-3}{99}{5-8}{1-31}
  • -dynamicStart variable value β€” Set the start offset of dynamic_id variable
  • -dynamicMax variable value β€” Set the maximum of dynamic_id variable
  • -dynamicStep variable value β€” Set the increment of dynamic_id variable

πŸ‘‘ Call behavior options πŸ‘‘

  • -aa β€” Enable automatic 200 OK answer for INFO, NOTIFY, OPTIONS and UPDATE.
  • -base_cseq β€” Start value of [cseq] for each call.
  • -cid_str β€” Call ID string (default %u-%p@%s). %u=call_number, %s=ip_address, %p=process_number, %r=random_integer, %%=% (in any order).
  • -d β€” Controls the length of calls. More precisely, this controls the duration of 'pause' instructions in the scenario, if they do not have a 'milliseconds' section. Default value is 0 and default unit is milliseconds.
  • -deadcall_wait β€” How long the Call-ID and final status of calls should be kept to improve message and error logs (default unit is ms).
  • -auth_uri β€” Force the value of the URI for authentication. By default, the URI is composed of remote_ip:remote_port.
  • -au β€” Set authorization username for authentication challenges. Default is taken from -s argument
  • -ap β€” Set the password for authentication challenges. Default is 'password'
  • -s β€” Set the username part of the request URI. Default is 'service'.
  • -default_behaviors β€” Set the default behaviors that SIPp will use. Possible values are:
    • all β€” Use all default behaviors
    • none β€” Use no default behaviors
    • bye β€” Send byes for aborted calls
    • abortunexp β€” Abort calls on unexpected messages
    • pingreply β€” Reply to ping requests
    • cseq β€” Check CSeq of ACKs

If a behavior is prefaced with a -, then it is turned off. Example: all,-bye

  • -nd β€” No Default. Disable all default behavior of SIPp which are the following:
    • On UDP retransmission timeout, abort the call by sending a BYE or a CANCEL
    • On receive timeout with no ontimeout attribute, abort the call by sending a BYE or a CANCEL
    • On unexpected BYE send a 200 OK and close the call
    • On unexpected CANCEL send a 200 OK and close the call
    • On unexpected PING send a 200 OK and continue the call
    • On unexpected ACK CSeq do nothing
    • On any other unexpected message, abort the call by sending a BYE or a CANCEL
  • -pause_msg_ign β€” Ignore the messages received during a pause defined in the scenario
  • -callid_slash_ign β€” Don't treat a triple-slash in Call-IDs as indicating an extra SIPp prefix.

🧚 Injection file options 🧚

  • -rxinf β€” Inject values from an external CSV file during calls into the scenarios. First line of this file say whether the data is to be read in sequence (SEQUENTIAL), random (RANDOM), or user (USER) order. Each line corresponds to one call and has one or more ';' delimited data fields. Those fields can be referred as [field0], [field1], ... in the xml scenario file. Several CSV files can be used simultaneously (syntax: -inf f1.csv -inf f2.csv ...)
  • -inf β€” Inject values from an external CSV file during calls into the scenarios. First line of this file say whether the data is to be read in sequence (SEQUENTIAL), random (RANDOM), or user (USER) order. Each line corresponds to one call and has one or more ';' delimited data fields. Those fields can be referred as [field0], [field1], ... in the xml scenario file. Several CSV files can be used simultaneously (syntax: -inf f1.csv -inf f2.csv ...)
  • -infindex file field β€” Create an index of file using field. For example -inf ../path/to/users.csv -infindex users.csv 0 creates an index on the first key.
  • -ip_field β€” Set which field from the injection file contains the IP address from which the client will send its messages. If this option is omitted and the '-t ui' option is present, then field 0 is assumed. Use this option together with '-t ui'

πŸ¦‹ RTP behaviour options πŸ¦‹

  • -mi β€” Set the local media IP address (default: local primary host IP address)
  • -rtp_echo β€” Enable RTP echo. RTP/UDP packets received on media port are echoed to their sender. RTP/UDP packets coming on this port + 2 are also echoed to their sender (used for sound and video echo).
  • -mb β€” Set the RTP echo buffer size (default: 2048).
  • -min_rtp_port β€” Minimum port number for RTP socket range.
  • -max_rtp_port β€” Maximum port number for RTP socket range.
  • -mp β€” Sets -min_rtp_port for backwards compatibility.
  • -rtp_payload β€” RTP default payload type.
  • -rtp_threadtasks β€” RTP number of playback tasks per thread.
  • -rtp_buffsize β€” Set the rtp socket send/receive buffer size.
  • -rtpcheck_debug β€” Write RTP check debug information to file
  • -audiotolerance β€” Audio error tolerance for RTP checks (0.0-1.0) -- default: 1.0
  • -videotolerance β€” Video error tolerance for RTP checks (0.0-1.0) -- default: 1.0
  • -random_base_ssrc β€” Use a random base SSRC for RTP streams instead of default value 0xCA110000

⭐ Call rate options ⭐

(cut here β€” this is where part 1 hands off, the rate stuff keeps going πŸ‘€)

  • -r β€” sets the call rate (in calls per second). Bestie you can literally change this mid-test by smashing '+', '_', '*' or '/'. Default is 10. Hitting '+' bumps the rate up by 1 * rate_scale, '-' drops it by 1 * rate_scale, '*' yeets it up by 10 * rate_scale, and '/' brings it down by 10 * rate_scale. πŸ’…
  • -rp β€” sets the rate period for the call rate. Default is 1 second and the default unit is milliseconds. This is the one that lets you have n calls every m milliseconds (just do -r n -rp m). Examples, served fresh:
-r 7 -rp 2000  ==>  7 calls every 2 seconds
-r 10 -rp 5s   =>   10 calls every 5 seconds
  • -rate_scale β€” controls the units for the '+', '-', '*', and '/' keys.
  • -rate_increase β€” specifies the rate increase every -rate_interval units (default is seconds). This is how you ramp the load up for each independent logging period. Example, because I know you want it:
-rate_increase 10 -rate_interval 10s
==> increase calls by 10 every 10 seconds
  • -rate_max β€” if -rate_increase is set, then quit after the rate reaches this value. Example:
-rate_increase 10 -rate_max 100
==> increase calls by 10 until 100 cps is hit
  • -rate_interval β€” sets the interval by which the call rate is increased. Defaults to the value of -fd.
  • -no_rate_quit β€” if -rate_increase is set, do not quit after the rate reaches -rate_max. She simply refuses to leave. πŸ™ˆ
  • -l β€” sets the maximum number of simultaneous calls. Once this limit is reached, traffic is decreased until the number of open calls goes down. Default:
(3 * call_duration (s) * rate)
  • -m β€” stop the test and exit when calls calls are processed. πŸŽ€
  • -users β€” instead of starting calls at a fixed rate, begin users calls at startup, and keep the number of calls constant. Lowkey the chill mode.

πŸŽ€ Retransmission and timeout options πŸŽ€

  • -recv_timeout β€” global receive timeout. Default unit is milliseconds. If the expected message is not received, the call times out and is aborted. 😭
  • -send_timeout β€” global send timeout. Default unit is milliseconds. If a message is not sent (due to congestion), the call times out and is aborted.
  • -timeout β€” global timeout. Default unit is seconds. If this option is set, SIPp quits after nb units (-timeout 20s quits after 20 seconds).
  • -timeout_error β€” SIPp fails if the global timeout is reached is set (requires the -timeout option). The drama is real.
  • -max_retrans β€” maximum number of UDP retransmissions before the call ends on timeout. Default is 5 for INVITE transactions and 7 for others.
  • -max_invite_retrans β€” maximum number of UDP retransmissions for invite transactions before the call ends on timeout.
  • -max_non_invite_retrans β€” maximum number of UDP retransmissions for non-invite transactions before the call ends on timeout.
  • -nr β€” disable retransmission in UDP mode. Periodt.
  • -rtcheck β€” select the retransmission detection method: full (default) or loose.
  • -T2 β€” global T2-timer in milli seconds.

🌈 Third-party call control options 🌈

  • -3pcc β€” launches the tool in 3pcc mode ("Third Party call control"). The passed IP address depends on the 3PCC role.
    • When the first twin command is 'sendCmd' then this is the address of the remote twin socket. SIPp will try to connect to this address:port to send the twin command (this instance must be started after all other 3PCC scenarios). Example: 3PCC-C-A scenario.
    • When the first twin command is 'recvCmd' then this is the address of the local twin socket. SIPp will open this address:port to listen for twin command. Example: 3PCC-C-B scenario.
  • -master β€” 3pcc extended mode: indicates the master number. πŸ‘‘
  • -slave β€” 3pcc extended mode: indicates the slave number.
  • -slave_cfg β€” 3pcc extended mode: indicates the file where the master and slave addresses are stored.

⭐ Performance and watchdog options ⭐

  • -timer_resol β€” sets the timer resolution. Default unit is milliseconds. Heads up bestie, this option has an impact on timers precision. Small values allow more precise scheduling but impacts CPU usage. If the compression is on, the value is set to 50ms. The default value is 10ms.
  • -max_recv_loops β€” sets the maximum number of messages received read per cycle. Increase this value for high traffic level. The default value is 1000.
  • -max_sched_loops β€” sets the maximum number of calls run per event loop. Increase this value for high traffic level. The default value is 1000.
  • -watchdog_interval β€” sets the gap between watchdog timer firings. Default is 400.
  • -watchdog_reset β€” if the watchdog timer has not fired in more than this time period, then reset the max triggers counters. Default is 10 minutes.
  • -watchdog_minor_threshold β€” if it has been longer than this period between watchdog executions, count a minor trip. Default is 500.
  • -watchdog_major_threshold β€” if it has been longer than this period between watchdog executions, count a major trip. Default is 3000.
  • -watchdog_major_maxtriggers β€” how many times the major watchdog timer can be tripped before the test is terminated. Default is 10.
  • -watchdog_minor_maxtriggers β€” how many times the minor watchdog timer can be tripped before the test is terminated. Default is 120.

πŸ¦‹ Tracing, logging and statistics options πŸ¦‹

  • -f β€” sets the statistics report frequency on screen. Default is 1 and the default unit is seconds.
  • -trace_stat β€” dumps all statistics in <scenario_name>_<pid>.csv file. Use the '-h stat' option for a detailed description of the statistics file content.
  • -stat_delimiter β€” sets the delimiter for the statistics file.
  • -stf β€” sets the file name to use to dump statistics.
  • -fd β€” sets the statistics dump log report frequency. Default is 60 and the default unit is seconds.
  • -rfc3339 β€” use timestamps in RFC3339 format.
  • -periodic_rtd β€” reset response time partition counters each logging interval.
  • -trace_msg β€” displays sent and received SIP messages in <scenario file name>_<pid>_messages.log.
  • -message_file β€” sets the name of the message log file.
  • -message_overwrite β€” overwrite the message log file (default true).
  • -trace_shortmsg β€” displays sent and received SIP messages as CSV in <scenario file name>_<pid>_shortmessages.log.
  • -shortmessage_file β€” sets the name of the short message log file.
  • -shortmessage_overwrite β€” overwrite the short message log file (default true).
  • -trace_counts β€” dumps individual message counts in a CSV file.
  • -trace_err β€” trace all unexpected messages in <scenario file name>_<pid>_errors.log.
  • -error_file β€” sets the name of the error log file.
  • -error_overwrite β€” overwrite the error log file (default true).
  • -trace_error_codes β€” dumps the SIP response codes of unexpected messages to <scenario file name>_<pid>_error_codes.log.
  • -trace_calldebug β€” dumps debugging information about aborted calls to <scenario_name>_<pid>_calldebug.log file.
  • -calldebug_file β€” sets the name of the call debug file.
  • -calldebug_overwrite β€” overwrite the call debug file (default true).
  • -trace_screen β€” dump statistic screens in the <scenario_name>_<pid>_screens.log file when quitting SIPp. Useful to get a final status report in background mode (-bg option). πŸ’–
  • -screen_file β€” sets the name of the screen file.
  • -screen_overwrite β€” overwrite the screen file (default true).
  • -trace_rtt β€” allow tracing of all response times in <scenario file name>_<pid>_rtt.csv.
  • -rtt_freq β€” freq is mandatory. Dump response times every freq calls in the log file defined by -trace_rtt. Default value is 200.
  • -trace_logs β€” allow tracing of <log> actions in <scenario file name>_<pid>_logs.log.
  • -log_file β€” sets the name of the log actions log file.
  • -log_overwrite β€” overwrite the log actions log file (default true).
  • -ringbuffer_files β€” how many error, message, shortmessage and calldebug files should be kept after rotation?
  • -ringbuffer_size β€” how large should error, message, shortmessage and calldebug files be before they get rotated?
  • -max_log_size β€” what is the limit for error, message, shortmessage and calldebug file sizes.

πŸ’€ Signal handling πŸ’€

SIPp can be controlled using POSIX signals. The following signals are handled:

  • USR1 β€” similar to pressing the 'q' key. It triggers a soft exit of SIPp. No more new calls are placed and all ongoing calls are finished before SIPp exits. Example:
kill -SIGUSR1 732
  • USR2 β€” triggers a dump of all statistics screens in <scenario_name>_<pid>_screens.log file. Especially useful in background mode to know what the current status is. Example:
kill -SIGUSR2 732

πŸ‘‘ Exit codes πŸ‘‘

Upon exit (on fatal error or when the number of asked calls (-m option) is reached), SIPp exits with one of the following exit codes:

  • 0: All calls were successful
  • 1: At least one call failed
  • 97: Exit on internal command. Calls may have been processed
  • 99: Normal exit without calls processed
  • 253: RTP validation failure
  • -1: Fatal error
  • -2: Fatal error binding a socket

SIPp v3.7.7-PCAP.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Author: see source files.


And that's a wrap bestie!! πŸŽ€ This was sipp, the December 2025 era, straight out of the SIPP(1) manual. Go run your tests, hydrate, and slay. πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from