Tag: VOS3000 CDR file rotation

VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical

VOS3000 CDR File Rotation Robust Backup Write Interval Best Configuration

king

VOS3000 CDR File Rotation Robust Backup Write Interval Configuration

๐Ÿ“‹ Every VoIP operator knows that CDR data is the lifeblood of billing reconciliation โ€” lose your call records, and you lose revenue. The VOS3000 CDR file rotation system, controlled by SERVER_CDR_FILE_WRITE_INTERVAL and SERVER_CDR_FILE_WRITE_MAX, provides a robust backup mechanism that writes call records to text files independently of the primary database. When configured correctly, this ensures you always have a secondary copy of every CDR โ€” even during database outages, server restarts, or unexpected failures. ๐Ÿ›ก๏ธ

โš ๏ธ But misconfigure the rotation parameters, and you risk two catastrophic outcomes: disk overflow from uncontrolled CDR file accumulation, or missing records if the rotation window is too long during peak traffic. The VOS3000 CDR file rotation parameters give you precise control over how frequently backup files are generated and how many are retained โ€” balancing data integrity against disk consumption. This guide covers every detail from the official VOS3000 2.1.9.07 manual, with no fabricated values. ๐Ÿ”ง

๐ŸŽฏ Need help configuring your VOS3000 CDR backup? Contact our team at WhatsApp: +8801911119966 for expert assistance with CDR rotation, billing setup, and complete VOS3000 deployment. ๐Ÿ’ฌ

Table of Contents

๐Ÿ” What Is VOS3000 CDR File Rotation?

๐Ÿ“Š The VOS3000 CDR file rotation system is an additional backup mechanism that writes call detail records to plain text files on the server filesystem. This operates alongside the primary CDR database, providing redundancy and enabling external analytics integration. The system generates pipe-delimited text files in the cdr directory beneath the VOS3000 installation directory, with one file created per configured time interval. ๐Ÿ“

๐Ÿ’ก Why this matters: The backup CDR file system serves several critical purposes:

  • ๐Ÿ›ก๏ธ Disaster recovery: If the database becomes corrupted or unavailable, text files remain intact on disk
  • ๐Ÿ“Š External analytics: Pipe-delimited files are easy to parse with Python, awk, or business intelligence tools
  • ๐Ÿ”„ Regulatory compliance: Many telecom regulators require CDR archival in flat-file format
  • ๐Ÿ’ฐ Billing reconciliation: Compare database CDRs against file CDRs to detect discrepancies
  • ๐Ÿ“ก Real-time monitoring: Some operators tail the CDR files for live traffic visibility

๐Ÿ”‘ Key distinction: The VOS3000 CDR file rotation is a backup mechanism. It does not replace the database CDR storage. The primary CDR records are always written to the database first; the file-based system creates a secondary copy that can be used independently.

โš™๏ธ SERVER_CDR_FILE_WRITE_INTERVAL โ€” The Core Parameter

โฑ๏ธ SERVER_CDR_FILE_WRITE_INTERVAL defines the time interval (in seconds) at which the softswitch creates new CDR text files. Each time this interval elapses, a new file is opened and the previous file is finalized for reading. ๐Ÿ“‹

AttributeValue
๐Ÿ“Œ Parameter NameSERVER_CDR_FILE_WRITE_INTERVAL
๐Ÿ”ข Default ValueNone (not set by default)
๐Ÿ“ UnitSeconds
๐Ÿ“ Range60โ€“86400
๐Ÿ“ DescriptionAdditional write call record file, the new file created time interval (seconds)
๐Ÿ“ LocationOperation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter

๐Ÿ’ก How the interval works: When you set SERVER_CDR_FILE_WRITE_INTERVAL to a value such as 3600 (1 hour), the softswitch creates a new CDR text file every hour. All CDRs whose end time falls within that hour are written to the corresponding file. At the end of the interval, the file is closed and a new one is opened. The file naming convention follows the format YYYYMMDDHH.txt โ€” for example, 2026042612.txt contains all CDRs that ended between 12:00 and 13:00 on April 26, 2026.

๐ŸŽฏ Interval Value Recommendations by Traffic Volume

๐Ÿ“ก The optimal interval depends heavily on your call volume. Higher traffic demands shorter intervals to prevent individual files from becoming too large: ๐Ÿ’ก

Traffic VolumeRecommended IntervalSeconds ValueRationale
๐Ÿ“ž Low (<50 CPS)1 hour3600โœ… Manageable file size; hourly granularity
๐Ÿ“Š Medium (50โ€“200 CPS)30 minutes1800๐Ÿ”ง Prevents oversized files during peaks
๐Ÿ”ฅ High (200+ CPS)15 minutes900๐Ÿ›ก๏ธ Keeps files manageable; easier parsing
โš ๏ธ Extreme (DDoS scenario)5 minutes300๐Ÿšจ Rapid rotation prevents disk fill

โš ๏ธ Important: The minimum allowed value is 60 seconds and the maximum is 86400 seconds (24 hours). Setting the interval below 60 seconds is not supported. If your traffic is so high that even 5-minute files are too large, consider increasing SERVER_CDR_FILE_WRITE_MAX to retain more files, or implementing an external script that periodically archives old files to remote storage.

๐Ÿ“ฆ SERVER_CDR_FILE_WRITE_MAX โ€” Rotation File Count Limit

๐Ÿ“ While SERVER_CDR_FILE_WRITE_INTERVAL controls how often new files are created, SERVER_CDR_FILE_WRITE_MAX controls how many backup CDR files are retained on disk. This parameter prevents uncontrolled disk consumption by automatically deleting the oldest files when the count exceeds the limit. ๐Ÿ—‘๏ธ

AttributeValue
๐Ÿ“Œ Parameter NameSERVER_CDR_FILE_WRITE_MAX
๐Ÿ”ข Default Value2048
๐Ÿ“ UnitNumber of files
๐Ÿ“ Range10โ€“4096
๐Ÿ“ DescriptionAdditional write call record file, the maximum number of reserved file
๐Ÿ“ LocationOperation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter

๐Ÿ”„ How rotation works: When the number of CDR text files exceeds SERVER_CDR_FILE_WRITE_MAX, the oldest files are automatically deleted. This creates a sliding window of retained CDR data โ€” at any given time, you have at most the most recent N files on disk, where N equals SERVER_CDR_FILE_WRITE_MAX.

๐Ÿ“Š Calculating Retention Period from Rotation Parameters

๐Ÿงฎ The total retention period depends on both the write interval and the maximum file count. Here is the formula: ๐Ÿ’ก

๐Ÿ“‹ VOS3000 CDR File Retention Calculation:

Retention Period = SERVER_CDR_FILE_WRITE_INTERVAL ร— SERVER_CDR_FILE_WRITE_MAX

Example 1 (Default Settings):
  Interval = 3600s (1 hour)  ร—  Max Files = 2048
  Retention = 3600 ร— 2048 = 7,372,800 seconds โ‰ˆ 85.3 days

Example 2 (High Traffic):
  Interval = 1800s (30 min)  ร—  Max Files = 2048
  Retention = 1800 ร— 2048 = 3,686,400 seconds โ‰ˆ 42.7 days

Example 3 (Maximum Retention):
  Interval = 86400s (24 hours)  ร—  Max Files = 4096
  Retention = 86400 ร— 4096 = 353,894,400 seconds โ‰ˆ 11.2 years

