A Class 4 softswitch performs this central role
in modern voice networks. It connects telecom operators, wholesale carriers and service providers by managing large volumes of voice traffic across different networks. Understanding its architecture reveals how switching, routing, signalling, billing and monitoring work together to support reliable telecom operations.
For wholesale VoIP providers, the architecture is not just a technical consideration. It directly influences traffic management, operational visibility and the ability to manage business growth. DeNovoLab Class 4 Fusion brings these essential functions into an integrated platform designed for termination and origination traffic.
What Is a Class 4 Softswitch?
The switching layer of a wholesale voice network
A Class 4 softswitch is a software-based switching platform used primarily to manage voice traffic between telecommunications networks. Unlike a traditional circuit-switched environment that relies on dedicated physical switching equipment, a softswitch uses IP-based infrastructure and signalling protocols to coordinate voice calls.
Its main responsibility is to receive call requests from an originating network and determine how those calls should reach their intended destinations.
A wholesale VoIP operator may receive traffic from several customers and terminate it through multiple upstream carriers. The softswitch manages this process by applying routing rules and selecting suitable outgoing connections.
Think of it as an air traffic control system. Aircraft arrive from different directions and must be assigned appropriate routes to reach their destinations. Similarly a Class 4 softswitch receives calls and directs them through available carrier connections according to configured policies.
Class 4 versus Class 5 switching
The distinction is based mainly on the type of traffic and services each system handles.
Class 4 softswitch: Primarily manages traffic between carrier networks. It focuses on wholesale termination, origination, trunk management and large-scale routing.
Class 5 softswitch: Typically handles subscriber-facing services such as residential or business calling features and local telephony services.
A wholesale VoIP provider dealing with international termination and carrier interconnection generally needs Class 4 switching capabilities. Some telecom platforms support additional workflows beyond this core role.
Core Components of Class 4 Softswitch Architecture
A modern Class 4 softswitch consists of several interconnected functional layers. Each performs a specific task while contributing to the overall call-processing workflow.
Switching engine and SIP signalling
The switching engine handles call signalling and coordinates call setup and teardown. In SIP-based networks it processes messages such as INVITE, TRYING, RINGING, OK and BYE as part of the session lifecycle.
For example, when an incoming carrier sends an INVITE request the switch evaluates the call and determines how to proceed. If a suitable outgoing route is available it can initiate the next call leg towards the selected carrier.
The switching layer also handles configured SIP connections and call-processing limits. DeNovoLab Class 4 Fusion uses a C and Sofia-SIP foundation for its switching core and supports SIP trunk operations.
Routing engine
The routing engine determines which outgoing carrier or trunk should receive a call. It evaluates configured rules and can use factors such as destination prefixes, route priorities, supplier costs and traffic performance.
Common routing approaches include:
Least Cost Routing (LCR): Selects routes based on configured cost criteria.
Static routing: Follows a predefined sequence such as top-down, round-robin or percentage-based distribution.
Dynamic routing: Selects routes using changing traffic conditions and configured performance criteria.
Failover routing: Provides an alternative route when the preferred route cannot complete a call.
DeNovoLab Class 4 Fusion supports static and dynamic routing along with routing plans and failover configurations.
Billing and database layer
The billing component applies customer and supplier rating rules to call records. It supports the commercial side of wholesale traffic by connecting call activity with rates, costs and invoices.
The database layer stores operational information such as customer configurations, carriers, trunks, routing rules and billing records. These records help the platform manage traffic consistently and provide information for reporting and investigation.
The value of this architecture comes from coordination. Switching processes the call while routing selects the outgoing path and billing records the commercial details associated with the traffic.
How a Class 4 Softswitch Processes a Call
Understanding the call flow makes the architecture easier to visualize. A typical wholesale termination call passes through several stages.
Step 1: Incoming call reception
A customer or originating carrier sends a SIP call request to the softswitch through a configured ingress connection.
The request contains information needed to process the call such as the calling number, destination number and session details.
The softswitch receives the request and applies the relevant call-processing rules.
Step 2: Validation and routing policy evaluation
The platform evaluates the incoming traffic against configured policies. These may include customer permissions, destination restrictions, account limits and routing criteria.
For example, a call to a particular country may need to follow a specific routing plan while another destination uses a different carrier group.
The routing plan determines which routing strategy applies based on configured conditions such as ANI or DNIS.
Step 3: Outgoing carrier selection
After identifying the applicable routing policy the system selects an outgoing carrier or trunk.
A dynamic routing configuration may consider supplier cost or performance criteria such as ASR and ACD. A static configuration may follow a predetermined order or traffic distribution.
If the preferred route cannot complete the call an available failover rule may direct it towards another configured route.
Step 4: Call establishment and media exchange
The softswitch coordinates outgoing call signalling with the selected carrier. If the call is accepted the session is established and voice media can flow between the connected endpoints.
SIP signalling and RTP media serve different purposes. SIP manages session establishment and control while RTP commonly carries the real-time voice packets.
Depending on network design and configuration media may travel directly between endpoints or through an intermediate media component.
Step 5: Call termination and record generation
When either party ends the call the session is terminated. The system processes the relevant call information and generates a Call Detail Record (CDR).
The CDR can contain details such as call duration, ingress and egress carriers, route information, billing minutes, costs and release causes.
These records support customer billing, supplier settlement, traffic analysis and troubleshooting.
Routing, Traffic Distribution and Network Performance
Why routing is central to the architecture
Routing is one of the most important functions of a Class 4 softswitch because it determines how traffic moves through the wholesale network.
A provider may have several suppliers offering termination for the same destination. However the lowest rate does not always represent the most suitable route.
Operators may also need to consider call completion performance, supplier capacity and route availability.
For example, imagine a provider has three configured routes to the same destination. One offers the lowest cost but has inconsistent call completion. Another has a higher rate but better historical performance. A third serves as a backup.
The routing strategy determines how these options are used according to the operator's business and technical requirements.
Monitoring performance indicators
Several metrics help operators evaluate routing performance:
ASR: Measures the proportion of call attempts that are answered.
ACD: Shows the average duration of answered calls.
PDD: Measures the delay between call initiation and the call progress response.
Latency: Measures the time taken for voice packets to travel across the network.
Jitter: Measures variation in packet arrival time.
Packet loss: Indicates voice packets that fail to reach their destination.
These indicators provide different perspectives on call quality and route behaviour. Operators should interpret them together with destination patterns and carrier-specific information.
DeNovoLab Class 4 Fusion supports routing based on criteria including least cost, highest ASR and highest ACD. Its routing plans can combine static and dynamic strategies to suit different traffic requirements.
Billing, CDRs and Monitoring Within the Softswitch
Connecting call activity with commercial operations
In wholesale VoIP the technical completion of a call is only one part of the transaction. The operator must also determine how the call should be rated and billed.
A Class 4 softswitch connects call-processing information with billing workflows. Customer rates determine the revenue side of the transaction while supplier rates determine the termination cost.
For example, consider a call that generates 4 billable minutes. If the customer rate is $0.02 per minute and the supplier rate is $0.015 per minute then the illustrative revenue is $0.08 and the supplier cost is $0.06. The difference is $0.02 before other operating expenses.
This simple example shows why accurate call records and rate application matter. A small discrepancy repeated across thousands of calls can affect financial reporting.
CDRs and operational troubleshooting
CDRs provide a detailed record of processed calls. They help operators investigate unsuccessful connections, billing questions and carrier performance.
Monitoring and reporting functions add another layer of visibility by helping teams identify traffic changes and operational issues.
DeNovoLab Class 4 Fusion combines billing, monitoring, rate generation, reporting and CDR/PCAP backup and archive capabilities. Its integrated approach connects technical call activity with the information required to manage wholesale operations.
Building a Modern Class 4 Softswitch Infrastructure with DeNovoLab
An integrated platform for wholesale VoIP operators
A Class 4 softswitch should not be evaluated only by its ability to connect calls. Its surrounding architecture must also support routing management, billing, reporting and day-to-day carrier operations.
DeNovoLab Class 4 Fusion is designed as an integrated platform for termination and origination traffic. It brings together:
Switching: SIP trunk operations and call handling.
Routing: LCR, prefix rules, static and dynamic routing and failover.
Billing: Rate decks, customer and vendor billing and invoicing.
Monitoring: Operational visibility into traffic and system activity.
Reporting: Call records and traffic information for business analysis.
Portals: Customer, vendor and agent workflows.
Automation and API integration: Support for automated operational processes and external application integration.
This architecture helps providers manage core telecom workflows through one platform rather than coordinating every function through separate applications.
Deployment flexibility and operational growth
Infrastructure requirements differ according to traffic volume, network design and operational preferences. Some operators prefer self-hosted deployments while others choose cloud infrastructure.
DeNovoLab supports deployment on servers and virtual machines as well as AWS and Google Cloud options. Its Community Edition currently offers a 500-port limit for evaluation and live-traffic use subject to the applicable edition terms. Commercial licensing provides options for expanding capacity.
Operators should assess expected concurrent traffic, call attempts per second, network capacity, storage requirements and redundancy before selecting a deployment design. A softswitch is only one part of the infrastructure; reliable operation also depends on the servers, network connections and operational practices supporting it.
Conclusion: Architecture That Connects Every Part of Voice Traffic Management
Class 4 softswitch architecture provides the foundation for modern wholesale voice networks. Its switching engine processes call signalling while the routing layer selects outgoing carriers and billing systems translate call activity into commercial records. Monitoring and reporting help operators understand how the network performs and where improvements may be needed.
For wholesale VoIP providers the real advantage comes from connecting these functions into a coordinated operating environment.
DeNovoLab Class 4 Fusion brings switching, routing, billing, monitoring, reporting and automation together in a platform built for carrier traffic. Whether you are establishing a wholesale VoIP operation or improving an existing infrastructure its integrated architecture provides a foundation for managing termination and origination workflows.
Explore DeNovoLab Class 4 Fusion and discover an integrated approach to wholesale telecom operations.
Visit https://www.denovolab.com/ to learn more!

0 Comments