
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options. Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well. Thanks, -- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net

http://sipcapture.org/ works great. Good team. They have a commercial product as well. From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nelson Hicks Sent: Tuesday, March 24, 2015 9:47 AM To: voiceops at voiceops.org Subject: [VoiceOps] SIP packet capture with index I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options. Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well. Thanks, -- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net<mailto:nelsonh at socket.net>

Voipmonitor.org is the BOMB! It does all of this plus analyzes the pcap for you. 9 times out of 10 you don't even have to touch the pcap. It's saved my team 100's of hours of the past 12 month. I literally cannot say enough nice things about it. dw On Tue, Mar 24, 2015 at 10:47 AM, Nelson Hicks <nelsonh at socket.net> wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- [image: Ringfree Communications, Inc] <http://ringfree.biz/> David Wessell / President 828-575-0030 x101/ david at ringfree.biz Ringfree Communications, Inc Office: 828-575-0030 / Fax: 888-243-7830 PO BOX 1994 Hendersonville, NC 28793 http://ringfree.biz This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.

We use this and find it very easy to use: http://www.voipmonitor.org/ On Tue, Mar 24, 2015 at 7:47 AM, Nelson Hicks <nelsonh at socket.net> wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've found that sngrep works great for finding calls and other SIP traffic inside packet captures. I'm not sure if it'll handle that many packet captures, but I've never tested it. Thank you, Michael Englehorn On 3/24/2015 9:47 AM, Nelson Hicks wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net <mailto:nelsonh at socket.net>
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVEXngAAoJELn0PzaYIQ6g+LMP/2oe054fydcovj4h3GY+Mvvb +ZKwGYMZDZzY24oprzzbKsQS7mBaNdH6fMV8pu5zoia0aAi91k6CuM+dMVrqe6dh b6/1veRv/SK2MOVHRcD9wLlybc3tP23EOZ5Sw1ii0tIyIKQp3wym6AWllRFsHYYa vlMESIn0mRqq7CfE2tbu558kgQtME2ucXvr2fpM2O71fpdvPj/3KB05frL6AaAJC /vRnRt+QFzMSD57ZGy/h5zh0zSNMT5IIglfhrz3/NFsDiaYM6aFMoqYZYuf2TOIA EQFPK+Nn3P1kG8k/vB1w8Ac5ojcpRba88VviaeQyW2TsoroDNTemEVWVyiLNXTEi zaqmuWbl++H0rGgDtfkm1rPbH9hV9qCO2K7LvzUasA+4LYCUqkgHLKzbx+ZwxE1+ pI1yqGR+3nj78KJFgGNDXRjviCICEf4X68e1sJv20xkLCJEZ7LqJSDR9UsxNTXaf 1T8AwztJqrE+4SfXIMjdod0yYi8PxbLJ4SnT/55NdPAL8oBrKmcPueDV6AwdunjA DfBGXrnFMyAw4FkaWA7/C6MOZ5N7APVSGzXxTGoKE2Q/RDK+1widVrUVJ1v9BvOT n85vYDLwK9ssb3fy1iF395XGfpWvyXMkQm4C2ANuRg4FxdUYmbL4PtYUqdyxpBig 40SFH9CAmg08WO+SGFh+ =6dc1 -----END PGP SIGNATURE-----

http://www.voipmonitor.org/ <http://www.voipmonitor.org/> It works, it is awesome, it is inexpensive. Our techs live in voipmon to debug issues, awesome product. -- Matthew S. Crocker President Crocker Communications, Inc. PO BOX 710 Greenfield, MA 01302-0710 E: matthew at crocker.com P: (413) 746-2760 F: (413) 746-3704 W: http://www.crocker.com
On Mar 24, 2015, at 10:47 AM, Nelson Hicks <nelsonh at socket.net> wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net <mailto:nelsonh at socket.net>_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

+1 on voipmonitor works amazingly well.
On Mar 24, 2015, at 10:51 AM, Matthew Crocker <matthew at corp.crocker.com> wrote:
http://www.voipmonitor.org/ <http://www.voipmonitor.org/>
It works, it is awesome, it is inexpensive.
Our techs live in voipmon to debug issues, awesome product.
-- Matthew S. Crocker President Crocker Communications, Inc. PO BOX 710 Greenfield, MA 01302-0710
E: matthew at crocker.com <mailto:matthew at crocker.com> P: (413) 746-2760 F: (413) 746-3704 W: http://www.crocker.com <http://www.crocker.com/>
On Mar 24, 2015, at 10:47 AM, Nelson Hicks <nelsonh at socket.net <mailto:nelsonh at socket.net>> wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net <mailto:nelsonh at socket.net>_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Voipmonitor +1 On Tue, Mar 24, 2015 at 8:25 AM, Calvin Ellison <calvin.ellison at voxox.com> wrote:
Voipmonitor +1
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- --- MICHAEL RICORDEAU | CO-FOUNDER Mobile: +1-415-430-5338 Plivo, Inc. 340 Pine St, San Francisco - 94104, USA Web: www.plivo.com | Twitter: @plivo, @mricordeau