Example 4 (Short Retention, Frequent Rotation):
  Interval = 300s (5 min)  ร—  Max Files = 2048
  Retention = 300 ร— 2048 = 614,400 seconds โ‰ˆ 7.1 days

โš ๏ธ Critical warning: A shorter interval with the same file count means shorter total retention. If you decrease the interval for performance reasons, you must proportionally increase the file count to maintain the same retention period. Otherwise, you may lose historical CDR backup data faster than expected. ๐Ÿ”ฅ

๐Ÿ–ฅ๏ธ Enabling VOS3000 CDR File Rotation

๐Ÿ”ง The VOS3000 CDR file rotation requires two conditions to be met before it generates backup files: the SS_CDR_RECORD_TO_FILE parameter must be enabled, and the SERVER_CDR_FILE_WRITE_INTERVAL must be set to a valid value. ๐Ÿ“‹

Step 1: Enable CDR Text File Export ๐Ÿ“„

  1. ๐Ÿ” Log in to VOS3000 Client
  2. ๐Ÿ“Œ Navigate: Operation management โ†’ Softswitch management โ†’ Additional settings โ†’ Softswitch parameter
  3. ๐Ÿ” Locate SS_CDR_RECORD_TO_FILE
  4. โœ๏ธ Set value to On
AttributeValue
๐Ÿ“Œ Parameter NameSS_CDR_RECORD_TO_FILE
๐Ÿ”ข Default ValueOff
๐Ÿ“ DescriptionSave CDR as TXT โ€” enables the backup CDR text file system
๐Ÿ“ LocationOperation management โ†’ Softswitch management โ†’ Additional settings โ†’ Softswitch parameter

Step 2: Configure Write Interval โฑ๏ธ

  1. ๐Ÿ“Œ Navigate: Operation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter
  2. ๐Ÿ” Locate SERVER_CDR_FILE_WRITE_INTERVAL
  3. โœ๏ธ Set the desired interval value (60โ€“86400 seconds) based on your traffic volume

Step 3: Configure Maximum File Count ๐Ÿ“

  1. ๐Ÿ” In the same Server parameter section, locate SERVER_CDR_FILE_WRITE_MAX
  2. โœ๏ธ Set the maximum number of files to retain (10โ€“4096, default: 2048)
  3. ๐Ÿ’พ Save and apply the configuration

Step 4: Verify CDR File Generation โœ…

๐Ÿ–ฅ๏ธ After configuration, verify that files are being generated in the CDR directory:

# Check the CDR directory on the VOS3000 server
ls -la /home/vos3000/cdr/

# Expected output โ€” files named by YYYYMMDDHH convention:
# -rw-r--r-- 1 vos3000 vos3000  245120 Apr 26 12:00 2026042612.txt
# -rw-r--r-- 1 vos3000 vos3000  189340 Apr 26 13:00 2026042613.txt
# -rw-r--r-- 1 vos3000 vos3000  312500 Apr 26 14:00 2026042614.txt

# Verify rotation is working โ€” old files should be auto-deleted
# when count exceeds SERVER_CDR_FILE_WRITE_MAX
ls -1 /home/vos3000/cdr/ | wc -l

๐Ÿ“Š For detailed CDR file format information, see our VOS3000 CDR pipe format reference guide.

๐Ÿ”„ VOS3000 CDR File Rotation and Disk Space Management

๐Ÿ’พ One of the most critical aspects of VOS3000 CDR file rotation is managing disk space consumption. Each CDR record written to the text file contains 18 pipe-delimited fields. A typical single CDR line is approximately 200โ€“350 bytes depending on the length of phone numbers, IP addresses, and other variable-length fields. ๐Ÿ“

๐Ÿ“ Estimating Disk Space Requirements

๐Ÿ“Š Use this calculation to estimate your CDR file storage needs: ๐Ÿ’ก

MetricFormulaExample (100 CPS)
CDR lines per hourCPS ร— 3600360,000
File size per hourLines ร— 300 bytes (avg)~108 MB/hour
Daily disk usageFile/hour ร— 24~2.6 GB/day
With 2048 hourly files2048 ร— 108 MB~221 GB total

โš ๏ธ Key insight: At 100 CPS with hourly intervals and the default 2048 file limit, you need approximately 221 GB of disk space for CDR files alone. This does not account for the database, logs, or other system files. Ensure your server has adequate storage, or implement an external archival strategy. For help sizing your VOS3000 server, see our concurrent call load test guide. ๐Ÿ”ง

๐Ÿ›ก๏ธ Common VOS3000 CDR File Rotation Problems and Solutions

โŒ Misconfigured rotation parameters cause a range of issues from missing records to disk overflow. Here are the most common problems and their solutions: ๐Ÿ”

โŒ Problem 1: CDR Files Not Being Generated

๐Ÿ” Symptom: The CDR directory exists but no text files are being created, even though calls are flowing through the system.

๐Ÿ’ก Cause: The most common reason is that SS_CDR_RECORD_TO_FILE is set to Off (default). Without enabling this parameter, the VOS3000 CDR file rotation system is completely inactive regardless of the interval and max file settings.

โœ… Solutions:

  • ๐Ÿ”ง Set SS_CDR_RECORD_TO_FILE to On in Softswitch parameter settings
  • ๐Ÿ“Š Verify SERVER_CDR_FILE_WRITE_INTERVAL is set to a valid value between 60 and 86400
  • ๐Ÿ“ Check that the cdr directory exists beneath the VOS3000 installation directory and has write permissions
  • ๐Ÿ” Check the softswitch logs for any write errors

โŒ Problem 2: Disk Space Exhausting Rapidly

๐Ÿ” Symptom: The server runs out of disk space quickly, and the CDR directory contains a very large number of files.

๐Ÿ’ก Cause: SERVER_CDR_FILE_WRITE_MAX is set too high, or the write interval is very short, causing many small files that collectively consume large amounts of disk space. Alternatively, the automatic file deletion mechanism may not be working correctly.

โœ… Solutions:

  • ๐Ÿ“ Reduce SERVER_CDR_FILE_WRITE_MAX to a value that fits within your available disk space
  • โฑ๏ธ Increase SERVER_CDR_FILE_WRITE_INTERVAL to create fewer, larger files
  • ๐Ÿ”„ Implement an external archival script that moves old CDR files to remote storage (NFS, S3, etc.)
  • ๐Ÿ“Š Monitor disk usage with a cron job that alerts you when usage exceeds 80%

โŒ Problem 3: Historical CDR Files Disappearing Too Quickly

๐Ÿ” Symptom: You need to look up CDR data from 30 days ago, but the oldest available file is only from 10 days ago.

๐Ÿ’ก Cause: The retention period (interval ร— max files) is shorter than your required retention window. This happens when the interval is decreased without proportionally increasing the file count.

โœ… Solutions:

  • ๐Ÿ“ Calculate your required retention: Required Max Files = Required Days ร— 86400 / Interval
  • ๐Ÿ“ฆ Increase SERVER_CDR_FILE_WRITE_MAX to the calculated value (up to 4096 maximum)
  • ๐Ÿ—„๏ธ If you need more than 4096 files, implement external archival before rotation deletes them
  • ๐Ÿ“‹ For detailed CDR querying guidance, see our VOS3000 CDR analysis and billing guide

โŒ Problem 4: Zero-Duration Calls Flooding CDR Files

