VOS3000 CDR Billing Mode Codes Accurate -1 0 1 3 Reference

💳 Every call detail record in VOS3000 carries a billingMode field that tells you exactly how — and whether — that call was charged. The four VOS3000 CDR billing mode codes (-1, 0, 1, and 3) are the key to understanding your billing data, detecting revenue leaks, and auditing your call accounting accuracy. Yet many operators treat this field as an afterthought, only discovering its importance when a billing dispute arises or a revenue discrepancy demands investigation. 📊

⚙️ The billingMode field (Field 17 in the pipe-delimited CDR format) determines which type of account was charged for the call. A code of -1 means no billing was applied at all. A code of 0 means the call was billed to a phone number account. A code of 1 means it was billed to a gateway ID. A code of 3 means it was billed to a phone card (calling card). Each code has distinct implications for how the billing engine calculates charges, which rate table is referenced, and how the revenue is attributed in your financial reports. Misunderstanding even one of these codes can lead to incorrect billing analysis and lost revenue. 🔍

🎯 This guide provides an accurate, manual-verified reference for all four VOS3000 CDR billing mode codes. All code definitions are sourced from the official VOS3000 2.1.8.0/2.1.9.07 English manual §4.4 (page 242), with detailed explanations of how each code affects billing calculations, which account types they correspond to, and how to use them in CDR analysis and reporting. 📘

🔐 What Are VOS3000 CDR Billing Mode Codes?

📋 The VOS3000 CDR billing mode codes appear in the billingMode field (position 17) of every CDR record in the pipe-delimited text export. They indicate the charge mode — the type of billing entity that was used to calculate and record charges for the call. This is distinct from the billing method field (position 16, calleeBilling), which indicates whether the caller or callee is charged. The billing mode tells you what kind of account was charged, while the billing method tells you which party was charged.

💡 Why billing mode codes matter:

• 💰 Revenue attribution: Knowing which account type generated revenue helps you track income by business segment (retail phone, wholesale gateway, calling card)
• 🔍 Fraud detection: An unexpected billing mode code in a CDR may indicate configuration errors or unauthorized access
• 📊 Reporting accuracy: Billing reports must separate revenue by account type for financial and regulatory purposes
• 🛡️ Audit compliance: Regulators may require documentation of how each call was billed and which account was charged
• 🔧 Troubleshooting: Calls with billingMode = -1 that should have been billed indicate a billing configuration problem

📍 CDR field location: The billingMode field is at position 17 in the VOS3000 pipe-delimited CDR format, as documented in the official manual §4.4 (page 242). It appears after the calleeBilling field and before the callerPdd field.

📊 VOS3000 CDR Billing Mode Code -1: No Billing

🚫 A billingMode of -1 means the call was not billed at all. No charges were calculated, no account was debited, and no billing record was generated for the call — although the CDR itself is still recorded for operational and security purposes.

Attribute	Detail
📌 Code	-1
📝 Manual Description	No billing (VOS3000 manual §4.4: “bobilling” — a typo for “no billing”)
💰 Billing Applied	None — call is completely exempt from charges
📋 Account Debited	No account is debited

📋 When Does VOS3000 CDR Billing Mode -1 Occur?

🔍 There are several scenarios where a call receives a billingMode of -1 in VOS3000:

Scenario	Description	Expected?
🛡️ Illegal/unauthorized calls	Calls from IP addresses not registered as valid mapping gateways	✅ Yes — no account to bill
📞 Free E.164 numbers	Calls to numbers listed in SERVER_BILLING_FREE_E164S	✅ Yes — configured as free
🚫 No-CDR free numbers	Calls to numbers in SERVER_BILLING_NO_CDR_E164S	✅ Yes — configured to skip billing
⚠️ Unmatched routing	Calls that could not be matched to any account or rate table	❌ No — indicates config error
🔧 System errors	Calls that encountered a billing engine error during processing	❌ No — requires investigation

