Looking for advice on resolving persistent SIP trunk registration failures for our primary provider. The Performance dashboard displays ‘Available’ status, yet call routing fails with a 403 Forbidden error. The logs indicate the issue stems from digest authentication mismatches.
‘Ensure the SIP URI matches the registered endpoint exactly.’
The endpoint configuration appears correct. Is there a known latency in status propagation for BYOC nodes in eu-west-1?