VOS3000 Gateway Switch Limit, VOS3000 RTP Lock-In, VOS3000 Aggressive Gateway Failover, VOS3000 Busy Stop Switch, VOS3000 real-time gateway ASR, VOS3000 ASR Cost Routing, VOS3000 Prefix Mode Extension

VOS3000 ASR Cost Routing Order Important SS_GATEWAY_ASR_ROUTE_SORT_CONFIG

April 26, 2026April 26, 2026 king

VOS3000 ASR Cost Routing Order Strategic SS_GATEWAY_ASR_ROUTE_SORT_CONFIG

📊 Every VoIP operator faces the same fundamental routing question: when multiple gateways can deliver a call to the same destination, should you route through the gateway with the best quality (highest ASR) or the lowest cost? The VOS3000 ASR cost routing order system, controlled by SS_GATEWAY_ASR_ROUTE_SORT_CONFIG and SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG, gives you precise control over this critical trade-off. By configuring where ASR quality sorting and cost-based sorting appear in the gateway selection priority chain, you can implement a VOS3000 ASR cost routing order strategy that prioritizes quality for premium traffic, cost for wholesale margin optimization, or any balance in between. 🔧

⚙️ The SS_GATEWAY_ASR_ROUTE_SORT_CONFIG parameter determines the position in the routing sort algorithm where gateways are ordered by their real-time ASR quality. The companion parameter SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG determines where gateways are sorted by their cost (lowest rate per second). And the tiebreaker parameter SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASR decides which metric takes priority when both ASR and cost sorting are configured at the same position. Together, these three parameters give you complete control over the VOS3000 ASR cost routing order, allowing you to design a VOS3000 ASR cost routing order strategy that aligns with your business priorities. 📈

🎯 This guide provides a complete, manual-verified reference for the ASR and cost routing sort parameters. All parameter definitions are sourced from the official VOS3000 2.1.9.07 English manual §4.3.5.2 (page 235–236) and the routing gateway sorting algorithm documented in §4.3.3, with detailed explanations of how each parameter affects gateway selection, practical configuration scenarios, and strategic recommendations for different business models. 📘

🔐 What Is the VOS3000 ASR Cost Routing Order?

📋 The VOS3000 ASR cost routing order is the relative priority of quality-based (ASR) versus cost-based (fee rate) sorting in the gateway selection algorithm. When a call arrives and multiple routing gateways match the destination prefix, VOS3000 must decide which gateway to try first. The VOS3000 ASR cost routing order determines this decision through a sequence of sorting steps, and the ASR_ROUTE_SORT_CONFIG and FEE_RATE_ROUTE_SORT_CONFIG parameters determine where ASR quality and cost sorting occur within that sequence.

💡 The three key parameters controlling ASR vs cost routing:

📊 SS_GATEWAY_ASR_ROUTE_SORT_CONFIG: Position where ASR quality sorting occurs (default: “Before line usage”)
💰 SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG: Position where cost-based sorting occurs (default: “Before line usage”)
🔄 SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASR: Tiebreaker — whether cost takes priority over ASR when both are at the same position (default: Off)

📊 The VOS3000 Routing Sort Algorithm

🔧 Understanding the VOS3000 ASR cost routing order requires understanding the complete gateway sorting algorithm documented in the VOS3000 manual §4.3.3. The VOS3000 ASR cost routing order determines how gateways are prioritized when multiple matches exist. When multiple routing gateways match a call’s destination prefix, VOS3000 sorts them through a multi-step priority chain:

Step	Sort Criterion	Description
1	Routing strategy	If mapping gateway or calling phone has first/second routing strategy enabled
2	Longest prefix match	Route with longest matching prefix takes precedence
3	Prefix priority	Routing gateway prefix priority number
4	Gateway priority	Gateway priority number (smaller is higher)
5	Line usage + ASR/Rate sort	Sort by line usage — ASR and Rate sort applied based on their CONFIG position
6	Current day total calls	+ ASR/Rate sort if configured at this position
7	Gateway ID	+ ASR/Rate sort if configured at this position

💡 How ASR and Rate sort integrate: At each step (5, 6, or 7), if ASR_ROUTE_SORT_CONFIG matches that step’s position, gateways are additionally sorted by ASR quality. Similarly, if FEE_RATE_ROUTE_SORT_CONFIG matches that step, gateways are additionally sorted by lowest rate per second. If both ASR and Rate sort are configured at the same position, the SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASR parameter determines which is applied first. For more on the complete routing algorithm, see our routing optimization guide.

📋 ASR Route Sort Config Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_ASR_ROUTE_SORT_CONFIG
📝 Manual Description	Position for routing gateway’s asr routing (VOS3000 2.1.9.07 manual §4.3.5.2, page 235)
🔧 Default Value	Before line usage
📋 Possible Values	Before line usage / Before current day total call / Before gateway ID

💰 Fee Rate Route Sort Config Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG
📝 Manual Description	Position for routing gateway’s rate routing (VOS3000 2.1.9.07 manual §4.3.5.2, page 235)
🔧 Default Value	Before line usage
📋 Possible Values	Before line usage / Before current day total call / Before gateway ID

🔄 Fee Rate Before ASR Tiebreaker Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASR
📝 Manual Description	Rate routing priority over asr routing (VOS3000 2.1.9.07 manual §4.3.5.2, page 235)
🔧 Default Value	Off
📋 Effect When On	Cost-based sorting takes priority over ASR quality when both are at the same position
📋 Effect When Off	ASR quality sorting takes priority over cost when both are at the same position

📊 Strategic Configuration Scenarios

🎯 The VOS3000 ASR cost routing order can be configured to support different business strategies. Choosing the right VOS3000 ASR cost routing order is critical for aligning routing with revenue goals. Here are the three most common strategic configurations and their trade-offs:

Strategy	ASR Route Sort	Rate Route Sort	Rate Before ASR
📊 Quality-first (ASR priority)	Before line usage	Before current day total call	Off
💰 Cost-first (margin priority)	Before current day total call	Before line usage	On
⚖️ Balanced (both at same position)	Before line usage	Before line usage	Off (ASR wins tiebreaker)

📊 Quality-First Strategy: ASR Priority

🎯 In the quality-first strategy, ASR quality sorting occurs at the highest priority position (“Before line usage”), while cost sorting is pushed to a lower position (“Before current day total call”). This means VOS3000 first tries the gateway with the highest ASR for each destination, and only considers cost as a secondary factor when multiple gateways have similar quality. This strategy is ideal for retail VoIP providers and premium termination services where call completion and customer satisfaction are the primary business drivers. The VOS3000 ASR cost routing order in quality-first mode ensures callers reach their destination reliably.

💡 Business impact: Quality-first routing typically results in higher ASR (3–8% improvement), lower PDD (faster connection on first attempt), and better customer experience. However, it may route calls through more expensive gateways, reducing per-minute margin. The trade-off is justified when customer retention and satisfaction outweigh per-call margin optimization. For comprehensive quality monitoring, see our ASR ACD analysis guide.

💰 Cost-First Strategy: Margin Priority

💵 In the cost-first strategy, fee rate sorting occurs at the highest priority position (“Before line usage”), while ASR quality sorting is pushed to a lower position. The FEE_RATE_ROUTE_BEFORE_ASR tiebreaker is set to On. This means VOS3000 first tries the gateway with the lowest cost for each destination, and only considers quality as a secondary factor when multiple gateways have similar pricing. This strategy is ideal for wholesale VoIP carriers and high-volume termination providers where per-minute margin is the primary business driver. The VOS3000 ASR cost routing order in cost-first mode maximizes margin on every call.

💡 Business impact: Cost-first routing maximizes per-minute margin by always routing through the cheapest available gateway. However, cheaper gateways often have lower ASR, which means more calls fail and need to be switched to backup gateways, increasing PDD and CPS load. The trade-off is justified when margin optimization outweighs call completion rates, and when you have enough failover depth to compensate for lower-quality primary routes. For cost-based routing configuration, see our LCR least cost routing guide.

⚖️ Balanced Strategy: Quality with Cost Awareness

🔄 In the balanced strategy, both ASR and cost sorting are configured at the same position (“Before line usage”), with the FEE_RATE_ROUTE_BEFORE_ASR tiebreaker set to Off (ASR wins). This creates a nuanced routing behavior where ASR quality is the primary differentiator, but cost is also considered within the same sort step. When two gateways have similar ASR, the cheaper one is preferred. This strategy is ideal for operators who want quality-first routing with cost awareness, using the VOS3000 ASR cost routing order to avoid the extreme of either pure quality or pure cost optimization.

📊 ASR Cost Routing Sort Position Impact Analysis

📈 The position where ASR and cost sorting occur in the routing algorithm has a significant impact on gateway selection behavior. The VOS3000 ASR cost routing order position determines how strongly quality or cost influences the final gateway choice. The following table analyzes each position’s effect:

Sort Position	When Applied	Impact on Gateway Selection
Before line usage (highest)	Step 5 — before load balancing by line utilization	🔴 Strong impact — quality or cost dominates over load distribution
Before current day total call (medium)	Step 6 — after line usage but before total call count	🟡 Moderate impact — load balancing considered first, then quality or cost
Before gateway ID (lowest)	Step 7 — last step before gateway ID tiebreaker	🟢 Weak impact — quality or cost only breaks ties between otherwise equal gateways

💡 Configuration tip: If you want ASR or cost to have a strong influence on gateway selection, use “Before line usage” (the highest position). If you want load balancing to be the primary factor with quality or cost as a secondary consideration, use “Before current day total call” or “Before gateway ID.” The position you choose should align with your business strategy: quality-driven operators should place ASR at the highest position in the VOS3000 ASR cost routing order, while cost-driven operators should place rate sorting at the highest position. For more on load balancing behavior, see our call routing guide.

🛡️ Common ASR Cost Routing Order Problems and Solutions

❌ Problem 1: ASR Sorting Not Taking Effect

🔍 Symptom: Real-time ASR calculation is enabled and showing values for gateways, but the routing selection does not appear to prefer higher-ASR gateways.

💡 Cause: The most common cause is that SS_GATEWAY_ASR_ROUTE_SORT_CONFIG is set to a low-priority position (e.g., “Before gateway ID”) while another sort criterion at a higher position is dominating the gateway selection in the VOS3000 ASR cost routing order. Another common cause is that not all gateways have ASR calculation enabled — gateways without ASR data are sorted before ASR-enabled gateways.

✅ Solutions:

🔧 Verify SS_GATEWAY_ASR_ROUTE_SORT_CONFIG is set to “Before line usage” for maximum VOS3000 ASR cost routing order impact
📊 Ensure all production gateways have “Real time computing asr” enabled in their Additional settings
📋 Check that gateway priority numbers (Step 4) are not overriding the ASR sort

❌ Problem 2: Cost Routing Selects Low-Quality Gateways

🔍 Symptom: Calls are being routed through the cheapest gateways, but those gateways have poor ASR, leading to high call failure rates and long PDD from failover attempts.

💡 Cause: SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG is at a higher position than ASR_ROUTE_SORT_CONFIG, or FEE_RATE_ROUTE_BEFORE_ASR is On at the same position, causing cost to always win over quality.

✅ Solutions:

🔧 Swap the positions — put ASR at “Before line usage” and Rate at “Before current day total call”
📊 Set SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASR = Off to give ASR the tiebreaker
📋 Consider using profit margin settings to automatically exclude gateways where the margin is too thin

❌ Problem 3: All Calls Going to Same Gateway Despite Multiple Routes

🔍 Symptom: Multiple gateways are configured for a destination, but almost all calls go to the same gateway, causing overload on that gateway while others are underutilized.

💡 Cause: The sort configuration creates a strong preference for one gateway that consistently wins at the highest-priority sort step. If ASR is at the highest position and one gateway has significantly higher ASR than others, that gateway will receive nearly all traffic.

✅ Solutions:

🔧 Move ASR sort to a lower position (“Before current day total call”) to allow load balancing more influence
📊 Ensure line limit settings properly distribute traffic across gateways
📋 Review the gateway configuration for line limit and reserved line settings

💡 ASR vs Cost Routing Order Best Practices

🎯 Follow these best practices for optimal VOS3000 ASR cost routing order configuration. The VOS3000 ASR cost routing order is one of the most important routing decisions you will make:

Best Practice	Recommendation	Reason
📊 Enable ASR calculation first	Set SS_GATEWAY_ASR_CALCULATE = On before configuring sort order	🔧 ASR sort has no effect without calculated ASR data — the VOS3000 ASR cost routing order depends on real-time ASR values
⚖️ Match strategy to business model	Quality-first for retail, cost-first for wholesale in the VOS3000 ASR cost routing order	📊 Aligns routing behavior with revenue priorities
📋 Test before deploying	Change sort configuration during low-traffic periods	🔄 Sort order changes can dramatically shift traffic patterns
📊 Monitor after changes	Track ASR, PDD, and margin for 24–48 hours after VOS3000 ASR cost routing order configuration change	📈 Verify the routing strategy produces expected results
🔧 Set proper switch limit	SS_GATEWAY_SWITCH_LIMIT = 3–4 as safety cap — prevents runaway failover regardless of VOS3000 ASR cost routing order	🛡️ Prevents runaway failover regardless of sort order

❓ Frequently Asked Questions

❓ What is the default value of SS_GATEWAY_ASR_ROUTE_SORT_CONFIG?

🔧 The default value is “Before line usage”, as documented in the VOS3000 2.1.9.07 manual §4.3.5.2 (page 235). This means that by default, ASR quality sorting occurs at Step 5 of the routing algorithm, before line utilization is considered. This is a quality-leaning default that prefers higher-ASR gateways over more-available (less utilized) gateways in the VOS3000 ASR cost routing order. If your business priorities favor cost optimization over quality, you may want to adjust this VOS3000 ASR cost routing order position or change the FEE_RATE_ROUTE_BEFORE_ASR tiebreaker.

❓ What happens when both ASR and Rate sort are at the same position?

🔄 When both SS_GATEWAY_ASR_ROUTE_SORT_CONFIG and SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG are set to the same position (e.g., both “Before line usage”), the SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASR parameter determines which sort criterion is applied first. If FEE_RATE_ROUTE_BEFORE_ASR is Off (default), ASR quality sorting is applied first, and then cost sorting is applied within groups of gateways that have the same ASR. If it is On, cost sorting is applied first, and then ASR sorting is applied within groups of gateways that have the same cost. The practical difference in the VOS3000 ASR cost routing order is significant: with ASR-first, the highest-ASR gateway is always tried first regardless of cost; with cost-first, the cheapest gateway is always tried first regardless of quality.

❓ Does the ASR sort position affect gateways without ASR calculation enabled?

📊 Yes, the VOS3000 routing sort algorithm gives special treatment to gateways that do not have real-time ASR calculation enabled. According to the routing sort documentation in §4.3.3, “Routings which disabled real-time computing ASR priory than enabled one.” This means that gateways without ASR data are sorted before gateways with ASR data at the same sort position.

The rationale is that gateways with unknown quality should be tried before gateways with known poor quality. However, this also means that if you enable ASR for some gateways but not others, the gateways without ASR may receive more traffic than expected, even if their actual quality is poor. For consistent VOS3000 ASR cost routing order behavior, enable ASR calculation for all production gateways.

❓ Can I configure different sort orders for different destinations?

📋 No, the VOS3000 ASR cost routing order parameters SS_GATEWAY_ASR_ROUTE_SORT_CONFIG and SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG are system-level parameters that apply globally to all routing decisions. You cannot set different sort orders for different destinations or prefixes. However, you can influence the effective sort order per destination by configuring gateway priority numbers (Step 4 in the sort algorithm) differently for each destination’s gateways.

Additionally, you can use the mapping gateway’s first and second routing strategy (Step 1) to override the normal sort algorithm for specific traffic sources. For advanced routing configuration, see our routing optimization guide.

❓ How do I know if my ASR cost routing order is working correctly?

📊 To verify your VOS3000 ASR cost routing order configuration, examine the CDR data for calls to a destination served by multiple gateways. If ASR-first routing is configured, you should see that the first-attempt gateway consistently has the highest ASR among all available gateways for that destination. If cost-first routing is configured, the first-attempt gateway should consistently be the cheapest option. You can also use the gateway analysis reports in VOS3000 to compare ASR and cost across gateways serving the same destination, and verify that the routing selection aligns with your configured sort order.

❓ Should I use ASR-first or cost-first routing?

🎯 The answer depends on your business model and priorities. Use ASR-first routing when customer satisfaction and call completion are your primary revenue drivers — this includes retail VoIP, premium termination, and enterprise SIP trunking. The VOS3000 ASR cost routing order in ASR-first mode ensures the highest quality gateway is always tried first. Use cost-first routing when per-minute margin is your primary revenue driver — this includes wholesale termination, carrier-to-carrier traffic, and high-volume commodity routing. The VOS3000 ASR cost routing order in cost-first mode always selects the cheapest gateway.

Many operators use a balanced approach where ASR is the primary sort criterion but cost is considered at the same position (with FEE_RATE_ROUTE_BEFORE_ASR = Off), ensuring that quality is prioritized while cheaper options are preferred among gateways with similar ASR. This balanced VOS3000 ASR cost routing order approach works well for most operators. For personalized routing strategy advice, contact us via WhatsApp.

📞 Need Expert Help with VOS3000 ASR Cost Routing Order?

🔧 Configuring the VOS3000 ASR cost routing order is one of the most impactful routing decisions you will make for your VoIP operation. The VOS3000 ASR cost routing order directly controls whether your system prioritizes call quality or cost efficiency. Whether you are implementing quality-first routing for a retail service, cost-first routing for wholesale termination, or designing a balanced strategy that optimizes both quality and margin, expert guidance ensures your routing configuration aligns with your business objectives and delivers measurable results. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 ASR cost routing order configuration, VOS3000 ASR cost routing order strategy design, and performance optimization. Our team specializes in VOS3000 routing engine configuration, quality-based routing, and margin optimization for carrier-grade VoIP deployments. 🔧

🔗 Explore related VOS3000 routing and quality configuration guides:

VOS3000 ASR ACD Analysis — Complete ASR and ACD monitoring methodology
VOS3000 LCR Least Cost Routing — Cost-based routing configuration
VOS3000 Routing Optimization — Quality and cost routing optimization
VOS3000 Profit Margin Complete — Margin analysis and optimization
VOS3000 Gateway Analysis Reports — Analyzing gateway performance data
VOS3000 System Parameters — Complete system parameter reference

📞 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

VOS3000 Prefix Mode Extension Expiration Smart Gateway Easy Selection Method

April 26, 2026April 26, 2026 king

VOS3000 Prefix Mode Extension Expiration Smart Gateway Selection Method

🔄 When a call arrives at VOS3000 and matches a routing gateway by its prefix, but that gateway cannot deliver the call, the softswitch must decide: should it try shorter prefix matches that also apply to this number, or should it stop trying additional prefixes altogether? This decision is controlled by the VOS3000 prefix mode extension expiration setting — a per-gateway configuration that determines how aggressively VOS3000 searches for alternative prefix matches when the primary gateway fails.

Understanding and correctly configuring the VOS3000 prefix mode extension expiration is essential for building routing chains that balance call completion with routing efficiency. 🔧

⚙️ VOS3000 supports four prefix modes for each routing gateway: Extension, Expiration, Terminal, and Continual. The Extension and Expiration modes are the two most strategically important VOS3000 prefix mode extension expiration options because they represent opposite philosophies: Extension mode enables fallback to shorter prefixes when a gateway fails, maximizing the chances of call delivery, while Expiration mode stops prefix-based failover entirely, creating a hard boundary that prevents routing beyond the matched prefix scope.

The Terminal and Continual modes are variants that control how the prefix chain is traversed. The VOS3000 prefix mode extension expiration configuration directly impacts your call completion rate, routing efficiency, and PDD performance. 📊

🎯 This guide provides a complete, manual-verified reference for VOS3000 prefix mode configuration. All mode definitions and examples are sourced from the official VOS3000 2.1.8.0/2.1.9.07 English manual §2.5.1.1 (Routing Gateway configuration), with detailed explanations of how each VOS3000 prefix mode extension expiration mode works, practical configuration scenarios, and strategic recommendations for different routing architectures. 📘

🔐 What Is VOS3000 Prefix Mode?

📋 The VOS3000 prefix mode is a per-gateway setting that controls what happens when a routing gateway matched by a specific prefix cannot deliver a call. The VOS3000 prefix mode extension expiration behavior determines how the softswitch handles prefix-based failover. When you configure a routing gateway, you assign it one or more prefixes (such as “901,” “90,” or “9”) that determine which called numbers this gateway will handle. When a call arrives with a called number that matches multiple gateway prefixes, VOS3000 must decide how to traverse the prefix hierarchy if the first gateway fails.

💡 Why prefix mode matters:

📞 Call completion: Extension mode provides more fallback options, increasing the chance that a call will be delivered even when the primary gateway fails — this is a key benefit of the VOS3000 prefix mode extension expiration Extension setting
⏱️ PDD impact: Expiration mode stops searching earlier, reducing PDD for calls that cannot be delivered through any prefix match — this VOS3000 prefix mode extension expiration Expiration advantage saves caller time
📊 Routing efficiency: Expiration mode avoids wasting switch attempts on short-prefix gateways that may have entirely different rate and quality characteristics
🔧 Billing accuracy: Prefix mode affects which gateway’s rate table is used for billing, which impacts the rate applied to the call
📋 Number transformation: Different prefix lengths may require different digit manipulation (stripping, adding), and prefix mode controls whether those transformations cascade

📊 The Four VOS3000 Prefix Modes

📋 VOS3000 supports four prefix modes, each defining a different VOS3000 prefix mode extension expiration behavior for prefix-based gateway traversal when a call fails to connect through the initially matched gateway. The VOS3000 prefix mode extension expiration choice determines the failover scope:

Prefix Mode	Behavior	When Failed Gateway Matched by This Prefix
📋 Extension	Shorter prefixes will be tried	VOS3000 falls back to gateways matching shorter prefixes of the same number
🚫 Expiration	No more prefixes will be tried	VOS3000 stops trying prefix-based gateways entirely — call fails
🔴 Terminal	Only same-length prefix gateways are tried	VOS3000 only tries other gateways with the same prefix length, not shorter ones
🟢 Continual	All prefixes will be tried	VOS3000 tries gateways matching all shorter prefixes in order

💡 Extension vs Continual distinction: Both Extension and Continual modes try shorter prefixes when a gateway fails under the VOS3000 prefix mode extension expiration system, but they differ in scope. Extension mode tries progressively shorter prefixes that are logical extensions of the current prefix, while Continual mode tries all remaining prefix-matched gateways regardless of their prefix relationship to the current one.

The VOS3000 prefix mode extension expiration distinction between Extension and Continual is important for routing design. The practical difference is that the VOS3000 prefix mode extension expiration Continual mode provides the broadest possible failover coverage, while Extension mode provides a more targeted fallback within the prefix hierarchy. The VOS3000 manual documents these modes in the routing gateway configuration section (§2.5.1.1, page 26).

📋 VOS3000 Prefix Mode Configuration Location

Attribute	Detail
📌 Setting Name	Prefix mode
📝 Manual Reference	VOS3000 2.1.8.0/2.1.9.07 manual §2.5.1.1 (page 26)
📍 Configuration Path	Operation management > Gateway operation > Routing gateway > Gateway prefix > Prefix mode
📋 Scope	Per gateway — each routing gateway can have its own prefix mode setting
🔄 Options	Extension / Expiration / Terminal / Continual

🔄 Extension Mode: Shorter Prefixes Will Be Tried

📊 When a routing gateway’s prefix mode is set to Extension, VOS3000 will attempt to route the call through gateways matching shorter prefixes if the current gateway cannot deliver the call. The VOS3000 prefix mode extension expiration Extension setting creates a cascading fallback mechanism where the most specific (longest) prefix match is tried first, and progressively less specific (shorter) prefix matches are attempted as fallbacks.

💡 How Extension mode works:

📞 Call arrives for number “90080001”
🔑 VOS3000 matches gateways by prefix: gw2 (prefix “9008”), gw4 (prefix “900”), gw3 (prefix “90”), gw1 (prefix “9”)
📊 VOS3000 tries gw2 first (longest prefix match)
🔄 If gw2 fails and its prefix mode is Extension, VOS3000 tries gw4 (shorter prefix “900”)
🔄 If gw4 fails, VOS3000 tries gw3 (shorter prefix “90”)
🔄 If gw3 fails, VOS3000 tries gw1 (shortest prefix “9”)
🚫 If all fail, the call is rejected

📊 When to use Extension mode: Extension mode is appropriate when you have a hierarchical routing structure where longer prefixes represent more specific (and potentially higher-quality) routes, and shorter prefixes represent broader fallback routes.

This is common in international routing where “country code + area code” (long prefix) routes to a specific regional carrier, while “country code only” (short prefix) routes to a general carrier. If the regional carrier fails, Extension mode ensures the call falls back to the general carrier. For prefix configuration guidance, see our prefix settings guide.

🚫 Expiration Mode: No More Prefixes Will Be Tried

📋 When a routing gateway’s prefix mode is set to Expiration, VOS3000 will not attempt to route the call through any other prefix-matched gateways if the current gateway fails. The VOS3000 prefix mode extension expiration Expiration setting creates a hard boundary in the routing chain.

💡 How Expiration mode works:

📞 Call arrives for number “90080001”
🔑 VOS3000 matches gateways by prefix: gw2 (prefix “9008”), gw4 (prefix “900”), gw3 (prefix “90”), gw1 (prefix “9”)
📊 VOS3000 tries gw2 first (longest prefix match)
🚫 If gw2 fails and its prefix mode is Expiration, VOS3000 stops trying — no fallback to shorter prefixes
📋 The call is rejected with an appropriate failure response

📊 When to use Expiration mode: Expiration mode is appropriate when the matched gateway represents the only acceptable route for that prefix, and routing through a shorter-prefix gateway would be inappropriate or undesirable. Common scenarios include: dedicated private routes where only one carrier is authorized, premium rate destinations where cost control is critical, and emergency or special service numbers where routing must be precisely controlled.

Expiration mode prevents calls from “leaking” to unauthorized or inappropriate backup routes. The VOS3000 prefix mode extension expiration Expiration mode is the right choice for these strict routing scenarios.

📊 Terminal and Continual Modes

📋 In addition to Extension and Expiration, VOS3000 supports two additional VOS3000 prefix mode extension expiration modes that provide more granular control over the prefix traversal behavior:

🔴 Terminal Mode: Same-Length Prefixes Only

📋 When a gateway’s prefix mode is set to Terminal, VOS3000 only tries other gateways that match the same prefix length as the current gateway. It does not fall back to shorter prefixes. This is useful when you have multiple gateways serving the same prefix length (e.g., multiple carriers for prefix “9008”) but do not want to fall back to broader routes.

