The VOS3000 protect route feature is one of the most misunderstood yet powerful routing mechanisms available in the softswitch, fundamentally different from the standard priority-based failover that most operators use. While priority-based failover simply tries gateways in order from highest to lowest priority, the protect route mechanism actively excludes designated backup gateways from normal routing and only activates them when all normal gateways fail within a specific timer window. This timer-based approach is controlled by the SS_TRY_PROTECT_ROUTE_DELAY parameter (0-180 seconds), documented in VOS3000 Manual Section 4.3.5.2, and it ensures that your expensive premium backup vendors are only used as a last resort, not as part of everyday traffic routing.
This guide explains the exact difference between protect route and priority-based failover, how to configure protect route on routing gateways, and when to use each approach for optimal routing design. Every feature described here is verified in the official VOS3000 V2.1.9.07 Manual Section 2.5.1.1 (Routing Gateway Additional Settings). For professional assistance with VOS3000 routing configuration, contact us on WhatsApp at +8801911119966.
The most common mistake operators make is confusing protect route with simple priority-based failover. While both involve backup gateways, their behavior is completely different, and using one when you need the other leads to either unexpected routing patterns or wasted backup resources.
In standard VOS3000 routing, gateways are sorted by priority number, and the softswitch tries them in order during call setup. When you configure multiple routing gateways with the same prefix but different priority values, VOS3000 always attempts the highest priority gateway first. If that gateway is busy, offline, or returns an error, VOS3000 automatically tries the next gateway in priority order. This is the failover mechanism most operators use, and it is configured simply by assigning different priority numbers to gateways sharing the same prefix.
The limitation of priority-based failover is that all gateways participate in normal routing. Even your expensive backup vendor is attempted during regular call routing, which means you are paying premium rates for traffic that could be handled by cheaper primary gateways. There is no mechanism to say “only use this gateway when everything else has failed.”
The VOS3000 protect route mechanism solves this limitation by creating a distinct category of backup gateways that are completely excluded from normal gateway sorting. When you mark a routing gateway as a protect route (by checking the “Protect route” checkbox in Additional Settings > Others), VOS3000 removes it from the standard priority queue entirely. During normal call routing, VOS3000 only considers non-protect gateways. Only when all normal gateways fail to connect the call within the SS_TRY_PROTECT_ROUTE_DELAY timer does VOS3000 activate the protect route gateways as a last resort.
| 📋 Aspect | 🔄 Priority Failover | 🛡️ Protect Route |
|---|---|---|
| Gateway participation | All gateways in normal sorting | Excluded from normal sorting |
| When backup is used | When higher-priority gateway fails | Only when ALL normal gateways fail |
| Timer mechanism | No timer, immediate failover | SS_TRY_PROTECT_ROUTE_DELAY timer |
| Cost control | Backup may carry regular traffic | Backup only used as last resort |
| Configuration | Different priority numbers | Protect route checkbox in Others |
| Between protect routes | N/A | Normal sorting rules apply |
Setting up a protect route involves two steps: enabling the protect route flag on the routing gateway, and configuring the SS_TRY_PROTECT_ROUTE_DELAY timer in softswitch parameters. Both steps are required for the feature to work correctly.
Navigate to Operation Management > Gateway Operation > Routing Gateway, select the gateway you want to designate as a backup, and click Additional Settings. In the Others section (VOS3000 Manual Section 2.5.1.1, Page 50), check the “Protect route” checkbox. This immediately removes the gateway from normal routing consideration. The gateway will no longer be included in the standard priority-based sorting during call setup.
You can configure multiple gateways as protect routes for the same prefix. When protect route gateways are activated (because all normal gateways failed), VOS3000 applies its standard sorting rules among the protect route gateways themselves. This means you can have a primary backup and a secondary backup, both configured as protect routes, with different priority values controlling the order in which they are attempted.
The SS_TRY_PROTECT_ROUTE_DELAY parameter controls the timer window during which VOS3000 attempts to connect the call through normal gateways before activating protect routes. Navigate to Operation Management > Softswitch Management > Additional Settings > System Parameter and find the SS_TRY_PROTECT_ROUTE_DELAY setting, documented in VOS3000 Manual Section 4.3.5.2.
| ⚙️ Value (seconds) | 📝 Behavior | 🎯 Best For |
|---|---|---|
| 0 | Protect routes tried immediately when normal fails | Maximum uptime, cost not a concern |
| 5-10 | Brief retry on normal gateways first | Balanced approach for most deployments |
| 30 | 30 seconds of trying normal gateways | When backup vendor is expensive |
| 60-180 | Extended retry on normal gateways | Premium backup, avoid at all costs |
The value you choose depends on your business requirements. If the backup vendor charges significantly more per minute, set a longer delay to give normal gateways more time to recover. If call completion is more important than cost, set a shorter delay or use 0 for immediate activation. Note that during the delay period, the caller hears ringing or silence while VOS3000 retries normal gateways.
Understanding the exact mechanics of the protect route timer is essential for correct configuration. The timer does not simply wait for a fixed period and then try protect routes. Instead, it defines the window during which VOS3000 continues attempting to route the call through normal gateways before falling back to protect route gateways.
When a call arrives at VOS3000 and the matching prefix has both normal gateways and protect route gateways configured, the following sequence occurs:
| ⏱️ Time | 📡 Action | 📊 Result |
|---|---|---|
| 0s | INVITE to Normal GW1 (priority 1) | 503 Service Unavailable |
| 2s | INVITE to Normal GW2 (priority 2) | 408 Timeout |
| 12s | INVITE to Normal GW3 (priority 3) | 503 All lines busy |
| 12s | All normal GWs failed, timer starts | Waiting SS_TRY_PROTECT_ROUTE_DELAY |
| 42s (timer=30) | Timer expired, activate protect routes | INVITE to Protect GW1 (backup) |
| 43s | 200 OK from Protect GW1 | Call connected via backup gateway |
Understanding when to use protect route instead of priority-based failover helps you design more cost-effective and reliable routing architectures. The following use cases demonstrate the practical value of the protect route feature.
You have three standard vendors for a destination prefix with rates of $0.02, $0.025, and $0.03 per minute. You also have a premium vendor that guarantees connectivity at $0.08 per minute. Using priority-based failover, the premium vendor might be attempted during normal call routing if the three standard vendors are temporarily busy, resulting in unexpectedly high costs. By configuring the premium vendor as a protect route with SS_TRY_PROTECT_ROUTE_DELAY set to 30 seconds, you ensure that the expensive vendor is only used when all three standard vendors have been unavailable for 30 seconds, minimizing the use of premium routing while ensuring call completion.
Some VoIP operators maintain a dedicated emergency route with a trusted carrier that has a near-100% completion rate but charges a premium. This route should never be used for regular traffic because it would erode profit margins. By setting it as a protect route, it only activates during genuine outage situations when primary and secondary vendors are both down. The timer delay gives normal vendors time to recover from temporary issues, avoiding unnecessary use of the expensive emergency route.
A carrier offers you a promotional rate that is only valid for a limited number of minutes per month. You want to use this vendor as a last resort to ensure you do not exceed the promotional limit while still benefiting from the lower rate during genuine outages. Setting this vendor as a protect route ensures it is only used when normal routing options have been exhausted.
| 🎯 Use Case | ⏱️ Timer Setting | 💰 Cost Impact | 📊 Reliability |
|---|---|---|---|
| Premium backup vendor | 30-60 seconds | Minimizes premium usage | High (guaranteed connectivity) |
| Emergency route | 60-180 seconds | Very rare activation | Highest (trusted carrier) |
| Promotional vendor | 10-30 seconds | Preserves promotional minutes | Good (limited availability) |
When routing gateways are organized into gateway groups, the protect route behavior interacts with the group’s sorting and allocation rules. Understanding this interaction prevents unexpected routing patterns when protect routes are used within gateway groups.
A gateway group in VOS3000 (Section 2.5.1.3) allows you to organize multiple routing gateways into a logical group with shared settings like reserved lines and sorting rules. When a protect route gateway belongs to a gateway group, it is still excluded from the group’s normal sorting. However, when protect routes are activated, the group’s sorting rules apply among the protect route members of that group. This means you can organize your backup gateways into a specific group and control how they are sorted when activated, independent of how normal gateways are sorted within the same group.
For example, if you have a gateway group with three normal gateways and two protect route gateways, the three normal gateways are sorted by the group’s sorting rules during regular routing. The two protect route gateways are completely ignored. When all three normal gateways fail and the timer expires, the two protect route gateways are then sorted according to the same group sorting rules, and VOS3000 tries them in the resulting order. For more on gateway groups and failover, see our vendor failover fallback routing guide.
After configuring protect route, testing ensures the mechanism activates correctly when normal gateways fail. VOS3000 provides several tools for testing and monitoring protect route behavior.
To test protect route without affecting production traffic, follow these steps during a low-traffic period:
Use the VOS3000 Routing Analysis tool (right-click any routing gateway and select “Routing Analysis”) to simulate how a specific number would be routed. This tool shows you the complete gateway selection chain, including whether protect route gateways would be considered. For additional routing optimization, see our VOS3000 routing optimization guide.
| 🧪 Test Step | 📋 Action | ✅ Expected Result |
|---|---|---|
| 1. Lock normal gateways | Set Lock Type to “Bar all calls” | Gateways show locked status |
| 2. Make test call | Call a number matching the prefix | Call rings, timer starts |
| 3. Wait for timer | Wait SS_TRY_PROTECT_ROUTE_DELAY seconds | Protect route activates |
| 4. Check CDR | Query CDR for the test call | Shows protect route gateway ID |
| 5. Unlock normal gateways | Set Lock Type back to “No lock” | Normal routing restored |
Priority-based failover includes all gateways in normal routing and tries them in priority order. Protect route completely excludes designated gateways from normal routing and only activates them when all normal gateways fail within the SS_TRY_PROTECT_ROUTE_DELAY timer period. Protect route is designed for backup vendors you want to use only as a last resort, not as part of everyday traffic distribution.
SS_TRY_PROTECT_ROUTE_DELAY is a VOS3000 softswitch parameter (Section 4.3.5.2) that defines the timer window in seconds (0-180) during which VOS3000 continues trying normal gateways before activating protect route gateways. A value of 0 means protect routes are activated immediately when all normal gateways fail. Higher values give normal gateways more time to recover, reducing the use of expensive backup routes. Contact us on WhatsApp at +8801911119966 for help configuring this parameter.
Yes, you can configure multiple routing gateways as protect routes for the same prefix. When protect routes are activated, VOS3000 applies normal sorting rules among the protect route gateways. This means you can have a primary backup and a secondary backup, both as protect routes, with different priorities controlling the order in which they are attempted.
No, that is the key difference. Protect route gateways are excluded from normal gateway sorting and will never carry regular traffic. They are only activated when all normal (non-protect) gateways for the prefix have failed within the SS_TRY_PROTECT_ROUTE_DELAY timer period. This ensures your expensive backup vendors are reserved for genuine outage situations.
The easiest way to test is to temporarily lock all normal gateways for a test prefix (set Lock Type to “Bar all calls”), make a test call, and check the CDR to verify the call was routed through the protect route gateway after the timer delay. After testing, unlock the normal gateways. Use the Routing Analysis tool to simulate routing without making actual calls.
Yes, protect route works within gateway groups. Protect route gateways in a group are excluded from normal group sorting. When activated, the group’s sorting rules apply among the protect route members. This allows you to organize backup gateways in groups with specific sorting and line allocation rules that are separate from normal gateway behavior.
Configuring VOS3000 protect route and designing cost-effective routing architectures with backup gateways requires expertise in VOS3000 routing mechanisms, gateway sorting rules, and softswitch parameters. Our team has extensive experience designing carrier-grade routing infrastructures with proper failover and backup mechanisms.
Contact us on WhatsApp: +8801911119966
We offer complete VOS3000 routing design services including protect route configuration, failover architecture, gateway group optimization, and cost-based routing strategies. Whether you need help with a specific routing problem or a comprehensive routing infrastructure design, we can ensure your traffic flows reliably and cost-effectively.
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com
🌐 Blog: multahost.com/blog
📥 Downloads: VOS3000 Downloads
VOS3000 caller number pool configuration for CLI rotation on outbound calls. Setup random and poll…
VOS3000 scaling guide for high-traffic VoIP operations. Proven methods for handling thousands of concurrent calls…
VOS3000 outbound registration setup guide for carrier SIP trunk connections. Configure VOS3000 to register outbound…
VOS3000 SIP debug guide with Wireshark capture, log analysis, and tcpdump commands. Learn essential troubleshooting…
Evite perdidas por saldo negativo VOS3000: configure Anti Overdraft, limite de descubierto (limitMoney) y bloqueo…
Configuracion inicial VOS3000 despues de instalar: agregar primer proveedor, crear cuenta SIP, tabla de tarifas…