SIP trunking / Five9
Bring your own carrier to Five9
Keep Five9 for campaigns, agents and reporting; put the minutes and numbers on an IPComms trunk peered directly with Five9’s data centres. $0.010 per minute outbound, $0.009 inbound, $0 per channel, no term contract, TLS and SRTP on every leg.
Request a BYOC quote or call +1 678-460-1475
Rates and cost math
| Item | Price |
|---|---|
| Outbound calling, US and Canada | $0.010 / min |
| Inbound to local numbers | $0.009 / min |
| Inbound to toll-free numbers | $0.0185 / min |
| Per channel / concurrent call | $0 |
| Local number | $1.50 / month |
| Toll-free number | $2.00 / month |
| E911, per number | $2.50 / month |
| Port a number in | $5.00 one-time |
| Term contract | None |
Full rate sheet: SIP trunking pricing
Worked at volume
| Usage | IPComms cost |
|---|---|
| 100,000 outbound minutes | $1,000 |
| 100,000 inbound minutes, local numbers | $900 |
| 100,000 inbound minutes, toll-free | $1,850 |
| 300 concurrent calls, any month | $0 |
| 500 local numbers | $750 / month |
No per-agent and no per-channel fee on the trunk, so the comparison is minutes and numbers only. Above roughly two million minutes a month, ask for a volume rate in the quote form.
What you keep, what moves
Stays in Five9
- Campaigns, skills, IVR scripts and routing in the Five9 VCC
- Agent desktop, dispositions, QM, WFM and reporting
- Call recording inside Five9
- Your Five9 domain, data centre pair and licences
Moves to IPComms
- Minutes: inbound and outbound rated per minute, no per-channel fee
- Numbers: local and toll-free DIDs, porting at $5 per number
- E911 with a dispatchable location per number
- The carrier relationship, invoice and trunk support
How it connects
A Five9 BYO SIP trunk is direct peering: Five9’s data centres send outbound calls to our trunk hosts and we send inbound calls for your numbers to Five9’s addresses, over TLS with SRTP. Our legs to the upstream carriers are SIP TLS with SRTP as well.
Trunk settings
What Five9’s BYO SIP trunk expects and what we provide.
- Trunk model
- Five9 BYO SIP Trunk: direct SIP peering between Five9’s data centres and IPComms. No SBC on your premises.
- Protocol / transport
- SIP over TLS on 5061 with SRTP (Five9’s default); UDP/TCP 5060 with RTP on request
- Certificates
- Five9 accepts public-CA certificates only. Ours chains to ISRG Root X1; no private CA to import.
- Authentication
- IP based: Five9 supplies its static signaling addresses, we allow-list them; we supply our trunk hosts, Five9 allow-lists those. SIP authentication ID and password can be added.
- Media
- SRTP (SDES). DTLS-SRTP is not used by Five9.
- Codec
- G.711 µ-law, 20 ms packetization (what Five9 expects); A-law available
- Number format
- +1E.164 or 1NPANXXXXXX for called and calling numbers, set per trunk to match your Five9 configuration
- Health
- SIP OPTIONS answered at both points of presence; Five9 uses OPTIONS to detect an unresponsive peer
Specifications
- Points of presence
- Two, geographically separate (US East, US West). Five9 peers each of its data centres with both.
- Upstream
- Multiple carriers, reached over SIP TLS with SRTP media; automatic failover on the outbound path
- Concurrent calls
- No per-channel fee and no set channel count. New accounts start with a fraud-protection limit that support raises on request; tell us your peak in the quote form.
- Caller ID
- Any number on your account, selectable per campaign in Five9; CNAM on inbound optional
- STIR/SHAKEN
- Every call is signed at A attestation, outbound and inbound
- E911
- Dispatchable location per number (Kari’s Law, RAY BAUM’S Act)
Setup steps
- Tell us your Five9 data centre pair and peak calls. Use the form below. We provision an IP-authenticated trunk, send you the trunk hosts for both points of presence and our signaling addresses, and confirm TLS/SRTP.
- Open the BYO SIP trunk request with Five9. Five9 provisions BYO SIP trunks through your Five9 account team, not from the VCC admin. Give them our trunk hosts and addresses; they return Five9’s static signaling addresses for your data centres.
- We allow-list Five9. Send us Five9’s addresses. We add them to the trunk, confirm OPTIONS is answered, and route your numbers toward Five9.
- Numbers and campaigns in Five9. Existing numbers port in parallel at $5 each. In the VCC, assign the DIDs to inbound campaigns and set the trunk on your outbound rules and campaign caller IDs.
- Test both directions. An inbound call to a DID and an outbound call from an agent, with Five9 watching trunk health and IPComms watching the same trunk from our side.
Questions operations teams ask
- Is BYOC worth it at our size?
- Minutes × our per-minute rate plus $1.50 per number, against the telephony line on your current invoice. There is no per-agent and no per-channel fee on our side. A 300-seat centre doing 1.5 million minutes a month pays $15,000 in outbound usage here; put your own figure beside it.
- Does this need an SBC on our side?
- No. A Five9 BYO SIP trunk peers Five9’s data centres directly with IPComms over the public internet with TLS and SRTP. If you already run an SBC and want it in the path, it connects to us like any SIP trunk.
- Is the audio encrypted?
- Yes. Five9 to IPComms is TLS with SRTP by default, and our upstream carrier legs are SIP TLS with SRTP as well.
- Do you sign calls under STIR/SHAKEN?
- Yes. Every call on the trunk is signed at A attestation, outbound and inbound. Reputation with the carrier analytics engines still depends on calling behaviour as much as on signing; IPComms does not carry automated dialer or campaign-blast traffic, which is stated in the acceptable use policy.
- Which Five9 data centres?
- Any pair Five9 assigns to your domain. Each peers with both of our points of presence, so a Five9 data centre failover and an IPComms failover are independent of each other.
- How long does provisioning take?
- Our side is one business day. The Five9 side is set by your account team; plan the numbers port to land the same week.