💡 Terminal mode example from the VOS3000 manual (page 26): “If the prefix mode of ‘gw2’ is set to ‘Terminal’, the prefixes being tried for the number ‘90080001’ will be ‘gw2’ and ‘gw4’ in order.” Here, gw2 matches prefix “9008” and gw4 also matches at the same prefix level. The Terminal mode allows VOS3000 to try gw4 as a same-level alternative, but does not cascade to shorter-prefix gateways like gw3 or gw1.

🟢 Continual Mode: All Prefixes Tried

📋 When a gateway’s prefix mode is set to Continual, VOS3000 tries all remaining prefix-matched gateways in order, including those matching shorter prefixes. This is the most aggressive prefix traversal mode, providing the maximum number of fallback options for call delivery.

💡 Continual mode example from the VOS3000 manual (page 26): “If the prefix mode of ‘gw2’ is set to ‘Continual’, while others remain the same, the prefixes being tried for the number ‘90080001’ will be ‘gw2’, ‘gw4’, ‘gw3’, and ‘gw1’ in order.” This means that when gw2 fails, VOS3000 tries every other prefix-matched gateway, from the most specific to the least specific, giving the call the maximum chance of completion.

📊 Complete Prefix Mode Comparison Table

Prefix Mode	Same-Length Prefixes	Shorter Prefixes	Call Completion	PDD Impact
📋 Extension	✅ Yes	✅ Yes (progressive)	High — broad fallback	Moderate — adds some attempts
🚫 Expiration	❌ No	❌ No	Low — no fallback at all	Minimal — fast failure
🔴 Terminal	✅ Yes	❌ No	Medium — limited to same level	Low — few additional attempts
🟢 Continual	✅ Yes	✅ Yes (all)	Highest — maximum fallback	Highest — many additional attempts

📋 Prefix Mode and Number Transformation

🔧 The VOS3000 prefix mode extension expiration setting directly affects how number transformation (digit manipulation) works in the routing chain. When different prefix lengths are configured with different callee rewrite rules, the prefix mode determines whether those transformations cascade when a gateway fails:

Transformation Aspect	Extension Mode Impact	Expiration Mode Impact
📋 Prefix stripping	Each shorter prefix gateway applies its own stripping rules	Only the matched gateway’s stripping rules apply
🔢 Number transformation	Called number may be transformed differently at each fallback level	No cascading transformations — number stays as transformed by first gateway
💰 Rate table lookup	Each gateway uses its own rate table — may result in different billing rates	Only one rate table is consulted — consistent billing
📊 Caller ID handling	Different gateways may transform caller ID differently	Consistent caller ID transformation

💡 Billing consistency note: When Extension mode causes a call to fall back to a shorter-prefix gateway, the billing rate may change because each gateway has its own rate table. A call that was initially routed through a premium gateway (with a specific long prefix and premium rate) might end up being delivered through a standard gateway (with a shorter prefix and lower rate) after fallback. While this can be beneficial for call completion, it means that the actual billing rate for a call may differ from the rate initially expected.

For consistent billing regardless of fallback, configure all gateways in a prefix chain with the same rate table, or use Expiration mode to prevent fallback to gateways with different rate structures. For more on rate configuration, see our gateway route prefix billing guide.

🛡️ Common Prefix Mode Problems and Solutions

❌ Problem 1: Calls Not Falling Back to Backup Routes

🔍 Symptom: When a primary gateway fails, calls are rejected immediately instead of being tried through backup gateways that match shorter prefixes.

💡 Cause: The primary gateway’s prefix mode is set to Expiration, which prevents VOS3000 from trying shorter-prefix gateways as fallbacks.

✅ Solutions:

🔧 Change the gateway’s prefix mode to Extension or Continual to enable fallback
📊 Verify that backup gateways with shorter prefixes are properly configured and active
📋 Check the call routing configuration to ensure the prefix hierarchy is set up correctly

❌ Problem 2: Unexpected Billing Rates After Fallback

🔍 Symptom: Calls that fall back to shorter-prefix gateways are billed at different rates than expected, causing billing discrepancies.

💡 Cause: Extension or Continual mode causes calls to be routed through backup gateways that have different rate tables than the primary gateway, resulting in unexpected billing charges.

✅ Solutions:

🔧 Use Expiration mode for gateways where billing consistency is critical
💰 Configure all gateways in a prefix chain with the same or compatible rate tables
📊 Monitor CDR records for rate discrepancies using CDR billing discrepancy analysis

❌ Problem 3: Excessive PDD from Deep Prefix Cascading

🔍 Symptom: Calls experience long PDD because VOS3000 is trying many gateway prefixes in sequence, each adding a timeout before moving to the next.

💡 Cause: Continual mode with many prefix-matched gateways creates a deep fallback chain where each failed attempt adds signaling delay.

✅ Solutions:

🔧 Use Terminal or Extension mode instead of Continual to limit the fallback depth
📊 Set SS_GATEWAY_SWITCH_LIMIT to 3–4 to cap the total number of gateway attempts per call
📋 Reduce SIP INVITE timeout (SS_SIP_TIMEOUT_INVITE) to speed up individual failover attempts

💡 Prefix Mode Configuration Best Practices

🎯 Follow these best practices for optimal VOS3000 prefix mode extension expiration configuration:

Best Practice	Recommendation	Reason
📊 Use Extension for hierarchical routes	Set Extension mode for gateways with natural prefix hierarchies — the VOS3000 prefix mode extension expiration Extension option enables intelligent fallback	🔄 Enables intelligent fallback through progressively broader routes
🚫 Use Expiration for dedicated routes	Set Expiration mode for private or premium routes — the VOS3000 prefix mode extension expiration Expiration option prevents unauthorized fallback	📋 Prevents unauthorized fallback to non-premium routes
📋 Align prefix lengths with routing hierarchy	Design prefix lengths that reflect your routing fallback structure for proper VOS3000 prefix mode extension expiration behavior	🔧 Makes prefix mode behavior predictable and logical
💰 Standardize rate tables across prefix chain	Use compatible rates for gateways that may serve as fallbacks under the VOS3000 prefix mode extension expiration Extension mode	📊 Prevents billing discrepancies when fallback occurs
🔧 Pair with switch limit	Set SS_GATEWAY_SWITCH_LIMIT = 3–4 even with VOS3000 prefix mode extension expiration Extension mode enabled	⏱️ Caps PDD even when deep prefix cascading is enabled

❓ Frequently Asked Questions

❓ What is the difference between Extension and Continual prefix modes?

📋 Both Extension and Continual modes try shorter prefixes when a gateway fails, but they differ in scope. Extension mode progressively tries shorter prefixes in a hierarchical manner — it falls back to the next shorter prefix match, then the next, in order of decreasing specificity. Continual mode tries all remaining prefix-matched gateways, regardless of their prefix relationship to the current gateway. The VOS3000 manual example on page 26 illustrates this: with Terminal mode, only “gw2” and “gw4” are tried (same-level prefixes), while with Continual mode, all four gateways are tried (“gw2”, “gw4”, “gw3”, “gw1” in order).

Continual mode provides the broadest fallback coverage but may also produce the longest PDD and the most variable billing rates.

❓ When should I use Expiration mode instead of Extension mode?

🚫 Use Expiration mode when the gateway represents the only acceptable route for that prefix, and falling back to a shorter-prefix gateway would be inappropriate. The VOS3000 prefix mode extension expiration Expiration option is essential for these specific scenarios: (1) Private or dedicated routes where only one carrier is authorized to handle traffic for a specific prefix; (2) Premium rate destinations where cost control requires that calls only go through the designated premium gateway; (3) Emergency or special service numbers where routing must be precisely controlled;

(4) Compliance scenarios where regulatory requirements mandate that certain call types only traverse specific network paths. In all other cases, Extension mode is generally preferred because it provides fallback options that improve call completion rates. The VOS3000 prefix mode extension expiration Extension option delivers better call delivery rates in most deployments.

❓ How does prefix mode interact with SS_GATEWAY_SWITCH_LIMIT?

🔄 The VOS3000 prefix mode and the gateway switch limit work at different levels but both affect how many gateways are tried for a call. The VOS3000 prefix mode extension expiration behavior controls prefix-level failover, while SS_GATEWAY_SWITCH_LIMIT caps the total number of auto-switch attempts per call, regardless of whether those attempts come from prefix-mode fallback or from failover within the same prefix. For example, if SS_GATEWAY_SWITCH_LIMIT is set to 3 and a gateway with Extension mode fails,

VOS3000 may try up to 3 additional gateways (from shorter prefixes or from same-prefix alternatives), but no more. This means that even with Continual mode and many prefix-matched gateways, the switch limit ensures that the total number of attempts per call remains bounded. For more on the switch limit, see our system parameters reference.

❓ Does changing prefix mode affect existing calls?

📋 No, Changing a gateway’s prefix mode only affects new calls that are processed after the VOS3000 prefix mode extension expiration configuration change. Calls that are already in progress or already in the failover process are not affected by the configuration change. However, you should be aware that the change takes effect immediately for new calls — there is no restart or service restart required.

If you are changing from VOS3000 prefix mode extension expiration Extension to Expiration mode, new calls will immediately stop falling back to shorter prefixes, which may cause a sudden drop in call completion rates if the primary gateway is experiencing problems. Always make prefix mode changes during a maintenance window or low-traffic period when possible.

❓ Can different gateways have different prefix modes?

🔧 Yes, the VOS3000 prefix mode extension expiration setting is configured per gateway, not system-wide. Each routing gateway can have its own VOS3000 prefix mode extension expiration setting. This allows you to design a mixed routing strategy where some gateways use Extension mode (for broad fallback) while others use Expiration mode (for strict routing control).

For example, you might configure your premium international gateways with Expiration mode to prevent fallback to standard routes, while configuring your domestic gateways with Extension mode to maximize call completion. This per-gateway flexibility is one of the strengths of the VOS3000 prefix mode extension expiration system. For help designing a mixed prefix mode strategy, contact us via WhatsApp.

❓ How does prefix mode affect the routing gateway sort order?

📊 Prefix mode operates independently of the gateway sort order parameters (SS_GATEWAY_ASR_ROUTE_SORT_CONFIG and SS_GATEWAY_FEE_RATE_ROUTE_SORT_CONFIG). The sort order determines which gateways are tried first within a single prefix level, while the VOS3000 prefix mode extension expiration setting determines whether gateways at different prefix levels are tried after a failure.

Both mechanisms work together: the sort order selects the preferred gateway within a prefix level, and the VOS3000 prefix mode extension expiration configuration determines whether the search extends to shorter prefix levels if all gateways at the current level fail. For a complete understanding of how these mechanisms interact, see the routing optimization guide.

📞 Need Expert Help with VOS3000 Prefix Mode Configuration?

🔧 Correct configuration of the VOS3000 prefix mode extension expiration setting is essential for building routing chains that balance call completion with routing efficiency and billing accuracy. The VOS3000 prefix mode extension expiration choice determines whether your routing chains are flexible or strict.

Whether you are designing a hierarchical prefix structure with Extension mode fallback, implementing strict routing boundaries with Expiration mode, or troubleshooting prefix-mode-related call delivery problems, expert guidance ensures your VOS3000 routing architecture delivers optimal performance. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 prefix mode extension expiration configuration, VOS3000 prefix mode extension expiration troubleshooting, routing chain design, and number transformation troubleshooting. Our team specializes in VOS3000 routing architecture, prefix-based failover design, and carrier-grade VoIP deployment. 🔧

🔗 Explore related VOS3000 prefix and routing configuration guides:

VOS3000 Prefix Settings Guide — Complete prefix configuration for rate, area, client, and vendor
VOS3000 Gateway Route Prefix Billing — How prefix stripping affects billing lookup
VOS3000 Callee Rewrite Rule Prefix — Number transformation and rewrite rules
VOS3000 Routing Optimization — Quality and cost routing optimization
VOS3000 Gateway Configuration Routing Mapping — Gateway routing and mapping setup
VOS3000 Call Routing — Complete call routing configuration guide

📞 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

VOS3000 Real-Time Gateway ASR Advanced SS_GATEWAY_ASR_CALCULATE Best Configuration

April 26, 2026April 26, 2026 king

ARTICLE CONTENT

VOS3000 Real-Time Gateway ASR Advanced SS_GATEWAY_ASR_CALCULATE Configuration

📊 Answer-Seizure Ratio (ASR) is the most critical quality metric in VoIP routing — it tells you what percentage of call attempts through a gateway actually result in connected calls. Without real-time ASR data, routing decisions are made blindly, based on static configurations or historical assumptions that may be hours or days out of date. The VOS3000 real-time gateway ASR system, powered by SS_GATEWAY_ASR_CALCULATE and its companion parameters RESERVE_TIME and RESERVE_SEPARATE, enables the softswitch to calculate and track ASR per gateway in real time, providing the data foundation for quality-based routing decisions that can dynamically avoid underperforming routes. 🔧

⚙️ By default, SS_GATEWAY_ASR_CALCULATE is set to Off, meaning VOS3000 does not compute real-time ASR for gateways. When you enable this parameter, the softswitch begins tracking call attempts and completions for each gateway, calculating ASR within a configurable time window (RESERVE_TIME) and at a configurable granularity (RESERVE_SEPARATE). This real-time data feeds into the routing engine’s gateway sorting algorithm, allowing VOS3000 to prefer gateways with higher ASR when multiple routes are available for the same destination. The VOS3000 real-time gateway ASR system transforms routing from a static, configuration-driven process into a dynamic, data-driven operation. 📈

🎯 This guide provides a complete, manual-verified reference for the three ASR calculation parameters: SS_GATEWAY_ASR_CALCULATE, SS_GATEWAY_ASR_RESERVE_TIME, and SS_GATEWAY_ASR_RESERVE_SEPARATE. All parameter definitions are sourced from the official VOS3000 2.1.9.07 English manual §4.3.5.2 (page 235–236), with detailed explanations of how each parameter works, how they interact, and practical configuration recommendations. 📘

🔐 What Is VOS3000 Real-Time Gateway ASR?

📋 The VOS3000 real-time gateway ASR system is controlled by three system parameters documented in the VOS3000 manual §4.3.5.2 (page 235–236). Together, these parameters enable the softswitch to calculate ASR for each routing gateway in real time, using a sliding time window and configurable step size. The calculated ASR values are then used by the routing engine to sort gateways by quality when multiple routes are available.

💡 The three ASR calculation parameters:

📊 SS_GATEWAY_ASR_CALCULATE: Master switch — enables or disables real-time ASR calculation per gateway (default: Off)
⏱️ SS_GATEWAY_ASR_RESERVE_TIME: Measurement window — the length of the time window for ASR calculation in seconds (default: 600, range: 300–86400)
🔢 SS_GATEWAY_ASR_RESERVE_SEPARATE: Step size — the number of sections that the measurement window is divided into for ASR calculation (default: 10, range: 5–24)

📍 How ASR is calculated: VOS3000 calculates ASR as the ratio of connected calls (answers) to total call attempts (seizures) through a gateway within the measurement window. For example, if a gateway handled 100 call attempts in the last 600 seconds and 45 of those connected, the ASR is 45/100 = 45%. This calculation is updated continuously as new call attempts and completions occur within the sliding window.

📋 SS_GATEWAY_ASR_CALCULATE Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_ASR_CALCULATE
📝 Manual Description	Real time computing asr (VOS3000 2.1.9.07 manual §4.3.5.2, page 235)
🔧 Default Value	Off
📍 Configuration Path	Operation management > Softswitch management > Additional settings > System parameter
🔄 Per-Gateway Override	Yes — Routing gateway > Additional settings > Real time computing asr
📊 Effect When On	Softswitch calculates real-time ASR for this gateway
📊 Effect When Off	Softswitch does not calculate ASR — gateway excluded from quality-based routing

⏱️ SS_GATEWAY_ASR_RESERVE_TIME Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_ASR_RESERVE_TIME
📝 Manual Description	Length for gateway’s asr routing in seconds (VOS3000 2.1.9.07 manual §4.3.5.2, page 235)
🔧 Default Value	600 seconds (10 minutes)
📊 Value Range	300–86400 seconds (5 minutes to 24 hours)
📋 Effect	Defines the sliding time window over which ASR is calculated

💡 How RESERVE_TIME affects ASR accuracy: A shorter window (e.g., 300 seconds = 5 minutes) makes the VOS3000 real-time gateway ASR more responsive to recent changes but noisier — a few failed calls can dramatically lower the calculated VOS3000 real-time gateway ASR value. A longer window (e.g., 3600 seconds = 1 hour) produces more stable ASR values but is slower to detect quality degradation. The default of 600 seconds (10 minutes) is a reasonable balance for most VOS3000 real-time gateway ASR deployments, providing enough data points for statistical significance while being responsive enough to detect problems within minutes rather than hours.

🔢 SS_GATEWAY_ASR_RESERVE_SEPARATE Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_ASR_RESERVE_SEPARATE
📝 Manual Description	Section for gateway’s asr routing (calculated as the step size) (VOS3000 2.1.9.07 manual §4.3.5.2, page 235)
🔧 Default Value	10
📊 Value Range	5–24
📋 Effect	Divides the RESERVE_TIME window into sections for granular ASR tracking

💡 How RESERVE_SEPARATE works with RESERVE_TIME: The RESERVE_SEPARATE value divides the measurement window into equal sections. With RESERVE_TIME = 600 and RESERVE_SEPARATE = 10, the 600-second window is divided into 10 sections of 60 seconds each. VOS3000 tracks call attempts and completions in each section independently. As the window slides forward, the oldest section is dropped and a new section is added. This section-based approach provides both recent and historical data within the VOS3000 real-time gateway ASR measurement window, allowing VOS3000 to compute a weighted ASR that reflects recent quality trends more accurately than a simple total ratio. With RESERVE_SEPARATE = 5 and RESERVE_TIME = 600, each VOS3000 real-time gateway ASR section is 120 seconds, providing coarser granularity but requiring less memory.

📊 RESERVE_TIME and RESERVE_SEPARATE Configuration Examples

🔧 Choosing the right combination of RESERVE_TIME and RESERVE_SEPARATE depends on your traffic volume and how quickly you need to detect quality changes:

Scenario	RESERVE_TIME	RESERVE_SEPARATE	Section Size	Reasoning
🏢 High-volume wholesale	600 (10 min)	10	60 seconds	Fast detection, enough calls per section for statistical significance
📞 Medium-volume retail	1800 (30 min)	12	150 seconds	Longer window for more data, moderate granularity
🌍 Low-volume international	3600 (1 hour)	6	600 seconds	Long window accumulates enough calls, coarse granularity
🔧 Lab / testing	300 (5 min)	5	60 seconds	Shortest window for fastest feedback during testing

🔄 Per-Gateway ASR Configuration

🔧 Each routing gateway can override the system-level VOS3000 real-time gateway ASR setting. The per-gateway “Real time computing asr” option in the routing gateway’s Additional settings panel allows you to enable VOS3000 real-time gateway ASR calculation for specific gateways while leaving it disabled for others. The default setting for each gateway inherits the system parameter SS_GATEWAY_ASR_CALCULATE.

Per-Gateway Setting	Effect	When to Use
Default	Inherits SS_GATEWAY_ASR_CALCULATE system parameter	📊 Most gateways — consistent system-wide behavior
On	Always calculate ASR for this gateway, regardless of system setting	📡 Critical gateways that need quality monitoring even when system ASR is Off
Off	Never calculate ASR for this gateway, regardless of system setting	🧪 Test gateways or low-volume routes where ASR data would be unreliable

💡 Routing sort behavior: When the VOS3000 real-time gateway ASR is enabled for a gateway, its calculated ASR value feeds into the gateway sorting algorithm. Gateways with VOS3000 real-time gateway ASR calculation disabled are sorted before those with ASR enabled in the routing priority, as documented in the routing gateway sorting section of the VOS3000 manual §4.3.3. This means that if you enable ASR for only some gateways, the gateways without ASR data will be tried first (since their quality is unknown), and the ASR-enabled gateways will be sorted by their calculated quality. For more on routing sort configuration, see our ASR ACD analysis guide.

📊 ASR Calculation and Routing Quality Monitoring

📈 The primary purpose of the VOS3000 real-time gateway ASR system is to provide data for quality-based routing decisions. When VOS3000 real-time gateway ASR calculation is enabled, the routing engine can sort gateways by their actual performance rather than relying solely on static priority settings or cost-based ordering. This creates a feedback loop where high-performing gateways receive more traffic and underperforming gateways are automatically deprioritized.

Monitoring Use Case	How Real-Time ASR Helps	Action Threshold
📡 Gateway degradation detection	ASR drops below normal range for a gateway	ASR drops 20%+ below gateway’s historical average
🔄 Carrier quality comparison	Compare ASR across gateways serving same destination	Re-route traffic from low-ASR to high-ASR gateways
🚨 Outage early warning	ASR drops to near 0% indicating total gateway failure	Immediate — trigger alarm and remove from routing
📊 SLA compliance monitoring	Verify gateway ASR meets contracted SLA targets	ASR below SLA threshold for 2+ consecutive windows

📊 Alarm integration: You can configure VOS3000 routing alarms that trigger when a gateway’s ASR drops below a configured threshold. The VOS3000 real-time gateway ASR alarm system provides proactive monitoring that alerts operators to quality degradation before it significantly impacts callers. Set up ASR alarms in “Navigation > Alarm management > Routing alarm” with appropriate thresholds for your deployment. For alarm configuration details, see our monitoring alarms and statistics guide.

🛡️ Common Real-Time ASR Problems and Solutions

❌ Problem 1: ASR Values Are Unstable or Noisy

🔍 Symptom: the VOS3000 real-time gateway ASR values fluctuate wildly between measurement periods, making it difficult to distinguish real quality changes from statistical noise in the VOS3000 real-time gateway ASR data.

💡 Cause: The RESERVE_TIME window is too short or the traffic volume per section is too low, resulting in insufficient call samples for statistically significant VOS3000 real-time gateway ASR calculation.

✅ Solutions:

🔧 Increase SS_GATEWAY_ASR_RESERVE_TIME to 1800 or 3600 seconds for longer measurement window
📊 Reduce SS_GATEWAY_ASR_RESERVE_SEPARATE to 5 or 6 for larger section sizes with more calls per section
📋 Ensure only high-volume gateways have VOS3000 real-time gateway ASR calculation enabled — low-volume routes produce unreliable VOS3000 real-time gateway ASR data

❌ Problem 2: ASR Calculation Not Affecting Routing

🔍 Symptom: Real-time VOS3000 real-time gateway ASR is enabled and showing values, but the routing selection does not appear to be influenced by the calculated VOS3000 real-time gateway ASR.

💡 Cause: The SS_GATEWAY_ASR_ROUTE_SORT_CONFIG parameter is not configured to sort by ASR. Even when VOS3000 real-time gateway ASR is calculated, it only affects routing if the sort configuration tells the routing engine to consider VOS3000 real-time gateway ASR in the gateway ordering. By default, the sort position is “Before line usage,” which does include ASR, but other configurations may deprioritize it.

✅ Solutions:

🔧 Verify SS_GATEWAY_ASR_ROUTE_SORT_CONFIG is set to an appropriate position in the sort order
📊 Check that the gateways have “Real time computing asr” enabled (not just the system parameter)
📋 Review the routing optimization configuration for any overrides that bypass ASR-based sorting

❌ Problem 3: High Memory Usage with Many ASR-Enabled Gateways

🔍 Symptom: System memory usage increases after enabling real-time ASR calculation for many gateways, especially with high RESERVE_SEPARATE values.

💡 Cause: Each ASR-enabled gateway requires memory to track call attempts and completions per section. With RESERVE_SEPARATE = 24 and many gateways, the memory footprint can be significant.

✅ Solutions:

🔧 Enable ASR calculation only for gateways where quality monitoring is needed — disable for test and low-volume gateways
📊 Reduce RESERVE_SEPARATE to 10 (default) or lower to decrease per-gateway memory usage
📋 Monitor system resources and adjust capacity planning accordingly

💡 Real-Time Gateway ASR Best Practices

🎯 Follow these best practices for effective VOS3000 real-time gateway ASR deployment. The VOS3000 real-time gateway ASR system delivers the most value when properly configured:

Best Practice	Recommendation	Reason
📊 Enable for all production gateways	Set SS_GATEWAY_ASR_CALCULATE = On system-wide	🔧 Provides complete visibility into gateway quality
⏱️ Match RESERVE_TIME to traffic volume	600s for high-volume, 1800s+ for low-volume	📊 Ensures statistical significance per section
🔢 Keep RESERVE_SEPARATE at default 10	Only increase if you need finer granularity	📋 Balance between granularity and memory/resource usage
🚨 Set ASR alarms	Configure routing alarms for ASR threshold breaches	📡 Proactive detection of gateway quality degradation
📋 Pair with ACD calculation	Also enable SS_GATEWAY_ACD_CALCULATE for complete quality picture	📊 ASR + ACD together provide full quality assessment

❓ Frequently Asked Questions

❓ What is the default value of SS_GATEWAY_ASR_CALCULATE?

🔧 The default value is Off, as documented in the VOS3000 2.1.9.07 manual §4.3.5.2 (page 235). This means that by default, VOS3000 does not calculate real-time ASR for gateways. The Off default is the conservative choice that minimizes system resource usage. However, for production deployments that want data-driven routing quality monitoring, it is strongly recommended to enable ASR calculation. The resource overhead is modest for most deployments, and the quality visibility it provides is invaluable for maintaining high call completion rates.

❓ What is the difference between RESERVE_TIME and RESERVE_SEPARATE?

📊 SS_GATEWAY_ASR_RESERVE_TIME defines the total measurement window in seconds (default 600, range 300–86400). This is how far back in time VOS3000 looks when calculating ASR. SS_GATEWAY_ASR_RESERVE_SEPARATE defines how many sections the measurement window is divided into (default 10, range 5–24). The section size is RESERVE_TIME divided by RESERVE_SEPARATE. For example, RESERVE_TIME = 600 with RESERVE_SEPARATE = 10 gives 10 sections of 60 seconds each. The section-based approach provides a sliding window where the oldest section is progressively aged out, making the ASR calculation more responsive to recent quality changes than a simple cumulative ratio over the entire window.

❓ Does enabling ASR calculation affect system performance?

⚡ Enabling the VOS3000 real-time gateway ASR system does introduce some overhead, as the softswitch must track call attempts and completions per section for each VOS3000 real-time gateway ASR-enabled gateway. The memory usage scales with the number of ASR-enabled gateways multiplied by RESERVE_SEPARATE. For a typical deployment with 50 ASR-enabled gateways and RESERVE_SEPARATE = 10, the overhead is minimal and well within the capacity of a production VOS3000 server. However, if you enable ASR for hundreds of gateways with high RESERVE_SEPARATE values, you should monitor system memory and CPU to ensure the overhead remains acceptable. the default values (RESERVE_TIME = 600, RESERVE_SEPARATE = 10) are optimized for minimal overhead with adequate VOS3000 real-time gateway ASR quality data.

❓ How does ASR calculation interact with the routing sort order?

