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. 💡
Table of Contents
🔐 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. 📡
🛡️ Related System Parameters for Gateway Switching
📋 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
 | | |
