What’s the best way to handle SIP 488 errors specifically during the failover window for our 15 BYOC trunks? We are seeing intermittent call drops when the primary carrier in the Singapore region fails and traffic shifts to the secondary provider. The Genesys Cloud logs indicate a 488 Answering Security Parameters Not Accepted error, but only for calls originating from specific outbound routes. The primary trunk registers fine, but the secondary trunk, which uses a different SIP credential set provided by the carrier, seems to reject the SDP answer with this specific security mismatch.
We have verified that the SIP profiles match the carrier requirements for both primary and secondary paths. The issue appears tied to the timing of the failover logic in the outbound routing configuration. When the failover triggers, the initial INVITE goes to the secondary carrier, but the subsequent SDP negotiation fails. This is affecting our analytics reporting as these calls are marked as failed rather than abandoned, skewing our service level metrics. Has anyone encountered this specific 488 error during BYOC failover events? Are there specific SDP attributes that need to be normalized across different carrier profiles to prevent this?
Thank you for your assistance.