๐Ÿ” Symptom: CDR text files are much larger than expected, filled with records for calls that never connected (0-second duration).

๐Ÿ’ก Cause: The SS_CDR_RECORD_NONCONNECT parameter is set to On, causing all non-connected calls (failed attempts, busy, no answer) to be included in the text file export along with successful calls.

โœ… Solutions:

  • โš™๏ธ Set SS_CDR_RECORD_NONCONNECT to Off to exclude zero-duration calls from the file export
  • ๐Ÿ“Š Keep it On only if you need failed call data for analytics or fraud detection
  • ๐Ÿ›ก๏ธ During DDoS attacks, set SERVER_BILLING_RECORD_ZERO_HOLD_TIME to Off to prevent database overload โ€” see our DDoS protection guide

๐Ÿ“‹ Complete VOS3000 CDR File Rotation Parameter Reference

๐Ÿ“Š Here is the complete reference table for all parameters related to CDR file rotation, sourced from the official VOS3000 2.1.9.07 manual: ๐Ÿ”ง

ParameterDefaultRangePurpose
SERVER_CDR_FILE_WRITE_INTERVALNone60โ€“86400sTime interval for new CDR file creation
SERVER_CDR_FILE_WRITE_MAX204810โ€“4096Maximum number of CDR files to retain
SS_CDR_RECORD_TO_FILEOffOn/OffEnable/disable CDR text file export
SS_CDR_RECORD_NONCONNECTOffOn/OffInclude non-connected calls (0s) in file export
SS_CDR_RECORD_ILLEGALOnOn/OffRecord illegal calls in CDR files
SERVER_CDR_REAL_TIME_REPORT_SERVERNoneIP:PortForward CDRs to external server in real-time

๐Ÿ“ All server parameters are located at: Navigation โ†’ Operation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter. Softswitch parameters are at the same path under Softswitch parameter.

๐Ÿ’ก VOS3000 CDR File Rotation Best Practices

๐ŸŽฏ Follow these best practices to ensure your VOS3000 CDR file rotation is both reliable and efficient: ๐Ÿ“‹

Best PracticeRecommendationReason
๐Ÿ“Š Calculate retention needsInterval ร— Max Files = Retentionโœ… Ensures you keep enough historical data
๐Ÿ“ Implement external archivalCron job to copy old files to remote storage๐Ÿ›ก๏ธ Prevents data loss when rotation deletes files
โฑ๏ธ Match interval to trafficHigher CPS = shorter interval๐Ÿ”ง Keeps individual file sizes manageable
๐Ÿ’พ Monitor disk spaceAlert at 80% usage threshold๐Ÿšจ Prevents unexpected disk-full outages
๐Ÿ”„ Test recovery regularlyParse backup files monthly to verify integrity๐Ÿ“‹ Confirms files are usable when needed
๐Ÿ” Secure CDR directoryRestrict file permissions to vos3000 user only๐Ÿ›ก๏ธ CDRs contain sensitive billing data

๐Ÿ’ฌ Questions about your VOS3000 CDR file rotation setup? Reach out at WhatsApp: +8801911119966 โ€” our VOS3000 experts can help you optimize rotation settings for your traffic volume and retention requirements. ๐Ÿ“ž

โ“ Frequently Asked Questions

โ“ What is the default value for SERVER_CDR_FILE_WRITE_INTERVAL?

๐Ÿ“‹ The default value for SERVER_CDR_FILE_WRITE_INTERVAL is None (not set). This means that CDR file rotation is not active by default. You must explicitly set a value between 60 and 86400 seconds and enable SS_CDR_RECORD_TO_FILE to On before the system generates backup CDR text files. Without this configuration, CDR records are only stored in the database. ๐Ÿ’ก

โ“ How does VOS3000 CDR file rotation prevent disk overflow?

๐Ÿ›ก๏ธ The VOS3000 CDR file rotation uses SERVER_CDR_FILE_WRITE_MAX to enforce a maximum number of retained files. When the file count exceeds this limit, the oldest files are automatically deleted. For example, with the default value of 2048 and an hourly interval, the system retains approximately 85 days of CDR files. Once the 2049th file is created, the oldest file is removed, maintaining a consistent disk footprint. This sliding window mechanism ensures the CDR directory never grows beyond a predictable size. ๐Ÿ“

โ“ Can I change the VOS3000 CDR file rotation interval without restarting?

๐Ÿ”ง Server parameters in VOS3000 typically take effect after saving and applying the configuration through the VOS3000 Client interface. While some parameters may apply immediately, it is recommended to verify that the new interval is in effect by checking the timestamps of newly created CDR files. If the old interval persists, a softswitch service restart may be required. Always test configuration changes during a maintenance window to avoid any disruption to CDR recording. ๐Ÿ“Š

โ“ What is the relationship between SS_CDR_RECORD_TO_FILE and SERVER_CDR_FILE_WRITE_INTERVAL?

๐Ÿ”— SS_CDR_RECORD_TO_FILE is the master switch that enables or disables the entire CDR text file system. SERVER_CDR_FILE_WRITE_INTERVAL controls the frequency of file creation within that system. If SS_CDR_RECORD_TO_FILE is Off (default), no CDR files are generated regardless of the interval setting. If it is On but the interval is not set (None), the system may not create files properly. Both parameters must be correctly configured for the VOS3000 CDR file rotation to function. ๐ŸŽฏ

โ“ How do I include non-connected calls in the CDR text files?

๐Ÿ“Š By default, SS_CDR_RECORD_NONCONNECT is set to Off, which means only successfully connected calls (calls with duration greater than 0 seconds) are written to the CDR text files. To include failed call attempts, busy calls, and no-answer calls, set SS_CDR_RECORD_NONCONNECT to On. Be aware that enabling this parameter significantly increases the number of CDR records per file, especially during traffic spikes or attack scenarios. For DDoS protection guidance, see our zero duration CDR control guide. โš ๏ธ

โ“ Where are VOS3000 CDR text files stored on the server?

๐Ÿ“ CDR text files are stored in the cdr directory beneath the VOS3000 installation directory. The file naming convention is YYYYMMDDHH.txt, where YYYY is the year, MM is the month, DD is the day, and HH is the hour. Each file contains all CDRs whose end time falls within that time window. For example, 2026042614.txt contains CDRs for calls that ended between 14:00 and 15:00 on April 26, 2026. The files use pipe-delimited format with 18 fields per record โ€” see our CDR pipe format reference for complete field documentation. ๐Ÿ“‹

๐Ÿ“ž Need Expert Help with VOS3000 CDR File Rotation?

๐Ÿ”ง Proper VOS3000 CDR file rotation configuration is essential for ensuring billing data integrity, meeting regulatory retention requirements, and preventing disk overflow disasters. Whether you need to set up CDR backup for the first time, tune rotation parameters for high traffic, or implement an external archival strategy, our VOS3000 experts are here to help. ๐Ÿ›ก๏ธ

๐Ÿ’ฌ Contact us at WhatsApp: +8801911119966 for professional VOS3000 deployment, CDR configuration, and ongoing support. We help VoIP operators worldwide optimize their softswitch performance and billing accuracy. ๐ŸŒ

๐Ÿ“– Explore more VOS3000 guides: CDR analysis and billing, billing system overview, and parameter description reference. ๐Ÿ”—

๐Ÿ“ž Need Professional VOS3000 Setup Support?

