I know this is in the documentation as only being available to External SIP/generic trunks. I'm looking to find out if that's a technical limitation (like it requires a customer-managed edge device), or just a design gap between legacy SIP trunk configurations and cloud-only ones.
At present, there doesn't appear to be any way to proactively monitor availability of BYOC Carrier trunks, so it's not really possible to proactively alert on issues with them as they arise.
This came up in our production environment by way of "dialing delay", where we have a BYOC Carrier trunk with several proxy addresses, as well as the PureCloud Voice trunk, in an outbound route on our default Site. The BYOC carrier trunk wasn't responding, so Genesys was retrying invites 4 times per proxy address, before it finally gave up and used the PureCloud Voice trunk. If these supported Options Ping/Availability, the BYOC Carrier trunk would've ostensibly been marked as down, and skipped for the outbound routing attempts.
From what I can tell, the BYOC Carrier is what's supported when using Genesys-managed Edges, and the External SIP is likely only supported for on-prem/hybrid deployments. At least, I can't get an External SIP trunk config to properly associate with the Genesys edges.
#Telephony------------------------------
Paul McGurn
Manager, Telecom & DevOps
GoTo
------------------------------