VOS3000 Black White List Groups, VOS3000 System White List, VOS3000 Callee Balance Verification, VOS3000 Dial Plan Wildcards, VOS3000 Number Length Matching, VOS3000 Random Routing Patterns, VOS3000 Position Keeper Dollar, VOS3000 LRN Number Portability, VOS3000 LRN Numbers

VOS3000 Dial Plan Wildcards: Complete Asterisk Question Mark Pattern Easy Guide

April 28, 2026April 28, 2026 king

VOS3000 Dial Plan Wildcards: Complete Asterisk Question Mark Pattern Guide

📞 Every VOS3000 deployment relies on dial plans to transform phone numbers as calls flow through the softswitch. Whether you need to add area codes, strip prefixes, or rewrite entire number sequences, VOS3000 dial plan wildcards give you the pattern-matching power to do it precisely and efficiently. The two wildcard characters — asterisk (*) and question mark (?) — are the foundation of flexible number transformation in VOS3000, and understanding how they work is essential for any VoIP engineer configuring routing rules. 🔧

⚙️ The asterisk wildcard matches any number of digits (including zero), making it ideal for catch-all rules that apply regardless of the dialed number length. The question mark wildcard matches exactly one digit, giving you fine-grained control when you need to match specific number patterns with positional precision. Together, these VOS3000 dial plan wildcards enable sophisticated number transformation rules that handle national dialing conventions, international prefix manipulation, and gateway-specific number formatting requirements. 📊

🎯 This guide covers every aspect of VOS3000 dial plan wildcards: how the asterisk and question mark characters match digits in original prefix patterns, how they interact with target prefix replacement rules, how VOS3000 resolves conflicts between overlapping dial plans using longest-match priority, and practical configuration examples for common VoIP routing scenarios. Need expert help? WhatsApp us at +8801911119966 for professional VOS3000 configuration support. 📞

🔐 What Are VOS3000 Dial Plan Wildcards?

⏱️ VOS3000 dial plan wildcards are special characters used in the Original Prefix field of dial plan rules to match variable digit patterns in dialed numbers. The VOS3000 softswitch evaluates incoming call numbers against dial plan rules, and when a match is found, it applies the corresponding Target Prefix transformation. The wildcard characters extend this matching capability beyond exact digit-to-digit comparison, enabling a single dial plan rule to cover an entire range of number patterns. 📞

💡 Why wildcards matter: Without wildcard matching, you would need to create a separate dial plan rule for every possible number prefix — an impractical approach when dealing with thousands of area codes, mobile prefixes, or international dialing patterns. Wildcards let you express complex matching logic in a single rule, reducing configuration complexity and making your dial plan table manageable and maintainable.

📍 Location in VOS3000 Client: Operation management → Gateway operation → Routing gateway → Dial plan (also available in Mapping gateway and Phone dial plans)

📋 The Two VOS3000 Dial Plan Wildcards Characters

🌐 VOS3000 supports exactly two wildcard characters for pattern matching in dial plans, each with distinct matching behavior:

Wildcard	Name	Matching Behavior	Use Case
*	Asterisk (star)	Matches any number of digits, including zero digits	Catch-all rules, add/remove/replace entire prefixes
?	Question mark	Matches exactly one digit (0-9)	Positional matching where a specific digit position is variable

🔑 Key distinction: The asterisk (*) is greedy — it consumes as many digits as possible in the match. The question mark (?) is precise — it matches exactly one digit and no more. You can use multiple question marks in a row (e.g., ???) to match exactly three digits, but you cannot control the specific digit value — each ? matches any single digit from 0 to 9.

⚙️ Asterisk Wildcard (*) — Match Any Number of Digits

🔧 The asterisk wildcard is the most powerful and most frequently used of the VOS3000 dial plan wildcards. In the Original Prefix field, the asterisk matches any sequence of digits — including an empty sequence. This means a dial plan with Original Prefix “*” will match every possible dialed number, making it the ultimate catch-all rule.

According to the official VOS3000 2.1.9.07 manual §4.3.1, the following examples demonstrate asterisk wildcard behavior in dial plans:

