SIP trunking / Zoom
Bring your own carrier to Zoom Phone and Zoom Contact Center
Zoom’s BYOC Premises Peering connects a Zoom-certified SBC on your side to Zoom Phone; Zoom Contact Center uses the same numbers and trunk. IPComms delivers the minutes and numbers to that SBC over TLS and SRTP. $0.010 per minute outbound, $0.009 inbound, $0 per channel, no term contract.
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 form.
What you keep, what moves
Stays in Zoom
- Zoom Phone call queues, auto receptionists and number assignment
- Zoom Contact Center flows, queues and agent desktop
- Zoom recording, analytics and QM
- Your Zoom account, Zoom Phone Pro licences and certified SBC
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
Under BYOC-P, Zoom peers with your session border controller over the public internet (bi-directional connectivity is required), and the SBC holds the carrier trunk. Our leg to the SBC runs over TLS with SRTP, and so do our legs to the upstream carriers. IPComms is not a Zoom Provider Exchange or Cloud Peering carrier, so the SBC model is the one we support.
Trunk settings
Our side of your SBC. The Zoom side follows Zoom’s premises-peering configuration for your SBC vendor (Ribbon, AudioCodes and Oracle publish Zoom notes).
- Trunk toward your SBC
- IP-authenticated SIP trunk to your SBC public address; digest registration also supported
- Protocol / transport
- SIP over TLS on 5061 with SRTP (recommended); UDP/TCP 5060 with RTP on request
- Certificates
- Our certificate chains to ISRG Root X1; trust the root, not an intermediate
- Media
- SRTP (SDES) with TLS; RTP otherwise
- Codecs
- G.711 µ-law, G.711 A-law
- Number format
- +1E.164, 1NPANXXXXXX or 10-digit for called and calling numbers, set per trunk
- Health
- SIP OPTIONS answered at both points of presence
Specifications
- Points of presence
- Two, geographically separate (US East, US West). Your SBC can be allow-listed at both; inbound calls are delivered to 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 form.
- Caller ID
- Any number on your account, per trunk or per call; 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 SBC and peak calls. Use the form below. We provision an IP-authenticated trunk to the SBC’s public address and send the trunk hosts for both points of presence.
- Configure the carrier leg on the SBC. Proxy or signaling group toward the IPComms trunk hosts on 5061 TLS, SRTP, G.711, +E.164. AudioCodes and Ribbon notes are on our Teams Direct Routing page.
- Set up premises peering with Zoom. With Zoom Phone Pro on the account, request BYOC-P from Zoom and complete the SBC-side peering per your vendor’s Zoom configuration note. Zoom requires a certified SBC.
- Numbers. Port existing numbers to IPComms at $5 each or provision new ones in the portal; add them in Zoom as BYOC numbers and assign to users, queues or Contact Center.
- Test both directions. Inbound to a Zoom number and outbound from a Zoom Phone user and a Contact Center agent, with the SBC and IPComms both watching the trunk.
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.
- Do we need an SBC?
- Yes. Premises peering requires a Zoom-certified SBC (Ribbon, AudioCodes, Oracle and others). Zoom’s no-SBC options are Zoom Phone native calling plans and Provider Exchange carriers; IPComms is not in Provider Exchange.
- Does Zoom Contact Center work the same way?
- Yes. Zoom Contact Center uses Zoom Phone numbers and connectivity, so a BYOC-P trunk serves both.
- Is the audio encrypted?
- Our leg to the SBC is TLS with SRTP; the SBC to Zoom leg is Zoom’s TLS/SRTP peering; our legs to the upstream carriers are SIP TLS with SRTP.
- 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.