Pushing the updated BYOC configuration to mypurecloud.com.au and the Sydney edge keeps rejecting the SIP trunk registration. Running platform v2024.3.1. The trunk handles Australian PSTN breakout, but the edge throws a SIP_403_FORBIDDEN right when the INVITE hits the ACMA compliance prompt block. Flow ID is arch-byoc-882-syd.
Number formatting looks correct in Admin. The E.164 pattern is locked to ^61\d{9}$. The BYOC carrier expects the leading zero stripped for domestic routing, which matches our porting docs. The trunk just sits there doing jack all while the registration timer ticks down. Latency sits around 180ms to Melbourne, which is fine, but the registration handshake drops every time the media path tries to negotiate the compliance recording.
Edge logs show EDGE_REGISTRATION_FAILED: NUMBER_FORMAT_MISMATCH at the exact moment the Play Prompt block triggers. We’ve tried toggling the “Preserve caller ID” setting on the trunk profile and adjusting the SIP timeout to 30s. Nothing sticks. Outbound dialing works on the US edge, but switching back to Sydney kills the session immediately. ACMA rules require the recording to play before any carrier handoff, so we don’t want to mess with the flow structure. It’s just dropping the ANI field during the compliance handshake.
The SIP trace captures this right before the drop:
SIP/2.0 403 Forbidden
Via: SIP/2.0/TCP 13.23.45.67:5060;branch=z9hG4bK-12345
From: <sip:61412345678@mypurecloud.com.au>;tag=98765
To: <sip:carrier-trunk@genesys-syd-edge.com>;tag=11223
Call-ID: abc-def-ghi@syd-edge
CSeq: 1 INVITE
Content-Length: 0
The carrier gateway is definitely rejecting the INVITE because the ANI field gets mangled during the compliance handshake. Sydney edge applies a different normalization rule for BYOC trunks when ACMA prompts are active