π Imagine this scenario: your billing team is running the end-of-month reconciliation, processing millions of CDR records to generate invoices, when a reseller launches a massive CDR query that consumes database resources and slows the entire billing run to a crawl. The VOS3000 CDR query blackout feature, controlled by SERVER_QUERY_CDR_DENY_TIME, prevents exactly this situation by blocking CDR queries during specified hours β protecting your database during critical billing windows, maintenance periods, and peak processing times. β±οΈ
π The VOS3000 CDR query blackout is a server-level parameter that defines specific hours of the day when CDR queries are denied to all users through the VOS3000 Client and web interface. During these blackout hours, any attempt to query CDR records returns a restriction notice instead of results. This ensures that database resources remain fully available for billing calculations, report generation, and system maintenance without interference from ad-hoc queries. π‘οΈ
π¬ Need to configure CDR access policies for your VOS3000 deployment? Contact our experts at WhatsApp: +8801911119966 for professional assistance with billing security and system optimization. π‘
π The VOS3000 CDR query blackout is a time-based access control mechanism that restricts CDR queries during designated hours. When enabled, users cannot search, view, or export CDR records through the VOS3000 Client or web portal during the configured blackout window. This protects database performance during periods when the system needs maximum resources for internal processing. π«
π‘ Why carriers need CDR query blackout:
π SERVER_QUERY_CDR_DENY_TIME defines the hours during which CDR queries are blocked. The parameter uses a 24-hour clock format, specifying which hours of the day are denied for CDR access. π
| Attribute | Value |
|---|---|
| π Parameter Name | SERVER_QUERY_CDR_DENY_TIME |
| π’ Default Value | None (no blackout by default) |
| π Format | Comma-separated hour values (24-hour format) |
| π Description | No CDR Query Time (24 hour) e.g. 18,19,20,21,22,23 |
| π Location | Operation management β Softswitch management β Additional settings β Server parameter |
π§ Configuration format: The parameter accepts comma-separated integer values representing the hours of the day (0β23) when CDR queries are blocked. For example, to block CDR queries from 6 PM to midnight, set the value to: 18,19,20,21,22,23. Each value represents one complete hour β setting β18β blocks queries from 18:00:00 to 18:59:59.
π Here are practical examples showing how to configure the VOS3000 CDR query blackout for different operational scenarios: π‘
| Scenario | Parameter Value | Blackout Window | Use Case |
|---|---|---|---|
| π Evening billing run | 18,19,20,21,22,23 | 6 PM β Midnight | π Monthly reconciliation during off-peak evening hours |
| π Overnight processing | 0,1,2,3,4,5 | Midnight β 6 AM | π§ Database maintenance and report generation |
| π° End-of-day billing | 22,23,0,1 | 10 PM β 2 AM | π Daily settlement across midnight boundary |
| π‘οΈ All-day restriction | 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23 | 24 hours | π¨ Complete CDR access lockdown during audits |
| β No restriction | (leave empty) | None | π Default β CDR queries available 24/7 |
β οΈ Important note: The blackout hours are specified in the serverβs local timezone. If your VOS3000 server is configured in UTC and your billing team works in a different timezone, you must convert the desired blackout window to match the server timezone. For example, if your billing team in Dhaka (UTC+6) wants to block queries from 6 PM to 10 PM local time, and the server is in UTC, the parameter should be set to 12,13,14,15,16 (6 PM UTC+6 = 12 UTC, 10 PM UTC+6 = 16 UTC). π
π₯οΈ Follow these steps to configure the CDR query blackout on your VOS3000 system: π§
π Identify the hours when CDR queries should be blocked based on your operational needs:
18,19,20,21,22,23)π After configuration, verify that the blackout is working correctly:
π The CDR query blackout works alongside several other CDR access control parameters that together form a comprehensive data protection strategy: π
| Parameter | Default | Purpose | Complements Blackout? |
|---|---|---|---|
| SERVER_QUERY_CDR_DENY_TIME | None | Blocks CDR queries during specified hours | π Core parameter |
| SERVER_QUERY_CDR_MAX_DAY_INTERVAL | 31 | Limits CDR query date range to 31 days max | β Prevents heavy queries outside blackout |
| SERVER_QUERY_MAX_ONE_PAGE_SIZE | 200000 | Maximum records per page in query results | β Limits query result size |
| SERVER_QUERY_MAX_SIZE | 30000000 | Total data query limit (items) | β Prevents runaway queries |
| SERVER_QUERY_ONE_PAGE_SIZE | 10000 | Default records per page | β Standard pagination control |
π‘ Layered protection strategy: For maximum database protection, combine the VOS3000 CDR query blackout with the date range limit (SERVER_QUERY_CDR_MAX_DAY_INTERVAL) and query size limits. The blackout prevents access during critical processing hours, while the date range and size limits prevent excessively heavy queries at any time. This layered approach ensures that even when queries are permitted, they cannot consume excessive resources. For the date range limit configuration, see our CDR query date range guide. π
β Misconfigured blackout settings can cause either insufficient protection or unexpected access denial. Here are the most common issues: π
π Symptom: Users can still query CDR records during the configured blackout hours.
π‘ Cause: The parameter value may contain formatting errors, or the configuration may not have been properly applied after saving.
β Solutions:
18,19,20 β not 18-20 or 6pm-8pm)π Symptom: CDR queries are blocked at unexpected times β not during your intended window.
π‘ Cause: The SERVER_QUERY_CDR_DENY_TIME operates on the serverβs system clock timezone, which may differ from your local timezone. If the server is configured in UTC and you specified hours in your local timezone, the blackout window will be offset.
β Solutions:
date or timedatectl on the VOS3000 Linux serverπ Symptom: Resellers complain they cannot check their CDRs during normal working hours.
π‘ Cause: The blackout window is set too broadly, covering business hours in addition to billing run periods. This is common when operators set the blackout for the entire evening without narrowing it to the actual billing processing window.
β Solutions:
π Symptom: Database performance degrades from heavy CDR queries that run outside the blackout window.
π‘ Cause: The VOS3000 CDR query blackout only restricts access during specified hours. Outside those hours, users can still run very large queries that impact performance.
β Solutions:
π― Follow these best practices to balance database protection with user access needs: π
| Best Practice | Recommendation | Reason |
|---|---|---|
| π Minimize blackout window | Cover only actual billing run hours | β Reduces impact on reseller operations |
| π Verify server timezone | Convert blackout hours to server local time | π§ Prevents misaligned blackout windows |
| π Communicate schedule | Notify all users of blackout periods | π Manages expectations and reduces support tickets |
| π‘οΈ Layer query controls | Combine blackout + date range + size limits | π Comprehensive database protection at all times |
| π Test after changes | Verify both denied and allowed periods | β Confirms correct configuration |
| π Schedule during low traffic | Align billing runs with off-peak hours | π Minimizes impact on active users |
π¬ Questions about configuring VOS3000 CDR access policies? Reach out at WhatsApp: +8801911119966 β our VOS3000 specialists can help you design a comprehensive data protection strategy. π
π The default value is None (not configured), which means there is no CDR query blackout β all users can query CDR records at any time. To enable the VOS3000 CDR query blackout, set the parameter to a comma-separated list of hours (0β23) when queries should be blocked. For example, 18,19,20,21,22,23 blocks CDR queries from 6 PM to midnight each day. π§
π Yes. The SERVER_QUERY_CDR_DENY_TIME parameter applies at the server level, which means it blocks CDR queries for all users β including administrators, agents, and resellers. There is no per-user or per-role exemption. During the blackout hours, no one can query CDR records through the VOS3000 Client or web interface. If you need differentiated access control, consider using the VOS3000 Web API with custom application-level access controls. For Web API details, see our VOS3000 Web API account management guide. π
π
No. The VOS3000 CDR query blackout applies the same hours every day. The SERVER_QUERY_CDR_DENY_TIME parameter does not support day-of-week differentiation β if you set 18,19,20, CDR queries are blocked from 6 PM to 9 PM on Monday through Sunday. If you need different schedules for weekdays vs weekends, you would need to manually change the parameter value, or implement a custom automation script that updates the parameter on a schedule. π
π The VOS3000 CDR query blackout restricts manual CDR queries through the client and web interfaces. Automated report generation (configured under Navigation β Report management) may operate independently of the blackout restriction since reports are generated by the system internally rather than through the query interface. However, if automated reports rely on the same query mechanism, they may also be affected. Always test your report generation schedule against the blackout window to ensure reports can complete successfully. For report configuration, see our billing system overview. π
π« When a user attempts to search or view CDR records during the configured blackout hours, the VOS3000 system denies the query and displays a restriction notice. The user is informed that CDR queries are not available during this time period. No partial results are returned. The query does not execute at all β it is blocked before reaching the database, ensuring zero impact on database performance during the blackout window. π
π§ Yes. To temporarily disable the VOS3000 CDR query blackout, set the SERVER_QUERY_CDR_DENY_TIME parameter to empty (None) and save the configuration. This immediately restores CDR query access for all users. After the emergency access is no longer needed, re-enter the blackout hours and save again. Remember to re-enable the blackout promptly to maintain database protection during billing runs. For help managing VOS3000 parameters, contact our team at WhatsApp: +8801911119966. π¬
π§ Proper VOS3000 CDR query blackout configuration protects your billing operations from performance disruptions while maintaining appropriate access for your resellers and support team. Whether you need to set up your first blackout window, troubleshoot timezone issues, or design a comprehensive CDR access control strategy, our VOS3000 experts are ready to assist. π‘οΈ
π¬ Contact us at WhatsApp: +8801911119966 for professional VOS3000 deployment and configuration support. We help VoIP operators worldwide optimize billing security, database performance, and operational efficiency. π
π Explore related guides: CDR query date range limit, CDR analysis and billing, and parameter description reference. π
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
π± WhatsApp: +8801911119966
π Website: www.vos3000.com
π Blog: multahost.com/blog
π₯ Downloads: VOS3000 Downloads
VOS3000 negocio VoIP mayorista: configuracion completa de terminacion mayorista, ruteo LCR, pasarelas, tarifas y gestion de trafico para operadores. Read More
Sistema VOS3000 interfaz web: control de acceso web, configuracion de equipos de servicio web y API de interfaz para operadores… Read More
Sistema VOS3000 transformacion numeros: reglas de transformacion de prefijos, manipulacion de numeros y rewrite rules para operadores VoIP. Read More
This website uses cookies.