For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:

๐Ÿ“ฑ WhatsApp: +8801911119966
๐ŸŒ Website: www.vos3000.com
๐ŸŒ Blog: multahost.com/blog
๐Ÿ“ฅ Downloads: VOS3000 Downloads

VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction CriticalVOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction CriticalVOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical
VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical

VOS3000 CDR Query Date Range Maximum Interval Limit Best Configuration

king

VOS3000 CDR Query Date Range Maximum Interval Limit Configuration

๐Ÿ“Š A single CDR query spanning 90 days on a high-traffic VOS3000 system can return tens of millions of records โ€” enough to overwhelm the database, exhaust client memory, and freeze the VOS3000 interface for minutes. The VOS3000 CDR query date range limit, controlled by SERVER_QUERY_CDR_MAX_DAY_INTERVAL, prevents this by capping the maximum number of days a user can query in a single CDR search. The default of 31 days is designed to balance operational needs against database performance โ€” but understanding how to work within and around this limit is essential for every VOS3000 operator. โฑ๏ธ

๐Ÿ”ง Whether you are a reseller who needs to pull quarterly reports or an administrator protecting your database from runaway queries, mastering the VOS3000 CDR query date range configuration is critical. This guide covers the parameter details from the official VOS3000 2.1.9.07 manual, practical workarounds for large-range queries, and how this limit works alongside other CDR access controls. ๐Ÿ“‹

๐Ÿ’ฌ Need help optimizing your VOS3000 CDR query performance? Contact our team at WhatsApp: +8801911119966 for expert database tuning and configuration support. ๐Ÿ’ก

Table of Contents

๐Ÿ” What Is VOS3000 CDR Query Date Range Limit?

๐Ÿ“ The VOS3000 CDR query date range limit specifies the maximum number of days a user can include in a single CDR query. When a user attempts to search CDRs with a start and end date that spans more than the configured maximum, the query is rejected with an error message indicating the date range exceeds the allowed limit. ๐Ÿšซ

๐Ÿ’ก Why this limit exists:

  • ๐Ÿ“Š Database performance: Large date range queries scan millions of rows, consuming CPU, memory, and I/O resources on the database server
  • ๐Ÿ–ฅ๏ธ Client stability: Returning millions of CDR records to the VOS3000 Client can cause memory exhaustion and application crashes
  • โฑ๏ธ Query timeout prevention: Long-running queries may time out before completion, wasting resources without returning results
  • ๐Ÿ›ก๏ธ Fair resource sharing: Prevents a single user from monopolizing database resources with an excessively broad query
  • ๐Ÿ“ž Operational continuity: Ensures the VOS3000 system remains responsive for real-time call processing even during heavy CDR analysis

โš™๏ธ SERVER_QUERY_CDR_MAX_DAY_INTERVAL โ€” The Core Parameter

๐Ÿ“ SERVER_QUERY_CDR_MAX_DAY_INTERVAL defines the maximum number of days allowed in a CDR query’s date range. Any query with a date range exceeding this value is automatically rejected. ๐Ÿ“‹

AttributeValue
๐Ÿ“Œ Parameter NameSERVER_QUERY_CDR_MAX_DAY_INTERVAL
๐Ÿ”ข Default Value31
๐Ÿ“ UnitDays
๐Ÿ“ DescriptionMaximum Interval for CDR Inquiry (Day)
๐Ÿ“ LocationOperation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter

๐Ÿ”ง How the 31-day default works: When a user queries CDRs with a date range of, say, January 1 to February 15 (45 days), VOS3000 calculates the interval: 45 days. Since this exceeds the default SERVER_QUERY_CDR_MAX_DAY_INTERVAL of 31, the query is rejected and the user receives an error. The user must then narrow the search to a maximum of 31 days โ€” for example, January 1 to January 31.

๐Ÿ“‹ VOS3000 CDR Query Date Range Limit Examples

๐Ÿ“Š Here are practical examples showing how the limit affects different query scenarios: ๐Ÿ’ก

Query Date RangeDays SpannedDefault Limit (31)Result
Apr 1 โ€“ Apr 1515 daysโœ… Within limitQuery executes normally
Apr 1 โ€“ Apr 3030 daysโœ… Within limitQuery executes normally
Apr 1 โ€“ May 131 daysโœ… Exactly at limitQuery executes (31 โ‰ค 31)
Apr 1 โ€“ May 232 daysโŒ Exceeds limitQuery rejected โ€” reduce date range
Jan 1 โ€“ Mar 3190 daysโŒ Exceeds limitQuery rejected โ€” use incremental approach

๐Ÿ”„ Workarounds for CDR Queries Exceeding the Date Range Limit

๐Ÿ“Š When you need CDR data spanning more than 31 days, there are several approaches to work around the VOS3000 CDR query date range limit without increasing the parameter value and risking database performance: ๐Ÿ’ก

๐Ÿ“‹ Method 1: Incremental Queries (Chunk the Date Range)

๐Ÿ”ข Break your large date range into multiple queries, each within the 31-day limit. For example, to get 90 days of CDR data: ๐Ÿ’ก

๐Ÿ“‹ Incremental CDR Query Strategy (90-day range, 31-day limit):

Query 1: Jan 1 โ€“ Jan 31    (31 days) โœ…
Query 2: Feb 1 โ€“ Feb 28    (28 days) โœ…  
Query 3: Mar 1 โ€“ Mar 31    (31 days) โœ…

Total: 3 queries covering 90 days
Merge results externally (Excel, Python, etc.)

๐Ÿ“Š Advantage: No parameter changes needed; each query is database-friendly. Disadvantage: Requires manual effort to merge multiple result sets. For automated merging, use Python or a spreadsheet tool to combine the CSV exports.

๐Ÿ“ Method 2: CDR Text File Export

๐Ÿ“„ Use the VOS3000 CDR text file system instead of the database query. When SS_CDR_RECORD_TO_FILE is enabled, all CDRs are written to pipe-delimited text files in the cdr directory. These files can be searched, filtered, and analyzed using any text processing tool without any date range restriction. ๐Ÿ“‹

AspectDatabase QueryText File Export
๐Ÿ“… Date range limit31 days (configurable)No limit โ€” read any files on disk
๐Ÿ” Search capabilityRich filtering (account, gateway, etc.)Text processing (grep, awk, Python)
๐Ÿ“Š SpeedFast for targeted queriesSlower for large file scans
๐Ÿ”ง Setup requiredNone โ€” built into VOS3000 ClientEnable SS_CDR_RECORD_TO_FILE + rotation

๐Ÿ’ก For detailed CDR text file setup instructions, see our CDR text file export guide and CDR file rotation guide. ๐Ÿ”—

๐Ÿ“ก Method 3: Real-Time CDR Forwarding to External Analytics

๐ŸŒ If you frequently need large-range CDR analysis, consider forwarding CDRs to an external analytics platform (Elasticsearch, Splunk, custom database) using SERVER_CDR_REAL_TIME_REPORT_SERVER. External platforms typically have no date range restrictions and offer more powerful search and visualization capabilities. For setup instructions, see our real-time CDR forwarding guide. ๐Ÿš€

โš™๏ธ Method 4: Increase the Parameter Value (With Caution)

โš ๏ธ You can increase SERVER_QUERY_CDR_MAX_DAY_INTERVAL beyond 31 days if your database has sufficient resources. However, be aware of the implications: ๐Ÿ’ก

