Sipp

tomeko.
net
Sipp cheatsheet
Sipp is a free test tool and traffic generator for the SIP protocol. It uses XML format files to define test scenarios.
ENGLISH VERSION WERSJA POLSKA Sitemap PROJEKTY PROGRAMY NARZDZIA ONLINE INNE Code Snippets Sipp LPT WinXP Avrdude/MinGW Linki Co nowego? Kontakt
General usage: sipp remote_host[:remote_port] [options]

Some important command-line options:
-sf filename Load test scenario from specified file. -inf filename Use CSV file to insert data substituted for [field0], [field1], etc into XML scenario. First line of file describes order of inserting field sets (SEQUENTIAL/RANDOM/USE). -sn name Use one of the embedded, predefined scenarios like "uac", "uas". -r rate Scenario execution rate, default value = 10 times per period, default period = 1000 ms. -rp period Scenario execution period [ms], combined with execution rate. Execution rate is combined of rate and period parameters, i.e. if period = 3500 and rate = 7 there will be 7 calls in 3.5 s. -t transport mode Set the transport mode: "u1" - UDP, one socket (default), "un" - UDP, one socket per call, other modes (TCP and with compression) available. -max_socket max Set the limit for simultaneously used sockets (for one socket per call mode). If limit is reached, sockets are reused. -m calls Stop and exit after specified tests count. -s service Set user part of the request URI (default: 'service'). Replaces [service] tag in XML scenario file. -ap pass Set password used for auth challenges (default: 'password'). -l limit Limit simultaneous calls (default: 3 * call_duration (s) * rate). -trace_msg Log sent and received SIP messages (file: scenario_pid_messages.log). -trace_err Log error message to file (like "Discarding message which can't be mapped to a known SIPp call").
Search
SLM, SLA Best Practices Learn SLM, SLA Basics and More. Get a Free Guide Now.
www.ITBusinessEdge.com/SLMGuide
Simple scenario files with usage

These scenario files were tested with sipp-win32-2009-06-06.
OPTIONS
Send OPTIONS message 5 times to 30@192.168.1.211.
sipp 192.168.1.211 -sf OPTIONS.xml -m 5 -s 30
Send OPTIONS message 30 times to 30@192.168.1.211 waiting 200 ms for 200/OK reply each time.
sipp 192.168.1.211 -sf OPTIONS_recv_200.xml -m 30 -s 30
REGISTER
Register to 192.168.1.106 using parameters from CSV file. If CSV file has more than one entry you can increase simultaneous call limit (-l option).
sipp 192.168.1.106 -sf REGISTER_client.xml -inf REGISTER_client.csv -m 1 -l 1 -trace_msg -trace_err
converted by Web2PDFConvert.com
REGISTER + SUBSCRIBE application/dialog-info+xml (BLF)

Register to 192.168.1.211 using parameters from CSV file and start dialog-info subscription (RFC4235).
sipp 192.168.1.211 -sf REGISTER_SUBSCRIBE_client.xml -inf REGISTER_SUBSCRIBE_client.csv -m 100 -l 2 -r 2
REGISTER + INVITE
SIPp is simulating 3 UACs, each one of them is making outgoing call. This scenario expects calls to be answered. Call targets are 3 other UACs configured to auto answer and play wav file (single pjsua instance with 3 accounts).
pjsua_vc6d --local-port=5068 --id sip:33@192.168.1.211 --registrar sip:192.168.1.211 --proxy sip:192.168.1.211 --realm * --username 33 --password 33 --next-account --id sip:34@192.168.1.211 --registrar sip:192.168.1.211 --proxy sip:192.168.1.211 --realm * --username 34 --password 34 --next-account --id sip:35@192.168.1.211 --registrar sip:192.168.1.211 --proxy sip:192.168.1.211 --realm * --username 35 --password 35 --play-file file.wav --auto-answer 200 --auto-play
Each call is disconnected after 30 s. Call limit is this time smaller than number of CSV entries to avoid multiple calls to single target.
sipp 192.168.1.211 -sf REGISTER_INVITE_client.xml -inf REGISTER_INVITE_client.csv -m 100 -l 2 -r 1 -rp 10000
REGISTER UAS + SUBSCRIBE application/dialog-info+xml (BLF) UAS

