VOS3000 Billing Overdraft Prevention Proven Advance Time Configuration
VOS3000 billing overdraft prevention is a crucial mechanism that protects VoIP operators from revenue loss when accounts go negative during active calls. The SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME parameter reserves a configurable advance time window (1-15 minutes) to ensure that concurrent calls cannot drain an account below zero. Need help setting this up? Contact us on WhatsApp: +8801911119966 for professional VOS3000 configuration assistance.
Without proper overdraft prevention, a client with a small remaining balance can initiate multiple concurrent calls, each consuming credit in real time. Because billing deductions happen at call termination, the account can easily fall into negative territory. This parameter proactively reserves advance time, blocking new calls before the balance is exhausted.
Table of Contents
How VOS3000 Billing Overdraft Prevention Works
The SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME parameter (defined in manual section §4.3.5.1) sets a reservation window in minutes that the billing engine deducts from the available balance before a call is connected. This reserved amount acts as a buffer against overdraft scenarios caused by concurrent calls or billing latency. The parameter accepts values from 1 to 15 minutes, giving operators flexibility to match their traffic patterns and risk tolerance.
📋 Parameter
📋 Detail
Parameter Name
SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME
Manual Section
§4.3.5.1 Server Billing Parameters
Value Range
1-15 minutes
Default Value
1 minute
Purpose
Reserve advance billing time to prevent account overdrafts
Advance Time Reservation Calculation Logic
When a client initiates a call, VOS3000 billing overdraft prevention works by calculating the maximum potential charge for the configured advance time period. This reserved amount is temporarily deducted from the available balance before the call is authorized. If the remaining balance after reservation is insufficient to cover the advance time at the applicable rate, the call is rejected. Once the call ends, the actual billing amount replaces the reservation, and any excess reserved credit is released back to the account.
📋 Step
📋 Billing Engine Action
📋 Description
1
Calculate advance reservation
Rate × advance time minutes
2
Deduct from available balance
Temporarily reserve the advance amount
3
Check sufficiency
If remaining balance ≥ 0, authorize call
4
Call proceeds
Actual billing accumulates during call
5
Call terminates
Actual charge replaces reservation
6
Release excess reservation
Unused reserved credit returned to balance
Choosing the Right Advance Time Value
Selecting the appropriate advance time value for VOS3000 billing overdraft prevention depends on your typical call duration patterns, average concurrent call count per client, and the rate structures you use. Operators with high-concurrency clients should set higher advance times, while those with simple single-call patterns can use the minimum value. For a tailored recommendation, message us on WhatsApp: +8801911119966.
📋 Advance Time
📋 Protection Level
📋 Client Impact
📋 Best For
1 minute
Basic
Minimal balance reservation
Low-concurrency retail clients
3 minutes
Moderate
Small reservation per call
Standard wholesale operators
5 minutes
Strong
Moderate balance hold
High-concurrency trunk clients
10 minutes
Very Strong
Significant reservation
Premium routes with high rates
15 minutes
Maximum
Largest balance hold
Maximum risk environments
Overdraft Scenario Without Prevention
To understand why VOS3000 billing overdraft prevention matters, consider a client with a $10.00 balance and a rate of $0.50 per minute. Without advance time reservation, the client could initiate 20 concurrent calls. Each call runs for 5 minutes, consuming $2.50 each. At termination, the total charge is $50.00, leaving the account at -$40.00. With a 5-minute advance reservation, the system would have blocked calls after the first two, capping the maximum possible loss.
Setting up VOS3000 billing overdraft prevention is straightforward but requires careful consideration of your traffic patterns. Navigate to the server billing parameters section in the VOS3000 admin interface and adjust the advance time value. Always test with a small subset of clients before applying changes system-wide.
Revenue Protection Strategy with Overdraft Prevention
Integrating VOS3000 billing overdraft prevention into your overall revenue protection strategy goes beyond simply setting the advance time parameter. You should combine this with credit limit monitoring, CDR-based audit trails, and real-time balance alerts. The advance time parameter works as a first line of defense, but a layered approach provides comprehensive protection against both accidental and intentional overdraft scenarios.
Frequently Asked Questions About VOS3000 Billing Overdraft Prevention
What does SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME do?
SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME is a VOS3000 server billing parameter that reserves a specified number of minutes (1-15) of advance billing time when a call is initiated. This reservation temporarily reduces the available balance by the maximum potential charge for that advance period, preventing the account from going into negative territory due to concurrent calls or billing delays. When the call terminates, the actual charge replaces the reservation and any unused reserved credit is returned to the account balance.
What is the valid range for the advance time parameter?
The valid range for SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME is 1 to 15 minutes. The minimum value of 1 minute provides basic protection suitable for retail clients with low concurrency. The maximum value of 15 minutes offers the strongest protection for high-risk scenarios with expensive routes and high concurrent call volumes. Values outside this range are not accepted by the VOS3000 system. The default value is 1 minute, which provides minimal but functional overdraft protection out of the box.
How does VOS3000 billing overdraft prevention handle multiple concurrent calls?
When a client has multiple concurrent calls, VOS3000 billing overdraft prevention reserves advance time for each call independently. Each new call attempt checks whether the remaining balance after the advance reservation would still be non-negative. If the balance after reservation would fall below zero, the new call is rejected while existing calls continue uninterrupted. This means a client with a $10 balance and a 5-minute advance at $1/minute can only have 2 concurrent calls authorized, as each requires a $5 reservation. The third call would be blocked because the system cannot reserve another $5 from the remaining balance.
Will setting a higher advance time block legitimate calls?
Yes, setting a higher advance time can potentially block legitimate calls for clients with smaller balances, because each call requires a larger reservation. For example, with a 10-minute advance time at $0.50 per minute, each call reserves $5.00 from the balance. A client with a $6.00 balance could only make one concurrent call, even though they have enough credit for a long-duration single call. You should carefully balance protection level against client experience, and consider using different advance time values for different client tiers based on their typical balance levels and call patterns.
Can I configure different advance times for different clients?
The SERVER_BILLING_PREVENT_OVERDRAFT_ADVANCE_TIME parameter is a server-level setting that applies uniformly to all clients on the VOS3000 system. It cannot be configured individually per client or per rate plan through this parameter alone. However, you can achieve similar per-client differentiation by combining this parameter with individual credit limits and concurrent call limits set at the client level. For more granular overdraft control strategies, contact our team on WhatsApp: +8801911119966 for a customized configuration plan.
What happens to the reserved advance time after a call ends?
After a call terminates, VOS3000 calculates the actual billing amount based on the real call duration and applicable rate. This actual charge is applied to the account, and the previously reserved advance time amount is released. If the actual charge is less than the reserved amount (which is typical for short calls), the difference is immediately returned to the client’s available balance. If the actual charge equals or exceeds the reservation, the full reservation is consumed. This ensures that the advance reservation only temporarily restricts the balance and does not result in overcharging the client.
How does overdraft prevention interact with the billing time precision setting?
VOS3000 billing overdraft prevention and the hold time precision setting (SERVER_BILLING_HOLD_TIME_PRECISION) work together in the billing pipeline but serve different purposes. The advance time reservation determines how much balance to reserve before a call starts, while the hold time precision determines how the actual call duration is rounded for billing after the call ends. Both parameters affect the final billing amount, but they operate at different stages. The advance reservation uses the rate and configured minutes to calculate a maximum potential charge, while hold time precision rounds the measured duration to determine the actual billable seconds. Optimizing both parameters together ensures comprehensive billing accuracy.
Get Professional Help with VOS3000 Billing Overdraft Prevention
Protecting your VoIP revenue with proper VOS3000 billing overdraft prevention configuration is essential for sustainable operations. Whether you need to set up advance time reservation for the first time, optimize your current settings to reduce false call blocks, or implement a comprehensive multi-layer revenue protection strategy, our experienced VOS3000 engineers are here to help you every step of the way.
Contact us on WhatsApp: +8801911119966
📞 Need Professional VOS3000 Setup Support?
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
Welcome to the ultimate guide on VOS3000 agent account configuration and reseller authorization management. If you’re running a VoIP wholesale or retail business using VOS3000, understanding how agent accounts work is absolutely critical for scaling your operations, delegating responsibilities, and building a profitable multi-level reseller network.
The VOS3000 agent account system is one of the most powerful features in the VOS3000 softswitch platform. It allows administrators to create hierarchical account structures where parent accounts (agents) can manage their own sub-accounts, handle payments, configure gateways, and even create sub-agents — all without needing direct admin intervention for every task.
In this comprehensive guide, we’ll walk through every aspect of the VOS3000 agent account system — from basic setup to advanced authorization management, sub-account filtering, number section limitations, and real-world deployment scenarios. Whether you’re a system administrator, a VoIP operator, or a reseller yourself, this guide has everything you need.
A VOS3000 agent account is a specialized account type within the VOS3000 softswitch that has the authority to manage other accounts beneath it — known as sub-accounts. Unlike ordinary accounts that simply originate or terminate calls, an agent account acts as a managerial entity that can create, modify, delete, and control its subordinate accounts.
According to the VOS3000 User Manual (Section 2.4.3, Page 22):
“Agent accounts differ from ordinary accounts in that there are accounts belonging to agent accounts. Once an account becomes an agent account, it will appear in the navigation tree.”
This means that the moment an account has sub-accounts assigned to it, VOS3000 automatically recognizes it as an agent account. The system then provides additional management capabilities and UI elements (like the navigation tree entry) that are not available for ordinary accounts.
💡 Why VOS3000 Agent Accounts Matter for Your Business
In the VoIP industry, the VOS3000 agent account system is the backbone of reseller operations. Here’s why it matters:
🔑 Delegation of Control: System admins don’t need to manage every single end-user account. Agent accounts can handle their own sub-account management.
💰 Revenue Distribution: Each agent manages their own payment collection, making multi-level billing seamless.
📊 Scalability: As your business grows from 10 customers to 10,000, the agent hierarchy keeps everything organized.
🛡️ Security: Agent accounts can only manipulate their own sub-accounts, ensuring data isolation and security.
⚡ Efficiency: Agents can perform routine operations (adding phones, making payments) without waiting for admin approval.
The VOS3000 agent account system is specifically designed to “facilitate agent development” (VOS3000 Manual, Section 2.4.5, Page 24), meaning it provides the tools resellers need to grow their business independently while the platform maintains overall control.
⚖️ Agent Account vs. Ordinary Account: Key Differences
Understanding the distinction between ordinary and agent accounts in VOS3000 is fundamental to proper system configuration. Let’s examine the critical differences:
🔄 Feature
👤 Ordinary Account
🏢 VOS3000 Agent Account
Sub-Accounts
❌ Cannot have sub-accounts
✅ Can manage sub-accounts
Navigation Tree
❌ Not visible in navigation tree
✅ Appears in navigation tree
Account Management
❌ Cannot add/modify/delete accounts
✅ Can manage sub-accounts (with authorization)
Payment Control
❌ No payment authority
✅ Can process payments for sub-accounts
Gateway Management
❌ No gateway access
✅ Can add/modify gateways (with authorization)
Phone Card Operations
❌ Cannot manage phone cards
✅ Can add/delete/modify phone cards
Account Category
“Account” (non-editable)
“Agent” (non-editable)
Scope of Control
Own account only
Own account + all sub-accounts
As shown in the table above, the VOS3000 agent account transforms a simple calling account into a management powerhouse. The key insight from the VOS3000 manual (Section 2.4.2, Page 16) is that the account category field is non-editable — it’s automatically determined by the system based on whether the account has sub-accounts or not.
⚙️ How VOS3000 Agent Accounts Work
The VOS3000 agent account system operates on a hierarchical principle. Let’s break down the core mechanics:
🔄 Automatic Agent Promotion
One of the most important concepts in VOS3000 is that agent status is automatically assigned. When you create an account and assign sub-accounts to it (by setting the Agent ID field on those sub-accounts), the parent account automatically becomes an agent account. The VOS3000 manual (Section 2.4.2, Page 16) states:
“When an account has sub accounts, it automatically becomes an agent.”
This means you don’t need to manually flip a switch to create an agent account — the system handles this dynamically based on the account relationships you establish.
🔗 The Agent ID Field
Every account in VOS3000 has an Agent ID field. This field specifies the parent account (the agent) to which this account belongs. Key rules:
📌 The Agent ID must reference an existing account in the system
📌 The parent account must exist before you can assign it as an Agent ID
📌 An account without an Agent ID is a top-level account (or a standalone account)
📌 When an account is created by an agent, it must be designated to an agent account (VOS3000 Manual, Section 2.4.5, Page 25)
The Agent ID relationship forms the backbone of the entire VOS3000 agent account hierarchy and determines the chain of command within your reseller network.
🛡️ Scope of Manipulation
A critical security feature of the VOS3000 agent account system is that an agent account can only manipulate its own sub-accounts (VOS3000 Manual, Section 2.4.5, Page 25). This means:
🔒 Agent A cannot see or modify Agent B’s sub-accounts
🔒 Each agent’s scope is strictly limited to their own hierarchy
🔒 Even sub-agents created by an agent fall under that agent’s control
🔒 Only system administrators have access to all accounts
This design ensures complete isolation between different resellers using the same VOS3000 platform — a fundamental requirement for multi-tenant VoIP operations.
📝 Step-by-Step: Creating a VOS3000 Agent Account
Creating a VOS3000 agent account involves several steps. Let’s walk through the complete process:
Step 1: Create the Parent Account
First, you need to create the account that will become the agent. Navigate to the Account Management section in VOS3000:
🖥️ Log in to VOS3000 with administrator credentials
📋 Navigate to Account Management (Section 2.4.2, Page 16)
➕ Click Add to create a new account
📝 Fill in the required account details
💾 Save the account
Step 2: Assign Sub-Accounts to the Agent
To transform the ordinary account into a VOS3000 agent account, you need to assign sub-accounts:
👤 Create a new account (or edit an existing one)
🔗 In the Agent ID field, enter the account ID of the parent account
✅ The parent account must already exist in the system
💾 Save the sub-account
🔄 The parent account automatically becomes an agent account
Step 3: Verify Agent Account Status
After assigning sub-accounts, verify that the account has been promoted to agent status:
🔍 Check the Account Category field — it should now display “Agent”
🌲 Look for the account in the navigation tree — it should now appear there
📂 Double-click the agent account to open the Sub Account Management interface
Step 4: Configure Authorizations
Now configure what operations the VOS3000 agent account can perform. This is covered in detail in the Authorization Management section below.
The complete workflow can be summarized in this configuration checklist:
🔢 Step
📋 Action
✅ Verification
1
Create parent account
Account appears in account list
2
Create sub-account with Agent ID
Agent ID field populated correctly
3
Verify agent promotion
Category shows “Agent”, appears in navigation tree
4
Configure authorizations
Permissions enabled as needed
5
Set number section limitations
Prefix restrictions applied
6
Test agent operations
Agent can perform authorized tasks
📂 Sub-Account Management in VOS3000
Once an account becomes a VOS3000 agent account, it gains access to the Sub-Account Management interface. This is where agents can view, manage, and control all accounts under their jurisdiction.
🔑 Accessing Sub-Account Management
According to the VOS3000 manual (Section 2.4.3, Page 22):
“Double-click the agent account to open ‘Sub account management’.”
This simple action opens a dedicated management interface for that specific agent’s sub-accounts. From here, the agent can perform all authorized operations on their sub-accounts.
🔍 Direct vs. All Sub-Account Filter
The Sub-Account Management interface provides two important filter options (VOS3000 Manual, Section 2.4.3, Page 22):
🔎 Filter
📋 Description
📌 Use Case
Direct
Shows only the immediate (first-level) sub-accounts
Quick view of directly managed accounts
All
Shows all sub-accounts including sub-sub-accounts (nested)
Complete hierarchical view of entire agent tree
The distinction between “Direct” and “All” is especially important in multi-level reseller scenarios. When an agent creates a sub-agent (who in turn has their own sub-accounts), the “Direct” filter shows only the immediate children, while “All” reveals the entire hierarchy beneath that agent.
⚡ Sub-Account Operations
From the Sub-Account Management interface, authorized agents can perform the following operations on their sub-accounts:
➕ Add new sub-accounts — Create new customer or sub-agent accounts
✏️ Modify sub-accounts — Update account settings, rates, and configurations
🗑️ Delete sub-accounts — Remove accounts that are no longer needed
📞 Add/delete/modify phones — Manage phone numbers for sub-accounts
💰 Process payments — Add credit/balance for sub-accounts
Each of these operations requires the corresponding authorization to be enabled for the VOS3000 agent account, which we’ll cover in the next section.
🔐 VOS3000 Agent Authorization Management
Authorization management is the heart of the VOS3000 agent account system. It determines exactly what operations an agent can and cannot perform. The VOS3000 manual (Section 2.4.5, Pages 24-25) provides a comprehensive list of authorizations that can be granted to agent accounts.
🛡️ Why Authorization Management Matters
Proper authorization configuration is essential because:
🔒 Security: Prevents unauthorized operations that could disrupt service or cause financial loss
🎯 Role-Based Access: Different agents may need different levels of control based on their business role
📈 Business Control: Administrators can limit what agents can do to maintain oversight
⚖️ Compliance: Ensures agents operate within the boundaries defined by the platform operator
🔄 Flexibility: Authorization can be adjusted as business relationships evolve
As stated in the VOS3000 manual (Section 2.4.5, Page 24):
“This function facilitates agent development. Agent user can have agent-typed account in system. Admins can create accounts limiting rights.”
This means the system administrator retains ultimate control — they decide which authorizations each VOS3000 agent account receives, enabling a fine-grained approach to permission management.
📋 Complete Authorization List
The following table lists all available authorizations for VOS3000 agent accounts as documented in the VOS3000 User Manual (Section 2.4.5, Pages 24-25):
🔢 #
🔐 Authorization
📋 Description
⚠️ Risk Level
1
Add/delete/modify account
Create new sub-accounts, remove existing ones, or modify account details
🔴 High
2
Add/delete/modify phone
Manage phone number assignments for sub-accounts
🟡 Medium
3
Add/delete/modify phone card
Manage calling card configurations for prepaid services
🟡 Medium
4
Add/delete gateway
Create or remove SIP gateways/trunk endpoints
🔴 High
5
Modify gateway information
Update gateway settings such as IP, port, codec, and protocol
🔴 High
6
Modify gateway capacity
Adjust concurrent call capacity limits on gateways
🟡 Medium
7
Payment for this account
Process payments/credit top-ups for the agent’s own account
🔴 High
8
Payment for sub accounts
Process payments/credit top-ups for all sub-accounts
🔴 High
Each authorization can be independently enabled or disabled for each VOS3000 agent account, giving administrators precise control over what each agent can do.
🔍 Detailed Breakdown of Authorization Types
Let’s examine each authorization type in detail to understand exactly what they enable and when you should grant them.
1️⃣ Add/Delete/Modify Account Authorization
This is the most fundamental authorization for a VOS3000 agent account. It allows the agent to:
➕ Add: Create new sub-accounts under the agent’s hierarchy
🗑️ Delete: Remove existing sub-accounts that are no longer needed
✏️ Modify: Edit sub-account settings including rates, codecs, prefixes, and more
When to grant: This authorization should be granted to any agent who needs to manage their own customer base. Without this, the agent cannot independently onboard new customers or modify existing ones.
Important note: As stated in the VOS3000 manual (Section 2.4.5, Page 25):
“Accounts created by agent must be designated to an agent account.”
This means every account created by an agent is automatically linked back to that agent — they cannot create “orphan” accounts that exist outside the agent hierarchy.
2️⃣ Add/Delete/Modify Phone Authorization
This authorization allows the VOS3000 agent account to manage phone numbers for sub-accounts:
📞 Add: Assign new phone numbers to sub-accounts
🗑️ Delete: Remove phone numbers from sub-accounts
✏️ Modify: Update phone number settings and configurations
When to grant: Essential for agents who manage DID numbers or need to assign specific caller IDs to their sub-accounts. Particularly important for retail VoIP resellers.
3️⃣ Add/Delete/Modify Phone Card Authorization
Phone card management is crucial for prepaid calling card businesses:
💳 Add: Create new calling card batches
🗑️ Delete: Remove calling card configurations
✏️ Modify: Update calling card rates and settings
When to grant: Only for agents who specifically operate calling card services. This authorization should be withheld from agents who don’t need calling card functionality.
4️⃣ Add/Delete Gateway Authorization
Gateway management is one of the highest-risk authorizations:
🌐 Add: Create new SIP gateways or trunk endpoints for sub-accounts
🗑️ Delete: Remove existing gateway configurations
When to grant: Only for trusted agents who need to configure their own SIP trunks or gateway endpoints. Most resellers do not need this authorization — the administrator typically manages gateway configurations centrally.
This authorization allows updating existing gateway settings:
🔧 IP Address: Change the gateway IP address
🔌 Port: Modify the SIP signaling port
🎵 Codec: Update the supported codec list
📡 Protocol: Change SIP protocol settings
📝 Prefix: Modify dial prefix configurations
When to grant: For agents who manage their own SIP infrastructure and need to update gateway parameters when their network changes. This is a high-risk authorization that should be carefully controlled.
6️⃣ Modify Gateway Capacity Authorization
This authorization controls the ability to adjust gateway concurrent call limits:
📊 Increase capacity: Allow more simultaneous calls through a gateway
📉 Decrease capacity: Reduce the number of simultaneous calls
When to grant: Useful for agents who need to manage their own bandwidth allocation. For instance, a reseller might need to increase capacity during peak hours and reduce it during off-peak times.
7️⃣ Payment for This Account Authorization
This authorization allows the VOS3000 agent account to process payments (credit top-ups) for its own account:
💰 Add balance: Increase the account’s calling credit
📋 View payment history: Track all payment transactions
When to grant: This is typically granted to agents who operate on a prepaid model and need to manage their own balance. However, in most wholesale setups, the administrator manages top-ups centrally, so this authorization is often disabled.
8️⃣ Payment for Sub Accounts Authorization
This is perhaps the most business-critical authorization for resellers:
💰 Top up sub-accounts: Add credit to customer accounts
📊 Manage sub-account balances: Distribute credit across multiple sub-accounts
📋 Track payments: Monitor all payment activities in the sub-account hierarchy
When to grant: Essential for any VOS3000 agent account that operates as a reseller. Without this, the agent cannot manage their customers’ balances, which is a core reseller function.
The following authorization matrix shows recommended configurations for different agent types:
🔐 Authorization
🛒 Retail Reseller
🏭 Wholesale Agent
💳 Calling Card Agent
🌐 SIP Trunk Provider
Add/delete/modify account
✅
✅
✅
✅
Add/delete/modify phone
✅
❌
❌
✅
Add/delete/modify phone card
❌
❌
✅
❌
Add/delete gateway
❌
✅
❌
✅
Modify gateway information
❌
✅
❌
✅
Modify gateway capacity
❌
✅
❌
✅
Payment for this account
✅
❌
✅
✅
Payment for sub accounts
✅
✅
✅
✅
📵 Number Section Limitation for Agent Accounts
The Number Section Limitation feature (VOS3000 Manual, Section 2.4.6, Page 26) allows administrators to restrict the phone number prefixes that a VOS3000 agent account (and its sub-accounts) can use. This is a powerful tool for controlling call routing and preventing unauthorized destination access.
🔧 How Number Section Limitation Works
Number Section Limitation works by defining allowed or blocked phone number prefixes for specific accounts:
📱 Prefix-based filtering: Controls which number prefixes (e.g., country codes, area codes) the account can dial
🔄 Inherited by sub-accounts: Sub-accounts inherit the limitations of their parent agent account
🛡️ Security layer: Prevents agents from routing calls to unauthorized or expensive destinations
📊 Business control: Allows platform operators to segment destination access by agent tier
The VOS3000 agent account system supports two CTD (Call Type Definition) billing models, as documented in the VOS3000 manual (Section 2.4.2, Page 16):
📊 Standard CTD Billing Model
The Standard billing model is the default and most commonly used model in VOS3000:
📞 Per-minute billing: Calls are billed based on duration
🔄 Rating by destination: Different rates apply to different destinations
💰 Prepaid/Postpaid: Supports both payment models
📋 CDR-based: All billing is calculated from Call Detail Records
🔄 Flow CTD Billing Model
The Flow billing model is specifically designed for callback business operations (VOS3000 Manual, Section 2.4.2, Page 16):
📲 Callback-oriented: Designed for callback service providers
🔗 Two-leg billing: Handles the unique billing requirements of callback calls
🌐 DID integration: Works with DID-based callback triggers
📊 Specialized CDR processing: Different CDR handling for callback scenarios
📋 Feature
📊 Standard Model
🔄 Flow Model
Primary Use Case
Standard VoIP calling
Callback business
Billing Method
Per-minute by destination
Two-leg callback billing
CDR Processing
Single CDR per call
Separate CDRs for each leg
Complexity
Simple
Moderate
Recommendation
Default choice for most deployments
Only for callback operations
When configuring a VOS3000 agent account, choose the Standard model unless you specifically operate a callback business. The Flow model introduces additional complexity that is unnecessary for standard wholesale or retail VoIP operations.
🏗️ Multi-Level Reseller Hierarchy
One of the most powerful aspects of the VOS3000 agent account system is the ability to create multi-level reseller hierarchies. The VOS3000 manual (Section 2.4.5, Page 25) confirms that “Agent can create sub-accounts for sub-agents”, enabling a tree-like organizational structure.
🌳 Understanding the Hierarchy Structure
In a VOS3000 deployment, the account hierarchy typically looks like this:
🏢 System Administrator (Admin)
├── 🏭 Master Agent (VOS3000 Agent Account - Level 1)
│ ├── 🛒 Sub-Agent A (VOS3000 Agent Account - Level 2)
│ │ ├── 👤 End Customer 1
│ │ ├── 👤 End Customer 2
│ │ └── 👤 End Customer 3
│ ├── 🛒 Sub-Agent B (VOS3000 Agent Account - Level 2)
│ │ ├── 👤 End Customer 4
│ │ └── 🛒 Sub-Sub-Agent (Level 3)
│ │ ├── 👤 End Customer 5
│ │ └── 👤 End Customer 6
│ └── 👤 Direct Customer 1
├── 🏭 Master Agent 2 (VOS3000 Agent Account - Level 1)
│ ├── 👤 Direct Customer 7
│ └── 👤 Direct Customer 8
└── 👤 Standalone Customer (No agent hierarchy)
📏 Key Hierarchy Rules
The VOS3000 agent account hierarchy follows strict rules that maintain order and security:
🔗 Agent ID Chain: Every account (except top-level) must have an Agent ID pointing to its parent
🔒 Scope Limitation: An agent can only manipulate accounts within its own hierarchy
📋 Authorization Inheritance: Sub-agents can only have authorizations that are a subset of their parent’s authorizations
📐 Mandatory Designation: Accounts created by agents must be designated to an agent account
🌲 Navigation Tree: Each agent account appears in the navigation tree with its sub-accounts organized beneath it
🌍 Real-World Hierarchy Example
Consider a VoIP operator based in Bangladesh who serves the South Asian market. Their VOS3000 agent account hierarchy might look like this:
🏢 Level
📋 Account Name
🔗 Agent ID
📋 Category
🔐 Key Authorizations
Admin
System Admin
N/A
Admin
All authorizations
Level 1
BD-Wholesale-Agent
Admin
Agent
All except gateway management
Level 2
Dhaka-Retail-Sub
BD-Wholesale-Agent
Agent
Account, Phone, Payment (sub)
Level 3
Customer-001
Dhaka-Retail-Sub
Account
N/A (end user)
This hierarchical structure enables each level to operate independently within their authorized scope while maintaining overall system integrity.
🌲 Agent Account Navigation Tree
A key visual indicator of a VOS3000 agent account is its appearance in the navigation tree. The VOS3000 manual (Section 2.4.3, Page 22) explicitly states that once an account becomes an agent, “it will appear in the navigation tree.”
🖥️ Navigation Tree Features
The navigation tree provides several important capabilities:
📂 Hierarchical View: Visual representation of the agent-sub-account relationship
🖱️ Quick Access: Double-click an agent account to open Sub-Account Management
🔍 Filter Options: Toggle between “Direct” and “All” views for sub-account display
📊 Real-time Updates: The tree updates dynamically as sub-accounts are added or removed
💡 Using the Navigation Tree Effectively
For administrators managing large numbers of VOS3000 agent accounts, the navigation tree is an essential tool. Here are some tips:
🏷️ Use descriptive account names: Name agent accounts clearly to identify them in the tree (e.g., “Agent-BD-Wholesale” instead of “A001”)
🔍 Use the “Direct” filter for quick access: When you only need to work with immediate sub-accounts, the “Direct” filter reduces visual clutter
🌐 Use “All” for audit purposes: When auditing an agent’s entire hierarchy, switch to “All” to see the complete sub-account tree
📐 Keep hierarchy depth reasonable: While VOS3000 supports multi-level hierarchies, keeping it to 2-3 levels makes the navigation tree more manageable
✅ Best Practices for VOS3000 Agent Account Management
Based on extensive experience with VOS3000 deployments, here are the best practices for managing VOS3000 agent accounts effectively:
🛡️ Security Best Practices
🔐 Principle of Least Privilege: Only grant the minimum authorizations an agent needs to perform their business functions. Don’t give gateway management access to retail resellers.
🔒 Regular Authorization Audits: Periodically review agent authorizations to ensure they still align with business needs. Remove any authorizations that are no longer required.
📱 Apply Number Section Limitations: Always configure prefix restrictions for agents to prevent unauthorized destination routing.
📊 Monitor Payment Activities: Keep a close eye on payment authorizations, especially for high-volume agents. Consider disabling “Payment for this account” for agents who should only process sub-account payments.
🔄 Use Strong Passwords: Ensure all agent accounts use strong, unique passwords and change them regularly.
⚙️ Operational Best Practices
📋 Document Your Hierarchy: Maintain a clear diagram of your agent hierarchy. This helps with troubleshooting and onboarding new team members.
🏷️ Naming Conventions: Use consistent naming conventions for agent accounts. For example: “[Region]-[Type]-[Name]” like “BD-Wholesale-AcmeTel”.
📊 Regular Balance Reviews: Monitor agent account balances to ensure they have sufficient credit for their operations. Set up alerts for low-balance situations.
🔄 Test Before Deployment: Always test new agent configurations in a non-production environment before deploying to your live system.
📋 Backup Configurations: Regularly backup your VOS3000 configuration, including agent account settings and authorizations.
💰 Business Best Practices
📈 Tier-Based Authorization: Create different authorization profiles for different agent tiers (e.g., Silver, Gold, Platinum) with progressively more capabilities.
🔄 Sub-Agent Approval Process: Implement an approval process before allowing agents to create sub-agents, preventing uncontrolled hierarchy growth.
🛡️ Prepaid Vendor Routing: Configure call routing to only pass calls to vendors with positive balance. Learn more in our article on prepaid vendor call routing in VOS3000.
⚠️ Common Mistakes and How to Avoid Them
When working with VOS3000 agent accounts, administrators often make these common mistakes:
❌ Mistake 1: Granting All Authorizations by Default
One of the most dangerous mistakes is giving every agent all available authorizations. This creates unnecessary security risks and can lead to accidental misconfigurations.
Solution: Follow the principle of least privilege. Start with minimal authorizations and add more only when there’s a documented business need.
❌ Mistake 2: Not Using Number Section Limitations
Without Number Section Limitations, agents can route calls to any destination, potentially resulting in unexpected costs or fraud.
Solution: Always configure Number Section Limitations for every VOS3000 agent account. Review and update them regularly. For fraud prevention, also consider the VOS3000 extended firewall configuration.
❌ Mistake 3: Creating Overly Deep Hierarchies
While VOS3000 supports multi-level agent hierarchies, creating too many levels makes management complex and can impact system performance.
Solution: Limit your hierarchy to 2-3 levels. If you need more levels, consider flattening the structure by creating separate top-level agents instead.
❌ Mistake 4: Ignoring the “Direct” vs. “All” Filter
Many administrators don’t realize the importance of the “Direct” and “All” filter in Sub-Account Management. Using the wrong filter can lead to confusion about the scope of an agent’s hierarchy.
Solution: Use “Direct” for day-to-day management and “All” for auditing and comprehensive reviews.
❌ Mistake 5: Not Setting Agent ID Correctly
Setting the wrong Agent ID can break the hierarchy chain and lead to accounts being managed by the wrong agent.
Solution: Always double-check the Agent ID field when creating sub-accounts. The parent account must exist before you can reference it as an Agent ID. Remember: “The Account id of its parent account. Parent account must exist” (VOS3000 Manual, Section 2.4.2, Page 16).
❌ Mistake 6: Choosing the Wrong CTD Billing Model
Selecting the Flow billing model when you’re not running a callback business introduces unnecessary complexity.
Solution: Use the Standard CTD billing model unless you specifically operate callback services.
🔧 Troubleshooting Agent Account Issues
When issues arise with your VOS3000 agent account setup, here are the most common problems and their solutions:
⚠️ Problem
🔍 Likely Cause
✅ Solution
Account doesn’t appear in navigation tree
Account has no sub-accounts assigned
Create at least one sub-account with this account as Agent ID
Agent cannot add sub-accounts
“Add/delete/modify account” authorization not granted
Enable the account management authorization in Authorization Management
Agent cannot process payments
Payment authorization not enabled
Enable “Payment for sub accounts” and/or “Payment for this account”
Sub-account shows wrong agent
Agent ID was set incorrectly during creation
Modify the sub-account and correct the Agent ID field
Agent can see other agents’ sub-accounts
System configuration issue
Verify account scope settings; agent should only manipulate its own sub-accounts
Account category won’t change to “Agent”
No sub-accounts assigned yet
Account category is auto-determined; assign sub-accounts to promote to Agent
Q1: How do I convert an ordinary account to a VOS3000 agent account?
A: You don’t need to manually convert an account. In VOS3000, agent status is automatically assigned when an account has sub-accounts. Simply create a sub-account and set its Agent ID to the ordinary account’s ID. The ordinary account will automatically become a VOS3000 agent account and appear in the navigation tree. As the manual states (Section 2.4.2, Page 16): “When an account has sub accounts, it automatically becomes an agent.”
Q2: Can a VOS3000 agent account create sub-agents (agents under agents)?
A: Yes! The VOS3000 manual (Section 2.4.5, Page 25) explicitly states that “Agent can create sub-accounts for sub-agents.” This means an agent can create sub-accounts that are themselves agents, building a multi-level reseller hierarchy. Each sub-agent can then manage their own set of sub-accounts, enabling complex business structures.
Q3: What happens if I delete a VOS3000 agent account that has sub-accounts?
A: Deleting a VOS3000 agent account that has active sub-accounts requires careful handling. You should first reassign or delete all sub-accounts before removing the parent agent account. Always check the “All” filter in Sub-Account Management to see the complete hierarchy before proceeding with deletion. It’s recommended to back up your configuration before making such changes.
Q4: Can I restrict an agent to only certain call destinations?
A: Absolutely. Use the Number Section Limitation feature (VOS3000 Manual, Section 2.4.6, Page 26) to restrict the phone prefixes that an agent’s sub-accounts can dial. This is essential for preventing agents from routing calls to expensive or unauthorized destinations. Each agent can have different prefix restrictions based on their business agreement.
Q5: What is the difference between “Direct” and “All” sub-account filters?
A: The “Direct” filter shows only the immediate (first-level) sub-accounts directly under the VOS3000 agent account. The “All” filter shows the entire hierarchy, including sub-sub-accounts and sub-agents’ sub-accounts. Use “Direct” for day-to-day management and “All” for comprehensive auditing. This feature is documented in Section 2.4.3, Page 22 of the VOS3000 manual.
Q6: Should I use the Standard or Flow CTD billing model for my agent account?
A: Use the Standard CTD billing model for regular VoIP calling (wholesale or retail). Use the Flow model only if you specifically operate a callback business. The Flow model is designed for two-leg callback billing scenarios and introduces unnecessary complexity for standard operations. The VOS3000 manual (Section 2.4.2, Page 16) confirms that the Flow model is specifically “for callback business.”
Q7: Can an agent account modify another agent’s sub-accounts?
A: No. A fundamental security principle of the VOS3000 agent account system is that “Agent account can only manipulate its sub accounts” (VOS3000 Manual, Section 2.4.5, Page 25). Agent A cannot see, modify, or interact with Agent B’s sub-accounts. This isolation ensures that different resellers on the same platform operate independently and securely.
Q8: How do I configure gateway access for a VOS3000 agent account?
A: Gateway access requires three authorizations to be enabled: “Add/delete gateway,” “Modify gateway information,” and “Modify gateway capacity.” Enable these authorizations only for agents who need to manage their own SIP infrastructure. For most retail resellers, gateway management should remain with the system administrator. Only grant gateway authorizations to trusted wholesale or SIP trunk provider agents.
📚 Related Resources
Expand your VOS3000 knowledge with these related guides from our blog:
Need help setting up your VOS3000 agent account system or configuring reseller authorization management? Our team of VOS3000 experts is ready to assist you with:
🔧 Agent Account Setup: Complete configuration of your agent hierarchy and authorization structure
🔐 Security Hardening: Implement best-practice authorization controls and number section limitations
📊 Billing Configuration: Set up CTD billing models and rate cards for your agent network
🛡️ Fraud Prevention: Configure firewall rules and monitoring to protect your platform
🔄 Migration Support: Migrate existing accounts to a proper agent hierarchy
Whether you’re setting up your first VOS3000 agent account or managing a complex multi-level reseller network, we’re here to help. Don’t let configuration challenges slow down your business — reach out today!
📖 This guide is based on the VOS3000 User Manual V2.1.9.07. All page references and feature descriptions are sourced from the official documentation. For the latest software updates, visit vos3000.com/downloads.php.
Published on multahost.com/blog — Your trusted source for VOS3000 tutorials, configuration guides, and VoIP business insights. Need expert help? Contact us on WhatsApp at +8801911119966.
📞 Need Professional VOS3000 Setup Support?
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
VOS3000 Time-Based Routing: Work Calendar and Period Rate Setup
Implementing VOS3000 time-based routing is one of the most powerful strategies for maximizing profit in a wholesale VoIP operation. While standard LCR routing selects gateways based on static cost priorities, this time-based approach adds a critical dimension: the ability to automatically shift traffic between vendors and rate tables based on the time of day, day of the week, and whether the day is a working day or a holiday. This means you can route calls through the cheapest available vendor during off-peak hours, switch to higher-quality providers during peak business hours, and apply entirely different rate structures on weekends and holidays — all without any manual intervention.
Many VOS3000 operators leave significant money on the table because they rely solely on static LCR routing and never configure time-based routing. Vendors frequently offer different rates for peak and off-peak hours, and failing to take advantage of these rate differences means you are overpaying for termination during low-cost periods. This guide walks you through the complete VOS3000 time-based routing configuration process, covering Work Calendar setup (VOS3000 Manual Section 2.12.4), Package Period Rate Management (VOS3000 Manual Section 2.3.2), and the practical integration of both features to create a dynamic routing strategy that adapts to time-based cost fluctuations. For professional assistance with your routing setup, contact us on WhatsApp at +8801911119966.
Table of Contents
Why VOS3000 Time-Based Routing Matters for VoIP Profitability
Understanding why VOS3000 time-based routing is essential requires looking at how VoIP termination costs actually work in the real world. Most carriers and termination providers offer different rates depending on the time of day. Peak hours typically have higher termination costs because network congestion is greater and demand is higher. Off-peak hours, usually nighttime and weekends, have significantly lower rates because network capacity is underutilized. A wholesale VoIP operator who routes all traffic through the same gateway with the same rate table regardless of time is effectively paying peak rates 24 hours a day.
The financial impact of this oversight can be enormous. Consider a VoIP operation handling 500,000 minutes per day. If the difference between peak and off-peak rates is just $0.002 per minute, and 40% of your traffic falls in off-peak hours, you are losing $400 per day or $12,000 per month by not implementing time-based routing. Over a year, that amounts to $146,000 in lost profit — all because you did not configure time-based routing properly.
📊 Scenario
💰 Daily Savings
💰 Monthly Savings
💰 Annual Savings
100K min/day, $0.002 diff
$80
$2,400
$29,200
500K min/day, $0.002 diff
$400
$12,000
$146,000
1M min/day, $0.002 diff
$800
$24,000
$292,000
1M min/day, $0.005 diff
$2,000
$60,000
$730,000
How VOS3000 Time-Based Routing Differs from Simple LCR
It is important to understand the distinction between standard LCR routing and VOS3000 time-based routing. Our VOS3000 LCR routing guide covers the fundamentals of least cost routing, which selects gateways based on static priorities and prefix matching. LCR routing always routes the same way regardless of when the call arrives. VOS3000 time-based routing adds a time dimension to this decision process, allowing different routing and billing rules to apply during different time periods.
Think of it this way: LCR routing answers the question “Which gateway is cheapest for this destination?” while VOS3000 time-based routing answers the question “Which gateway is cheapest for this destination at this specific time?” The combination of LCR and time-based routing gives you the most sophisticated routing strategy possible in VOS3000.
⚙️ Feature
📋 LCR Routing Only
🕐 VOS3000 Time-Based Routing
Gateway selection
Static priority-based
Dynamic, time-dependent
Rate table applied
Single rate table always
Different rate tables by time
Weekend handling
Same as weekday
Different routing and rates
Holiday handling
Same as any day
Custom holiday rates
Cost optimization
Lowest static cost
Lowest cost per time period
Manual intervention
Required for rate changes
Fully automatic switching
Profit potential
Good
Maximum
Understanding the VOS3000 Work Calendar System
The Work Calendar is the foundation of VOS3000 time-based routing. It defines what constitutes a working day, a non-working day, working hours, and non-working hours. These definitions are then used by the Package Period Rate system to determine which rate table and routing rules apply at any given moment. The Work Calendar is configured in the VOS3000 web interface under Navigation > System management > Work calendar (VOS3000 Manual Section 2.12.4, Page 174).
The Work Calendar system in VOS3000 is surprisingly powerful. It does not simply distinguish between “day” and “night” — it allows you to define complex schedules that account for different working hours on different days of the week, designated holidays, and special non-working days. This granularity is what makes time-based routing so effective for wholesale VoIP operations that need to adapt to carrier rate schedules.
Work Calendar Configuration Fields
When you create a new Work Calendar entry, you need to understand each configuration field and how it affects your routing. Here is a detailed breakdown of the Work Calendar settings as documented in VOS3000 Manual Section 2.12.4 (Page 174-176):
Calendar Name: A descriptive name for the calendar. Choose a name that clearly indicates its purpose, such as “BD_Wholesale_Schedule” for a Bangladesh wholesale operation or “UK_Business_Hours” for UK-oriented traffic. The calendar name is referenced by other VOS3000 modules including Package Period Rate and account settings.
Working Day: Specify which days of the week are considered working days. Typically Monday through Friday are working days, while Saturday and Sunday are non-working days. However, in some regions, the work week differs, and VOS3000 allows you to configure any combination of days as working or non-working.
Working Hours: Define the start and end times for working hours on working days. For example, 08:00 to 18:00 means that calls between 8 AM and 6 PM on working days use the working-hour rate table and routing rules. The time format is 24-hour (HH:MM).
Non-Working Hours: The period outside the defined working hours on working days, plus all hours on non-working days. Non-working hours automatically use different rate tables and potentially different gateway priorities.
Holiday Settings: Designate specific dates as holidays, which are treated as non-working days regardless of which day of the week they fall on. This is essential for applying special holiday rates.
⚙️ Field
📝 Description
💡 Example Value
🎯 Routing Impact
Calendar Name
Identifier for the calendar
BD_Wholesale_Schedule
Referenced by period rates and accounts
Working Days
Days classified as working
Mon-Fri
Applies working hour rates
Working Hours Start
Beginning of working period
08:00
Switches to daytime rate table
Working Hours End
End of working period
18:00
Switches to nighttime rate table
Holidays
Designated non-working dates
2026-01-01, 2026-03-26
Applies non-working day rates
Step-by-Step Work Calendar Configuration for VOS3000 Time-Based Routing
Now let us walk through the actual process of creating and configuring a Work Calendar for VOS3000 time-based routing. This step-by-step guide follows the interface described in VOS3000 Manual Section 2.12.4 (Page 174-176).
Step 1: Access the Work Calendar Interface
Log in to the VOS3000 web management interface with an administrator account. Navigate to Navigation > System management > Work calendar. The Work Calendar list page displays all existing calendars. From here, you can add, modify, or delete calendar entries.
To create a new calendar, click the Add button. A new calendar configuration form will appear with the fields described above.
Step 2: Define Calendar Name and Working Days
Enter a descriptive Calendar Name that reflects the purpose of this calendar. For time-based routing purposes, use names that clearly indicate the schedule type and target market. Examples include:
BD_PeakOffPeak: For Bangladesh traffic with peak/off-peak rate switching
UK_BusinessHours: For UK-destined traffic following UK business hours
Global_247_Weekend: For a global operation that only differentiates weekday vs. weekend
Holiday_Special_2026: For a calendar specifically designed for holiday rate management
Select the Working Days checkboxes to indicate which days of the week are working days. In most wholesale VoIP scenarios, Monday through Friday are working days because carrier rate structures typically differentiate between weekday and weekend rates.
Step 3: Set Working and Non-Working Hours
Define the Working Hours start and end times. The most common configuration for time-based routing is 08:00 to 18:00, which aligns with typical carrier peak-hour billing periods. However, you should check your vendor rate agreements to determine their exact peak and off-peak definitions.
Some important considerations when setting working hours:
Match vendor definitions: Your working hours must align with when your vendors charge peak rates. If a vendor defines peak hours as 09:00-21:00, set your working hours accordingly to avoid paying peak rates while applying off-peak rates to your customers.
Time zone awareness: Working hours should correspond to the time zone of your vendor or destination, not necessarily your local time zone. If you route traffic to the US but operate from Asia, your working hours should reflect US business hours.
Multiple calendars: Create separate calendars for different destination regions if they have different peak-hour definitions. You can then assign the appropriate calendar to each account or rate configuration.
Step 4: Configure Holiday Dates
Add specific dates as holidays in the Work Calendar. Holidays are treated as non-working days regardless of the day of the week. For time-based routing, holidays are important because many carriers offer special low rates on public holidays, similar to weekend rates.
To add a holiday, specify the date in the holiday list within the calendar configuration. You can add as many holidays as needed. Common holidays to include for Bangladesh-destined traffic include:
March 26 — Independence Day
December 16 — Victory Day
Eid ul-Fitr and Eid ul-Adha (variable dates)
January 1 — New Year’s Day
For international operations, include the public holidays of your primary destination countries. Remember to update holiday dates annually as some holidays change each year.
Step 5: Save and Verify the Calendar
After configuring all fields, click Save to create the calendar. Verify the calendar appears in the Work Calendar list with the correct configuration. The calendar is now ready to be referenced by Package Period Rate configurations and account settings.
Configuring Package Period Rate Management for VOS3000 Time-Based Routing
The Work Calendar defines when different time periods occur, but it is the Package Period Rate Management that determines what actually happens during those periods. This is where you bind specific rate tables to working hours and non-working hours, creating the actual time-dependent billing and routing behavior. Navigate to Rate Management > Package Period Rate Management (VOS3000 Manual Section 2.3.2, Page 10-12).
Package Period Rate Management is the engine that drives time-based routing in VOS3000. Without it, the Work Calendar simply categorizes time periods but does not change any routing or billing behavior. The Package Period Rate configuration links a calendar to specific rate tables, ensuring that the correct rates are applied at the correct times automatically.
Package Period Rate Configuration Fields
When you create a Package Period Rate entry, you need to configure the following fields as described in VOS3000 Manual Section 2.3.2 (Page 10-12):
Period Rate Name: A descriptive name for this period rate configuration. Use names that clearly describe the rate switching behavior, such as “BD_DayNight_Switch” or “UK_PeakOffPeak_Rate”.
Work Calendar: Select the Work Calendar that defines the time periods for this configuration. The calendar determines which hours are working hours and which are non-working hours.
Working Hours Rate Table: Select the rate table that applies during working hours as defined by the selected calendar. This is typically your peak-hour rate table with higher rates.
Non-Working Hours Rate Table: Select the rate table that applies during non-working hours. This is typically your off-peak rate table with lower rates.
⚙️ Field
📝 Description
🎯 Purpose in Time-Based Routing
Period Rate Name
Identifier for the configuration
Links to account and rate group settings
Work Calendar
Reference to calendar definition
Determines when each period starts/ends
Working Hours Rate Table
Rate table for peak hours
Higher sell rates during business hours
Non-Working Hours Rate Table
Rate table for off-peak hours
Lower sell rates during nights/weekends
Step-by-Step Package Period Rate Configuration
Follow these steps to configure Package Period Rate Management for VOS3000 time-based routing:
Step 1: Navigate to Rate Management > Package Period Rate Management in the VOS3000 web interface.
Step 2: Click Add to create a new Package Period Rate entry.
Step 3: Enter the Period Rate Name. Use a descriptive name that indicates the routing purpose, such as “BD_Wholesale_DayNight”.
Step 4: Select the Work Calendar from the dropdown list. This should be the calendar you created earlier that defines the working and non-working hours for your target market.
Step 5: Select the Working Hours Rate Table from the dropdown. This rate table should contain your peak-hour selling rates. These rates are typically higher because vendor costs are higher during peak hours, and you need to maintain your margin.
Step 6: Select the Non-Working Hours Rate Table from the dropdown. This rate table should contain your off-peak selling rates. These can be lower while still maintaining profit margins because vendor costs are lower during off-peak hours.
Step 7: Click Save to create the Package Period Rate configuration.
After saving, the period rate configuration will automatically switch between the two rate tables based on the Work Calendar schedule. No manual intervention is required — the system handles the switching seamlessly.
Binding Rate Tables for Daytime vs. Nighttime in VOS3000 Time-Based Routing
Creating effective rate table bindings is where time-based routing translates from configuration into actual financial results. The rate tables you bind to working and non-working hours determine exactly how much you charge customers during each period, directly affecting your profit margins.
Before configuring Package Period Rate bindings, you need to have both rate tables already created in Rate Management > Rate Table Management (VOS3000 Manual Section 2.2.2). Each rate table must contain rate entries for all the prefixes you plan to bill. For a comprehensive understanding of rate table setup, refer to our VOS3000 billing system guide.
Designing Daytime and Nighttime Rate Tables
The key principle for designing rate tables for this routing method is that each rate table must cover the same set of prefixes but with different rate values. The daytime rate table has higher rates that account for peak vendor costs plus your desired margin. The nighttime rate table has lower rates that reflect reduced vendor costs while still maintaining acceptable margins.
🔢 Prefix
📋 Destination
☀️ Day Rate (08:00-18:00)
🌙 Night Rate (18:00-08:00)
💰 Rate Difference
88017
BD Grameenphone
$0.012/min
$0.008/min
33% lower
88018
BD Robi Mobile
$0.012/min
$0.008/min
33% lower
88019
BD Banglalink
$0.013/min
$0.009/min
31% lower
8802
BD Landline
$0.010/min
$0.005/min
50% lower
44
UK Landline
$0.008/min
$0.004/min
50% lower
1
USA/Canada
$0.005/min
$0.003/min
40% lower
Vendor Rate Table Considerations
While most operators focus on customer-facing sell rates when setting up time-based routing, you should also configure rate switching on the vendor (buy) side if your vendors offer different rates for peak and off-peak periods. This ensures that VOS3000 accurately calculates your margins in real time and can make better routing decisions.
To configure vendor-side period rates, create separate buy rate tables for peak and off-peak hours, then create a Package Period Rate configuration that binds these rate tables to the same Work Calendar. Assign this period rate configuration to your vendor accounts. When VOS3000 time-based routing switches the buy rate table at 18:00, the system immediately starts using the lower off-peak rates for cost calculations.
Practical Use Cases for VOS3000 Time-Based Routing
Understanding the configuration steps is important, but seeing how time-based routing applies to real-world scenarios helps you design the most effective routing strategy for your specific business. Here are three practical use cases that demonstrate the power and flexibility of time-based routing.
Use Case 1: Wholesale Traffic Day/Night Shifting
A wholesale VoIP operator routes traffic to Bangladesh, India, and the UK. Their vendors offer significantly different rates for peak and off-peak hours. During peak hours (08:00-18:00), VendorA offers the best rates for Bangladesh at $0.008/min, while VendorB is cheaper for UK traffic at $0.006/min. During off-peak hours, VendorC offers much lower rates across all destinations — $0.004/min for Bangladesh and $0.003/min for the UK. However, VendorC has limited capacity and lower ASR during peak hours.
Without time-based routing, the operator would need to manually switch gateway priorities twice a day, which is error-prone and impractical. With time-based routing configured, the system automatically routes through VendorA and VendorB during peak hours and switches to VendorC during off-peak hours. This can save the operator thousands of dollars per month while maintaining optimal call quality during peak hours.
🕐 Time Period
🏢 BD Gateway
🏢 UK Gateway
💰 BD Rate
💰 UK Rate
08:00-18:00 (Peak)
VendorA (Priority 1)
VendorB (Priority 1)
$0.008/min
$0.006/min
18:00-22:00 (Shoulder)
VendorC (Priority 1)
VendorC (Priority 1)
$0.005/min
$0.004/min
22:00-08:00 (Off-Peak)
VendorC (Priority 1)
VendorC (Priority 1)
$0.004/min
$0.003/min
Use Case 2: Weekend and Holiday Routing
Many carriers treat weekends and public holidays as extended off-peak periods, offering the same low rates as overnight hours. A VoIP operator who does not implement VOS3000 time-based routing for weekends is paying peak rates on Saturday and Sunday even though vendors charge off-peak rates. With the Work Calendar correctly defining Saturday and Sunday as non-working days, and holidays configured in the holiday list, VOS3000 automatically applies the non-working hours rate table for the entire weekend and on designated holidays.
This is especially valuable for operators handling call center traffic, which often has reduced or zero volume on weekends. By applying lower sell rates on weekends (matching the lower vendor costs), you can attract more weekend traffic from price-sensitive customers while still maintaining healthy margins.
Use Case 3: Multi-Timezone Routing
For operators routing traffic to multiple countries across different time zones, VOS3000 time-based routing becomes even more critical. When it is peak hours in Bangladesh (GMT+6), it might be off-peak in the UK (GMT+0) and late night in the US (GMT-5). A single Work Calendar cannot accurately represent peak hours for all destinations simultaneously.
The solution is to create multiple Work Calendars, each aligned to a specific destination’s time zone. Then create separate Package Period Rate configurations for each destination group. Assign the appropriate period rate to each customer account or rate group based on the destinations they call most frequently. While this requires more initial setup, the resulting routing precision can significantly increase profitability for multi-region operations.
Integrating Work Calendar with Account Settings in VOS3000 Time-Based Routing
The Work Calendar does not operate in isolation — it integrates with several other VOS3000 modules to deliver complete VOS3000 time-based routing functionality. One of the most important integrations is with the account settings, where you can bind a Work Calendar to individual accounts for customized time-based behavior.
Account-Level Calendar Binding
In the account configuration (Operation Management > Account Operation), each account can be associated with a specific Work Calendar. This association affects how time-based routing behaves for that particular account. When an account has a Work Calendar assigned, the system uses that calendar’s definitions to determine whether the current time falls in working or non-working hours for rate and routing decisions specific to that account.
This is particularly useful when you have customers in different time zones. A customer based in the UK should have their account bound to a UK Work Calendar, while a customer in Bangladesh should use a BD Work Calendar. This ensures that each customer’s rates and routing are aligned with their local business hours, not yours.
Suppressing All Duration Too Long Alarm
An often-overlooked feature that integrates with the Work Calendar is the account setting “Suppressing all duration too long alarm” (VOS3000 Manual Section 2.5.2.3). This setting, when enabled for an account, suppresses alarm notifications for calls that exceed the configured maximum duration threshold. The relevance to VOS3000 time-based routing is that during non-working hours, long-duration calls are more common (especially for international traffic where people have extended conversations during off-peak rate periods).
Without this suppression, your alarm system would generate excessive notifications during nighttime and weekend hours, flooding your monitoring system with false alerts. By binding the Work Calendar to the account and enabling duration alarm suppression, VOS3000 can intelligently manage alarms based on time periods, reducing noise during expected long-call periods while maintaining alert sensitivity during working hours when unexpectedly long calls may indicate fraud or technical issues.
🔧 Feature
📝 Description
🎯 VOS3000 Time-Based Routing Impact
Account Calendar Binding
Links account to a Work Calendar
Per-account time-based rate switching
Duration Alarm Suppression
Suppresses long-call alarms
Reduces false alerts during off-peak
Period Rate Assignment
Binds period rate to account
Automatic rate table switching per account
Rate Group Authorization
Controls which rates accounts can use
Limits time-based rates to authorized accounts
VOS3000 Time-Based Routing and Gateway Priority Integration
While the Package Period Rate system handles rate table switching, the actual call routing (which gateway the call is sent through) is controlled by gateway priorities in the routing gateway configuration. For a complete time-based routing setup, you need to understand how rate switching interacts with gateway priority settings.
There are two primary approaches to implementing time-based gateway switching in VOS3000:
Approach 1: Period Rate with Fixed Gateway Priorities
In this approach, gateway priorities remain static, but the rate table changes based on time. This means that the same gateway is always used for a given prefix regardless of time, but the billing rate applied to the call changes. This is the simpler approach and works well when your vendor offers different rates for peak and off-peak but routes through the same gateway.
The advantage of this approach is simplicity — you only need to configure the Package Period Rate, and the gateway configuration remains unchanged. The disadvantage is that you cannot route calls through different gateways based on time; you can only change the billing rates.
Approach 2: Period Rate with Dynamic Gateway Priorities
For more advanced VOS3000 time-based routing, you can combine period rates with different gateway priority configurations. This approach involves creating separate routing gateway entries with different priorities for working and non-working hours. While VOS3000 does not natively switch gateway priorities based on the Work Calendar directly, you can achieve similar results by:
Creating multiple rate groups — one for peak hours with the peak-hour vendor as the preferred gateway, and one for off-peak hours with the off-peak vendor as preferred
Using the Package Period Rate to switch between these rate groups based on the Work Calendar
Configuring account settings to use the appropriate rate group based on the period
This approach requires more configuration but provides the most flexible and profitable time-based routing setup. The key insight is that when the period rate switches the rate table, the rate table can be associated with different gateway priority configurations, effectively changing which gateway handles the call.
For help setting up this advanced configuration, contact our VOS3000 specialists on WhatsApp at +8801911119966.
🎯 Approach
⚙️ Configuration Complexity
✅ Advantages
⚠️ Limitations
Fixed Gateway + Period Rates
Low
Simple setup, reliable
Cannot switch gateways by time
Dynamic Gateway + Period Rates
Medium-High
Full time-based routing control
Requires more configuration effort
Common VOS3000 Time-Based Routing Configuration Mistakes
Even experienced VOS3000 operators make mistakes when configuring time-based routing. These errors can result in incorrect billing, lost revenue, or routing failures. Here are the most common pitfalls and how to avoid them.
Mistake 1: Mismatched Working Hours Between Calendar and Vendor Definitions
If your Work Calendar defines working hours as 08:00-18:00, but your vendor defines peak hours as 09:00-21:00, you will be applying off-peak sell rates during the vendor’s peak period from 18:00-21:00. This means you are selling at off-peak rates but paying peak vendor costs, which erodes your margin or even causes losses. Always verify that your Work Calendar working hours match your vendor’s peak-hour definitions exactly.
Mistake 2: Incomplete Rate Tables
Both the working hours and non-working hours rate tables must contain rate entries for all prefixes that your customers might dial. If the daytime rate table has an entry for prefix 88017 but the nighttime rate table does not, calls to 88017 during nighttime hours will either fail to bill correctly or use a default rate that may be incorrect. Always ensure both rate tables have complete and matching prefix coverage.
Mistake 3: Forgetting to Update Holiday Dates
Holiday dates change every year, and some holidays (like Eid) move based on the lunar calendar. If you configure holidays in your Work Calendar but never update them, your time-based routing will treat old holidays as non-working days while actual holidays pass unrecognized. Set a recurring reminder to update holiday dates at the beginning of each year.
Mistake 4: Not Testing Time-Based Rate Switching
After configuring VOS3000 time-based routing, many operators fail to verify that the rate switching actually works. The result can be that rates never switch, or they switch at the wrong times. Always test by making test calls just before and after the working hours boundary and verifying in the CDR that the correct rate table was applied.
After configuring your Work Calendar and Package Period Rate, you must verify that VOS3000 time-based routing is working correctly. Verification involves both immediate testing and ongoing monitoring.
Immediate Verification Steps
Step 1: Check Calendar Status. Navigate to System Management > Work Calendar and verify your calendar appears in the list with the correct working days and hours. Click on the calendar to review all settings including holiday dates.
Step 2: Verify Period Rate Configuration. Navigate to Rate Management > Package Period Rate Management and confirm that your period rate entry shows the correct Work Calendar, working hours rate table, and non-working hours rate table.
Step 3: Make Test Calls. Make test calls during both working and non-working hours. After each test call, check the CDR record to verify that the correct rate table was applied. The CDR should show the rate from the working hours table during the day and the rate from the non-working hours table at night.
Step 4: Test Boundary Conditions. Make test calls at the exact boundary between working and non-working hours (for example, at 17:59 and 18:01) to verify that the rate switch happens at the correct time. This is where timing errors are most likely to appear.
Ongoing Monitoring for VOS3000 Time-Based Routing
Regular monitoring ensures that your VOS3000 time-based routing continues to function correctly over time. Key monitoring activities include:
Weekly CDR review: Sample CDRs from both working and non-working hours to confirm rate tables are switching correctly
Margin analysis: Compare working hours margins against non-working hours margins to verify that your time-based pricing is generating the expected profitability improvement
Gateway utilization reports: Monitor whether traffic distribution between gateways changes between working and non-working hours as expected
Holiday verification: Before each holiday, verify that the date is correctly configured in the Work Calendar
Once you have the basic time-based routing configuration working, several advanced techniques can further optimize your routing strategy and increase profitability.
Multiple Period Rate Configurations
VOS3000 allows you to create multiple Package Period Rate configurations, each with a different Work Calendar and different rate table bindings. This is essential for operations that serve customers across multiple time zones or with different pricing agreements. For example, you might have one period rate configuration for retail customers (who get a small off-peak discount) and another for wholesale customers (who get a larger off-peak discount).
Each period rate configuration is assigned to specific accounts or rate groups, ensuring that the correct time-based billing behavior applies to each customer segment.
Combining Time-Based Routing with Prefix-Based Rate Optimization
The most powerful routing strategies combine VOS3000 time-based routing with prefix-based rate optimization. For detailed prefix configuration, see our VOS3000 prefix settings guide. By having different rate tables for different prefix groups AND different time periods, you create a multi-dimensional pricing matrix that maximizes margin across every combination of destination and time.
For example, you might have four rate tables for Bangladesh mobile traffic:
BD_Mobile_Peak_Workday: Highest rates for weekday peak hours
BD_Mobile_OffPeak_Workday: Medium rates for weekday off-peak hours
BD_Mobile_Peak_Weekend: Lower rates for weekend daytime
BD_Mobile_OffPeak_Weekend: Lowest rates for weekend nighttime
By combining multiple Work Calendars and Package Period Rate configurations, you can implement this level of granular pricing control within VOS3000.
Using VOS3000 System Parameters to Support Time-Based Routing
Several VOS3000 system parameters affect how time-based routing behaves. Understanding these parameters helps you fine-tune the routing behavior:
SERVER_WORK_CALENDAR_ENABLED: This system parameter must be enabled for Work Calendar functionality to work. If this parameter is disabled, all time-based routing features are inactive regardless of your calendar configuration.
SERVER_PERIOD_RATE_ENABLED: This parameter must be enabled for Package Period Rate functionality to work. Without it, rate tables will not switch based on time periods.
Check these parameters in System Management > System Parameter (VOS3000 Manual Section 4.3) to ensure they are set correctly. If time-based routing is not working after configuration, these system parameters are the first thing to check.
Use this checklist to ensure you have completed all necessary steps for a fully functional VOS3000 time-based routing setup. Follow each step in order and verify the result before proceeding to the next step.
Create Work Calendar — Define calendar name, working days, working hours, and holidays in System Management > Work Calendar
Create Daytime Rate Table — Build a complete rate table with peak-hour rates for all prefixes in Rate Management > Rate Table Management
Create Nighttime Rate Table — Build a matching rate table with off-peak rates for the same prefixes
Create Package Period Rate — Bind the calendar and both rate tables in Rate Management > Package Period Rate Management
Enable System Parameters — Verify SERVER_WORK_CALENDAR_ENABLED and SERVER_PERIOD_RATE_ENABLED are set to 1
Bind Calendar to Accounts — Assign the Work Calendar to customer and vendor accounts that should use time-based routing
Assign Period Rate to Rate Groups — Link the Package Period Rate to the appropriate rate groups
Test Rate Switching — Make test calls during working and non-working hours and verify CDR rates
Test Boundary Conditions — Verify rate switching happens at the exact configured time boundaries
Set Up Monitoring — Establish regular CDR review and margin analysis procedures
Document Configuration — Record all calendar and period rate settings for future reference
Schedule Annual Holiday Updates — Set reminders to update holiday dates each year
Frequently Asked Questions About VOS3000 Time-Based Routing
❓ What is VOS3000 time-based routing and how does it work?
VOS3000 time-based routing is a feature that automatically switches rate tables and routing behavior based on the time of day, day of the week, and calendar dates. It works through two integrated components: the Work Calendar (which defines working hours, non-working hours, and holidays) and the Package Period Rate (which binds different rate tables to each time period). When the current time falls within working hours as defined by the calendar, VOS3000 applies the working hours rate table. When it falls outside working hours, the non-working hours rate table is applied automatically.
❓ How is VOS3000 time-based routing different from standard LCR routing?
Standard LCR routing uses static gateway priorities and rate tables that do not change based on time. VOS3000 time-based routing adds a time dimension, allowing different rate tables and potentially different routing priorities during different time periods. With LCR alone, the cheapest gateway for a destination is always used. With time-based routing, a different gateway may be cheapest at different times of day, and VOS3000 automatically adapts. The combination of LCR and time-based routing provides the most profitable routing strategy possible.
❓ Can I use multiple Work Calendars for different time zones in VOS3000 time-based routing?
Yes. You can create multiple Work Calendars in VOS3000, each aligned to a different time zone’s peak and off-peak hours. Each calendar is then assigned to the appropriate accounts or rate groups based on the destinations they serve. This is the recommended approach for operators routing traffic to multiple countries across different time zones, as it ensures that rate switching happens at the correct local time for each destination.
❓ Do I need to manually switch rate tables when using VOS3000 time-based routing?
No. The entire purpose of VOS3000 time-based routing is to automate rate table switching. Once you configure the Work Calendar and Package Period Rate correctly, VOS3000 automatically switches between the working hours and non-working hours rate tables at the boundaries defined in the calendar. No manual intervention is required, which eliminates the risk of forgetting to switch rates and the operational overhead of manual changes.
❓ What happens if I do not bind a Work Calendar to an account?
If an account does not have a Work Calendar assigned, VOS3000 time-based routing will not apply to that account. The account will use its default rate table at all times, regardless of the time of day or day of the week. This means no rate switching occurs, and the account effectively operates with static LCR routing only. To enable time-based routing for an account, you must both create the Package Period Rate configuration and bind the appropriate calendar and period rate to the account.
❓ How do I verify that VOS3000 time-based routing is switching rates correctly?
The most reliable verification method is to make test calls during both working and non-working hours, then check the CDR records for each call. The CDR will show which rate was applied to the call. If the working hours rate was applied during the day and the non-working hours rate was applied at night, your configuration is working correctly. Also test at the exact boundary times (for example, at 17:59 and 18:01) to confirm the switch happens at the right moment.
❓ Can VOS3000 time-based routing handle different rates for weekends and holidays?
Yes. The Work Calendar distinguishes between working days and non-working days (which include weekends and designated holidays). Non-working days use the non-working hours rate table for the entire day, not just during nighttime. This means weekends and holidays automatically receive the lower off-peak rates all day long, which aligns with how most carriers price their services. You can add specific holiday dates to the calendar each year to ensure correct holiday rate application.
❓ What system parameters must be enabled for VOS3000 time-based routing to work?
Two system parameters must be enabled: SERVER_WORK_CALENDAR_ENABLED (must be set to 1) enables the Work Calendar feature, and SERVER_PERIOD_RATE_ENABLED (must be set to 1) enables the Package Period Rate switching feature. If either of these parameters is disabled, the corresponding time-based routing functionality will not work, regardless of your calendar and period rate configuration. Verify these parameters in System Management > System Parameter (VOS3000 Manual Section 4.3).
Configure VOS3000 Time-Based Routing with Expert Help
Setting up VOS3000 time-based routing correctly can transform your VoIP business from one that pays static peak rates around the clock to one that dynamically optimizes costs based on time. The financial impact of proper time-based routing configuration is significant — many operators report 15-30% reduction in termination costs after implementing day/night rate switching and weekend routing. However, the configuration requires careful attention to detail, from matching working hours to vendor definitions to ensuring complete prefix coverage in both rate tables.
Our VOS3000 specialists have helped operators worldwide implement and optimize time-based routing configurations. Whether you need help with initial Work Calendar setup, Package Period Rate configuration, advanced multi-timezone routing strategies, or troubleshooting an existing configuration that is not switching rates correctly, we are here to help.
📱 Contact us on WhatsApp: +8801911119966
We offer complete VOS3000 time-based routing configuration services, including Work Calendar creation, rate table design, period rate binding, account integration, testing, and documentation. Let us help you unlock the full profit potential of time-based routing in your VOS3000 operation.
📞 Need Professional VOS3000 Setup Support?
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
VOS3000 provides Web API functionality to enable automation, integration, and external system control. This guide explains VOS3000 API concepts, use cases, and security considerations.
What Is the VOS3000 API?
The VOS3000 API allows third-party systems to interact programmatically with the VOS3000 softswitch. It enables automation of tasks that would otherwise require manual web or client access.
Common VOS3000 API Use Cases
Account creation and management
Balance and billing queries
Routing updates
CDR retrieval
APIs are especially useful for large-scale operations.
VOS3000 Web API Architecture
The API operates over web protocols and integrates with the VOS3000 core services.
Requests must be authenticated and authorized to prevent misuse.
Security Considerations for API Access
Restrict API access by IP
Use secure authentication
Limit API permissions
Monitor API usage
Unsecured APIs can expose critical system functions.
VOS3000 Softswitch Rent, Installation & Price – Dedicated and Cloud Server Solutions
We provide professional VOS3000 Softswitch services including VOS3000 Rent, VOS3000 Installation, VOS3000 Hosting, and long-term technical support. Our solutions are designed for VoIP wholesalers, telecom operators, and carriers.
We offer both Dedicated Server and Cloud Server deployments with scalable capacity from 100 CC up to 5000 CC.
Table of Contents
VOS3000 Hosting & Rent Services
Our Hosted VOS3000 solutions start from 30 USDT, making it affordable for new VoIP businesses and enterprise-level providers.
Cloud VOS3000 hosting from 30 USDT
Dedicated VOS3000 server solutions
100 CC to 5000 CC supported
Carrier-grade performance
Supported VOS3000 Versions
We support all VOS3000 versions. Currently, the most stable and widely used versions are:
VOS3000 2.1.8.05 – Cloud & Dedicated Server
VOS3000 2.1.9.07 – Dedicated Server
We also provide one-time VOS3000 installation services for:
VOS3000 2.1.8.00
VOS3000 2.1.8.05
VOS3000 2.1.9.07
Dedicated Server & Cloud Server Options
Our Dedicated Servers are optimized for high traffic and large concurrent call volumes, while Cloud Servers offer flexibility and lower operational cost.
Dedicated Server supports both 2.1.8.05 and 2.1.9.07, while Cloud Server is available with VOS3000 2.1.8.05.
Payment Methods
We support multiple international payment options:
USDT (Crypto Payment)
Wise Payments
Other international payment options
Experience & Technical Support
We have been working with VOS3000 Softswitch since 2006. Our experience covers installation, upgrades, configuration, troubleshooting, and performance optimization.
VOS3000 troubleshooting & error fixing
Routing, billing, and CDR issue resolution
SIP & gateway configuration
System performance optimization
Frequently Asked Questions (FAQ)
What is VOS3000?
VOS3000 is a carrier-grade VoIP softswitch platform used for call routing, billing, SIP/H323 signaling, and telecom traffic management.
What is the VOS3000 rent price?
VOS3000 hosting starts from 30 USDT. Final price depends on server type, version, and concurrent call capacity.
Do you provide VOS3000 installation?
Yes. We provide one-time VOS3000 installation for all major versions including 2.1.8.00, 2.1.8.05, and 2.1.9.07.
Which VOS3000 version is best?
Currently, VOS3000 2.1.8.05 and 2.1.9.07 are the most stable and widely deployed versions.
Do you offer troubleshooting support?
Yes. We provide full troubleshooting and technical support for all VOS3000 versions.
For More details contact in whatsapp: +8801911119966 (only whatsapp text)
