π° In VoIP wholesale operations, traffic flows between your platform and your partnersβ platforms in both directions β you send calls to vendors and receive calls from customers. When the CDR records on both sides do not match, revenue leaks, billing disputes, and trust issues arise. The VOS3000 bilateral reconciliation feature solves this by automatically checking the amount deviation between customer and vendor accounts across two platforms. When VOS3000 bilateral reconciliation is enabled, the system verifies traffic consistency and flags discrepancies for investigation. Need help with reconciliation? Contact us on WhatsApp at +8801911119966. π§
βοΈ According to the VOS3000 V2.1.9.07 Manual Β§2.5.1.1 (page 31), the VOS3000 bilateral reconciliation is defined as: βBilateral reconciliation: reconciliation between two platform accounts.β Additionally, in the Additional settings > Others section: βEnable bilateral reconciliation: VOS will check the amount deviation of customer and vendor automatically.β The right-click menu also provides a βBilateral reconciliationβ option for manual reconciliation operations. The VOS3000 bilateral reconciliation feature ensures complete two-way traffic verification between interconnected platforms.
π― This guide provides a complete, manual-verified reference for the VOS3000 bilateral reconciliation feature. All parameter definitions are sourced exclusively from the official VOS3000 V2.1.9.07 Manual Β§2.5.1.1 (page 31). No fabricated values, no guesswork. π
π The VOS3000 bilateral reconciliation is a feature that performs automated verification of traffic and billing amounts between two VOS3000 platform accounts. When two VoIP platforms exchange traffic, each platform maintains its own CDR records. The VOS3000 bilateral reconciliation compares these records to identify discrepancies in call counts, durations, and billing amounts. When enabled, the VOS3000 bilateral reconciliation automatically checks the amount deviation of customer and vendor traffic.
π‘ Key characteristics of VOS3000 bilateral reconciliation:
| Attribute | Detail |
|---|---|
| π Feature Name | Bilateral reconciliation |
| π Manual Description | βBilateral reconciliation: reconciliation between two platform accounts.β (VOS3000 V2.1.9.07 Manual Β§2.5.1.1, page 31) |
| π Configuration Path (Automatic) | Routing gateway > Additional settings > Others > Enable bilateral reconciliation |
| π Manual Trigger | Right-click menu > Bilateral reconciliation |
| π Additional Description | βEnable bilateral reconciliation: VOS will check the amount deviation of customer and vendor automatically.β |
| π Scope | Between two platform accounts β customer and vendor |
π§ The VOS3000 bilateral reconciliation operates by comparing CDR records and billing amounts between two interconnected VOS3000 platforms. When enabled, the VOS3000 bilateral reconciliation automatically checks the amount deviation between what the customer account records and what the vendor account records for the same traffic. Discrepancies are flagged for investigation.
| Step | Description |
|---|---|
| 1οΈβ£ Traffic exchange | Two VOS3000 platforms exchange VoIP traffic in both directions |
| 2οΈβ£ CDR generation | Each platform generates its own CDR records for the traffic |
| 3οΈβ£ Automatic deviation check | VOS3000 bilateral reconciliation compares customer and vendor amounts automatically |
| 4οΈβ£ Discrepancy detection | Amount deviations between the two accounts are identified and flagged |
| 5οΈβ£ Investigation | Flagged discrepancies can be investigated to resolve billing differences |
π‘ Practical example: Platform A sends 10,000 minutes of traffic to Platform B. Platform Aβs CDRs show 10,000 minutes billed at $500. Platform Bβs CDRs show 9,850 minutes billed at $492.50. The VOS3000 bilateral reconciliation detects a deviation of 150 minutes ($7.50) between the two platforms. This discrepancy could be caused by call setup failures, different billing increments, or CDR recording differences. Without the VOS3000 bilateral reconciliation, this $7.50 discrepancy would go unnoticed and could compound over time into significant revenue loss.
π The VOS3000 bilateral reconciliation can be performed both automatically and manually. Understanding the difference is important for effective reconciliation operations.
| Aspect | Automatic Reconciliation | Manual Reconciliation |
|---|---|---|
| π Trigger | Automatic β runs continuously when enabled | On-demand β triggered via right-click menu |
| π Configuration | Additional settings > Others > Enable bilateral reconciliation | Right-click menu > Bilateral reconciliation |
| π Scope | Checks amount deviation of customer and vendor automatically | User selects specific accounts and time range for reconciliation |
| π§ Use case | Ongoing monitoring β detects deviations as they occur | Periodic audits β detailed reconciliation at specific intervals |
| π° Benefit | Early detection β catches discrepancies immediately | Thorough review β detailed analysis of specific traffic patterns |
π‘ Recommendation: Use both automatic and manual VOS3000 bilateral reconciliation together. Enable the automatic VOS3000 bilateral reconciliation for continuous monitoring, and perform manual reconciliation periodically for thorough audits. The automatic VOS3000 bilateral reconciliation catches deviations early, while the manual VOS3000 bilateral reconciliation provides detailed analysis for dispute resolution. For billing best practices, see our billing FAQ guide.
π§ When the VOS3000 bilateral reconciliation detects amount deviations, the root cause typically falls into one of several categories. Understanding these causes helps you resolve discrepancies quickly.
| Deviation Cause | Description | Resolution |
|---|---|---|
| π Billing increment differences | Different billing increments (1s vs 6s vs 60s) cause rounding differences in call duration and amount | π§ Align billing increments with partner platform or accept small deviations |
| π° Rate table differences | Different rate table entries on the two platforms produce different billing amounts for the same call | π Synchronize rate tables between platforms |
| π« CDR recording gaps | One platform fails to record a call that the other platform records β call setup failures, timeouts | π Investigate call end reasons to identify failed calls |
| π Time zone differences | CDR timestamps in different time zones cause calls to be recorded on different dates | π§ Align time zone settings between platforms |
| π Minimum duration differences | Different minimum call duration settings cause calls to be billed differently | π§ Synchronize minimum duration settings between platforms |
π Symptom: The VOS3000 bilateral reconciliation consistently shows amount deviations with a specific partner platform, and the deviations are growing over time.
π‘ Cause: Systematic differences in billing configuration between the two platforms β different billing increments, rate tables, or minimum duration settings. The VOS3000 bilateral reconciliation is correctly detecting these differences.
β Solutions:
π Symptom: You know there are billing discrepancies with a partner, but the VOS3000 bilateral reconciliation is not flagging them.
π‘ Cause: The VOS3000 bilateral reconciliation may not be enabled on the gateway, or the automatic deviation check may be configured with a tolerance that exceeds the actual deviation amount.
β Solutions:
π Symptom: The VOS3000 bilateral reconciliation process is very slow, especially for high-traffic partnerships with millions of CDR records.
π‘ Cause: Large volumes of CDR records and complex deviation calculations can slow down the reconciliation process, particularly for long time ranges.
β Solutions:
| Best Practice | Recommendation | Reason |
|---|---|---|
| π Enable automatic reconciliation | Enable VOS3000 bilateral reconciliation on all gateway connections with partner platforms | π‘οΈ Catches deviations early before they compound into significant amounts |
| π° Perform periodic manual audits | Use the right-click Bilateral reconciliation option for detailed periodic audits | π Provides thorough verification beyond automatic deviation detection |
| π Align billing configurations | Synchronize billing increments, rate tables, and minimum durations with partner platforms | π§ Reduces the root causes of amount deviations |
| π Investigate deviations promptly | Review and resolve flagged deviations quickly rather than letting them accumulate | π Prevents small discrepancies from becoming large billing disputes |
| π Document reconciliation results | Keep records of reconciliation findings and resolutions for audit trails | π Supports dispute resolution and regulatory compliance |
π The VOS3000 bilateral reconciliation works closely with the CDR analysis module. When the VOS3000 bilateral reconciliation detects deviations, you need CDR analysis to drill down into the specific calls causing the discrepancies. Together, the VOS3000 bilateral reconciliation identifies that a deviation exists, and CDR analysis identifies which specific calls are responsible.
| Workflow Step | Tool | Action |
|---|---|---|
| 1οΈβ£ Deviation detection | VOS3000 bilateral reconciliation | Identifies amount deviation between customer and vendor accounts |
| 2οΈβ£ CDR comparison | CDR analysis | Compares individual call records between platforms |
| 3οΈβ£ Root cause identification | CDR analysis + Call end reasons | Identifies specific calls and reasons for discrepancies |
| 4οΈβ£ Resolution | Configuration adjustments | Align billing settings, update rate tables, or accept documented deviations |
π‘ Key insight: The VOS3000 bilateral reconciliation is the starting point for traffic verification. It tells you that a deviation exists and how large it is. The CDR analysis tells you why the deviation exists by identifying the specific calls and billing differences. Using the VOS3000 bilateral reconciliation together with CDR analysis provides complete two-way traffic verification. For CDR billing discrepancy resolution, see our related guide.
π° The VOS3000 bilateral reconciliation is a feature that performs reconciliation between two platform accounts. According to the VOS3000 V2.1.9.07 Manual Β§2.5.1.1 (page 31), βBilateral reconciliation: reconciliation between two platform accounts.β When enabled, βVOS will check the amount deviation of customer and vendor automatically.β The VOS3000 bilateral reconciliation ensures complete two-way traffic verification between interconnected platforms by detecting billing amount deviations.
π To enable the VOS3000 bilateral reconciliation, navigate to the routing gatewayβs Additional settings, open the Others section, and check the βEnable bilateral reconciliationβ option. This enables automatic amount deviation checking between the customer and vendor accounts for that gateway. You can also access the VOS3000 bilateral reconciliation manually via the right-click menu on the gateway, which provides the βBilateral reconciliationβ option for on-demand reconciliation operations.
π The automatic VOS3000 bilateral reconciliation runs continuously when enabled, checking the amount deviation of customer and vendor accounts automatically. The manual VOS3000 bilateral reconciliation is triggered on-demand via the right-click menu, allowing you to select specific accounts and time ranges for detailed reconciliation. Both methods serve the same purpose β verifying traffic consistency between platforms β but the automatic VOS3000 bilateral reconciliation provides continuous monitoring while the manual option provides detailed analysis for specific periods.
π§ Common causes of amount deviations detected by the VOS3000 bilateral reconciliation include: different billing increments between platforms (e.g., one uses 1-second billing while the other uses 6-second billing), different rate table entries producing different billing amounts, CDR recording gaps where one platform fails to record a call, time zone differences causing calls to be recorded on different dates, and different minimum call duration settings. The VOS3000 bilateral reconciliation identifies that a deviation exists, and CDR analysis helps determine the specific cause.
π The VOS3000 bilateral reconciliation is designed for reconciliation between two VOS3000 platform accounts. It works best when both platforms are running VOS3000 and can exchange CDR data for comparison. If your partner uses a different softswitch, the VOS3000 bilateral reconciliation may have limited functionality because CDR format and billing calculations may differ. For cross-platform reconciliation, you may need to export CDRs and perform manual comparison. Contact us on WhatsApp at +8801911119966 for cross-platform reconciliation guidance.
π If the automatic VOS3000 bilateral reconciliation is enabled, it runs continuously and you do not need to schedule it separately. For manual reconciliation, it is recommended to run the VOS3000 bilateral reconciliation at least monthly for each partner platform, or more frequently for high-volume partnerships. Weekly reconciliation allows you to catch and resolve deviations before they accumulate into significant amounts. The VOS3000 bilateral reconciliation frequency should match your billing cycle and partner agreement terms.
π No, the VOS3000 bilateral reconciliation does not affect call routing. It is a billing verification feature that compares CDR records and amounts between platforms after calls have been completed. The VOS3000 bilateral reconciliation operates on historical data, not live traffic. However, if the VOS3000 bilateral reconciliation reveals significant deviations, you may choose to adjust routing, billing, or partner configuration to prevent future discrepancies. The VOS3000 bilateral reconciliation is a monitoring tool, not a routing control. See our profit margin guide for routing-related cost controls.
π§ The VOS3000 bilateral reconciliation is a critical billing integrity feature that ensures complete two-way traffic verification between interconnected platforms. When configured correctly, the VOS3000 bilateral reconciliation detects amount deviations early, supports dispute resolution, and prevents revenue leakage. Whether you are enabling the VOS3000 bilateral reconciliation for the first time, investigating persistent deviations, or setting up reconciliation with a new partner platform, expert guidance ensures your billing verification is accurate and effective. π°
π¬ WhatsApp: +8801911119966 β Get immediate assistance with VOS3000 bilateral reconciliation configuration, deviation investigation, CDR analysis, and partner billing alignment. Our team specializes in VOS3000 billing, reconciliation, and carrier-grade VoIP financial operations. π§
π Explore related VOS3000 billing and analysis guides:
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
π± WhatsApp: +8801911119966
π Website: www.vos3000.com
π Blog: multahost.com/blog
π₯ Downloads: VOS3000 Downloads
Master VOS3000 gateway group reserved lines configuration. Guarantee capacity for priority customers, prevent starvation during…
Master VOS3000 G729 Annex B silence suppression with 5 modes: Auto, Yes, No, None, Passthrough.…
Configure VOS3000 T38 fax over IP for essential fax protocol support. Enable T.38 signal for…
Configure VOS3000 SIP OPTIONS online check for reliable gateway health monitoring. Auto-detect SIP port reachability…
Configure VOS3000 auxiliary ring tone with flexible activation delay. Set custom ringback tone timing per…
Configure VOS3000 LRN number portability for proven US carrier lookup. Enable Local Routing Number queries…