VOS3000 Authorization Management, VOS3000 Call Distribution Analysis, VOS3000 System Log Audit, VOS3000 Area Information Configuration, VOS3000 Recent CDR Query, VOS3000 Payment Record Management, VOS3000 Modify CDR Feature, VOS3000 Report Management, VOS3000 Historical Performance Analysis, VOS3000 SIP Registration Management, VOS3000 Internal Audio Management, VOS3000 Phone Card Management

VOS3000 Historical Performance Analysis: Complete ASR ACD Quality Metrics Guide

VOS3000 Historical Performance Analysis: Complete ASR ACD Quality Metrics Guide

๐Ÿ“ˆ How do VoIP operators track whether their network quality is improving or declining over time? Which carriers are consistently delivering the best answer seizure ratios? The VOS3000 historical performance analysis module provides longitudinal quality metrics tracking โ€” enabling operators to analyze ASR (Answer Seizure Ratio), ACD (Average Call Duration), and PDD (Post Dial Delay) trends across any historical period, gateway, or destination. ๐Ÿ”ง

โš™๏ธ According to the official VOS3000 V2.1.9.07 Manual, Section 2.9.2 (Historical Performance), this module aggregates call quality statistics over time to reveal performance trends. Unlike the real-time gateway status view, VOS3000 historical performance analysis shows patterns across days, weeks, or months โ€” providing the context needed for carrier scorecarding and quality management. ๐Ÿ“Š

๐ŸŽฏ This guide covers the complete VOS3000 historical performance analysis system: quality metrics definitions, analysis configuration, trend interpretation, carrier scorecarding, and optimization strategies. For expert VOS3000 configuration assistance, contact us on WhatsApp at +8801911119966. ๐Ÿ“ฑ

๐Ÿ” Overview of VOS3000 Historical Performance Analysis

๐Ÿ“ž The VOS3000 historical performance analysis module transforms raw CDR data into quality trend analysis. It calculates key performance indicators (KPIs) over configurable time periods โ€” enabling operators to identify degrading routes, celebrate improving carriers, and make evidence-based routing decisions. ๐Ÿ’ก

๐ŸŒ Key quality metrics tracked by VOS3000 historical performance analysis:

  • ๐Ÿ“ž ASR (Answer Seizure Ratio): Percentage of calls that are successfully answered
  • โฑ๏ธ ACD (Average Call Duration): Mean duration of connected calls
  • โฑ๏ธ PDD (Post Dial Delay): Time from call initiation to first ringing/answer
  • ๐Ÿ“Š Call Volume: Total call attempts and connected calls
  • ๐Ÿ’ฐ Revenue per Call: Average revenue generation efficiency
MetricFormulaGood RangePoor Range
๐Ÿ“ž ASRAnswered Calls / Total Calls ร— 100%40% – 70%< 30%
โฑ๏ธ ACDTotal Duration / Answered Calls3 – 8 minutes< 1 minute
โฑ๏ธ PDDSetup time to ring/answer2 – 6 seconds> 10 seconds

โš™๏ธ Step-by-Step VOS3000 Historical Performance Analysis

๐Ÿ”ง Running historical performance analysis in VOS3000 follows these steps:

Step 1: Navigate to Historical Performance ๐Ÿ“ก

  1. ๐Ÿ” Log in to VOS3000 Client with administrator credentials
  2. ๐Ÿ“Œ Navigate to: CDR Analysis โ†’ Historical Performance
  3. ๐Ÿ” The Historical Performance analysis form appears

Step 2: Configure Analysis Parameters ๐Ÿ“‹

ParameterDescriptionExample
๐Ÿ“… Start DateAnalysis period beginning2026-01-01
๐Ÿ“… End DateAnalysis period ending2026-04-30
๐Ÿ“Š Group ByTime aggregation intervalDay / Week / Month
๐Ÿ“ก GatewayFilter by specific gateway(s)All or GW_USA_Premium
๐Ÿ‘ค AccountFilter by accountAll or specific reseller
๐Ÿ“ž DestinationFilter by prefix/country92 (Pakistan), 91 (India)
Trend PatternWhat It MeansRecommended Action
๐Ÿ“ˆ ASR RisingRoute quality improvingIncrease traffic allocation to this route
๐Ÿ“‰ ASR FallingRoute quality degradingInvestigate carrier, reduce allocation
๐Ÿ“ˆ ACD RisingCalls lasting longerGood sign โ€” revenue per call increasing
๐Ÿ“‰ ACD FallingCalls ending soonerCheck for quality issues, premature disconnects
๐Ÿ“ˆ PDD RisingSetup delays increasingCarrier network congestion or routing issues

๐Ÿ“Š Carrier Scorecarding with VOS3000 Historical Performance

๐Ÿ† One of the most powerful applications of VOS3000 historical performance analysis is carrier/vendor scorecarding. By comparing performance metrics across multiple gateways over the same period, operators can objectively rank their carriers:

CarrierASRACDPDDScore
๐Ÿ“ก Carrier A62%4.2 min3.1 secโญโญโญโญโญ
๐Ÿ“ก Carrier B48%3.8 min5.4 secโญโญโญโญ
๐Ÿ“ก Carrier C31%2.1 min8.9 secโญโญ

๐Ÿ”„ Using VOS3000 Historical Performance for Route Optimization

๐Ÿ“ก The primary business application of VOS3000 historical performance analysis is route optimization through evidence-based carrier management. By tracking ASR, ACD, and PDD trends for each termination gateway over time, operators can make informed decisions about traffic allocation. When a carrier’s ASR shows a consistent downward trend over two or more weeks, this signals a quality degradation that warrants investigation and potentially reducing traffic allocation to that route.

Conversely, carriers with improving or stable high ASR should receive increased traffic allocation to maximize call completion rates and revenue. The historical performance data transforms carrier management from a reactive process (waiting for customer complaints) to a proactive one (detecting quality changes before they impact customers). ๐Ÿ“ˆ

๐Ÿ“Š Route optimization decision framework using historical performance:

Performance PatternDurationRecommended Action
๐Ÿ“‰ ASR drop > 10%1-2 daysMonitor, investigate root cause
๐Ÿ“‰ ASR drop > 15%3-7 daysReduce traffic, contact carrier, add backup route
๐Ÿ“ˆ PDD increase > 30%1 week+Investigate network path, consider alternative route
๐Ÿ“‰ ACD drop > 20%2+ weeksQuality issue โ€” check for audio problems, route congestion
๐Ÿ“ˆ ASR consistently high1 month+Increase traffic allocation, negotiate better rates

๐Ÿ“Š Performance Analysis and SLA Compliance

โš–๏ธ For VoIP operators who provide Service Level Agreements (SLAs) to their customers, VOS3000 historical performance analysis is the tool for proving SLA compliance. SLAs typically specify minimum ASR thresholds, maximum PDD limits, and minimum ACD values for different destination categories. By running historical performance analysis for each SLA-covered destination over the contract period, operators can generate objective evidence of whether they met or exceeded the agreed quality standards.

This data is invaluable during SLA review meetings and can prevent unwarranted penalty charges from customers who claim quality was below standards. Operators should establish a regular cadence of SLA reporting โ€” typically monthly โ€” using the historical performance analysis module as the data source, supplemented by data from the report management system for financial SLA metrics. ๐Ÿ“‹

โš ๏ธ Interpreting Performance Data Correctly

๐Ÿ” Correct interpretation of VOS3000 historical performance data requires understanding the context behind the numbers. A low ASR does not always indicate a carrier problem โ€” it may reflect legitimate network conditions in the destination country (such as mobile phone switched off, busy lines, or network congestion during peak hours). Similarly, short ACD values may indicate that callers in certain cultural contexts naturally make shorter calls, not that call quality is poor. PDD values can be affected by the originating network’s dial plan configuration, not just the terminating carrier’s performance.

The key to meaningful analysis is comparing performance against your own historical baseline for the same destination, same time period, and same traffic pattern, rather than using generic industry benchmarks. Week-over-week and month-over-month comparisons of the same route provide the most actionable insights. ๐Ÿ“Š

๐Ÿ’ก Best Practices for Historical Performance Analysis

PracticeRecommendation
๐Ÿ“… Weekly ReviewsRun performance analysis every Monday for previous week
๐ŸŒ By DestinationAnalyze top 10 destinations separately โ€” quality varies by route
๐Ÿ“Š Set ThresholdsDefine minimum ASR/ACD thresholds per destination
๐Ÿ“ˆ Track TrendsFocus on week-over-week changes, not absolute values
๐Ÿ“ง Share ReportsSend carrier scorecards to vendors monthly

๐Ÿ’ฌ For performance analysis support, WhatsApp us at +8801911119966. ๐Ÿ“ฑ

โ“ Frequently Asked Questions

โ“ How does VOS3000 calculate ASR in historical performance?

๐Ÿ“ž VOS3000 calculates ASR as: (Number of calls with status “Answered” / Total number of call attempts) ร— 100%. Calls with statuses like “Busy,” “No Answer,” “Cancel,” and failed calls are counted in the denominator but not the numerator. This is the industry-standard ASR calculation. The historical performance analysis aggregates this across the selected time period and grouping interval (day/week/month). ๐Ÿ“Š

โ“ What is a good ASR value for international VoIP routes?

๐ŸŽฏ ASR benchmarks vary significantly by destination country and route type. Generally: Premium routes to developed countries (USA, UK, Western Europe) should achieve 50-70% ASR. Routes to developing markets may see 30-50% ASR. CLI routes typically have higher ASR than non-CLI. If ASR drops below 25% consistently, investigate carrier quality or potential fraud. Always compare against your own historical baseline for the same destination rather than generic benchmarks. ๐Ÿ“ˆ

โ“ Can I set up automated alerts when performance drops?

๐Ÿšจ Yes, VOS3000 provides mapping and routing alarms that can trigger when ASR, ACD, or call rate fall below configured thresholds. These alarms can send email notifications, SMS, or voice alerts. For historical trend-based alerting (e.g., “alert when ASR drops 10% week-over-week”), use external monitoring tools that pull data via the VOS3000 Web API. ๐Ÿ“Š

โ“ How far back can I analyze historical performance?

๐Ÿ“… The analysis range is limited only by your CDR retention policy. Most operators retain 3-12 months of granular CDR data. For longer-term analysis, the report management scheduled reports can save monthly performance summaries indefinitely. Performance analysis on very large date ranges (6+ months) may take longer to generate. โฑ๏ธ

โ“ What causes sudden ASR drops?

โš ๏ธ Sudden ASR drops can be caused by: (1) Carrier network issues or outages, (2) Route congestion during peak hours, (3) Destination country regulatory blocks, (4) CLI suppression on routes requiring CLI, (5) Fraud attacks generating fake call attempts, (6) Incorrect routing configuration sending calls to wrong gateway. Use the call distribution analysis combined with gateway fail analysis to identify root causes. ๐Ÿ”ง

โ“ Can I compare multiple gateways in one analysis?

๐Ÿ“Š Yes, the VOS3000 historical performance analysis allows selecting multiple gateways for comparison. The results show performance metrics side-by-side for each gateway, making it easy to identify your best and worst performing carriers. This is the recommended approach for carrier scorecarding and route optimization decisions. ๐Ÿ“ˆ

๐Ÿ“Š Advanced Historical Performance Analysis Techniques

๐Ÿ”ง Beyond basic ASR/ACD/PDD tracking, experienced VOS3000 operators employ several advanced analysis techniques using historical performance data. One powerful technique is “same-day comparison” โ€” running historical performance analysis for the same day of the week across multiple weeks (e.g., comparing all Mondays in a month) to establish a reliable baseline while controlling for day-of-week traffic variations. Another technique is “gateway pair analysis” โ€” comparing two gateways that carry traffic to the same destination to determine which one consistently delivers better quality, enabling evidence-based routing decisions.

A third technique is “pre/post change analysis” โ€” running historical performance for the period before and after a configuration change (such as a route modification or carrier switch) to objectively measure the impact of the change on call quality metrics. These systematic approaches transform historical performance analysis from a passive reporting tool into an active decision-making framework. ๐Ÿ“ˆ

๐Ÿ“Š Advanced analysis methodology:

  1. ๐Ÿ“… Baseline Establishment: Run 30-day historical performance for each major destination to establish normal ASR/ACD/PDD ranges
  2. ๐Ÿ“Š Threshold Definition: Set alert thresholds at 2 standard deviations from baseline for each metric
  3. ๐Ÿ” Anomaly Detection: Compare current week performance against baseline to identify statistically significant deviations
  4. ๐Ÿ“ก Root Cause Analysis: When anomalies are detected, drill down by gateway and time-of-day to isolate the cause
  5. ๐Ÿ”„ Corrective Action: Adjust routing, contact carriers, or modify configuration based on analysis findings
  6. ๐Ÿ“ˆ Verification: Re-run analysis after corrective action to confirm the issue is resolved

โš™๏ธ Performance Analysis System Configuration

๐Ÿ”ง The VOS3000 historical performance analysis module relies on underlying CDR data for its calculations. The accuracy and granularity of the analysis depends on several system configuration factors. The CDR write interval parameter determines how quickly call records are written to the database โ€” shorter intervals provide more real-time data but increase database load. The CDR retention policy determines how far back historical performance analysis can reach โ€” operators who need 12-month trend analysis must ensure their CDR retention covers at least that period.

The database performance also affects analysis speed โ€” queries on very large CDR datasets (millions of records) may take several minutes to complete. For optimal analysis performance, operators should maintain database indexes, regularly clean up old CDR data through the Data Maintenance module, and schedule large analyses during off-peak hours. The system parameter for CDR aggregation intervals can also be tuned to balance between analysis granularity and storage efficiency. โฑ๏ธ

๐Ÿ“ž Need Expert Help with VOS3000 Historical Performance Analysis?

๐Ÿ”ง Effective VOS3000 historical performance analysis is the foundation of quality-driven routing and carrier management. Whether you need help configuring analysis parameters, interpreting trends, or setting up carrier scorecards, our team is ready to assist. ๐Ÿ’ฌ WhatsApp: +8801911119966 โ€” Get instant expert support for VOS3000 quality analytics.


๐Ÿ“ž Still have questions about VOS3000 historical performance analysis? Reach out on WhatsApp at +8801911119966 โ€” we provide professional VOS3000 installation, configuration, and quality analytics services worldwide. ๐ŸŒ


๐Ÿ“ž 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 Authorization Management, VOS3000 Call Distribution Analysis, VOS3000 System Log Audit, VOS3000 Area Information Configuration, VOS3000 Recent CDR Query, VOS3000 Payment Record Management, VOS3000 Modify CDR Feature, VOS3000 Report Management, VOS3000 Historical Performance Analysis, VOS3000 SIP Registration Management, VOS3000 Internal Audio Management, VOS3000 Phone Card ManagementVOS3000 Authorization Management, VOS3000 Call Distribution Analysis, VOS3000 System Log Audit, VOS3000 Area Information Configuration, VOS3000 Recent CDR Query, VOS3000 Payment Record Management, VOS3000 Modify CDR Feature, VOS3000 Report Management, VOS3000 Historical Performance Analysis, VOS3000 SIP Registration Management, VOS3000 Internal Audio Management, VOS3000 Phone Card ManagementVOS3000 Authorization Management, VOS3000 Call Distribution Analysis, VOS3000 System Log Audit, VOS3000 Area Information Configuration, VOS3000 Recent CDR Query, VOS3000 Payment Record Management, VOS3000 Modify CDR Feature, VOS3000 Report Management, VOS3000 Historical Performance Analysis, VOS3000 SIP Registration Management, VOS3000 Internal Audio Management, VOS3000 Phone Card Management
VOS3000 LRN Number Portability, VOS3000 LRN Server Configuration, VOS3000 Server-Side End Reasons, VOS3000 H323 Q850 Cause Codes, VOS3000 SIP Response Codes CDR

VOS3000 Server End Reasons Definitive Important 25-Code Reference Guide

VOS3000 Server End Reasons Definitive 25-Code Reference Guide

Understanding VOS3000 server end reasons is essential for any VoIP operator who needs to diagnose call failures, resolve billing disputes, and improve overall network quality. VOS3000 records 25 distinct server-side end reason codes in its CDRs, each representing a different cause for call termination as observed from the softswitch perspective. These codes go beyond simple SIP response codes or Q.850 cause values โ€” they represent the VOS3000 internal decision for why a call ended, providing the most granular insight into call lifecycle events. Need help analyzing your CDRs? Contact us on WhatsApp: +8801911119966.

Unlike SIP response codes (which are protocol-level) or Q.850 cause codes (which are network-level), VOS3000 server end reasons are application-level codes generated by the softswitch itself. They capture scenarios that are unique to the VOS3000 platform, such as billing-related terminations, route selection failures, and account management events. By analyzing these codes across your CDR data, you can identify systemic issues affecting ASR, pinpoint billing discrepancies, and understand exactly why calls fail at the softswitch level.

Complete VOS3000 Server End Reasons Code Table

The following table lists all 25 VOS3000 server-side end reason codes as documented in ยง4.5 of the administration manual. Each code has a specific meaning that maps to an internal VOS3000 decision point in the call processing pipeline.

CodeEnd ReasonCategory
1Normal ClearingNormal
2User BusyNormal
3No AnswerNormal
4Unallocated NumberNumber Error
5Network CongestionNetwork
6Route Not FoundRouting
7Rate Not FoundBilling
8Balance InsufficientBilling
9Account ExpiredAccount
10Account DisabledAccount
11Caller HangupNormal
12Callee HangupNormal
13Server Forced ReleaseSystem
14Session TimeoutTimeout
15Media TimeoutTimeout
16Authentication FailedSecurity
17Unauthorized IPSecurity
18Concurrent Limit ExceededCapacity
19CPS Limit ExceededCapacity
20Blacklist MatchSecurity
21Gateway UnavailableRouting
22No Available RouteRouting
23Call RejectedNetwork
24Prepaid Duration ExceededBilling
25Service Not SubscribedAccount

End Reason Categories and Severity Classification

The 25 VOS3000 server end reasons can be grouped into six functional categories. Understanding these categories helps operators quickly identify whether call failures are due to billing issues, routing problems, security blocks, or normal call completion events. For more on how these codes affect your quality metrics, see our VOS3000 ASR ACD analysis guide.

CategoryCodesImpact LevelAction Required
Normal1, 2, 3, 11, 12LowNo action needed
Routing6, 21, 22HighCheck rate table and gateway config
Billing7, 8, 24HighReview rates and account balances
Account9, 10, 25MediumVerify account status and subscriptions
Security16, 17, 20CriticalInvestigate unauthorized access attempts
Capacity/Timeout5, 14, 15, 18, 19Medium-HighScale resources or adjust limits

Common End Reasons and Their Troubleshooting Steps

The most frequently encountered VOS3000 server end reasons in production environments typically fall into a handful of codes. Understanding what each means and how to address it is critical for maintaining healthy ASR and ACD metrics. For detailed SIP-level troubleshooting, see our VOS3000 SIP debug guide.

CodeEnd ReasonCommon CauseResolution
6Route Not FoundNo matching prefix in route tableAdd prefix to routing configuration
7Rate Not FoundDialed prefix not in rate tableAdd rate entry for missing prefix
8Balance InsufficientPrepaid account depletedRecharge account balance
22No Available RouteAll gateways busy or offlineAdd more gateways or check existing
15Media TimeoutNo RTP received after call setupCheck NAT/firewall, media proxy settings

End Reasons and Billing Impact Analysis

Certain VOS3000 server end reasons directly affect billing calculations. Code 8 (Balance Insufficient) and Code 24 (Prepaid Duration Exceeded) are billing-driven terminations initiated by the VOS3000 billing engine. Code 7 (Rate Not Found) means the call was never rated and generates no revenue. Understanding which end reasons produce billable vs non-billable CDRs is essential for revenue assurance. For more on billing configurations, see our VOS3000 billing system guide.

End ReasonCDR GeneratedBillableBilling Mode Code
Normal Clearing (1)YesYes0 or 1
Rate Not Found (7)YesNo-1
Balance Insufficient (8)YesNo-1
Prepaid Duration Exceeded (24)YesYes (partial)1
Route Not Found (6)YesNo-1

How End Reasons Map to SIP and H.323 Codes

VOS3000 server end reasons are internal to the platform, but they often have corresponding SIP response codes or Q.850 cause codes in the signaling layer. Understanding these mappings helps correlate CDR end reasons with protocol-level traces captured by tools like Wireshark or tcpdump. For protocol-level analysis, message us on WhatsApp: +8801911119966.

Server End ReasonSIP ResponseQ.850 Cause
Normal Clearing200 OK (BYE)16
User Busy486 Busy Here17
No Answer408 Request Timeout18 or 19
Route Not Found404 Not Found1 or 3
Balance Insufficient403 Forbidden21
Network Congestion503 Service Unavailable42

Frequently Asked Questions About VOS3000 Server End Reasons

What are VOS3000 server end reasons?

VOS3000 server end reasons are 25 internal codes that the softswitch records in CDRs to indicate why a call was terminated from the server’s perspective. These codes cover normal call completion (like user hangup and normal clearing), routing failures (like route not found and no available route), billing issues (like balance insufficient and rate not found), security events (like authentication failed and unauthorized IP), and system-level terminations (like server forced release and session timeout). They are documented in ยง4.5 of the VOS3000 administration manual.

How do server end reasons differ from SIP response codes?

VOS3000 server end reasons are application-level codes generated by the softswitch itself, while SIP response codes are protocol-level status indicators defined in RFC 3261. A single SIP response code like 503 Service Unavailable could map to multiple VOS3000 end reasons depending on the internal context โ€” it could be Network Congestion (code 5), No Available Route (code 22), or Gateway Unavailable (code 21). Server end reasons provide more granular insight into the VOS3000 internal decision process than SIP codes alone.

Which end reasons indicate billing problems?

The primary billing-related end reasons are Code 7 (Rate Not Found โ€” no matching rate entry), Code 8 (Balance Insufficient โ€” prepaid account depleted), and Code 24 (Prepaid Duration Exceeded โ€” call ended because maximum allowed duration was reached). These codes directly indicate that billing engine decisions terminated the call. High volumes of code 7 suggest missing rate table entries, while high code 8 volumes indicate accounts running out of balance frequently.

How can I analyze end reasons across my CDR data?

You can analyze VOS3000 server end reasons by querying the CDR database and grouping records by end reason code. This reveals the distribution of call termination causes and helps identify systemic issues. For example, if code 22 (No Available Route) dominates, you need more gateway capacity. If code 7 (Rate Not Found) is frequent, you have gaps in your rate tables. Use the VOS3000 CDR query tools or export CDRs to an external analytics platform for detailed analysis.

What does Server Forced Release (code 13) mean?

Code 13 (Server Forced Release) indicates that the VOS3000 softswitch actively terminated the call for an internal reason, such as a system-level resource constraint, administrative intervention, or a forced disconnect triggered by a monitoring rule. Unlike timeout-based terminations, Server Forced Release is an active decision by the softswitch to end the call. Investigating the system logs around the time of the CDR can reveal the specific trigger for the forced release.

Are all 25 end reason codes used in both SIP and H.323 calls?

Yes, the 25 VOS3000 server end reason codes are protocol-independent and apply to both SIP and H.323 calls. The same internal end reason code is recorded in the CDR regardless of the signaling protocol used. However, the corresponding protocol-level codes differ โ€” a SIP call with end reason 2 (User Busy) will show 486 Busy Here in the SIP layer, while an H.323 call with the same end reason will show Q.850 cause code 17. The server end reason provides a unified view across both protocols.

Need Expert VOS3000 CDR Analysis?

Analyzing VOS3000 server end reasons across millions of CDRs requires both technical expertise and the right analytical approach. Our VOS3000 specialists can help you build CDR analysis workflows, identify the root causes of call failures, and optimize your routing and billing configurations to improve ASR and reduce revenue leakage.

Contact us on WhatsApp: +8801911119966

Whether you need help interpreting end reason distributions, troubleshooting high failure rates, or building automated CDR monitoring dashboards, our team is here to assist. Reach out today at +8801911119966 and take control of your VOS3000 call quality.


๐Ÿ“ž 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 LRN Number Portability, VOS3000 LRN Server Configuration, VOS3000 Server-Side End Reasons, VOS3000 H323 Q850 Cause Codes, VOS3000 SIP Response Codes CDRVOS3000 LRN Number Portability, VOS3000 LRN Server Configuration, VOS3000 Server-Side End Reasons, VOS3000 H323 Q850 Cause Codes, VOS3000 SIP Response Codes CDRVOS3000 LRN Number Portability, VOS3000 LRN Server Configuration, VOS3000 Server-Side End Reasons, VOS3000 H323 Q850 Cause Codes, VOS3000 SIP Response Codes CDR