WebRTC ICE Failure on Secondary BYOC Trunk

Is it possible to configure specific STUN/TURN server overrides for WebRTC sessions when traffic routes through secondary BYOC trunks in Asia/Singapore? Agents using SDK v2.1.4 experience immediate drops with the following error during failover events:

ICE candidate gathering failed: host candidate connection timed out after 5000ms

Primary trunks remain stable, but secondary paths trigger this consistently. Does the platform support dynamic STUN selection per trunk group?