Learn how to use SIPp integrated scenarios by examples.

Example 1: Using the default UAC scenario to send calls

./sipp -sn uac -d 20000 -s 1001  -m 6

will generate a maximum of 6 SIP calls to the destination IP address of , each call lasting for 20 seconds. The calls will use the uac scenario and set the From header to 1001.

-snUse a default scenario (embedded in the SIPp executable)
-dControls 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
-sSet the username part of the request URI. Default is 'service'.
-mStop the test and exit when 'calls' calls are processed

Example 2: Using the default UAC scenario to send calls with rate limit

Send 6 Calls (INVITE) to 1001@ with the rate of 2 concurrent calls in 10 seconds - After the Call answered pause for 20000 ms and Hangup (BYE)

(target will get a call every 5 seconds)

./sipp -sn uac -d 20000 -s 1001  -m 6 -r 2 -rp 10000
-rSet the call rate (in calls per seconds).
-rp: Specify the rate period for the call rate. Default is 1 second and default unit is milliseconds. This allows you to have n calls every m milliseconds (by using -r n -rp m). Example: -r 7 -rp 2000 ==> 7 calls every 2 seconds. -r 10 -rp 5s => 10 calls every 5 seconds.

Example 3: Enabling logs

./sipp -sn uac -d 20000 -s 1001  -m 6 -trace_msg -trace_shortmsg -trace_err -trace_screen
trace_msgDisplays sent and received SIP messages in __messages.log
trace_shortmsgDisplays sent and received SIP messages as CSV in __shortmessages.log
trace_errTrace all unexpected messages in __errors.log.
trace_screenDump statistic screens in the <scenario_name>__screens.log file when quitting SIPp. Useful to get a final status report in background mode