SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization

VOS3000 QoS Configuration: Complete Voice Quality Optimization Guide

VOS3000 QoS Configuration: Complete Voice Quality Optimization Guide

VOS3000 QoS configuration is essential for ensuring superior voice quality in enterprise and carrier VoIP deployments. By properly marking SIP signaling and RTP media packets with DSCP (Differentiated Services Code Point) values, VOS3000 enables network infrastructure to prioritize voice traffic, reducing latency, jitter, and packet loss that degrade call quality. This comprehensive guide covers all QoS features based on official VOS3000 2.1.9.07 documentation.

📞 Need help with VOS3000 QoS configuration? WhatsApp: +8801911119966

🔍 Understanding VoIP QoS

Reference: VOS3000 2.1.9.07 Manual, Section 4.1.4 (Page 214)

Quality of Service (QoS) in VoIP refers to the ability to prioritize voice traffic over data traffic on IP networks. Voice calls are highly sensitive to network conditions – even small amounts of latency, jitter, or packet loss can significantly degrade call quality. QoS mechanisms ensure voice packets receive preferential treatment.

📊 Voice Quality Requirements

MetricVoice RequirementImpact if ExceededQoS Benefit
Latency< 150ms one-wayEcho, talk-over, delayed responsePriority queuing reduces delay
Jitter< 30ms variationChoppy audio, robotic voiceConsistent queuing reduces variation
Packet Loss< 1%Clicks, pops, missing syllablesPriority treatment reduces drops
Bandwidth~30-90 kbps per callCongestion, quality degradationGuaranteed bandwidth allocation

⚙️ VOS3000 QoS Parameters

Reference: VOS3000 2.1.9.07 Manual, Section 4.1.4 (Page 214)

📊 VOS3000 QoS Configuration Parameters

ParameterDefaultDescriptionApplies To
SS_QOS_SIGNAL0xa0QoS marking for SIP signaling packetsSIP INVITE, REGISTER, BYE, etc.
SS_QOS_RTP0xa0QoS marking for RTP media packetsVoice/audio RTP streams

📐 Understanding DSCP Values

The QoS parameters use hexadecimal values that correspond to the DSCP field in the IP header:

Hex ValueBinaryDSCP NameTypical UsePriority Level
0xb8101110EF (Expedited Forwarding)Voice RTPHighest
0xa0101000CS5 (Class Selector 5)Voice SignalingHigh
0x88100010AF41Video ConferencingMedium-High
0x00000000BE (Best Effort)Regular DataDefault

📐 How VOS3000 QoS Works

Reference: VOS3000 2.1.9.07 Manual, Section 4.1.4 (Page 214)

📊 IP Header DSCP Field

IP Header QoS Field Structure:
==============================

The Differentiated Services Field in IP header:

Bits:     0   1   2   3   4   5   6   7
        +---+---+---+---+---+---+---+---+
        |   DSCP (6 bits)   |   ECN     |
        +---+---+---+---+---+---+---+---+

DSCP = Differentiated Services Code Point
ECN  = Explicit Congestion Notification

VOS3000 Default: 0xa0
======================
Binary:     10100000
DSCP bits:  101000 (DSCP 40 = CS5)
ECN bits:   00

This means:
- DSCP Class Selector 5
- High priority for signaling
- No ECN marking

Wireshark Display:
==================
Differentiated Services Field: 0xa0 (DSCP: CS5, ECN: Not-ECT)

📊 VOS3000 QoS Application

Reference: VOS3000 2.1.9.07 Manual, Section 4.1.4 (Page 214)

Packet TypeParameterDefault ValueEffect
SIP SignalingSS_QOS_SIGNAL0xa0 (CS5)Fast call setup, priority for INVITE/REGISTER
RTP MediaSS_QOS_RTP0xa0 (CS5)Clear voice, reduced jitter and loss

🔧 Configuring QoS in VOS3000

📍 Configuration Location

Navigate to: Operation management > Softswitch management > Additional settings > System parameter

⚙️ Configuration Steps (VOS3000 QoS)

Step-by-Step VOS3000 QoS Configuration:
========================================

1. Access System Parameters:
   Navigation > Operation management > Softswitch management
   > Additional settings > System parameter

2. Locate QoS Parameters:
   Find: SS_QOS_SIGNAL
   Find: SS_QOS_RTP

3. Set Signaling QoS:
   Parameter: SS_QOS_SIGNAL
   Default: 0xa0 (CS5)
   Options:
   - 0xa0 = CS5 (recommended for SIP signaling)
   - 0x00 = Best Effort (no priority)
   - 0xb8 = EF (if signaling needs highest priority)

4. Set RTP Media QoS:
   Parameter: SS_QOS_RTP
   Default: 0xa0 (CS5)
   Options:
   - 0xb8 = EF (recommended for voice RTP)
   - 0xa0 = CS5 (acceptable for voice)
   - 0x00 = Best Effort (not recommended)

5. Apply Configuration:
   Click Apply to save changes

6. Verify with Packet Capture:
   Use Wireshark to confirm DSCP markings

Recommended Values:
===================
SS_QOS_SIGNAL = 0xa0  (CS5 - High priority signaling)
SS_QOS_RTP    = 0xb8  (EF - Highest priority voice)

📊 Network Configuration for VOS3000 QoS

QoS markings in VOS3000 are only effective if network infrastructure respects them. Here’s how to configure common network devices:

🔹 Cisco Router QoS Configuration