Original Prefix	Target Prefix	Input Number	Result	Explanation
*	025*	117	025117	Add prefix 025 before any number
*	(empty)	02584316146	(empty)	Delete entire number
*	12345678	02584316146	12345678	Replace entire number with fixed value
025*	010	02584316146	010	Replace 025-prefixed number with 010
025*	010*	02584316146	01002584316146	Add prefix 010 while keeping 025 prefix

💡 How the asterisk preserves digits: When you use the asterisk in both the Original Prefix and Target Prefix, the digits matched by the asterisk in the original number carry through to the target. For example, Original Prefix “025*” matches “02584316146” where the asterisk matches “84316146”. In Target Prefix “010*”, the “010” is the new prefix and the “*” carries forward the matched digits “84316146”, producing “01084316146”. This is documented in the VOS3000 manual §4.3.1. For SIP protocol standards, refer to RFC 3261.

📋 Asterisk Wildcard Priority Rules

⚠️ The VOS3000 dial plan wildcards follow strict priority rules when multiple dial plan rules could match the same number. Understanding these rules is critical to avoid unexpected number transformations:

Rule	Description	Example
Longest match wins	When multiple dial plans match, the one with the longest original prefix is selected	“010” wins over “0” for number 01012345678
* has lowest priority	The asterisk wildcard pattern is only matched when no other specific pattern matches	“025*” matches only if no more specific “0258” rule exists
Exact match is highest	An exact prefix without wildcards always takes precedence over wildcard patterns of the same length	“025” exact beats “02?” wildcard

🔑 Practical implication: You can safely create a catch-all “*” rule as a default transformation while adding more specific rules for particular prefixes. VOS3000 will always prefer the more specific rule. This layered approach is the recommended way to structure your dial plan configuration — a broad default with narrow exceptions.

❓ Question Mark Wildcard (?) — Match Exactly One Digit

🎯 The question mark wildcard in VOS3000 dial plan wildcards matches exactly one digit at a specific position. This gives you positional control that the asterisk cannot provide. While the asterisk is broad and greedy, the question mark is narrow and precise — it matches any single digit from 0 to 9, but only one digit in that exact position.

According to the VOS3000 manual §4.3.1, the question mark can appear multiple times in a single pattern, and each occurrence matches an independent digit. The following example from the manual illustrates this behavior:

Original Prefix	Target Prefix	Input Number	Result	Explanation
0??8431	8431	02584316146	84316146	Two ? wildcards match any two digits between 0 and 8431
*	12345?78	02584316146	12345178 (or similar)	? in target prefix becomes a random digit

💡 Question mark in target prefix: When the question mark appears in the Target Prefix field, it generates a random digit (0-9) at that position. This is different from the Original Prefix usage where it matches an existing digit. This distinction is crucial — in the original prefix, ? matches any digit; in the target prefix, ? produces a random digit. This feature is documented in §4.3.1 of the VOS3000 manual.

📋 Common Question Mark Pattern Examples

Pattern	Matches	Does NOT Match	Scenario
0??8431	0258431…, 0138431…, 0998431…	08431… (only one digit after 0)	Area codes with two-digit variable middle
00?	001, 002, 003… 009	00, 0012 (too many/few digits)	International prefix with single country digit
13???????	1301234567, 1398765432	13, 13012 (too short)	Mobile number pattern with fixed prefix

🖥️ Combined Wildcard Patterns with Semicolons and Ranges

🔄 The VOS3000 dial plan wildcards become even more powerful when combined with semicolon-separated targets and numeric ranges. The VOS3000 manual §4.3.1 documents that multiple substitution targets can be specified using the semicolon (;) separator, and ranges can be expressed using a dash (-) between numbers.

Original Prefix	Target Prefix	Input Number	Possible Results	Explanation
025*	8008100-8008121	02584316146	8008100 to 8008121 (randomly selected)	Range generates numbers from 8008100 to 8008121
*	12345678;8008100-8008121;12345?78	02584316146	12345678 or 8008100-8008121 or 12345?78	Randomly chooses one of the three rules, then applies

