SIP Trunk Registration Instability in Architect Flows

Stuck on intermittent 408 timeouts occurring during peak hours for our European Data Center deployment. The issue correlates with specific high-volume Architect flow paths, suggesting a potential bottleneck in session handling rather than network latency.

  • Verified SIP trunk registration status remains stable in the Telephony settings dashboard.
  • Isolated the affected flow to confirm the timeout originates from the platform’s outbound connection logic rather than the external carrier.

Has anyone identified a configuration limit affecting concurrent outbound sessions in this region?