SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization
VOS3000 dial plan is a powerful feature that enables precise number transformation for routing, billing, and gateway interconnection scenarios. Understanding dial plan syntax and configuration is essential for VoIP operators who need to manipulate called numbers, handle international prefix variations, and ensure seamless interoperability between different networks and devices. This comprehensive guide covers all dial plan capabilities based on official VOS3000 2.1.9.07 documentation.
π Need help with VOS3000 dial plan? WhatsApp: +8801911119966
The dial plan in VOS3000 provides a flexible mechanism for transforming phone numbers before routing and billing. When a call is processed, VOS3000 can apply dial plan rules to modify the called number (callee) or calling number (caller) based on pattern matching and substitution rules.
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.1 (Page 219-220)
| Application Point | Location | Purpose | Affects |
|---|---|---|---|
| Mapping Gateway Dial Plan | Mapping Gateway > Additional settings | Transform incoming called number | Number before routing decision |
| Routing Gateway Dial Plan | Routing Gateway > Additional settings | Transform outgoing called number | Number sent to downstream gateway |
| Phone Dial Plan | Phone Management > Additional settings | Transform called number for phone | Number before routing from phone |
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.1 (Page 219-220)
VOS3000 dial plan supports wildcard characters for flexible pattern matching:
| Wildcard | Name | Matches | Example |
|---|---|---|---|
| * | Asterisk | Any number of any digits (including zero) | * matches any number |
| ? | Question Mark | Single random digit (in target prefix only) | 123?78 matches 123178, 123278, etc. |
| $ | Dollar Sign | Keep original digit at position (in target only) | $$$ keeps first three digits unchanged |
VOS3000 dial plan supports escape characters to specify number length constraints:
| Escape Char | Meaning | Syntax | Example |
|---|---|---|---|
| L | Length Less Than | Prefix followed by L and digit count | 13L9 matches 11-digit numbers starting with 13 |
| E | Length Equal To | Prefix followed by E and digit count | 010E7 matches exactly 10 digits starting with 010 |
| G | Length Greater Than | Prefix followed by G and digit count | 010G7 matches 11+ digits starting with 010 |
Note: Use backslash before escape character (\L, \E, \G) to remove its special meaning and match literally.
Reference: VOS3000 2.1.9.07 Manual, Table 4-1 (Page 219-220)
| Original Prefix | Target Prefix | Example Input | After Transformation | Description |
|---|---|---|---|---|
| 0 | 0 | 02584316146 | 02584316146 | No change β pass through |
| 0 | 010 | 02584316146 | 01084316146 | Change prefix 0 to 010 |
| 025 | (empty) | 02584316146 | 84316146 | Remove prefix 025 |
| * | 025* | 117 | 025117 | Add prefix 025 to all numbers |
| 025* | 010 | 02584316146 | 01084316146 | Change prefix 025 to 010 |
| 010* | (empty) | 02584316146 | 01002584316146 | Add prefix 010 (empty = append) |
| * | (empty) | 02584316146 | (empty) | Delete all numbers |
| * | 12345678 | 02584316146 | 12345678 | Replace all numbers with constant |
| 025* | 8008100-8008121 | 02584316146 | 8008100 to 8008121 | Range-based random selection |
| * | 12345?78 | 02584316146 | 12345178, 12345278, etc. | ? becomes random digit |
| 0??8431 | 8431 | 02584316146 | 84316146 | ? matches any digit in pattern |
| 0134 | $$$ | 0134131 | 013131 | $ keeps original digit position |
Reference: VOS3000 2.1.9.07 Manual, Section 4.3.1 (Page 220)
When multiple dial plan rules exist, VOS3000 uses the longest matching principle to select which rule to apply. This ensures that more specific patterns take precedence over generic ones.
| Dial Plan Rules | Input Number | Matched Rule | Result | Reason |
|---|---|---|---|---|
| 0 β 0 010 β 025 | 01012345678 | 010 β 025 | 02512345678 | 010 is longer match than 0 |
| * β 025* 01 β 00 | 0112345678 | 01 β 00 | 0012345678 | 01 is longer match than * |
| 0 β 0 01 β 025 011 β 00 | 01117654321 | 011 β 00 | 0017654321 | 011 is longest matching prefix |
Important: The pattern β*β has the lowest priority and will only be matched when no other pattern matches. This makes it useful as a βdefaultβ rule.
VOS3000 dial plan supports multiple substitution targets separated by semicolons (;). When β?β exists in the target, each β?β is replaced by a randomly generated digit.
Multiple Substitution Target Examples: ====================================== Target: 12345678;8008100-8008121;12345?78 This means randomly choose ONE of: - 12345678 (constant) - Any number from 8008100 to 8008121 (range) - 12345?78 where ? is a random digit (pattern) Result Examples: - 12345678 - 8008105 - 8008119 - 12345178 - 12345878 Use Cases: ========== 1. Load balancing across multiple destination numbers 2. A/B testing different routes 3. Redundancy with fallback numbers 4. Random selection for pool allocation
Reference: VOS3000 2.1.9.07 Manual, Section 2.5.1.1 (Page 28-32)
Step-by-Step Mapping Gateway Dial Plan Configuration: ===================================================== 1. Navigate to: Navigation > Operation management > Gateway operation > Routing gateway 2. Right-click gateway and select "Additional settings" 3. Find "Callee number transform" section: - Callee number transform: Original prefix β Target prefix - Multiple rules separated by comma 4. Example Configuration: Original: 00 Target: (empty) Effect: Remove 00 prefix from incoming calls 5. Apply changes and test Example Scenarios: ================== Scenario 1: International calls coming with 00 prefix Need to route to gateway expecting numbers without 00 Solution: Original: 00, Target: (leave empty) Scenario 2: Local calls coming without area code Need to add area code for routing Solution: Original: *, Target: 025* (adds 025 prefix to all) Scenario 3: Convert mobile prefix Solution: Original: 013, Target: 8613 (convert Chinese mobile format)
Reference: VOS3000 2.1.9.07 Manual, Section 2.5.1.1 (Page 32-39)
| Setting | Location | Purpose |
|---|---|---|
| Callee number transform | Routing Gateway > Additional settings > Dial plan | Transform called number before sending to this gateway |
| Caller number transform | Routing Gateway > Additional settings > Dial plan | Transform calling number before sending to this gateway |
| Gateway prefix | Routing Gateway > Main settings | Add prefix for routing to this gateway |
| Scenario | Original | Target | Example |
|---|---|---|---|
| Remove 00 international prefix | 00 | (empty) | 004412345678 β 4412345678 |
| Add 00 international prefix | * | 00* | 4412345678 β 004412345678 |
| Convert + to 00 | + | 00 | +4412345678 β 004412345678 |
| Add country code | * | 86* | 13812345678 β 8613812345678 |
| Scenario | Original | Target | Example |
|---|---|---|---|
| Add area code to local numbers | E8 | 025* | 84316146 β 02584316146 |
| Remove area code | 025 | (empty) | 02584316146 β 84316146 |
| Change area code | 025 | 010 | 02584316146 β 01084316146 |
Emergency Number Dial Plan Examples: ==================================== Scenario: Route emergency numbers to specific gateway 1. Emergency 911/112 routing: Create routing gateway with prefix: 911,112 Dial plan on mapping gateway: - Original: 911, Target: (empty - pass through) - Original: 112, Target: 911 (convert 112 to 911) 2. Police emergency: Original: 110 Target: (empty or specific routing number) 3. Ambulance/Medical: Original: 120 Target: (routing destination) Important Notes: ================ - Emergency numbers should have highest priority - Use specific prefixes (not wildcards) for emergency routing - Test thoroughly before production deployment
| Problem | Possible Cause | Solution |
|---|---|---|
| Number not matching expected rule | Longer pattern exists and takes precedence | Review all dial plan rules, use longest matching principle |
| Prefix not removed | Original prefix doesnβt match exactly | Verify exact prefix in CDR, adjust dial plan |
| Wrong transformation applied | Multiple rules with overlapping patterns | Check longest matching, reorder if needed |
| Billing discrepancy | Dial plan changes number after billing lookup | Verify dial plan application point (before/after billing) |
| Number becomes empty | Target prefix is empty for full match | Use correct wildcard patterns, avoid deleting entire number |
Dial Plan Testing Steps: ======================== 1. Enable Debug Trace: System > Debug trace > Check "On" 2. Make Test Call: Place call with number to test 3. View Call Analysis: CDR > Right-click failed call > Call analysis 4. Check Number Transformation: - Look for "called number" before and after transformation - Verify correct dial plan was applied 5. Check CDR: - Verify "callee billing" shows correct number - Compare with "callee access" for incoming number 6. Adjust if needed: - Modify dial plan rules - Re-test with new configuration
VOS3000 applies the longest matching principle. The dial plan rule with the longest matching prefix is selected. For example, if you have rules for β0β and β010β, the number β01012345678β will match β010β because itβs longer. The β*β wildcard has the lowest priority.
Yes, VOS3000 supports caller number transformation in routing gateway settings. Configure βCaller number transformβ in the routing gatewayβs additional settings to modify the calling party number before sending to the downstream gateway.
Enable debug trace in VOS3000, make a test call, then check the CDR and call analysis. The call analysis will show the number before and after transformation, confirming which dial plan rule was applied.
Yes, dial plan can affect billing if applied before the rate lookup. Mapping gateway dial plan transforms numbers before billing, while routing gateway dial plan transforms numbers after billing. Consider this when designing your number transformation strategy.
Gateway prefix is used for routing decisions β it determines which gateway handles the call. Dial plan transforms the actual number. Gateway prefix matching happens first for route selection, then dial plan transforms the number for the selected gateway.
Need assistance with complex dial plan configurations? Our VOS3000 experts can help you design and implement number transformation strategies for any VoIP scenario.
π± WhatsApp: +8801911119966
Contact us for VOS3000 installation, dial plan configuration, gateway setup, and professional VoIP support services!
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 protect route configuration guide for smart backup gateway activation. Learn how timer-based failover with…
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…