🚨 Revenue leak alert: If you find CDR records with billingMode = -1 for calls that should have been billed (normal calls to paying destinations), this indicates a billing configuration problem. The most common cause is a missing rate table entry for the destination number — VOS3000 cannot apply billing if it cannot find a matching rate. Check your rate table configuration and ensure all active destinations have valid rates assigned.

📊 VOS3000 CDR Billing Mode Code 0: Phone Number Billing

📞 A billingMode of 0 means the call was billed to a phone number account. This is the most common billing mode for retail VoIP operations where individual SIP accounts (each identified by a phone number or extension) are charged for their calls.

Attribute	Detail
📌 Code	0
📝 Manual Description	Phone number (VOS3000 manual §4.4: “phone number”)
💰 Billing Applied	Yes — charges calculated and applied to the phone number account
📋 Account Debited	Individual SIP account identified by phone number/extension

📋 How Phone Number Billing Works

🔢 When billingMode is 0, the VOS3000 billing engine identifies the calling (or called) party by their phone number or SIP account ID. The charges are applied to that specific account’s balance. The rate table lookup uses the destination number (calleeE164) matched against the account’s assigned rate table. This is the standard billing model for:

• 📞 Retail SIP accounts: Individual users with their own phone numbers and prepaid/postpaid balances
• 🏢 Business extensions: PBX extensions that are individually metered and charged
• 📱 Calling card accounts: When the calling card system maps to individual phone number accounts (distinct from phone card billing mode 3)
• 🏠 Residential VoIP: Home users with per-call billing on their personal SIP account

💡 Balance check: For prepaid phone number accounts, VOS3000 checks the account balance before allowing the call. If the balance is insufficient, the call is rejected or limited to the duration that the remaining balance can support. The SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME parameter reserves advance time to prevent accounts from going negative during active calls.

📊 VOS3000 CDR Billing Mode Code 1: Gateway ID Billing

📡 A billingMode of 1 means the call was billed to a gateway ID account. This is the dominant billing mode for wholesale VoIP operations where traffic is routed through mapping gateways and routing gateways, and the charges are applied to the gateway’s account rather than to individual phone numbers.

Attribute	Detail
📌 Code	1
📝 Manual Description	Gateway ID (VOS3000 manual §4.4: “gateway ID”)
💰 Billing Applied	Yes — charges calculated and applied to the gateway account
📋 Account Debited	Mapping gateway or routing gateway account, identified by gateway ID

📋 How Gateway ID Billing Works

🌐 When billingMode is 1, the VOS3000 billing engine attributes the call charge to the gateway through which the traffic passed. This is the standard billing model for wholesale and carrier-grade VoIP operations where traffic volume is high and individual call billing would be impractical. The gateway’s rate table is used for rate lookup, and charges are deducted from the gateway’s account balance.

📡 Common scenarios for gateway billing:

• 🔄 Wholesale termination: Carriers sending large volumes of traffic through a gateway and billed by the gateway’s aggregate rates
• 📞 Origination gateways: Incoming traffic from a PBX or softswitch is billed to the originating mapping gateway
• 🔗 Interconnect billing: Traffic exchanged between carriers, billed to the gateway representing the interconnection point
• 🏢 Enterprise PBX trunking: A business PBX connected via a SIP trunk is billed at the gateway level rather than per extension

📊 Gateway-level reporting: The billingMode = 1 designation is essential for wholesale traffic analysis. When generating revenue reports, you should filter CDRs by billingMode to separate gateway-billed wholesale revenue from phone-number-billed retail revenue. This separation is critical for understanding your business mix and margins. For more details on wholesale billing analysis, see our CDR analysis and billing guide.

📊 VOS3000 CDR Billing Mode Code 3: Phone Card Billing

💳 A billingMode of 3 means the call was billed to a phone card (calling card) account. This applies specifically to calls made through the VOS3000 IVR-based calling card system, where users dial an access number, enter their PIN, and then dial the destination number.

