sipwise
/
rtpengine
mirror of https://github.com/sipwise/rtpengine.git
1
0
Fork 0
Code Issues Releases Wiki Activity

added note to readme about recording-daemon

Browse Source
pull/508/head
Juha Heinanen 8 years ago
parent fb04399465
commit 217446ce89
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

4
README.md
Unescape View File

@ -583,8 +583,8 @@ The options are described in more detail below.
The recording method `proc` works by writing metadata files directly into the The recording method `proc` works by writing metadata files directly into the
`recording-dir` (i.e. not into a subdirectory) and instead of recording RTP packet data `recording-dir` (i.e. not into a subdirectory) and instead of recording RTP packet data
into pcap files, the packet data is exposed via a special interface in the `/proc` filesystem. into pcap files, the packet data is exposed via a special interface in the `/proc` filesystem.
Packets must then be retrieved from this interface by a dedicated 3rd party userspace component Packets must then be retrieved from this interface by a dedicated userspace component
(usually a daemon). (usually a daemon such as recording-daemon included in this repository).
Packet data is held in kernel memory until retrieved by the userspace component, but only a limited Packet data is held in kernel memory until retrieved by the userspace component, but only a limited
number of packets (default 10) per media stream. If packets are not retrieved in time, they will number of packets (default 10) per media stream. If packets are not retrieved in time, they will

Write Preview
Loading…
Cancel
Save