SettingRisk LevelImpact at 100 CPSRecommendation
31 days (default)๐ŸŸข Low~267M records maxโœ… Safe for most deployments
60 days๐ŸŸก Medium~518M records maxโš ๏ธ Only with powerful database server
90 days๐ŸŸ  High~778M records max๐Ÿšจ Risk of query timeouts and client crashes
365 days๐Ÿ”ด Very High~3.15B records maxโŒ Not recommended โ€” use external analytics instead

๐Ÿ–ฅ๏ธ Step-by-Step VOS3000 CDR Query Date Range Configuration

๐Ÿ”ง Follow these steps to configure the CDR query date range limit: ๐Ÿ“‹

Step 1: Configure the Parameter ๐Ÿ“Œ

  1. ๐Ÿ” Log in to VOS3000 Client
  2. ๐Ÿ“Œ Navigate: Operation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter
  3. ๐Ÿ” Locate SERVER_QUERY_CDR_MAX_DAY_INTERVAL
  4. โœ๏ธ Set the desired maximum day interval (default: 31)
  5. ๐Ÿ’พ Save and apply the configuration

Step 2: Verify the Limit โœ…

๐Ÿ“Š After configuration, test the limit by attempting a CDR query that exceeds the configured maximum:

  1. ๐Ÿ“… Open the CDR query window in VOS3000 Client
  2. ๐Ÿ” Set a date range that exceeds the configured limit
  3. โœ… Verify that the query is rejected with a date range error message
  4. ๐Ÿ“‹ Try a query within the limit and confirm it executes successfully

๐Ÿ”— The VOS3000 CDR query date range limit works alongside several other query size parameters that together control database load: ๐Ÿ’ก

ParameterDefaultPurpose
SERVER_QUERY_CDR_MAX_DAY_INTERVAL31Maximum days in CDR query date range
SERVER_QUERY_MAX_ONE_PAGE_SIZE200000Maximum records per page in results
SERVER_QUERY_MAX_SIZE30000000Total data query limit (items)
SERVER_QUERY_ONE_PAGE_SIZE10000Default records per page
SERVER_QUERY_NON_PAGABLE_MAX_LINES100000Non-pagable table max lines per page (1000โ€“200000)

๐Ÿ’ก Practical example: At 100 CPS, a 31-day query could return approximately 267 million records โ€” well above the SERVER_QUERY_MAX_SIZE of 30 million items. This means that even with a 31-day date range, the actual query results may be truncated by the total query size limit. The combination of date range and result size limits provides defense in depth against database overload. ๐Ÿ›ก๏ธ

๐Ÿ›ก๏ธ Common VOS3000 CDR Query Date Range Problems and Solutions

โŒ Problem 1: Reseller Needs Quarterly CDR Report

๐Ÿ” Symptom: A reseller needs to generate a quarterly CDR report (90 days) but the query is rejected.

โœ… Solutions:

  • ๐Ÿ“‹ Use incremental queries: three 31-day queries covering the quarter
  • ๐Ÿ“„ Export CDR text files and process them externally with Python or Excel
  • ๐Ÿ“ก Set up real-time CDR forwarding to an external analytics platform
  • โš™๏ธ Temporarily increase the limit for the specific query (then reduce it back)

โŒ Problem 2: CDR Query Returns Incomplete Results

๐Ÿ” Symptom: A 31-day CDR query returns fewer records than expected.

๐Ÿ’ก Cause: The total result count exceeds SERVER_QUERY_MAX_SIZE (30 million items), causing truncation. Or the query falls within the CDR query blackout window for some hours.

โœ… Solutions:

  • ๐Ÿ“Š Add more specific filters (account, gateway, call type) to reduce result count
  • ๐Ÿ“… Use a narrower date range and merge results
  • ๐Ÿ”ง Check SERVER_QUERY_MAX_SIZE setting if you need larger result sets

โŒ Problem 3: Changing the Limit Does Not Take Effect

๐Ÿ” Symptom: After changing SERVER_QUERY_CDR_MAX_DAY_INTERVAL, queries still fail at the old limit.

โœ… Solutions:

  • ๐Ÿ”„ Re-login to the VOS3000 Client after saving the parameter
  • ๐Ÿ”ง Clear the client cache and restart the application
  • ๐Ÿ“Š Verify the parameter value was saved correctly by re-opening the settings panel

๐Ÿ’ก VOS3000 CDR Query Date Range Best Practices

Best PracticeRecommendationReason
๐Ÿ“Š Keep default 31-day limitDo not increase without careful analysisโœ… Protects database from runaway queries
๐Ÿ“‹ Use incremental queriesChunk large ranges into 31-day segments๐Ÿ”ง No parameter changes; database-friendly
๐Ÿ“„ Leverage text file exportsUse CDR text files for large-range analysis๐Ÿ“Š No date range restriction on file reads
๐Ÿ“ก Forward to external analyticsIntegrate with Elasticsearch/Splunk๐Ÿš€ No limits; powerful visualization
๐Ÿ“ž Add query filtersSpecify account, gateway, or call type๐Ÿ” Reduces result count and query time

๐Ÿ’ฌ Need to optimize your VOS3000 CDR query strategy? Contact us at WhatsApp: +8801911119966 for expert guidance on database performance, CDR export workflows, and external analytics integration. ๐Ÿ“ž

โ“ Frequently Asked Questions

โ“ What is the default value for SERVER_QUERY_CDR_MAX_DAY_INTERVAL?

๐Ÿ“‹ The default value is 31 days. This means that by default, any CDR query in VOS3000 with a date range exceeding 31 days is automatically rejected. The 31-day default covers a typical monthly reporting cycle and provides a reasonable balance between operational needs and database protection. If your business requires larger query ranges, you can increase this value โ€” but consider the performance implications carefully, especially on high-traffic systems. ๐Ÿ”ง

โ“ Can I increase the VOS3000 CDR query date range to 365 days?

โš ๏ธ While SERVER_QUERY_CDR_MAX_DAY_INTERVAL can technically be set to 365 or higher, doing so on a production system with significant call volume is strongly discouraged. At 100 CPS, a 365-day query could attempt to return over 3 billion records โ€” far exceeding the SERVER_QUERY_MAX_SIZE of 30 million items and likely causing query timeouts or client crashes. For annual CDR analysis, use incremental queries, text file exports, or external analytics platforms instead. For CDR text file setup, see our CDR text file export guide. ๐Ÿ“Š

โ“ Does the date range limit apply to the CDR text file export?

๐Ÿ“„ No. The VOS3000 CDR query date range limit only applies to queries made through the VOS3000 Client and web interface (database queries). The CDR text file system writes all records to files on disk without any date range filtering. You can read, search, and analyze these text files using external tools (Python, awk, grep) with no date range restriction whatsoever. This makes the text file system the preferred method for large-range historical CDR analysis. ๐Ÿ”—

โ“ How do I export more than 31 days of CDR data for a reseller?

๐Ÿ“Š You have several options: (1) Use incremental queries โ€” run multiple 31-day queries and merge the results externally, (2) Access the CDR text files on the server directly โ€” they contain all records with no date range limit, (3) Use the real-time CDR forwarding feature to send records to an external analytics platform where larger queries are supported, or (4) Temporarily increase SERVER_QUERY_CDR_MAX_DAY_INTERVAL for the specific query (remember to reduce it back afterward). For the most robust long-term solution, option 3 provides unlimited analytical capability. ๐Ÿ’ก

