-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Description
📋 Bug Description
When using the Evolution API with the official WhatsApp API, integrated into Chatwoot, sending an audio file from Chatwoot to a contact triggers an error in the container logs.
"details": "Unsupported Audio mime type audio/opus. Please use one of audio/ogg; codecs=opus, audio/mpeg, audio/amr, audio/mp4, audio/aac."
🔄 Steps to Reproduce
Integrate Chatwoot with the official WhatsApp API via Evolution API.
Send an audio message from Chatwoot to any contact.
Check the container logs.
Expected behavior:
The audio file should be delivered to the contact without errors.
Actual behavior:
The audio fails to send, and the logs show an unsupported MIME type error (audio/opus).
Environment:
Chatwoot version: 3.14.1
Evolution API version: 2.3.4
WhatsApp API: Official Meta API
Deployment: [Docker]
Additional context:
It looks like Chatwoot (or Evolution API) is sending audio in audio/opus format, which is not accepted by the WhatsApp API. The API only supports the following formats:
audio/ogg; codecs=opus
audio/mpeg
audio/amr
audio/mp4
audio/aac
A possible fix could be adding a conversion step before sending, or handling the audio format compatibility.
✅ Expected Behavior
Please use one of audio/ogg; codecs=opus, audio/mpeg, audio/amr, audio/mp4, audio/aac.
❌ Actual Behavior
audio/opus
🌍 Environment
- OS: [e.g. Ubuntu 20.04, Windows 10, macOS 12.0]
- Node.js version: [e.g. 18.17.0]
- Evolution API version: [e.g. 2.3.4]
- Database: [e.g. PostgreSQL 14, .0]
- Connection type: [e.g. WhatsApp Business API]
📋 Logs
"details": "Unsupported Audio mime type audio/opus. Please use one of audio/ogg; codecs=opus, audio/mpeg, audio/amr, audio/mp4, audio/aac."
📝 Additional Context
No response