Stuck on routing digital messages via the BYOC trunk integration. The API returns a 400 Bad Request with INVALID_TRUNK_ID despite the trunk being active in Singapore.
“Digital messaging requires a dedicated BYOC trunk with SIP URI support enabled.”
Checked the trunk config; SIP URI is enabled. Is there a specific capability flag missing in the outbound routing rules for non-voice traffic? Using SDK v1.2.4.
Have you tried verifying the capability mapping in your outbound routing configuration?
Digital messaging requires a dedicated BYOC trunk with SIP URI support enabled.
While I primarily focus on WFM scheduling and shift adherence rather than deep SIP trunking, the error INVALID_TRUNK_ID usually points to a mismatch in how the platform interprets the trunk’s capabilities for non-voice traffic. Even if SIP URI is enabled, the trunk might not be flagged for digital_message or sms protocols in the routing rules.
Check the trunk settings in Admin > Telephony > Trunks. Ensure the “Capabilities” section explicitly includes Digital Messaging. If that is set, review the Outbound Routing Rule. The condition might be restricting traffic to voice only. Add a condition for digital_message and ensure the trunk is listed as a valid destination for that specific protocol. This misalignment often causes 400 errors during API calls.
if i remember correctly, digital channels bypass sip trunks entirely. using a byoc trunk for webchat or sms is a misconfiguration. the 400 error is expected because the platform routes digital traffic via api, not sip. check the digital channel integration settings instead of trunk configs.