Attribute	Detail
📌 Code	3
📝 Manual Description	Phone card (VOS3000 manual §4.4: “phone card”)
💰 Billing Applied	Yes — charges calculated and applied to the calling card account
📋 Account Debited	Phone card (calling card) account identified by PIN/card number

📋 How Phone Card Billing Works

💳 When billingMode is 3, the VOS3000 billing engine charges the call to the calling card account that was authenticated through the IVR system. The calling card has its own balance, rate table, and billing rules that are separate from both phone number accounts and gateway accounts. The IVR system plays a balance announcement, authenticates the PIN, and manages call duration based on the card’s remaining balance.

📋 Phone card billing specifics:

• 📞 IVR authentication: The caller dials an access number, enters their PIN via DTMF, and the IVR validates the card
• 💰 Prepaid only: Phone cards are always prepaid — the card balance must be sufficient before the call is allowed
• 📊 Separate rate table: Calling card calls may use a different rate table than regular phone number accounts
• ⏱️ Duration enforcement: The maximum call duration is calculated based on the card’s remaining balance and the per-minute rate
• 🔊 Balance announcements: The IVR can announce remaining balance and maximum talk time before connecting the call

🔑 Distinguishing from billingMode 0: Do not confuse phone card billing (mode 3) with phone number billing (mode 0). Even though both involve individual accounts with balances, phone card accounts are accessed through the IVR PIN authentication flow, while phone number accounts are accessed directly via SIP registration. The billing separation ensures that calling card revenue and expenses are tracked independently from retail SIP account revenue.

📋 Complete VOS3000 CDR Billing Mode Codes Comparison Table

Code	Mode	Account Type	Billing Applied	Typical Use Case
-1	🚫 No billing	None	No	Illegal calls, free numbers, unmatched calls
0	📞 Phone number	SIP account	Yes	Retail VoIP, individual SIP accounts
1	📡 Gateway ID	Gateway account	Yes	Wholesale termination, interconnect billing
3	💳 Phone card	Calling card account	Yes	IVR-based calling card service

📊 VOS3000 CDR Billing Mode Distribution Analysis

📈 Analyzing the distribution of billing mode codes across your CDR data reveals important patterns about your traffic mix and billing health. Here is what to look for in each mode’s proportion:

Billing Mode	Healthy Range	Warning Sign	Action Required
-1 (No billing)	0–5% of total CDRs	Sudden spike in no-billing records	Investigate rate table gaps or illegal call volume
0 (Phone number)	Varies by business model	Lower than expected for retail operations	Verify SIP account billing configuration
1 (Gateway ID)	Varies by business model	Gateway-billed calls showing zero revenue	Check gateway rate tables and balances
3 (Phone card)	Only if calling card service is active	Phone card CDRs without IVR prefix	Verify IVR and calling card configuration

📊 Practical analysis tip: Run a daily query on your CDR data to count the billing mode distribution. If the percentage of mode -1 records suddenly increases, it may indicate a rate table is missing entries for a new destination, or that an attack is generating unauthorized calls. If mode 3 records appear but you do not operate a calling card service, it suggests a configuration error that needs immediate attention. Use our VOS3000 data report guide for setting up automated daily reports. VOS3000 CDR Billing Mode

📋 VOS3000 CDR Billing Mode and Related VOS3000 Parameters

🔧 Several VOS3000 parameters interact with the billing mode system. Understanding these relationships helps you configure billing correctly and interpret CDR billing mode codes accurately:

Parameter	Default	Effect on Billing Mode
SERVER_BILLING_FREE_E164S	(blank)	Calls to these numbers incur no charges — may result in billingMode = -1
SERVER_BILLING_NO_CDR_E164S	(blank)	Calls to these numbers skip CDR generation entirely — no billingMode recorded
SERVER_BILLING_RECORD_ILLEGAL_CALL	On	When On, illegal calls generate CDRs with billingMode = -1
SS_CDR_RECORD_ILLEGAL	On	When On, illegal call CDRs (mode -1) are included in text file export
SS_NO_BILLING_TO_PHONE	Off	When On, provides free billing to phone — affects billing mode attribution

