Bug Description
The call.received webhook event is not being triggered when an incoming call arrives on WhatsApp, using WEBJS engine with WAHA Plus 2026.3.4.
Environment
- WAHA Version: 2026.3.4
- Engine: WEBJS
- Tier: PLUS
- Image: devlikeapro/waha-plus:chrome
- Platform: linux/x64
- Browser: /usr/bin/google-chrome-stable
Webhook Configuration
Events configured: message, message.any, message.ack, call.received, session.status
Expected Behavior
When someone calls the WhatsApp number, WAHA should emit a call.received webhook event to my endpoint.
Actual Behavior
No webhook event is fired when a call arrives. Docker logs show no call-related activity. The call rings normally on the device but WAHA does not detect it.
Steps to Reproduce
- Configure webhook with
call.received event
- Call the WhatsApp number from another phone
- No event appears in Docker logs or webhook endpoint
Additional Notes
The Apps/Calls API also returns 500 error when trying to configure automatic call rejection via REST API.
Calling from a completely different phone number (not the session number).
Zero activity in Docker logs during the entire call duration.

Bug Description
The
call.receivedwebhook event is not being triggered when an incoming call arrives on WhatsApp, using WEBJS engine with WAHA Plus 2026.3.4.Environment
Webhook Configuration
Events configured: message, message.any, message.ack, call.received, session.status
Expected Behavior
When someone calls the WhatsApp number, WAHA should emit a
call.receivedwebhook event to my endpoint.Actual Behavior
No webhook event is fired when a call arrives. Docker logs show no call-related activity. The call rings normally on the device but WAHA does not detect it.
Steps to Reproduce
call.receivedeventAdditional Notes
The Apps/Calls API also returns 500 error when trying to configure automatic call rejection via REST API.
Calling from a completely different phone number (not the session number).
Zero activity in Docker logs during the entire call duration.