rtpengine

3.0 GiB

Tree: a714fbc462

Author	SHA1	Message	Date
Dylan Mikus	a714fbc462	Record RTP in PCAP files in the /tmp directory. RTP Engine creates PCAP files for recorded calls on offer answer instead of initial offer. We make up bogus values for the nonessential parts of the PCAP, UDP, and IP headers. We might be able to pull these from other parts of the RTP Engine, but that information was unnecessary for recording calls so they can be recorded to audio files. If you change the packet headers, be really careful about byte order and datatype size!	10 years ago
Eric Green	70eb6b9e81	Record raw RTP to recording files on the filesystem. Pass in "record-call" flag over `rtpengine_offer` or `rtpengine_answer` message. RTP Engine tracks files used to record pcaps and send them back in the response message. Pipes call audio (unencrypted from both ends) to recording files. Sets up file descriptors for local files to dump RTP recordings. A file and a file descriptor per monologue in a call. Recorded streams will be running in user daemon mode, not in kernel mode. This removes first 12 octets from packet to record just the rtp.	10 years ago
Richard Fuchs	b82812260d	move advertised_address out of intf_spec into local_intf supports aliasing a local interface multiple times with the same local address for different advertised addresses closes #216 Change-Id: I6f98d1a17290b0bb1831e48ad89fc61d8b2d7914	10 years ago
Richard Fuchs	6d3865b971	Mass update - manual merge of rfuchs/socket-rework branch This brings master up to date with branch `rfuchs/socket-rework` at commit `b1bcc096b7`. The branches have diverged too much for a proper merge, so this is a manual (squashed) merge. The old master before this merge can be found in branch `old-master-before-socket-rework` (commit `82199216b2`). This is a complete rewrite of all socket handling routines. The most important functional change is that sockets aren't indiscriminately bound to INADDR_ANY (or rather in6addr_any), but instead are always bound to their respective local interface address and with the correct address family. Side effects of this are that in multi-homed environments, multiple sockets must be opened (one per interface address and family) which must be taken into account when considering RLIMIT_NOFILE values. As a benefit, this change allows rtpengine to utilize the full UDP port space per interface address, instead of just one port space per machine. The socket abstraction also makes it possible to support RTP over TCP in the future. Change-Id: If6cf4f42136229490186d2d2482fb4fc140c2b53	10 years ago

4 Commits (a714fbc462588647d52e1190057dd30e76a5a5a3)