VOS3000 Routing Optimization: Complete ASR/ACD-Based Gateway Selection Guide
VOS3000 routing optimization is critical for maximizing call quality and profitability in VoIP operations. By leveraging ASR (Answer Seizure Ratio) and ACD (Average Call Duration) metrics, VOS3000 can intelligently select the best performing gateways for each call, ensuring optimal quality for customers while maximizing revenue for operators. This comprehensive guide covers all routing optimization features based on official VOS3000 2.1.9.07 documentation.
📞 Need help with VOS3000 routing optimization? WhatsApp: +8801911119966
Table of Contents
🔍 Understanding Route Quality Metrics
Before configuring routing optimization, it’s essential to understand the key metrics that VOS3000 uses to evaluate gateway performance and make routing decisions.
📊 Key VoIP Quality Metrics (VOS3000 Routing Optimization)
| Metric | Full Name | Definition | Good Value |
|---|---|---|---|
| ASR | Answer Seizure Ratio | Percentage of calls that are answered | 40-60%+ (varies by route type) |
| ACD | Average Call Duration | Average length of connected calls | 3-10 minutes (depends on destination) |
| PDD | Post Dial Delay | Time from dialing to hearing ringback | < 5 seconds ideal |
| NER | Network Effectiveness Ratio | Calls delivered vs attempted | 95%+ for quality routes |
📈 ASR and ACD Impact on Profitability (VOS3000 Routing Optimization)
Reference: VOS3000 2.1.9.07 Manual, Section 4.1.1 and 4.3.3 (Page 212, 220-221)
| Scenario | Low ASR Impact | Low ACD Impact | Combined Effect |
|---|---|---|---|
| Revenue Loss | More failed calls = less billable time | Shorter calls = less revenue per call | Multiplicative revenue reduction |
| Customer Satisfaction | Frustration with failed calls | Complaints about call drops | Customer churn increases |
| Carrier Relations | Wasted capacity on failed attempts | Lower quality perception | Poor partner relationships |
⚙️ VOS3000 Routing Gateway Sorting Algorithm
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.3 (Page 220-221)
VOS3000 uses a sophisticated multi-step algorithm to determine gateway selection order when multiple gateways match a called number. Understanding this algorithm is essential for configuring optimal routing.
📊 Gateway Sorting Steps (VOS3000 Routing Optimization)
| Step | Sorting Criteria | Description | Configuration |
|---|---|---|---|
| Step 1 | Routing Strategy | Apply first/second routing strategy from mapping gateway | Mapping Gateway > Additional settings |
| Step 2 | Longest Prefix Match | Gateway with longest matching prefix takes precedence | Routing Gateway > Gateway prefix |
| Step 3 | Prefix Priority | Priority setting within same prefix | Routing Gateway > Prefix mode |
| Step 4 | Gateway Priority | Gateway priority value (lower = higher priority) | Routing Gateway > Priority |
| Step 5 | ASR/Rate Sorting | Sort by ASR or lowest rate based on configuration | System parameters |
| Step 6 | Current Day Calls | Total calls processed today | Automatic tracking |
| Step 7 | Gateway ID | Final tie-breaker by gateway ID | Gateway name |
📊 ASR-Based Routing Configuration
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 235-236)
⚙️ ASR Routing Parameters (VOS3000 Routing Optimization)
| Parameter | Default | Range | Description |
|---|---|---|---|
| SS_GATEWAY_ASR_CALCULATE | Off | On/Off | Enable real-time ASR calculation |
| SS_GATEWAY_ASR_RESERVE_TIME | 600 | 300-86400 sec | Time window for ASR calculation |
| SS_GATEWAY_ASR_RESERVE_SEPARATE | 10 | 5-24 | Number of time segments for ASR calculation |
| SS_GATEWAYASRROUTESORTCONFIG | Before line usage | Position options | Where ASR sorting is inserted in algorithm |
📐 How ASR is Calculated
Reference: VOS3000 2.1.9.07 Manual, Section 4.1.1 (Page 212)
VOS3000 ASR Calculation Method: =============================== Formula: ASR = (Answered Calls / Total Call Attempts) × 100% VOS3000 divides ASR calculation into time segments: - Segment length = SS_GATEWAY_ASR_RESERVE_TIME / SS_GATEWAY_ASR_RESERVE_SEPARATE - Example: 600 / 10 = 60 seconds per segment - ASR at any point = mean of last 10 segments (rolling average) Example Calculation: =================== SS_GATEWAY_ASR_RESERVE_TIME = 600 (10 minutes) SS_GATEWAY_ASR_RESERVE_SEPARATE = 10 segments Time segments (each 60 seconds): Segment 1: 0-60 sec → 45 attempts, 25 answered = 55.6% ASR Segment 2: 60-120 sec → 50 attempts, 30 answered = 60.0% ASR Segment 3: 120-180 sec → 40 attempts, 22 answered = 55.0% ASR ... (and so on) Current ASR = Average of last 10 segments = ~57% Benefits of Rolling Average: ============================ - Smooths out temporary fluctuations - Reflects recent gateway performance - Adapts to changing network conditions - Prevents single bad period from dominating
🔧 Enabling ASR-Based Routing
Step-by-Step ASR Routing Configuration: ======================================= 1. Enable Real-Time ASR Calculation: Location: Softswitch management > Additional settings > System parameter Parameter: SS_GATEWAY_ASR_CALCULATE Set to: On 2. Configure ASR Time Window: Parameter: SS_GATEWAY_ASR_RESERVE_TIME Recommended: 600 (10 minutes) for responsive routing Higher values = more stable but slower to react 3. Set Calculation Segments: Parameter: SS_GATEWAY_ASR_RESERVE_SEPARATE Recommended: 10 segments Each segment = 60 seconds in this example 4. Set ASR Sorting Position: Parameter: SS_GATEWAYASRROUTESORTCONFIG Options: - "Before line usage" (default) - "Before gateway ID" 5. Enable ASR Routing on Gateway: Location: Routing Gateway > Additional settings Check: "Calculate routing quality in real time" 6. Apply and Test: - Make test calls - Monitor CDR for gateway selection - Verify ASR-based routing is active
📊 ACD-Based Routing Configuration
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 235-236)
⚙️ ACD Routing Parameters (VOS3000 Routing Optimization)
| Parameter | Default | Range | Description |
|---|---|---|---|
| SS_GATEWAY_ACD_CALCULATE | Off | On/Off | Enable real-time ACD calculation |
| SS_GATEWAY_ACD_RESERVE_TIME | 600 | 300-86400 sec | Time window for ACD calculation |
| SS_GATEWAY_ACD_RESERVE_SEPARATE | 10 | 5-24 | Number of time segments for ACD calculation |
📐 ACD Calculation Method
VOS3000 ACD Calculation: ======================== Formula: ACD = Total Duration of Answered Calls / Number of Answered Calls Example: - 30 answered calls in time window - Total duration: 4500 seconds - ACD = 4500 / 30 = 150 seconds (2.5 minutes) ACD indicates call quality: - High ACD (> 180 sec): Good voice quality, engaged conversations - Medium ACD (60-180 sec): Normal for most destinations - Low ACD (< 60 sec): Possible quality issues, quick hangups Use Cases for ACD Routing: ========================== 1. Route to gateways with longer average call duration 2. Avoid gateways where calls drop quickly 3. Balance quality with cost considerations 4. Detect and avoid fraud routes (unusually high ACD)
💰 Rate-Based Routing Configuration
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.3 (Page 220-221)
⚙️ Rate Routing Parameters
| Parameter | Default | Description |
|---|---|---|
| SS_GATEWAYFEERATEROUTESORTCONFIG | Before line usage | Position for rate-based sorting in algorithm |
| SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASR | Off | Rate routing priority over ASR routing |
⚖️ Balancing Cost vs Quality (VOS3000 Routing Optimization)
The key decision in routing optimization is balancing cost (rate) against quality (ASR/ACD). VOS3000 provides multiple strategies:
| Strategy | Configuration | Best For | Trade-off |
|---|---|---|---|
| Lowest Cost First | Rate routing before ASR, ASR disabled | Wholesale, high margin routes | May have quality issues |
| Best Quality First | ASR routing before rate, rate disabled | Premium services, retail | Higher cost per minute |
| Balanced Approach | Both enabled, rate before ASR | General wholesale operations | Moderate cost, moderate quality |
| Quality with Cost Fallback | ASR before rate, rate as secondary | Premium with cost management | Quality prioritized when available |
🔄 Gateway Switch Configuration
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 236)
⚙️ Gateway Switch Parameters
| Parameter | Default | Description |
|---|---|---|
| SS_GATEWAY_SWITCH_LIMIT | None | Maximum auto-switch attempts before stopping |
| SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START | On | Stop switching after RTP media starts |
| SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY | On | Stop switching when user is busy |
| SS_GATEWAY_SWITCH_UNTIL_CONNECT | Off | Keep switching until call connects |
📐 Gateway Switch Behavior (VOS3000 Routing Optimization)
How Gateway Switching Works: ============================ When a call fails on one gateway, VOS3000 can automatically try the next available gateway. Example with SS_GATEWAY_SWITCH_LIMIT = 3: ========================================= Call attempt 1: Gateway A (fails) Call attempt 2: Gateway B (fails) Call attempt 3: Gateway C (fails) → Stop trying, return failure to caller Example with SS_GATEWAY_SWITCH_LIMIT = None: ============================================ Call attempt 1: Gateway A (fails) Call attempt 2: Gateway B (fails) Call attempt 3: Gateway C (connects) → Success! Configuration Recommendations: ============================= - High-value routes: SS_GATEWAY_SWITCH_LIMIT = None (unlimited retries) - Standard routes: SS_GATEWAY_SWITCH_LIMIT = 3-5 - Capacity-limited: SS_GATEWAY_SWITCH_LIMIT = 2-3 Stop Conditions: ================ - RTP Started: Stop after media established (prevents disruption) - User Busy: Don't retry on busy destination - Until Connect: Keep trying until connected or all gateways exhausted
📊 Quality Reserve Time System
Reference: VOS3000 2.1.9.07 Manual, Section 4.1.1 (Page 212)
The quality reserve time system controls how VOS3000 calculates and uses quality metrics for routing decisions.
⚙️ Quality Reserve Parameters (VOS3000 Routing Optimization)
| Parameter | Default | Purpose |
|---|---|---|
| SS_GATEWAY_QUALITY_RESERVE_TIME | 600 | Total time window for quality calculation (seconds) |
| SS_GATEWAY_QUALITY_RESERVE_SEPARATE | 10 | Number of segments to divide the time window |
📐 Quality Calculation Example
Quality Reserve Time Calculation: ================================= Given: - SS_GATEWAY_QUALITY_RESERVE_TIME = 600 seconds (10 minutes) - SS_GATEWAY_QUALITY_RESERVE_SEPARATE = 10 segments Each segment = 600 / 10 = 60 seconds Gateway ASR over 10 minutes: Segment 1 (0-60s): 55% ASR Segment 2 (60-120s): 58% ASR Segment 3 (120-180s): 52% ASR Segment 4 (180-240s): 60% ASR Segment 5 (240-300s): 57% ASR Segment 6 (300-360s): 54% ASR Segment 7 (360-420s): 59% ASR Segment 8 (420-480s): 56% ASR Segment 9 (480-540s): 61% ASR Segment 10 (540-600s): 58% ASR Current Gateway ASR = Average of all 10 segments = 57% This rolling average provides: - Smooth response to quality changes - Protection from temporary spikes - Historical context for decisions
🔗 Related Resources (VOS3000 Routing Optimization)
- 📖 VOS3000 Call Routing Guide
- 📖 NoAvailableRouter Error Troubleshooting
- 📖 VOS3000 Concurrent Call Load Test
- 📖 VOS3000 Gateway Configuration
- 📖 VOS3000 Downloads
❓ Frequently Asked Questions
What is a good ASR value for VoIP routes?
ASR values vary significantly by destination type. International routes typically see 30-50% ASR, while domestic routes may achieve 50-70%. Premium routes can reach 70%+. Compare your ASR against industry benchmarks for similar destinations rather than absolute values.
Should I use ASR or rate-based routing?
It depends on your business model. For wholesale operations with thin margins, rate-based routing may be appropriate. For retail or premium services where customer satisfaction is critical, ASR-based routing ensures better quality. Many operators use a balanced approach with rate routing as primary and ASR as quality threshold.
How often does VOS3000 update ASR calculations?
VOS3000 calculates ASR continuously in real-time when SS_GATEWAY_ASR_CALCULATE is enabled. The quality reserve time parameters determine the time window and granularity. With default settings (600 seconds, 10 segments), each 60-second period contributes to the rolling average.
Can gateway switching cause duplicate calls?
No, VOS3000 handles gateway switching at the signaling level. When a call fails on one gateway, the system tries the next gateway before responding to the caller. The caller sees only one call attempt, even if VOS3000 tried multiple gateways internally.
How do I monitor route quality in VOS3000?
Use the Gateway Performance reports in VOS3000: Navigation > Data query > CDR Analysis > Historical Performance. This shows ASR, ACD, and call volume trends. You can also enable gateway analysis reports in system parameters.
📞 Get Expert Help with VOS3000 Routing Optimization
Need assistance configuring optimal routing strategies? Our VOS3000 experts can help you design ASR/ACD-based routing, tune quality parameters, and maximize your VoIP profitability.
📱 WhatsApp: +8801911119966
Contact us for VOS3000 installation, routing optimization, gateway configuration, and professional VoIP support services!
📞 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
 | | |