💡 Semicolon behavior: When the target prefix contains semicolons, VOS3000 randomly selects one of the semicolon-separated rules at call time. This enables load-balanced number distribution across multiple target numbers — a technique frequently used for distributing inbound calls across multiple service numbers or hunt groups. Combined with VOS3000 dial plan wildcards, this creates powerful routing patterns.

📋 Step-by-Step VOS3000 Dial Plan Wildcards Configuration

🖥️ Follow these steps to configure dial plan wildcard rules on a routing gateway, based on the VOS3000 2.1.9.07 manual §4.3.1:

Step 1: Access the Dial Plan Configuration 🌐

🔐 Log in to VOS3000 Client
📌 Navigate: Operation management → Gateway operation → Routing gateway
🔍 Select the target routing gateway
📋 Go to the Dial plan tab in the gateway’s configuration

Step 2: Create Asterisk Wildcard Rules ⏰

➕ Click Add to create a new dial plan row
📝 In the Original Prefix field, enter the wildcard pattern (e.g., “025*” for all numbers starting with 025)
📝 In the Target Prefix field, enter the replacement pattern (e.g., “010*” to prepend 010 while preserving the rest)
💾 Save the dial plan configuration

Step 3: Create Question Mark Wildcard Rules 🎯

➕ Click Add to create a new dial plan row
📝 In the Original Prefix field, enter the positional wildcard pattern (e.g., “0??8431” to match any two digits between 0 and 8431)
📝 In the Target Prefix field, enter the replacement (e.g., “8431” to strip the leading 0 and two variable digits)
💾 Save the configuration

Step 4: Verify Dial Plan Matching Order 🔍

📊 Review all dial plan rules to ensure more specific rules appear before generic ones
🔧 Remember: VOS3000 uses longest-match priority — the rule with the longest matching original prefix wins
📞 Test with sample numbers to verify the correct transformation is applied
📈 Use the dial plan configuration guide for detailed walkthrough

🛡️ Common VOS3000 Dial Plan Wildcards Problems and Solutions

⚠️ Misconfigured dial plan wildcard rules cause incorrect number transformations and failed call routing. Here are the most common problems and their solutions:

❌ Problem 1: Wrong Dial Plan Matched — Generic Rule Overriding Specific Rule

🔍 Symptom: A number starting with “025” is being transformed by the “*” catch-all rule instead of the “025*” rule.

💡 Cause: VOS3000 always selects the dial plan with the longest matching original prefix. If your specific rule has a shorter effective match than another rule, the longer match wins.

✅ Solutions:

🔧 Make your specific rule’s original prefix longer — e.g., use “0258” instead of “025*” if you only need to match 0258-prefixed numbers
📊 Verify the longest-match priority by testing with the exact number
📞 Review the call routing configuration to understand how dial plans interact with routing

❌ Problem 2: Question Mark in Target Prefix Produces Unexpected Random Digits

🔍 Symptom: The transformed number contains random digits that were not in the original number.

💡 Cause: The question mark (?) in the Target Prefix field generates a random digit, which is different from matching an existing digit in the Original Prefix.

✅ Solutions:

🔧 If you want to preserve digits from the original number, use the asterisk (*) in both original and target prefix fields
📊 Use the dollar sign ($) position keeper to preserve specific digit positions — see our number transform guide
📞 Only use ? in target prefix when you intentionally want random digit generation

❌ Problem 3: Asterisk Catch-All Rule Deleting All Numbers

🔍 Symptom: All dialed numbers are being deleted or replaced with empty strings.

💡 Cause: A dial plan with Original Prefix “*” and an empty Target Prefix removes all digits from the number. While this is valid per the VOS3000 manual §4.3.1, it may not be your intent.

✅ Solutions:

🔧 If you want to keep the number but add a prefix, use Target Prefix “newprefix*” (e.g., “025*”)
📊 If you want to keep the number unchanged, set Original Prefix “0” and Target Prefix “0”
📞 Remove the catch-all rule entirely if no default transformation is needed

💡 VOS3000 Dial Plan Wildcards Best Practices

🎯 Follow these best practices to optimize your VOS3000 dial plan wildcards configuration for reliable number transformation:

