License

This page explains how channel licensing works in VoIPmonitor, including what constitutes a channel, what happens when you exceed the limit, and how to resolve license lock issues.

What is a Channel License?

A channel license limits the number of concurrent calls processed by the VoIPmonitor GUI. Commercial licenses are sold with a specific channel cap (e.g., 100, 500, 1000 channels).

What Counts as a Channel?

A **channel** represents a **single, un-mergeable CDR leg** tracked and processed by VoIPmonitor.

Understanding channels requires distinguishing between "logical calls" (what users perceive as one conversation) and "CDR legs" (the technical records VoIPmonitor generates).

Basic Channel Counting

For typical call scenarios, VoIPmonitor counts **one channel per call**.

Important: License counting is performed by the GUI, which considers CDRs from all configured sensors (single or multiple servers). The GUI deduplicates multiple CDRs as a single license channel if the last 6 digits of the caller and called numbers are identical across all related CDRs.

This means that if you have multiple sniffers on different servers capturing the same call (for example, geo-redundancy or overlapping network mirrors), the GUI will correctly count this as one channel as long as the phone numbers match (last 6 digits).

For example:

• Call from 123456001 to 123456002 = 1 channel (caller and called share last 6 digits: 456001 and 456002)
• Call from 123456789 to 987654321 = 1 channel (different numbers do not merge)
• Multiple calls to different phone numbers are counted separately
• Same call captured by Server A and Server B = 1 channel (GUI deduplicates based on phone number match)

When One Logical Call Consumes Multiple Channels

A single logical phone conversation can generate **multiple separate CDR leg records** that VoIPmonitor cannot automatically merge. When this occurs, each un-mergeable leg is counted as an independent channel for licensing purposes.

This commonly happens in scenarios involving:

• Call transfers (attended or blind)
• Forking (parallel ringing to multiple destinations)
• Re-invites (media session renegotiation)
• Complex SIP routing (multiple proxies, B2BUA)

For example:

• Simple call: SIP Phone A calls SIP Phone B = 1 CDR = 1 Channel
• Complex call: SIP Phone A calls SIP Phone B, which forwards to SIP Phone C. If the transfer creates two distinct legs that cannot be merged, this counts as **2 Channels**.

Why Your License May Require More Channels Than Expected

If you request a license based on the number of users or logical calls (e.g., estimating 250 channels for 250 concurrent callers), but your traffic pattern involves frequent transfers or forking, the actual monitored volume of un-mergeable CDR legs will be higher. The license tier you receive reflects the reviewed usage pattern to ensure the monitoring system does not lock due to exceeding the channel limit.

What Happens When the License Limit is Exceeded?

When the channel count exceeds your license limit, VoIPmonitor has a grace period before locking:

1. **3-Day Grace Period:** You can exceed the limit for up to 3 consecutive days without any blocking 2. **Day 4 onwards:** The system begins a lockdown process 3. **After 14 Days:** The GUI locks completely

Effects of a Locked GUI

When the GUI becomes locked after exceeding the license limit for more than 14 consecutive days:

• **GUI becomes unusable:** You cannot access the web interface
• **Alerts are disabled:** No alert notifications will be sent
• **Reports are unavailable:** You cannot generate reports
• **CSV exports are blocked:** Data export functionality is disabled

What Still Works During Lock

Important: The sniffer continues to operate normally and record all CDRs to the database even when the GUI is locked. Your call data is not lost.

Resolving a License Lock

To unlock your VoIPmonitor GUI after it has been locked due to license limit overage:

Option 1: Upgrade Your License

The recommended solution is to upgrade to a larger channel limit. You can view available license tiers and upgrade directly through the voipmonitor.org portal:

1. Log in to the [[1]] portal 2. Navigate to Services → My services 3. Locate your active VoIPmonitor license in the service list 4. Click the UPGRADE button to view available license tiers 5. Select your desired license tier (e.g., higher channel limit) 6. Follow the checkout process to complete the upgrade 7. After purchase, download the new license key file 8. Install the new license key (see License Key File Location) 9. Restart the GUI service

