SIP trunking / Webex Contact Center
Bring your own PSTN to Webex Contact Center
Webex Contact Center takes third-party carriers through a Local Gateway on your premises: a Cisco CUBE or approved SBC that Webex Calling trusts. IPComms delivers the minutes and numbers to that gateway over TLS and SRTP. $0.010 per minute outbound, $0.009 inbound, $0 per channel, no term contract.
Request a test trunk to your gateway 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 form.
What you keep, what moves
Stays in Webex
- Flows, queues, entry points and routing in Webex Contact Center
- Agent desktop, recording, analytics and WFO
- Webex Calling users and numbers in Control Hub
- Your Local Gateway or vPOP CUBE and its 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
Cisco’s “Webex Calling Local Gateway” option: inbound calls arrive from the carrier at your gateway and are forwarded into Webex Calling for Webex Contact Center; outbound calls leave the same way. Webex’s Voice POP Bridge (vPOP) model uses the same customer CUBE. Our leg to the gateway runs over TLS with SRTP, and so do our legs to the upstream carriers.
Trunk settings
Our side of your gateway. The Webex side follows Cisco’s Local Gateway configuration (registration- or certificate-based trunk, G.711, RFC 2833 DTMF, +E.164, 20 ms packetization).
- Trunk toward your gateway
- IP-authenticated SIP trunk to the gateway’s 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; on IOS-XE set the trustpool policy to revocation-check none (see the Cisco CUBE guide)
- Media
- SRTP (SDES) with TLS; RTP otherwise
- Codecs
- G.711 µ-law, G.711 A-law at 20 ms
- DTMF
- RFC 2833 (telephone-event)
- Number format
- +1E.164 on the trunk to match Webex Calling; 1NPANXXXXXX or 10-digit available 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 gateway and peak calls. Use the form below. We provision an IP-authenticated trunk to the gateway’s public address and send the trunk hosts for both points of presence.
- Configure the carrier dial-peers on the CUBE. Session target the IPComms trunk hosts on 5061 TLS, SRTP, G.711, +E.164. Our Cisco CUBE guide has the dial-peer and trustpoint settings.
- Connect the gateway to Webex Calling. In Control Hub, create the Local Gateway trunk (registration- or certificate-based) and add the route group; on the CUBE, the Webex dial-peers per Cisco’s Local Gateway article.
- Numbers. Port existing numbers to IPComms at $5 each or provision new ones in the portal; add them in Control Hub as Local Gateway numbers and assign them to Contact Center entry points.
- Test both directions. Inbound to an entry point and outbound from an agent, with the CUBE 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 a CUBE or SBC?
- Yes. Webex Contact Center takes a third-party carrier only through Webex Calling’s Local Gateway (or a vPOP CUBE): the trunk lands on your gateway, not in Cisco’s cloud. Cisco’s own PSTN and Cloud Connected PSTN are the no-gateway options, and both are Cisco-side carriers.
- Which gateways?
- Cisco CUBE on IOS-XE is the reference; Cisco also approves third-party SBCs as Local Gateway. Our CUBE guide covers the carrier side; Cisco’s Local Gateway articles cover the Webex side.
- Is the audio encrypted?
- Our leg to the gateway is TLS with SRTP; the gateway to Webex Calling leg is Cisco’s TLS/SRTP trunk; 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.