Application
- Your application
- Agents, workflows, models, ASR/TTS, and customer experience
- HD Carrier operates
- Third-party endpoint connection to the telecom network
The HD Direct platform
Connect your existing SIP infrastructure to major US carriers through a direct IP path designed to reduce intermediate hops, preserve call data, and carry AMR-WB audio where supported.
Not a guess. A known path.
Traditional least-cost routing can pass a call through multiple downstream providers. On eligible HD Direct routes, CarrierX connects on-net to the destination carrier without secondary carrier hops.
Technical clarity
HD Carrier strengthens the telecom path without asking you to replace the application layer that differentiates your product.
Configuration, route availability, capacity, and commercial terms vary by account and traffic profile. Confirm the production architecture with the HD Carrier team and current CarrierX documentation. Read the current CarrierX HD Direct documentation.
Platform capabilities
HD Carrier is the direct telecom layer beneath the application. Keep control of your product while CarrierX HD Direct handles the route into the mobile network.
Inbound and outbound calling over direct interconnections currently including AT&T, T-Mobile, and Verizon.
HD Direct uses G.722.2 AMR-WB, with automatic codec negotiation and transparent transcoding when an endpoint cannot accept HD audio.
End-to-end IP connectivity preserves attestation information through the path so downstream systems retain useful provenance data.
Attach DIDs to trunk groups and use the same third-party endpoint architecture for calls entering or leaving your application.
Prioritize endpoints for failover or distribute traffic with weighted round-robin routing across your application infrastructure.
Provision phone numbers, endpoints, trunks, and trunk groups through the CarrierX portal or Core API.
From sandbox to production
Telecom resources are issued after company and use-case review. The process protects customers, carriers, and the network while giving qualified teams a useful technical evaluation.
Describe your company, intended traffic, target carriers, current SIP environment, and the result the evaluation needs to prove.
Point a CarrierX third-party endpoint to the public IP address or domain used by your existing SIP application.
Create a trunk group, assign the endpoint and DID, and choose failover or round-robin behavior for the environment.
Validate inbound and outbound calls, codec negotiation, quality, latency contribution, and call data before moving production traffic.
Bring your voice stack
Use a qualified sandbox evaluation to inspect route behavior, codec integrity, call data, and conversational quality with your own infrastructure.