โ“ Does the VOS3000 CDR query date range limit affect automated reports?

๐Ÿ“‹ The date range limit primarily affects manual CDR queries through the VOS3000 Client interface. Automated reports (configured under Report management) generate based on their own scheduling parameters. However, if an automated report’s date range configuration exceeds the SERVER_QUERY_CDR_MAX_DAY_INTERVAL, it may also be subject to the same restriction. Always verify that your automated report schedules are compatible with the configured date range limit. For more on reporting, see our CDR analysis guide. ๐Ÿ“Š

โ“ What other parameters control CDR query performance?

๐Ÿ”ง Several parameters work together to protect database performance: SERVER_QUERY_CDR_MAX_DAY_INTERVAL (date range limit), SERVER_QUERY_MAX_ONE_PAGE_SIZE (max records per page = 200000), SERVER_QUERY_MAX_SIZE (total query limit = 30M items), SERVER_QUERY_ONE_PAGE_SIZE (default page size = 10000), and SERVER_QUERY_CDR_DENY_TIME (blackout hours). Together, these parameters provide layered protection against heavy queries. For the blackout configuration, see our CDR query blackout guide. ๐Ÿ›ก๏ธ

๐Ÿ“ž Need Expert Help with VOS3000 CDR Query Date Range Configuration?

๐Ÿ”ง Proper VOS3000 CDR query date range configuration protects your database while ensuring your team can access the billing data they need. Whether you need to optimize query performance, set up CDR text file exports for large-range analysis, or integrate with external analytics platforms, our VOS3000 experts are here to help. ๐Ÿ›ก๏ธ

๐Ÿ’ฌ Contact us at WhatsApp: +8801911119966 for professional VOS3000 deployment and optimization services. We serve VoIP operators worldwide with proven solutions for billing, analytics, and system performance. ๐ŸŒ

๐Ÿ“– Explore related guides: CDR query blackout configuration, CDR analysis and billing, and parameter description reference. ๐Ÿ”—

๐Ÿ“ž Need Professional VOS3000 Setup Support?

For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:

๐Ÿ“ฑ WhatsApp: +8801911119966
๐ŸŒ Website: www.vos3000.com
๐ŸŒ Blog: multahost.com/blog
๐Ÿ“ฅ Downloads: VOS3000 Downloads

VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction CriticalVOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction CriticalVOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical
VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical

VOS3000 Real-Time CDR Forwarding Advanced External Server Easy Integration

king

VOS3000 Real-Time CDR Forwarding Advanced External Server Integration

๐Ÿ“ก In modern VoIP operations, CDR data must reach external systems immediately โ€” not hours later after a batch export. The VOS3000 real-time CDR forwarding feature, powered by SERVER_CDR_REAL_TIME_REPORT_SERVER, pushes every call detail record to an external server the moment a call ends. This enables live billing by external rating engines, instant fraud detection, real-time traffic monitoring, and seamless integration with third-party business intelligence platforms. ๐Ÿš€

โš™๏ธ Without real-time CDR forwarding, operators must rely on scheduled database exports or CDR text file parsing โ€” both of which introduce latency ranging from minutes to hours. For high-value wholesale operations where every second of billing delay impacts cash flow, the VOS3000 real-time CDR forwarding capability is not a luxury โ€” it is a necessity. This guide covers the configuration, use cases, and integration patterns based exclusively on the official VOS3000 2.1.9.07 manual. ๐Ÿ“‹

๐Ÿ’ฌ Need help setting up external CDR integration? Contact our VOS3000 team at WhatsApp: +8801911119966 for expert configuration and deployment assistance. ๐Ÿ’ก

Table of Contents

๐Ÿ” What Is VOS3000 Real-Time CDR Forwarding?

๐Ÿ“Š The VOS3000 real-time CDR forwarding system transmits each completed call detail record to a designated external server immediately after the call ends. Unlike the text file export (which writes CDRs to local files at regular intervals) or the database storage (which requires direct database access), real-time forwarding delivers CDR data over the network to any system that can accept the connection โ€” whether it is a custom billing application, a fraud detection platform, or a data warehouse. ๐ŸŒ

๐Ÿ’ก Key advantages over other CDR access methods:

  • โšก Zero latency: CDRs are forwarded the instant a call completes โ€” no waiting for batch exports
  • ๐Ÿ”— Loose coupling: The external system does not need database access or file system access to VOS3000
  • ๐Ÿ›ก๏ธ Redundancy: Provides a third copy of CDR data (database + text files + external server)
  • ๐Ÿ“Š Real-time analytics: Feed live CDR data into dashboards, monitoring tools, and alerting systems
  • ๐Ÿ’ฐ External billing: Route CDRs to a separate rating engine for specialized billing calculations

โš™๏ธ SERVER_CDR_REAL_TIME_REPORT_SERVER โ€” The Core Parameter

๐Ÿ“ก SERVER_CDR_REAL_TIME_REPORT_SERVER specifies the target server address (IP and port) where VOS3000 forwards CDR records in real-time. This is the single parameter that enables and configures the entire real-time forwarding system. ๐ŸŽฏ

AttributeValue
๐Ÿ“Œ Parameter NameSERVER_CDR_REAL_TIME_REPORT_SERVER
๐Ÿ”ข Default ValueNone (not configured by default)
๐Ÿ“ FormatIP:Port (e.g., 192.168.1.100:5060)
๐Ÿ“ DescriptionAdditional send call record to server address
๐Ÿ“ LocationOperation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter

๐Ÿ”ง Configuration syntax: Set the parameter value to the IP address and port of your external CDR receiving server, separated by a colon. For example, to forward CDRs to a server at IP 10.0.0.50 listening on port 8080, set the value to 10.0.0.50:8080. When this parameter is left empty (default), real-time CDR forwarding is disabled.

๐Ÿ”— Two additional parameters work alongside SERVER_CDR_REAL_TIME_REPORT_SERVER to control the external CDR delivery pipeline: ๐Ÿ’ก

ParameterDefaultRangePurpose
EXTERNAL_SEND_CDROffOn/OffInterface: send CDR โ€” master switch for external CDR delivery
EXTERNAL_MAX_CDR_PENDING_SIZE100001000โ€“100000Queue size for resending CDR when external server is unavailable

โš ๏ธ Important: EXTERNAL_SEND_CDR must be set to On for the real-time CDR forwarding to work. This is the master switch for the entire external CDR interface. Additionally, EXTERNAL_MAX_CDR_PENDING_SIZE defines a buffer queue โ€” if the external server is temporarily unreachable, VOS3000 queues up to this many CDRs for automatic resend when the connection is restored. This prevents CDR loss during network interruptions. ๐Ÿ›ก๏ธ

๐ŸŽฏ VOS3000 Real-Time CDR Forwarding Use Cases

๐ŸŒ The real-time CDR forwarding capability enables a wide range of integration scenarios that are essential for modern VoIP operations: ๐Ÿ“Š