Best Practice	Recommendation	Reason
📊 Order by specificity	Create specific rules before generic * rules	✅ Longest-match priority ensures correct rule applies
🔧 Use ? for positional matching	Use ? when you know the digit position is variable	🎯 More precise than * for known-length patterns
🔄 Test with real numbers	Verify every wildcard rule with test calls	🛡️ Prevents misrouted calls in production
📋 Document wildcard rules	Add memo comments explaining each wildcard pattern	📞 Easier troubleshooting and team collaboration
⚠️ Avoid * with empty target	Never use Original “*” with empty Target unless intentional	🛡️ Prevents accidental number deletion
📈 Combine with escape characters	Use L/E/G/F escape characters for length-based matching	🔧 Adds number-length constraints to wildcard rules

💡 Pro tip: VOS3000 dial plan wildcards work together with prefix settings and the callee rewrite rule to create a complete number transformation pipeline. Use dial plans for routing-level transformations and callee rewrite rules for account-level adjustments. For complex configurations, reach us at +8801911119966 for expert guidance. 🔧

📊 Complete VOS3000 Dial Plan Wildcard Reference

📋 Here is the complete reference table for all wildcard behaviors, sourced from the official VOS3000 2.1.9.07 manual §4.3.1:

Character	Usage Location	Behavior	Priority
* in Original Prefix	Pattern matching	Matches any number of digits (including zero)	Lowest — only matched when no other rule matches
* in Target Prefix	Replacement	Inserts the digits matched by the corresponding * in Original Prefix	N/A — substitution only
? in Original Prefix	Pattern matching	Matches exactly one digit at that position	Same as exact match length
? in Target Prefix	Replacement	Generates a random digit (0-9) at that position	N/A — substitution only

❓ Frequently Asked Questions

❓ What are VOS3000 dial plan wildcards?

⏱️ VOS3000 dial plan wildcards are special characters used in the Original Prefix and Target Prefix fields of dial plan rules to match and transform variable digit patterns. The two wildcard characters are the asterisk (*), which matches any number of digits including zero, and the question mark (?), which matches exactly one digit. These wildcards enable you to create flexible number transformation rules that handle a wide range of dialed number patterns without needing a separate rule for each possible number. They are documented in the VOS3000 2.1.9.07 manual §4.3.1.

❓ How does the asterisk wildcard work in VOS3000 dial plans?

🔧 The asterisk (*) in the Original Prefix matches any sequence of digits — from zero digits to an unlimited number. When used in the Target Prefix, it inserts the digits that were matched by the corresponding asterisk in the Original Prefix. For example, Original Prefix “025*” with Target Prefix “010*” transforms “02584316146” into “01084316146” — the asterisk in the original prefix matches “84316146” and the asterisk in the target prefix carries those digits forward after the new “010” prefix. This carry-forward behavior is the key to prefix manipulation in VOS3000 dial plans.

❓ How does the question mark wildcard work in VOS3000 dial plans?

🎯 The question mark (?) serves two different purposes depending on where it appears. In the Original Prefix, it matches exactly one digit (0-9) at that position. For example, “0??8431” matches any number starting with 0, followed by any two digits, followed by 8431. In the Target Prefix, the question mark generates a random digit (0-9) at that position. This dual behavior is important to understand — matching in the original prefix versus generating in the target prefix — as documented in the VOS3000 manual §4.3.1.

❓ What is the priority of VOS3000 dial plan wildcards?

📋 VOS3000 uses longest-match priority for dial plan selection. When multiple dial plan rules could match a given number, the rule with the longest original prefix is selected. The asterisk (*) wildcard has the lowest priority and will only be matched when no other more specific pattern matches. This means you can safely create a catch-all “*” rule as a default while adding more specific rules like “025*” or “010” for particular prefixes — VOS3000 will always prefer the more specific match.

❓ Can I combine * and ? wildcards in the same dial plan rule?

🔄 Yes, you can combine asterisk and question mark wildcards in the same dial plan rule’s Original Prefix. For example, “0??*” would match numbers starting with 0, followed by any two digits, followed by any number of additional digits. However, combining wildcards in the Target Prefix requires careful attention — the asterisk carries matched digits forward while the question mark generates random digits. Understanding the interaction between these two behaviors is essential for correct number transformation.