🔄 When a gateway has VOS3000 real-time gateway ASR enabled and the routing engine is sorting gateways for a call, the SS_GATEWAY_ASR_ROUTE_SORT_CONFIG parameter determines where ASR-based sorting occurs in the priority chain. If ASR_ROUTE_SORT_CONFIG is set to “Before line usage,” gateways are sorted by ASR quality before considering line utilization. Gateways with ASR calculation disabled are sorted before ASR-enabled gateways (since their quality is unknown). This means that enabling ASR calculation for some but not all gateways can actually change the routing priority order in ways you might not expect. For the most predictable behavior, enable ASR calculation for all production gateways consistently. For more on sort configuration, see our routing optimization guide.

❓ Can I calculate ASR per prefix or destination instead of per gateway?

📋 The VOS3000 real-time gateway ASR system calculates ASR at the gateway level, not per individual prefix or destination. However, the VOS3000 real-time gateway ASR RESERVE_SEPARATE parameter does provide some granularity by dividing the measurement window into sections, which helps track quality trends over time within the window. If you need per-destination or per-prefix ASR analysis, you should use the CDR data and external reporting tools to calculate ASR by destination after the fact. The VOS3000 data report module can generate ASR reports by various dimensions using historical CDR data, which complements the real-time per-gateway ASR calculation provided by the system parameters.

❓ How quickly does ASR respond to a gateway failure?

📡 The response time depends on the RESERVE_TIME and RESERVE_SEPARATE settings. With the default values (RESERVE_TIME = 600 seconds, RESERVE_SEPARATE = 10), the section size is 60 seconds. When a gateway fails completely, its ASR starts dropping within the first 60-second section, and the calculated ASR reflects the failure progressively as more sections contain zero completions. Within 2–3 sections (120–180 seconds), the calculated ASR will be significantly depressed, causing the routing engine to deprioritize the failing gateway. For faster detection, you can reduce RESERVE_TIME to 300 seconds, which provides noticeable ASR degradation within 60–90 seconds of a complete gateway failure.

📞 Need Expert Help with VOS3000 Real-Time Gateway ASR?

🔧 Implementing VOS3000 real-time gateway ASR monitoring transforms your routing from static configuration to dynamic, data-driven decision making. The VOS3000 real-time gateway ASR system is essential for operators who want to maximize call quality. Whether you are enabling ASR calculation for the first time, tuning RESERVE_TIME and RESERVE_SEPARATE for your traffic volume, or integrating ASR data with routing sort configuration, expert guidance ensures your VOS3000 system maximizes call quality and minimizes wasted routing attempts. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 real-time gateway ASR configuration, VOS3000 real-time gateway ASR tuning, routing quality optimization, and alarm setup. Our team specializes in VOS3000 ASR/ACD analysis, quality-based routing, and carrier-grade VoIP performance tuning. 🔧

🔗 Explore related VOS3000 ASR and routing quality guides:

VOS3000 ASR ACD Analysis — Complete ASR and ACD monitoring methodology
VOS3000 Routing Optimization — Quality and cost-based routing configuration
VOS3000 Gateway Analysis Reports — Analyzing gateway performance data
VOS3000 Monitoring Alarms Statistics — Setting up quality-based alarms
VOS3000 LCR Least Cost Routing — Cost-based routing configuration
VOS3000 System Parameters — Complete system parameter reference

📞 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

VOS3000 Busy Stop Switch Reliable SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY

April 26, 2026April 26, 2026 king

VOS3000 Busy Stop Switch Reliable SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY

🚫 When a SIP 486 Busy Here response arrives from a gateway in VOS3000, it signals that the called party is genuinely occupied — not that the gateway failed, the route was unreachable, or the call setup timed out. The called person is on another call, and no amount of trying alternative gateways will change that fact. Yet without the VOS3000 busy stop switch parameter, SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY, the softswitch might continue switching to other gateways after receiving a busy signal, wasting system resources, inflating CPS load, and generating unnecessary failed CDR records for a call that was never going to complete. 🔧

⚙️ By default, SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY is set to On, which means VOS3000 stops switching gateways immediately when it receives a busy signal (SIP 486 Busy Here or H.323 Release Complete with busy cause code). This is the correct and recommended setting for virtually all deployments because a busy signal indicates a genuine user-level condition, not a network or gateway problem. When the VOS3000 busy stop switch is Off, the softswitch ignores the busy signal and continues trying other gateways, which is wasteful because the called party is busy regardless of which gateway delivers the call. This parameter is independent of the SS_GATEWAY_SWITCH_UNTIL_CONNECT setting — even when aggressive failover mode is enabled, a busy signal still stops the switching process. 📊

🎯 This guide provides a complete, manual-verified reference for the SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY parameter. All parameter definitions are sourced from the official VOS3000 2.1.9.07 English manual §4.3.5.2 (page 236) and the gateway operation documentation, with detailed explanations of why busy stop switching is essential, how it saves resources, and when you might consider the rare scenario of disabling it. 📘

🔐 What Is the VOS3000 Busy Stop Switch?

📋 The VOS3000 busy stop switch mechanism is controlled by the system parameter SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY, documented in the VOS3000 manual §4.3.5.2 (page 236) as “Callee busy stop switch.” The parameter determines whether VOS3000 should stop attempting gateway failover when a busy signal is received from the called party through a gateway.

💡 Key characteristics of SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY:

🔧 Default value: On — busy stop switch is enabled by default, which is the recommended setting
📍 Configuration location: Operation management > Softswitch management > Additional settings > System parameter
🔄 Per-gateway override: Yes — can be set per routing gateway in “Additional settings > Callee busy stop switch”
📡 Trigger signal: SIP 486 Busy Here or H.323 Release Complete with user-busy cause code
🛡️ Independence: NOT affected by SS_GATEWAY_SWITCH_UNTIL_CONNECT — busy stop overrides aggressive mode
📋 Also configurable per-gateway: Routing gateway > Additional settings > Callee busy stop switch

📍 The critical distinction: A busy signal (486) is fundamentally different from other call failure reasons. A timeout (408) means the gateway or destination did not respond — trying another gateway makes sense. A service unavailable (503) means the gateway itself has a problem — trying another gateway makes sense. But a busy signal (486) means the called person is on another call — trying another gateway will not change the user’s busy status, because the busy condition exists at the endpoint, not at the gateway level. The VOS3000 busy stop switch recognizes this distinction and prevents wasteful switching after a genuine busy condition. Understanding this distinction is fundamental to VOS3000 busy stop switch configuration.

📊 Why Continuing to Switch After Busy Wastes Resources

💰 When the VOS3000 busy stop switch is disabled (Off), the softswitch treats a busy signal as just another failure reason and continues trying other gateways. This creates a cascade of wasteful activity for every busy call under the VOS3000 busy stop switch Off configuration, as illustrated in the following analysis:

Resource Wasted	With Busy Stop Off	With Busy Stop On
📊 Additional SIP INVITE attempts	N-1 extra INVITEs (N = available gateways)	0 — stops immediately on busy
🔄 CPS load per busy call	Multiplied by number of gateways tried	1 attempt only — minimal CPS impact
📋 CDR records generated	1 per gateway attempt — all with 486 result	1 CDR — clean and accurate
💾 Database load	N× CDR inserts per busy call	1 CDR insert per busy call
⏱️ Processing time	Multiple seconds per additional gateway	Immediate — no wasted processing

🚨 CPS inflation analysis: Consider a deployment with 5 routing gateways where 20% of calls receive a busy response. With the VOS3000 busy stop switch Off, every busy call generates up to 4 additional INVITE attempts (trying the remaining 4 gateways). At 100 calls per second with 20% busy rate, that is 20 busy calls × 4 extra INVITEs = 80 additional CPS load, on top of the normal 100 CPS. This 80% overhead is entirely wasted because none of those additional attempts will succeed — the called party is busy regardless of the gateway. Enabling busy stop switch eliminates this wasted CPS entirely. For CPS capacity planning, see our capacity planning guide.

📋 SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY
📝 Manual Description	Callee busy stop switch (VOS3000 2.1.9.07 manual §4.3.5.2, page 236)
🔧 Default Value	On
📍 Configuration Path	Operation management > Softswitch management > Additional settings > System parameter
🔄 Per-Gateway Override	Yes — Routing gateway > Additional settings > Callee busy stop switch
📡 Trigger Signal (SIP)	486 Busy Here
📡 Trigger Signal (H.323)	Release Complete with user-busy cause code (17)
🛡️ Independence	NOT affected by SS_GATEWAY_SWITCH_UNTIL_CONNECT — overrides aggressive mode

🔄 Busy Stop Switch and Aggressive Failover Independence

🔗 One of the most important characteristics of the VOS3000 busy stop switch is its independence from the aggressive failover mode (SS_GATEWAY_SWITCH_UNTIL_CONNECT). The VOS3000 busy stop switch always takes priority over aggressive mode. The VOS3000 manual explicitly documents this independence: “This option is NOT affected by ‘Switch gateway until connect’. When ‘Switch gateway until connect’ is on, if received busy signal, stop switch gateway.”

SWITCH_UNTIL_CONNECT	STOP_AFTER_USER_BUSY	Behavior on 486 Busy
Off	On	✅ Stops switching — standard mode with busy protection
On	On	✅ Stops switching — busy stop overrides aggressive mode
Off	Off	⚠️ Continues switching — wastes resources on busy calls
On	Off	🔴 Continues switching aggressively — maximum waste on busy calls

💡 Recommended configuration: Always keep SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY = On, regardless of your SWITCH_UNTIL_CONNECT setting. The only exception is the extremely rare scenario where different gateways serve different endpoints with the same phone number (such as in a multi-site PBX with shared extensions), and a busy response from one site does not necessarily mean the extension is busy at all sites. Even in this case, the resource waste from continued switching should be carefully weighed against the potential benefit. For more on failover configuration, see our vendor failover setup guide.

📊 Busy Stop Switch and CDR Recording Impact

📋 The VOS3000 busy stop switch directly affects the number and quality of CDR records generated for busy calls. When the VOS3000 busy stop switch is enabled, a single clean CDR is generated with the busy end reason. When disabled, multiple CDR records may be created — one for each gateway that returns a busy response.

CDR Aspect	Busy Stop On	Busy Stop Off
📊 CDR records per busy call	1 — clean single record	N — one per gateway attempted
📝 Call end reason accuracy	486 Busy — accurate and clear	Multiple 486 records — confusing for analysis
💾 Database storage impact	Minimal — 1 record per busy call	Inflated — N× records per busy call
📊 Reporting accuracy	Accurate busy call count	Inflated call count — each busy appears as N calls

📊 Reporting impact: When the VOS3000 busy stop switch is Off, your CDR reports will show inflated call counts because each busy call generates multiple CDR records. A 486 Busy response from 4 different gateways looks like 4 separate failed calls in the CDR data, even though it was a single call attempt to a single busy endpoint. This distorts your ASR calculation, inflates your failure rate, and makes it difficult to determine the true number of busy calls versus actual call failures. The VOS3000 busy stop switch prevents this distortion and ensures accurate ASR calculations. For CDR analysis best practices, see our CDR analysis and billing guide.

📋 Busy Signal vs Other Failure Responses

🔍 Understanding why the VOS3000 busy stop switch treats 486 Busy differently from other failure responses requires a clear understanding of what each response means and whether trying another gateway could potentially succeed:

SIP Response	Meaning	Can Another Gateway Help?	Busy Stop Applies?
486 Busy Here	Called party is on another call	❌ No — user is busy regardless of gateway	✅ Yes — stops switching
408 Request Timeout	Gateway or destination did not respond	✅ Yes — different gateway may reach the destination	❌ No — not a busy condition
503 Service Unavailable	Gateway cannot process the call	✅ Yes — another gateway may be operational	❌ No — not a busy condition
480 Temporarily Unavailable	Destination temporarily unreachable	✅ Possibly — different route may work	❌ No — not a busy condition
487 Request Terminated	Call was cancelled or timed out	✅ Yes — may succeed on retry	❌ No — not a busy condition

💡 Key takeaway: The VOS3000 busy stop switch only applies to the 486 Busy response (and its H.323 equivalent). This selective VOS3000 busy stop switch behavior is what makes the parameter so valuable — it prevents wasteful switching only in the one scenario where switching cannot possibly help, while allowing normal failover for all other failure types. For a complete reference of SIP response codes in VOS3000, see our SIP response codes guide.

🛡️ Common Busy Stop Switch Problems and Solutions

❌ Problem 1: Excessive Failed CDR Records for Busy Calls

🔍 Symptom: CDR records show multiple failed call attempts with 486 Busy result for what should be a single busy call, inflating the total call count and distorting ASR calculations.

💡 Cause: SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY is set to Off, allowing VOS3000 to continue trying other gateways after receiving a 486 Busy response.

✅ Solutions:

🔧 Set SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY to On
📊 Clean up historical CDR data by filtering for duplicate busy records per call session
📋 Verify the per-gateway “Callee busy stop switch” setting is also set to Default or On

❌ Problem 2: Unusual CPS Spikes During Peak Hours

🔍 Symptom: CPS load on the VOS3000 softswitch increases disproportionately during peak hours, even though the actual call volume has not increased that much.

💡 Cause: With busy stop switch disabled, the higher busy rate during peak hours (more people on calls) multiplies the CPS load because each busy call triggers additional gateway attempts. A 30% busy rate with 5 gateways means 30% of calls generate 4× extra INVITE traffic.

✅ Solutions:

🔧 Enable the VOS3000 busy stop switch immediately to eliminate wasted CPS
📊 Monitor CPS before and after the VOS3000 busy stop switch change to quantify the improvement
📋 Review your CPS control settings to ensure proper capacity management

❌ Problem 3: Distorted ASR Due to Multiple Busy Records

🔍 Symptom: Your ASR appears artificially low because CDR reports count each gateway attempt as a separate call. A single busy call that tried 4 gateways counts as 4 failed calls in the ASR calculation.

💡 Cause: Without the busy stop switch, each gateway attempt generates its own CDR. When calculating ASR, the system counts all these records, making it appear that you have many more failed calls than you actually do.

✅ Solutions:

🔧 Enable SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY = On to generate only one CDR per busy call under the VOS3000 busy stop switch
📊 Adjust your ASR reporting to deduplicate CDR records by call session ID if you cannot change the parameter immediately
📋 Review your call end reasons analysis to identify the true busy call rate

💡 VOS3000 Busy Stop Switch Best Practices

🎯 Follow these best practices for optimal busy stop switch configuration:

Best Practice	Recommendation	Reason
🔒 Always enable in production	SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY = On	🛡️ Prevents wasteful switching on genuine busy signals
📊 Monitor busy call rate	Track percentage of 486 responses in CDR	📈 High busy rate may indicate capacity issues downstream
🔄 Pair with RTP lock-in	SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START = On	📡 Two independent stop conditions provide layered protection
📋 Set switch limit as safety net	SS_GATEWAY_SWITCH_LIMIT = 3–4	🔧 Caps total attempts even if busy stop fails
🚫 Never disable without justification	Only disable if you have a documented multi-site PBX use case	📊 Disabling wastes resources and distorts reporting

❓ Frequently Asked Questions

❓ What is the default value of SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY?

🔧 The default value is On, as documented in the VOS3000 2.1.9.07 manual §4.3.5.2 (page 236). This means that by default, VOS3000 stops switching gateways when a busy signal is received. The default of On reflects the correct design principle that a busy signal from the called party is a user-level condition that cannot be resolved by trying a different gateway. Leaving this parameter at its default value is strongly recommended for all production deployments.

❓ Does the busy stop switch apply to H.323 calls?

📡 Yes, the VOS3000 busy stop switch applies to both SIP and H.323 calls. For SIP calls, the VOS3000 busy stop switch trigger is a 486 Busy Here response. For H.323 calls, the VOS3000 busy stop switch trigger is a Release Complete message with Q.850 cause code 17 (user busy). The behavior is the same regardless of protocol: when a busy signal is received and the VOS3000 busy stop switch is enabled, VOS3000 stops trying additional gateways. This consistent behavior across protocols ensures that your failover strategy works correctly regardless of which signaling protocol your gateways use.

❓ What happens if both busy stop and aggressive mode are enabled?

🔄 The busy stop switch takes priority over aggressive mode. The VOS3000 manual explicitly states: “This option is NOT affected by ‘Switch gateway until connect’. When ‘Switch gateway until connect’ is on, if received busy signal, stop switch gateway.” This means that even with aggressive failover enabled (SWITCH_UNTIL_CONNECT = On), a busy signal stops the switching process immediately. The VOS3000 busy stop switch overrides aggressive mode in all cases. The aggressive mode will continue trying gateways for other failure reasons (timeouts, 503 errors, etc.), but it will not continue after a 486 Busy response. This is the correct and expected behavior — the VOS3000 busy stop switch should never be overridden by aggressive mode.

❓ When would I ever disable the busy stop switch?

⚠️ The only scenario where disabling the VOS3000 busy stop switch might be considered is when you have a multi-site PBX deployment where the same extension number exists at different physical locations, and each location is served by a different gateway. In this case, a busy response from one site’s gateway does not necessarily mean the extension is busy at all sites — the same extension at another location might be available. However, this is an extremely rare deployment scenario, and even in this case, the resource waste from continued switching should be carefully weighed against the potential benefit. For 99% of VOS3000 deployments, the busy stop switch should remain enabled. For help with multi-site configurations, contact us via WhatsApp.

❓ Does the busy stop switch affect calls that receive 480 Temporarily Unavailable?

📋 No, the VOS3000 busy stop switch only applies to 486 Busy Here responses (and the H.323 equivalent). A 480 Temporarily Unavailable response is treated as a normal failure condition that triggers standard failover behavior — VOS3000 will try the next available gateway. The 480 response indicates a temporary condition (such as the destination being unregistered or a Do Not Disturb setting), which could potentially be resolved through a different gateway or route. The busy stop switch is specifically designed for the 486 response because a busy condition at the endpoint cannot be resolved by trying a different gateway. The VOS3000 busy stop switch ensures resources are not wasted on impossible completions.

❓ How do I verify the busy stop switch is working correctly?

📊 To verify the VOS3000 busy stop switch is working, call a number that you know will return a 486 Busy response (call a mobile phone that is currently on another call). Check the CDR for that call — there should be exactly one CDR record with a busy end reason, not multiple records from different gateways. If you see multiple CDR records with 486 Busy result for the same call, the VOS3000 busy stop switch is not working correctly. Verify that SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY is set to On in system parameters and that the per-gateway “Callee busy stop switch” is not set to Off for the gateways involved. For CDR verification methods, see our CDR analysis guide.

📞 Need Expert Help with VOS3000 Busy Stop Switch?

🔧 Proper configuration of the VOS3000 busy stop switch is essential for efficient resource utilization, accurate CDR reporting, and correct ASR calculation. The VOS3000 busy stop switch is one of the most impactful failover parameters for operational efficiency. Whether you are troubleshooting inflated CPS load, cleaning up duplicate CDR records, or optimizing your failover strategy, expert guidance ensures your VOS3000 system operates efficiently and your billing data is accurate. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 busy stop switch configuration, failover optimization, and CDR analysis. Our VOS3000 busy stop switch experts specialize in VOS3000 system tuning, resource optimization, and carrier-grade VoIP deployment. 🔧

🔗 Explore related VOS3000 failover and system configuration guides:

VOS3000 Vendor Failover Setup — Complete guide to configuring gateway failover
VOS3000 SIP Response Codes — Complete reference of SIP response codes in CDR
VOS3000 Call End Reasons — Understanding call termination reasons
VOS3000 CDR Analysis and Billing — Analyzing CDR data for revenue optimization
VOS3000 Gateway Config FAQ — Common gateway configuration questions
VOS3000 System Parameters — Complete system parameter reference

📞 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

VOS3000 Aggressive Gateway Failover Dynamic SS_GATEWAY_SWITCH_UNTIL_CONNECT

April 26, 2026April 26, 2026 king

VOS3000 Aggressive Gateway Failover Dynamic SS_GATEWAY_SWITCH_UNTIL_CONNECT

🔄 In normal failover mode, VOS3000 stops trying additional gateways when it encounters certain conditions — the call is ringing, a busy signal is received, or protocol-level stop conditions are met. But what if you want the softswitch to keep trying every available gateway until one actually connects the call? That is exactly what VOS3000 aggressive gateway failover mode does. Enabled by the SS_GATEWAY_SWITCH_UNTIL_CONNECT parameter, this mode instructs VOS3000 to continue switching gateways until it receives a connect signal (SIP 200 OK or H.323 Connect), maximizing the chance of call completion at the potential cost of longer post-dial delay. 🔧

⚙️ By default, SS_GATEWAY_SWITCH_UNTIL_CONNECT is set to Off, which means VOS3000 uses the standard failover behavior: it stops switching when the call reaches ringing state, receives a busy signal, encounters a no-answer condition, or meets protocol-level stop conditions. When you enable the VOS3000 aggressive gateway failover mode by setting this parameter to On, the softswitch overrides several of these stop conditions and keeps trying gateways until one returns a connect signal. The key difference is that in aggressive mode, even if a gateway returns a 180 Ringing response, VOS3000 may continue trying other gateways if the ringing times out without a 200 OK answer. 📊

🎯 This guide provides a complete, manual-verified reference for the SS_GATEWAY_SWITCH_UNTIL_CONNECT parameter. All parameter definitions are sourced from the official VOS3000 2.1.9.07 English manual §4.3.5.2 (page 236) and the gateway operation documentation, with detailed explanations of how the VOS3000 aggressive gateway failover works, when it improves ASR, when it hurts PDD, and how the VOS3000 aggressive gateway failover differs from the switch limit parameter. 📘

🔐 What Is VOS3000 Aggressive Gateway Failover?

📋 The VOS3000 aggressive gateway failover mode is controlled by the system parameter SS_GATEWAY_SWITCH_UNTIL_CONNECT, documented in the VOS3000 manual §4.3.5.2 (page 236) as “Switch Gateway Until Connect.” When enabled, this parameter changes the failover behavior from the standard conservative mode to an aggressive mode that continues attempting gateways until a connect signal is received.

💡 Key characteristics of SS_GATEWAY_SWITCH_UNTIL_CONNECT:

🔧 Default value: Off — standard failover behavior applies by default
📍 Configuration location: Operation management > Softswitch management > Additional settings > System parameter
🔄 Per-gateway override: Yes — can be set per routing gateway in “Additional settings > Switch gateway until connect”
📡 Protocol support: Affects both SIP (200 OK) and H.323 (Connect) connect signals
🛡️ Override priority: Priors to protocol-level stop conditions (Stop switch after OLC, Stop switch after SDP)
📋 Limits still apply: SS_GATEWAY_SWITCH_LIMIT, RTP lock-in, and busy stop override aggressive mode

📊 Aggressive Mode vs Standard Mode Comparison

🔄 Understanding the behavioral difference between aggressive and standard failover modes is essential for making the right VOS3000 aggressive gateway failover configuration decision. The following table compares the two modes across all key failover conditions:

Failover Condition	Standard Mode (Off)	Aggressive Mode (On)
📞 180 Ringing received	Stops switching — call is ringing at destination	Continues switching until connect or timeout
🚫 486 Busy received	Stops switching — user is busy	Stops switching — busy stop overrides aggressive mode
📡 RTP media starts flowing	Stops switching — audio path established	Stops switching — RTP lock-in overrides aggressive mode
⏱️ INVITE timeout (no response)	Tries next gateway	Tries next gateway (same behavior)
📞 200 OK / Connect received	Stops switching — call connected	Stops switching — call connected (same behavior)
🔄 Switch limit reached	Stops switching — limit cap applies	Stops switching — limit cap still applies

💡 Key insight: The primary difference between standard and aggressive mode is how each handles the ringing state. In standard mode, once VOS3000 receives a 180 Ringing response from a gateway, it stops switching because the call appears to be progressing. In aggressive mode, VOS3000 does not consider ringing as a stop condition — it keeps trying other gateways until one actually connects with a 200 OK. This is the core behavioral change that the VOS3000 aggressive gateway failover mode introduces. For operators considering the VOS3000 aggressive gateway failover option, this ringing-state behavior is the key differentiator. For more on SIP call flow states, see our SIP call flow guide.

📋 SS_GATEWAY_SWITCH_UNTIL_CONNECT Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_SWITCH_UNTIL_CONNECT
📝 Manual Description	Switch Gateway Until Connect (VOS3000 2.1.9.07 manual §4.3.5.2, page 236)
🔧 Default Value	Off
📍 Configuration Path	Operation management > Softswitch management > Additional settings > System parameter
🔄 Per-Gateway Override	Yes — Routing gateway > Additional settings > Switch gateway until connect
📡 Connect Signal (SIP)	200 OK
📡 Connect Signal (H.323)	Connect
🛡️ Override Priority	Priors to Protocol > Stop switch after OLC and Stop switch after receive SDP

🔄 How Aggressive Failover Differs from Switch Limit

📊 A common point of confusion is the relationship between the VOS3000 aggressive gateway failover mode (SS_GATEWAY_SWITCH_UNTIL_CONNECT) and the gateway switch limit (SS_GATEWAY_SWITCH_LIMIT). The VOS3000 aggressive gateway failover and switch limit are two independent parameters that control different aspects of VOS3000 aggressive gateway failover behavior, and they work together rather than replacing each other.

Aspect	SWITCH_UNTIL_CONNECT	SWITCH_LIMIT
📋 Purpose	Defines when to stop switching (only on connect)	Defines how many switch attempts are allowed
🔧 Default	Off (standard mode)	None (unlimited attempts)
📊 Effect on ASR	Increases ASR by trying more gateways	May decrease ASR if set too low
⏱️ Effect on PDD	Increases PDD by extending switching window	Decreases PDD by capping attempts
🔄 Interaction	Aggressive mode still respects switch limit cap	Switch limit caps total attempts regardless of mode

💡 Recommended combination: For production deployments, the recommended configuration is SS_GATEWAY_SWITCH_UNTIL_CONNECT = On (aggressive mode) combined with SS_GATEWAY_SWITCH_LIMIT = 3–4 (sensible cap). This gives you the best of both worlds: aggressive failover that keeps trying until a connect signal is received, but with a safety cap that prevents runaway switching if all gateways are having problems. Without the switch limit, the VOS3000 aggressive gateway failover mode could try every gateway in your routing table, creating unacceptably long PDD. For more on the switch limit parameter, see our routing optimization guide.

📊 When Aggressive Mode Improves ASR

📈 The VOS3000 aggressive gateway failover mode can significantly improve your Answer-Seizure Ratio in scenarios where gateways frequently return ringing responses but never complete the call. The VOS3000 aggressive gateway failover is particularly valuable in these deployment scenarios where aggressive mode provides the most ASR benefit:

Scenario	Why Aggressive Helps	Expected ASR Gain
🔄 Unreliable downstream carriers	Carriers that ring but never answer get bypassed	5–15% ASR improvement
📞 Multiple termination providers	Fastest-connecting provider wins the call	3–10% ASR improvement
🌍 International routes with variable quality	Routes that ring without answer are quickly skipped	10–20% ASR improvement
🔧 New untested gateway routes	Unknown quality routes are tried with fallback ready	Variable — depends on route quality

