Control the routing layer of your voice business.
Discuss Class 4 switching, trunk management, rates and traffic visibility for your carrier operation.
- 01INGRESSTrunk admission
- 02NORMALIZATIONNumber & identity rules
- 03ROUTE POLICYLCR + quality review
- 04EGRESSSelected carrier trunk
- 05CALL RECORDSDuration & outcome
- 06RATING REVIEWDeck & billing records
Separate voice transit from subscriber features.
Understand the switching role
A Class 4 softswitch sits in the carrier voice path, handling traffic between networks or trunk groups. The discussion centers on ingress, egress, routing policies and usage records. Subscriber applications such as team extensions and voicemail belong to a different layer of the communications service.
Define the trunks, destination groups and commercial relationships that the switching design must represent. Establish which team controls rates and route policies, and which changes require engineering approval.
Connect policy with operational evidence
Routing needs a commercial basis and a quality basis. A preferred route may change when rates change, a destination becomes unavailable or a performance objective is not met. Evaluate how policy decisions will be recorded and how operations will identify the path used by a particular call.
Agree reporting, billing and access requirements as part of the platform scope. Available controls and account permissions must be confirmed before building a workflow around them. Test a controlled configuration change and its reversal before relying on the process in production.
Where it fits in your network
- 01Ingress trunks
- 02Policy and controls
- 03Routing engine
- 04Egress trunks
Plan the connection around your traffic
Ingress and egress
Model customer and supplier trunks separately. Define ownership, normalization and traffic policies at each boundary.
Routing policy
Evaluate least-cost, quality, prefix and priority rules against commercial requirements. Review which controls are included in the proposed deployment.
Operational visibility
Define the handover through reporting requirements. Agree access, billing responsibilities and support boundaries.
Agree the details before production
| Parameter | Planning detail |
|---|---|
| Commercial model | Confirm dedicated or managed platform scope. |
| Rates | Define rate formats, currencies and effective dates. |
| Controls | Agree CPS, concurrent-call and destination restrictions. |
| Reporting | Confirm exports, retention and permissions. |
What to review with your team
| Review area | What to establish |
|---|---|
| Ingress / egress | Trunk ownership, destination groups and permitted traffic. |
| Policy control | Rate versions, route preferences and change approval. |
| Operations | CDR needs, access roles, reporting and incident evidence. |
Before the next step
Is a Class 4 platform a hosted office phone system?
No. Carrier switching addresses network-to-network voice transit. Hosted PBX supplies end-user calling features and is organized under Business Communications.
Are all listed controls included by default?
The final platform scope, permissions and available operations must be agreed for the service. Use the technical review to confirm required controls before implementation.
Explore the sample operating views.
DID management
Inventory, assignment and inbound routing.
| Number / market | Type | Assigned route | State |
|---|---|---|---|
| +1 212 555 0104 | Local | Demo trunk A | Assigned |
| +1 305 555 0112 | Local | Demo trunk B | Assigned |
| +44 · masked example | Geographic | Unassigned | Review |
| +49 · masked example | Geographic | Demo trunk C | Assigned |
Traffic overview
Read outcomes alongside the traffic profile.
| Destination | Attempts | ASR | ACD | Cost | Status |
|---|---|---|---|---|---|
| Demo group A | 8,240 | 62.1% | 04:42 | $48.20 | Normal |
| Demo group B | 5,180 | 61.3% | 04:28 | $36.10 | Review |
Carrier routing
A sample policy view, not an active configuration.
| Priority | Route group | Policy | CPS limit | State |
|---|---|---|---|---|
| 01 | Demo primary | Quality preference | 250 | Enabled |
| 02 | Demo alternate | Fallback path | 150 | Standby |
| 03 | Demo restricted | Destination review | — | Restricted |
Call detail records
Example call references and reporting fields.
| Call reference | Direction | Duration | Outcome | Trunk |
|---|---|---|---|---|
| DEMO-004812 | Outbound | 04:36 | Answered | Demo trunk A |
| DEMO-004813 | Inbound | 02:18 | Answered | Demo trunk B |
| DEMO-004814 | Outbound | 00:00 | Not answered | Demo trunk A |
Sample records omit personal calling data. Actual fields and retention depend on the agreed reporting scope.
Rate management
Illustrative commercial data for comparison only.
| Rate deck | Effective | Billing increment | Currency | State |
|---|---|---|---|---|
| Demo deck A | Example period | 60 / 60 sec | USD | Sample |
| Demo deck B | Example period | 30 / 6 sec | USD | Sample |
| Demo deck C | Example period | 60 / 1 sec | USD | Sample |
Not a quote or published rate deck. Confirm destination rates, increments and effective dates with sales.
SIP trunk overview
A visual inventory of connection boundaries.
| Trunk | Direction | CPS | Concurrent limit | State |
|---|---|---|---|---|
| Demo trunk A | Bidirectional | 250 | 500 | Configured |
| Demo trunk B | Inbound | 100 | 300 | Configured |
| Demo trunk C | Outbound | 50 | 100 | Review |
Billing overview
Illustrative usage and invoice presentation.
- Voice usage
- $984.60
- Number services
- $240.00
- Other services
- $60.00
| Document | Period | Amount | State |
|---|---|---|---|
| DEMO-INV-001 | Example month | $1,284.60 | Sample |
Illustrative amounts only. Not an account balance, invoice or offer.
Number selection
A sample workflow for selecting numbering requirements.
| Illustrative result | Type | Next step |
|---|---|---|
| +1 212 555 0104 | Local | Check availability |
| +1 212 555 0116 | Local | Review requirements |
Reserved example numbers, not purchasable inventory. This demonstration does not place orders.
Illustrative interface concept with sample data. Actual portal features, permissions and workflows are confirmed for your account.
Follow the call through the switching layer
Carrier switching begins with an ingress relationship, then applies the treatment needed to select an egress path. Number normalization, rating inputs and route policy need to work together. The goal is a call that can be traced from its incoming trunk to the selected destination path and the record used for reporting.
This is different from a hosted PBX that manages user extensions and office features. A Class 4 discussion belongs with the people responsible for trunk groups, traffic economics, carrier relationships and operational control. Use Business Communications when buying a phone system for your own staff.
Keep commercial rules and quality rules distinct
The cheapest eligible route is a commercial choice. A quality objective may restrict that choice or cause traffic to use another path. Define destination groups, rate versions and selection rules so the reason for a routing decision can be understood after the call. Do not let an uncontrolled rate import become an undocumented policy change.
Record how the service applies capacity boundaries, destination restrictions and retries. The available controls and permissions are part of the agreed platform scope. The routing page explains policy design; fraud prevention covers access and traffic boundaries.
Operate the platform through its records
A switching operation needs useful CDRs, repeatable rate management and a clear billing handoff. Agree which identifiers join those systems and what happens when a record arrives late or requires investigation. The sample console demonstrates the types of views an operator may use; it is not a statement that every illustrated feature is enabled for every account.
Access should follow responsibility. Identify who can inspect traffic, who can change a route and who can authorize a commercial update. Include a change-and-reversal exercise in testing, then document the accepted configuration with the operational team.
Questions about this service
Where do customer extensions belong?
Extensions and subscriber features belong to the PBX or application layer. Class 4 switching addresses carrier traffic between ingress and egress relationships.
How should rate changes enter routing?
Use a controlled process that records the deck, effective date and affected policy. Confirm the supported import and approval workflow for the platform.
What should operations receive at handover?
The accepted trunk and route design, access roles, reporting definitions, change process and escalation contacts.
Follow one call into the commercial record
A carrier call enters through an ingress relationship, is evaluated against the configured policies and leaves through a selected egress relationship. The resulting record should be interpretable alongside the route decision and applicable rate version. Keep the operational and commercial view connected rather than treating them as unrelated systems.
For a disputed charge, establish the call identity, timing, duration definition and deck used before comparing totals. For a failed call, examine signaling and route selection before assuming that a rate rule is responsible. This conceptual example shows the questions a Class 4 environment needs to answer; exact functions and ownership are confirmed for the proposed platform.