Cisco Router QoS Configuration Example:
========================================

! Define class maps for voice traffic
class-map match-any VOICE-SIGNAL
 match ip dscp cs5

class-map match-any VOICE-RTP
 match ip dscp ef

! Define policy map
policy-map VOICE-POLICY
 class VOICE-RTP
  priority percent 30
  set dscp ef
 class VOICE-SIGNAL
  bandwidth percent 5
  set dscp cs5

! Apply to interface
interface GigabitEthernet0/0
 service-policy output VOICE-POLICY

! Verify configuration
show policy-map interface GigabitEthernet0/0

🔹 MikroTik RouterOS QoS Configuration

MikroTik RouterOS QoS Configuration:
=====================================

# Create mangle rules to mark packets
/ip firewall mangle
add chain=postrouting protocol=udp dst-port=5060 action=mark-packet new-packet-mark=sip-signal passthrough=yes
add chain=postrouting protocol=udp dst-port=10000-20000 action=mark-packet new-packet-mark=voice-rtp passthrough=yes

# Create queue tree for prioritization
/queue tree
add name="voice-rtp" parent=global packet-mark=voice-rtp priority=1 max-limit=10M
add name="sip-signal" parent=global packet-mark=sip-signal priority=2 max-limit=2M

# Verify with packet sniffing
/tool sniffer quick protocol=udp port=5060,10000-20000

🔹 Linux tc QoS Configuration

Linux Traffic Control QoS Example:
===================================

# Create root qdisc
tc qdisc add dev eth0 root handle 1: htb default 20

# Create classes
tc class add dev eth0 parent 1: classid 1:1 htb rate 100mbit
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 30mbit prio 1  # Voice
tc class add dev eth0 parent 1:1 classid 1:20 htb rate 70mbit prio 2  # Data

# Filter by DSCP
tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip dscp 0xb8 0xfc flowid 1:10
tc filter add dev eth0 protocol ip parent 1:0 prio 2 u32 match ip dscp 0xa0 0xfc flowid 1:10

# Verify
tc -s qdisc show dev eth0

📊 End-to-End QoS Chain

For effective QoS, all network elements must be configured:

Network ElementConfiguration RequiredImpact if Not Configured
VOS3000 ServerSet SS_QOS_SIGNAL and SS_QOS_RTPPackets sent without priority markings
Local RouterQoS policy matching DSCP valuesVoice packets treated as data
WAN/MPLSProvider respects DSCP or maps to MPLS EXPCongestion causes voice quality issues
Remote RouterQoS policy on egressLast-mile congestion affects quality
EndpointSend/receive marked packetsMay mark differently, causing mismatch

🔍 Verifying QoS Configuration

📊 Wireshark Analysis

Verifying QoS with Wireshark:
=============================

1. Capture packets on VOS3000 server or network

2. Filter for SIP signaling:
   Display filter: sip

3. Filter for RTP media:
   Display filter: rtp

4. Check DSCP field:
   - Expand IP header in packet details
   - Look for "Differentiated Services Field"
   - Verify value matches configuration

Expected Results:
=================
SIP packets: Differentiated Services Field: 0xa0 (DSCP: CS5)
RTP packets: Differentiated Services Field: 0xb8 (DSCP: EF)

Wireshark Column Setup:
=======================
Add "DSCP Value" column to quickly verify markings:
1. Right-click column header
2. Column Preferences
3. Add new column: "DSCP" with type "DSCP Value"

Common Issues to Check:
=======================
- Value shows 0x00 = QoS not applied
- Value doesn't match configuration = Check parameter setting
- Different values on different interfaces = Router rewriting DSCP

📊 QoS Verification Commands

PlatformCommandPurpose
Ciscoshow policy-map interfaceView QoS statistics
MikroTik/queue tree print statsView queue statistics
Linuxtc -s qdisc showView traffic control stats
tcpdumptcpdump -i eth0 -vv ipView DSCP in packet headers

🚨 QoS Troubleshooting

📊 Common QoS Problems

ProblemSymptomSolution
Packets unmarkedWireshark shows DSCP 0x00Verify SS_QOS parameters are set correctly
Router ignoring DSCPVoice quality poor during congestionConfigure QoS policy on router
DSCP rewritingDifferent DSCP on different network segmentsCheck router config for DSCP rewriting rules
Inconsistent markingSome packets marked, some notCheck if media proxy is interfering
WAN provider strips DSCPQoS works locally but not across WANNegotiate QoS with provider, use MPLS EXP

🔧 QoS Troubleshooting Steps

QoS Troubleshooting Checklist:
==============================

1. Verify VOS3000 Configuration:
   ☐ Check SS_QOS_SIGNAL value
   ☐ Check SS_QOS_RTP value
   ☐ Verify parameters applied after change

2. Verify Packet Marking:
   ☐ Capture packets with Wireshark/tcpdump
   ☐ Check DSCP field in IP header
   ☐ Confirm values match configuration

3. Verify Network QoS:
   ☐ Check router QoS configuration
   ☐ Verify DSCP matching rules
   ☐ Check queue statistics for voice traffic

4. Verify End-to-End:
   ☐ Test from endpoint to VOS3000
   ☐ Test through entire network path
   ☐ Check DSCP preservation at each hop

5. Performance Testing:
   ☐ Run voice quality tests under load
   ☐ Compare MOS scores with/without QoS
   ☐ Monitor latency, jitter, packet loss

