VOS3000 FAQ From Linknat Website at Single Post, Only Text – Easy Guide!

SECTION 1: HOT ISSUES

QUESTION 1:
Soft/Hardware allocation of VOS server

ANSWER:
VOS server hardware allocation depends on your expected concurrent call volume and traffic patterns. For small deployments handling up to 500 concurrent calls, a server with 8 CPU cores and 16GB RAM provides adequate performance. Medium-scale operations requiring support for 500 to 2000 concurrent calls benefit from 16 CPU cores and 32GB RAM configurations. For large-scale carriers processing over 2000 concurrent calls, consider servers with 32+ CPU cores and 64GB+ RAM.

Storage requirements include approximately 40GB for the operating system and 100-200GB of SSD storage for optimal database performance, particularly for CDR (Call Detail Records) management. The VOS3000 platform runs on Linux-based operating systems, with CentOS 6.x and 7.x being the most widely tested and recommended options.

CPU requirements are influenced by SIP signaling processing, media transcoding needs, and concurrent call handling capacity. Intel Xeon and AMD EPYC server processors are recommended for production VOS3000 deployments due to their reliability under sustained load. Ensure your server has low-latency connectivity to upstream providers and implement Quality of Service (QoS) policies on network equipment.

QUESTION 2:
Information requested for technical support

ANSWER:
When requesting VOS3000 technical support, provide the following essential information for faster resolution:

1. VOS3000 Software Version: Document your exact VOS3000 software version and build number from the system information section of the web management interface.
2. Operating System Details: Prepare details about your Linux operating system version, distribution type, and kernel revision.
3. Log Files: Gather relevant log files from the VOS3000 logs directory, particularly those dated around the specific time when the issue occurred.
4. Network Configuration: Include information about your firewall rules, network topology showing how VOS3000 connects to other systems, and any recent infrastructure changes.
5. Issue Details: Document specific calling scenarios that fail, including gateway configurations, prefix patterns, and timing information.

This comprehensive information enables support technicians to quickly identify root causes and provide targeted solutions.

QUESTION 3:
Which ports VOS is used outside (firewall need to allow these ports)

ANSWER:
VOS3000 requires specific ports for different types of traffic including SIP signaling, RTP media streams, database connections, and web management access. The essential ports include:

1. SIP Signaling (5060/5061): Primary port for SIP protocol communication between VOS3000 and connected gateways, softphones, and other SIP endpoints. This port handles all call setup, modification, and teardown signaling.
2. RTP Media Ports (10000-20000): The designated port range used for actual voice media transmission during active calls. These ports carry encoded audio data between calling endpoints and must be properly configured in both VOS3000 settings and firewall rules.
3. Web Interface (8080): The default port for VOS3000 web management interface providing administrative access to system configuration, monitoring, and reporting functions. Consider changing this port from the default for enhanced security.
4. Database Port (3306): MySQL database port required only if remote database access is explicitly configured. In many deployments, the database operates locally only, eliminating the need for this port to be externally accessible.
5. Additional SIP Port (5070): VOS3000 supports additional SIP listening ports for flexible deployment scenarios and traffic segregation.

When configuring firewalls for VOS3000 deployment, implement a deny-all approach and explicitly allow only necessary traffic from trusted sources.

QUESTION 4:
How to change the website default port (8080) into others

ANSWER:
Changing the default web port in VOS3000 enhances security by using non-standard ports that are less likely to be targeted by automated attacks.

To modify the web interface port:

1. Access the web server configuration file in your VOS3000 installation directory.
2. Modify the listening port setting to your desired port number. Common alternatives include:

• Port 8443 (often used for HTTPS connections)
• Port 8444
• Other high-numbered ports (e.g., 8888)

1. Update your firewall rules to allow traffic on the new port.
2. Restart the web service to apply changes.
3. Update any bookmarks, shortcuts, or integration points that reference the old port to ensure continued access to the management interface.

Note: Document the port change in your system records and update any remote access configurations accordingly.

QUESTION 5:
How to set automatic e-mail report and alarm

ANSWER:
Configuring automatic email reports and alarms ensures stakeholders receive regular updates on system status without manual intervention.

To set up automatic email reports and alarms in VOS3000:

1. Navigate to the notification configuration section in the web management interface.
2. Specify report schedules (daily, weekly, or monthly) based on your operational requirements.
3. Define recipient email addresses for report delivery.
4. Configure alarm triggers for key metrics including:

• CPU utilization thresholds
• Call success rate minimums
• Memory usage limits
• Disk space warnings
• Security event detections

1. Set up multiple notification channels including email and SMS for critical alarms requiring urgent attention.
2. Test delivery to verify recipients receive notifications correctly.

Configure the content and frequency of reports based on the intended audience – technical teams may need detailed operational reports, while management may require high-level summaries.

