User contributions for Petr.halounek

16:2516:25, 20 December 2024 diff hist +1‎ Multiple sniffer instancies ‎ →‎How to start more sniffer instancies in a single host current
16:2416:24, 20 December 2024 diff hist +1‎ Multiple sniffer instancies ‎ →‎How to start more sniffer instancies in a single host
16:2316:23, 20 December 2024 diff hist +16‎ Multiple sniffer instancies ‎ →‎How to start more sniffer instancies in a single host
16:2116:21, 20 December 2024 diff hist +218‎ Multiple sniffer instancies ‎No edit summary
16:1716:17, 20 December 2024 diff hist +1,468‎ N Multiple sniffer instancies ‎ Created page with "=How to start more sniffer instancies in a single host= t.e. useful to distinct between calls which came via which network interface of a single host in a GUI (using id_sensor) If a single instance is runing ok there - you can add manually second instance by a following way: == copy of a binary== cp -a /usr/local/sbin/voipmonitor /usr/local/sbin/voipmon2 == copy the init script and modify it to control voipmon2== cp /etc/init.d/voipmonitor /etc/init.d/voipmonitor/v..."
16:0416:04, 20 December 2024 diff hist +94‎ FAQ ‎No edit summary current

15:4515:45, 24 September 2024 diff hist +10‎ DTLS ‎No edit summary current
15:1415:14, 24 September 2024 diff hist +7‎ DTLS ‎No edit summary
15:1215:12, 24 September 2024 diff hist 0‎ DTLS ‎ →‎Special options
15:1215:12, 24 September 2024 diff hist −11‎ DTLS ‎ →‎Special options
15:1115:11, 24 September 2024 diff hist −14‎ DTLS ‎ →‎Details
15:0915:09, 24 September 2024 diff hist +3,643‎ N DTLS ‎ Created page with "DTLS (Datagram Transport Layer Security) is a protocol used for securing the RTP voice or video streams. Voipmonitor uses the key received from the keylogger and from DTLS packets to make decryption possible DTLS packets preceeding the RTP streams. Because the use of a keys from DTLS packets is possible after RTP packets arrives, and after keylogger packets arrives voipmonitor needs to store the DTLS packets aside from call struct - It is putting DTLS packets into a se..."
14:4114:41, 24 September 2024 diff hist −592‎ Ubuntu 24.04 LTS ‎No edit summary
13:3413:34, 24 September 2024 diff hist +53‎ Internal support hints ‎No edit summary

17:3717:37, 9 September 2024 diff hist +5‎ Minimizing Delay Between Call End and CDR Database Storage ‎ →‎Setting the Flushing Buffers as Fast as Possible current
17:3717:37, 9 September 2024 diff hist +129‎ Minimizing Delay Between Call End and CDR Database Storage ‎ →‎Setting the Flushing Buffers as Fast as Possible
17:3117:31, 9 September 2024 diff hist +2‎ Minimizing Delay Between Call End and CDR Database Storage ‎ →‎Setting the Flushing Buffers as Fast as Possible
17:2417:24, 9 September 2024 diff hist +1,347‎ N Minimizing Delay Between Call End and CDR Database Storage ‎ Created page with "=Behavior= The VoIPmonitor sniffer service uses buffers for queuing inserts into the database. These buffers are either flushed to disk or processed from RAM, depending on the query_cache option (yes or no). When the database service performs well, the CDR can take up to 35 seconds after the call ends to appear in the database (and be visible in the GUI’s CDR view). ==Timeout after bye== 5 sec. There is a hardcoded 5-second timeout after the BYE is confirmed when no..."
16:3216:32, 9 September 2024 diff hist +2‎ FAQ ‎ →‎There is a delay between active calls view and the CDR view

Navigation menu