Option 2: Contact Support for Temporary Increase

If you need immediate access to the GUI without upgrading, contact VoIPmonitor support to request a **temporary license limit increase**.

This is the recommended approach when:

• You need to troubleshoot why the channel count is higher than expected
• You believe the license check may be incorrectly counting unmerged CDRs
• You plan to upgrade later but need access now

Support can:

• Temporarily increase your channel limit to unlock the GUI
• Investigate whether the license check is incorrectly counting unmerged CDRs
• Make permanent license limit adjustments if counting errors are identified

After the temporary increase allows access, you can then decide whether to:

• Upgrade to a license tier that supports your expected concurrent call volume
• Keep your current tier if the issue was caused by incorrect CDR counting

Option 3: Increase License Limit (If Available)

If you already have a higher tier license available but the limit is currently set lower in your license key configuration:

1. Update your license key configuration to increase the channel limit 2. Restart the GUI service

Option 4: Remove and Re-compute CDRs

If you need to quickly unlock the GUI without upgrading:

# WARNING: This will delete all existing CDRs from the database
# Make sure you have backups or can re-compute from PCAP files

# Stop VoIPmonitor
systemctl stop voipmonitor

# Connect to MySQL and delete CDRs
mysql -u root -p voipmonitor

# Run these commands in MySQL
TRUNCATE TABLE cdr;
TRUNCATE TABLE cdr_next_partition;
-- Also truncate any cdr_partition_* tables
TRUNCATE TABLE cdr_partition_YYYYMM;
EXIT;

# Restart VoIPmonitor
systemctl start voipmonitor

After deleting the CDRs and restarting, the GUI will recalculate the channel count from the remaining data. If the count is now within the license limit, the GUI will unlock.

Note: This is a destructive operation. Only use this if you can afford to lose historical CDR data.

Option 5: Re-compute CDRs from PCAP Files

If you have PCAP files in your spool directory, you can re-compute CDRs after making changes:

# Stop VoIPmonitor
systemctl stop voipmonitor

# Delete old CDRs (see Option 3 above)

# Re-process PCAP files to regenerate CDRs with the new license settings
voipmonitor --config-file /etc/voipmonitor.conf --readpcapdir /var/spool/voipmonitor

# After processing completes, restart VoIPmonitor normally
systemctl start voipmonitor

Monitoring Your Channel Usage

You can check your channel usage and license limit in multiple ways:

Quick View (Current Status)

To see the current channel count:

1. Log in to the VoIPmonitor GUI 2. Check the footer or the **About/License** page (often found under the Gear icon or User menu) 3. Look for **Active channels** vs **License limit**

Historical View (Last 14 Days)

For license planning and capacity planning, use the dedicated concurrent calls report:

1. Navigate to Tools > Concurrent Calls Stats 2. This report shows maximum concurrent call statistics for the last 14 days 3. It is specifically designed for GUI licensing compliance 4. The data is averaged over 60-minute windows to provide a clear view of peak usage

This historical view is particularly useful when determining the required license size, as it allows you to identify your peak usage patterns over an extended period rather than relying on a single snapshot.

If you consistently hit the limit during peak hours, consider upgrading your license to avoid lock situations.

Troubleshooting Trial Expiration

When a trial period ends, users may see messages indicating their license has expired. Before assuming a new purchase is needed, follow these troubleshooting steps:

Step 1: Verify If a License Has Already Been Purchased

The first and most important step is to check if a license purchase has already been completed in the system:

1. Log in to the voipmonitor.org portal 2. Navigate to Services > My services 3. Check for any active or pending VoIPmonitor license orders 4. Verify the order status (completed, pending, processing)

If a license has already been purchased but is not yet active:

• Check if the order is still being processed (may take a few minutes to hours)
• Verify the license key has been delivered to the correct email address
• Contact VoIPmonitor support if the order status is unclear

Important: Many cases where users believe they need to purchase after trial expiration are actually resolved by finding an existing purchase that simply needs to be applied or activated.

