SIP 488 Response on AP-Southeast-1 BYOC Trunk Failover

SIP/2.0 488 Not Acceptable Here
Call-ID: [email protected]

Rerouting calls from our primary AP-Southeast-1 BYOC trunk to the secondary carrier triggers immediate 488 errors. The primary trunk handles inbound traffic without issue, but outbound failover logic seems to reject the INVITE before media negotiation.

Is there a specific header mismatch or region-specific codec requirement for secondary carrier registration in this cluster?

According to the docs, they say the 488 error often stems from SDP mismatches during failover. Check if your secondary trunk supports the same codecs as the primary.

In my JMeter tests, forcing PCMU and PCMA in the INVITE header bypassed this. The APAC edge cluster might be rejecting complex codec negotiations under load.