Architecture: Difference between revisions
(Created page with "VoIPmonitor architecture is made from sensors (sniffers) which stores CDR to database. The CDR stores signalization informations (like length of call, start of the call etc.) ...") |
No edit summary |
||
| Line 1: | Line 1: | ||
VoIPmonitor architecture | VoIPmonitor architecture allows running multiple sensors and one MySQL/HTTP server. Stored CDR in database stores signalization informations (like length of call, start of the call etc.) and QOS for RTP stream. It also can create pcap files which stores all packets for particular call (SIP or SIP+RTP) and those pcap files are stored as files on local file systems. The sniffer can listen on single network interface (like eth0) or on all interfaces. The most common scenario is to install sniffer on dedicated server mirroring traffic from switch. It is also often installed directly on production PBX/SBC if it is linux based. In this case - you should take care about system resources to not influence the other parts of system (asterisk, etc.). All type of sniffing is described in chapter [[sniffing modes]]. | ||
VoIPmonitor WEB interface reads CDR from database and does various statistics from it - like ACD, ASR. WEB interface is usually installed directly on the sniffer server but it can be installed on standalone linux instance alongside with mysql database. | VoIPmonitor WEB interface reads CDR from database and does various statistics from it - like ACD, ASR. WEB interface is usually installed directly on the sniffer server but it can be installed on standalone linux instance alongside with mysql database. | ||
Revision as of 16:24, 17 May 2013
VoIPmonitor architecture allows running multiple sensors and one MySQL/HTTP server. Stored CDR in database stores signalization informations (like length of call, start of the call etc.) and QOS for RTP stream. It also can create pcap files which stores all packets for particular call (SIP or SIP+RTP) and those pcap files are stored as files on local file systems. The sniffer can listen on single network interface (like eth0) or on all interfaces. The most common scenario is to install sniffer on dedicated server mirroring traffic from switch. It is also often installed directly on production PBX/SBC if it is linux based. In this case - you should take care about system resources to not influence the other parts of system (asterisk, etc.). All type of sniffing is described in chapter sniffing modes.
VoIPmonitor WEB interface reads CDR from database and does various statistics from it - like ACD, ASR. WEB interface is usually installed directly on the sniffer server but it can be installed on standalone linux instance alongside with mysql database.
All in one
If the sensor is installed on the same server as MySQL and WEB server you do not need to configure sensors in GUI. The GUI is reading PCAP files directly from local file system and database are connected via localhost mysql database.
Multiple remote sensors one DB/WEB server
If sensors are remote it have to write CDR to remote database. MySQL must listen not only on localhost (my.cf -> bind = 0.0.0.0)