Step 2: Apply the License Key

If a license purchase is confirmed but not yet applied:

1. Obtain the license key from the order confirmation email or portal 2. Apply the key using one of these methods:

  * GUI: Settings > About > License Key field
  * CLI: voipmonitor --set-license-key XXXX-XXXX-XXXX-XXXX
  * Config: Add license_key = "XXXX-XXXX-XXXX-XXXX" to voipmonitor.conf

3. Restart the VoIPmonitor service

Step 3: If No Purchase Found in System

Only after verifying that no purchase exists in the system should you guide the user to:

1. Purchase a license via the GUI (About > Buy License button) or voipmonitor.org store 2. Follow the activation steps above 3. Verify the license is displayed in the GUI About page

Common Scenarios

• Trial warning appears but license was purchased: The license key was obtained but not yet applied to the system. Apply the existing key instead of purchasing again.
• License purchased but not yet active: The order may still be processing. Check the order status in the portal.
• Multiple trial warnings sent: Automated warnings may continue until the new license key is applied and the service is restarted.

Subscription and Renewal Terms

VoIPmonitor licenses have a formal subscription structure with specific dates for renewal and cancellation. Understanding these terms is important when planning license renewals or cancellations.

License Period Structure

Each VoIPmonitor license has two key dates:

• Formal End Date: The official expiration date of your current license term. This is the date when your paid service period ends.
• Grace Period End Date: Approximately 20 days after the formal end date, provided for automatic renewal processing.

When a license is renewed, the new license key extends the formal end date beyond the current grace period end date.

Active Service Cancellations

If you cancel your VoIPmonitor subscription while the service is still active (before the formal end date):

• Access to the license and GUI features ends on the formal end date, not at the end of the grace period
• The 20-day grace period is for automatic renewal processing, not extended access after cancellation
• If you cancel or do not renew, your license will stop functioning when the formal end date is reached
• Plan any migrations or data exports before the formal end date if canceling

This can sometimes appear as "earlier than expected" revocation if you expected access to continue through the grace period. The grace period provides a buffer for renewal processing, not extended usage beyond the formal end date when a service is canceled.

Emergency Access During Transition

If your license expires due to payment delays or cancellation and you need immediate access:

• Contact VoIPmonitor support to request an emergency trial license
• Emergency trial licenses typically last 30 days
• This allows you to maintain service while resolving billing issues
• Apply the emergency license token in GUI > Settings > License section

For information on license channel limits and GUI lock behavior, see the sections above on channel licensing.

License Key File Location

The license key file is typically located at:

/var/www/html/voipmonitor/key.php

This file contains your license details including the channel limit. Updates to this file (e.g., when upgrading your license) should be provided by VoIPmonitor support.

Transferring a GUI License to a New System

You can transfer your GUI license to a new system installation without re-issuance. The license token can be used directly on the new installation.

Using Your Existing License

When moving to a new system:

• Copy your existing license file from the old installation
• Upload or install it on the new system
• Restart the GUI service

The license is typically stored at /var/www/html/voipmonitor/key.php.

Running Old and New Systems Concurrently

If you need to keep both the old and new systems running simultaneously during migration:

• Contact VoIPmonitor support to request a **temporary trial license**
• The trial license allows concurrent operation of both systems
• Use the trial license on the new system until migration is complete
• Cancel the trial when ready to retire the old system

This is the recommended approach when you cannot afford downtime during the transition.

OS Compatibility Notes

When installing on new operating systems, be aware of PHP version requirements:

• RHEL-based distributions (Alma Linux 9.5, Rocky Linux 9, CentOS 9)

 ** Install PHP 8.2 from the remi repository
 ** PHP 8.0 is not supported
 ** Install the ionCube loader that matches your PHP version
 ** Follow the official installation documentation for your target OS

See GUI_Installation for detailed installation instructions and ionCube loader setup.

Virtual Machine Clones

If you are cloning a virtual machine rather than performing a fresh installation:

