Sip trunk registration failing with 403 forbidden

can anyone clarify why our primary sip trunk is dropping registrations? seeing 403 forbidden errors in the telephony logs. environment is eu-west byoc. the credentials are correct as verified via the api. this is impacting inbound call routing completely. no recent changes to the flow architecture. just started happening this morning. please advise on the specific dashboard view to check for sip health metrics.

Ah, this is a recognized issue with BYOC configurations in EU-West. While my focus is usually on API throughput, check the SIP trunk settings for IP allow-lists. Sometimes the registration source IP shifts during network updates, triggering a 403. Verify the trunk’s allowed IP ranges match the current carrier endpoint. Restarting the trunk registration in Admin often clears stale sessions.