11 Commits (aea277dbbe271b26f0b8735591a391e1746c6f69)

Author	SHA1	Message	Date
Eric Green	aea277dbbe	Add a mutex lock for recording to ensure thread safety when writing to pcap	10 years ago
Dylan Mikus	fa8146f053	Fixes for recording packet counter ... - The packet counter was accidentally a pointer, resulting in it incrementing by 8 instead of 1. That is fixed. - Use proper formatting macro for uint64_t printing. - Start PCAP packet indexing at 1 since that is what Wireshark does.	10 years ago
Dylan Mikus	5fe68b9097	Link recording metadata SDP to RTP packet numbers ... We write out what RTP packet number the SDP came before. When we receive an SDP offer or answer, we write out the RTP packet number that the SDP preceeded. This will let us split the RTP recording PCAP around SDP renegotiation for things like hold/unhold. Also write out whether the SDP was an offer or an answer.	10 years ago
Dylan Mikus	adb6193891	Minorly adjusted the recording metadata file format ... In the recording metadata files, we now separate each logical section of metadata by two blank lines. So, it goes: 1. the PCAP file URL 2. two blank lines 3. all answer SDP, each separated by one blank line 4. two blank lines 5. start timestamp 6. end timestamp (no blank line in between) 7. the rest of the file is unstructured metadata (any number of lines)	10 years ago
Dylan Mikus	d09f34a70b	Updates to description of metadata file format ... Added the answer SDP lines to the file format description.	10 years ago
Dylan Mikus	0b33b4815a	Write out rewritten SDP from answer to metadata file	10 years ago
Dylan Mikus	466c52c18e	Refactored recording setup to streamline it ... We had initialization code for recording scattered through "call_interfaces.c", "call.c", and "recording.c". I moved more of the actual code into functions within recording.c under the parent function `detect_setup_recording`. We call this function from "call_interfaces.c". I moved the disjointed bit of PCAP initialization to occur right below where we toggle recording on or off.	10 years ago
Dylan Mikus	b3d6073447	Prefix recording metadata and pcap files with call id ... We want to be able to associate call files with a call without the presence of identifying metadata within the metadata file. To accomplish this, we prepend the call-id to the start of the pcap recording files and the call metadata files. Even though call-id is supposed to be unique, because of paranoia we keep some of the random affix hex string, but we reduced it down to an 8-byte random value. Also, some minor argument ordering and name refactoring for random string generation functions.	10 years ago
Dylan Mikus	1af73c665a	Fixed description of metadata file format to list just one pcap file. ... Now that all RTP streams for a call go to the same PCAP file, we don't need a list of multiple PCAP files. We still separate it from the timestamps by an extra newline.	10 years ago
Dylan Mikus	7acc3239d2	Write out unique ip:port pairs for all streams. ... We should do some more checking to make sure we're using the correct values for source and destination ip:port pairs.	10 years ago
Dylan Mikus	f516684ade	All RTP packet data for a call goes to one PCAP file. ... This involved moving all code from fs.(c|h) to recording.(c|h). We still spoof packets, so the UDP will look like all monologues are coming over the same port and will probably look like they are all one stream if you look at the PCAP file.	10 years ago