Tools: Difference between revisions

From VoIPmonitor.org
(Add documentation about IP lookup network masks and how /24 mask causes same hostname for multiple IPs in subnet)
(Rewrite: konsolidace a vylepšení struktury - zjednodušení IP lookup sekce, přidání tabulek, See Also)
 
Line 1: Line 1:
= Tools =
= Tools =


This page describes the diagnostic and utility tools available in the VoIPmonitor GUI.
Diagnostic and utility tools available in the VoIPmonitor GUI ('''GUI > Tools''').


== MTR ==
== MTR ==


MTR traces from VoIPmonitor WEB server to selected IP using Linux mtr tool (10 seconds, 10 packets).
Network path tracing from VoIPmonitor web server to a selected IP address using the Linux <code>mtr</code> tool.
 
* '''Duration:''' 10 seconds
* '''Packets:''' 10


[[File:tools-mtr.png]]
[[File:tools-mtr.png]]
Line 11: Line 14:
== IP Lookup ==
== 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'''.
Substitutes IP addresses with custom hostnames in CDR views and other displays. Takes precedence over DNS lookups.
 
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 ===
'''Enable:''' Settings > System Configuration > "database IP reverse lookup"


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.
{| class="wikitable"
! Mask !! Scope !! Example
|-
| /32 || Single IP only || 192.168.1.100/32 applies to only 192.168.1.100
|-
| /24 || Entire subnet (256 IPs) || 192.168.1.0/24 applies to 192.168.1.0 - 192.168.1.255
|}


For example, an entry for <code>192.168.1.0/24</code> with hostname "PBX" will cause ALL IPs in the 192.168.1.0/24 range to display as "PBX" in the GUI.
{{Note|1=If the same hostname appears for multiple IPs, the entry likely uses a subnet mask (e.g., /24). Change to '''/32''' for per-IP hostnames.}}
 
=== Solution: Fix Incorrect Hostnames ===
 
To have different hostnames for individual IPs in the same subnet:
 
# Navigate to '''GUI > Tools > IP lookup'''
# Find the IP entry that is causing the issue
# Change the network mask from the subnet value (e.g., /24) to '''32'''
# 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.


[[File:tools-iplookup.png]]
[[File:tools-iplookup.png]]
Line 42: Line 32:
== Prefix Lookup ==
== Prefix Lookup ==


Prefix lookup table substitutes numbers in places like CDR view, taking precedence over IP lookup/DNS. Enable by setting <code>ENABLE_SQL_CUSTOMER_PREFIX_LOOKUP</code> to <code>true</code> in <code>config/configuration.php</code>.
Substitutes phone numbers with custom labels in CDR views. Takes precedence over IP lookup and DNS.
 
'''Enable:''' Set <code>ENABLE_SQL_CUSTOMER_PREFIX_LOOKUP = true</code> in <code>config/configuration.php</code>


[[File:tools-prefixlookup.png]]
[[File:tools-prefixlookup.png]]
Line 48: Line 40:
== Load PCAP ==
== Load PCAP ==


Upload PCAP files (libpcap format: tcpdump, tshark, Wireshark, voipmonitor). Processed by:
Upload and process PCAP files (libpcap format from tcpdump, tshark, Wireshark) to create CDRs.


<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
Line 54: Line 46:
</syntaxhighlight>
</syntaxhighlight>


Change conf path in '''Settings > System Configuration > Upload sniffer conf path'''.
'''Config path:''' 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:
 
# Obtain a sample PCAP file containing the traffic type you want to monitor (VoLTE test call, WebRTC session, etc.)
# Log in to the VoIPmonitor GUI and navigate to '''Tools > Load PCAP'''
# Upload the PCAP file
# 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.
{{Tip|Use this feature for '''pre-deployment verification''' - upload sample traffic (VoLTE, WebRTC, etc.) to confirm VoIPmonitor can parse the protocol before deploying live mirroring.}}


== Batch Download CDR WAV ==
== Batch Download CDR WAV ==


Download WAVs in batch via CSV upload.
Download multiple audio recordings via CSV upload.


[[File:tools-batchwav.png]]
[[File:tools-batchwav.png]]


Example CSV:
'''CSV columns:'''
{| class="wikitable"
! Column !! Description
|-
| Telephone || Caller or Called number
|-
| Lead Number || Record identifier (exported with audio/PCAP)
|-
| Start Time || CDR timestamp (second pass uses +/-5 min if no exact match)
|}


[[File:tools-batchwav-examplecsv.png]]
[[File:tools-batchwav-examplecsv.png]]
'''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 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.
Creates a comprehensive diagnostic package for VoIPmonitor support escalation.