Best Practices:
===============
- Document your QoS configuration
- Test during peak traffic periods
- Monitor QoS statistics regularly
- Coordinate with WAN providers
- Consider using separate VLAN for voice

📊 MPLS QoS Considerations

For MPLS networks, DSCP values may need to be mapped to MPLS EXP bits:

DSCP ValueMPLS EXPTraffic Type
EF (0xb8)7Real-time voice
CS5 (0xa0)5Voice signaling
AF41 (0x88)4Interactive video
BE (0x00)0Best effort data

❓ Frequently Asked Questions

What DSCP value should I use for RTP voice packets?

The recommended DSCP value for voice RTP is EF (Expedited Forwarding, 0xb8), which provides the highest priority treatment. However, the VOS3000 default is CS5 (0xa0), which is also acceptable for voice. For best results in controlled networks, use 0xb8 for RTP and 0xa0 for SIP signaling.

Does QoS work over the public internet?

No, QoS markings are generally not respected over the public internet. Most ISPs either ignore DSCP values or strip them entirely. QoS is effective only on networks you control (LAN, WAN with SLA, MPLS) or where you have agreement with the provider to honor markings.

Why do my QoS settings seem to have no effect?

QoS requires end-to-end configuration. Check: 1) VOS3000 parameters are set correctly, 2) Network devices are configured to match and prioritize marked packets, 3) There’s actual congestion for QoS to manage, 4) DSCP values aren’t being rewritten by intermediate devices.

Can different endpoints have different QoS settings?

VOS3000 QoS parameters (SS_QOS_SIGNAL and SS_QOS_RTP) apply globally to all calls processed by the softswitch. For per-endpoint QoS differentiation, you would need to implement QoS policies on network devices based on IP addresses or other criteria.

Should signaling and media use the same DSCP value?

Generally, media (RTP) should have higher priority than signaling because it’s more sensitive to delay and jitter. A common approach is EF (0xb8) for RTP and CS5 (0xa0) for SIP signaling. However, VOS3000 defaults both to CS5, which works well in most scenarios.

📞 Get Expert Help with VOS3000 QoS

Need assistance configuring QoS for optimal voice quality? Our VOS3000 experts can help design and implement end-to-end QoS strategies for enterprise and carrier networks.

📱 WhatsApp: +8801911119966

Contact us for VOS3000 installation, QoS configuration, network optimization, and professional VoIP support 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 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization
SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization

VOS3000 Debug Trace: Complete Call Signaling Analysis & Troubleshooting Easy Guide

VOS3000 Debug Trace: Complete Call Signaling Analysis & Troubleshooting Guide

VOS3000 debug trace is an essential tool for diagnosing and resolving VoIP signaling issues. When calls fail, registrations don’t complete, or audio problems occur, the debug trace function provides detailed visibility into SIP and H.323 message flows, enabling administrators to pinpoint root causes quickly. This comprehensive guide covers all debug trace features based on official VOS3000 2.1.9.07 documentation.

📞 Need help with VOS3000 troubleshooting? WhatsApp: +8801911119966

🔍 Understanding VOS3000 Debug Trace

Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)

The debug trace function in VOS3000 captures all signaling messages processed by the softswitch, including SIP INVITE, REGISTER, BYE messages and H.323 signaling. This provides a complete record of call flows for troubleshooting and analysis.

📊 What Debug Trace Captures (VOS3000 Debug Trace)

ProtocolMessages CapturedUse Cases
SIPINVITE, REGISTER, BYE, CANCEL, OPTIONS, 1xx/2xx/3xx/4xx/5xx/6xx responsesCall setup failures, registration issues, NAT problems
H.323Setup, CallProceeding, Alerting, Connect, ReleaseComplete, H.245 messagesGateway interconnection, codec negotiation
RTPMedia stream information (limited)Audio path verification, codec confirmation

⚙️ Enabling Debug Trace

Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)

📍 Access Location

Navigate to: System > Debug trace in the VOS3000 client menu.

🔧 Debug Trace Configuration Options

SettingDescriptionRecommendation
On/OffEnable or disable trace captureEnable only when troubleshooting
Trace LengthDuration to capture (in minutes)Set specific duration or uncheck for continuous
Step-by-Step Debug Trace Activation:
====================================

1. Open VOS3000 Client

2. Navigate to:
   Menu bar > System > Debug trace

3. Configure Settings:
   ☑ Check "On" to enable trace
   ☐ Uncheck "Trace length" for continuous capture
   OR set specific duration (e.g., 30 minutes)

4. Click OK to start capture

5. Reproduce the problem:
   - Make test call
   - Attempt registration
   - Generate the issue you're investigating

6. View Trace Results:
   - Current Call: Right-click > Trace
   - CDR: Right-click > Call analysis

Important Notes:
================
- Trace impacts performance slightly when enabled
- Disable trace when not actively troubleshooting
- Trace files rotate automatically when size limit reached

📁 Trace File Management (VOS3000 Debug Trace)

Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205) and Section 4.3.5.2 (Page 237-238)

⚙️ Trace File Parameters

ParameterDefaultRangeDescription
SS_TRACE_FILE_LENGTH40960KBSize of softswitch debug file (KB)
SS_TRACE_CALL_FILE_SIZE1616-2048 MBCall signaling trace file size limit (MB)
SS_TRACE_REGISTER_FILE_SIZE1616-2048 MBRegistration signaling trace file size limit (MB)
SS_TRACE_MASKERRORERROR/DEBUGLevel of debug information to display
SS_TRACETOFILEOnOn/OffOutput debug information into file

