Difference between revisions of "Architecture"
| Line 11: | Line 11: | ||
If sensors are remote it needs to be configured to do so. | If sensors are remote it needs to be configured to do so. | ||
| − | *TCP manager interface must listen not only on localhost so the GUI server can reach it. In | + | *TCP manager interface must listen not only on localhost so the GUI server can reach it. In voipmonitor.conf set managerip = 0.0.0.0 |
*Set mysql in voipmonitor.conf to store to remote database | *Set mysql in voipmonitor.conf to store to remote database | ||
*set id_sensor to some number (this is required) | *set id_sensor to some number (this is required) | ||
Revision as of 16:27, 7 June 2013
Architecture
VoIPmonitor architecture allows running multiple sensors (linux) and one MySQL/HTTP server. Call detail records (CDR) are saved over MySQL TCP protocol to local or remote database and pcap files (which stores SIP and RTP packets) are saved on local sensor storage. WEB GUI reads CDR from database and can read pcap files from local disk (in all in one setup) or directly from the sniffer over TCP manager interface (on port 5029).
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 needs to be configured to do so.
- TCP manager interface must listen not only on localhost so the GUI server can reach it. In voipmonitor.conf set managerip = 0.0.0.0
- Set mysql in voipmonitor.conf to store to remote database
- set id_sensor to some number (this is required)
- In the GUI add the sensor in Settings#Sensors
Sniffing packets
VoIPmonitor sniffer can run only on Linux. You can compile it or download static binaries and run it directly on your PBX / SBC. But although the sniffer was designed to handle thousands of simultaneous calls it is recommended to install it on dedicated Linux server (which can be also virtual).
The sniffer can listen only on one interface or on all interfaces (interface=any). For more information refer to sniffer manual.
Mirroring packets
Hardware mirroring
If the sniffer cannot run directly on PBX/SBC you need to mirror packets to sniffer server. The most common approach is to do it in hardware switch. This feature is called spanning or mirroring ports. Check if your switch can do this. Some PBX/SBC are capable of mirroring VoIP using IP in IP protocol which voipmonitor supports natively (enabled by default).
Software mirroring
If your switch lacks mirroring feature you can mirror packets using Linux iptables feature or you can set sniffer in only special mirror mode which sniffs on the PBX/SBC all packets and mirrors them to central sniffer server over IPinIP protocol. For more details refer to sniffer manual.