Tools

From VoIPmonitor.org
Revision as of 19:41, 7 January 2026 by Admin (talk | contribs) (Add documentation about IP lookup network masks and how /24 mask causes same hostname for multiple IPs in subnet)

Tools

This page describes the diagnostic and utility tools available in the VoIPmonitor GUI.

MTR

MTR traces from VoIPmonitor WEB server to selected IP using Linux mtr tool (10 seconds, 10 packets).

IP Lookup

IP lookup table substitutes IPs in places like CDR view, taking precedence over DNS. Enable via "database IP reverse lookup" in Settings > System Configuration.

Each entry consists of an IP address and a network mask (e.g., /24, /32). The mask determines how many IP addresses the entry applies to.

How Network Masks Work

  • /32 mask: Applies to a single IP address only (e.g., 192.168.1.100/32 → only 192.168.1.100)
  • /24 mask: Applies to an entire subnet of 256 IPs (e.g., 192.168.1.0/24 → all IPs from 192.168.1.0 to 192.168.1.255)
  • Other masks: Apply to larger or smaller ranges accordingly

Common Issue: Same Hostname for Multiple IPs

If you see the same hostname displayed for multiple different IP addresses within the same subnet, this typically means the IP lookup entry has a network mask larger than /32.

For example, an entry for 192.168.1.0/24 with hostname "PBX" will cause ALL IPs in the 192.168.1.0/24 range to display as "PBX" in the GUI.

Solution: Fix Incorrect Hostnames

To have different hostnames for individual IPs in the same subnet:

  1. Navigate to GUI > Tools > IP lookup
  2. Find the IP entry that is causing the issue
  3. Change the network mask from the subnet value (e.g., /24) to 32
  4. Save the changes

Using /32 ensures the hostname only applies to that specific IP address. Other IPs will fall back to DNS or use their own specific IP lookup entries.

Prefix Lookup

Prefix lookup table substitutes numbers in places like CDR view, taking precedence over IP lookup/DNS. Enable by setting ENABLE_SQL_CUSTOMER_PREFIX_LOOKUP to true in config/configuration.php.

Load PCAP

Upload PCAP files (libpcap format: tcpdump, tshark, Wireshark, voipmonitor). Processed by: 

voipmonitor --config-file /etc/voipmonitor.conf -r upload.pcap

Change conf path in Settings > System Configuration > Upload sniffer conf path.

Pre-Deployment Verification

This feature is commonly used to verify whether VoIPmonitor can monitor and parse specific types of traffic before full deployment. For example, to test VoLTE, WebRTC, or custom protocol implementations:

  1. Obtain a sample PCAP file containing the traffic type you want to monitor (VoLTE test call, WebRTC session, etc.)
  2. Log in to the VoIPmonitor GUI and navigate to Tools > Load PCAP
  3. Upload the PCAP file
  4. Check if CDRs (Call Detail Records) are created in the CDR view

If CDRs are successfully created from the uploaded PCAP, this confirms that VoIPmonitor can parse and monitor that specific traffic type. This is the recommended way to verify protocol compatibility without setting up live network mirroring.

Batch Download CDR WAV

Download WAVs in batch via CSV upload.

Example CSV:

Details:

  • Telephone: Caller or Called number.
  • Lead Number: Identifies record in CSV log (exported with audio/PCAP).
  • Start Time: Locates CDR; second pass uses +-5 minutes if not exact.

Generate Debug Log

Generate a comprehensive debug report for troubleshooting issues with VoIPmonitor support. This feature collects system information, configuration files, and diagnostic logs into a single package.

How to Generate a Debug Log

  1. Navigate to GUI > Tools > Generate debug log
  2. Enter your email address where you want to receive the debug log link
  3. Click Generate
  4. The system will process and upload the debug report
  5. A download link will be sent to your email address
  6. Share this link with VoIPmonitor support for analysis

What the Debug Report Contains

  • System information (OS version, kernel, CPU, memory)
  • VoIPmonitor configuration files (voipmonitor.conf)
  • Performance logs and recent error messages
  • Sensor status and capture statistics
  • Network and storage information
  • Database connection status

When to Use Generate Debug Log

After performing initial diagnostics and you need to escalate to VoIPmonitor support:

  • You have identified a sensor issue (e.g., via Settings > Sensor RRD charts) but cannot resolve it independently
  • System shows recurring errors like "packetbuffer: MEMORY IS FULL" that persist after configuration changes
  • You need detailed root cause analysis from VoIPmonitor developers
  • Diagnostics indicate a potential bug or unexpected behavior

Workflow Example: Troubleshooting "packetbuffer: MEMORY IS FULL" with Bad MOS

  1. Use Settings > Sensor RRD charts to confirm buffer usage pattern (Settings: Sensor RRD Charts)
  2. Adjust the From date to compare buffer usage before and after the issue started
  3. Correlate buffer usage spikes with the timing of errors and bad MOS scores
  4. Check kernel messages for storage errors: dmesg -T
  5. If unable to resolve, navigate to Tools > Generate debug log
  6. Enter your email and generate the report
  7. Share the provided link with VoIPmonitor support

File:Tools-generatedebuglog.png

Concurrent Calls Stats

Shows max concurrent calls (connected) stats for last 14 days, averaged over 60-minute windows: Max average from minute-by-minute counts.

Applies to GUI licensing. Counts all CDR legs (e.g., 100 calls with 2 legs = 200). License needed for actual calls (e.g., 100).

If over license, sniffer continues but GUI warns/blocks in 14 days; contact support.

AI Summary for RAG

Summary: This article describes VoIPmonitor GUI tools: MTR tracing from web server to selected IP, IP lookup table for substituting IPs in CDR views (with network masks explaining how /32 applies to single IPs and larger masks cover subnets, and how using subnet masks like /24 causes same hostname to display for multiple IPs in the same subnet - fixed by changing mask to 32), prefix lookup for number substitution, PCAP upload for pre-deployment verification of protocol support, batch WAV downloads, concurrent calls stats, and generate debug log for support escalation.

Keywords: MTR, IP lookup, network mask, CIDR, subnet mask, hostname display, same hostname multiple IPs, /32 mask, /24 mask, IP lookup table precedence over DNS, prefix lookup, PCAP upload, pre-deployment verification, batch WAV download, concurrent calls stats, generate debug log, VoLTE verification, WebRTC verification

Key Questions:

  • What is MTR in VoIPmonitor?
  • How to enable IP lookup in VoIPmonitor?
  • Why does the same hostname appear for multiple different IP addresses?
  • How do network masks work in IP lookup?
  • How to fix incorrect hostnames showing for multiple IPs in the same subnet?
  • What is the difference between /32 and /24 network masks in IP lookup?
  • How to enable prefix lookup in VoIPmonitor?
  • How to upload and process PCAP files?
  • How to verify if VoIPmonitor can monitor specific traffic types (VoLTE, WebRTC)?
  • What are concurrent calls stats and their licensing impact?
  • How to generate a debug log for VoIPmonitor support?
Retrieved from "https://www.voipmonitor.org/doc/index.php?title=Tools&oldid=9787"