📊 ASR measurement tip: Before and after enabling VOS3000 aggressive gateway failover, measure your ASR over the same time period and traffic volume to quantify the improvement. Use the ASR ACD analysis tools in VOS3000 to track the metric. Pay attention to ASR by destination and by gateway, as aggressive mode may improve ASR for some routes while having no effect on others. Also monitor PDD alongside ASR — the goal is to find the sweet spot where ASR gains outweigh PDD costs.

⏱️ When Aggressive Mode Hurts PDD

🚨 While the VOS3000 aggressive gateway failover mode can improve ASR, it comes with a PDD cost that must be managed. Every additional gateway switch attempt under the VOS3000 aggressive gateway failover mode adds signaling delay before the call connects. In scenarios where the first gateway would have connected the call (just with a slightly longer ring time), aggressive mode wastes time by trying additional gateways unnecessarily.

Scenario	Why Aggressive Hurts	PDD Impact
📞 Reliable gateways with slow answer	Gateway would have connected — aggressive mode wastes time on alternates	🔴 +5–15 seconds unnecessary delay
🏢 Retail callers expecting fast connection	Retail users are PDD-sensitive and may hang up	🔴 Caller abandonment increases
💳 Calling card services	Card users hear silence during switching attempts	🔴 Card user frustration and perceived service failure
📊 High-volume traffic periods	Aggressive switching increases CPS load during peak	🔴 System overload potential

💡 Mitigation strategy: Always pair the VOS3000 aggressive gateway failover mode with a reasonable SS_GATEWAY_SWITCH_LIMIT and appropriate SIP timeout settings. The combination of VOS3000 aggressive gateway failover mode + switch limit gives you the ASR benefit while bounding the PDD cost. Additionally, use per-gateway configuration to enable aggressive mode only on the gateways and routes where it provides measurable ASR improvement, rather than enabling it system-wide. For more on PDD optimization, see our SIP call progress timeout guide.

🛡️ Common Aggressive Failover Problems and Solutions

❌ Problem 1: Increased PDD Without ASR Improvement

🔍 Symptom: After enabling SS_GATEWAY_SWITCH_UNTIL_CONNECT, PDD increases significantly but ASR does not improve, suggesting the aggressive switching is not finding additional connected calls.

💡 Cause: The gateways in the routing pool are all similarly reliable (or all similarly unreliable). Aggressive switching only helps when some gateways connect while others ring without answer. If all gateways behave the same way, switching between them just adds delay without benefit.

✅ Solutions:

📊 Analyze CDR data by gateway to identify which gateways connect and which ring without answer
🔧 Use per-gateway aggressive mode — enable only for routes with mixed gateway quality
📋 Set SS_GATEWAY_SWITCH_LIMIT to 2–3 to cap the PDD impact

❌ Problem 2: Double Ringing or Multiple Call Legs

🔍 Symptom: The called party’s phone rings multiple times or the callee sees multiple incoming calls from the same caller.

💡 Cause: In aggressive mode, VOS3000 may send INVITE to a second gateway while the first gateway is still ringing the destination. If both gateways reach the same endpoint, the phone rings twice. This is particularly problematic in mobile networks where the same destination may be reachable through multiple gateways.

✅ Solutions:

🔧 Enable SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START = On to lock in once media flows
📊 Configure proper gateway prefix settings to avoid duplicate routes — see prefix settings guide
🔄 Reduce the ringing timeout (SS_SIP_TIMEOUT_RINGING) to minimize the overlap window

❌ Problem 3: CPS Overload with Aggressive Mode

🔍 Symptom: System CPS (calls per second) increases significantly after enabling aggressive failover, causing performance problems during peak hours.

💡 Cause: Each failed gateway attempt generates a complete SIP INVITE transaction. In aggressive mode, every call that does not connect on the first attempt generates additional INVITE attempts, multiplying the signaling load.

✅ Solutions:

🔧 Set SS_GATEWAY_SWITCH_LIMIT to 3–4 to bound the maximum CPS multiplier per call
📊 Monitor system capacity planning metrics during peak hours
🔄 Consider enabling aggressive mode only during off-peak hours or only for specific routes

💡 Aggressive Gateway Failover Best Practices

🎯 Follow these best practices to maximize the ASR benefit of VOS3000 aggressive gateway failover while minimizing the PDD cost. Proper VOS3000 aggressive gateway failover deployment requires careful attention to these guidelines:

Best Practice	Recommendation	Reason
📊 Always pair with switch limit	Set SS_GATEWAY_SWITCH_LIMIT = 3–4	🔧 Bounds PDD while preserving ASR benefit
🔒 Keep RTP lock-in enabled	SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START = On	🛡️ Prevents one-way audio — overrides aggressive mode
🚫 Keep busy stop enabled	SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY = On	📊 Prevents wasteful switching after genuine busy
🔧 Use per-gateway configuration	Enable aggressive mode only on routes that benefit	📋 Avoids unnecessary PDD on reliable routes
📊 Measure before and after	Compare ASR and PDD metrics before enabling	📈 Data-driven decision making

❓ Frequently Asked Questions

❓ What is the default value of SS_GATEWAY_SWITCH_UNTIL_CONNECT?

🔧 The default value is Off, as documented in the VOS3000 2.1.9.07 manual §4.3.5.2 (page 236). This means that by default, VOS3000 uses standard failover behavior: it stops switching when the call reaches ringing state, receives a busy signal, or encounters a no-answer condition. The Off default is the conservative choice that prioritizes lower PDD over higher ASR. You should only enable the VOS3000 aggressive gateway failover mode after analyzing your traffic patterns and determining that the ASR improvement justifies the potential PDD increase. The VOS3000 aggressive gateway failover decision should always be data-driven.

❓ Does aggressive mode override the RTP lock-in stop condition?

🛡️ No, the VOS3000 manual explicitly states: “This option is NOT affected by ‘Switch gateway until connect’. When ‘Switch gateway until connect’ is on, if received RTP packet, stop switch gateway.” This means that even in aggressive mode, if RTP media starts flowing, VOS3000 stops switching immediately. The RTP lock-in failover (SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START) always takes priority over aggressive mode. This is a critical safety mechanism that prevents one-way audio and ghost calls, regardless of the failover mode you select. For more details, see our RTP media proxy guide.

❓ Does aggressive mode override the busy stop condition?

🚫 No, the VOS3000 manual states: “When ‘Switch gateway until connect’ is on, if received busy signal, stop switch gateway.” The busy stop switch (SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY) is independent of the VOS3000 aggressive gateway failover setting. When a 486 Busy Here response is received, VOS3000 stops switching regardless of whether VOS3000 aggressive gateway failover is On or Off. This is because a busy signal indicates the called party is genuinely unavailable — trying other gateways will not change the user’s busy status and would only waste system resources and inflate CPS.

❓ When should I use aggressive gateway failover?

📊 You should consider enabling VOS3000 aggressive gateway failover when you have multiple routing gateways for the same destination and some of them consistently ring without connecting. The VOS3000 aggressive gateway failover is particularly valuable for wholesale termination with multiple carrier routes, international traffic with variable quality paths, and scenarios where ASR improvement is more valuable than PDD optimization. You should avoid aggressive mode for retail operations where callers are PDD-sensitive, calling card services where silence during switching frustrates users, and deployments where all gateways have similar quality (no ASR benefit from switching). Always measure ASR and PDD before and after enabling aggressive mode to verify the benefit. Use the gateway analysis reports for data-driven decision making.

❓ Can I enable aggressive mode for specific gateways only?

🔧 Yes, VOS3000 supports per-gateway configuration of the VOS3000 aggressive gateway failover mode. In the routing gateway’s “Additional settings” panel, you can set “Switch gateway until connect” to On, Off, or Default (which inherits the system parameter value). This per-gateway override allows you to enable aggressive mode only on the gateways and routes where it provides measurable benefit, while keeping standard mode on reliable routes where it would only add unnecessary PDD. This granular control is the recommended approach for production deployments.

❓ How does aggressive mode affect H.323 calls?

📡 For H.323 calls, the VOS3000 aggressive gateway failover mode works identically to SIP — the softswitch continues switching gateways until it receives an H.323 Connect message. The H.323 equivalent of SIP 180 Ringing is the Alerting message, and in aggressive mode, receiving an Alerting does not stop the switching process. The softswitch will continue trying other gateways until one returns a Connect message. The same overrides apply under VOS3000 aggressive gateway failover: RTP lock-in and busy stop conditions still take priority over the VOS3000 aggressive gateway failover mode for H.323 calls. For H.323-specific parameters, see the VOS3000 system parameters reference.

📞 Need Expert Help with VOS3000 Aggressive Gateway Failover?

🔧 Configuring the VOS3000 aggressive gateway failover mode requires careful balancing between call completion rates and post-dial delay performance. The VOS3000 aggressive gateway failover setting is one of the most impactful parameters in your failover strategy. Whether you are evaluating whether aggressive mode will improve your ASR, configuring per-gateway failover settings, or troubleshooting PDD issues after enabling aggressive switching, expert guidance ensures your VOS3000 system achieves the optimal balance for your business requirements. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 aggressive gateway failover configuration, ASR optimization, and PDD tuning. Our team specializes in VOS3000 failover strategy design, routing quality analysis, and carrier-grade VoIP performance optimization. 🔧

🔗 Explore related VOS3000 failover and routing configuration guides:

VOS3000 Vendor Failover Setup — Complete guide to configuring gateway failover
VOS3000 ASR ACD Analysis — Monitoring and improving call completion rates
VOS3000 SIP Call Progress Timeout — Tuning SIP timeout for failover optimization
VOS3000 Routing Optimization — Optimizing routing for quality and cost
VOS3000 Gateway Configuration Routing Mapping — Gateway routing and mapping setup
VOS3000 LCR Least Cost Routing — Cost-based routing configuration

📞 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

VOS3000 Gateway Switch Limit Essential SS_GATEWAY_SWITCH_LIMIT Failover Cap

April 26, 2026April 26, 2026 king

VOS3000 Gateway Switch Limit Essential SS_GATEWAY_SWITCH_LIMIT Failover Cap

🔄 Every time a call fails to connect through one routing gateway in VOS3000, the softswitch can automatically try the next available gateway in the route. This failover mechanism is critical for maintaining high call completion rates, but without a cap on the number of attempts, a single call can cascade through every gateway in your routing table, creating painfully long post-dial delay (PDD) for the caller. The VOS3000 gateway switch limit parameter, SS_GATEWAY_SWITCH_LIMIT, is the essential control that prevents this runaway switching behavior by capping the maximum number of failover attempts per call. 🔧

⚙️ By default, SS_GATEWAY_SWITCH_LIMIT is set to None, meaning there is no limit on how many gateways VOS3000 will try before giving up on a call. While unlimited switching maximizes the chance of call completion, it comes at a steep cost: each failover attempt adds signaling overhead, increases PDD, inflates calls-per-second (CPS) load on the softswitch, and can generate a cascade of failed CDR records. Setting the VOS3000 gateway switch limit to a specific value forces the softswitch to stop trying after that many attempts, returning a failure response to the caller faster and freeing system resources for other calls. The key is finding the right balance between giving calls enough chances to connect and preventing excessive delay. 📊

🎯 This guide provides a complete, manual-verified reference for the SS_GATEWAY_SWITCH_LIMIT parameter. All parameter definitions are sourced from the official VOS3000 2.1.9.07 English manual §4.3.5.2 (page 236), with detailed explanations of how the VOS3000 gateway switch limit works, how it interacts with other failover parameters, and practical recommendations for different deployment scenarios. 📘

🔐 What Is the VOS3000 Gateway Switch Limit?

📋 The VOS3000 gateway switch limit is defined by the system parameter SS_GATEWAY_SWITCH_LIMIT, documented in the VOS3000 manual §4.3.5.2 (page 236) as “Times limit for Routing Gateway Auto-Switch.” This parameter controls the maximum number of times VOS3000 will automatically switch to a different routing gateway when the current gateway fails to deliver a call. Each switch attempt represents one failover cycle: the softswitch selects the next gateway according to the routing rules and sends a new INVITE (for SIP) or Setup (for H.323) to that gateway.

💡 Key characteristics of SS_GATEWAY_SWITCH_LIMIT:

🔢 Default value: None — unlimited switching attempts per call
📊 Configuration location: Operation management > Softswitch management > Additional settings > System parameter
🔄 Scope: Applies per call — each new call starts with a fresh switch counter
📡 Protocol support: Affects both SIP and H.323 gateway switching
📋 Interaction: Works alongside SS_GATEWAY_SWITCH_UNTIL_CONNECT, SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START, and SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY

📍 Setting the value: When you configure SS_GATEWAY_SWITCH_LIMIT in the VOS3000 client, you set a numeric value representing the maximum number of auto-switch attempts allowed by the VOS3000 gateway switch limit. For example, a value of 3 means VOS3000 will try up to 3 additional gateways after the initial attempt fails, for a total of 4 gateway attempts per call. Setting it to None (or 0, depending on version) removes the limit entirely, allowing unlimited switching until either a gateway connects or all available gateways have been exhausted.

📊 How Unlimited Switching Causes Long PDD

⏱️ Post-dial delay (PDD) is the time between when a caller dials a number and when they hear ringback tone. In VOS3000, each gateway failover attempt adds to the PDD because the softswitch must wait for a timeout or rejection from one gateway before trying the next. When the VOS3000 gateway switch limit is set to None, a single call can trigger sequential INVITE attempts to every gateway in the routing table, each consuming several seconds of timeout before moving on.

Scenario	Gateways Tried	Approx. PDD	Caller Experience
Limit = None, 10 gateways all down	10 attempts	30–60 seconds	🔴 Extremely poor — caller hangs up
Limit = 3, gateways down	4 attempts (1 + 3)	9–15 seconds	🟡 Tolerable — some callers wait
Limit = 2, gateways down	3 attempts (1 + 2)	6–10 seconds	🟢 Acceptable — fast failure response
Limit = None, 1st gateway succeeds	1 attempt	1–3 seconds	🟢 Excellent — no failover needed

🚨 PDD calculation insight: The approximate PDD for failover is the sum of all SIP INVITE timeouts for each failed attempt. The default SS_SIP_TIMEOUT_INVITE is 10 seconds (VOS3000 manual §4.3.5.2, page 231), but the actual time per attempt depends on whether the gateway actively rejects (fast) or simply does not respond (slow timeout). When gateways are truly unreachable, each attempt consumes the full timeout duration, making unlimited switching extremely costly in terms of PDD when the VOS3000 gateway switch limit is not configured. For detailed SIP timeout tuning, see our SIP INVITE timeout guide.

📋 SS_GATEWAY_SWITCH_LIMIT Parameter Reference

Attribute	Detail
📌 Parameter Name	SS_GATEWAY_SWITCH_LIMIT
📝 Manual Description	Times limit for Routing Gateway Auto-Switch (VOS3000 2.1.9.07 manual §4.3.5.2, page 236)
🔧 Default Value	None (unlimited switching)
📍 Configuration Path	Operation management > Softswitch management > Additional settings > System parameter
📊 Value Range	None or positive integer (recommended: 2–5)
🔄 Scope	Per call — each call has its own switch counter
📡 Protocol	SIP and H.323

🔄 How Gateway Switch Limit Interacts with Other Failover Parameters

🔗 The VOS3000 gateway switch limit does not operate in isolation — it is one part of a comprehensive failover control system. The VOS3000 gateway switch limit works alongside three other system parameters that control different aspects of failover behavior. Understanding these interactions is critical for designing an effective failover strategy that balances call completion with setup speed.

Parameter	Default	Function	Interaction with SWITCH_LIMIT
SS_GATEWAY_SWITCH_UNTIL_CONNECT	Off	Enables aggressive failover until connect signal received	When On, SWITCH_LIMIT still caps total attempts
SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START	On	Stops switching once RTP media starts flowing	Overrides SWITCH_LIMIT — stops switching regardless of remaining attempts
SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY	On	Stops switching when 486 Busy received	Overrides SWITCH_LIMIT — stops switching on busy signal

💡 Priority hierarchy: The stop conditions (RTP start and user busy) take priority over the switch limit. Even if SS_GATEWAY_SWITCH_LIMIT allows more attempts, if RTP starts flowing or a busy signal is received, VOS3000 stops switching immediately. The VOS3000 gateway switch limit acts as a maximum ceiling — it never forces additional switching, it only prevents excessive switching. For more on the RTP lock-in behavior, see our VOS3000 RTP media guide.

📊 Recommended Switch Limit Values by Deployment Type

🎯 The optimal VOS3000 gateway switch limit depends on your deployment type, the number of available gateways, and your priority between call completion rate (ASR) and post-dial delay (PDD). Here are practical recommendations based on common VoIP deployment scenarios:

Deployment Type	Recommended Limit	Reasoning
🏢 Retail VoIP (low PDD critical)	2–3	Retail callers are impatient — fast failure is better than long silence
🔄 Wholesale termination (ASR critical)	3–5	Wholesale clients value completion rate over PDD — more attempts improve ASR
💳 Calling card service	2–3	Card users hear silence during switching — limit prevents frustration
📡 Enterprise SIP trunking	3–4	Business users tolerate some delay but expect reliable completion
🔗 Multi-carrier failover	4–6	Multiple carriers increase chances — more attempts justified for redundancy
🧪 Testing / lab environment	None	Unlimited switching helps discover all routing paths during testing

📊 ASR vs PDD trade-off: Every additional switch attempt governed by the VOS3000 gateway switch limit improves your Answer-Seizure Ratio (ASR) by giving the call another chance to connect, but each attempt also adds to the PDD. The relationship is not linear — the first 2–3 failover attempts typically yield the largest ASR improvement, while attempts beyond 5 provide diminishing returns because the remaining gateways are often lower-priority routes with poorer quality. For comprehensive ASR analysis methodology, see our VOS3000 ASR ACD analysis guide.

📋 Gateway Switch Limit and CDR Impact

📊 The VOS3000 gateway switch limit directly affects your CDR data. Each gateway attempt governed by the VOS3000 gateway switch limit produces signaling and record-keeping consequences. Each failover attempt that fails generates a CDR record (when SS_CDR_RECORD_NONCONNECT is enabled), and calls that exhaust the switch limit generate a final CDR with the appropriate call end reason. Understanding this CDR impact helps you analyze failover patterns and tune the limit appropriately.

CDR Impact	With None Limit	With Set Limit (e.g., 3)
Non-connected CDR records per call	Up to N (all gateways tried)	Up to 3 + 1 (initial attempt + 3 switches)
Database load during gateway outage	🔴 Very high — every call generates maximum CDRs	🟢 Controlled — capped CDR generation per call
CPS load on softswitch	🔴 High — N INVITE attempts per failed call	🟢 Bounded — predictable maximum attempts per call
Call end reason accuracy	Last gateway’s rejection reason recorded	Last attempted gateway’s reason, or “switch limit exceeded”

🔧 CDR recording tip: When you enable SS_CDR_RECORD_NONCONNECT (documented in manual §4.3.5.2, page 235), VOS3000 records CDRs for calls that never connected — including failover attempts. With an unlimited switch limit, a single call to an unreachable destination could generate dozens of non-connected CDR records, significantly inflating your database. Setting the VOS3000 gateway switch limit prevents this CDR flood by capping the number of failover records per call. For more on CDR configuration, see our CDR analysis and billing guide.

🛡️ Common Gateway Switch Limit Problems and Solutions

❌ Problem 1: Excessive PDD with Default None Setting

🔍 Symptom: Callers experience very long silence (30+ seconds) before hearing ringback or a fast-busy tone, especially when multiple gateways are unavailable.

💡 Cause: SS_GATEWAY_SWITCH_LIMIT is set to None (default), allowing VOS3000 to try every available gateway sequentially when the VOS3000 gateway switch limit is not configured. Each failed attempt consumes the full INVITE timeout (default 10 seconds), so 5 failed gateways means 50+ seconds of PDD.

✅ Solutions:

🔧 Set SS_GATEWAY_SWITCH_LIMIT to 3 or 4 — this caps failover attempts while still giving calls reasonable chances under the VOS3000 gateway switch limit
⏱️ Reduce SS_SIP_TIMEOUT_INVITE from 10 to 5 seconds — faster timeout means faster failover between gateways
📊 Enable vendor failover setup to ensure only healthy gateways are in the routing pool

❌ Problem 2: Low ASR After Setting Switch Limit Too Low

🔍 Symptom: After setting SS_GATEWAY_SWITCH_LIMIT to 1 or 2, the Answer-Seizure Ratio drops significantly because calls that would have connected on the 3rd or 4th gateway attempt are now rejected early.

💡 Cause: The switch limit is too restrictive for the number of available gateways. If you have 5 gateways but the VOS3000 gateway switch limit only allows 2 switch attempts, the softswitch never reaches the gateways that could successfully deliver the call.

✅ Solutions:

📊 Analyze CDR data to determine how many switch attempts typically succeed — the limit should be at least 1 more than the highest successful attempt number
🔧 Increase the limit to 3–4 for wholesale deployments where ASR is more valuable than PDD — the VOS3000 gateway switch limit should reflect your traffic priorities
📡 Use routing optimization to ensure the best gateways are tried first, reducing the need for many switch attempts

❌ Problem 3: CPS Overload During Gateway Outage

🔍 Symptom: When one or more gateways go offline, the VOS3000 softswitch experiences high CPU and CPS load because every incoming call triggers maximum failover attempts.

💡 Cause: With unlimited switching, every failed call generates N INVITE attempts (where N is the number of available gateways), multiplying the signaling load by the number of gateways during outage conditions.

✅ Solutions:

🔧 Set the VOS3000 gateway switch limit to 2–3 to bound the maximum signaling load per call
📊 Configure gateway analysis reports with alarm thresholds to detect gateway outages early
🛡️ Remove failed gateways from the routing pool immediately during outages to prevent wasted switch attempts

💡 Gateway Switch Limit Best Practices

🎯 Follow these best practices to optimize the VOS3000 gateway switch limit for your specific deployment. Proper VOS3000 gateway switch limit configuration prevents both runaway PDD and premature call rejection:

Best Practice	Recommendation	Reason
📊 Never leave default None in production	Set limit to 2–5 based on deployment type	🔧 Prevents runaway PDD and CPS overload
🔄 Pair with RTP stop enabled	Keep SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START = On	📡 Stops switching once media flows — prevents one-way audio
📞 Enable busy stop switch	Keep SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY = On	🚫 Prevents wasteful switching after genuine busy signal
⏱️ Tune SIP INVITE timeout	Reduce from 10s to 5s for faster failover	📊 Lower PDD per switch attempt without sacrificing reliability
📋 Analyze CDR failover patterns	Review which attempt number succeeds most often	📊 Data-driven limit setting instead of guessing

❓ Frequently Asked Questions

❓ What is the default value of SS_GATEWAY_SWITCH_LIMIT?

🔧 The default value of SS_GATEWAY_SWITCH_LIMIT is None, which means there is no limit on the number of gateway auto-switch attempts per call. This is documented in the VOS3000 2.1.9.07 manual §4.3.5.2 (page 236) as “Times limit for Routing Gateway Auto-Switch” with default value “None.” While this maximizes call completion chances, it can cause excessively long PDD when multiple gateways are unreachable. It is strongly recommended to set a specific VOS3000 gateway switch limit (2–5) in production deployments to bound failover behavior and prevent CPS overload during gateway outages.

❓ Does the gateway switch limit count the initial attempt or only failovers?

📊 The SS_GATEWAY_SWITCH_LIMIT parameter counts the number of auto-switch attempts, which are the failover attempts after the initial gateway selection. The VOS3000 gateway switch limit counts only these additional attempts, not the initial routing decision. So if you set the limit to 3, VOS3000 will make the initial attempt plus up to 3 additional switch attempts, for a total of 4 gateway tries per call. This interpretation is consistent with the parameter description “Times limit for Routing Gateway Auto-Switch” — the word “auto-switch” refers to the automatic switching between gateways, not the initial routing selection.

❓ What happens when the switch limit is reached?

🚫 When the VOS3000 gateway switch limit is reached and no gateway has successfully connected the call, VOS3000 stops trying additional gateways and returns a failure response to the calling party. The specific SIP response code depends on the last failure reason — it could be 503 Service Unavailable, 408 Request Timeout, or another appropriate code. A CDR record is generated for the call with the appropriate call end reason. The caller hears a fast-busy tone or a failure announcement, depending on your call failed announcement configuration.

❓ Can I set different switch limits per gateway?

📋 No, SS_GATEWAY_SWITCH_LIMIT is a system-level parameter that applies globally to all calls processed by the softswitch. You cannot set different VOS3000 gateway switch limit values per individual gateway. However, you can control failover behavior at the gateway level through the routing gateway’s “Additional settings” panel, which includes per-gateway options like “Switch gateway until connect” and “Stop switch gateway when RTP start” that override the system defaults for that specific gateway. This per-gateway override capability gives you some granularity in controlling failover behavior without needing per-gateway switch limits.

❓ How does the switch limit interact with SS_GATEWAY_SWITCH_UNTIL_CONNECT?

🔄 SS_GATEWAY_SWITCH_UNTIL_CONNECT enables aggressive failover that keeps trying gateways until one returns a connect signal (SIP 200 OK or H.323 Connect). When this parameter is On, the VOS3000 gateway switch limit still applies — it caps the total number of switch attempts even in aggressive mode. The combination of UNTIL_CONNECT = On and SWITCH_LIMIT = 3 means VOS3000 will aggressively try up to 3 additional gateways, but will stop after that even if no connect signal has been received. This is the recommended combination for production: aggressive mode with a sensible cap. For more on aggressive failover, refer to the VOS3000 system parameters overview.

❓ Should I change the switch limit when adding more gateways?

📡 Yes, you should review and potentially increase the VOS3000 gateway switch limit when you add more routing gateways to your system. The general rule is: the limit should be high enough to cover your best gateways plus 1–2 backup attempts, but not so high that it causes unacceptable PDD. If you add 3 new gateways, consider increasing the limit by 1–2 to give calls a chance to reach the new routes. Always monitor PDD and ASR after any change to the VOS3000 gateway switch limit, and use CDR analysis to verify that the additional attempts are actually producing completed calls rather than just adding delay.

📞 Need Expert Help with VOS3000 Gateway Switch Limit?

🔧 Proper configuration of the VOS3000 gateway switch limit is essential for balancing call completion rates with post-dial delay performance. The VOS3000 gateway switch limit directly impacts both ASR and caller experience. Whether you are troubleshooting excessive PDD, optimizing ASR after changing your switch limit, or designing a failover strategy for a multi-carrier deployment, expert guidance ensures your VOS3000 system delivers the best possible caller experience. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 gateway switch limit configuration, VOS3000 gateway switch limit tuning, failover optimization, and PDD troubleshooting. Our team specializes in VOS3000 softswitch tuning, routing quality improvement, and carrier-grade failover design. 🔧