📁 Two-File Rotation System

Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)

VOS3000 Trace File Rotation:
=============================

VOS3000 uses 2 files to record trace signaling:

File 1: trace1.log (or similar)
File 2: trace2.log (or similar)

How It Works:
=============
1. System writes to File 1
2. When File 1 reaches size limit (SS_TRACE_FILE_LENGTH)
3. System switches to File 2
4. When File 2 reaches size limit
5. System overwrites File 1 (oldest data lost)
6. Cycle continues...

Advantages:
===========
- Actual storage is double the file size limit
- Continuous capture without manual intervention
- Recent history always available
- Automatic cleanup of old data

Important:
==========
All trace signaling is saved unless file has been covered.
If you need to preserve trace data, copy files before rotation.

📊 Using Trace for Troubleshooting

📍 Accessing Trace Results (VOS3000 Debug Trace)

Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)

Access MethodLocationInformation Shown
Current Call TraceCurrent Call > Right-click > TraceReal-time call signaling for active calls
CDR Call AnalysisCDR > Right-click > Call analysisComplete signaling flow for completed call
Registration AnalysisRegistration Management > Right-clickRegistration message flow and status

🔧 Interpreting Trace Output

📊 SIP Message Format

Sample SIP INVITE Trace Output:
===============================

---------- 2026-04-03 10:25:32.123 ----------
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK123456
From: ;tag=12345
To: 
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: 
Content-Type: application/sdp
Content-Length: 200

v=0
o=user 123 456 IN IP4 192.168.1.50
s=Session
c=IN IP4 192.168.1.50
t=0 0
m=audio 10000 RTP/AVP 0 8 18
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000

Key Headers to Analyze:
=======================
- Via: Message path and NAT information
- From/To: Caller and callee identities
- Call-ID: Unique call identifier
- Contact: Where to send responses
- SDP (body): Media negotiation details

📊 H.323 Message Format

Sample H.323 Setup Trace Output:
================================

---------- 2026-04-03 10:26:15.456 ----------
H.225 Setup Message:
  Protocol Identifier: 0.0.8.2250.0.4
  Source Address:
    IP: 192.168.1.50
    Port: 1720
  Destination Address:
    IP: 192.168.1.100
    Port: 1720
  Source Info:
    E164: 0987654321
  Destination Info:
    E164: 1234567890
  Active MC: FALSE
  Conference ID: 0x12345678...

Key Elements to Analyze:
========================
- Protocol Identifier: H.323 version
- Source/Destination: Endpoint addresses
- E164 numbers: Calling/called numbers
- Conference ID: Call identifier

🚨 Common Debugging Scenarios

📊 One-Way Audio Diagnosis (VOS3000 Debug Trace)

Trace FindingMeaningSolution
SDP shows private IP in c= lineNAT issue – endpoint behind NATEnable media proxy, check NAT settings
RTP port mismatch between INVITE and 200 OKSDP negotiation problemCheck codec compatibility, port ranges
Contact header has wrong IPSIP ALG interferenceDisable SIP ALG on router

📊 Registration Failure Analysis

Trace FindingMeaningSolution
401 Unauthorized responseAuthentication credentials requiredConfigure correct username/password
403 Forbidden responseAccount locked or IP not allowedCheck account status, IP whitelist
No response to REGISTERNetwork or firewall issueCheck SIP port 5060, firewall rules
Authentication retry exceededWrong credentials repeatedlyVerify credentials, check for typos

📊 Call Drop Investigation

Trace FindingMeaningSolution
BYE at 30-second intervalNAT binding timeoutIncrease NAT keepalive, disable SIP ALG
Session timer expirySession timer not refreshedCheck SS_SIP_SESSION_TTL setting
RTP timeout in traceNo media received for configured timeCheck media path, SS_MEDIA_CHECK_TIMEOUT
503 Service UnavailableGateway overloaded or downCheck gateway status, line limits

⚙️ Advanced Trace Configuration (VOS3000 Debug Trace)

📊 Trace Mask Settings

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 238)

SettingInformation LevelWhen to Use
ERRORErrors and warnings onlyNormal troubleshooting, production systems
DEBUGDetailed debug informationComplex issues, development testing

⚙️ Performance Impact

Performance Considerations:
==========================

SS_TRACE_MASK = ERROR (Default):
- Minimal performance impact
- Captures only error conditions
- Suitable for production systems
- Adequate for most troubleshooting

SS_TRACE_MASK = DEBUG:
- Higher performance impact
- Captures all message details
- More disk space usage
- Use for complex debugging only

Recommendations:
================
1. Use ERROR level for normal operations
2. Switch to DEBUG only when needed
3. Disable trace when not troubleshooting
4. Monitor disk space on busy systems
5. Set appropriate file size limits

Production Guidelines:
======================
- Keep SS_TRACETOFILE = On (writes to file, not memory)
- Set SS_TRACE_FILE_LENGTH appropriately (40MB default)
- Use SS_TRACE_MASK = ERROR
- Disable during high-traffic periods if possible

📊 CDR End Reason Reference (VOS3000 Debug Trace)

Reference: VOS3000 2.1.9.07 Manual, Section 4.5 (Page 243-248)

When analyzing call failures, the end reason in CDR combined with trace provides complete information:

📋 Server-Side End Reasons

