BYOC Trunk Failover Logic for AppFoundry SIP Integrations

Is it possible to configure automatic failover for BYOC trunks when the upstream AppFoundry SIP provider returns a 503 Service Unavailable?

Currently, the Genesys Cloud edge continues retrying the failed trunk registration instead of switching to the secondary route defined in the routing profile. Need to know if the platform API supports dynamic trunk state updates based on real-time SIP response codes.