FAQ: Difference between revisions
No edit summary |
No edit summary |
||
Line 85: | Line 85: | ||
*login | *login | ||
*logout | *logout | ||
= PCI compliance = | |||
Voipmonitor is PCI compliance ready. Read following about ways on how to choose how force voipmonitor to skip record of sensitive data. | |||
== Don't record any payload == | |||
To prevent recording of sensitive data, you can use in global setting to not record payload of RTP packets - option savertp=no or savertp=header | |||
== Selectively choose what to NOT record == | |||
With savertp=yes in global settings, You can create exceptions in GUI -> capture rules and define for which IP/extension/domain/header to NOT record the payload of RTP (sensitive data) with SAVE RTP=OFF|HEADER | |||
== Selectively choose what to record == | |||
With savertp=no|header in global settings, You can create exceptions in GUI -> capture rules and define for which IP/extension/domain/header to record the payload of RTP (sensitive data)with SAVERTP=ON | |||
Revision as of 23:35, 20 June 2019
Scalability
How does voipmonitor scale?
Read this: Scaling
How to clean old data and database?
Read this: Data Cleaning
CDR
What is the red small icon in CDR?
The red icon in those columns signalize which side sends BYE first.
How to interpret two charts in the cdr detail?
See this: Graph cheat sheet
Supported architectures
What architectures are tested?
x86 32 and 64, ARMv5 - (if you have error with missing "__sync_fetch_and_sub_8" you have to upgrade GCC compiler to version 4.8)
Configuration
Why I do not see sip packets other then port 5060?
Voipmonitor sniffer by default sniffs packets only on port 5060 from or to. If you need to sniff more SIP ports you need to specify it in configuration. Please see this: Sniffer_configuration#sipport
How to disable timezone check
Go to settings -> System configuration -> Advanced section -> Hide timezone information -> Enable and set to TRUE
Licensing
How to know how many license channels do we need?
You can have unlimited number of phones / endpoints but you need to buy channels according to your maximum number of calls at the same time during peak.
Go to GUI -> Tools -> concurrent calls which will show peaks past 14 days. All multiple legs are already aggregated into single channel so you do not need to buy extra channels in case you have two or more CDR per one real call. The intention is to scale pricing based on real concurrent calls not accounting multiple legs of the same calls.
How does having multiple sensors affect the licensing? If I add a 2-3 remote sensors to the system, would they use the same license pool?
Central GUI calculates connected channels for the whole database but groups all calls legs as a single call so multiple legs are not counted twice etc.
accident / unwanted spikes
If your license is blocked due to high spike (accident / hack whatever) you need to delete those CDR from database via the GUI (filter those calls and in toolbar use delete buttons) and then try to unblock the license. If you do not want to delete them and you will have higher channels than your license for two consecutive days your license will be blocked after 14 days - you need to upgrade to higher channels license which you can do on voipmonitor.org portal.
DTMF
You can enable DTMF RFC2833 or DTMF SIP INFO in voipmonitor.conf by enabling:
dtmf2db = yes
You can also enable DTMF inband detection (only for G.711) by enabling (it will take some CPU)
inbanddtmf = yes
Bulk download of pcaps or audio (wav/ogg)
Read this: download of pcap files / audio files using GUI's api
GeoIP location services
Read this: order of GeoIP processing
Self signed certificate
Read this: Enable SSL/TLS + self signed certificate for http server
Corrupted GUI installation, how to reinstall the GUI
Read this: Re-install_the_GUI
Bad sniffer version, how to reinstall the sniffer to latest version
Read this: Latest_sniffer
What does Audit log cover
It covers these actions of users in the GUI:
- download wav
- download pcap
- play wav
- show fax
- batch download
- filter CDR in form
- login
- logout
PCI compliance
Voipmonitor is PCI compliance ready. Read following about ways on how to choose how force voipmonitor to skip record of sensitive data.
Don't record any payload
To prevent recording of sensitive data, you can use in global setting to not record payload of RTP packets - option savertp=no or savertp=header
Selectively choose what to NOT record
With savertp=yes in global settings, You can create exceptions in GUI -> capture rules and define for which IP/extension/domain/header to NOT record the payload of RTP (sensitive data) with SAVE RTP=OFF|HEADER
Selectively choose what to record
With savertp=no|header in global settings, You can create exceptions in GUI -> capture rules and define for which IP/extension/domain/header to record the payload of RTP (sensitive data)with SAVERTP=ON
Geek's/Developer's corner
Read this: Internal_support_hints
.