End ReasonDescriptionTrace Analysis
Response timeoutNo answer before timeoutCheck INVITE sent, no 180/183/200 received
Connection timeoutNo SIP response after retriesCheck INVITE sent, check network path
Account lockedAccount disabled403 Forbidden in trace
Session timeoutSession timer expiredCheck UPDATE/re-INVITE messages
No matching rateNo rate for destinationCall rejected before INVITE sent
Insufficient balanceAccount out of funds403 Forbidden after billing check
The called not onlineNo route availableNo matching routing gateway

❓ Frequently Asked Questions

Where are trace files stored?

Trace files are stored in the VOS3000 installation directory, typically under a “trace” or “log” subdirectory. The exact location depends on your installation path. The files are managed automatically by VOS3000’s two-file rotation system.

How long should I keep debug trace enabled?

Enable debug trace only when actively troubleshooting issues. For production systems, keep trace disabled or set to ERROR level to minimize performance impact. Enable DEBUG level only when investigating complex issues, then disable after resolution.

Can I export trace data for analysis?

Yes, you can use the call analysis feature in CDR to view detailed trace for specific calls. For bulk analysis, trace files can be copied from the server and analyzed with text editors or tools like Wireshark (for SIP traces saved in pcap format).

Why can’t I see trace for old calls?

Trace files have size limits and use rotation. When files exceed SS_TRACE_FILE_LENGTH or SS_TRACE_CALL_FILE_SIZE, older data is overwritten. If you need to preserve trace data for compliance or analysis, copy trace files before rotation occurs.

Does trace capture RTP media content?

No, VOS3000 debug trace captures signaling only (SIP and H.323). It does not capture the actual RTP media content (voice/audio). For media analysis, you would need separate packet capture tools like tcpdump or Wireshark on the server.

📞 Get Expert Help with VOS3000 Debugging

Need assistance analyzing trace output or resolving complex VoIP issues? Our VOS3000 experts provide remote debugging support, signaling analysis, and troubleshooting services.

📱 WhatsApp: +8801911119966

Contact us for VOS3000 installation, troubleshooting support, configuration optimization, and professional VoIP 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 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization
SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization

VOS3000 Routing Optimization: Complete ASR/ACD-Based Gateway Selection Best Guide

VOS3000 Routing Optimization: Complete ASR/ACD-Based Gateway Selection Guide

VOS3000 routing optimization is critical for maximizing call quality and profitability in VoIP operations. By leveraging ASR (Answer Seizure Ratio) and ACD (Average Call Duration) metrics, VOS3000 can intelligently select the best performing gateways for each call, ensuring optimal quality for customers while maximizing revenue for operators. This comprehensive guide covers all routing optimization features based on official VOS3000 2.1.9.07 documentation.

📞 Need help with VOS3000 routing optimization? WhatsApp: +8801911119966

🔍 Understanding Route Quality Metrics

Before configuring routing optimization, it’s essential to understand the key metrics that VOS3000 uses to evaluate gateway performance and make routing decisions.

📊 Key VoIP Quality Metrics (VOS3000 Routing Optimization)

MetricFull NameDefinitionGood Value
ASRAnswer Seizure RatioPercentage of calls that are answered40-60%+ (varies by route type)
ACDAverage Call DurationAverage length of connected calls3-10 minutes (depends on destination)
PDDPost Dial DelayTime from dialing to hearing ringback< 5 seconds ideal
NERNetwork Effectiveness RatioCalls delivered vs attempted95%+ for quality routes

📈 ASR and ACD Impact on Profitability (VOS3000 Routing Optimization)

Reference: VOS3000 2.1.9.07 Manual, Section 4.1.1 and 4.3.3 (Page 212, 220-221)

ScenarioLow ASR ImpactLow ACD ImpactCombined Effect
Revenue LossMore failed calls = less billable timeShorter calls = less revenue per callMultiplicative revenue reduction
Customer SatisfactionFrustration with failed callsComplaints about call dropsCustomer churn increases
Carrier RelationsWasted capacity on failed attemptsLower quality perceptionPoor partner relationships

⚙️ VOS3000 Routing Gateway Sorting Algorithm

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.3 (Page 220-221)

VOS3000 uses a sophisticated multi-step algorithm to determine gateway selection order when multiple gateways match a called number. Understanding this algorithm is essential for configuring optimal routing.

📊 Gateway Sorting Steps (VOS3000 Routing Optimization)

StepSorting CriteriaDescriptionConfiguration
Step 1Routing StrategyApply first/second routing strategy from mapping gatewayMapping Gateway > Additional settings
Step 2Longest Prefix MatchGateway with longest matching prefix takes precedenceRouting Gateway > Gateway prefix
Step 3Prefix PriorityPriority setting within same prefixRouting Gateway > Prefix mode
Step 4Gateway PriorityGateway priority value (lower = higher priority)Routing Gateway > Priority
Step 5ASR/Rate SortingSort by ASR or lowest rate based on configurationSystem parameters
Step 6Current Day CallsTotal calls processed todayAutomatic tracking
Step 7Gateway IDFinal tie-breaker by gateway IDGateway name

📊 ASR-Based Routing Configuration

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 235-236)

⚙️ ASR Routing Parameters (VOS3000 Routing Optimization)

