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. 💡

🔐 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. 🎯

🔧 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.

📋 Related Parameters for External CDR Interface

🔗 Two additional parameters work alongside SERVER_CDR_REAL_TIME_REPORT_SERVER to control the external CDR delivery pipeline: 💡

⚠️ 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: 📊

📋 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 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: 📋

💬 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: 🔧

📍 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