• The license remains valid since the Machine ID is preserved
• No license changes are required
• However, avoid running identical clones concurrently as this may cause licensing conflicts

Resolving "license file key.php is for another hwid" Error

If you see the error message **"license file key.php is for another hwid"**, it indicates that the Hardware ID (HWID) of the current server does not match the HWID embedded in your license file (key.php). This typically occurs when:

• You migrated the installation to new physical or virtual hardware
• You restored a backup from a different environment (e.g., production to development)
• A cloud instance was terminated and re-created with a new instance ID

Solution: Use the "Get License" Button

This error can be resolved directly from the GUI without contacting support. The "Get License" button will automatically re-synchronize your license with the current server's HWID.

Steps

1. Log in to the VoIPmonitor GUI on the affected server
2. Navigate to Settings > License section
3. Click the "Get License" button to fetch and install a fresh license key file that matches the current HWID
4. Verify that the license status changes to OK

The system will automatically detect your server's HWID and regenerate the license accordingly.

When to Contact Support

In rare cases, clicking "Get License" may not resolve the issue. Contact VoIPmonitor support if:

• The error persists after clicking the "Get License" button
• You need to keep the old server running while setting up the new one (requires a temporary license)
• You are moving to a domain-based licensing model instead of hardware-bound licensing

Related Topics

• Billing - Learn about billing features and call cost calculation
• CDR_Summary - Pre-aggregated CDR data for faster queries
• Reports - Configure and generate VoIPmonitor reports
• GUI_Installation - GUI installation and upgrade procedures

AI Summary for RAG

Summary: VoIPmonitor channel licensing limits the number of concurrent calls processed by the GUI, with licenses sold in channel caps (e.g., 100, 500, 1000 channels). What is a channel: A channel represents a single, un-mergeable CDR leg tracked and processed by VoIPmonitor. This is a critical distinction: one logical phone conversation can generate multiple separate CDR leg records that VoIPmonitor cannot automatically merge. Each un-mergeable leg is counted as an independent channel for licensing purposes. Basic channel counting: License counting is performed by the GUI, which considers CDRs from ALL configured sensors (single or multiple servers). The GUI deduplicates multiple CDRs as a single license channel if the last 6 digits of the caller and called numbers are identical across all related CDRs. This means if multiple sniffers on different servers capture the same call (geo-redundancy or overlapping mirrors), the GUI correctly counts this as one channel as long as phone numbers match (last 6 digits). When one logical call consumes multiple channels: Common scenarios include call transfers (attended or blind), forking (parallel ringing to multiple destinations), re-invites (media session renegotiation), and complex SIP routing (multiple proxies, B2BUA). Example: Simple call Phone A to Phone B = 1 channel; Complex call Phone A to Phone B which forwards to Phone C = 2 channels if the transfer creates two distinct un-mergeable legs. Why license may require more channels than expected: If you request a license based on logical calls but your traffic pattern involves frequent transfers or forking, the actual monitored volume of un-mergeable CDR legs will be higher. The license tier reflects the reviewed usage pattern. Exceeding the limit consequences: 3-day grace period allows exceeding limit without block; after 3 consecutive days over limit, lockdown process begins; after 14 days total, GUI locks completely. When locked, GUI, alerts, reports, and CSV exports become unusable. The sniffer continues recording all CDRs to database even while locked (sniffer does NOT stop). Resolution options: (1) Upgrade license to higher channel limit (recommended), (2) Increase license limit if higher tier available, (3) Remove and re-compute CDRs from database (destructive - TRUNCATE TABLE cdr and cdr_next_partition, then restart), (4) Re-compute CDRs from PCAP files using --readpcapdir. Monitor usage: check GUI footer or About/License page (Gear icon or User menu) for Active channels vs License limit. For historical data and license planning, navigate to Tools > Concurrent Calls Stats which shows maximum concurrent call statistics for the last 14 days, averaged over 60-minute windows - this is specifically designed for GUI licensing compliance and helps identify peak usage patterns for determining required license size. License key file location: /var/www/html/voipmonitor/key.php (provided by VoIPmonitor support). Subscription and renewal terms: Each VoIPmonitor license has two key dates: (1) Formal End Date - the official expiration date when paid service period ends, (2) Grace Period End Date - approximately 20 days after formal end date for automatic renewal processing. When a license is renewed, the new license key extends the formal end date beyond the current grace period end date. Active service cancellations: If you cancel your subscription before the formal end date, access ends on the formal end date (NOT at the end of the grace period). The 20-day grace period is for automatic renewal processing, not extended access after cancellation. This can appear as "earlier than expected" revocation if you expected access to continue through the grace period. Plan migrations or data exports before formal end date if canceling. Emergency access: If license expires due to payment delays or cancellation, contact VoIPmonitor support to request an emergency trial license (typically 30 days) to maintain service while resolving billing issues. Apply emergency license token in GUI > Settings > License section. Transferring license to new system: Can transfer GUI license to new system installation without re-issuance. The existing license token can be used directly on new installation by copying the license file (typically /var/www/html/voipmonitor/key.php) and restarting GUI service. For concurrent operation of old and new systems during migration, contact support to request a temporary trial license. OS compatibility notes: For RHEL-based distributions (Alma Linux 9.5, Rocky Linux 9, CentOS 9), install PHP 8.2 from remi repository as PHP 8.0 is not supported. Install the ionCube loader that matches the PHP version. Virtual machine clones: License remains valid since Machine ID is preserved, no re-issuance needed, but avoid running identical clones concurrently. HWID mismatch error "license file key.php is for another hwid": This error occurs when the current server's Hardware ID (HWID) does not match the license file. Common causes: migration to new hardware, restoring backup from different environment, cloud instance termination and recreation. Solution: Use the "Get License" button in GUI Settings > License section to automatically re-synchronize the license with the current HWID. Steps: (1) Log in to GUI on affected server, (2) Navigate to Settings > License, (3) Click "Get License" button, (4) Verify license status changes to OK. The system automatically detects HWID and regenerates license. Only contact support if error persists or you need concurrent systems during migration.