🔗 Explore related VOS3000 failover and routing configuration guides:

VOS3000 Vendor Failover Setup — Complete guide to configuring gateway failover
VOS3000 SIP INVITE Timeout — Tuning SIP timeout for faster failover
VOS3000 Gateway Configuration Routing Mapping — Setting up gateway routing and mapping
VOS3000 Routing Optimization — Optimizing routing for quality and cost
VOS3000 ASR ACD Analysis — Monitoring and improving call completion rates
VOS3000 System Parameters — Complete system parameter reference

📞 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

VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical

VOS3000 CDR End Direction Critical Call Termination Party Detection

April 26, 2026April 26, 2026 king

VOS3000 CDR End Direction Critical Call Termination Party Detection

📞 Knowing who hung up the call is not just a curiosity — it is a critical data point that affects billing disputes, quality analysis, fraud detection, and network performance optimization. The VOS3000 CDR end direction field records exactly which party initiated the call termination: the caller (0), the callee (1), or the VOS3000 server itself (2). This three-code system, documented in the official VOS3000 manual §4.4 (page 242), provides the definitive answer to “who ended this call?” — and that answer has far-reaching implications for your VoIP business. 🔍

⚙️ Consider the billing dispute scenario: A customer claims they were overcharged because “the call dropped after only a few seconds.” Without the endDirection field, you have no way to prove whether the customer hung up normally, the far end hung up, or the server terminated the call due to a timeout or balance exhaustion. With endDirection = 2 (server), you can explain that the server terminated the call because the prepaid balance was depleted — resolving the dispute with evidence. Without it, you are relying on guesswork. 📊

🎯 This guide provides a comprehensive reference for the VOS3000 CDR end direction field, covering all three codes (0, 1, 2), their meanings, how they interact with other CDR fields like endReason and billingMode, and practical analysis techniques for using end direction data in billing, quality monitoring, and security applications. All definitions are sourced from the official VOS3000 2.1.8.0/2.1.9.07 English manual §4.4 (page 242). 📘

🔐 What Is VOS3000 CDR End Direction?

📋 The VOS3000 CDR end direction (also called “hangup side” in the manual) is Field 7 in the pipe-delimited CDR format. It records which party initiated the termination of the call by sending the SIP BYE message, H.323 EndSessionCommand, or equivalent call teardown signal. This is not about which party originated the call — it is specifically about which party ended it.

📍 CDR field location: Position 7 in the pipe-delimited CDR format, between the endReason (Field 6) and callerGatewayId (Field 8) fields, as documented in the VOS3000 manual §4.4.

📋 Official Manual Definition

📖 The VOS3000 2.1.8.0/2.1.9.07 English manual §4.4 (page 242) defines the endDirection field as:

“endDirection — Hangup side（0-caller，1-callee，2-server）”

📝 This is the complete and official definition. The three possible values and their meanings are:

Code	Party	Meaning	SIP Signal
0	🔔 Caller	The calling party initiated the hangup	BYE from caller side
1	📞 Callee	The called party initiated the hangup	BYE from callee side
2	🖥️ Server	The VOS3000 server initiated the hangup	BYE generated by VOS3000

📊 End Direction Code 0: Caller Hangup

🔔 When the VOS3000 CDR end direction is 0, it means the calling party initiated the call termination. In SIP terms, the BYE message originated from the caller’s side of the call leg. This is the most common end direction for normal completed calls — the person who made the call decides they are done talking and hangs up.

Attribute	Detail
📌 Code	0
📝 Party	Caller (calling party)
🔄 Typical Scenario	Normal call completion — caller hangs up after conversation
📊 Expected Proportion	50–80% of connected calls in most deployments

📋 Analysis Implications of Caller Hangup

💡 What caller hangup tells you: When endDirection = 0, the call followed a normal pattern — the calling party placed the call, the conversation took place, and the caller ended it when finished. This is the expected behavior for the majority of outbound calls. However, if you notice an unusually high percentage of caller hangups with very short hold times (under 3 seconds), it may indicate that callers are reaching the wrong number or encountering audio problems and hanging up immediately.

📊 Quality correlation: Pair endDirection = 0 with short holdTime values to identify potential audio quality issues. If callers consistently hang up within the first few seconds, there may be a one-way audio problem or incorrect number routing. Cross-reference with the endReason codes to get the full picture — a normal SIP 200 OK with endDirection = 0 and holdTime under 2000ms suggests a quick hangup after audio issues rather than a failed call.

📊 End Direction Code 1: Callee Hangup

📞 When the VOS3000 CDR end direction is 1, it means the called party initiated the call termination. The BYE message came from the callee’s side. This typically happens when the person who received the call decides to end the conversation.

Attribute	Detail
📌 Code	1
📝 Party	Callee (called party)
🔄 Typical Scenario	Called party hangs up after conversation ends
📊 Expected Proportion	15–40% of connected calls in most deployments

📋 Analysis Implications of Callee Hangup

💡 What callee hangup tells you: An endDirection of 1 is perfectly normal for many call scenarios — the called party simply ends the conversation. However, a high proportion of callee hangups, especially combined with short hold times, may indicate that the called parties are not expecting the call (possible spam or unsolicited traffic), or that the audio from the caller side is not reaching the callee properly.

🔍 Wholesale traffic quality indicator: In wholesale VoIP operations, monitoring the ratio of callee hangups to caller hangups on specific routes helps assess traffic quality. A route with a high percentage of callee hangups and short durations may indicate that the terminating carrier’s end users are rejecting or quickly ending calls — a sign of potential CLI (Caller Line Identification) issues or unwanted traffic. This data supports decisions about route optimization and carrier selection.

📊 End Direction Code 2: Server Hangup

🖥️ When the VOS3000 CDR end direction is 2, it means the VOS3000 server itself initiated the call termination. This is the most operationally significant of the three codes, because it indicates the softswitch actively intervened to end the call — and the reasons for that intervention directly impact billing, customer experience, and system health. 🚨

Attribute	Detail
📌 Code	2
📝 Party	Server (VOS3000 softswitch)
🔄 Typical Scenario	Server-initiated call termination for policy, timeout, or balance reasons
📊 Expected Proportion	5–20% of connected calls, depending on prepaid ratio

📋 When Does Server Hangup Occur?

🖥️ There are several important scenarios where VOS3000 terminates a call from the server side, each with different operational implications:

Scenario	Description	End Reason	Impact
💰 Balance exhaustion	Prepaid account runs out of funds during active call	Various (may show session timeout code)	Customer may dispute charges
⏱️ Session timer expiry	SIP session timer expires without successful re-INVITE refresh	200 (normal) or 408	Call duration capped by timer
🔧 Administrative disconnect	Operator manually disconnects the call via VOS3000 client	200	Immediate call termination
📡 No-media timeout	RTP media stream stops flowing for the configured timeout period	Various	Detects dead calls consuming resources
🛡️ Maximum duration limit	Call exceeds the configured maximum call duration	200	Policy-based call length cap
🔄 Gateway failover cleanup	Server terminates call during gateway switching or failover process	503 or other error	Call may be re-routed

💡 Recording server hangups: Whether CDRs for server-initiated hangups are recorded depends on the SERVER_BILLING_RECORD_SERVER_HANG_UP parameter. When this parameter is On, VOS3000 generates CDR records even when the server initiates the hangup, providing a complete audit trail of all call terminations. When Off, server-initiated hangups may not generate CDR records, creating gaps in your billing and operational data. For detailed configuration guidance, see our server hangup CDR recording guide.

📋 End Direction and Billing Dispute Resolution

💰 The VOS3000 CDR end direction field is one of the most powerful tools for resolving billing disputes. When a customer challenges a charge, the endDirection code provides objective evidence of what happened during the call:

Dispute Claim	End Direction	Resolution
“The call dropped after a few seconds”	0 (caller hangup)	✅ The caller (customer) hung up normally — not a dropped call
“I was disconnected unexpectedly”	2 (server hangup)	⚠️ Server terminated — investigate balance exhaustion or session timeout
“The call was much shorter than billed”	1 (callee hangup)	✅ The called party hung up — duration matches CDR holdTime
“I never made this call”	0 (caller hangup) with specific callerIp	🔍 Verify the callerIp matches the customer’s registered device

📊 Evidence chain: For maximum dispute resolution effectiveness, combine the endDirection field with other CDR fields. The endReason code tells you why the call ended, the holdTime tells you how long the conversation lasted, the callerIp confirms where the call originated, and the endDirection tells you who terminated the call. Together, these four fields create an unambiguous evidence chain that resolves most billing disputes. For detailed CDR analysis methodology, see our CDR billing discrepancy guide.

📊 End Direction and Call Quality Analysis

📈 Analyzing end direction patterns across your traffic reveals important quality trends that are not visible from ASR and ACD metrics alone. Here are the key analysis patterns to monitor:

📋 End Direction Distribution Analysis

Pattern	End Direction Mix	Indicates	Action
✅ Normal distribution	60% caller, 30% callee, 10% server	Healthy traffic with normal call patterns	No action needed — continue monitoring
⚠️ High server hangup	Server hangup over 25%	Session timeouts, balance exhaustion, or system issues	Check session timer and prepaid balance settings
🔍 Short callee hangup	Callee hangup with holdTime under 5s	Called parties rejecting calls — possible CLI or spam issue	Review caller ID presentation and traffic source
🚨 Short caller hangup	Caller hangup with holdTime under 3s	One-way audio or wrong number — callers hanging up immediately	Check audio quality on affected routes

📋 End Direction by Gateway Analysis

📡 Segmenting end direction data by gateway (using the callerGatewayId and calleeGatewayId fields) reveals gateway-specific quality issues. A gateway that shows an unusually high percentage of server-initiated hangups (endDirection = 2) may have connectivity problems causing session timer expirations. A gateway with a high proportion of short-duration callee hangups may be routing traffic to low-quality destinations where end users reject the calls. This gateway-level analysis supports data-driven routing decisions and helps you identify which carriers deliver the best call completion quality. For gateway performance monitoring techniques, see our gateway analysis reports guide.

📋 End Direction and Session Timer Interaction

⏱️ One of the most important operational interactions is between the VOS3000 CDR end direction and the SIP session timer system. When session timers are enabled, VOS3000 periodically sends re-INVITE messages to refresh the session. If the re-INVITE fails (the endpoint does not respond), VOS3000 terminates the call — and the endDirection will be 2 (server). This is a common scenario for calls that “mysteriously drop” after a fixed interval.

Session Timer Scenario	End Direction	End Reason	Resolution
✅ Re-INVITE succeeds	0 or 1 (normal)	200 OK	Call continues until party hangs up
⚠️ Re-INVITE fails (NAT issue)	2 (server)	408 or timeout	Check NAT keepalive settings
🔧 No session timer support	2 (server)	Session expiry	Configure SS_SIP_NO_TIMER_REINVITE_INTERVAL
💰 Prepaid balance depleted	2 (server)	200 OK (normal clear)	Expected behavior for prepaid accounts

💡 Investigating mysterious drops: If customers report calls dropping at consistent intervals (e.g., always at 30 minutes or 2 hours), check the SIP session timer configuration. The session timer interval, combined with the SS_SIP_SESSION_UPDATE_SEGMENT parameter, determines when VOS3000 sends re-INVITE refreshes. If the endpoint does not support session timers and SS_SIP_NO_TIMER_REINVITE_INTERVAL is not configured, VOS3000 may terminate the call after the session timer expires — resulting in endDirection = 2.

🛡️ Common End Direction Analysis Problems and Solutions

❌ Problem 1: Excessive Server Hangups (endDirection = 2)

🔍 Symptom: A high percentage of CDRs show endDirection = 2, indicating the server is terminating many calls.

💡 Cause: Multiple factors can cause excessive server hangups: session timer misconfiguration, NAT traversal failures causing re-INVITE timeouts, prepaid accounts frequently running out of balance, or RTP timeout detecting dead media streams.

✅ Solutions:

⏱️ Review SIP session timer settings — ensure SS_SIP_NO_TIMER_REINVITE_INTERVAL provides a safety net for non-timer endpoints
🌐 Check NAT keepalive settings — failed re-INVITEs through NAT firewalls are a leading cause of server-initiated hangups
💰 Verify prepaid balance thresholds — the mid-call balance warning should alert users before their balance is depleted
📡 Monitor RTP timeout settings that may be too aggressive for legitimate silent periods in calls

❌ Problem 2: Billing Disputes Where Customer Claims Call Dropped

🔍 Symptom: Customer disputes a charge, claiming the call dropped unexpectedly, but the CDR shows endDirection = 0 (caller hangup) with a substantial holdTime.

💡 Cause: The customer may have accidentally ended the call, or their SIP device may have sent a BYE due to a local issue (not a server-side drop). The CDR end direction provides the objective evidence.

✅ Solutions:

📋 Present the endDirection = 0 record to the customer as evidence that their device initiated the hangup
🔍 Cross-reference with callerIp to confirm the call originated from the customer’s registered device
📊 Compare the holdTime with the customer’s claim about call duration
📞 For endDirection = 2 cases, explain the server termination reason (balance exhaustion, session timeout, etc.)

❌ Problem 3: Short Callee Hangups Indicating Traffic Quality Issues

🔍 Symptom: High volume of endDirection = 1 records with very short holdTime values on a specific route or gateway.

💡 Cause: The called parties are answering and immediately hanging up. This can indicate wrong-number calls, CLI (Caller Line Identification) not being presented correctly, or the traffic being perceived as spam by the called parties.

✅ Solutions:

📞 Verify that the caller ID being presented to the called party is correct and recognizable
🔧 Check the caller ID management configuration for the affected mapping gateway
📊 Analyze the geographic distribution of short callee hangups to identify specific regions or carriers with quality issues
🔄 Consider routing adjustments to avoid low-quality termination carriers

💡 End Direction Best Practices

🎯 Follow these best practices to maximize the value of VOS3000 CDR end direction data in your operations:

Best Practice	Recommendation	Reason
📋 Always enable server hangup CDR recording	Set SERVER_BILLING_RECORD_SERVER_HANG_UP = On	🔍 Complete audit trail of all call terminations
📊 Monitor end direction distribution weekly	Track % of codes 0, 1, 2 across all traffic	📈 Early detection of quality and configuration issues
💰 Use end direction in billing dispute workflows	Include endDirection in dispute resolution SOP	🛡️ Objective evidence resolves disputes faster
📡 Segment by gateway for quality analysis	Analyze end direction per routing gateway	🔧 Data-driven carrier selection and route optimization
⏱️ Correlate endDirection = 2 with session timer	Match server hangups to timer expiry patterns	🔧 Identifies NAT and timer configuration problems

❓ Frequently Asked Questions

❓ What does VOS3000 CDR end direction 2 mean?

🖥️ A VOS3000 CDR end direction of 2 means the VOS3000 server initiated the call termination. This occurs when the softswitch actively ends the call, rather than either endpoint (caller or callee) hanging up. Common reasons include: prepaid account balance exhaustion (the server terminates the call when funds run out), SIP session timer expiry (the server did not receive a successful re-INVITE refresh), administrative disconnect by the operator, maximum call duration limit reached, or RTP media timeout detecting a dead media stream. The endDirection = 2 code is documented in the VOS3000 manual §4.4 (page 242) as “server” hangup side.

❓ How do I determine why a server hangup occurred?

🔍 To determine the specific reason for a server-initiated hangup (endDirection = 2), cross-reference the endDirection field with the endReason field (Field 6) in the same CDR record. The endReason provides the SIP response code or cause code that explains why the call was terminated. For example, endDirection = 2 with endReason = 200 typically indicates a normal server-initiated clear (such as balance exhaustion or maximum duration). EndDirection = 2 with endReason = 408 indicates a timeout. Combining these two fields gives you the complete picture of who ended the call and why.

❓ Does endDirection affect billing calculations?

💰 The endDirection field itself does not directly change billing calculations — the holdTime field determines the billable duration regardless of who hung up. However, endDirection has indirect billing implications. When endDirection = 2 (server hangup), the call may have been terminated before the natural conversation end, which can lead to customer disputes. When analyzing billing data, filtering by endDirection helps you understand the nature of your call completions and identify patterns that affect revenue, such as premature server terminations due to balance exhaustion on prepaid accounts.

❓ Can the endDirection value be incorrect?

🔧 In rare cases, the endDirection may not accurately reflect the true termination party. This can happen when a SIP ALG (Application Layer Gateway) or intermediate proxy modifies the BYE message direction, or when a gateway sends a BYE on behalf of an endpoint (making it appear as a callee hangup when the caller actually hung up). If you suspect endDirection inaccuracy, enable SIP debug tracing to capture the actual BYE message flow and verify which IP address sent the termination signal. Check our SIP debug guide for instructions on capturing and analyzing SIP message traces.

❓ How is endDirection different from endReason in VOS3000 CDR?

📋 The endDirection field (Field 7) tells you who terminated the call — caller (0), callee (1), or server (2). The endReason field (Field 6) tells you why the call was terminated — using SIP response codes (200, 486, 503, etc.) or Q.850 cause codes. These two fields answer different questions and must be analyzed together for the complete picture. For example, endDirection = 0 with endReason = 200 means the caller hung up normally. EndDirection = 2 with endReason = 200 means the server terminated the call normally (likely due to balance exhaustion or duration limit). EndDirection = 1 with endReason = 486 means the callee rejected the call with a busy signal.

❓ Should I always record CDRs for server-initiated hangups?

📝 Yes, it is strongly recommended to record CDRs for server-initiated hangups by setting SERVER_BILLING_RECORD_SERVER_HANG_UP = On. Without these records, your CDR data has gaps — you lose visibility into calls that the server terminated, which are often the most operationally significant calls (balance exhaustion, session timeouts, administrative actions). These records are essential for billing dispute resolution, quality analysis, and system health monitoring. The zero-duration CDR control parameter (SERVER_BILLING_RECORD_ZERO_HOLD_TIME) serves a different purpose — it controls whether failed call attempts are recorded, while SERVER_BILLING_RECORD_SERVER_HANG_UP specifically addresses server-initiated terminations.

📞 Need Expert Help with VOS3000 CDR End Direction?

🔧 Understanding and analyzing VOS3000 CDR end direction data is essential for billing accuracy, quality monitoring, and operational intelligence. Whether you are investigating server-initiated hangups, resolving billing disputes, or building a call quality dashboard, expert guidance ensures your analysis is accurate and actionable. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 CDR end direction analysis, billing dispute resolution, and call quality monitoring. Our team specializes in VOS3000 CDR analytics, billing system optimization, and VoIP quality assurance. 🔧

🔗 Explore related VOS3000 CDR and call quality guides:

VOS3000 Call Termination Reasons — Complete reference for endReason codes that complement endDirection analysis
VOS3000 Server Hangup CDR — Configuring SERVER_BILLING_RECORD_SERVER_HANG_UP for complete audit trails
VOS3000 CDR Analysis and Billing — Comprehensive CDR analysis methodology for revenue optimization
VOS3000 Zero Duration CDR — Managing zero-duration call records during attacks and normal operations
VOS3000 Session Timer — SIP session timer configuration that affects server-initiated hangups
VOS3000 ASR ACD Analysis — Using ASR and ACD metrics alongside end direction for quality assessment

📞 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

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

April 26, 2026April 26, 2026 king

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

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

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

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

🔐 What Are VOS3000 CDR Billing Mode Codes?

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

💡 Why billing mode codes matter:

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

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

📊 VOS3000 CDR Billing Mode Code -1: No Billing

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

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

📋 When Does VOS3000 CDR Billing Mode -1 Occur?

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

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

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

📊 VOS3000 CDR Billing Mode Code 0: Phone Number Billing

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

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

📋 How Phone Number Billing Works

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

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

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

📊 VOS3000 CDR Billing Mode Code 1: Gateway ID Billing

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

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

📋 How Gateway ID Billing Works

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

📡 Common scenarios for gateway billing:

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

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

📊 VOS3000 CDR Billing Mode Code 3: Phone Card Billing

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

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

📋 How Phone Card Billing Works

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

📋 Phone card billing specifics:

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

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

📋 Complete VOS3000 CDR Billing Mode Codes Comparison Table

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

📊 VOS3000 CDR Billing Mode Distribution Analysis

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

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

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

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

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

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

🛡️ Common VOS3000 CDR Billing Mode Code Problems and Solutions

❌ Problem 1: Revenue Calls Showing billingMode = -1

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

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

✅ Solutions:

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

❌ Problem 2: Wrong Billing Mode for Gateway Calls

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

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

✅ Solutions:

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

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

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

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

✅ Solutions:

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

💡 VOS3000 CDR Billing Mode Code Best Practices

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

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

❓ Frequently Asked Questions

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

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

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

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

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

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

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

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

❓ Is billingMode = 3 only for calling card services?

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

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

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

📞 Need Expert Help with VOS3000 CDR Billing Mode Codes?

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

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

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

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

📞 Need Professional VOS3000 Setup Support?

For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:

📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com
🌐 Blog: multahost.com/blog
📥 Downloads: VOS3000 Downloads

VOS3000 CDR Pipe Format Definitive 18-Field Important Reference Guide

April 26, 2026April 26, 2026 king

VOS3000 CDR Pipe Format Definitive 18-Field Reference Guide

📊 Every VOS3000 operator who exports call detail records must understand the VOS3000 CDR pipe format down to the individual field level. The pipe-delimited text file is the universal interface between your softswitch and every external system that consumes call data — billing platforms, fraud detection engines, analytics dashboards, and regulatory compliance archives. A single misinterpreted field can cascade into billing errors, incorrect traffic reports, or failed audits. Yet the official manual provides only a brief field listing, leaving operators to figure out data types, edge cases, and integration mappings on their own. 🔍

⚙️ This guide provides a definitive, field-by-field reference of every column in the VOS3000 CDR pipe format. Each field is documented with its position in the pipe-delimited line, data type, example value, special considerations, and how it maps to external billing and analytics systems. All field definitions are sourced from the official VOS3000 2.1.8.0/2.1.9.07 English manual §4.4 (pages 241–243), with additional practical guidance based on real-world parsing and integration experience. 📘

🎯 Whether you are building a Python CDR parser, configuring a MySQL import pipeline, or integrating VOS3000 with a third-party billing system, this reference eliminates the guesswork from field mapping and data interpretation. Let us walk through every field in the exact order it appears in each CDR line. 🔧

🔐 VOS3000 CDR Pipe Format Overview

📁 When SS_CDR_RECORD_TO_FILE is enabled in VOS3000, the softswitch generates hourly text files in the cdr/ directory. Each file follows the naming convention YYYYMMDDHH.txt, and each line within the file represents one call detail record with fields separated by the pipe character (|, ASCII 124). The format specification is documented in the official VOS3000 manual §4.4.

📋 CDR Line Format Structure – VOS3000 CDR Pipe

callerE164|calleeE164|startTime|stopTime|holdTime|endReason|
endDirection|callerGatewayId|calleeGatewayId|callerIp|calleeIp|
callerAccessE164|calleeAccessE164|callerToGatewayE164|
calleeToGatewayE164|calleeBilling|billingMode|callerPdd|calleePdd

📝 Field count note: The VOS3000 manual §4.4 documents the header line with 18 pipe separators producing 19 columns. The first 17 fields (through billingMode) are the core billing-critical fields present in all CDR records. Fields 18 and 19 (callerPdd and calleePdd) provide Post-Dial Delay metrics that measure call setup timing. Your parsing logic should handle both 17-field and 19-field records for maximum compatibility across VOS3000 versions.

📊 Complete Field-by-Field Reference – VOS3000 CDR Pipe

📋 Below is the definitive reference for every field in the VOS3000 CDR pipe format, in the exact order they appear in each line:

Field 1: callerE164 — The Caller ID 🔔

Attribute	Value
📌 Field Position	1 (first field)
📐 Data Type	String (numeric E.164 format)
📝 Description	The caller ID — the originating party’s phone number
🔢 Example	12125551234
⚠️ Notes	May differ from callerAccessE164 after prefix transformations

💡 Practical note: The callerE164 field reflects the caller ID after VOS3000 has applied any configured prefix transformations. This is the number as seen by the billing engine, not necessarily the original incoming number. For the original incoming caller ID before any transformations, refer to Field 12 (callerAccessE164). Understanding this distinction is essential when troubleshooting billing discrepancies.

Field 2: calleeE164 — The Callee ID 📞

Attribute	Value
📌 Field Position	2
📐 Data Type	String (numeric E.164 format)
📝 Description	The callee ID — the destination phone number
🔢 Example	18005559876
⚠️ Notes	This is the billed destination number after prefix processing

🔑 Billing relevance: The calleeE164 is the number used by the VOS3000 billing engine to match the call against rate tables. If your prefix settings strip or add digits, the calleeE164 reflects the number after those transformations. This is critical for rate table matching — a calleeE164 of 18005559876 matches a different rate entry than 01118005559876.

Field 3: startTime — Call Begin Time ⏰

Attribute	Value
📌 Field Position	3
📐 Data Type	Datetime string
📝 Description	Begin time of the call
🔢 Example	2018-12-20 11:20:18
⚠️ Notes	Format is YYYY-MM-DD HH:MM:SS; timezone is server local time

⏱️ Time zone awareness: The startTime is recorded in the VOS3000 server’s local timezone. If your server is configured in UTC+6 (Bangladesh Standard Time), all timestamps reflect that timezone. When integrating CDR data with systems in different timezones, always account for the offset. The startTime represents when the call was initially received by VOS3000, not when it was answered.

Field 4: stopTime — Call End Time 🛑

Attribute	Value
📌 Field Position	4
📐 Data Type	Datetime string
📝 Description	End time of the call
🔢 Example	2018-12-20 16:34:09

📊 Duration calculation: The actual call duration is stored in Field 5 (holdTime), not calculated from startTime and stopTime. The difference between startTime and stopTime includes call setup time, ringing time, and other pre-connection delays. Only holdTime represents the actual conversation duration. The stopTime determines which hourly CDR file the record is written to.

Field 5: holdTime — Call Duration ⏱️

Attribute	Value
📌 Field Position	5
📐 Data Type	Integer (milliseconds)
📝 Description	Call duration in milliseconds
🔢 Example	45000 (equals 45 seconds)
🚨 Critical Note	Value is in MILLISECONDS, not seconds — a common parsing error

⚠️ The #1 parsing mistake: The holdTime field is recorded in milliseconds, not seconds. A value of 45000 means 45 seconds of conversation, not 45000 seconds. This is the single most common error when integrating VOS3000 CDR data with external billing systems. Always divide holdTime by 1000 before applying per-second or per-minute billing rates. The holdTime is also affected by the SERVER_BILLING_HOLD_TIME_PRECISION parameter, which controls millisecond rounding before billing calculation.

Field 6: endReason — End Reason Code 📋

Attribute	Value
📌 Field Position	6
📐 Data Type	String/Integer
📝 Description	End reason — SIP response code or Q.850 cause code
🔢 Example	200 (normal), 486 (busy), 480 (no answer)

