Is BYOC worth it at our size?

Do the arithmetic with your own numbers: minutes × our per-minute rate plus $1.50 per number, against the telephony line on your current invoice. There is no per-channel or per-agent fee on our side, so the comparison is only minutes and numbers. A 300-seat centre doing 1.5 million minutes a month pays $15,000 in outbound usage here; check that figure against what you pay today.

BYOC Cloud terminates the trunk in Genesys’s region and needs no equipment; this page describes it. BYOC Premises terminates on your own Genesys Cloud Edge appliances; we connect to those like any SIP trunk (see below).

Do you support the FQDN, TGRP and DNIS routing methods?

Yes. FQDN is the default: we send inbound calls to your org’s BYOC FQDN. TGRP or DNIS replacement can be set per trunk if your Genesys configuration needs them.

Which Genesys regions?

Any region whose BYOC addresses Genesys publishes. US East (use1, use2) pairs naturally with our East point of presence and US West (usw2) with West; Canada Central (cac1) works with either. Other regions are supported; latency to the trunk is the only difference.

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 traffic, which is stated in the acceptable use policy.

Is the audio encrypted?

With TLS on the trunk, media is SRTP between Genesys and IPComms, and our upstream carrier legs are SIP TLS with SRTP as well.

SIP trunking / Genesys Cloud CX

Bring your own carrier to Genesys Cloud CX

Keep Genesys for routing, agents and analytics; put the minutes and numbers on an IPComms trunk. $0.010 per minute outbound, $0.009 inbound, $0 per channel, no term contract. Works with BYOC Cloud (no equipment) and BYOC Premises (your Edge appliances), over TLS and SRTP.

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.020 / min
Per channel / concurrent call	$0
Local number, US	$1.50 / month, $1.00 setup
Toll-free number	$2.00 / month, $1.00 setup
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

Our side of the comparison. Put your Genesys telephony invoice line beside it.
Usage	IPComms cost
100,000 outbound minutes	$1,000
100,000 inbound minutes, local numbers	$900
100,000 inbound minutes, toll-free	$2,000
200 concurrent calls, any month	$0
250 local numbers	$375 / month

There is 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 Genesys Cloud

Architect flows, IVR, queues and routing
Agent desktop, scripts, WFM, quality management
Call recording and analytics inside Genesys Cloud
Your Genesys org, region 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 support for the trunk

How it connects

Under BYOC Cloud, Genesys terminates the trunk in your org’s region and sends outbound calls to our trunk host; we send inbound calls for your numbers to your org’s BYOC FQDN. Both legs to Genesys run over TLS with SRTP, and so do our legs to the upstream carriers.

Two points of presence; pair the one nearest your Genesys region as primary.

Trunk settings in Genesys

The fields as they appear in Admin › Telephony › Trunks › External Trunk, with the value to use.

Trunk type: BYOC Cloud › External trunk › generic BYOC carrier
Protocol / transport: SIP over TLS on 5061 (or UDP/TCP 5060)
SIP servers or proxies: Your IPComms trunk host(s): one per point of presence, port 5061
Inbound SIP Termination Identifier: Your choice of identifier. Genesys derives your org FQDN from it; we route your numbers to that FQDN.
Outbound SIP Termination FQDN: Your IPComms trunk host
Authentication: IP: we allow-list the published Genesys signaling addresses for your region. Digest is also supported.
Media: SRTP (SDES) with TLS; RTP with UDP/TCP. Genesys media addresses arrive in SDP and are accepted as-is.
Codecs: G.711 µ-law, G.711 A-law, G.729
Number format: +1E.164 on the trunk (Genesys default); 1NPANXXXXXX or 10-digit available per trunk

Specifications

Points of presence: Two, geographically separate (US East, US West). Map them to your Genesys region: use1 / use2 to East, usw2 to West, cac1 to either.
Upstream: Multiple carriers, reached over SIP TLS with SRTP media; automatic failover on the outbound path
Inbound delivery: Every number on the trunk is sent to your BYOC FQDN with the Request-URI format Genesys expects (FQDN method; TGRP and DNIS also supported)
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, per trunk or per call from Genesys; 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)
OPTIONS: Answered at both points of presence; Genesys trunk health shows the trunk as up

Setup steps

Tell us your Genesys region and peak calls. Use the form below. We provision an IP-authenticated trunk, allow-list the Genesys BYOC signaling addresses for your region, and send you the SIP server hostnames for both points of presence.
Create the external trunk in Genesys Cloud. Admin › Telephony › Trunks › Create New › External Trunk, type BYOC Carrier (generic). Set transport TLS 5061 and the SIP servers from step 1. Choose an Inbound SIP Termination Identifier and enter the Outbound SIP Termination FQDN.
Send us the identifier. Reply with your Inbound SIP Termination Identifier (or the full FQDN Genesys shows). We point your numbers at it. Existing numbers port in parallel at $5 each.
Assign numbers and the trunk to a site. Telephony › DID Numbers: add the numbers as DIDs on the trunk. Telephony › Sites: set the trunk on the site’s outbound routes and assign DIDs to users or flows.
Test both directions. Place an inbound call to a DID and an outbound call from an agent. Trunk health in Genesys shows OPTIONS state; we watch the same trunk from our side during the test.

Typical time from quote to a working trunk with test numbers: one business day. Porting your existing numbers runs in parallel.

BYOC Premises

If your Genesys Cloud Edge appliances sit in your data centre, the trunk lands on them instead of in Genesys’s region: an IP-authenticated SIP trunk to each Edge’s public address, TLS 5061 or UDP/TCP 5060, G.711, numbers delivered in +1E.164 or the format you set per trunk. Everything else on this page, including the rates, is the same.

Questions operations teams ask

Is BYOC worth it at our size?: Do the arithmetic with your own numbers: minutes × our per-minute rate plus $1.50 per number, against the telephony line on your current invoice. There is no per-channel or per-agent fee on our side, so the comparison is only minutes and numbers. A 300-seat centre doing 1.5 million minutes a month pays $15,000 in outbound usage here; check that figure against what you pay today.
Cloud or Premises?: BYOC Cloud terminates the trunk in Genesys’s region and needs no equipment; this page describes it. BYOC Premises terminates on your own Genesys Cloud Edge appliances; we connect to those like any SIP trunk (see below).
Do you support the FQDN, TGRP and DNIS routing methods?: Yes. FQDN is the default: we send inbound calls to your org’s BYOC FQDN. TGRP or DNIS replacement can be set per trunk if your Genesys configuration needs them.
Which Genesys regions?: Any region whose BYOC addresses Genesys publishes. US East (use1, use2) pairs naturally with our East point of presence and US West (usw2) with West; Canada Central (cac1) works with either. Other regions are supported; latency to the trunk is the only difference.
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 traffic, which is stated in the acceptable use policy.
Is the audio encrypted?: With TLS on the trunk, media is SRTP between Genesys and IPComms, and our upstream carrier legs are SIP TLS with SRTP as well.