is it possible to configure the webrtc softphone to automatically switch to a secondary sip trunk if the primary byoc connection drops? currently, agents using the web client experience a 503 service unavailable error when our ap-southeast-1 carrier has latency spikes. the standard failover logic seems to ignore the softphone’s active session state. any insights on architecting a reliable fallback for these specific trunk configurations?