Giacomo Vacca

This is just a practical guide to have latest sipp on debian , to benefit from features that are not available in the stock package ( sip-tester  - version 3.2.1). For example support for playing pcap files or computing authentication hashes. Build sipp with pcap support apt-get install autoconf libncurses5-dev libpcap-dev g++ cd /usr/local/src/ git clone https://github.com/SIPp/sipp.git cd sipp/ ./build.sh --with-pcap ./sipp is the built binary. You can see the version and capabilities with './sipp -v', e.g.: $ ./sipp -v SIPp v3.6-dev-149-gb95f98f-PCAP-RTPSTREAM. ... This version will be able to use actions like exec rtp_stream="file.wav" or exec play_pcap_audio="pcap/g711a.pcap" (see details in current documentation ). A little caveat for 'rtp_stream' and WAV files . As the documentation says sipp expects a WAV file encoded with PCAM ('A-law'). You can also loop that audio for as long as you need, by adding '...

SIP is a relatively simple, text-based, human readable protocol that is now the standard de facto for VoIP signalling. The protocol though (in my opinion!) is a little tricky, where typically the tricks are: details . In this first post of a series of "Trip-wires for the SIP fans", I'll talk about CANCEL. The main concept is easy: a caller may decide to cancel a call before this is answered. To do this, it sends a CANCEL request to the called party. What's important to know is that: A CANCEL request relates to an INVITE request, and does not relate to the SIP dialog the request may have created (or will create). For this reason the To header tag must be the same as the INVITE request, even if meanwhile there's been a provisional response to the INVITE creating a dialog (e.g. a 180 with a tag in the To header). From RFC 3261, 9.1 : The following procedures are used to construct a CANCEL request.  The    Request-URI, Call-ID, To, the numeric part of ...