ParameterDefaultRangeDescription
SS_GATEWAY_ASR_CALCULATEOffOn/OffEnable real-time ASR calculation
SS_GATEWAY_ASR_RESERVE_TIME600300-86400 secTime window for ASR calculation
SS_GATEWAY_ASR_RESERVE_SEPARATE105-24Number of time segments for ASR calculation
SS_GATEWAYASRROUTESORTCONFIGBefore line usagePosition optionsWhere ASR sorting is inserted in algorithm

📐 How ASR is Calculated

Reference: VOS3000 2.1.9.07 Manual, Section 4.1.1 (Page 212)

VOS3000 ASR Calculation Method:
===============================

Formula: ASR = (Answered Calls / Total Call Attempts) × 100%

VOS3000 divides ASR calculation into time segments:
- Segment length = SS_GATEWAY_ASR_RESERVE_TIME / SS_GATEWAY_ASR_RESERVE_SEPARATE
- Example: 600 / 10 = 60 seconds per segment
- ASR at any point = mean of last 10 segments (rolling average)

Example Calculation:
===================
SS_GATEWAY_ASR_RESERVE_TIME = 600 (10 minutes)
SS_GATEWAY_ASR_RESERVE_SEPARATE = 10 segments

Time segments (each 60 seconds):
Segment 1: 0-60 sec    → 45 attempts, 25 answered = 55.6% ASR
Segment 2: 60-120 sec  → 50 attempts, 30 answered = 60.0% ASR
Segment 3: 120-180 sec → 40 attempts, 22 answered = 55.0% ASR
... (and so on)

Current ASR = Average of last 10 segments = ~57%

Benefits of Rolling Average:
============================
- Smooths out temporary fluctuations
- Reflects recent gateway performance
- Adapts to changing network conditions
- Prevents single bad period from dominating

🔧 Enabling ASR-Based Routing

Step-by-Step ASR Routing Configuration:
=======================================

1. Enable Real-Time ASR Calculation:
   Location: Softswitch management > Additional settings > System parameter
   Parameter: SS_GATEWAY_ASR_CALCULATE
   Set to: On

2. Configure ASR Time Window:
   Parameter: SS_GATEWAY_ASR_RESERVE_TIME
   Recommended: 600 (10 minutes) for responsive routing
   Higher values = more stable but slower to react

3. Set Calculation Segments:
   Parameter: SS_GATEWAY_ASR_RESERVE_SEPARATE
   Recommended: 10 segments
   Each segment = 60 seconds in this example

4. Set ASR Sorting Position:
   Parameter: SS_GATEWAYASRROUTESORTCONFIG
   Options:
   - "Before line usage" (default)
   - "Before gateway ID"

5. Enable ASR Routing on Gateway:
   Location: Routing Gateway > Additional settings
   Check: "Calculate routing quality in real time"

6. Apply and Test:
   - Make test calls
   - Monitor CDR for gateway selection
   - Verify ASR-based routing is active

📊 ACD-Based Routing Configuration

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 235-236)

⚙️ ACD Routing Parameters (VOS3000 Routing Optimization)

ParameterDefaultRangeDescription
SS_GATEWAY_ACD_CALCULATEOffOn/OffEnable real-time ACD calculation
SS_GATEWAY_ACD_RESERVE_TIME600300-86400 secTime window for ACD calculation
SS_GATEWAY_ACD_RESERVE_SEPARATE105-24Number of time segments for ACD calculation

📐 ACD Calculation Method

VOS3000 ACD Calculation:
========================

Formula: ACD = Total Duration of Answered Calls / Number of Answered Calls

Example:
- 30 answered calls in time window
- Total duration: 4500 seconds
- ACD = 4500 / 30 = 150 seconds (2.5 minutes)

ACD indicates call quality:
- High ACD (> 180 sec): Good voice quality, engaged conversations
- Medium ACD (60-180 sec): Normal for most destinations
- Low ACD (< 60 sec): Possible quality issues, quick hangups

Use Cases for ACD Routing:
==========================
1. Route to gateways with longer average call duration
2. Avoid gateways where calls drop quickly
3. Balance quality with cost considerations
4. Detect and avoid fraud routes (unusually high ACD)

💰 Rate-Based Routing Configuration

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.3 (Page 220-221)

⚙️ Rate Routing Parameters

ParameterDefaultDescription
SS_GATEWAYFEERATEROUTESORTCONFIGBefore line usagePosition for rate-based sorting in algorithm
SS_GATEWAY_FEE_RATE_ROUTE_BEFORE_ASROffRate routing priority over ASR routing

⚖️ Balancing Cost vs Quality (VOS3000 Routing Optimization)

The key decision in routing optimization is balancing cost (rate) against quality (ASR/ACD). VOS3000 provides multiple strategies:

StrategyConfigurationBest ForTrade-off
Lowest Cost FirstRate routing before ASR, ASR disabledWholesale, high margin routesMay have quality issues
Best Quality FirstASR routing before rate, rate disabledPremium services, retailHigher cost per minute
Balanced ApproachBoth enabled, rate before ASRGeneral wholesale operationsModerate cost, moderate quality
Quality with Cost FallbackASR before rate, rate as secondaryPremium with cost managementQuality prioritized when available

🔄 Gateway Switch Configuration

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 236)

⚙️ Gateway Switch Parameters

ParameterDefaultDescription
SS_GATEWAY_SWITCH_LIMITNoneMaximum auto-switch attempts before stopping
SS_GATEWAY_SWITCH_STOP_AFTER_RTP_STARTOnStop switching after RTP media starts
SS_GATEWAY_SWITCH_STOP_AFTER_USER_BUSYOnStop switching when user is busy
SS_GATEWAY_SWITCH_UNTIL_CONNECTOffKeep switching until call connects

