Elastic SIP trunking that scales with your call volume
Replace rigid PRI circuits with software-defined trunks that burst on demand, fail over between regions automatically and bill only for what you actually use. Provisioned in minutes through the portal or the API.
# Live trunk telemetry TRUNK CHANNELS ACTIVE MOS JITTER STATE hq-primary 250 184 4.44 4 ms healthy hq-failover 250 0 4.41 3 ms standby emea-branch 120 67 4.38 6 ms healthy apac-branch 80 41 4.35 7 ms healthy # Burst event, 14:22:07 UTC hq-primary requested +90 channels → granted in 1.2s no re-registration required, no dropped sessions
What ships with every Telecorenetwork trunk
Not an upsell list — these are defaults on every trunk we provision, from a 10-channel branch office to a 5,000-channel contact centre.
Instant elastic bursting
Request additional concurrent channels through the portal or API and have them live in under two seconds. Seasonal peaks and marketing campaigns stop being capacity-planning exercises.
Automatic dual-region failover
Each trunk is anchored in a primary PoP with a hot standby in a second region. If the primary degrades, sessions re-anchor in under 400 milliseconds — usually before an agent notices.
Encrypted by default
TLS 1.3 signalling and SRTP media on every trunk with no premium tier. IP authentication, digest registration or mutual TLS, whichever fits your session border controller.
Intelligent least-cost routing
Live route scoring on MOS, ASR and ACD. Underperforming carriers are demoted automatically rather than after a quarterly review.
Codec flexibility with transcoding
OPUS, G.711 A-law and µ-law, G.729 and G.722 with edge transcoding, so you can run HD internally and hand off narrowband to the PSTN without extra hardware.
Real-time analytics and CDR streaming
Per-call MOS, jitter, packet loss and post-dial delay in the portal, with CDRs streamed to your data warehouse over webhook or S3 within 30 seconds of hangup.
The commercial case for retiring your PRIs
A 23-channel PRI costs the same whether you use one channel or all twenty-three, and adding the twenty-fourth means ordering an entire second circuit. SIP trunking removes that step function from your capacity planning and, typically, 30–50% from your monthly voice spend.
- Pay for concurrent channels actually in use rather than pre-provisioned circuit blocks
- Consolidate every site onto one trunk group with a single, auditable invoice
- Eliminate site-level ISDN maintenance contracts and legacy gateway hardware refreshes
- Keep business continuity through outages by re-routing to mobile or a secondary site instantly
- Add a new office in a new country in days rather than the eight-week circuit lead time
30–50% lower spend
Typical saving when replacing PRI or legacy hosted trunks, before international rate improvements.
Same-day activation
Most trunks are live within a business day; complex multi-site builds within two weeks.
Fraud caps included
Per-trunk spend ceilings and destination allow-lists configured at provisioning.
Named voice engineer
Enterprise accounts get a named engineer through migration, not a rotating queue.
From first call to full cutover
A structured migration that keeps your existing service running until every site is verified.
Architecture review
We map your current sites, PBXs, codecs, number ranges and peak concurrency, then produce a written design with capacity and failover recommendations.
Sandbox trunk
You receive a free test trunk with 500 minutes. Register your PBX, run interop tests and validate call quality against your own handsets.
Parallel run
Production trunks are provisioned alongside your legacy circuits. Outbound moves first, then inbound number ranges port in scheduled batches.
Cutover and optimise
Legacy circuits are decommissioned once every range is verified. We then tune routing, codecs and capacity based on 30 days of real traffic.
Interoperability and protocol support
Tested against the platforms our enterprise customers actually run. If yours is not listed, our lab will validate it during the trial.
| Capability | Supported | Detail |
|---|---|---|
| Signalling | SIP over UDP / TCP / TLS 1.3 | RFC 3261 compliant, IPv4 and IPv6 dual stack |
| Media | RTP / SRTP AES-256 | Edge transcoding, comfort noise, DTMF via RFC 2833 or SIP INFO |
| Codecs | OPUS, G.711, G.722, G.729 | HD wideband internally, narrowband handoff to PSTN |
| Authentication | IP ACL, digest, mutual TLS | Multiple credentials per trunk with independent channel caps |
| Fax | T.38 and G.711 pass-through | Redundancy level configurable per trunk |
| Emergency calling | E911, 112, 999 | Dispatchable location, address validation at provisioning |
| PBX interop | 60+ platforms validated | Asterisk, FreeSWITCH, 3CX, Avaya, Cisco CUCM, Mitel, Genesys |
| Number portability | Full LNP support | Parallel-run porting with scheduled batch cutover windows |
Interop certificates and SIP interoperability guides are available in the customer portal.
Trunk pricing without the fine print
Choose per-channel for predictable spend or per-minute for variable traffic. Switch between models at any renewal with no penalty.
- Up to 50 concurrent channels
- Unlimited inbound minutes
- 1 DID included per 5 channels
- TLS 1.3 + SRTP encryption
- Portal analytics
- Business-hours support
- Up to 500 concurrent channels
- Elastic bursting to 150% of committed
- Dual-region automatic failover
- 5 DIDs included per 10 channels
- CDR streaming + webhooks
- 24/7 NOC support
- Named migration engineer
- Unlimited concurrent channels
- Dedicated SBC capacity
- Private interconnect or cross-connect
- Custom SLA with financial remedies
- Data residency pinning
- Quarterly architecture reviews
- Named account and NOC contact
All prices are illustrative USD list rates excluding local taxes and regulatory fees. Committed-volume and multi-year agreements are quoted individually — request a tailored quote.
SIP trunking questions, answered plainly
Still unsure? Our voice architects answer technical questions directly — no gatekeeping through sales.
The usual rule of thumb is one channel per three to four concurrent users for a general office, and one per active agent plus 20% headroom for a contact centre. But rules of thumb are a poor substitute for data.
If you can export call records from your current system, we will analyse your busiest hour across the last 90 days and size the trunk against measured peak concurrency rather than a guess. With elastic bursting enabled, under-sizing is also far less punishing than it was on PRI.
Yes. Number portability is supported across every market we operate in, and porting is included at no charge for standard geographic and toll-free ranges.
We run ports as parallel migrations: your new trunk is live and tested before any range moves, and ranges are ported in scheduled batches so a single problematic number cannot delay the whole project.
Almost certainly. We maintain validated interoperability profiles for more than 60 platforms including Asterisk, FreeSWITCH, 3CX, Avaya Aura, Cisco CUCM, Mitel MiVoice and Genesys.
If your platform is not on the list, our interop lab will test it during your free trial and publish a configuration guide specific to your version.
Budget roughly 85–100 kbps per concurrent call with G.711 including IP overhead, or around 40 kbps with OPUS at typical enterprise settings. A 50-channel trunk therefore needs about 5 Mbps of reliably prioritised bandwidth in each direction.
What matters more than raw capacity is jitter and queueing. We recommend DSCP EF marking for voice and a dedicated queue on the WAN edge; our onboarding engineers will review your QoS configuration as part of the architecture review.
Inbound calls automatically overflow to a pre-configured destination — a mobile number, a secondary site, a voicemail-to-email box or another trunk — triggered by loss of SIP OPTIONS response rather than a manual switch.
Enterprises with strict continuity requirements typically pair a primary broadband circuit with an LTE or secondary fibre path and let the trunk re-anchor to whichever is healthy.
Two models. Per-channel billing charges a flat monthly rate for concurrent capacity with unlimited inbound and bundled outbound minutes to your primary market. Per-minute billing charges only for connected traffic at published per-destination rates.
High-volume international traffic usually favours per-minute; predictable office telephony usually favours per-channel. We will model both against your actual call records before you sign anything.
Pairs well with
Get a trunk design built around your actual traffic
Send us 90 days of call records — or just tell us your site count and peak concurrency — and we will return a written architecture, a capacity recommendation and a transparent quote.
30-day trial · 500 free minutes · No credit card required