Use CaseExternal SystemBenefit
๐Ÿ’ฐ External billing engineCustom rating/billing applicationReal-time invoice generation; custom rate plans beyond VOS3000
๐Ÿ›ก๏ธ Fraud detectionFraud monitoring platform (e.g., custom SIEM)Instant detection of SIM box, arbitrage, and premium rate fraud
๐Ÿ“Š Traffic analyticsElasticsearch, Splunk, or custom dashboardLive traffic visualization and capacity planning
๐Ÿ”„ CDR reconciliationThird-party reconciliation toolCross-vendor CDR matching for carrier dispute resolution
๐Ÿ“‹ Regulatory complianceLawful interception / CALEA systemImmediate CDR delivery to compliance systems
๐Ÿข Multi-system distributionCDR router/multiplexer applicationOne source feeding multiple downstream systems

๐Ÿ“‹ Step-by-Step VOS3000 Real-Time CDR Forwarding Configuration

๐Ÿ–ฅ๏ธ Follow these steps to configure real-time CDR forwarding on your VOS3000 system: ๐Ÿ”ง

Step 1: Enable External CDR Interface ๐ŸŒ

  1. ๐Ÿ” Log in to VOS3000 Client
  2. ๐Ÿ“Œ Navigate: Operation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter
  3. ๐Ÿ” Locate EXTERNAL_SEND_CDR
  4. โœ๏ธ Set value to On

Step 2: Configure Target Server Address ๐Ÿ“ก

  1. ๐Ÿ” In the same Server parameter section, locate SERVER_CDR_REAL_TIME_REPORT_SERVER
  2. โœ๏ธ Set the value to the IP address and port of your external CDR receiver (e.g., 10.0.0.50:8080)

Step 3: Configure CDR Queue Size ๐Ÿ“ฆ

  1. ๐Ÿ” Locate EXTERNAL_MAX_CDR_PENDING_SIZE
  2. โœ๏ธ Set an appropriate queue size (default: 10000, range: 1000โ€“100000)
  3. ๐Ÿ’พ Save and apply the configuration

Step 4: Verify CDR Forwarding โœ…

๐Ÿ“ก After configuration, verify that CDRs are being forwarded by checking both the VOS3000 side and the external server: ๐Ÿ’ก

๐Ÿ“‹ VOS3000 Real-Time CDR Forwarding Verification:

1. Make a test call through the softswitch
2. On the external server, check for incoming CDR data:
   - Monitor the listening port for connections from VOS3000
   - Verify CDR records are being received after call completion

3. On VOS3000 server, check for forwarding errors:
   - Review softswitch logs for connection failures
   - Monitor the CDR pending queue size

4. If CDRs are not being received:
   - Verify firewall allows traffic from VOS3000 to target IP:Port
   - Confirm the external server application is listening
   - Check that EXTERNAL_SEND_CDR = On
   - Verify SERVER_CDR_REAL_TIME_REPORT_SERVER format (IP:Port)

๐Ÿ”„ CDR Queue and Delivery Guarantee – VOS3000 Real-Time CDR Forwarding

๐Ÿ›ก๏ธ The EXTERNAL_MAX_CDR_PENDING_SIZE parameter plays a critical role in ensuring CDR delivery reliability. When the external server is temporarily unreachable โ€” due to network issues, server maintenance, or application restarts โ€” VOS3000 does not simply discard the CDRs. Instead, it places them in a memory queue for automatic resend once the connection is restored. ๐Ÿ“ฆ

Queue ScenarioBehaviorRecommendation
โœ… External server onlineCDRs forwarded immediately upon call completionNormal operation โ€” no action needed
โš ๏ธ External server temporarily offlineCDRs queued up to EXTERNAL_MAX_CDR_PENDING_SIZESet queue size based on expected downtime duration
๐Ÿšจ Queue full (exceeded limit)Oldest CDRs in queue are discarded to make roomIncrease queue size or fix external server connectivity
๐Ÿ”„ External server restoredQueued CDRs automatically resent in orderVerify CDR ordering on the receiving side

๐Ÿ“ Queue sizing calculation: To determine the appropriate queue size, estimate how many CDRs might accumulate during the longest expected downtime. For example, at 100 CPS with a potential 10-minute server outage: 100 ร— 60 ร— 10 = 60,000 CDRs. Set EXTERNAL_MAX_CDR_PENDING_SIZE to at least 60000 to ensure no data loss. The default of 10000 covers approximately 100 seconds at 100 CPS, which may be insufficient for longer outages. ๐Ÿ“Š

๐Ÿ›ก๏ธ Common VOS3000 Real-Time CDR Forwarding Problems and Solutions

โŒ Misconfigured real-time CDR forwarding causes silent data loss that may go undetected for days. Here are the most common issues and their solutions: ๐Ÿ”

โŒ Problem 1: External Server Not Receiving CDRs

๐Ÿ” Symptom: The external CDR receiver shows no incoming data, even though calls are completing on VOS3000.

๐Ÿ’ก Cause: The most common reasons are: EXTERNAL_SEND_CDR is Off, SERVER_CDR_REAL_TIME_REPORT_SERVER is not configured, or a firewall is blocking the connection.

โœ… Solutions:

  • ๐Ÿ”ง Verify EXTERNAL_SEND_CDR is set to On
  • ๐Ÿ“ก Check that SERVER_CDR_REAL_TIME_REPORT_SERVER contains the correct IP:Port value
  • ๐Ÿ›ก๏ธ Ensure firewall rules allow outbound connections from VOS3000 to the target server
  • ๐Ÿ“‹ Test connectivity from the VOS3000 server: telnet target_ip target_port

โŒ Problem 2: CDRs Arriving Out of Order

๐Ÿ” Symptom: The external system receives CDRs but they are not in chronological order, causing billing calculation errors.

๐Ÿ’ก Cause: During high traffic periods, multiple CDR forwarding threads may deliver records in slightly different order than they were generated. Additionally, if the external server was temporarily unreachable and CDRs were queued, the resend order may not perfectly match the original sequence.

โœ… Solutions:

  • ๐Ÿ“Š Use the startTime field in each CDR record for ordering, not the arrival sequence
  • ๐Ÿ”ง Implement a small buffer window on the receiving side to reorder CDRs before processing
  • ๐Ÿ“‹ For the complete CDR field reference, see our VOS3000 CDR pipe format guide

โŒ Problem 3: CDR Loss During External Server Outages

๐Ÿ” Symptom: After an external server outage, some CDRs are missing from the received data.

๐Ÿ’ก Cause: The CDR queue (EXTERNAL_MAX_CDR_PENDING_SIZE) filled up during the outage, and older CDRs were discarded to make room for new ones.

โœ… Solutions:

  • ๐Ÿ“ฆ Increase EXTERNAL_MAX_CDR_PENDING_SIZE based on your maximum expected downtime
  • ๐Ÿ›ก๏ธ Implement high-availability for the external CDR receiver (redundant servers, load balancer)
  • ๐Ÿ”„ Cross-reference with VOS3000 CDR text files for missing records โ€” see our CDR file rotation guide
  • ๐Ÿ“Š Set up monitoring that alerts you immediately when the queue depth exceeds 50%

โŒ Problem 4: High CPU or Network Usage from CDR Forwarding

๐Ÿ” Symptom: VOS3000 server performance degrades noticeably after enabling real-time CDR forwarding.

๐Ÿ’ก Cause: At very high call volumes, the overhead of opening a network connection and transmitting CDR data for every single call can consume significant CPU and network resources, especially if the external server is slow to respond.

