Trunks that stretch when your business does
Create a trunk in the console, authorise your IPs, set a concurrency cap and start sending. Burst above your commitment when the day demands it.
Capacity as a setting, not a purchase order
Channel counts belong in a configuration screen. Waiting a week for someone to approve more capacity is a business process pretending to be a technical limit.
A NexDial trunk is created in the console in about a minute. Authorise static IPs or use digest registration, choose your codecs, set a concurrency cap and a spend cap, and point your switch at our edge. Everything after that is self-service.
Capacity is elastic. You contract for your steady state and burst above it when volume spikes — a campaign, a weather event, month-end. Burst headroom is provisioned on the platform in advance rather than allocated on request, so the spike is carried rather than queued behind an approval.
Trunks terminate on geographically diverse US edges with automatic failover, and every trunk carries its own telemetry so a problem on one customer or one switch is visible in isolation rather than averaged away.
- Self-service creation. A working trunk in minutes, configured entirely by you.
- Elastic concurrency. Committed channels plus burst headroom provisioned ahead of demand.
- Either authentication. Static IP authorisation or SIP digest registration, your choice.
- Encrypted if you want it. TLS signalling and SRTP media at no additional cost.
- Per-trunk telemetry. Quality and concurrency measured per trunk, not averaged across the network.
What you get
Technical summary
| Signalling | SIP over UDP, TCP or TLS 1.2+ |
| Media | RTP and SRTP, with re-invite and media release supported |
| Codecs | G.711 µ-law, G.729, G.722, Opus, with transcoding where required |
| Fax | T.38 relay with G.711 pass-through fallback |
| Authentication | Static IP authorisation or SIP digest registration |
| Concurrency | From 10 to 10,000+ channels, burstable above commitment |
| Failover | Automatic between US edges, typically under 60 seconds |
| Emergency calling | E911 with Registered Location per number — see Terms, Section 9 |
What customers ask
Almost certainly. We interoperate with the mainstream platforms — Asterisk, FreeSWITCH, Kamailio, OpenSIPS, 3CX, FreePBX, Cisco, Avaya, Mitel and the major UCaaS and CCaaS stacks. Codec and DTMF negotiation is settled during your test window rather than discovered in production.
Calls above the cap receive a congestion response rather than being silently billed at a premium. The cap is yours to set and raise in the console, and we alert you as you approach it. Sustained operation well above your commitment starts a re-rating conversation, never a surprise charge.
No. Geographic redundancy, automatic failover, TLS and SRTP are how the platform is built rather than upsells. You pay for channels and usage.
Yes, and you should. Create a trunk per downstream customer or per site and each gets its own credentials, concurrency cap, CDRs and telemetry. That also makes traceback response straightforward, which matters because you are responsible for identifying the true originator of any call.
Get started through the contact form, create a trunk, load a small balance and send real traffic alongside your existing carrier. Compare the telemetry over a few days. There is no commitment to make that comparison, and it is a far better basis for a decision than a rate sheet.
Stand up a trunk in the next ten minutes
Get started through the contact form, then build a trunk, authorise an IP and send a test call. If anything about the interop looks unusual, our engineers will get on it with you.