Manual › Tools
Sample scenarios
The folder scenarios has many ready-to-run scenarios. Most come in pairs: a client scenario and the server scenario that answers it, so you can run both with SIP Inspector, one against the other, on one computer. Every file starts with a comment that tells what it does.
| Scenario | What it does |
|---|---|
Asterisk_reg_client.txt | Client: registers with an Asterisk server |
Asterisk_reg_incoming_call_client.txt | Client: registers with Asterisk and answers incoming calls |
Asterisk_reg_outgoing_call_client.txt | Client: registers with Asterisk and makes a call |
Attended_transfer_pbx_client.txt | Client: attended call transfer, as a transferor (lab scenario) |
Attended_transfer_phones_client.txt | Client: attended call transfer, as a transferor (lab scenario) |
Attended_transfer_target_server.txt | Server: answers a call and then calls extension 109 (lab scenario) |
Call_brokering_b2bua_server.txt | Server: registrar and call broker (back-to-back user agent) |
Call_busy_client.txt | Client: call that is rejected with 486 Busy Here |
Call_busy_server.txt | Server: rejects every call with 486 Busy Here |
Call_cancel_client.txt | Client: call that is cancelled while it rings (CANCEL, 487 Request Terminated) |
Call_cancel_server.txt | Server: rings and accepts the CANCEL of the caller |
Call_codec_change_rtp_only_client.txt | Client: call whose RTP changes in mid-call without any signalling |
Call_codec_change_signaling_client.txt | Client: call with a mid-call codec change by re-INVITE |
Call_codec_change_signaling_server.txt | Server: answers a call and a re-INVITE (mid-call change) |
Call_hold_resume_client.txt | Client: call put on hold and taken off hold with re-INVITEs |
Call_hold_resume_server.txt | Server: answers a call that the caller puts on hold and resumes |
Call_speech_dials_asserts_client.txt | Client: call with live speech and dialled digits, with pass/fail assertions |
Call_speech_dials_client.txt | Client: call with live speech and dialled digits |
Call_speech_dials_server.txt | Server: answers one incoming call |
Call_transfer_client.txt | Client: transfers a call (blind transfer, RFC 3515), playing two roles |
Call_transfer_server.txt | Server: the transferee of a blind transfer (RFC 3515) |
Call_video_client.txt | Client: video call, H.264 and PCMU |
Call_video_server.txt | Server: video call, H.264 and PCMU |
HexBody_client.txt | Client: call with binary (QSIG) bodies written in hexadecimal |
HexBody_server.txt | Server: call with binary (QSIG) bodies written in hexadecimal |
Load_gradual_increase_client.txt | Client: raises the number of simultaneous calls step by step |
Message_client.txt | Client: SIP instant message (MESSAGE, RFC 3428) |
Message_server.txt | Server: receives a SIP instant message (MESSAGE) and answers 200 OK |
Options_ping_client.txt | Client: OPTIONS ping - is the server up and answering SIP? |
Options_ping_server.txt | Server: answers OPTIONS with 200 OK and its capabilities |
PBX_call_codec_change_reinvite_client.txt | Client: call through a proxy with a codec change by re-INVITE |
PBX_call_series_client.txt | Client: outgoing calls, one per row of a values file |
PBX_reg_incoming_call_client.txt | Client: registers every minute and answers incoming calls |
Perf_cps_client.txt | Client: call rate test - a short call without media |
Perf_cps_server.txt | Server: call rate test - answers a short call without media |
Perf_rtp_client.txt | Client: RTP test - a call with G.711 audio both ways |
Perf_rtp_server.txt | Server: RTP test - answers and sends G.711 audio until the BYE |
Port_scan_client.txt | Client: sends a REGISTER to many addresses and ports |
PRACK_client.txt | Client: call with reliable provisional responses (RFC 3262) |
PRACK_server.txt | Server: answers a call with a reliable 180 Ringing (RFC 3262) |
Record_route_client.txt | Client: call through proxies (Record-Route / Route) |
Record_route_server.txt | Server: call through proxies (Record-Route / Route) |
Reg_auth_call_advanced_client.txt | Client: registers and calls, following the server's challenge |
Reg_auth_call_client.txt | Client: registers and calls, both challenged |
Reg_auth_call_server.txt | Server: registrar and call server that challenges the REGISTER and the INVITE |
Reg_branching_client.txt | Client: registers with authentication, branching on the response |
Reg_call_client.txt | Client: registers, then makes a call |
Reg_call_server.txt | Server: registrar that also takes a call |
Reg_client.txt | Client: registers with authentication |
Reg_series_client.txt | Client: registers many users, one per row of a values file |
Reg_server.txt | Registrar server with authentication scenario |
Reg_subscribe_call_client.txt | Client: registers, subscribes for message-waiting notifications, then makes a call |
Reg_subscribe_call_server.txt | Server: registrar, message-waiting notifier and call server |
Reg_subscribe_incoming_call_client.txt | Client: registers, subscribes for message-waiting notifications, then receives a call |
Reg_subscribe_incoming_call_server.txt | Server: registrar and message-waiting notifier that calls the client |
SRTP_reg_incoming_call_client.txt | Client: registers and answers an SRTP call |
SRTP_reg_outgoing_call_client.txt | Client: SRTP call to a server that challenges with 401 |
SUBSCRIBE_dialog_client.txt | Client: subscribes to dialog events (BLF) |
SUBSCRIBE_dialog_server.txt | SUBSCRIBE server scenario - subscribes for dialog event (BLF) Subscriber username: any Subscribing to: any Scenario simulates subscription, and a full cycle state changing: terminated->early->confirmed->terminated. |
WebRTC_reg_incoming_call_server.txt | Server: WebSocket server that takes a call from a browser (WebRTC) |
WebRTC_reg_outgoing_call_server.txt | Server: WebSocket server that calls a registered browser (WebRTC) |