❓ How do VOS3000 dial plan wildcards interact with semicolons and ranges?

📊 The VOS3000 dial plan wildcards work together with semicolons and ranges in the Target Prefix field. Semicolons (;) separate multiple substitution targets — VOS3000 randomly selects one target at call time. Ranges (e.g., 8008100-8008121) define a span of numbers from which one is randomly selected. You can combine these with wildcards: for example, Target Prefix “12345678;8008100-8008121;12345?78” would randomly choose between three different transformation patterns for each call. This is documented in §4.3.1 of the VOS3000 manual.

📞 Still have questions? WhatsApp us at +8801911119966 for quick answers. 📞

📞 Need Expert Help with VOS3000 Dial Plan Wildcards?

🔧 Proper VOS3000 dial plan wildcards configuration is essential for accurate number transformation, correct call routing, and efficient prefix management across your VoIP network. Misconfigured wildcard rules lead to misrouted calls, incorrect billing prefixes, and failed call completion. Whether you need help designing wildcard patterns, configuring prefix transformation rules, or troubleshooting dial plan issues, our team is ready to assist. Reach us on WhatsApp at +8801911119966 for professional VOS3000 support and configuration services. 📞

📞 Need Professional VOS3000 Setup Support?

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

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

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 Period Capacity Configuration, VOS3000 Period Dial Plan, VOS3000 RTP Interrupt Detection, VOS3000 Lowest Profit Rate Limit, VOS3000 Max Minute Rate Cap, VOS3000 Sort Lowest Rate Per Second, VOS3000 Check Rate Before Routing, VOS3000 Sort by Lowest Rate, VOS3000 Bilateral Reconciliation, VOS3000 SIP OPTIONS Online Check, VOS3000 T38 Fax Over IP, VOS3000 G729 Annex B Silence, VOS3000 Gateway Group Reserved Lines, VOS3000 Auxiliary Ring Tone, VOS3000 Black White List Groups, VOS3000 System White List, VOS3000 Callee Balance Verification, VOS3000 Dial Plan Wildcards, VOS3000 Number Length Matching, VOS3000 Random Routing Patterns, VOS3000 Position Keeper Dollar, VOS3000 LRN Number Portability, VOS3000 LRN Numbers

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 Dial Plan Wildcards: Complete Asterisk Question Mark Pattern Guide

Table of Contents

🔐 What Are VOS3000 Dial Plan Wildcards?

📋 The Two VOS3000 Dial Plan Wildcards Characters

⚙️ Asterisk Wildcard (*) — Match Any Number of Digits

📋 Asterisk Wildcard Priority Rules

❓ Question Mark Wildcard (?) — Match Exactly One Digit

📋 Common Question Mark Pattern Examples

🖥️ Combined Wildcard Patterns with Semicolons and Ranges

📋 Step-by-Step VOS3000 Dial Plan Wildcards Configuration

Step 1: Access the Dial Plan Configuration 🌐

Step 2: Create Asterisk Wildcard Rules ⏰

Step 3: Create Question Mark Wildcard Rules 🎯

Step 4: Verify Dial Plan Matching Order 🔍

🛡️ Common VOS3000 Dial Plan Wildcards Problems and Solutions

❌ Problem 1: Wrong Dial Plan Matched — Generic Rule Overriding Specific Rule

❌ Problem 2: Question Mark in Target Prefix Produces Unexpected Random Digits

❌ Problem 3: Asterisk Catch-All Rule Deleting All Numbers

💡 VOS3000 Dial Plan Wildcards Best Practices

📊 Complete VOS3000 Dial Plan Wildcard Reference

❓ Frequently Asked Questions

❓ What are VOS3000 dial plan wildcards?

❓ How does the asterisk wildcard work in VOS3000 dial plans?

❓ How does the question mark wildcard work in VOS3000 dial plans?

❓ What is the priority of VOS3000 dial plan wildcards?

❓ Can I combine * and ? wildcards in the same dial plan rule?

❓ How do VOS3000 dial plan wildcards interact with semicolons and ranges?

📞 Need Expert Help with VOS3000 Dial Plan Wildcards?

📞 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?