💡 Parameter interaction note: The SERVER_BILLING_FREE_E164S parameter creates a distinct billing behavior from billingMode = -1. When a call matches a free E.164 number, the call is still processed through the billing engine (which may record it with a specific billing mode code), but the calculated charge is zero. This is different from billingMode = -1, which means billing was not applied at all. For details on free number configuration, see our toll-free E164 billing guide. VOS3000 CDR Billing Mode

🛡️ Common VOS3000 CDR Billing Mode Code Problems and Solutions

❌ Problem 1: Revenue Calls Showing billingMode = -1

🔍 Symptom: Calls that should generate revenue are appearing in CDR records with billingMode = -1 instead of 0 or 1.

💡 Cause: The most common cause is a missing rate table entry for the destination. When VOS3000 cannot find a matching rate for the calleeE164 in the account’s rate table, it cannot calculate a charge and assigns billingMode = -1.

✅ Solutions:

• 📊 Verify the destination has a valid rate in the appropriate rate table
• 🔧 Check that the account’s rate table assignment is correct
• 📋 Ensure prefix settings properly strip routing prefixes before rate lookup — see our gateway route prefix billing guide
• 🔍 Review the CDR billing discrepancy troubleshooting guide for systematic diagnosis

❌ Problem 2: Wrong Billing Mode for Gateway Calls

🔍 Symptom: Calls through a gateway are being billed to a phone number account (mode 0) instead of the gateway account (mode 1).

💡 Cause: The gateway’s billing configuration in the VOS3000 client may be set to bill the calling party’s phone number account rather than the gateway account. This typically happens when the mapping gateway is configured with a specific SIP account instead of billing at the gateway level.

✅ Solutions:

• 🔧 Review the mapping gateway’s billing settings in VOS3000 client
• 📋 Verify the gateway’s rate table and billing account assignment
• 📞 Check the VOS3000 account billing configuration to ensure proper billing attribution

❌ Problem 3: Unexpected billingMode = 3 Without Calling Card Service

🔍 Symptom: CDR records show billingMode = 3 (phone card) but no calling card service is deployed on this VOS3000 system.

💡 Cause: A SIP account may have been incorrectly configured with phone card billing attributes, or a mapping gateway may be routing calls through the IVR calling card module unintentionally.

✅ Solutions:

• 🔧 Audit all SIP accounts for unexpected calling card configuration
• 📋 Check mapping gateway settings for IVR routing misconfigurations
• 📊 Filter CDR records by billingMode = 3 and investigate the affected accounts

💡 VOS3000 CDR Billing Mode Code Best Practices

🎯 Follow these best practices to ensure accurate billing mode attribution and effective CDR analysis:

Best Practice	Recommendation	Reason
📊 Monitor billing mode distribution daily	Track percentage of each code	🔍 Early detection of configuration errors and fraud
🚨 Alert on billingMode = -1 spikes	Set threshold alerts for no-billing records	💰 Prevents revenue leaks from rate table gaps
📋 Separate revenue reports by billing mode	Generate distinct reports for modes 0, 1, 3	📊 Accurate revenue attribution by business segment
🔧 Validate rate table coverage	Ensure all destinations have valid rates	🛡️ Prevents unexpected billingMode = -1 records
📝 Document billing mode usage	Record which account types use which billing modes	📋 Enables faster troubleshooting and onboarding

❓ Frequently Asked Questions

❓ What does billingMode = -1 mean in VOS3000 CDR?

🚫 A billingMode of -1 in VOS3000 means no billing was applied to the call. The call record exists in the CDR for operational and security purposes, but no account was charged. This occurs for illegal/unauthorized calls from unknown IP addresses, calls to free E.164 numbers configured in SERVER_BILLING_FREE_E164S, and calls that could not be matched to any billing account or rate table. If you are seeing billingMode = -1 for calls that should generate revenue, check your rate table configuration to ensure all active destinations have valid rates. The VOS3000 manual §4.4 (page 242) documents this code as “no billing.”