🔍 Interpreting endReason: For SIP calls, the endReason typically contains the SIP response code from the final response message (200 OK, 486 Busy, 480 Temporarily Unavailable, 503 Service Unavailable, etc.). For H.323 calls, it may contain Q.850 cause codes. The endReason field, combined with endDirection, provides the complete picture of why and how a call terminated. For a detailed breakdown of termination codes, see our guide on VOS3000 call termination reasons.

Field 7: endDirection — Hangup Side 🔄

Attribute	Value
📌 Field Position	7
📐 Data Type	Integer (0, 1, or 2)
📝 Description	Hangup side: 0 = caller, 1 = callee, 2 = server

🔑 Billing impact: The endDirection tells you who initiated the call termination. A value of 0 means the calling party hung up normally, 1 means the called party hung up, and 2 means the VOS3000 server itself terminated the call (which could indicate a session timeout, account balance exhaustion, or administrative intervention). This field is critical for dispute resolution — see our detailed analysis in the server hangup CDR recording guide.

Fields 8–9: Gateway Identifiers 📡

Field	Position	Description	Example
callerGatewayId	8	Calling gateway ID	1001
calleeGatewayId	9	Called gateway ID	2003

📡 Gateway mapping: These fields contain the VOS3000 internal gateway IDs, not the gateway names you see in the client interface. To map these IDs to human-readable gateway names, you need to cross-reference the VOS3000 gateway configuration. The callerGatewayId refers to the mapping gateway (incoming side), while the calleeGatewayId refers to the routing gateway (outgoing side). Understanding this mapping is essential for gateway performance analysis and route optimization.

Fields 10–11: IP Addresses 🌐

Field	Position	Description	Example
callerIp	10	Caller IP address	192.168.1.100
calleeIp	11	Callee IP address	10.0.0.50

🔒 Security value: The IP address fields are invaluable for security analysis. By tracking callerIp patterns, you can identify traffic from unexpected source IPs that may indicate unauthorized access or SIP scanning attacks. The VOS3000 anti-hack configuration uses IP-level authentication, and these CDR fields provide the audit trail for verifying that authentication is working correctly.

Fields 12–13: Access (Incoming) E164 Numbers 📥

Field	Position	Description
callerAccessE164	12	Incoming caller — the original caller ID as received by VOS3000 before any transformations
calleeAccessE164	13	Incoming callee — the original destination number as received before transformations

🔄 Why access fields matter: These fields preserve the original phone numbers as they arrived at VOS3000, before any callee rewrite rules, prefix stripping, or number transformations were applied. This is crucial for debugging routing issues — if a call was routed incorrectly because a prefix transformation changed the destination, you can compare calleeAccessE164 (original) with calleeE164 (transformed) to identify exactly where the routing went wrong. For detailed prefix configuration guidance, see our callee rewrite rule guide.

Fields 14–15: Outbound (To Gateway) E164 Numbers 📤

Field	Position	Header Name	Description
callerToGatewayE164	14	callerToGatewayE164	Outbound caller — the caller ID sent to the outgoing gateway
calleeToGatewayE164	15	calleeToGatewayE164	Outbound callee — the destination number sent to the outgoing gateway

📋 Naming discrepancy note: The VOS3000 manual §4.4 header line labels these fields as callerToGatewayE164 and calleeToGatewayE164, but the field description table in the same section refers to them as “Outbound caller” and “Outbound callee” (callerOutE164 / calleeOutE164). Both names refer to the same data — the phone numbers after all VOS3000 transformations have been applied, as they are sent out to the routing gateway. These outbound fields show the final form of the numbers as seen by the terminating carrier.

Field 16: calleeBilling — Billing Method 💰

Attribute	Value
📌 Field Position	16
📐 Data Type	Integer (0 or 1)
📝 Description	Billing method: 0 = By caller, 1 = By callee

💡 Understanding billing method: This field indicates which party’s account is charged for the call. A value of 0 means the caller’s account is billed (the standard arrangement for most calls). A value of 1 means the callee’s account is billed, which applies to collect calls, toll-free number calls, or special reverse-charging arrangements. This field works in conjunction with billingMode (Field 17) to determine the complete billing attribution for each call.

Field 17: billingMode — Charge Mode 💳

Attribute	Value
📌 Field Position	17
📐 Data Type	Integer (-1, 0, 1, or 3)
📝 Description	Charge mode: -1 = no billing, 0 = phone number, 1 = gateway ID, 3 = phone card

🔑 Billing mode codes explained: This is one of the most important fields for billing analysis. A billingMode of -1 means the call was not billed at all — this applies to illegal calls, free numbers, and calls that bypass the billing engine. A value of 0 means billing is attributed to a phone number account. A value of 1 means billing is attributed to a gateway ID. A value of 3 means billing is attributed to a phone card (calling card). For a comprehensive breakdown of how each code affects billing calculations, refer to our detailed billing mode codes reference.

Fields 18–19: Post-Dial Delay Metrics ⏱️

Field	Position	Description
callerPdd	18	Time elapsed from call received to call connected (incoming PDD)
calleePdd	19	Time elapsed from call sent to routing response (outgoing PDD)

📊 PDD analysis value: Post-Dial Delay is a critical quality-of-service metric. High callerPdd values indicate that calls take too long to connect on the incoming side, which frustrates callers. High calleePdd values indicate slow response from routing gateways, which may point to gateway overload, network latency, or incorrect INVITE timeout configuration. Monitoring PDD trends helps you identify degrading gateway performance before it impacts your ASR.

📋 Complete VOS3000 CDR Pipe Format Quick Reference Table

#	Field Name	Type	Description	Example
1	callerE164	String	The caller ID	12125551234
2	calleeE164	String	The callee ID	18005559876
3	startTime	Datetime	Call begin time	2018-12-20 11:20:18
4	stopTime	Datetime	Call end time	2018-12-20 16:34:09
5	holdTime	Integer (ms)	Call duration in milliseconds	45000
6	endReason	String/Int	End reason code	200
7	endDirection	Integer	Hangup side (0/1/2)	0
8	callerGatewayId	Integer	Calling gateway	1001
9	calleeGatewayId	Integer	Called gateway	2003
10	callerIp	String	Caller IP address	192.168.1.100
11	calleeIp	String	Callee IP address	10.0.0.50
12	callerAccessE164	String	Incoming caller	12125551234
13	calleeAccessE164	String	Incoming callee	01118005559876
14	callerToGatewayE164	String	Outbound caller	12125551234
15	calleeToGatewayE164	String	Outbound callee	18005559876
16	calleeBilling	Integer	Billing method (0/1)	0
17	billingMode	Integer	Charge mode (-1/0/1/3)	0
18	callerPdd	Integer	Incoming PDD (ms)	3200
19	calleePdd	Integer	Outgoing PDD (ms)	1500

📊 External System Mapping Guide – VOS3000 CDR Pipe

🔗 When integrating VOS3000 CDR data with external billing and analytics systems, field names and data types often need to be mapped to the target system’s schema. Here is a reference mapping for common integration targets:

VOS3000 Field	MySQL Column	Common Billing Label	Transform Needed
callerE164	VARCHAR(32)	ANI / Calling Number	None
calleeE164	VARCHAR(32)	DNIS / Called Number	None
startTime	DATETIME	Call Start / Setup Time	Parse datetime string
holdTime	INT	Duration (seconds)	⚠️ Divide by 1000
endReason	VARCHAR(16)	Release Cause	Map to cause code table
endDirection	TINYINT	Release Source	Map 0/1/2 to labels
billingMode	TINYINT	Billing Type	Map -1/0/1/3 to labels

❓ Frequently Asked Questions

❓ How many fields are in the VOS3000 CDR pipe format?

📋 The VOS3000 CDR pipe format contains 17 core billing-critical fields (through the billingMode field at position 17) plus 2 Post-Dial Delay fields (callerPdd at position 18 and calleePdd at position 19), for a total of up to 19 fields. The pipe delimiter creates 18 separators for the full 19-column format. Older VOS3000 versions may produce records with only 17 fields (without PDD data). Your parsing code should handle variable field counts gracefully by checking the number of pipe-delimited columns in each line before processing.

❓ Why is holdTime in milliseconds instead of seconds?

⏱️ VOS3000 records holdTime in milliseconds to support high-precision billing configurations. The SERVER_BILLING_FEE_PRECISTION and SERVER_BILLING_HOLD_TIME_PRECISION parameters allow billing calculations down to millisecond granularity. While most operators bill in whole seconds or minutes, the millisecond precision in the CDR ensures that no rounding is applied before the data is exported — any rounding happens in the billing engine according to the configured precision parameters. When parsing CDR data, always divide holdTime by 1000 to convert to seconds.

❓ What is the difference between callerE164 and callerAccessE164?

🔄 callerE164 (Field 1) is the caller ID after VOS3000 has applied all prefix transformations and number manipulations. callerAccessE164 (Field 12) is the original incoming caller ID as it was received by VOS3000 before any transformations. The two values differ when VOS3000’s callee rewrite rules, prefix stripping, or caller ID manipulation features modify the number. Similarly, calleeE164 (Field 2) may differ from calleeAccessE164 (Field 13) when the destination number is transformed before routing.

❓ What does a billingMode of -1 mean in the CDR?

💳 A billingMode of -1 means the call was not billed. This applies to calls that bypass the billing engine entirely, including illegal calls from unauthorized IP addresses, calls to toll-free numbers configured under SERVER_BILLING_FREE_E164S, and calls where the billing system could not determine an account to charge. These records still appear in the CDR export (when SS_CDR_RECORD_ILLEGAL is On) for security auditing purposes, but they carry no billing charge.

❓ How do I parse VOS3000 CDR files with different field counts?

🔧 The safest approach is to split each CDR line on the pipe character and check the resulting field count before processing. Lines with 17 fields contain core billing data without PDD metrics. Lines with 19 fields include the PDD columns. Always map fields by position (index), not by counting from the end, since new fields are added at the end of the line. Use the field position reference table in this guide to ensure correct mapping regardless of the field count in your specific VOS3000 version.

❓ Are VOS3000 CDR timestamps in UTC or local time?

⏰ VOS3000 CDR timestamps (startTime and stopTime) are recorded in the server’s local timezone, not UTC. If your server is configured with timezone Asia/Dhaka (UTC+6), all timestamps will be in BST. When integrating CDR data with systems that expect UTC, you must apply the appropriate timezone offset during parsing. Always verify your server’s timezone setting with the date command in SSH before assuming the timezone in your CDR processing logic.

📞 Need Expert Help with VOS3000 CDR Pipe Format?

🔧 Accurate VOS3000 CDR pipe format parsing is the foundation of every billing integration, analytics pipeline, and compliance archive. A single misinterpreted field — especially the millisecond holdTime or the billing mode codes — can cascade into revenue-impacting billing errors. Whether you are building a CDR parser from scratch, troubleshooting field mapping issues, or integrating VOS3000 with an external billing platform, expert guidance ensures your data pipeline is accurate from day one. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 CDR pipe format parsing, field mapping, and external system integration. Our team specializes in VOS3000 CDR data extraction, billing system integration, and custom analytics development. 🔧

🔗 Explore related VOS3000 CDR and configuration guides:

VOS3000 CDR Analysis and Billing — Complete guide to analyzing CDR data for revenue optimization
VOS3000 CDR Billing Discrepancy — Troubleshooting billing differences between CDR and rate tables
VOS3000 Billing System — Overview of the entire VOS3000 billing architecture
VOS3000 Call Termination Reasons — Complete reference for endReason codes in CDR records
VOS3000 Parameter Description — Complete parameter reference for all VOS3000 configuration settings
VOS3000 Gateway Configuration — Setting up mapping and routing gateways for CDR field population

📞 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

VOS3000 CDR Text File Export Complete Pipe-Delimited Format Best Guide

April 26, 2026April 26, 2026 king

VOS3000 CDR Text File Export Complete Pipe-Delimited Format Guide

📊 Every VoIP operator needs reliable call data — and the VOS3000 CDR text file export is the backbone of billing accuracy, traffic analysis, and regulatory compliance. When enabled, VOS3000 generates pipe-delimited text files containing every call detail record, ready for ingestion by external billing systems, analytics platforms, and fraud detection tools. Yet many operators never configure this powerful feature correctly, leaving critical data trapped inside the VOS3000 database with no external backup or integration path. 📁

⚙️ The two parameters that control this entire process — SS_CDR_RECORD_TO_FILE and SS_CDR_RECORD_NONCONNECT — are straightforward to configure, but their implications for disk space, data completeness, and billing accuracy are often misunderstood. Setting SS_CDR_RECORD_TO_FILE to On creates an hourly CDR text file in the softswitch’s cdr/ directory, while SS_CDR_RECORD_NONCONNECT determines whether zero-duration calls (failed attempts, busy signals, no-answer) are included in that export. The difference between having these records and not having them can mean the difference between catching a fraud pattern early and discovering it weeks too late. 🔍

🎯 This guide provides a complete walkthrough of the VOS3000 CDR text file export system: how to enable it, how the pipe-delimited format is structured, how file naming and rotation work, and how to integrate the exported data with external systems. All parameter details are sourced from the official VOS3000 2.1.8.0/2.1.9.07 English manual, §4.3.5.1 (page 225) and §4.4 (pages 241–243). 📘

🔐 What Is VOS3000 CDR Text File Export?

📁 The VOS3000 CDR text file export is a softswitch-level feature that writes call detail records to flat text files on the server filesystem. Unlike CDR records stored in the MySQL database — which require the VOS3000 client or web interface to query — text file exports provide a continuous, externally accessible stream of call data that can be consumed by any system capable of parsing pipe-delimited text. 📋

💡 Why text file export matters:

🔄 External billing integration: Feed CDR data directly into third-party billing platforms without database access
🛡️ Backup redundancy: Maintain a file-based CDR copy independent of the MySQL database
📊 Analytics pipeline: Pipe-delimited files are easily consumed by Python, Excel, BigQuery, and custom tools
🔍 Fraud detection: Real-time or near-real-time CDR analysis on exported files catches anomalies faster
📋 Regulatory compliance: Many telecom regulators require CDR archival in a portable, non-proprietary format
🔗 System migration: Export historical CDR data when migrating to a new billing or CRM system

📍 Parameter location in VOS3000 Client: Operation management → Softswitch management → Additional settings → Softswitch parameter

📋 SS_CDR_RECORD_TO_FILE — The Master Switch

🔧 SS_CDR_RECORD_TO_FILE is the primary parameter that enables or disables the entire text file CDR export. When set to On, VOS3000 creates hourly text files containing all CDR records in pipe-delimited format.

Attribute	Value
📌 Parameter Name	SS_CDR_RECORD_TO_FILE
🔢 Default Value	Off
⚙️ Valid Values	On / Off
📝 Description	Save CDR as TXT (per VOS3000 manual §4.3.5.1, page 225)
📍 Location	Operation management → Softswitch management → Additional settings → Softswitch parameter

⚠️ Critical note: This parameter is Off by default. Many VOS3000 deployments run for years without CDR text file export enabled, which means no file-based CDR backup exists. If the MySQL database becomes corrupted or the server experiences a disk failure, all historical CDR data stored only in the database may be lost. Enabling SS_CDR_RECORD_TO_FILE provides a critical safety net.

📋 SS_CDR_RECORD_NONCONNECT — Zero-Duration Call Export

📞 SS_CDR_RECORD_NONCONNECT controls whether non-connected calls — those with zero hold time — are included in the text file export. This includes busy signals, no-answer attempts, failed calls, and other call attempts that never established a two-way audio path.

Attribute	Value
📌 Parameter Name	SS_CDR_RECORD_NONCONNECT
🔢 Default Value	Off
⚙️ Valid Values	On / Off
📝 Description	When saving CDR as TXT, contains CDR which hold time is 0s (per VOS3000 manual §4.3.5.1, page 225)
📍 Location	Operation management → Softswitch management → Additional settings → Softswitch parameter

💡 Why you might want non-connected CDRs: While zero-duration calls generate no revenue, they carry essential operational intelligence. High volumes of busy signals from a specific gateway may indicate capacity problems. Repeated no-answer attempts to a destination could signal a routing misconfiguration. Patterns of failed calls from unauthorized IPs — tracked by SS_CDR_RECORD_ILLEGAL — are often the first sign of toll fraud. Without SS_CDR_RECORD_NONCONNECT enabled, all of this intelligence is excluded from your text file export.

📁 CDR Text File Naming and Storage

📂 When SS_CDR_RECORD_TO_FILE is enabled, VOS3000 creates CDR text files in the cdr/ directory under the VOS3000 installation path. The naming convention follows a precise hourly pattern documented in the official manual §4.4 (page 241):

📋 File Naming Convention

Attribute	Detail
📐 Format	YYYYMMDDHH.txt
📁 Directory	cdr/ under VOS3000 installation path
⏰ Granularity	One file per hour
📝 Example	2013103112.txt contains CDRs ending between 12:00:00 and 12:59:59

🔍 How the hourly file system works: Each CDR is written to the file corresponding to the hour in which the call ended (stop time). A call that starts at 11:45 and ends at 12:10 will be recorded in the 12:00 hour file, not the 11:00 hour file. This means each file contains a self-contained set of CDRs that can be processed independently without worrying about time-overlap between files.

📋 CDR File Rotation and Retention

🔄 VOS3000 manages CDR text file rotation using two server-level parameters that control how long files are retained and how many are kept on disk:

Parameter	Default	Range	Purpose
SERVER_CDR_FILE_WRITE_INTERVAL	None	60–86400 seconds	Time interval for creating new CDR files
SERVER_CDR_FILE_WRITE_MAX	2048	10–4096 files	Maximum number of CDR files retained on disk

📊 Disk space planning: With the default SERVER_CDR_FILE_WRITE_MAX of 2048 files and one file per hour, VOS3000 retains approximately 85 days of CDR text files. For high-traffic systems, monitor disk usage closely — each hourly file can range from a few KB on a low-traffic system to hundreds of MB on a system processing thousands of concurrent calls. To learn more about CDR file rotation and backup strategies, see our guide on VOS3000 CDR analysis and billing.

📊 Pipe-Delimited CDR Format Overview

🔗 Each line in the VOS3000 CDR text file represents one call detail record, with fields separated by the pipe character (|). The format is documented in the official VOS3000 manual §4.4 (pages 241–243). Understanding this format is essential for parsing CDR data into external systems.

📋 CDR Line Format Structure

callerE164|calleeE164|startTime|stopTime|holdTime|endReason|
endDirection|callerGatewayId|calleeGatewayId|callerIp|calleeIp|
callerAccessE164|calleeAccessE164|callerToGatewayE164|
calleeToGatewayE164|calleeBilling|billingMode|callerPdd|calleePdd

📝 Field count note: The VOS3000 manual §4.4 documents the pipe-delimited format with 18 pipe separators, resulting in 19 columns of data. The first 18 fields (through billingMode) are the core CDR fields present in all versions, while the callerPdd and calleePdd fields provide Post-Dial Delay metrics that were added in later revisions of the software.

📋 Key CDR Fields at a Glance

#	Field	Description	Example
1	callerE164	The caller ID	12125551234
2	calleeE164	The callee ID	18005559876
3	startTime	Call begin time	2018-12-20 11:20:18
4	stopTime	Call end time	2018-12-20 16:34:09
5	holdTime	Call duration in milliseconds	45000
6	endReason	End reason code	200
7	endDirection	Hangup side (0=caller, 1=callee, 2=server)	0
17	billingMode	Charge mode (-1=no billing, 0=phone, 1=gateway, 3=phone card)	0

🔑 Key observations: The holdTime field records call duration in milliseconds, not seconds. This is critical for billing calculations — a holdTime of 45000 means 45 seconds, not 45000 seconds. The endDirection field identifies who terminated the call (caller, callee, or server), which is essential for call termination analysis. The billingMode field determines how the call was charged and whether billing was applied at all.

⚙️ Step-by-Step VOS3000 CDR Text File Export Configuration

🖥️ Follow these steps to enable and configure the VOS3000 CDR text file export on your softswitch:

Step 1: Enable CDR Text File Export 📁

🔐 Log in to VOS3000 Client with administrator credentials
📌 Navigate: Operation management → Softswitch management → Additional settings → Softswitch parameter
🔍 Locate SS_CDR_RECORD_TO_FILE in the parameter list
✏️ Change the value from Off to On
💾 Click Save to apply the configuration

⚠️ Important: After enabling SS_CDR_RECORD_TO_FILE, VOS3000 will begin writing CDR text files starting from the next hourly interval. Historical CDR data from before the parameter was enabled is not retroactively exported. If you need historical data, use the CDR query interface in the VOS3000 client to export it manually, as described in our CDR analysis guide.

Step 2: Configure Non-Connected Call Recording 📞

📋 In the same Softswitch parameter section, locate SS_CDR_RECORD_NONCONNECT
✏️ Change the value from Off to On if you need zero-duration call records in the export
💾 Save the configuration

💡 Recommendation: Enable SS_CDR_RECORD_NONCONNECT for most deployments. The additional disk space consumed by zero-duration CDRs is minimal compared to the operational value they provide. However, during a DDoS or flood attack, the volume of zero-duration CDRs can spike dramatically. If disk space is a concern during such events, you can temporarily disable this parameter to prevent disk overflow.

Step 3: Configure File Rotation Parameters 🔄

📋 Navigate: Operation management → Server management → Server parameter
🔍 Review SERVER_CDR_FILE_WRITE_INTERVAL — set the hourly interval for new file creation (default: one file per hour)
🔍 Review SERVER_CDR_FILE_WRITE_MAX — set the maximum number of CDR files to retain (default: 2048)
💾 Save and restart the VOS3000 service for changes to take effect

Scenario	WRITE_INTERVAL	WRITE_MAX	Result
✅ Default (most deployments)	3600 (1 hour)	2048	~85 days of CDR files retained
📊 High-traffic analytics	1800 (30 min)	4096	~85 days with finer granularity
💾 Low disk space	3600 (1 hour)	720	~30 days of retention
🛡️ Long-term compliance	3600 (1 hour)	4096	~170 days of retention

🛡️ Another important softswitch parameter that affects CDR text file content is SS_CDR_RECORD_ILLEGAL. This parameter controls whether CDRs are generated for calls originating from unauthorized IP addresses — calls that VOS3000 rejects as illegal or unauthorized.

Attribute	Value
📌 Parameter Name	SS_CDR_RECORD_ILLEGAL
🔢 Default Value	On
📝 Description	Record illegal call (per VOS3000 manual §4.3.5.1, page 225)

🔒 Unlike SS_CDR_RECORD_NONCONNECT (which defaults to Off), SS_CDR_RECORD_ILLEGAL defaults to On. This means VOS3000 is configured by default to record CDRs for hack attempts and unauthorized call attempts. These records appear in the text file export with a special billing mode code of -1 (no billing), making them easy to filter and analyze separately. For more details on how VOS3000 handles unauthorized calls, see our guide on illegal call detection and prevention.

🛠️ Parsing VOS3000 CDR Text Files for External Systems

📊 Once the VOS3000 CDR text file export is configured, the next step is integrating the exported data with your external systems. The pipe-delimited format is universally supported by programming languages, databases, and analytics tools.

📋 Parsing Methods Comparison

Method	Best For	Complexity	Real-Time
🐍 Python script	Custom analytics, billing import	Medium	Near-real-time (cron)
🗄️ MySQL LOAD DATA	Database import, reporting	Low	Batch (hourly)
📊 Excel/CSV conversion	Manual review, one-time analysis	Low	Manual
🔄 Logstash/Fluentd	Elasticsearch, SIEM integration	High	Near-real-time

📋 Python Parsing Example

import csv

# VOS3000 CDR field names (per manual §4.4)
CDR_FIELDS = [
    'callerE164', 'calleeE164', 'startTime', 'stopTime',
    'holdTime', 'endReason', 'endDirection',
    'callerGatewayId', 'calleeGatewayId',
    'callerIp', 'calleeIp',
    'callerAccessE164', 'calleeAccessE164',
    'callerToGatewayE164', 'calleeToGatewayE164',
    'calleeBilling', 'billingMode',
    'callerPdd', 'calleePdd'
]

def parse_cdr_file(filepath):
    """Parse VOS3000 CDR text file into list of dictionaries."""
    records = []
    with open(filepath, 'r') as f:
        reader = csv.reader(f, delimiter='|')
        for row in reader:
            if len(row) >= 17:  # Minimum core fields
                record = dict(zip(CDR_FIELDS[:len(row)], row))
                records.append(record)
    return records

# Usage: Parse a CDR file and filter connected calls
cdr_data = parse_cdr_file('/home/vos3000/cdr/2026042612.txt')
connected = [r for r in cdr_data if int(r.get('holdTime', 0)) > 0]
print(f"Total CDRs: {len(cdr_data)}, Connected: {len(connected)}")

🛡️ Common VOS3000 CDR Text File Export Problems and Solutions

⚠️ Misconfigurations and misunderstandings about the CDR text file export can lead to data loss, disk space issues, or incomplete records. Here are the most common problems and their solutions:

❌ Problem 1: No CDR Text Files Being Generated

🔍 Symptom: The cdr/ directory is empty or does not contain the expected hourly text files.

💡 Cause: SS_CDR_RECORD_TO_FILE is still set to Off (the default value). Many operators assume CDR files are generated automatically, but this feature must be explicitly enabled.

✅ Solution:

🔧 Navigate to Softswitch parameter and set SS_CDR_RECORD_TO_FILE = On
💾 Save the configuration and wait for the next hourly interval
📁 Verify the cdr/ directory exists and has proper write permissions
📋 Confirm with the VOS3000 system parameter guide that no other settings are blocking file creation

❌ Problem 2: Missing Zero-Duration Call Records

🔍 Symptom: The CDR text files only contain records for connected calls. Failed calls, busy signals, and no-answer attempts are absent.

💡 Cause: SS_CDR_RECORD_NONCONNECT is set to Off (default), which excludes zero-duration calls from the text file export.

✅ Solution:

📞 Set SS_CDR_RECORD_NONCONNECT = On in Softswitch parameter
📊 Be aware this increases file sizes — monitor disk usage after enabling
🔍 For fraud detection purposes, this setting is strongly recommended

❌ Problem 3: Disk Space Exhaustion from CDR Files

🔍 Symptom: The server runs low on disk space, and the cdr/ directory contains thousands of large CDR text files.

💡 Cause: SERVER_CDR_FILE_WRITE_MAX is set too high, or an external script is not archiving and cleaning up old CDR files.

✅ Solution:

🔄 Reduce SERVER_CDR_FILE_WRITE_MAX to a lower value (e.g., 720 for ~30 days)
📁 Implement a cron job to move CDR files older than X days to archive storage
📊 Monitor disk usage with the VOS3000 disk alarm feature
💾 Consider compressing older CDR files with gzip to save space

❌ Problem 4: Parsing Errors Due to Extra Pipe Characters

🔍 Symptom: External parsing scripts produce incorrect field alignment or data corruption.

💡 Cause: Caller or callee E164 fields contain unexpected characters, or the number of pipe separators varies between CDR records.