Keywords: channel license, concurrent calls, license limit, GUI lock, license lock, exceed limit, grace period, 14 days lock, unlock GUI, upgrade license, CDR merging, un-mergeable CDR leg, CDR leg, logical call vs CDR leg, call transfer, attended transfer, blind transfer, forking, parallel ringing, re-invite, complex SIP routing, B2BUA, multiple channels per call, one conversation multiple channels, channel definition, what is a channel, channel meaning, caller called numbers, 6 digits, channel count per call, active channels, Tools Concurrent Calls Stats, Tools Concurrent Calls, concurrent calls history, historical channel usage, 14 days statistics, 60 minute averages, license planning, license sizing, peak usage, determine license size, required license channels, license key key.php, re-compute CDR, PCAP restore, sniffer continues recording, GUI locked, alerts disabled, reports unavailable, CSV export blocked, license transfer, move license, new system, new installation, copy license, license token, concurrent systems, dual operation, temporary trial license, trial license, migration, downtime, Alma Linux 9.5, Rocky Linux 9, CentOS 9, PHP 8.2, remi repository, PHP 8.0 not supported, ionCube loader, virtual machine clone, Machine ID, clone, VM clone, license duplication, multiple servers, multiple sniffers, multiple sensors, cross-server, geo-redundancy, duplicate calls, deduplication, CDR deduplication, license deduplication, GUI deduplicates CDRs, multiple instances, distributed monitoring, overcounting license, overlapping mirrors, subscription terms, license renewal, formal end date, grace period end date, subscription cancellation, license expiration, 20 day grace period, automatic renewal, access revoked earlier than expected, license access cancellation, emergency trial license, billing issues, license file key.php is for another hwid, HWID mismatch, hardware ID mismatch, get license button, license resynchronize, sync license with HWID, license status invalid

Key Questions:

• What is the license formal end date?
• What is the license grace period end date?
• How does the 20-day grace period work for license renewal?
• When does VoIPmonitor license access end after cancellation?
• Does license access end on the formal end date or grace period end date?
• Why was my license access revoked earlier than expected?
• How long is the VoIPmonitor license grace period?
• What happens to my VoIPmonitor license when I cancel?
• How do I get emergency access when my license expires?
• What is the VoIPmonitor subscription renewal structure?
• When should I plan my license migration before cancellation?
• Can I get a temporary license while resolving billing issues?
• What is an emergency trial license for VoIPmonitor?
• What is a channel in VoIPmonitor licensing?
• What constitutes a channel in VoIPmonitor licensing?
• How do I transfer a GUI license to a new system?
• Can I copy my VoIPmonitor license file to a new server?
• Do I need to re-issue my license when moving to a new system?
• Can I run old and new VoIPmonitor systems concurrently with the same license?
• How do I get a temporary trial license for migration?
• What PHP version is required for Alma Linux 9.5 / Rocky Linux 9?
• Do I need to install ionCube loader for the GUI?
• How does VoIPmonitor define a channel for licensing?
• Is a channel the same as one phone call in VoIPmonitor?
• What is the difference between a logical call and a CDR leg?
• Can one logical phone conversation use multiple license channels?
• When does one call consume more than one license channel?
• What happens when you transfer a call - does it count as one or multiple channels?
• Do call forking and re-invites affect channel count in VoIPmonitor?
• Does VoIPmonitor count each un-mergeable CDR leg as a separate channel?
• Why did I need more channels in my license than the number of concurrent calls I expected?
• Why does my license have more channels than the number of users I estimated?
• How do call transfers affect channel counting in VoIPmonitor licensing?
• What scenarios cause one call to consume multiple channels?
• What happens when I exceed the channel license limit in VoIPmonitor?
• How many days can I exceed the license limit before the GUI locks?
• Does VoIPmonitor stop recording CDRs when the license limit is exceeded?
• How do I unlock my VoIPmonitor GUI after the license limit lock?
• What happens to CDRs when the GUI is locked due to license overage?
• How do I check my channel usage vs license limit in VoIPmonitor?
• How do I find the number of concurrent calls for license sizing?
• Where is the Tools Concurrent Calls Stats in the GUI?
• How do I view concurrent call history for license planning?
• What is the best way to determine required license size?
• Where can I find 14-day concurrent call statistics?
• Can I re-compute CDRs to fix a license lock without upgrading?
• What is the grace period for exceeding the VoIPmonitor channel license?
• Do I have to upgrade my license if the GUI is locked?
• How does VoIPmonitor count channels for licensing?
• How are CDRs merged for channel counting purposes?
• Does the sniffer stop when the license limit is reached?
• What functionality is disabled when the GUI is locked?
• How long can I exceed the channel limit before locking?
• Where is the VoIPmonitor license key file located?
• How do I upgrade my VoIPmonitor channel license?
• Can I delete CDRs to unlock the GUI temporarily?
• Does VoIPmonitor have a trial period for exceeding licenses?
• How does VoIPmonitor count duplicate calls captured by multiple sniffers?
• If I have multiple servers sniffing the same traffic, will I be charged duplicate license channels?
• Does VoIPmonitor deduplicate CDRs from multiple sensors for license counting?
• How do duplicate calls from geo-redundant sniffers affect my license?
• What happens to my license count if multiple servers capture the same call?
• What does the error "license file key.php is for another hwid" mean?
• How do I fix the "license file key.php is for another hwid" error?
• How do I re-synchronize my license with the current server's Hardware ID?
• What is the Get License button in VoIPmonitor GUI?
• How do I resolve HWID mismatch error in VoIPmonitor?
• Do I need to contact support when moving to new server hardware?
• Can I re-use my VoIPmonitor license on a new server?
• How does the Get License button re-synchronize licenses?
• What causes the "license file key.php is for another hwid" error?
• How do I fix license status invalid after server migration?
• Can I restore license after moving to new hardware?
• Does VoIPmonitor license work after cloud instance recreation?