Stuck on a recurring HTTP 409 Conflict response when attempting to synchronize SIP registration states for our 15 BYOC trunks in AP-Southeast-1 via the Platform API. The specific endpoint /api/v2/telephony/providers/edges/{edgeId}/trunks returns a conflict error when the sipRegistrationStatus field is updated to registered while the underlying carrier SBC is still negotiating TLS certificates. The environment runs Architect v14.2.1, and the failover logic depends on real-time registration data to route outbound calls away from degraded carriers. The API response includes a conflictReason of SIP_STATE_MISMATCH, indicating the platform’s internal state does not match the SBC’s reported status. This discrepancy causes the analytics reporting module to miss critical trunk downtime events, resulting in inaccurate WEM export files. The issue persists across all 15 trunks, suggesting a systemic latency in the SIP registration polling mechanism rather than a carrier-specific quirk. The retry logic in our Python SDK (v2.1.4) exacerbates the problem by flooding the endpoint with requests, leading to temporary rate limiting.
Is there a documented workaround to bypass the strict state validation during the initial TLS handshake, or should the integration rely on webhook notifications instead of polling for registration status updates?