✅ Solution:

🔧 Use a robust parser that handles variable field counts gracefully
📋 Always validate the number of fields per line before processing
📊 Reference the official VOS3000 manual §4.4 (page 241) for the exact field specification

💡 VOS3000 CDR Text File Export Best Practices

🎯 Follow these best practices to get the most from your VOS3000 CDR text file export configuration:

Best Practice	Recommendation	Reason
📁 Always enable SS_CDR_RECORD_TO_FILE	Set to On	✅ Provides file-based CDR backup independent of MySQL
📞 Enable SS_CDR_RECORD_NONCONNECT	Set to On for most deployments	🔍 Captures failed call data for fraud detection and quality analysis
🔄 Archive CDR files regularly	Move files older than 30 days to archive	💾 Prevents disk space exhaustion on active server
📊 Validate CDR data daily	Check record counts and file sizes	🛡️ Early detection of data export problems
🔒 Set proper file permissions	Restrict cdr/ directory access	🔐 CDR files contain sensitive call data and IP addresses
📡 Consider real-time forwarding	Use SERVER_CDR_REAL_TIME_REPORT_SERVER	⚡ For immediate CDR delivery to external billing systems

💡 Pro tip: The VOS3000 CDR text file export works best as part of a comprehensive data strategy. Combine the text file export with the VOS3000 billing system for complete revenue tracking, and use the exported data to build custom dashboards that go beyond what the VOS3000 client interface provides. For operators who need real-time CDR delivery rather than hourly file batches, the SERVER_CDR_REAL_TIME_REPORT_SERVER parameter provides an alternative integration path.

📊 Complete VOS3000 CDR Export Parameter Reference

📋 Here is the complete reference table for all parameters related to CDR text file export, sourced from the official VOS3000 2.1.8.0/2.1.9.07 English manual:

Parameter	Default	Category	Purpose
SS_CDR_RECORD_TO_FILE	Off	Softswitch	Enable CDR text file export
SS_CDR_RECORD_NONCONNECT	Off	Softswitch	Include zero-duration calls in export
SS_CDR_RECORD_ILLEGAL	On	Softswitch	Record illegal/unauthorized call CDRs
SERVER_CDR_FILE_WRITE_INTERVAL	None	Server	CDR file creation interval (60–86400 seconds)
SERVER_CDR_FILE_WRITE_MAX	2048	Server	Maximum CDR files retained (10–4096)
SERVER_CDR_REAL_TIME_REPORT_SERVER	(blank)	Server	Real-time CDR forwarding server address
SERVER_QUERY_CDR_DENY_TIME	(blank)	Server	No CDR query time (blackout hours)
SERVER_QUERY_CDR_MAX_DAY_INTERVAL	31	Server	Maximum CDR query date range (days)
SERVER_MAX_CDR_PENDING_LIST_LENGTH	100000	Server	CDR queue length limit (10000–100000)

❓ Frequently Asked Questions

❓ How do I enable VOS3000 CDR text file export?

📁 To enable the VOS3000 CDR text file export, navigate to Operation management → Softswitch management → Additional settings → Softswitch parameter and set SS_CDR_RECORD_TO_FILE to On. This parameter is Off by default, so it must be explicitly enabled. After saving the configuration, VOS3000 will begin creating hourly CDR text files in the cdr/ directory starting from the next hourly interval. The files follow the naming convention YYYYMMDDHH.txt as documented in the VOS3000 manual §4.4.

❓ What is the difference between SS_CDR_RECORD_TO_FILE and SS_CDR_RECORD_NONCONNECT?

🔧 SS_CDR_RECORD_TO_FILE is the master switch that enables CDR text file export entirely. Without it set to On, no CDR text files are created at all. SS_CDR_RECORD_NONCONNECT only takes effect when SS_CDR_RECORD_TO_FILE is already On — it controls whether zero-duration call records (failed calls, busy signals, no-answer attempts) are included in the exported text files. When SS_CDR_RECORD_NONCONNECT is Off, only connected calls with non-zero hold time appear in the export.

❓ Where are VOS3000 CDR text files stored?

📂 VOS3000 CDR text files are stored in the cdr/ directory under the VOS3000 installation path. Each file is named using the format YYYYMMDDHH.txt, where each file contains all CDRs for calls that ended during that specific hour. For example, the file 2026042612.txt contains all CDRs for calls that ended between 12:00:00 and 12:59:59 on April 26, 2026. This file structure is documented in the official VOS3000 manual §4.4 (page 241).

❓ Can I export historical CDR data that was generated before enabling text file export?

📋 No, the VOS3000 CDR text file export only generates files for new calls after the feature is enabled. Historical CDR data that was generated while SS_CDR_RECORD_TO_FILE was Off is only available through the VOS3000 client CDR query interface or by querying the MySQL database directly. If you need to export historical data, use the CDR query function in the client and export the results manually. This is why it is strongly recommended to enable SS_CDR_RECORD_TO_FILE from the very first day of deployment.

❓ How much disk space do VOS3000 CDR text files consume?

💾 Disk space consumption depends entirely on your call volume. Each CDR record is approximately 200–350 bytes in the pipe-delimited text format. A system processing 100,000 calls per day would generate roughly 25–35 MB of CDR text data per day, or about 1 GB per month. With the default SERVER_CDR_FILE_WRITE_MAX of 2048 files (roughly 85 days of retention), a mid-traffic system would need approximately 3–4 GB of dedicated disk space for CDR files. Always monitor disk usage and configure VOS3000 disk alarms to receive alerts before space runs out.

❓ What is the pipe delimiter character used in VOS3000 CDR text files?

🔗 The VOS3000 CDR text file format uses the vertical bar or pipe character (|, ASCII 124) as the field delimiter. Each line in the file represents one call detail record, with fields separated by pipe characters. This format is widely supported by data processing tools, programming languages (Python, PHP, Perl), database import utilities (MySQL LOAD DATA INFILE), and spreadsheet applications. When parsing, always split on the pipe character and validate the expected field count.

📞 Need Expert Help with VOS3000 CDR Text File Export?

🔧 Proper VOS3000 CDR text file export configuration ensures your billing data is complete, your audit trail is intact, and your external systems receive the call data they need. Whether you are setting up CDR export for the first time, troubleshooting missing records, or integrating CDR data with an external billing platform, expert guidance saves time and prevents costly data gaps. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 CDR text file export setup, parsing, and integration. Our team specializes in VOS3000 softswitch configuration, billing system integration, and custom CDR analytics solutions. 🔧

🔗 Learn more about related VOS3000 CDR and billing configurations:

VOS3000 CDR Analysis and Billing — Complete guide to analyzing CDR data for revenue optimization
VOS3000 Billing System — Overview of the entire VOS3000 billing architecture
VOS3000 Zero Duration CDR — Managing zero-duration call records during DDoS and flood attacks
Illegal Call Detection in VOS3000 — How SS_CDR_RECORD_ILLEGAL captures unauthorized call attempts
VOS3000 CDR Billing Discrepancy — Troubleshooting billing differences between CDR and rate tables
VOS3000 Data Report — Using VOS3000 reporting tools for traffic and revenue analysis

📞 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

VOS3000 SIP Authentication Retry, VOS3000 SIP Early Hangup, VOS3000 SIP Session Timer Refresh, VOS3000 Non-Timer Endpoint Safety, VOS3000 SIP NAT Keepalive, VOS3000 SIP Resend Interval, VOS3000 SIP INVITE Timeout, VOS3000 SIP Call Progress Timeout, VOS3000 SIP Outbound Registration Parameters, VOS3000 SIP Privacy Header, VOS3000 SIP Routing Gateway Contact, VOS3000 SIP Publish Expire, VOS3000 SIP Display From, VOS3000 SIP Send Unregister

VOS3000 SIP INVITE Timeout and Gateway Switching: Complete Call Setup Guide

April 21, 2026April 21, 2026 king

VOS3000 SIP INVITE Timeout and Gateway Switching: Complete Call Setup Guide

📞 Nothing kills call completion rates faster than an incorrectly configured VOS3000 SIP INVITE timeout — and nothing disrupts active calls more than misconfigured gateway switching behavior. When your softswitch sends an INVITE and the far end never responds, how long should it wait? What happens when a gateway responds with SDP — should VOS3000 commit to that gateway or keep trying alternatives? These decisions, controlled by SS_SIP_TIMEOUT_INVITE, SS_SIP_STOP_SWITCH_AFTER_SDP, and SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT, directly impact your ASR, call reliability, and caller experience. ⏱️

⚙️ Set the INVITE timeout too short, and legitimate calls get abandoned before the gateway can answer. Set it too long, and failed calls consume precious port capacity. Enable gateway switching after SDP, and you risk disrupting early media. Disable switching after INVITE timeout, and backup routes never get tried. Understanding how these three parameters work together is what separates a basic VOS3000 deployment from a professionally tuned one. 🔧

🎯 This guide covers every aspect of the VOS3000 SIP INVITE timeout, gateway switching decisions, and stop switch behavior: the global parameters, per-gateway overrides, related system parameters like SS_GATEWAY_SWITCH_LIMIT and SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START, and best practices for configuring gateway failover in production environments. All data is sourced exclusively from the official VOS3000 V2.1.9.07 Manual, Section 4.3.5.2 (Tables 4-3 and 4-4). For expert assistance, contact us on WhatsApp at +8801911119966. 💡

🔐 What Is VOS3000 SIP INVITE Timeout?

⏱️ The VOS3000 SIP INVITE timeout defines the maximum number of seconds the softswitch will wait for a response after sending a SIP INVITE message to a gateway. If no provisional response (100 Trying, 180 Ringing, 183 Session Progress) or final response (200 OK, 4xx, 5xx, 6xx) arrives within this period, VOS3000 considers the INVITE failed and proceeds to the gateway switching decision. 📞

📋 This parameter is governed by SS_SIP_TIMEOUT_INVITE with a default value of 10 seconds:

Attribute	Value
📌 Parameter Name	SS_SIP_TIMEOUT_INVITE
🔢 Default Value	10
📐 Unit	Seconds
📝 Description	SIP INVITE timeout. Default value in “Routing Gateway > Additional settings > Protocol > SIP”
📍 Location	Operation management → Softswitch management → Additional settings → SIP parameter

💡 How the 10-second default works: When VOS3000 sends an INVITE to a gateway, it starts a countdown timer. During this period, SIP retransmissions occur based on SS_SIP_RESEND_INTERVAL (default: 0.5,1,2,4,4,4,4,4,4,4). If no response arrives within 10 seconds total, VOS3000 stops retransmitting, marks the INVITE as failed, and proceeds based on your gateway switching configuration.

📋 VOS3000 SIP INVITE Timeout vs Other SIP Timers

🌐 The VOS3000 SIP INVITE timeout is just one of several SIP timers that govern call setup. Understanding the differences is essential:

Timer	Parameter	Default	Controls
📞 INVITE Timeout	SS_SIP_TIMEOUT_INVITE	10 seconds	Total wait for any INVITE response
⏳ Trying Timeout	SS_SIP_TIMEOUT_TRYING	20 seconds	Wait for progress after 100 Trying
🔔 Ringing Timeout	SS_SIP_TIMEOUT_RINGING	120 seconds	Wait for answer while ringing
📡 Session Progress	SS_SIP_TIMEOUT_SESSION_PROGRESS	20 seconds	Wait after 183 Session Progress

🔑 Key distinction: The VOS3000 SIP INVITE timeout is the overall timer for the INVITE transaction. The Trying, Ringing, and Session Progress timers only activate after specific provisional responses are received. If no response comes at all, only the INVITE timeout applies.

🔄 Gateway Switching Decision Points

🌐 VOS3000 makes gateway switching decisions at multiple points during call setup. Understanding these decision points is critical for configuring reliable failover. The two most important are controlled by the VOS3000 SIP INVITE timeout parameters: 📡

Decision Point	Parameter	Default	Effect
📨 After SDP received	SS_SIP_STOP_SWITCH_AFTER_SDP	On	Stops switching — commits to gateway
⏱️ After INVITE timeout	SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT	Off	Continues switching — tries next gateway
📡 After RTP starts	SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START	On	Stops switching when RTP media flows
📞 Callee busy	SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY	On	Stops switching when 486 Busy received
🔗 Until connect	SS_GATEWAY_SWITCH_UNTIL_CONNECT	Off	Switch until 200 OK received

🔑 Key insight: These parameters work together as a layered decision system. The VOS3000 SIP INVITE timeout parameters (stop switch after SDP and stop switch after INVITE timeout) are the two most important because they control the two most common switching decisions: committing after media negotiation begins, and failing over after a gateway is unresponsive.

🛑 SS_SIP_STOP_SWITCH_AFTER_SDP — Stop Switch After SDP

📞 The SS_SIP_STOP_SWITCH_AFTER_SDP parameter controls whether VOS3000 stops trying alternative gateways once it receives SDP (Session Description Protocol) in a provisional response from the current gateway. When this parameter is On (default), VOS3000 commits to the current gateway as soon as SDP arrives — preventing mid-setup failover that would disrupt early media and call progress. 🛡️

Attribute	Value
📌 Parameter Name	SS_SIP_STOP_SWITCH_AFTER_SDP
🔢 Default Value	On
📝 Description	Stop Switch Gateway After Receive SDP
📋 Options	On / Off
📍 Location	Operation management → Softswitch management → Additional settings → SIP parameter

💡 Why SDP matters in gateway switching: In the SIP call flow, SDP carries the media negotiation details — codecs, IP addresses, and port numbers. When a gateway sends SDP in a 183 Session Progress response, it means the gateway has allocated media resources, early media may already be playing, the media session is partially established, and switching to another gateway at this point causes audio disruption and potential double-answer scenarios.

Setting	Gateway Switching Behavior	Call Impact	When to Use
✅ On (default)	Stops switching after SDP — commits to current gateway	🛡️ Prevents audio disruption, no double-answer, stable media path	📞 Nearly all deployments — recommended default
❌ Off	Continues switching even after SDP — may try other gateways	⚠️ Audio disruption risk, potential double-answer, unstable media	🔬 Only for special testing or specific carrier requirements

🚨 Warning: Setting SS_SIP_STOP_SWITCH_AFTER_SDP to Off is rarely appropriate. When a gateway has already sent SDP and you switch to another gateway, the original gateway may continue playing audio or billing for the session while the new gateway also attempts call setup. This creates chaotic call states. ⚡

⏱️ SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT

🔄 The companion parameter to stop switch after SDP is SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT. While the SDP parameter controls switching after media negotiation begins, this parameter controls switching after an INVITE times out with no response at all. ⏳

Attribute	Value
📌 Parameter Name	SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT
🔢 Default Value	Off
📝 Description	Stop Switch Gateway After INVITE Timeout
📋 Options	On / Off
📍 Per-Gateway Override	Yes — Routing Gateway > Additional settings > Protocol > SIP

🔑 Why the default is Off: When a gateway does not respond to an INVITE within the timeout period (defined by SS_SIP_TIMEOUT_INVITE), the most common cause is a network or gateway failure. In this scenario, you want VOS3000 to try the next available gateway — not give up. Setting this parameter to Off (default) ensures that backup routes are attempted, maximizing call completion rates. 📈

Setting	INVITE Timeout Behavior	Impact on Call
❌ Off (default)	VOS3000 continues gateway switching to the next available gateway	✅ Call attempts backup routes — higher completion rate
✅ On	VOS3000 stops switching — call fails immediately after INVITE timeout	⚠️ No failover — caller gets failure tone right away

💡 When to set On: The only scenario where setting this to On makes sense is for compliance or regulatory routing where calls must use a specific carrier and failover to alternatives is not permitted. 🏛️

📊 Complete Gateway Switching Flow

🔄 Understanding how the VOS3000 SIP INVITE timeout interacts with gateway switching requires seeing the complete flow. Here is the full decision tree: 🌳

📞 VOS3000 INVITE Timeout & Gateway Switching Flow:

VOS3000 ──► INVITE ──► Gateway A (Primary)
    │                          │
    │   ⏱️ INVITE Timeout countdown starts
    │   📡 Retransmissions per SS_SIP_RESEND_INTERVAL
    │                          │
    │   ┌── T = INVITE Timeout ──┐
    │   │   No response received │
    │   └────────────────────────┘
    │                          │
    ├── ❌ Gateway A INVITE failed
    │
    ├── Check: Stop switch after INVITE timeout?
    │   │
    │   ├── OFF (default) ✅
    │   │   └──► Try next gateway in route
    │   │        VOS3000 ──► INVITE ──► Gateway B (Backup)
    │   │                          │
    │   │            (new INVITE timeout starts)
    │   │
    │   └── ON ⚠️
    │       └──► Stop switching
    │            Return error to caller (SIP 408 / 503)
    │
    ┌── OR Gateway A responds ─────────────────┐
    │                                           │
    │   ├── 100 Trying / 180 Ringing (no SDP)   │
    │   │   └──► Continue waiting               │
    │   │        (may still switch)              │
    │   │                                       │
    │   ├── 183 Session Progress + SDP          │
    │   │   ├── Stop switch after SDP =         │
    │   │   │   ON (default) ✅                 │
    │   │   │   └──► Commit to Gateway A        │
    │   │   │        No more switching           │
    │   │   │                                   │
    │   │   └── Stop switch after SDP =         │
    │   │       OFF ⚠️                          │
    │   │       └──► May switch to Gateway B    │
    │   │            (risk of disruption!)       │
    │   │                                       │
    │   ├── SIP Error Code (4xx/5xx/6xx)        │
    │   │   └──► May try next gateway           │
    │   │                                       │
    │   └── 200 OK (Answer)                     │
    │       └──► Call established                │
    │            No switching                    │
    │                                           │
    └── 📝 CDR recorded with switching details   │

🔧 For detailed gateway failover configuration, see our vendor failover setup guide. For more on the complete SIP call flow, see our SIP call flow reference. 📡

📋 The VOS3000 SIP INVITE timeout and stop switch parameters do not work in isolation. Several system-level parameters from Table 4-4 of the official VOS3000 2.1.9.07 manual control the broader gateway switching behavior: 🔧

Parameter	Default	Description
📌 SS_GATEWAY_SWITCH_LIMIT	None	Times limit for Routing Gateway Auto-Switch — maximum number of gateways VOS3000 will try
📡 SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START	On	Stop Switch Gateway when RTP Start — prevents switching once media flows
📞 SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY	On	Callee busy stop switch — stops trying other gateways when 486 Busy received
🔗 SS_GATEWAY_SWITCH_UNTIL_CONNECT	Off	Switch Gateway Until Connect — when On, continues switching until 200 OK received

🔑 Key takeaway: The default VOS3000 configuration creates a logical switching strategy — try alternative gateways when the primary is unresponsive (INVITE timeout), but stop switching once the call progresses to the point where switching would cause disruption (SDP received, RTP started, callee busy). This is the correct behavior for virtually all VoIP deployments. ✅

🖥️ Per-Gateway INVITE Timeout and Stop Switch Settings

🎯 Not all gateways are created equal. VOS3000 provides per-gateway overrides for both INVITE timeout and stop switch behavior. 📡

📋 Gateway-Level SIP Settings

📍 Path: Routing Gateway → Additional settings → Protocol → SIP

Gateway Setting	Default Source	Function
📞 Invite timeout	SS_SIP_TIMEOUT_INVITE (10s)	INVITE signal timeout for this specific gateway
🛑 Stop switch gateway after receive SDP	SS_SIP_STOP_SWITCH_AFTER_SDP (On)	Prevent or allow gateway switching once SDP is received
🚫 Stop switching response code	—	Stop switch gateway when receiving this specific SIP code
🔄 Stop switch gateway after INVITE timeout	SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT (Off)	Control failover behavior after INVITE timeout expires

🎯 Recommended INVITE Timeout by Gateway Type

Gateway Type	Recommended INVITE Timeout	Rationale
🏢 Local LAN gateway	5–8 seconds	✅ Fast response expected; shorter timeout frees resources quickly
🌐 Standard WAN gateway	10 seconds (default)	🔧 Proven balance for typical VoIP networks
📡 High-latency / satellite	15–20 seconds	⏱️ Accounts for propagation delay and slow gateway response
🛡️ Premium carrier gateway	8–10 seconds	📞 Reliable carriers respond quickly; faster failover on failure
⚠️ Intermittent gateway	5–7 seconds	🔄 Quick failover to backup route; minimize dead air time

🚫 Stop Switching Response Code — Per-Code Control

📋 Beyond the global stop switch parameters, VOS3000 offers a more granular control: the “Stop switching response code” per-gateway setting. This lets you specify a particular SIP response code that triggers stop-switch behavior. 🎯

SIP Code	Meaning	Set as Stop Code?	Rationale
🚫 403 Forbidden	Destination not authorized	✅ Yes	Other gateways likely same result
🔍 404 Not Found	Destination does not exist	✅ Yes	Number invalid on all routes
🔧 503 Service Unavailable	Gateway overloaded	❌ No	Another gateway may accept — see our SIP 503/408 fix guide
⏱️ 408 Request Timeout	No response from gateway	❌ No	Backup gateway should be tried

🔧 Step-by-Step Configuration

🖥️ Follow these steps to configure the VOS3000 SIP INVITE timeout and gateway switching parameters:

Step 1: Configure Global INVITE Timeout 🌐

🔐 Log in to VOS3000 Client
📌 Navigate: Operation management → Softswitch management → Additional settings → SIP parameter
🔍 Locate SS_SIP_TIMEOUT_INVITE and set based on network characteristics (default: 10)
🔍 Verify SS_SIP_STOP_SWITCH_AFTER_SDP is On (default)
🔍 Verify SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT is Off (default)
💾 Save and apply

Step 2: Configure Per-Gateway Settings 🎯

📌 Navigate: Routing Gateway → Additional settings → Protocol → SIP
✏️ Set Invite timeout per gateway (leave empty for global default)
🔧 Configure Stop switch gateway after receive SDP — typically leave Default/On
🚫 Set Stop switching response code if needed (e.g., 403, 404)
🔄 Set Stop switch gateway after INVITE timeout — typically leave Default/Off
💾 Save gateway configuration

Step 3: Configure System-Level Gateway Switch Parameters ⚙️

Parameter	Default	Recommended	Notes
SS_GATEWAY_SWITCH_LIMIT	None	3–5	✅ Prevents excessive failover loops
SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START	On	On	📞 Never switch after media starts
SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY	On	On	🚫 Busy means busy on all routes typically
SS_GATEWAY_SWITCH_UNTIL_CONNECT	Off	Off	⚠️ Setting On may cause excessive switching

🛡️ Common Problems and Solutions

❌ Problem 1: Gateway Failover Not Triggering

🔍 Symptom: When the primary gateway goes down, calls fail instead of routing to the backup gateway.

💡 Cause: The “Stop switch gateway after INVITE timeout” is set to On, preventing VOS3000 from trying the next gateway.

✅ Solutions:

🔄 Set “Stop switch gateway after INVITE timeout” to Off (default) in the gateway’s SIP settings
📋 Verify your vendor failover configuration includes backup gateways
🛡️ Ensure the SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT global parameter is also Off

❌ Problem 2: Audio Disruption During Call Setup

🔍 Symptom: Callers hear ringback tone that suddenly cuts off and restarts, or brief audio glitches during call setup.

💡 Cause: SS_SIP_STOP_SWITCH_AFTER_SDP is set to Off, allowing VOS3000 to switch gateways after SDP has been received and early media is flowing.

✅ Solutions:

🛑 Set SS_SIP_STOP_SWITCH_AFTER_SDP to On (default) globally
🔧 Check per-gateway settings — ensure “Stop switch gateway after receive SDP” is not Off
📞 Verify SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START is On

❌ Problem 3: Callers Hear Long Dead Air Before Failure

🔍 Symptom: Callers hear 15-20 seconds of silence before getting a busy or failure tone.

💡 Cause: The VOS3000 SIP INVITE timeout is set too high, causing the softswitch to wait unnecessarily long.

✅ Solutions:

⏱️ Reduce the INVITE timeout to 8-10 seconds for standard gateways
🎯 For local gateways, set per-gateway timeout to 5 seconds
🔄 Ensure failover is enabled so backup gateways are tried quickly
📊 Monitor your call termination reasons to identify patterns

📊 Complete Parameter Reference

Parameter	Default	Unit	Purpose
SS_SIP_TIMEOUT_INVITE	10	Seconds	SIP INVITE timeout — total wait for INVITE response
SS_SIP_RESEND_INTERVAL	0.5,1,2,4,4,4,4,4,4,4	Seconds	INVITE retransmission intervals
SS_SIP_STOP_SWITCH_AFTER_SDP	On	On/Off	Stop gateway switching after SDP received
SS_SIP_USER_AGENT_STOP_SWITCH_AFTER_INVITE_TIMEOUT	Off	On/Off	Stop gateway switching after INVITE timeout
SS_GATEWAY_SWITCH_LIMIT	None	Number	Max gateway switching attempts
SS_GATEWAY_SWITCH_STOP_AFTER_RTP_START	On	On/Off	Stop switching after RTP media starts
SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY	On	On/Off	Stop switching on 486 Busy
SS_GATEWAY_SWITCH_UNTIL_CONNECT	Off	On/Off	Keep switching until 200 OK

❓ Frequently Asked Questions

❓ What is the default VOS3000 SIP INVITE timeout?

⏱️ The default VOS3000 SIP INVITE timeout is 10 seconds, configured via SS_SIP_TIMEOUT_INVITE. VOS3000 will wait up to 10 seconds for any response before considering the attempt failed. The default can be overridden per gateway in Routing Gateway > Additional settings > Protocol > SIP.

❓ What does SS_SIP_STOP_SWITCH_AFTER_SDP do?

🛑 When On (default), VOS3000 stops trying alternative gateways once it receives SDP in a provisional response (like 183 Session Progress with SDP). This prevents mid-call audio disruption, double-answer scenarios, and media path instability. When Off, VOS3000 may switch gateways even after media negotiation has begun — which is almost never desirable. Keep this On. 🔧

❓ Should I enable stop switch after INVITE timeout?

🔄 No — keep it Off (default) for most deployments. When a gateway does not respond to an INVITE, you want VOS3000 to try the next available gateway (failover). Setting it to On means VOS3000 stops switching and the call fails immediately. The only exception is compliance routing where failover to a different carrier is not permitted. 🏛️

❓ How do I prevent infinite gateway switching loops?

🔢 Set SS_GATEWAY_SWITCH_LIMIT to a reasonable value (3–5 gateway attempts). This prevents VOS3000 from endlessly cycling through gateways when all are failing. Also keep SS_GATEWAY_SWITCH_UNTIL_CONNECT Off (default) and ensure SS_SIP_STOP_SWITCH_AFTER_SDP is On (default). 🛡️

📞 Need Expert Help?

🔧 Proper VOS3000 SIP INVITE timeout and gateway switching configuration is essential for maximizing call completion rates, enabling fast gateway failover, and delivering a quality caller experience. Whether you need help with timeout tuning, stop switch configuration, or troubleshooting failover issues, our team is ready to assist. 🛡️