Ok, the other question I'm currently getting beat up on, for anyone using this to capture RTP streams as well as SIP, how long do you try to retain RTP captures for? How much storage do you have set aside for this? Thanks, -- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net On Tue, 2015-03-24 at 08:52 -0700, Mike wrote:
Voipmonitor +1
On Tue, Mar 24, 2015 at 8:25 AM, Calvin Ellison <calvin.ellison at voxox.com> wrote:
Voipmonitor +1
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Yes, voipmonitor can retain RTP, and access controls permit you to restrict who can download SIP vs. RTP for privacy concerns. Retention is largely based on how much you want to invest in storage; their support can probably tell you if there are any hard or soft limits on retention. Voipmonitor is very configurable regarding what it captures, and very detailed in the reporting. Regards, *Calvin Ellison* Voice Services Engineer calvin.ellison at voxox.com +1 (213) 285-0555 ----------------------------------------------- *voxox.com <http://www.voxox.com/> * 9276 Scranton Rd, Suite 200 San Diego, CA 92121 [image: Voxox] On Tue, Mar 24, 2015 at 6:48 AM, Nelson Hicks <nelsonh at socket.net> wrote:
Ok, the other question I'm currently getting beat up on, for anyone using this to capture RTP streams as well as SIP, how long do you try to retain RTP captures for? How much storage do you have set aside for this?
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net
On Tue, 2015-03-24 at 08:52 -0700, Mike wrote:
Voipmonitor +1
On Tue, Mar 24, 2015 at 8:25 AM, Calvin Ellison <calvin.ellison at voxox.com> wrote:> Voipmonitor +1>>> _______________________________________________> VoiceOps mailing list> VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops>

VoipMonitor lets you store just the RTP headers so you can still see the quality stats but cut down on disk space and creepiness (listening) issues. I store about 30 days of RTP header data - and 90 days of CDR data on VoipMonitor for troubleshooting. --- Christopher Aloi Sent from my iPhone
On Mar 24, 2015, at 12:48 PM, Nelson Hicks <nelsonh at socket.net> wrote:
Ok, the other question I'm currently getting beat up on, for anyone using this to capture RTP streams as well as SIP, how long do you try to retain RTP captures for? How much storage do you have set aside for this?
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net
On Tue, 2015-03-24 at 08:52 -0700, Mike wrote: Voipmonitor +1
On Tue, Mar 24, 2015 at 8:25 AM, Calvin Ellison <calvin.ellison at voxox.com> wrote:
Voipmonitor +1
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Nelson, Homer is a great open source tool for basic troubleshooting. Pcapture, which is the commercial version of it, can provide additional functionality. Google both. There is plenty of information online. Regards, Brad Anouar On Mar 24, 2015 7:47 AM, "Nelson Hicks" <nelsonh at socket.net> wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Another vote for VoIP monitor. --- Christopher Aloi Sent from my iPhone
On Mar 24, 2015, at 10:47 AM, Nelson Hicks <nelsonh at socket.net> wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

VoIPMonitor has been great for us as well. -- Jason Park From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nelson Hicks Sent: Tuesday, March 24, 2015 9:47 AM To: voiceops at voiceops.org Subject: [VoiceOps] SIP packet capture with index I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options. Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well. Thanks, -- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net<mailto:nelsonh at socket.net>

Another vote for voipmonitor. Geoff Mina CEO & Founder Connect First, Inc. 720.335.5924<tel:720.335.5924> www.connectfirst.com<http://www.connectfirst.com> On Tue, Mar 24, 2015 at 9:09 AM -0700, "Jason Park Personal" <jason at jasonpark.com<mailto:jason at jasonpark.com>> wrote: VoIPMonitor has been great for us as well. -- Jason Park From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nelson Hicks Sent: Tuesday, March 24, 2015 9:47 AM To: voiceops at voiceops.org Subject: [VoiceOps] SIP packet capture with index I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options. Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well. Thanks, -- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net<mailto:nelsonh at socket.net>