================================================================================

SECTION 2: VOS SOFTSWITCH

QUESTION 1:
Information requested for technical support

ANSWER:
(See Answer to Hot Issues Question 2 – Same Question)

QUESTION 2:
How to create agent

ANSWER:
Creating agents in VOS3000 is essential for managing customer accounts and traffic distribution. Agents represent clients or partners who will be sending or receiving VoIP traffic through your softswitch.

To create an agent:

1. Navigate to the client management section in VOS3000.
2. Create a new client account with the following information:

• Unique agent/client ID
• Descriptive name for administrative reference
• Contact information (email, phone)

1. Configure SIP credentials for authentication:

• Username
• Password
• Authentication method (IP-based or SIP digest)

1. Assign appropriate rate group for billing purposes.
2. Set calling privileges and any restrictions for the agent’s traffic volume or destination scope.
3. Test the configuration with a sample call to verify proper setup and billing application.

Agents can be organized into groups for easier management, and their traffic can be routed through specific gateways based on your operational requirements.

QUESTION 3:
How to add a mapping/routing gateway

ANSWER:
Adding gateways in VOS3000 is fundamental to establishing connectivity with other VoIP systems.

For Mapping Gateway Configuration:

1. Navigate to Gateway management in VOS3000.
2. Create new gateway with unique ID and descriptive name.
3. Configure SIP listening parameters including:

• Port number (default 5060)
• Protocol (UDP, TCP, or TLS)

1. Set up authentication credentials:

• IP-based authentication (allow specific IP addresses)
• SIP digest authentication (username and password)

1. Assign rate group for billing.
2. Configure calling number handling rules for caller ID management.

For Routing Gateway Configuration:

1. Create routing gateway with unique identifier.
2. Configure SIP connection parameters:

• Carrier’s SIP server hostname or IP address
• Listening port
• Transport protocol

1. Define routing prefixes that this gateway can terminate.
2. Set up carrier-specific handling rules and quality monitoring.
3. Test connectivity to ensure proper interconnection.

QUESTION 4:
How to let a certain mapping gateway to go to a certain routing gateway

ANSWER:
Configuring specific routing from mapping gateways to designated routing gateways enables customer-specific routing arrangements. This feature allows you to direct traffic from particular customers to specific termination partners based on commercial agreements or routing requirements.

To configure this:

1. Navigate to routing configuration in VOS3000.
2. Create or edit routing rules that specify:

• Condition: Mapping gateway identifier as the source
• Action: Target routing gateway for termination

1. The routing configuration uses the mapping gateway identifier as a condition and specifies the desired routing gateway as the target.
2. This ensures that calls entering through a specific mapping gateway are routed through designated termination partners according to your routing policies.
3. Test the routing configuration to verify calls are properly directed to the intended routing gateway.

This capability is essential for implementing customer-specific routing arrangements, carrier-specific routing, and quality-based routing strategies.

QUESTION 5:
How to set priority of certain routing prefix

ANSWER:
Setting routing prefix priority determines the order in which routing gateways are attempted when multiple gateways can terminate the same destination. Higher priority gateways are tried first, with fallback to lower priority gateways if the primary gateway fails or cannot complete the call.

To configure routing prefix priority:

1. Access routing configuration for each routing gateway.
2. Specify priority values where lower numbers indicate higher priority:

• Priority 1 = Primary choice
• Priority 2 = First backup
• Priority 3 = Second backup, etc.

1. Configure multiple gateways with the same prefix at different priorities for failover.
2. Test failover behavior by temporarily disabling primary gateways to verify backup routing works correctly.

Priority configuration works alongside prefix routing to define both preferred routing choices and failover sequences. When a call is placed, VOS3000 examines the destination prefix and selects the highest priority routing gateway configured for that prefix. If that gateway fails, the system automatically attempts the next priority gateway in sequence.

QUESTION 6:
How to achieve billing by different caller prefix in mapping gateway

ANSWER:
Implementing caller prefix-based billing allows different rates to apply based on the calling number’s prefix rather than the destination prefix. This capability is essential for wholesale VoIP operations where different rates apply based on the source of traffic, customer tier, or commercial agreement terms.

To configure caller prefix billing:

1. Navigate to mapping gateway settings in VOS3000.
2. Configure rate group assignments based on caller ID analysis.
3. The calling number analysis feature examines the caller ID or ANI information and applies the corresponding rate group for billing calculation.
4. Define different rate groups for different caller prefixes.
5. This enables differentiated billing for different traffic sources terminating to the same destinations.

This capability supports complex wholesale scenarios including aggregator billing, tiered customer pricing, and traffic redistribution arrangements where the same destination might be billed at different rates depending on which customer or traffic source originates the call.

QUESTION 7:
How to achieve encryption between two VOS

ANSWER:
Configuring encryption between VOS3000 systems enables secure communication between distributed deployments or interconnection with partner systems. Encryption prevents eavesdropping on inter-system signaling and media, protecting sensitive routing and billing information from exposure.

To achieve encryption between two VOS systems:

1. Configure TLS for signaling encryption:

• Obtain SSL/TLS certificates for both systems
• Configure TLS transport on both VOS3000 servers
• Set up mutual authentication if required

1. Configure SRTP for media encryption:

• Enable SRTP in VOS3000 media settings
• Configure encryption keys and algorithms

1. Establish SIP peer relationships using TLS transport.
2. Verify that encrypted connections are established for all inter-system traffic.
3. Test both signaling and media encryption to ensure proper operation.

VOS3000 supports TLS 1.2 and 1.3 for secure connections. Ensure certificates are properly signed and regularly renewed to maintain secure communication.

QUESTION 8:
How to solve the accuracy lost when import the rate table

ANSWER:
Rate table import accuracy loss can occur due to formatting problems, character encoding issues, or rounding errors in the import process. Preventing accuracy loss requires careful attention to data preparation and import procedures.

To solve accuracy loss during rate table import:

1. Use UTF-8 encoded CSV format for international character support.
2. Verify field separators are consistent throughout the file (use comma, semicolon, or tab consistently).
3. Ensure all numeric values use consistent decimal formats (use dot or comma consistently).
4. Validate prefix formatting matches VOS3000 requirements (no leading zeros, proper format).
5. Enable import validation features in VOS3000 to identify potential issues before processing.
6. Perform spot checks of imported data against source records after completion.
7. Export existing rates as backup before importing new data to enable quick recovery if issues occur.
8. Consider using the VOS3000 import validation tool to check for common errors before actual import.

Following these procedures ensures accurate rate table imports and prevents billing discrepancies.

QUESTION 9:
How to catch the call-flow in VOS softswitch

ANSWER:
Capturing call flow in VOS3000 helps troubleshoot routing issues, verify call processing, and analyze system behavior. Call flow capture provides detailed information about how calls are processed through the softswitch.

To catch the call flow in VOS3000:

1. Navigate to the data query section in the web management interface.
2. Access CDR (Call Detail Records) data to examine call records and routing decisions.
3. Use the navigation section to access call flow information for troubleshooting.
4. Enable detailed logging for specific gateways or calling scenarios.
5. Analyze the captured data to identify:

• Call routing paths
• Gateway selection decisions
• Any failures or rejections
• Timing information

1. Export data for offline analysis if needed.

The call flow analysis tools help identify routing issues, verify that calls are following expected paths, and troubleshoot problems with specific calls or gateways.

QUESTION 10:
The definition of Rate of connected and Rate of response

ANSWER:
Rate of connected and Rate of response are two different billing concepts in VOS3000 that apply to different call scenarios:

RATE OF CONNECTED:

• Applies billing when calls are successfully connected
• Voice traffic flows between calling parties
• The call is fully established and communication is possible
• Standard per-minute rates apply
• This is the primary billing metric for completed calls

RATE OF RESPONSE:

• Applies when the called party answers (SIP 200 OK response received)
• The call may not complete successfully for various reasons
• May include cases where:
• The called number is busy
• No answer after connection
• Call was forwarded but not answered
• Network issues prevented completion
• Different pricing can be configured for response-only calls
• Typically lower than connected rates

Different pricing can be configured for each scenario, allowing carriers to bill appropriately for partial call attempts that do not complete. This distinction is important for accurate billing and revenue collection in wholesale VoIP operations.

QUESTION 11:
How to change the website default port (8080) into others

ANSWER:
(See Answer to Hot Issues Question 4 – Same Question)

QUESTION 12:
About the size of the cdrs

ANSWER:
CDR (Call Detail Record) size depends on several factors including call volume, retention period, and the specific fields captured for each call record.

Factors affecting CDR size:

1. Call Volume: High-volume deployments can generate millions of CDR records daily. Each call generates a complete record with multiple fields.
2. Fields Captured: The more fields captured per CDR (caller ID, timestamps, routing info, billing details), the larger each record becomes.
3. Retention Period: Longer retention periods mean more records stored, increasing total storage requirements.
4. Compression: Whether CDRs are compressed for storage affects effective size.

Typical considerations:

• Each CDR record is approximately 200-500 bytes depending on fields captured
• 1 million calls/day generates approximately 200-500 MB of CDR data
• Consider implementing tiered retention policies:
• Detailed records for 30-90 days for billing verification
• Summarized data for longer-term compliance and analysis

Storage planning should account for database growth, implement regular cleanup of old records, and ensure adequate performance for CDR queries.

QUESTION 13:
Which ports VOS is used outside (firewall need to allow these ports)

ANSWER:
(See Answer to Hot Issues Question 3 – Same Question)

QUESTION 14:
The server time is correct, but the some cdr billings are different with other platforms

ANSWER:
CDR billing differences between platforms can occur due to various factors even when server time appears correct. Common causes include:

1. Timezone Settings:

• Different platforms may use different timezones for billing calculations
• Daylight saving time transitions can cause discrepancies
• UTC vs local time interpretation differences

1. Billing Rules:

• Different platforms may use different billing increments (per second, per minute, 6-second increments)
• Rounding rules may vary between platforms
• Connection fee calculations may differ

1. Call Duration Calculation:

• Some platforms measure from INVITE to BYE
• Others measure from 200 OK to BYE
• This can cause significant differences in billed duration

1. Rate Table Differences:

• Different platforms may have different rates loaded
• Rate effective dates may vary

1. Processing Delays:

• Some platforms include processing delays in call duration
• Others exclude these delays

To resolve:

• Verify timezone configurations match across all platforms
• Check billing increment and rounding settings
• Compare rate tables for accuracy
• Synchronize time using NTP across all systems
• Review call duration measurement methodology

QUESTION 15:
How to backup VOS data

ANSWER:
Regular VOS data backup is essential for disaster recovery and business continuity. A comprehensive backup strategy should include all critical system components.

Essential backup elements include:

1. Database Backup:

• Use mysqldump utility to create complete database backups
• Include all databases: vos3000, mysql, information_schema
• Schedule regular automated backups (daily recommended)

1. Configuration Files:

• Backup all configuration files from /opt/vos3000 directory
• Include system configuration files
• Document custom settings and modifications

1. Rate Tables:

• Export complete rate tables and routing configurations
• Include rate group definitions and pricing structures

1. CDR Archives:

• Implement regular archival of historical CDR data
• Compress older records for efficient storage
• Maintain compliance and support dispute resolution

1. Certificate and License Files:

• Backup SSL/TLS certificates
• Backup license files and activation keys

Best practices:

• Implement automated backup schedules
• Store backups in geographically separate locations
• Test restoration procedures regularly (at least quarterly)
• Document backup and recovery procedures
• Maintain at least 30 days of backup history
• Consider offsite or cloud backup for disaster recovery

QUESTION 16:
How to add the sip register port

ANSWER:
Adding SIP register ports in VOS3000 enables flexible access for endpoints that cannot use standard ports or require separate registration paths for different purposes.

To add SIP register ports:

1. Navigate to SIP configuration in VOS3000 settings.
2. Configure additional listening ports (e.g., 5070, 5080, or custom ports).
3. Update firewall rules to allow traffic to the new ports from authorized sources only.
4. Configure endpoints to register using the appropriate port.
5. Verify that registrations and calls function correctly through the new registration path.

Use cases for multiple SIP ports:

• Separating traffic by customer or gateway
• Providing dedicated registration paths for specific applications
• Port-based access control as additional security layer
• Supporting endpoints behind restrictive firewalls

Note: Document all custom port configurations and update firewall rules accordingly.

QUESTION 17:
How to use the registration analysis

ANSWER:
Registration analysis in VOS3000 monitors SIP registration status of connected gateways and endpoints. This feature ensures that only registered and authorized devices can send or receive calls through the system.

To use registration analysis:

1. Configure registration monitoring through system settings:

• Enable registration tracking
• Set registration expiration parameters (typically 3600 seconds)
• Configure refresh intervals

1. Set up alerts for registration failures:

• Failed registration attempts
• Expired registrations
• Unusual registration patterns

1. Use registration status in routing decisions:

• Prevent calls to unregistered endpoints
• Route traffic only through registered gateways
• Block traffic from unregistered sources

1. Analyze registration data to identify:

• Registered devices and their status
• Registration patterns and trends
• Potential security issues (unauthorized registration attempts)

1. Generate reports on registration activity for auditing and security review.

Registration analysis improves routing reliability and security by ensuring calls are only processed through properly registered and authorized endpoints.

QUESTION 18:
Dynamic black list

ANSWER:
Dynamic blacklist in VOS3000 enables automated threat response by blocking attack sources in real-time without requiring manual intervention. Dynamic blacklists automatically populate based on configurable triggers.

Configuration triggers for dynamic blacklisting:

1. Failed Authentication:

• Block sources with multiple failed login attempts
• Set threshold (e.g., 5 failures within 10 minutes)
• Configure automatic unblock after timeout period

1. Suspicious Calling Patterns:

• High call volume from single source
• Unusually short call durations
• Calls to suspicious number patterns

1. Attack Detection:

• SIP flood detection
• Registration attacks
• Brute force attempts

1. Anomaly Detection:

• Traffic volume anomalies
• Time-based anomalies
• Geographic anomalies

Best practices for dynamic blacklisting:

1. Configure thresholds carefully to balance security responsiveness against false positives.
2. Implement graduated response:

• First violation: Warning or temporary rate limiting
• Repeated violations: Temporary block
• Severe violations: Permanent block

1. Monitor dynamic blacklist effectiveness regularly.
2. Review and adjust thresholds based on traffic patterns.
3. Maintain logs of all dynamic blacklist actions for security review.

QUESTION 19:
Black/White number list

ANSWER:
Blacklist and whitelist number management in VOS3000 allows blocking or allowing specific phone numbers based on your security policies.

BLACKLIST (Blocking Numbers):

• Block specific calling numbers identified as sources of abuse or fraudulent activity
• Block specific called numbers to prevent termination to unwanted destinations
• Apply blocks globally or to specific gateways
• Configure block duration (temporary or permanent)

WHITELIST (Allowing Numbers):

• Ensure trusted numbers always have access regardless of other security settings
• Whitelisted entries take precedence over blacklist entries
• Apply for critical customers, partners, or internal numbers
• Provide guaranteed access for priority traffic

Management procedures:

1. Create blacklist/whitelist entries with:

• Number pattern (specific number or prefix)
• Reason for listing
• Effective date and expiration (if applicable)
• Scope (global or gateway-specific)

1. Regular review cycles:

• Audit entries quarterly
• Remove outdated entries
• Update entries as needed

1. Integration with dynamic features:

• Allow dynamic blacklist exceptions
• Support automated list population

Number list management is essential for fraud prevention, abuse blocking, and ensuring service continuity for trusted parties.

QUESTION 20:
Rate template

ANSWER:
Rate templates in VOS3000 provide an efficient mechanism for defining common billing structures that can be applied across multiple rate groups or customers. Templates define rate structure, rounding rules, and billing parameters.

Benefits of rate templates:

1. Consistency: Apply uniform billing rules across multiple customers.
2. Efficiency: Reduce configuration time for new rate groups.
3. Standardization: Ensure common rate structures across business units.
4. Maintenance: Update templates once to propagate changes.

Creating rate templates:

1. Define template components:

• Rate structure (per minute, per second)
• Rounding rules (nearest minute, 6-second increments)
• Connection fees
• Minimum call duration
• Billing increments

1. Create templates for common scenarios:

• Standard wholesale rates
• Premium rates
• promotional rates
• Carrier-specific rates

1. Apply templates when creating new rate groups.
2. Override specific rates as needed for individual customer agreements.

Templates can be exported and imported, making it easy to share rate structures between systems or backup template definitions.

QUESTION 21:
Server monitor

ANSWER:
Server monitoring in VOS3000 provides real-time visibility into system health, resource utilization, and performance metrics. Effective monitoring is essential for proactive issue identification and capacity planning.

Key monitoring areas:

1. Resource Utilization:

• CPU usage (target: below 70% during normal operations)
• Memory consumption (monitor for leaks or increasing usage)
• Disk space and I/O performance
• Network bandwidth and latency

1. Call Processing Metrics:

• Concurrent calls (current and peak)
• Call success rates
• Call setup latency
• Call completion rates

1. Gateway Status:

• Gateway availability
• Registration status
• Call capacity utilization

1. Database Performance:

• Query response times
• Connection pool usage
• Table lock status

1. Queue Depths:

• CDR queue depth
• Processing queue status

Monitoring best practices:

1. Configure alerts for threshold violations.
2. Establish baseline metrics during normal operations.
3. Implement trend analysis for capacity planning.
4. Regular review of monitoring data.
5. Correlate metrics across system components.

The VOS3000 server monitor provides comprehensive dashboards and alerting capabilities for all these metrics.

QUESTION 22:
Media proxy on/off

ANSWER:
Media proxy control in VOS3000 determines whether media traffic flows directly between endpoints or through VOS3000. This setting has significant implications for security, NAT traversal, and call quality.

MEDIA PROXY ON (Enabled):

• All voice traffic passes through VOS3000
• Enables media recording and inspection
• Provides better NAT traversal support
• Allows media manipulation and transcoding
• Increases server resource usage
• Higher latency due to intermediate hop
• Enhanced security and control

MEDIA PROXY OFF (Disabled):

• Media flows directly between endpoints
• Lower latency (direct path)
• Reduced server resource usage
• No media visibility or recording capability
• NAT traversal issues may occur
• Limited media manipulation options

Use cases:

• Enable media proxy for security-sensitive applications, recording requirements, or NAT environments.
• Disable media proxy for low-latency applications or when direct media connectivity is assured.

Configuration:

1. Navigate to media settings in VOS3000.
2. Toggle media proxy setting based on requirements.
3. Configure RTP port ranges if using media proxy.
4. Test call quality after changing settings.

QUESTION 23:
Web interface demo

ANSWER:
The VOS3000 web interface provides comprehensive management capabilities for system configuration, monitoring, and reporting. The web interface (also called Web VOS) offers intuitive navigation and powerful functionality.

Key features of the web interface:

1. Dashboard: Overview of system status, key metrics, and alerts.
2. Gateway Management: Configure and monitor both mapping and routing gateways.
3. Rate Management: Create and manage rate tables, templates, and rate groups.
4. CDR查询: Access call detail records and generate reports.
5. Security Settings: Configure blacklists, whitelists, and access controls.
6. Monitoring: Real-time system monitoring and alerts.
7. Reports: Generate various reports on traffic, billing, and system performance.
8. System Settings: Configure system parameters, users, and preferences.

Accessing the web interface:

• URL: http://your-server-ip:8080
• Default login: admin with configured password
• HTTPS available with SSL certificate configuration

The web interface demo allows administrators to explore and understand the various features and configuration options available before deploying to production.

QUESTION 24:
Session timeout

ANSWER:
Session timeout configuration is an important access control measure that limits the exposure window if a session is left unattended or credentials are compromised.

Configuring session timeout:

1. Navigate to system security settings in VOS3000.
2. Configure timeout values based on user role:

• Administrative accounts: 15-30 minutes
• Standard user accounts: 60-120 minutes
• Read-only accounts: 120-240 minutes

1. Implement separate timeout policies:

• Web interface sessions
• API access sessions
• Mobile access sessions

1. Configure session timeout behavior:

• Automatic logout on timeout
• Warning before timeout
• Option to extend session

Security considerations:

1. Shorter timeouts for accounts with broader access.
2. Consider implementing idle timeout (no activity) vs. absolute timeout (regardless of activity).
3. Balance security against user convenience.
4. Implement CAPTCHA after failed logins.
5. Log all session timeout events for security review.

Best practices:

• Use 15-30 minute timeouts for administrative accounts
• Use 60-120 minute timeouts for standard users
• Implement session activity monitoring
• Require re-authentication for sensitive operations

QUESTION 25:
How to set sip redirect

ANSWER:
SIP redirect handling in VOS3000 enables sophisticated routing scenarios where calls can be redirected to alternative destinations based on various conditions. SIP redirect responses inform the calling party about alternative destinations.

Configuring SIP redirect:

1. Navigate to SIP settings in VOS3000.
2. Configure redirect handling options:

• Follow redirects automatically
• Return redirects to calling party
• Limit number of redirects to prevent loops

1. Set up redirect routing rules:

• Define conditions for redirect
• Specify alternative destinations
• Configure redirect timeout values

Use cases for SIP redirect:

1. Number Portability: Redirect calls to new numbers when carriers change.
2. Load Balancing: Distribute calls across multiple destinations.
3. Failover: Redirect calls when primary destination is unavailable.
4. Geographic Routing: Redirect based on caller location.
5. Business Hours: Redirect calls based on time of day.

Redirect configuration should be tested thoroughly to ensure calls are properly redirected and billing is applied correctly at each redirect stage.

QUESTION 26:
How to check license information

ANSWER:
Checking VOS3000 license information ensures that your system is properly licensed for the features and capacity you are using.

To check license information:

1. Navigate to system information or license management section in the web interface.
2. View license details:

• License type (trial, standard, enterprise)
• Licensed features and capabilities
• Maximum concurrent calls allowed
• License expiration date
• License status (active, expired, expiring soon)

1. Check feature availability:

• Compare licensed features against enabled functions
• Verify capacity limits match deployment requirements

1. Monitor license utilization:

• Track concurrent call usage against limits
• Receive alerts before reaching capacity

1. License renewal:

• Contact vendor before expiration
• Prepare license upgrade requests
• Document license changes for compliance

License information should be regularly reviewed to ensure compliance and avoid service interruption due to expired licenses.

QUESTION 27:
Cdr queue

ANSWER:
CDR queue management ensures that call detail records are processed completely and accurately even during high-volume traffic periods. The CDR queue buffers incoming call records during processing peaks and manages systematic record handling to prevent data loss.

Understanding CDR queue:

1. Queue Purpose:

• Buffers incoming CDR records during peak periods
• Ensures no call records are lost
• Manages systematic processing to maintain database performance

1. Queue Monitoring:

• Monitor queue depth (number of records awaiting processing)
• Track queue growth trends
• Identify processing bottlenecks

1. Queue Health Indicators:

• Queue depth should remain stable or grow slowly
• Rapid queue growth indicates processing cannot keep pace
• Empty queue may indicate underutilization

Troubleshooting queue issues:

1. If queue grows consistently:

• Check database performance
• Increase processing resources
• Optimize CDR processing settings

1. If queue overflows:

• Immediate action required
• Check database connectivity
• Review recent system changes

1. Prevention:

• Regular monitoring and alerting
• Capacity planning for peak periods
• Database optimization and maintenance

CDR queue management is critical for accurate billing and compliance.

QUESTION 28:
Billing precision

ANSWER:
Billing precision configuration determines how accurately calls are billed in the VOS3000 system. Proper configuration ensures fair billing for both carriers and customers and prevents revenue disputes.

Billing precision options:

1. Per-Second Billing:

• Most accurate billing method
• Charges for exact seconds used
• Requires more sophisticated calculations
• May result in fractional charges

1. Per-Minute Billing:

• Rounds to nearest minute
• Simpler billing calculations
• Common in wholesale VoIP
• Customer-friendly for longer calls

1. 6-Second Increments:

• Industry standard compromise
• Bills in 6-second blocks
• Reduces billing complexity
• Reasonable accuracy

1. Custom Rounding:

• Configure specific rounding rules
• Minimum call duration
• Billing increments
• Connection fees

Configuring billing precision:

1. Navigate to billing settings.
2. Select billing method for each rate group.
3. Configure rounding rules:

• Round up to next unit
• Round to nearest unit
• Truncate partial units

1. Set minimum call duration:

• Some platforms bill minimum 1 minute
• Prevents very short calls with minimal revenue

Billing precision should match customer agreements and industry standards for your market segment.

QUESTION 29:
How to check VOS services

ANSWER:
Checking VOS3000 services ensures that all system components are functioning correctly and enables rapid identification of service degradations.

To check VOS services:

1. Access service management interface in VOS3000 web panel.
2. View status of all system components:

• SIP proxy service
• Database service
• Web interface service
• Billing processing service
• CDR generation service
• Monitoring service

1. Verify critical services show running status.
2. Review any warnings or errors requiring attention.
3. Check service uptime and restart history.

Common service status indicators:

1. Running: Service is active and processing normally.
2. Stopped: Service is not running – requires immediate attention.
3. Warning: Service is running but experiencing issues.
4. Starting/Stopping: Service is in transition state.

Automated monitoring:

• Implement automated monitoring that alerts when services transition to failed or stopped status
• Configure health checks for critical services
• Set up automatic restart for non-critical services
• Log all service status changes for audit trail

Regular service checks should be part of daily operational routine to maintain system reliability.

QUESTION 30:
How to set automatic e-mail report and alarm

ANSWER:
(See Answer to Hot Issues Question 5 – Same Question)

QUESTION 31:
How to generate report manually/automatically

ANSWER:
VOS3000 provides flexible report generation tools that enable customization of time periods, data filters, and output formats.

Manual report generation:

1. Navigate to reports section in VOS3000.
2. Select report type:

• Traffic reports
• Billing reports
• Gateway performance reports
• CDR reports
• Quality reports

1. Configure parameters:

• Date range selection
• Gateway filters
• Customer filters
• Destination filters

1. Choose output format:

• Screen display for immediate review
• PDF for printing
• CSV for Excel analysis
• XML for integration

1. Generate and review report.
2. Export or save as needed.

Automatic report generation:

1. Navigate to scheduled reports configuration.
2. Create scheduled report with:

• Report type
• Schedule (daily, weekly, monthly)
• Recipient list
• Format preferences

1. Configure delivery options:

• Email delivery
• FTP upload
• Local storage

1. Set report retention and archiving.

Common report types:

• Daily traffic summary
• Weekly billing report
• Monthly gateway performance
• Quarterly quality analysis
• Custom ad-hoc reports

Report generation should be optimized for performance, especially for large date ranges.

QUESTION 32:
Black/White list group

ANSWER:
Black and white list group functionality in VOS3000 allows organizing entries into logical groups for easier management and more sophisticated application.

Creating list groups:

1. Create named groups in security settings:

• Fraud prevention group
• Abuse blocking group
• Regulatory compliance group
• Customer-specific groups

1. Add individual entries to groups:

• Numbers (specific or prefix-based)
• IP addresses
• Address ranges

1. Configure group-level application rules:

• Apply globally or to specific gateways
• Set time-based restrictions
• Configure priority between groups

Benefits of list groups:

1. Simplified Management:

• Organize related entries together
• Apply changes to entire group
• Easy to audit and review

1. Sophisticated Application:

• Apply groups to specific gateways
• Configure time-based rules
• Set different actions per group

1. Flexibility:

• Create groups for different purposes
• Mix number-based and IP-based entries
• Nest groups for complex scenarios

Best practices:

• Use descriptive group names
• Document group purpose and criteria
• Regular review of group membership
• Test group application before deployment

QUESTION 33:
Dynamic black list

ANSWER:
(See Answer to Question 18 – Same Question)

QUESTION 34:
How to clear history data

ANSWER:
History data clearing helps manage server storage space and maintains system performance over time. History data including old CDR records, log files, and historical statistics accumulates continuously.

To clear history data in VOS3000:

1. Navigate to data management section in VOS3000.
2. Configure retention policies specifying how long different data types should be retained:

• CDR records: 30-90 days typically
• System logs: 7-30 days typically
• Performance statistics: 30-90 days typically
• Audit logs: 365+ days for compliance

1. Implement automated cleanup jobs:

• Schedule regular maintenance
• Configure cleanup frequency
• Set retention periods per data type

1. Execute manual cleanup if needed:

• Select data to clear
• Confirm deletion
• Verify cleanup completion

Best practices:

1. Balance storage management against compliance requirements.
2. Ensure CDR data is backed up before clearing.
3. Consider archiving older data instead of deletion.
4. Test data recovery procedures before clearing.
5. Document all data clearing activities.
6. Implement automated policies to prevent manual intervention.

Storage management is critical for long-term system performance and cost control.

QUESTION 35:
How to analyze routing

ANSWER:
Routing analysis enables continuous optimization of call routing based on performance data and quality metrics. VOS3000 routing analysis tools provide visibility into routing success rates, gateway performance, and destination-level quality metrics.

To analyze routing in VOS3000:

1. Access routing analysis tools in the web interface.
2. Examine per-gateway success rates:

• Identify gateways with high success rates
• Flag gateways with low success rates
• Track success rate trends over time

1. Analyze per-destination performance:

• Review success rates by destination prefix
• Identify destinations with quality issues
• Track destination-level quality metrics

1. Evaluate failover effectiveness:

• Verify backup gateways are used when primary fails
• Measure failover timing
• Identify failed failover scenarios

1. Generate routing analysis reports:

• Summary of routing performance
• Gateway comparison
• Destination analysis
• Trend analysis

Routing optimization opportunities:

1. Adjust gateway priorities based on performance data.
2. Negotiate better rates with high-performing carriers.
3. Identify and remove underperforming routes.
4. Optimize prefix routing based on actual traffic patterns.
5. Implement quality-based routing rules.

Regular routing analysis supports continuous improvement of call completion rates and cost optimization.

================================================================================

SECTION 3: SERVER

QUESTION 1:
Soft/Hardware allocation of VOS server

ANSWER:
(See Answer to Hot Issues Question 1 – Same Question)

QUESTION 2:
Modify linux timezone & time

ANSWER:
Proper Linux server setup and accurate timezone configuration are essential for precise VOS3000 operation, particularly for accurate billing calculations, correct CDR timestamps, and reliable scheduled reporting functions.

To modify the Linux timezone on your VOS3000 server:

1. Check current timezone:

   date

2. List available timezones:

   timedatectl list-timezones

3. Set desired timezone:

   sudo timedatectl set-timezone your_timezone_here

Example: sudo timedatectl set-timezone UTC
Example: sudo timedatectl set-timezone America/New_York

4. Verify the change:

   date

5. Restart VOS3000 services:

   systemctl restart vos3000

Additional time configuration:

1. Configure NTP for time synchronization:

   timedatectl set-ntp yes

2. Check NTP status:

   timedatectl status

3. Configure NTP servers in /etc/chrony.conf or /etc/ntp.conf.

Best practices:

1. Use UTC for international deployments to simplify CDR correlation across multiple time zones.
2. Ensure NTP synchronization is enabled and working.
3. Document timezone configuration for compliance.
4. Verify CDR timestamps after timezone changes.
5. Consider time configuration as part of initial server setup.

Time configuration affects billing accuracy, CDR correlation, report scheduling, and system logs – all critical for VoIP operations.

================================================================================

SUMMARY

Total Unique FAQ Questions: 35

Categories:

• Server Configuration: 13 questions
• Gateway & Routing: 12 questions
• Security: 7 questions
• Monitoring: 5 questions
• Billing: 8 questions

---

---

Visit MultaHost.Com Blog for Many More Information Related VOS3000 with Screenshots and Videos

---

• VOS3000 Instalacion Servicio Best Professional: Guia Completa para Operadores Telecom
• VOS3000 2.1.9.07 New Version Powerful Features Upgrade Guide Complete
• VOS3000 Installation Service True Expert Setup Guide for VoIP Operators
• Sistema VOS3000 Tarifas LCR True Essential: Tabla de Tarifas, Prefijos, Ruteo Menor Costo y Area Codigos
• Sistema VOS3000 Troncal SIP Important: Registro Upstream, Dominio Local, Cabeceras y Transparencia