📐 Gateway Switch Behavior (VOS3000 Routing Optimization)

How Gateway Switching Works:
============================

When a call fails on one gateway, VOS3000 can automatically try the next available gateway.

Example with SS_GATEWAY_SWITCH_LIMIT = 3:
=========================================
Call attempt 1: Gateway A (fails)
Call attempt 2: Gateway B (fails)
Call attempt 3: Gateway C (fails)
→ Stop trying, return failure to caller

Example with SS_GATEWAY_SWITCH_LIMIT = None:
============================================
Call attempt 1: Gateway A (fails)
Call attempt 2: Gateway B (fails)
Call attempt 3: Gateway C (connects)
→ Success!

Configuration Recommendations:
=============================
- High-value routes: SS_GATEWAY_SWITCH_LIMIT = None (unlimited retries)
- Standard routes: SS_GATEWAY_SWITCH_LIMIT = 3-5
- Capacity-limited: SS_GATEWAY_SWITCH_LIMIT = 2-3

Stop Conditions:
================
- RTP Started: Stop after media established (prevents disruption)
- User Busy: Don't retry on busy destination
- Until Connect: Keep trying until connected or all gateways exhausted

📊 Quality Reserve Time System

Reference: VOS3000 2.1.9.07 Manual, Section 4.1.1 (Page 212)

The quality reserve time system controls how VOS3000 calculates and uses quality metrics for routing decisions.

⚙️ Quality Reserve Parameters (VOS3000 Routing Optimization)

ParameterDefaultPurpose
SS_GATEWAY_QUALITY_RESERVE_TIME600Total time window for quality calculation (seconds)
SS_GATEWAY_QUALITY_RESERVE_SEPARATE10Number of segments to divide the time window

📐 Quality Calculation Example

Quality Reserve Time Calculation:
=================================

Given:
- SS_GATEWAY_QUALITY_RESERVE_TIME = 600 seconds (10 minutes)
- SS_GATEWAY_QUALITY_RESERVE_SEPARATE = 10 segments

Each segment = 600 / 10 = 60 seconds

Gateway ASR over 10 minutes:
Segment 1 (0-60s):    55% ASR
Segment 2 (60-120s):  58% ASR
Segment 3 (120-180s): 52% ASR
Segment 4 (180-240s): 60% ASR
Segment 5 (240-300s): 57% ASR
Segment 6 (300-360s): 54% ASR
Segment 7 (360-420s): 59% ASR
Segment 8 (420-480s): 56% ASR
Segment 9 (480-540s): 61% ASR
Segment 10 (540-600s): 58% ASR

Current Gateway ASR = Average of all 10 segments = 57%

This rolling average provides:
- Smooth response to quality changes
- Protection from temporary spikes
- Historical context for decisions

❓ Frequently Asked Questions

What is a good ASR value for VoIP routes?

ASR values vary significantly by destination type. International routes typically see 30-50% ASR, while domestic routes may achieve 50-70%. Premium routes can reach 70%+. Compare your ASR against industry benchmarks for similar destinations rather than absolute values.

Should I use ASR or rate-based routing?

It depends on your business model. For wholesale operations with thin margins, rate-based routing may be appropriate. For retail or premium services where customer satisfaction is critical, ASR-based routing ensures better quality. Many operators use a balanced approach with rate routing as primary and ASR as quality threshold.

How often does VOS3000 update ASR calculations?

VOS3000 calculates ASR continuously in real-time when SS_GATEWAY_ASR_CALCULATE is enabled. The quality reserve time parameters determine the time window and granularity. With default settings (600 seconds, 10 segments), each 60-second period contributes to the rolling average.

Can gateway switching cause duplicate calls?

No, VOS3000 handles gateway switching at the signaling level. When a call fails on one gateway, the system tries the next gateway before responding to the caller. The caller sees only one call attempt, even if VOS3000 tried multiple gateways internally.

How do I monitor route quality in VOS3000?

Use the Gateway Performance reports in VOS3000: Navigation > Data query > CDR Analysis > Historical Performance. This shows ASR, ACD, and call volume trends. You can also enable gateway analysis reports in system parameters.

📞 Get Expert Help with VOS3000 Routing Optimization

Need assistance configuring optimal routing strategies? Our VOS3000 experts can help you design ASR/ACD-based routing, tune quality parameters, and maximize your VoIP profitability.

📱 WhatsApp: +8801911119966

Contact us for VOS3000 installation, routing optimization, gateway configuration, and professional VoIP support 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 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization
SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization

VOS3000 Dial Plan: Complete Number Transformation & Prefix Manipulation Guide

VOS3000 Dial Plan: Complete Number Transformation & Prefix Manipulation Guide

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

🔍 Understanding VOS3000 Dial Plan

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.

📊 Dial Plan Application Points

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.1 (Page 219-220)

Application PointLocationPurposeAffects
Mapping Gateway Dial PlanMapping Gateway > Additional settingsTransform incoming called numberNumber before routing decision
Routing Gateway Dial PlanRouting Gateway > Additional settingsTransform outgoing called numberNumber sent to downstream gateway
Phone Dial PlanPhone Management > Additional settingsTransform called number for phoneNumber before routing from phone

📐 Dial Plan Syntax and Wildcards

Reference: VOS3000 2.1.9.07 Manual, Section 4.3.1 (Page 219-220)