We capture 100% of our SIP traffic using tcpdump and logging 14 files at 100MB per file (1.5GB rough usage). We have at least a few days worth of SIP packets to review if necessary. Use tshark to find sets of connected data. This command line does all the rotation and capture for us: /usr/sbin/tcpdump -qpni eth0 -s 65535 -C 100 -W 14 -Z root -w /var/log/sip.pcap port 5060 -q Quick (quiet?) output. Print less protocol information so output lines are shorter. -p Don?t put the interface into promiscuous mode. -n Don?t convert host addresses to names. -i Interface (eth0 here) -s Snarf snaplen bytes of data from each packet rather than the default of 68. -C Magic Sauce. Before writing a raw packet to a savefile, check whether the file is currently larger than file_size and, if so, close the current savefile and open a new one. Savefiles after the first savefile will have the name specified with the -w flag, with a number after it, starting at 1 and continuing upward. The units of file_size are millions of bytes (1,000,000 bytes, not 1,048,576 bytes). -W Used in conjunction with the -C option, this will limit the number of files created to the specified number, and begin overwriting files from the beginning, thus creating a ?rotating? buffer. In addition, it will name the files with enough leading 0s to support the maximum number of files, allowing them to sort correctly. -Z Drops privileges (if root) and changes user ID to user and the group ID to the primary group of user. This behavior is enabled by default (-Z pcap), and can be disabled by -Z root. -w Write the raw packets to file rather than parsing and printing them out. They can later be printed with the -r option. Standard output is used if file is ??-??. On Tue, 24 Mar 2015, Nelson Hicks wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------

Thanks for the excellent reply here - I know i will refer to this down the road. Curious, how do you use the raw files ? --- Christopher Aloi Sent from my iPhone
On Mar 24, 2015, at 10:22 PM, Peter Beckman <beckman at angryox.com> wrote:
We capture 100% of our SIP traffic using tcpdump and logging 14 files at 100MB per file (1.5GB rough usage).
We have at least a few days worth of SIP packets to review if necessary. Use tshark to find sets of connected data.
This command line does all the rotation and capture for us:
/usr/sbin/tcpdump -qpni eth0 -s 65535 -C 100 -W 14 -Z root -w /var/log/sip.pcap port 5060
-q Quick (quiet?) output. Print less protocol information so output lines are shorter.
-p Don?t put the interface into promiscuous mode.
-n Don?t convert host addresses to names.
-i Interface (eth0 here)
-s Snarf snaplen bytes of data from each packet rather than the default of 68.
-C Magic Sauce. Before writing a raw packet to a savefile, check whether the file is currently larger than file_size and, if so, close the current savefile and open a new one. Savefiles after the first savefile will have the name specified with the -w flag, with a number after it, starting at 1 and continuing upward. The units of file_size are millions of bytes (1,000,000 bytes, not 1,048,576 bytes).
-W Used in conjunction with the -C option, this will limit the number of files created to the specified number, and begin overwriting files from the beginning, thus creating a ?rotating? buffer. In addition, it will name the files with enough leading 0s to support the maximum number of files, allowing them to sort correctly.
-Z Drops privileges (if root) and changes user ID to user and the group ID to the primary group of user. This behavior is enabled by default (-Z pcap), and can be disabled by -Z root.
-w Write the raw packets to file rather than parsing and printing them out. They can later be printed with the -r option. Standard output is used if file is ??-??.
On Tue, 24 Mar 2015, Nelson Hicks wrote:
I'm looking for options to capture SIP/RTP traffic, index it by call, and make it easy to download the capture for a specific call based on calling/called and time. I want the capture to remain ongoing (rotating capture) with, say, a 96 hour window of calls available. I'm open to hardware and software options.
Right now, I have a server that uses tshark running rotating 1-minute captures, but finding and extracting an individual call out of each of the packet segments and merging them together is a slower and more manual process than I'd like, and I'd like to get our techs direct access to these captures as well.
Thanks,
-- Nelson Hicks Network Operations SOCKET (573) 817-0000 ext. 210 nelsonh at socket.net
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

?They can be ingested by tshark and searched based on SIP attributes (e.g. sip.Call-ID). This is how we do troubleshooting, too. In the end, it's far faster than most high-level tools, and readily provides the low-level SIP data that is often essential to solving nontrivial problems. -- Alex?Balashov?|?Principal?|?Evariste?Systems?LLC 303?Perimeter?Center?North,?Suite?300 Atlanta,?GA?30346 United?States Tel:?+1-800-250-5920?(toll-free)?/?+1-678-954-0671 (direct) Web:?http://www.evaristesys.com/, http://www.csrpswitch.com/ Sent?from?my?BlackBerry.
participants (15)
-
abalashov@evaristesys.com
-
beckman@angryox.com
-
brad.anouar@masergy.com
-
caalvarez@gmail.com
-
calvin.ellison@voxox.com
-
ctaloi@gmail.com
-
david@ringfree.biz
-
gmina@connectfirst.com
-
jason@jasonpark.com
-
jjackson@aninetworks.net
-
matthew@corp.crocker.com
-
michael@englehorn.com
-
mike@plivo.com
-
nelsonh@socket.net
-
shripald@gmail.com