StarTrinity.com

VoIP software

VoIP community

VoIP marketplace


logged in as
log out

SIP Tester usage diagrams

The diagrams show how SIP Tester is used in various environments

Active mode: generation and receiving SIP calls

Testing a SIP server
CallXML script(s)
wav/mp3/pcap audio files for playback
reference audio files for IVR verification
CSV file(s): list of test parameters
SIP Tester
Windows desktop GUI, Web UI, CLI
CDR: CSV files, database
recorded wav/pcap files
sound card (speakers+microphone)
VoIP network
SIP, RTP, RTCP, T.38
Destination under test (DUT):
trunk, provider, IVR server
SIP Tester "master" node
reports collected from all "slave" nodes
synchronization over HTTP
SIP Tester "slave" nodes
SIP+RTP
SIP server under test
Testing a VoIP network
SIP Tester at customer's site
Customer's VoIP network
SIP Tester at datacenter
Testing a SIP-PSTN gateway
SIP Tester - sends and receives calls
SIP-PSTN gateway 1
SIP+RTP
SIP-PSTN gateway 2
ISUP/SS7/PRI/E1,
FXS/FXO
SIP+RTP
Testing SIP phones by simulating IP-PBX
Multiple
SIP phones
INVITE, REGISTER
Testing IP-PBX by simulating SIP phones
SIP Tester as multiple SIP phones: simulates calls between extensions
INVITE, REGISTER
IP-PBX
VoIP dialer
SIP Tester receives calls,
simulates various call terminations: real person, IVR, fax machine
Verifying integrity of routes
Originating SIP Tester
HTTP API (info about calls)
Terminating SIP Tester
SIP calls going through the route
VoIP route
(system of softswitches)
Testing IVR server or call center via PRI
SIP Tester
SIP+RTP
VoIP provider
PSTN
PRI
+1800xx
IVR server / call center

Passive mode: detecting (sniffing) SIP calls

Analyzing VoIP traffic on a Windows server with IP-PBX
IP-PBX
Trunks, SIP phones
windows server

SIP Tester
reports, pcaps
Analyzing VoIP traffic through mirroring port
SIP/media server(s)
IP switch
mirroring port
Trunks, SIP phones
SIP Tester
reports, pcaps
Analyzing recorded PCAP files
Some VoIP network
PCAP file(s)
SIP Tester
reports, decoded wav files
Copyright 2011-2017 StarTrinity.com | Blog | Contact lead developer via LinkedIn | Get support via TeamViewer