💬 WhatsApp: +8801911119966 | 📞 Phone: +8801911119966

📞 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

VOS3000 SIP Resend Interval: Important Message Retransmission Guide

April 20, 2026April 20, 2026 king

VOS3000 SIP Resend Interval: Important Message Retransmission Guide

🔄 Are failed SIP messages causing dropped calls and frustrated customers? The VOS3000 SIP resend interval is the critical parameter that controls how your softswitch retries unanswered SIP messages — and getting it wrong means the difference between reliable calls and silent failures. 📞

⚙️ When VOS3000 sends a SIP INVITE and receives no response, it doesn’t just give up. The softswitch follows a carefully designed exponential backoff retransmission pattern defined by SS_SIP_RESEND_INTERVAL. Each retry waits longer than the last, giving the remote gateway time to process while avoiding network flooding. If all retries fail, VOS3000 triggers gateway failover — automatically trying another route or hanging up the call.

🎯 This guide covers everything you need to know about the VOS3000 SIP resend interval: default values, how exponential backoff works, configuration steps, troubleshooting retransmission failures, and best practices to maximize call reliability across your VoIP network.

📡 What Is VOS3000 SIP Resend Interval?

⏱️ The VOS3000 SIP resend interval defines the time intervals (in seconds) that the softswitch waits before retransmitting an unacknowledged SIP message. It is configured through the SS_SIP_RESEND_INTERVAL parameter.

💡 Why retransmission matters: SIP uses UDP as its default transport — a connectionless protocol with no built-in delivery guarantee. If a SIP message is lost due to network congestion, firewall issues, or gateway overload, the only way to recover is through retransmission. The VOS3000 SIP resend interval controls exactly how this recovery happens:

🔄 Retransmits unacknowledged SIP messages at increasing intervals
📈 Follows an exponential backoff pattern for network efficiency
❌ Stops retrying after all intervals are exhausted
🔀 Triggers gateway failover or call failure when retries are exceeded
🛡️ Ensures call reliability even in unstable network conditions

📍 Location in VOS3000 Client: Navigation → Operation management → Softswitch management → Additional settings → SIP parameter

📋 SS_SIP_RESEND_INTERVAL — Core Parameter Details

🔧 Here is the exact specification from the VOS3000 2.1.9.07 official manual (Table 4-3, Section 4.3.5.2):

Attribute	Value
📌 Parameter Name	SS_SIP_RESEND_INTERVAL
🔢 Default Value	0.5,1,2,4,4,4,4,4,4,4
📐 Unit	Seconds (comma-separated, up to 10 intervals)
📝 Description	Resend SIP Message Interval (Second). If got no response or confirm within the time, Softswitch will resend SIP message. If exceeded the retry times, Softswitch will stop sending and regard as call failure, then try another gateway or hang up.
🎯 Format	Comma-separated seconds (up to 10 intervals)

🔄 How VOS3000 SIP Resend Interval Exponential Backoff Works

📊 The default value 0.5,1,2,4,4,4,4,4,4,4 follows a classic exponential backoff pattern that doubles the wait time for the first three retries, then caps at 4 seconds for the remaining attempts. Let’s break down exactly what happens:

📈 Default Retransmission Timeline

Retry #	Wait Time	Cumulative Time	Phase
Original Send	0s	0.0s	📡 Initial transmission
1st Retry	0.5s	0.5s	🔄 Quick retry
2nd Retry	1.0s	1.5s	📈 Backoff doubling
3rd Retry	2.0s	3.5s	📈 Backoff doubling
4th Retry	4.0s	7.5s	🔒 Capped at 4s
5th Retry	4.0s	11.5s	🔒 Capped at 4s
6th Retry	4.0s	15.5s	🔒 Capped at 4s
7th Retry	4.0s	19.5s	🔒 Capped at 4s
8th Retry	4.0s	23.5s	🔒 Capped at 4s
9th Retry	4.0s	27.5s	🔒 Capped at 4s
10th Retry	4.0s	31.5s	❌ Final attempt

💡 Total retry window: With the default VOS3000 SIP resend interval, the softswitch spends up to 31.5 seconds attempting to deliver a SIP message before giving up. After all 10 retries are exhausted, VOS3000 will stop sending, regard the call as failed, and then try another gateway or hang up.

🔍 Why Exponential Backoff?

🌐 The exponential backoff pattern (0.5 → 1 → 2 → 4) is a proven network reliability strategy:

⚡ Fast initial retries (0.5s, 1s) recover from momentary packet loss quickly
📈 Progressive delays (2s, 4s) give overloaded gateways time to recover
🔒 Capped interval (4s max) prevents excessively long wait times between retries
🔄 10 total attempts provides sufficient retry opportunities without indefinite waiting

⚠️ Without exponential backoff, if VOS3000 retried at a fixed interval (e.g., 1s every second), a failed gateway would be bombarded with 10 messages in 10 seconds — potentially worsening network congestion. The backoff pattern is self-regulating.

🔗 The VOS3000 SIP resend interval does not operate in isolation. It works alongside several related SIP timeout parameters that together define the complete retry and timeout behavior:

Parameter	Default	Unit	Purpose
SS_SIP_RESEND_INTERVAL	0.5,1,2,4,4,4,4,4,4,4	Seconds	🔄 Retry intervals for unacknowledged messages
SS_SIP_TIMEOUT_INVITE	10	Seconds	📞 SIP INVITE timeout
SS_SIP_TIMEOUT_TRYING	20	Seconds	📋 SIP Trying timeout
SS_SIP_TIMEOUT_RINGING	120	Seconds	📱 SIP Ringing timeout
SS_SIP_SEND_RETRY	Referenced	Count	🔁 Max number of SIP message resend trials

💡 How they interact: The VOS3000 SIP resend interval controls when each retry happens. The timeout parameters (INVITE, Trying, Ringing) define the maximum wait for different call stages. SS_SIP_SEND_RETRY controls the maximum number of retransmission attempts. Together, these parameters form a complete reliability framework. For a deeper understanding of the full SIP signaling lifecycle, see our SIP call flow guide.

🔄 VOS3000 SIP Resend Interval — Complete Retransmission Flow

📞 Understanding the exact retransmission flow is critical for troubleshooting call setup failures. Here is what happens when VOS3000 sends a SIP INVITE and receives no response:

📞 SIP INVITE Retransmission Flow:

VOS3000 ────────────────────────────────── Remote Gateway
   │                                              │
   │──── INVITE ─────────────────────────────────►│  (0.0s)
   │                                              │
   │   ... no response within 0.5s ...            │
   │                                              │
   │──── INVITE (Retry 1) ──────────────────────►│  (0.5s)
   │                                              │
   │   ... no response within 1.0s ...            │
   │                                              │
   │──── INVITE (Retry 2) ──────────────────────►│  (1.5s)
   │                                              │
   │   ... no response within 2.0s ...            │
   │                                              │
   │──── INVITE (Retry 3) ──────────────────────►│  (3.5s)
   │                                              │
   │   ... no response within 4.0s ...            │
   │                                              │
   │──── INVITE (Retry 4) ──────────────────────►│  (7.5s)
   │                                              │
   │   ... continues at 4s intervals ...          │
   │                                              │
   │──── INVITE (Retry 10 / Final) ─────────────►│  (27.5s)
   │                                              │
   │   ... no response after final retry ...      │
   │                                              │
   │   ❌ All retries exhausted!                  │
   │                                              │
   │   🔀 Option A: Try another gateway           │
   │   ──── INVITE ──────────────────────────►│  (Backup GW)
   │                                              │
   │   ❌ Option B: No backup gateway → Hang up   │
   │   ◄─── BYE / Call Failure                  │

🔀 Gateway failover: After all VOS3000 SIP resend interval retries are exhausted, the softswitch attempts to route the call through an alternative gateway if one is configured. This is why proper vendor failover setup is essential for high-availability VoIP networks.

🔧 Configuring VOS3000 SIP Resend Interval — Step by Step

🖥️ Follow these steps to configure or modify the VOS3000 SIP resend interval:

Step 1: Navigate to SIP Parameters 📋

🔐 Log in to VOS3000 Client
📌 Navigate: Operation management → Softswitch management → Additional settings → SIP parameter
🔍 Locate SS_SIP_RESEND_INTERVAL in the parameter list

Step 2: Understand the Format 📝

📊 The SS_SIP_RESEND_INTERVAL accepts a comma-separated list of up to 10 values, each representing the wait time in seconds before the next retransmission:

Format Rule	Detail
📏 Maximum intervals	10 comma-separated values
📐 Unit	Seconds (supports decimal, e.g., 0.5)
🔢 Order	First value = wait before 1st retry, etc.
✅ Pattern	Exponential backoff recommended
⚠️ Fewer than 10 values	Fewer retry attempts (reduces total retry window)

Step 3: Choose the Right Configuration 🎯

💡 Different deployment scenarios benefit from different VOS3000 SIP resend interval configurations:

Deployment Type	Recommended Value	Total Window	Rationale
🏢 Standard (default)	0.5,1,2,4,4,4,4,4,4,4	31.5s	✅ Proven balance for most networks
📡 Unstable networks	0.5,1,2,4,8,8,8,8,8,8	55.5s	🔧 Longer backoff for slow gateways
⚡ Fast failover	0.5,1,2,4,4,4	15.5s	🚀 Quick fail, switch to backup GW
🔒 High reliability	1,2,4,4,4,4,4,4,4,4	35.0s	🛡️ Slightly longer initial wait
📞 Aggressive retry	0.5,0.5,1,1,2,2,4,4,4,4	23.0s	🔥 More early attempts, less total time

⚠️ Important: Reducing the number of intervals (e.g., from 10 to 6) means fewer retry attempts. This speeds up failover but may reduce recovery from transient packet loss. Always test changes in a staging environment before applying to production.

📊 VOS3000 SIP Resend Interval — Impact on Call Reliability

🎯 The VOS3000 SIP resend interval directly affects your call completion rate and post-dial delay. Here’s how different configurations impact key metrics:

Metric	Short Interval (Fast Fail)	Default Interval	Long Interval (High Retry)
⏱️ Post-dial delay	⚡ Low (15.5s max)	📊 Medium (31.5s max)	🐌 High (55.5s+ max)
📞 Call success rate	⚠️ Lower on flaky nets	✅ Balanced	🛡️ Higher on flaky nets
🔀 Failover speed	🚀 Fast	📊 Moderate	🐌 Slow
📊 Signaling overhead	📉 Lower (fewer msgs)	📊 Medium	📈 Higher (more msgs)
💻 CPU load	📉 Lower	📊 Moderate	📈 Higher

💡 Key insight: The default VOS3000 SIP resend interval (0.5,1,2,4,4,4,4,4,4,4) is optimized for the majority of VoIP deployments. Only modify it if you have a specific, measurable problem with call setup reliability or post-dial delay.

🔀 VOS3000 SIP Resend Interval and Gateway Failover

🌐 When all retransmission attempts in the VOS3000 SIP resend interval are exhausted, the softswitch’s next action depends on your call routing configuration:

🎯 Failover Decision Flow

🔀 After All Retransmission Attempts Exhausted:

   ┌─── Is a backup gateway configured? ───┐
   │                                        │
   YES                                      NO
   │                                        │
   ▼                                        ▼
┌─────────────────┐              ┌──────────────────┐
│ 🔀 Try next     │              │ ❌ Call failure   │
│ gateway in      │              │ Hang up the call  │
│ routing table   │              │ Log as failed     │
└────────┬────────┘              └──────────────────┘
         │
         ▼
┌─────────────────┐
│ 📡 Send new     │
│ INVITE to       │
│ backup gateway  │
│ (resend interval│
│ restarts)       │
└─────────────────┘

🔧 Critical point: When VOS3000 switches to a backup gateway, the VOS3000 SIP resend interval restarts from the beginning. This means the total call setup time could be up to 31.5 seconds × number of gateways before a final failure. This is why the fast-failover configuration (6 intervals = 15.5s max) is preferred when multiple backup gateways are available.

📞 Need help configuring gateway failover? See our complete vendor failover setup guide or contact us on WhatsApp at +8801911119966.

🛡️ Common VOS3000 SIP Resend Interval Problems and Solutions

⚠️ Misconfigured resend intervals can cause serious call quality issues. Here are the most common problems and their solutions:

❌ Problem 1: Excessive Post-Dial Delay

🔍 Symptom: Callers wait 30+ seconds before hearing ringback or a failure tone.

💡 Cause: The default VOS3000 SIP resend interval with 10 retries takes up to 31.5 seconds. If the primary gateway is consistently unreachable, callers experience a long silent wait before failover.

✅ Solutions:

⚡ Reduce the number of intervals to 6 (e.g., 0.5,1,2,4,4,4) for faster failover
🔀 Ensure backup gateways are configured for automatic vendor failover
🔧 Lower SS_SIP_TIMEOUT_INVITE from 10 to a shorter value if appropriate
📊 Monitor gateway response times and remove consistently slow gateways

❌ Problem 2: Calls Failing on Reliable Gateways

🔍 Symptom: Calls to gateways that are known to be working are still failing.

💡 Cause: The VOS3000 SIP resend interval may be too short, and the gateway needs more processing time before responding. Some carrier gateways take 3-5 seconds to process INVITE messages during peak hours.

✅ Solutions:

📈 Increase the initial backoff: use 1,2,4,4,4,4,4,4,4,4 instead of 0.5,1,2,4,4,4,4,4,4,4
🔧 Verify the gateway is responding at all — use our SIP debug guide
📊 Check for firewall or SIP ALG issues blocking SIP responses
📞 Confirm the gateway’s IP and port are correctly configured in gateway configuration

❌ Problem 3: High Signaling Overhead

🔍 Symptom: Excessive SIP traffic on the network, high CPU usage on VOS3000 server.

💡 Cause: If many calls are failing simultaneously, the VOS3000 SIP resend interval generates up to 10 retransmissions per failed INVITE. On a system with hundreds of concurrent call attempts to a downed gateway, this creates a signaling storm.

✅ Solutions:

⚡ Use fewer intervals (6 instead of 10) to reduce total messages per failure
🔀 Configure call routing to quickly detect and bypass downed gateways
📊 Monitor gateway health and proactively disable failing routes
🔧 Consider SS_SIP_SEND_RETRY settings to limit overall retransmission count

💡 VOS3000 SIP Resend Interval Best Practices

🎯 Follow these best practices to optimize your VOS3000 SIP resend interval configuration:

Best Practice	Recommendation	Reason
🎯 Start with defaults	0.5,1,2,4,4,4,4,4,4,4	Proven for most VoIP deployments
🔀 Configure backup gateways	Always have failover routes	Retries alone cannot fix a dead gateway
📊 Monitor CDR data	Track call failure rates per gateway	Identifies systemic reachability issues
⚡ Use fast failover	6 intervals for multi-gateway routes	Reduces post-dial delay with backups
🔒 Keep exponential backoff	Never use flat intervals like 1,1,1,1	Prevents network congestion storms
📝 Test before production	Validate with SIP debug tools	Avoids unexpected call drops
📡 Check network health	Monitor packet loss and latency	Retransmission is not a fix for bad networks

💡 Pro tip: The VOS3000 SIP resend interval works in conjunction with your parameter description settings. Make sure SS_SIP_TIMEOUT_INVITE, SS_SIP_TIMEOUT_TRYING, and SS_SIP_TIMEOUT_RINGING are also configured appropriately for your network conditions. These timeout values set the maximum wait at each call stage, while the resend interval controls the retry pattern within those stages.

🔍 Verifying VOS3000 SIP Resend Interval Operation

📝 After configuring the VOS3000 SIP resend interval, verify it works correctly using SIP debug tools:

Step-by-Step Verification 🔧

# Verifying SIP Retransmission with VOS3000 SIP Debug

1. 📌 Enable SIP debug in VOS3000 Client
   Navigation → Operation management → Softswitch management
   → Additional settings → SIP parameter → Debug options

2. 🔍 Make a test call to a known-unreachable gateway
   This forces retransmission attempts

3. 📊 Observe the SIP message timestamps:
   - INVITE sent at T=0.0s
   - INVITE retransmit at T=0.5s  (1st retry)
   - INVITE retransmit at T=1.5s  (2nd retry)
   - INVITE retransmit at T=3.5s  (3rd retry)
   - INVITE retransmit at T=7.5s  (4th retry)
   - ... continues at 4s intervals

4. ✅ Verify the intervals match your SS_SIP_RESEND_INTERVAL config

5. ❌ After final retry, check for:
   - 🔀 Gateway failover (INVITE to backup GW), OR
   - 📞 Call failure recorded in CDR

🔧 For detailed instructions on capturing and analyzing SIP traffic, see our comprehensive VOS3000 SIP debug guide.

📊 VOS3000 SIP Resend Interval vs. SIP Timeout Parameters

🎯 Many administrators confuse the VOS3000 SIP resend interval with SIP timeout parameters. Here’s a clear comparison:

Aspect	SS_SIP_RESEND_INTERVAL	SIP Timeout Parameters
🎯 Purpose	When to retry sending	Maximum total wait time
📐 Format	Multiple comma-separated values	Single value per parameter
🔄 Pattern	Exponential backoff	Fixed countdown
❌ On expiry	Stop sending, failover or hang up	Terminate the call stage
🔗 Relationship	Controls retry timing	Defines maximum wait per stage

💡 In practice: The VOS3000 SIP resend interval determines the retry schedule, while timeout parameters like system parameters SS_SIP_TIMEOUT_INVITE set the absolute maximum time VOS3000 will wait at each call stage. Both must be configured in harmony.

❓ Frequently Asked Questions

❓ What is the default VOS3000 SIP resend interval?

⏱️ The default VOS3000 SIP resend interval is 0.5,1,2,4,4,4,4,4,4,4 seconds. This means VOS3000 will wait 0.5 seconds before the first retransmission, 1 second before the second, 2 seconds before the third, and then 4 seconds before each subsequent retry. With all 10 intervals, the total retry window is approximately 31.5 seconds.

❓ Can I reduce the number of retry intervals below 10?

✅ Yes. The SS_SIP_RESEND_INTERVAL parameter accepts up to 10 comma-separated values. You can provide fewer values (e.g., 0.5,1,2,4,4,4) to reduce the total retry window and speed up gateway failover. With 6 intervals, the total window is 15.5 seconds instead of 31.5 seconds, which means faster switching to backup gateways.

❓ What happens after all VOS3000 SIP resend interval retries are exhausted?

🔀 When all retransmission attempts fail, VOS3000 stops sending the SIP message and regards the call as a failure. It then attempts to try another gateway if a backup route is configured in the call routing table. If no alternative gateway is available, VOS3000 hangs up the call and records it as a call failure in the CDR. This behavior is essential for maintaining call reliability in call end reasons analysis.

❓ Should I change the VOS3000 SIP resend interval from its default?

💡 In most cases, the default value works well and should not be changed without a specific reason. Consider modifying it only if you experience: (1) excessive post-dial delay with unreachable gateways — reduce intervals; (2) calls failing on slow but reliable gateways — increase initial intervals; (3) high signaling overhead from mass failures — reduce interval count. Always test changes before deploying to production.

❓ How does the VOS3000 SIP resend interval interact with SS_SIP_SEND_RETRY?

🔧 The SS_SIP_SEND_RETRY parameter controls the maximum number of SIP message resend trials, while SS_SIP_RESEND_INTERVAL controls the timing between each retry. Think of SS_SIP_SEND_RETRY as the “how many times” and SS_SIP_RESEND_INTERVAL as the “when.” Both must be configured consistently — if SS_SIP_SEND_RETRY limits retries to fewer than the number of intervals defined, the remaining intervals will never be used.

❓ Does the VOS3000 SIP resend interval apply to all SIP messages?

📞 The VOS3000 SIP resend interval applies to SIP messages that require a response (such as INVITE). When VOS3000 sends a message and receives no confirmation or response within the specified interval, it retransmits the message. The retransmission pattern follows the same exponential backoff sequence defined in SS_SIP_RESEND_INTERVAL for all applicable SIP message types. For a complete overview of the SIP message lifecycle, see our SIP session guide.

❓ How do I troubleshoot VOS3000 SIP resend interval issues?

🔍 Start by enabling SIP debug and capturing the retransmission timestamps. Verify that the intervals between retransmitted messages match your SS_SIP_RESEND_INTERVAL configuration. If messages are being retransmitted but no response is ever received, the issue is likely with the remote gateway — check firewall rules, network routing, and gateway configuration. Use our troubleshooting guide for systematic diagnosis. You can also reach our support team on WhatsApp at +8801911119966.

📞 Need Expert Help with VOS3000 SIP Resend Interval?

🔧 Configuring the VOS3000 SIP resend interval correctly is critical for maximizing call completion rates and minimizing post-dial delay. Whether you need help tuning retransmission parameters, setting up gateway failover, or diagnosing call setup failures, our team is ready to assist.

💬 WhatsApp: +8801911119966 — Get instant support for VOS3000 SIP resend interval configuration, exponential backoff tuning, and VoIP network reliability optimization.

🔗 VOS3000 SIP Call Flow — Complete SIP signaling lifecycle and message flow
🔗 VOS3000 SIP Debug Guide — Troubleshoot SIP retransmission and signaling issues
🔗 VOS3000 SIP Session — SIP session management and timer configuration
🔗 VOS3000 Parameter Description — Complete parameter reference guide
🔗 VOS3000 System Parameters — System-level configuration parameters
🔗 VOS3000 Call Routing — Routing table and gateway selection
🔗 VOS3000 Call Termination Reasons — Understand why calls fail
🔗 VOS3000 Call End Reasons — Analyze call completion and failure patterns
🔗 VOS3000 Vendor Failover Setup — Configure backup gateway switching
🔗 VOS3000 Troubleshooting Guide 2026 — Comprehensive VoIP problem solving
🔗 VOS3000 Installation — Fresh deployment and setup guide
🔗 VOS3000 Billing System — Billing and CDR configuration
🔗 VOS3000 Gateway Configuration Routing Mapping — Gateway setup and route mapping
🔗 VOS3000 Official Downloads — Official software and documentation

📞 Still have questions about the VOS3000 SIP resend interval? Reach out on WhatsApp at +8801911119966 — we provide professional VOS3000 installation, configuration, and support services worldwide. 🌐

📞 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

VOS3000 ASR Cost Routing Order Strategic SS_GATEWAY_ASR_ROUTE_SORT_CONFIG

Table of Contents

🔐 What Is the VOS3000 ASR Cost Routing Order?

📊 The VOS3000 Routing Sort Algorithm

📋 ASR Route Sort Config Parameter Reference

💰 Fee Rate Route Sort Config Parameter Reference

🔄 Fee Rate Before ASR Tiebreaker Parameter Reference

📊 Strategic Configuration Scenarios

📊 Quality-First Strategy: ASR Priority

💰 Cost-First Strategy: Margin Priority

⚖️ Balanced Strategy: Quality with Cost Awareness

📊 ASR Cost Routing Sort Position Impact Analysis

🛡️ Common ASR Cost Routing Order Problems and Solutions

❌ Problem 1: ASR Sorting Not Taking Effect

❌ Problem 2: Cost Routing Selects Low-Quality Gateways

❌ Problem 3: All Calls Going to Same Gateway Despite Multiple Routes

💡 ASR vs Cost Routing Order Best Practices

❓ Frequently Asked Questions

❓ What is the default value of SS_GATEWAY_ASR_ROUTE_SORT_CONFIG?

❓ What happens when both ASR and Rate sort are at the same position?

❓ Does the ASR sort position affect gateways without ASR calculation enabled?

❓ Can I configure different sort orders for different destinations?

❓ How do I know if my ASR cost routing order is working correctly?

❓ Should I use ASR-first or cost-first routing?

📞 Need Expert Help with VOS3000 ASR Cost Routing Order?

📞 Need Professional VOS3000 Setup Support?

VOS3000 Prefix Mode Extension Expiration Smart Gateway Selection Method

Table of Contents

🔐 What Is VOS3000 Prefix Mode?

📊 The Four VOS3000 Prefix Modes

📋 VOS3000 Prefix Mode Configuration Location

🔄 Extension Mode: Shorter Prefixes Will Be Tried

🚫 Expiration Mode: No More Prefixes Will Be Tried

📊 Terminal and Continual Modes

🔴 Terminal Mode: Same-Length Prefixes Only

🟢 Continual Mode: All Prefixes Tried

📊 Complete Prefix Mode Comparison Table

📋 Prefix Mode and Number Transformation

🛡️ Common Prefix Mode Problems and Solutions

❌ Problem 1: Calls Not Falling Back to Backup Routes

❌ Problem 2: Unexpected Billing Rates After Fallback

❌ Problem 3: Excessive PDD from Deep Prefix Cascading

💡 Prefix Mode Configuration Best Practices

❓ Frequently Asked Questions

❓ What is the difference between Extension and Continual prefix modes?

❓ When should I use Expiration mode instead of Extension mode?

❓ How does prefix mode interact with SS_GATEWAY_SWITCH_LIMIT?

❓ Does changing prefix mode affect existing calls?

❓ Can different gateways have different prefix modes?

❓ How does prefix mode affect the routing gateway sort order?

📞 Need Expert Help with VOS3000 Prefix Mode Configuration?

📞 Need Professional VOS3000 Setup Support?

ARTICLE CONTENT

VOS3000 Real-Time Gateway ASR Advanced SS_GATEWAY_ASR_CALCULATE Configuration

Table of Contents

🔐 What Is VOS3000 Real-Time Gateway ASR?

📋 SS_GATEWAY_ASR_CALCULATE Parameter Reference

⏱️ SS_GATEWAY_ASR_RESERVE_TIME Parameter Reference

🔢 SS_GATEWAY_ASR_RESERVE_SEPARATE Parameter Reference

📊 RESERVE_TIME and RESERVE_SEPARATE Configuration Examples

🔄 Per-Gateway ASR Configuration

📊 ASR Calculation and Routing Quality Monitoring

🛡️ Common Real-Time ASR Problems and Solutions

❌ Problem 1: ASR Values Are Unstable or Noisy

❌ Problem 2: ASR Calculation Not Affecting Routing

❌ Problem 3: High Memory Usage with Many ASR-Enabled Gateways

💡 Real-Time Gateway ASR Best Practices

❓ Frequently Asked Questions

❓ What is the default value of SS_GATEWAY_ASR_CALCULATE?

❓ What is the difference between RESERVE_TIME and RESERVE_SEPARATE?

❓ Does enabling ASR calculation affect system performance?

❓ How does ASR calculation interact with the routing sort order?

❓ Can I calculate ASR per prefix or destination instead of per gateway?

❓ How quickly does ASR respond to a gateway failure?

📞 Need Expert Help with VOS3000 Real-Time Gateway ASR?

📞 Need Professional VOS3000 Setup Support?

VOS3000 Busy Stop Switch Reliable SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSY

Table of Contents

🔐 What Is the VOS3000 Busy Stop Switch?

📊 Why Continuing to Switch After Busy Wastes Resources