🔤 Wildcard Characters

VOS3000 dial plan supports wildcard characters for flexible pattern matching:

WildcardNameMatchesExample
*AsteriskAny number of any digits (including zero)* matches any number
?Question MarkSingle random digit (in target prefix only)123?78 matches 123178, 123278, etc.
$Dollar SignKeep original digit at position (in target only)$$$ keeps first three digits unchanged

🔧 Escape Characters for Length Constraints

VOS3000 dial plan supports escape characters to specify number length constraints:

Escape CharMeaningSyntaxExample
LLength Less ThanPrefix followed by L and digit count13L9 matches 11-digit numbers starting with 13
ELength Equal ToPrefix followed by E and digit count010E7 matches exactly 10 digits starting with 010
GLength Greater ThanPrefix followed by G and digit count010G7 matches 11+ digits starting with 010

Note: Use backslash before escape character (\L, \E, \G) to remove its special meaning and match literally.

📋 Complete Dial Plan Examples from Manual

Reference: VOS3000 2.1.9.07 Manual, Table 4-1 (Page 219-220)

📊 Dial Plan Transformation Table (VOS3000 Dial Plan)

Original PrefixTarget PrefixExample InputAfter TransformationDescription
000258431614602584316146No change – pass through
00100258431614601084316146Change prefix 0 to 010
025(empty)0258431614684316146Remove prefix 025
*025*117025117Add prefix 025 to all numbers
025*0100258431614601084316146Change prefix 025 to 010
010*(empty)0258431614601002584316146Add prefix 010 (empty = append)
*(empty)02584316146(empty)Delete all numbers
*123456780258431614612345678Replace all numbers with constant
025*8008100-8008121025843161468008100 to 8008121Range-based random selection
*12345?780258431614612345178, 12345278, etc.? becomes random digit
0??843184310258431614684316146? matches any digit in pattern
0134$$$0134131013131$ keeps original digit position

🔀 Longest Matching Principle (VOS3000 Dial Plan)

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.

📊 Longest Matching Examples (VOS3000 Dial Plan)

Dial Plan RulesInput NumberMatched RuleResultReason
0 → 0
010 → 025
01012345678010 → 02502512345678010 is longer match than 0
* → 025*
01 → 00
011234567801 → 00001234567801 is longer match than *
0 → 0
01 → 025
011 → 00
01117654321011 → 000017654321011 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.

🔧 Multiple Substitution Targets

VOS3000 dial plan supports multiple substitution targets separated by semicolons (;). When “?” exists in the target, each “?” is replaced by a randomly generated digit.

📋 Multiple Target Examples

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

⚙️ Dial Plan Configuration in VOS3000

📍 Configuring Mapping Gateway Dial Plan (VOS3000 Dial Plan)

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)

📍 Configuring Routing Gateway Dial Plan

Reference: VOS3000 2.1.9.07 Manual, Section 2.5.1.1 (Page 32-39)

SettingLocationPurpose
Callee number transformRouting Gateway > Additional settings > Dial planTransform called number before sending to this gateway
Caller number transformRouting Gateway > Additional settings > Dial planTransform calling number before sending to this gateway
Gateway prefixRouting Gateway > Main settingsAdd prefix for routing to this gateway

🎯 Common Dial Plan Use Cases

🌐 International Prefix Handling (VOS3000 Dial Plan)

ScenarioOriginalTargetExample
Remove 00 international prefix00(empty)004412345678 → 4412345678
Add 00 international prefix*00*4412345678 → 004412345678
Convert + to 00+00+4412345678 → 004412345678
Add country code*86*13812345678 → 8613812345678

📞 Area Code Manipulation

ScenarioOriginalTargetExample
Add area code to local numbersE8025*84316146 → 02584316146
Remove area code025(empty)02584316146 → 84316146
Change area code02501002584316146 → 01084316146

🚨 Emergency Number Routing

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

🔍 Troubleshooting Dial Plan Issues

🚨 Common Problems and Solutions

ProblemPossible CauseSolution
Number not matching expected ruleLonger pattern exists and takes precedenceReview all dial plan rules, use longest matching principle
Prefix not removedOriginal prefix doesn’t match exactlyVerify exact prefix in CDR, adjust dial plan
Wrong transformation appliedMultiple rules with overlapping patternsCheck longest matching, reorder if needed
Billing discrepancyDial plan changes number after billing lookupVerify dial plan application point (before/after billing)
Number becomes emptyTarget prefix is empty for full matchUse correct wildcard patterns, avoid deleting entire number

📋 Dial Plan Testing Procedure

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

❓ Frequently Asked Questions

What happens when multiple dial plan rules match?

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.

Can I use dial plan to change caller ID?

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.

How do I test if my dial plan is working correctly?

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.

Can dial plan affect billing?

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.

What’s the difference between gateway prefix and dial plan?

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.

📞 Get Expert Help with VOS3000 Dial Plan

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!


📞 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 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimizationVOS3000 softswitch VoIP, VOS3000 seguridad, VOS3000 Call Center Soluciones, VOS3000 API Integración, VOS3000 Infraestructura, VOS3000 Errores Ruting Llamadas, VOS3000错误代码替换与呼叫失败排查, VOS3000 Optimización de Rendimiento, VOS3000 Códigos Error Terminación, VOS3000 NoAvailableRouter错误解决方案, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP批发业务, 软交换比较, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Guía Completa VOS3000 2026, VOS3000 指南 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization