stuck on 503 Service Unavailable when pushing WebRTC softphone config via Genesys Cloud CLI.
using gc-cli 2.4.0 and terraform-provider-genesyscloud 1.20.0.
terraform apply succeeds but the softphone registration fails with 503 in the browser console. any ideas?
This is actually a known issue with the interaction between CLI deployments and real-time media routing. The 503 usually indicates that the softphone service endpoint is either not fully provisioned or blocked by a firewall rule introduced during the Terraform apply. Since the CLI succeeds, the configuration object exists, but the underlying WebRTC signaling path is likely broken.
Check if your BYOC trunk configuration inadvertently restricted outbound SIP traffic to the WebRTC media servers. Sometimes, aggressive outbound routing rules can block the softphone’s local registration. Also, verify that the genesyscloud_ivr or genesyscloud_routing_queue resources linked to the softphone are correctly associated.
Try forcing a re-registration by clearing the browser cache and ensuring the softphone app has microphone permissions. If the issue persists, inspect the SIP signaling logs for any 408 or 503 responses from the media server. This often points to a carrier-specific timeout or a misconfigured NAT traversal setting.