❓ What is the difference between billingMode 0 and billingMode 1?

📋 billingMode 0 (phone number) bills the call to an individual SIP account identified by a phone number or extension. This is typical for retail VoIP where each user has their own account with a personal balance and rate table. billingMode 1 (gateway ID) bills the call to a gateway account. This is typical for wholesale VoIP where traffic is billed at the gateway level rather than per individual user. The distinction matters for revenue reporting — mode 0 revenue comes from retail accounts, while mode 1 revenue comes from wholesale/interconnect relationships.

❓ Can a call have different billing modes for caller and callee sides?

🔄 No, the billingMode field in the CDR represents a single billing attribution for the entire call. However, the separate calleeBilling field (position 16) does indicate which party is charged: 0 means the caller’s account is billed, and 1 means the callee’s account is billed. These two fields together provide the complete billing picture: calleeBilling tells you which side pays, and billingMode tells you what type of account is charged. For example, calleeBilling = 0 with billingMode = 1 means the caller’s gateway account is charged.

❓ Why do I see billingMode = -1 for legitimate calls?

⚠️ If legitimate, connected calls appear with billingMode = -1, the most likely cause is a missing rate table entry for the destination number. When VOS3000 cannot find a matching rate in the account’s assigned rate table, it cannot calculate charges and assigns no billing mode. Other causes include incorrect gateway route prefix configuration that transforms the destination number into something that does not match any rate table entry, or a misconfigured account that lacks a rate table assignment. Audit your rate tables and prefix settings to resolve these issues.

❓ Is billingMode = 3 only for calling card services?

💳 Yes, billingMode = 3 is specifically designated for phone card (calling card) billing in the VOS3000 manual §4.4. This code only appears when calls are authenticated through the VOS3000 IVR calling card module using a PIN. If you do not operate a calling card service and see this code in your CDRs, it indicates a configuration error where a SIP account or gateway is incorrectly associated with the calling card billing system. Investigate and correct the account configuration to prevent billing misattribution.

❓ How do I filter CDRs by billing mode in VOS3000 client?

📊 In the VOS3000 client CDR query interface (documented in manual §2.7.2), you can filter records by billing mode through the query options. The “Billing mode” filter allows you to select specific modes (Phone, Gateway, Phone card) for display. Note that the client interface uses descriptive labels rather than numeric codes — “Phone” corresponds to mode 0, “Gateway” to mode 1, and “Phone card” to mode 3. For no-billing records (mode -1), use the illegal call recording filter or query the text file export directly.

📞 Need Expert Help with VOS3000 CDR Billing Mode Codes?

🔧 Accurate interpretation of VOS3000 CDR billing mode codes is essential for billing accuracy, revenue protection, and operational intelligence. Whether you are investigating unexpected billingMode values, setting up revenue reports by billing type, or troubleshooting billing discrepancies, expert guidance ensures your analysis is correct and your billing configuration is airtight. 💰 VOS3000 CDR Billing Mode

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 CDR billing mode analysis, billing configuration, and revenue auditing. Our team specializes in VOS3000 billing system optimization, CDR analytics, and fraud detection. 🔧 VOS3000 CDR Billing Mode

🔗 Explore related VOS3000 billing and CDR configuration guides: VOS3000 CDR Billing Mode

• VOS3000 Billing System — Complete overview of the VOS3000 billing architecture
• VOS3000 CDR Analysis and Billing — Analyzing CDR data for revenue optimization
• VOS3000 CDR Billing Discrepancy — Troubleshooting billing differences between CDR records and rate tables
• VOS3000 Billing Precision — Fee decimal precision and rate unit configuration
• VOS3000 Billing Free Time — Configuring free duration for promotional billing
• VOS3000 Rate Table — Setting up rate tables for accurate billing calculations

---

📞 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

---