Genesys Cloud BYOC
Delphi reaches Genesys Cloud CX on the egress (outbound / transfer) trunk, not by inventing a second inbound carrier-trunk product. The ticket text for VGWK-6 mentions ingress URIs; the shipped surface is egress routing — the request-URI Delphi puts on INVITE / REFER toward Genesys.
Configure trunks under Egress routing. Customer prefix (for example vodafoneczechrepublicdev) is per environment and per trunk.
Routing methods
| Method | Request-URI shape | When to use |
|---|---|---|
FQDN (genesys_fqdn) | sip:<number>@<prefix>.tobi.byoc.<region>.<domain> | DNS SRV to the customer-specific Genesys FQDN |
TGRP (genesys_tgrp) | sip:<number>;tgrp=<prefix>.tobi;trunk-context=byoc.<domain>@<proxy-host> | Recommended for TLS trunks so the host name matches the Genesys certificate SAN |
Examples (PRE-PROD Czech, prefix vodafoneczechrepublicdev):
FQDN: sip:+420123456@vodafoneczechrepublicdev.tobi.byoc.mypurecloud.de
TGRP: sip:+420123456;tgrp=vodafoneczechrepublicdev.tobi;trunk-context=byoc.mypurecloud.de@lb01.byoc.eu-central-1.mypurecloud.de
TLS
Genesys BYOC Cloud requires TLS 1.2 on port 5061, one-way (server) TLS, public CA on both ends. Set the egress trunk transport to TLS. Mutual TLS is not supported by Genesys BYOC. Both ends of the trunk must use the same protocol or the trunk fails.
What this page is not
- Inbound Delphi SIP trunks (carrier → TelPro) stay on SIP trunks. Ask for a follow-up story if VF also needs inbound Genesys-style ingress URIs.
- Header k/v pairs on BYE / REFER are Header manipulation plus bot
hangupSipHeaders/transferSipHeaders— see Managed callback actions.