โœ… Solutions:

  • ๐Ÿ“Š Ensure the external CDR receiver can process records as fast as they arrive
  • ๐ŸŒ Use a local network connection (same datacenter) between VOS3000 and the CDR receiver
  • ๐Ÿ”ง Consider implementing a local CDR buffering proxy that batches records before forwarding
  • ๐Ÿ“‹ Monitor VOS3000 system resources to ensure forwarding does not impact call processing

๐Ÿ’ก VOS3000 Real-Time CDR Forwarding Best Practices

๐ŸŽฏ Follow these best practices to ensure reliable and efficient CDR forwarding: ๐Ÿ“‹

Best PracticeRecommendationReason
๐Ÿ›ก๏ธ Use high-availabilityRedundant CDR receiver with failoverPrevents CDR loss during receiver maintenance
๐Ÿ“ฆ Size the queue correctlyCalculate based on max downtime ร— CPSEnsures no CDRs are dropped during outages
๐Ÿ“Š Monitor queue depthAlert when queue exceeds 50% capacityEarly warning of external server problems
๐Ÿ”„ Cross-reference regularlyCompare forwarded CDRs with database records weeklyDetects silent CDR loss or duplication
๐ŸŒ Keep receiver closeSame datacenter or low-latency networkMinimizes forwarding delay and connection failures
๐Ÿ” Secure the connectionUse VPN or TLS tunnel for CDR trafficCDRs contain sensitive billing and subscriber data

๐Ÿ’ฌ Need to integrate VOS3000 with your external billing or fraud detection system? Our team at WhatsApp: +8801911119966 can help you configure real-time CDR forwarding and build the complete data pipeline. ๐Ÿš€

๐Ÿ“Š Complete VOS3000 Real-Time CDR Forwarding Parameter Reference

๐Ÿ“‹ Here is the complete reference table for all parameters related to real-time CDR forwarding, sourced from the official VOS3000 2.1.9.07 manual: ๐Ÿ”ง

ParameterDefaultRangePurpose
SERVER_CDR_REAL_TIME_REPORT_SERVERNoneIP:PortTarget server address for real-time CDR forwarding
EXTERNAL_SEND_CDROffOn/OffMaster switch for external CDR interface
EXTERNAL_MAX_CDR_PENDING_SIZE100001000โ€“100000Queue size for resend when external server is unavailable
EXTERNAL_WEB_SEND_PHONE_ONLINEOffOn/OffInterface: phone online/offline transfer

๐Ÿ“ All server parameters are located at: Navigation โ†’ Operation management โ†’ Softswitch management โ†’ Additional settings โ†’ Server parameter

โ“ Frequently Asked Questions

โ“ What is the default value for SERVER_CDR_REAL_TIME_REPORT_SERVER?

๐Ÿ“‹ The default value is None (not configured). This means VOS3000 real-time CDR forwarding is disabled by default. You must explicitly configure the IP:Port address of your external CDR receiving server and set EXTERNAL_SEND_CDR to On before any CDRs are forwarded. The parameter format is IP:Port โ€” for example, 192.168.1.100:8080 for a server at IP 192.168.1.100 listening on port 8080. ๐Ÿ”ง

โ“ Does VOS3000 real-time CDR forwarding guarantee delivery?

๐Ÿ›ก๏ธ VOS3000 provides a best-effort delivery mechanism with a configurable queue buffer. When the external server is unavailable, CDRs are queued up to the limit specified by EXTERNAL_MAX_CDR_PENDING_SIZE (default: 10000). If the queue fills up, older CDRs are discarded to make room. For guaranteed delivery, implement a high-availability CDR receiver, size the queue appropriately for your maximum expected downtime, and cross-reference with the VOS3000 CDR text file backup system described in our CDR file rotation guide. ๐Ÿ“Š

โ“ Can I forward CDRs to multiple external servers?

๐Ÿ“ก The VOS3000 SERVER_CDR_REAL_TIME_REPORT_SERVER parameter supports a single target address. To distribute CDRs to multiple downstream systems, you have two options: (1) Deploy a CDR multiplexer application at the target address that receives the CDR stream and forwards copies to multiple destinations, or (2) Use a combination of real-time forwarding for immediate processing and CDR text file rotation for batch distribution. The CDR text files can be parsed by multiple independent systems. For complex multi-system integration, contact our team at WhatsApp: +8801911119966. ๐Ÿ”—

โ“ What format are CDRs sent in during real-time forwarding?

๐Ÿ“‹ CDRs forwarded in real-time use the same pipe-delimited format as the text file export, containing all 18 standard fields: callerE164, calleeE164, startTime, stopTime, holdTime, endReason, endDirection, callerGatewayId, calleeGatewayId, callerIp, calleeIp, callerAccessE164, calleeAccessE164, callerToGatewayE164, calleeToGatewayE164, calleeBilling, billingMode, callerPdd, and calleePdd. Each field is separated by a pipe character (|). For the complete field reference, see our VOS3000 CDR pipe format guide. ๐Ÿ“Š

โ“ How do I troubleshoot real-time CDR forwarding connection issues?

๐Ÿ” Start by verifying the basics: (1) Confirm EXTERNAL_SEND_CDR is On, (2) Verify the SERVER_CDR_REAL_TIME_REPORT_SERVER value is correct (IP:Port format), (3) Test network connectivity from the VOS3000 server to the target using telnet or nc, (4) Check firewall rules on both sides, (5) Verify the external application is listening on the specified port, (6) Review VOS3000 softswitch logs for connection error messages, (7) Monitor the EXTERNAL_MAX_CDR_PENDING_SIZE queue depth to detect if CDRs are being queued due to connection failures. For additional troubleshooting, see our VOS3000 debug trace guide. ๐Ÿ”ง

โ“ Does real-time CDR forwarding affect VOS3000 call processing performance?

โšก Under normal conditions, the VOS3000 real-time CDR forwarding has minimal impact on call processing. The forwarding operation occurs after the call has ended, so it does not affect call setup or in-call quality. However, at extremely high call volumes (500+ CPS) or if the external server is slow to respond, the forwarding threads may consume additional CPU and network resources. Best practice is to keep the CDR receiver on the same local network as VOS3000 and ensure it can process records as fast as they arrive. Monitor your gateway analysis reports for any performance anomalies after enabling forwarding. ๐Ÿ“Š

๐Ÿ“ž Need Expert Help with VOS3000 Real-Time CDR Forwarding?

๐Ÿ”ง Whether you are integrating VOS3000 with an external billing engine, setting up a fraud detection pipeline, or building a real-time traffic monitoring dashboard, proper VOS3000 real-time CDR forwarding configuration is the foundation. Our VOS3000 experts can help you design and deploy the complete CDR integration architecture โ€” from softswitch parameters to the receiving application. ๐Ÿ›ก๏ธ

๐Ÿ’ฌ Contact us at WhatsApp: +8801911119966 for professional VOS3000 deployment and CDR integration support. We serve VoIP operators worldwide with proven solutions for billing, fraud prevention, and traffic analytics. ๐ŸŒ

๐Ÿ“– Explore related guides: CDR analysis and billing, billing system overview, and illegal call recording detection. ๐Ÿ”—

๐Ÿ“ž Need Professional VOS3000 Setup Support?

For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:

๐Ÿ“ฑ WhatsApp: +8801911119966
๐ŸŒ Website: www.vos3000.com
๐ŸŒ Blog: multahost.com/blog
๐Ÿ“ฅ Downloads: VOS3000 Downloads

VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction CriticalVOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction CriticalVOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical