A carrier can offer competitive rates yet deliver inconsistent call quality. A trunk can appear operational while certain destinations experience poor call completion, making it difficult for telecom operators to identify where performance is deteriorating.
For wholesale VoIP businesses, monitoring carrier, trunk and destination performance together is essential for controlling costs, improving routing decisions and maintaining reliable service. DeNovoLab Class 4 Fusion brings switching, routing, billing, monitoring and reporting into one operating platform to help operators connect these critical workflows.
Understand the Three Levels of VoIP Performance Monitoring
Effective monitoring begins by understanding what each performance level reveals. Carrier-level metrics provide a broader view of supplier performance while trunk-level metrics help isolate connection issues and destination-level metrics expose problems affecting particular number ranges or markets.
Carrier performance: Evaluate the supplier
Carrier monitoring helps operators understand how reliably each supplier handles traffic. Useful indicators include Answer-Seizure Ratio (ASR), Average Call Duration (ACD), call failure patterns and termination costs.
For example, a carrier may deliver acceptable results for one destination but perform poorly for another. Looking only at its overall performance can hide these differences.
Trunk performance: Identify connection problems
A carrier may have multiple trunks with different configurations or traffic loads. Monitoring each trunk helps identify issues such as connection failures, capacity constraints or unexpected changes in call outcomes.
Destination performance: Find specific weaknesses
Destination-level analysis examines traffic to individual countries, area codes or number prefixes. This is important because performance can vary significantly across destinations even when the same carrier is used.
DeNovoLab Class 4 Fusion supports carrier and trunk workflows alongside routing and CDR reporting. Its data model includes fields such as ingress and egress carrier, trunk, destination information and call outcomes. These records help operators investigate performance at multiple levels.
Track the Metrics That Reveal Performance Changes
Monitoring becomes useful when teams focus on indicators that support clear operational decisions. A large dashboard full of numbers is less valuable than a small set of metrics that reveal meaningful changes.
Answer-Seizure Ratio (ASR)
ASR measures the proportion of call attempts that receive an answer according to the system's measurement method. A declining ASR can indicate routing problems, destination issues or changes in traffic composition.
For example, if a destination's ASR falls from 55% to 30% after a routing change, the operator should investigate the affected traffic before assuming the carrier is responsible. These figures are illustrative rather than industry benchmarks.
Average Call Duration (ACD)
ACD measures the average duration of answered calls under the platform's calculation rules. A sudden decrease may indicate unsuccessful call experiences, short-duration calls or a change in the traffic mix.
ACD should be interpreted alongside ASR and call records because short calls can be legitimate in some business scenarios.
Cost and billing indicators
Review termination costs, billed minutes and rate changes alongside call quality. A low-cost route may not be the most commercially effective choice if it consistently produces poor results.
The key principle: interpret metrics together and compare similar traffic periods, destinations and customer profiles rather than relying on one isolated number.
Connect Carrier, Trunk and Destination Data in One Workflow
When performance information is scattered across switching logs, spreadsheets and billing systems, troubleshooting becomes slower. Teams may spend valuable time collecting records before they can determine whether an issue is related to a carrier, trunk or destination.
A unified workflow helps reduce this investigative effort.
Start with call detail records
Call detail records (CDRs) provide information about individual calls. Depending on the available fields, they can show call duration, billing results, ingress and egress carriers, trunks, rates and routing information.
DeNovoLab's documented CDR structure includes ingress and egress carrier fields, trunk information, call duration, billing data and routing details. These fields provide a useful foundation for investigating call outcomes.
Follow a consistent investigation process
When a performance issue appears:
Identify the affected destination or prefix.
Compare the relevant ASR, ACD and call failure patterns.
Identify which carriers and trunks handled the affected traffic.
Review the associated CDRs and routing decisions.
Check for rate changes, capacity constraints or configuration changes.
Apply a targeted correction and monitor the results.
For example, if only one destination prefix shows a sharp decline in call completion, compare the trunks carrying that traffic with those serving other destinations. This helps narrow the investigation instead of treating the entire network as the source of the problem.
Use Performance Insights to Improve Routing Decisions
Monitoring should lead to action. Once operators identify an underperforming carrier or trunk, they need a way to adjust routing policies according to their business rules and network conditions.
Balance cost with call quality
Least-cost routing selects routes according to configured cost criteria. Performance-based routing can prioritize routes using indicators such as ASR or ACD.
DeNovoLab Class 4 Fusion supports static and dynamic routing. Its documented dynamic routing options include least-cost, highest-ASR and highest-ACD selection. Routing plans can combine strategies according to configured calling and called number criteria.
For instance, suppose Carrier A offers a lower rate but consistently delivers weaker call completion for a particular destination. Carrier B costs slightly more but performs better. A properly configured routing policy can prioritize the route that best meets the operator's cost and performance objectives.
Configure fallback routes
Failover routing provides an alternative path when a preferred route cannot handle a call. This can help maintain service continuity when a trunk or route becomes unavailable.
However, fallback rules should be tested carefully. An alternative route must have suitable capacity and compatible commercial terms. Operators should also monitor whether failover changes increase costs or alter call quality.
The objective is not to select the cheapest route in every situation. It is to establish routing rules that balance commercial requirements with reliable call delivery.
Investigate Problems with Monitoring and Call Traces
Performance metrics indicate where to investigate but do not always explain why an issue occurred. Detailed call records and SIP traces can provide the additional evidence needed to identify the underlying cause.
Move from an alert to the evidence
A sudden increase in failed calls may result from an unavailable trunk, an incorrect routing configuration, a carrier-side rejection or a signaling issue. The correct response depends on the evidence.
Review the call's signaling sequence, response codes, ingress and egress paths and relevant timestamps. Comparing successful and unsuccessful calls can help isolate the difference.
DeNovoLab Class 4 Fusion documents CDR access and PCAP search workflows that support call-level investigation. SIP packet captures can help technical teams inspect signaling exchanges when the available records do not fully explain a failure.
For example, if a call reaches the ingress side but fails during egress setup, the investigation can focus on the selected route and the downstream response rather than immediately changing the entire routing policy.
Access to technical evidence makes troubleshooting more precise and reduces the risk of applying broad changes to a localized problem.
Build a Repeatable Monitoring and Review Routine
One-time investigations can resolve individual issues but consistent monitoring helps teams detect recurring problems earlier. A structured review process also makes it easier to assess whether operational changes are producing the intended results.
Establish practical review intervals
Real-time or frequent checks: Monitor major call failures, unexpected traffic changes and important trunk availability indicators where supported by your monitoring setup.
Daily reviews: Examine destination-level ASR and ACD changes, high-cost traffic and repeated call failures.
Weekly reviews: Compare carrier performance, identify recurring trunk issues and evaluate routing adjustments.
Monthly reviews: Review supplier performance trends, rate changes, traffic distribution and billing discrepancies.
These intervals are suggested operating practices rather than fixed industry standards. The appropriate frequency depends on traffic volume, business risk and monitoring capabilities.
Define thresholds based on your network
Avoid adopting universal ASR or ACD thresholds without considering your traffic mix. Establish baselines for important destinations and investigate material deviations from those baselines.
For example, an operator might configure an internal alert when a destination's ASR falls significantly below its recent average over a sufficient sample of calls. The threshold should account for low-volume destinations where a few calls can distort the results.
Document the issue, investigation, corrective action and outcome. Over time, this creates a practical record of what works across your carrier and destination portfolio.
Bring Monitoring and Operations Together with DeNovoLab Class 4 Fusion
The value of monitoring increases when performance insights connect directly to routing, switching and billing workflows. Operators should not have to reconstruct the full picture manually every time a destination experiences problems.
One platform for connected workflows
DeNovoLab Class 4 Fusion is designed to bring switching, routing, billing, monitoring, reporting and automation into one operating platform. Its documented capabilities support carrier and trunk configuration, routing decisions, CDR access and operational analysis.
This integrated approach helps teams connect call outcomes with the routes and carriers involved. It also provides a foundation for investigating billing results and reviewing traffic performance within the broader operating workflow.
When evaluating the platform, verify that the reports and fields available in your chosen edition support the specific carrier, trunk and destination views your team requires. Confirm how frequently the relevant data is updated and which alerts or automation rules need to be configured.
A unified platform does not remove the need for good operational procedures. Clear ownership, sensible alert thresholds and regular performance reviews remain essential to making monitoring useful.
Conclusion: Turn VoIP Performance Data into Better Decisions
Monitoring carrier, trunk and destination performance in one workflow gives wholesale VoIP operators a clearer way to identify service problems, investigate their causes and improve routing decisions. By combining ASR, ACD, cost analysis, CDR review and SIP troubleshooting, teams can move beyond isolated metrics and make decisions based on the complete traffic picture.
DeNovoLab Class 4 Fusion connects switching, routing, billing, monitoring and reporting capabilities to support this approach. Its integrated workflows can help operators investigate call performance and manage their wholesale VoIP operations more systematically.
Ready to improve visibility across your carrier network? Visit www.denovolab.com to explore DeNovoLab Class 4 Fusion and evaluate how it fits your monitoring and routing requirements.
0 Comments