We’re getting intermittent SIP error 408 timeouts on inbound calls - request timed out waiting for a response. It started happening immediately after pushing a small change to the architect flow associated with the 1877-555-1212 number. The flow now pipes the caller ID through a data action to set a custom field - nothing fancy.
The SIP stack is on v2024.2.0. Console shows the INVITE getting a 408, but the PBX logs aren’t offering anything useful beyond that. It’s probably something changed in the SIP mediation layer after the architect rollout.
Is there a known issue with data actions in architect impacting SIP timeouts? A quick fix to bypass it would be nice.