Little tricky scenario that requires two actual scenario files. Sipp is simulating registration and BLF subscription server that immediately terminates subscription with reason=noresource. 1) With tested UAC create registration account 30@your_pc_ip_address, no password. Create dialog-info+xml subscription for 108@your_pc_ip_address. 2) Run UAS REGISTER scenario and wait for the phone to log in. 3) Break REGISTER scenario by hitting Ctrl+C and run UAS SUBSCRIBE scenario.
sipp -sf uas_register.xml sipp -sf uas_subscribe.xml
REGISTER UAC + INVITE + DTMF INFO

1) SIP registration with authorization. 2) Calling number 110. In my test extension 110 is FXS and is looped back to FXO port and call is answered by DISA. 3) Dialing another 3-digit number using SIP INFO DTMF (Content-Type: application/dtmf-relay in this scenario). Call is not answered. 4) Disconnecting. Note: if using "application/dtmf" Content-Type (message body consisting of dtmf only) sign "*" should be encoded as "10" and "#" as "11".
sipp 192.168.1.211 -sf REGC_INVITE_INFO.xml -inf REGC_INVITE_INFO.csv -m 5 -l 1 -r 1 -rp 10000
SIP digest leak test
SIP digest leak is a SIP phone vulnerability that allows attacker to get digest response from a phone and use it to guess password using brute-force method described first on enablesecurity.com page. Here are required steps: 1. 2. 3. 4. 5. 6. attacker calls phone (direct IP call) sending INVITE frame, callee picks up phone, connection is confirmed by both sites, attacker does not send any RTP frames (at least does not have to) and just waits, callee hangs up phone sending BYE request (probably throwing some profanities), in response to BYE attacker sends SIP/401 or 407 message (authentification request), if attack is successfull callee is sending BYE again with Authorization: Digest header added.
At this point attacker has authentification challenge (sent by him with 401/407 message) and response (received with last BYE). Most likely there will be simplest SIP/2.0 authentification scheme used (RFC2069):
ha1 = MD5(username ":" realm ":" password) ha2 = MD5(method ":" req_uri) response = MD5(ha1 ":" nonce ":" ha2)
Assuming that username and realm are known attacker can now use brute-force method to guess user password. There are few conditions that have to be met to make this scheme work: SIP phone has to respond to authentication challenges sent by other sources than registration server(s) it is using (as a note it works with one hardware phone and one softphone I've tested (and those were all user agents I've tested)), phone SIP port has to accessible to attacker, usally phone will be placed behind the Restricted Cone NAT and port would not be forwarded, attacker would most likely have to know username and authentication realm used by target; for better security you probably should not leave "realm" configuration field of SIP phone empty (it could respond to challenges with any realm then making it easier to prepare attack), guessing password through brute-fource would be time consuming or almost impossible for more complex passwords.
sipp 192.168.1.211 -sf uac_digest_leak.xml -s 30 -m 1
Example result: digest_leak.log.
Generating calls using G.729 codec

If you ever had to make high-load call or even single-call tests with G.729(a) codec then you may find out that finding a free softphone with G729a capability is not an easy task. Obviously pjsua would be good choice, but it require downloading DirectX SDK, Intel Performance Primitives package and rebuilding from sources, so it would take few hours to get working binary. Another option is capturing RTP stream using Wireshark and playing it back when generating or receiving calls with SIPp. Here is .pcap file with 2 minutes of G.729 RTP stream. This is actually recorded connection with some voice mail system. Extract this file to \pcap subdirectory of SIPp. Included scenario is UAC call, to get credible load test results you can call i.e. some DISA or auto-attendant lines that will play some announcement back.
sipp 192.168.1.211 -sf uac_pcap_G729.xml -l 1 -m 10
Asterisk FreePBX Hosting Fully featured and private PBX ultra high speed connection vps.powerpbx.org Force Calibration Device Calibrate load with this new device 15% discount on online orders! www.engineeringhelper.com OnSIP Hosted PBX The complete phone system replacement and so much more! www.onsip.com
"Cookie monsters": 299886 Parse time: 0.506 s

Sipp

Uploaded by

Copyright:

Available Formats

Sipp

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sipp

Uploaded by

Copyright:

Available Formats

tomeko.

General usage: sipp remote_host[:remote_port] [options]

Simple scenario files with usage

REGISTER + SUBSCRIBE application/dialog-info+xml (BLF)

REGISTER UAS + SUBSCRIBE application/dialog-info+xml (BLF) UAS

REGISTER UAC + INVITE + DTMF INFO

SIP digest leak test

Example result: digest_leak.log.

Generating calls using G.729 codec

"Cookie monsters": 299886 Parse time: 0.506 s

You might also like