Predictive Routing campaign stalls on +61 IVR timeout threshold

Pushing a new predictive campaign through mypurecloud.com.au using the /api/v2/predictive-routing/campaigns endpoint and the dialer won’t engage. The Architect flow throws a 504 Gateway Timeout right after the Wait For Response block, even though latency to our Melbourne SIP trunks sits at a steady 45ms.

ACMA rules force a 12-second abandon window while the campaign config caps it at 8.0. Debug logs just spit out predictive_dialer_engagement_failure with a null callDisposition field.