- Region: APAC (Singapore)
- Trunks: 15 BYOC (SIP)
- Digital Channel: Web Chat & SMS
- Architect Version: 2023.11
- SDK: Genesys Cloud SDK v2.48
Running into a weird bug with the message routing logic when attempting to bind digital channels to our existing BYOC infrastructure. The goal is to leverage the SIP proxy capabilities for SMS delivery via one of our secondary carriers, but the system rejects the configuration.
When updating the digital engagement settings via the API, specifically /api/v2/conversations/messaging/config, the response returns a 400 Bad Request. The error payload indicates:
`“code”: “invalid_trunk_binding”, “message”: “Selected trunk does not support digital signaling protocols. BYOC trunks are restricted to voice-only routing.”
This contradicts the documentation which suggests that SIP-enabled trunks can handle signaling for digital carriers if the digital_enabled flag is set in the trunk configuration. We have verified the SIP credentials and registration status; the trunks are active and handling voice traffic without issues. However, the digital channel engine seems to ignore the custom carrier settings during failover.
Has anyone successfully mapped a BYOC trunk to a digital messaging provider in this region? The failover logic appears to drop the digital session immediately when the primary channel fails, rather than attempting to route via the SIP proxy on the secondary trunk. The logs show a timeout on the handshake phase before the SIP INVITE is even generated for the digital payload.