=== How to Generate a Debug Log ===
'''Contents:'''
* System info (OS, kernel, CPU, RAM)
* VoIPmonitor configuration
* Performance logs and errors
* Sensor status and capture stats
* Network/storage info


# Navigate to '''GUI > Tools > Generate debug log'''
'''How to use:'''
# Enter your email address where you want to receive the debug log link
# Navigate to '''Tools > Generate debug log'''
# Enter your email address
# Click '''Generate'''
# Click '''Generate'''
# The system will process and upload the debug report
# Share the received link with support
# A download link will be sent to your email address
# Share this link with VoIPmonitor support for analysis
 
=== What the Debug Report Contains ===


* System information (OS version, kernel, CPU, memory)
{{Warning|Use after initial troubleshooting fails. First check [[Settings#Sensor_Health_Monitoring_with_RRD_Charts|Sensor RRD Charts]] and logs.}}
* VoIPmonitor configuration files (<code>voipmonitor.conf</code>)
* 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 ===
 
# Use '''Settings > Sensor RRD charts''' to confirm buffer usage pattern ([[Settings#Sensor_Health_Monitoring_with_RRD_Charts|Settings: Sensor RRD Charts]])
# Adjust the '''From''' date to compare buffer usage before and after the issue started
# Correlate buffer usage spikes with the timing of errors and bad MOS scores
# Check kernel messages for storage errors: <code>dmesg -T</code>
# If unable to resolve, navigate to '''Tools > Generate debug log'''
# Enter your email and generate the report
# Share the provided link with VoIPmonitor support


[[File:tools-generatedebuglog.png]]
[[File:tools-generatedebuglog.png]]
Line 128: Line 92:
== Concurrent Calls Stats ==
== 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.
Displays maximum concurrent connected calls for the last 14 days, averaged over 60-minute windows.


Applies to GUI licensing. Counts all CDR legs (e.g., 100 calls with 2 legs = 200). License needed for actual calls (e.g., 100).
* '''Licensing:''' Counts all CDR legs (100 calls with 2 legs = 200 counted)
* '''Exceeded limit:''' Sniffer continues, but GUI warns/blocks after 14 days


If over license, sniffer continues but GUI warns/blocks in 14 days; contact support.
For license details, see [[License]].


[[File:tools-concurrentcallsstat.png]]
[[File:tools-concurrentcallsstat.png]]
== See Also ==
* [[Settings]] - System configuration and sensor management
* [[License]] - Channel licensing and limits
* [[GUI_troubleshooting]] - GUI debug mode and troubleshooting


== AI Summary for RAG ==
== 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.
'''Summary:''' VoIPmonitor GUI tools documentation covering: MTR (network path tracing from web server), IP Lookup (IP-to-hostname substitution with CIDR masks - /32 for single IP, /24 for subnet), Prefix Lookup (phone number substitution), Load PCAP (upload PCAP files for CDR creation and pre-deployment protocol verification), Batch Download WAV (bulk audio export via CSV), Generate Debug Log (diagnostic package for support), and Concurrent Calls Stats (license monitoring showing max concurrent calls over 14 days).


'''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
'''Keywords:''' tools, MTR, IP lookup, network mask, CIDR, /32, /24, hostname substitution, prefix lookup, PCAP upload, pre-deployment verification, batch WAV download, generate debug log, concurrent calls stats, license monitoring, VoLTE, WebRTC


'''Key Questions:'''
'''Key Questions:'''
* What is MTR in VoIPmonitor?
* What diagnostic tools are available in VoIPmonitor GUI?
* How to enable IP lookup in VoIPmonitor?
* How do I trace network path from VoIPmonitor server?
* Why does the same hostname appear for multiple different IP addresses?
* How do I substitute IP addresses with hostnames in CDR view?
* How do network masks work in IP lookup?
* Why does the same hostname appear for multiple IPs?
* How to fix incorrect hostnames showing for multiple IPs in the same subnet?
* How do network masks (/32 vs /24) work in IP lookup?
* What is the difference between /32 and /24 network masks in IP lookup?
* How do I enable prefix lookup for phone numbers?
* How to enable prefix lookup in VoIPmonitor?
* How do I upload PCAP files to VoIPmonitor?
* How to upload and process PCAP files?
* How can I verify if VoIPmonitor supports a specific protocol before deployment?
* How to verify if VoIPmonitor can monitor specific traffic types (VoLTE, WebRTC)?
* How do I download multiple audio files at once?
* What are concurrent calls stats and their licensing impact?
* How do I generate a debug log for VoIPmonitor support?
* How to generate a debug log for VoIPmonitor support?
* How do I check concurrent call statistics for licensing?

Latest revision as of 16:47, 8 January 2026

Tools

Diagnostic and utility tools available in the VoIPmonitor GUI (GUI > Tools).

MTR

Network path tracing from VoIPmonitor web server to a selected IP address using the Linux mtr tool.

  • Duration: 10 seconds
  • Packets: 10

IP Lookup

Substitutes IP addresses with custom hostnames in CDR views and other displays. Takes precedence over DNS lookups.

Enable: Settings > System Configuration > "database IP reverse lookup"

Mask Scope Example
/32 Single IP only 192.168.1.100/32 applies to only 192.168.1.100
/24 Entire subnet (256 IPs) 192.168.1.0/24 applies to 192.168.1.0 - 192.168.1.255

ℹ️ Note: If the same hostname appears for multiple IPs, the entry likely uses a subnet mask (e.g., /24). Change to /32 for per-IP hostnames.

Prefix Lookup

Substitutes phone numbers with custom labels in CDR views. Takes precedence over IP lookup and DNS.

Enable: Set ENABLE_SQL_CUSTOMER_PREFIX_LOOKUP = true in config/configuration.php

Load PCAP

Upload and process PCAP files (libpcap format from tcpdump, tshark, Wireshark) to create CDRs. 

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

Config path: Settings > System Configuration > "Upload sniffer conf path"

💡 Tip: Use this feature for pre-deployment verification - upload sample traffic (VoLTE, WebRTC, etc.) to confirm VoIPmonitor can parse the protocol before deploying live mirroring.

Batch Download CDR WAV

Download multiple audio recordings via CSV upload.

CSV columns:

Column Description
Telephone Caller or Called number
Lead Number Record identifier (exported with audio/PCAP)
Start Time CDR timestamp (second pass uses +/-5 min if no exact match)

Generate Debug Log

Creates a comprehensive diagnostic package for VoIPmonitor support escalation.

Contents:

  • System info (OS, kernel, CPU, RAM)
  • VoIPmonitor configuration
  • Performance logs and errors
  • Sensor status and capture stats
  • Network/storage info

How to use:

  1. Navigate to Tools > Generate debug log
  2. Enter your email address
  3. Click Generate
  4. Share the received link with support

⚠️ Warning: Use after initial troubleshooting fails. First check Sensor RRD Charts and logs.

File:Tools-generatedebuglog.png

Concurrent Calls Stats

Displays maximum concurrent connected calls for the last 14 days, averaged over 60-minute windows.

  • Licensing: Counts all CDR legs (100 calls with 2 legs = 200 counted)
  • Exceeded limit: Sniffer continues, but GUI warns/blocks after 14 days

For license details, see License.

See Also

AI Summary for RAG

Summary: VoIPmonitor GUI tools documentation covering: MTR (network path tracing from web server), IP Lookup (IP-to-hostname substitution with CIDR masks - /32 for single IP, /24 for subnet), Prefix Lookup (phone number substitution), Load PCAP (upload PCAP files for CDR creation and pre-deployment protocol verification), Batch Download WAV (bulk audio export via CSV), Generate Debug Log (diagnostic package for support), and Concurrent Calls Stats (license monitoring showing max concurrent calls over 14 days).

Keywords: tools, MTR, IP lookup, network mask, CIDR, /32, /24, hostname substitution, prefix lookup, PCAP upload, pre-deployment verification, batch WAV download, generate debug log, concurrent calls stats, license monitoring, VoLTE, WebRTC

Key Questions:

  • What diagnostic tools are available in VoIPmonitor GUI?
  • How do I trace network path from VoIPmonitor server?
  • How do I substitute IP addresses with hostnames in CDR view?
  • Why does the same hostname appear for multiple IPs?
  • How do network masks (/32 vs /24) work in IP lookup?
  • How do I enable prefix lookup for phone numbers?
  • How do I upload PCAP files to VoIPmonitor?
  • How can I verify if VoIPmonitor supports a specific protocol before deployment?
  • How do I download multiple audio files at once?
  • How do I generate a debug log for VoIPmonitor support?
  • How do I check concurrent call statistics for licensing?
Retrieved from "https://www.voipmonitor.org/doc/index.php?title=Tools&oldid=10018"