Hi, I need some help with a problem I have with Node-RED and Wazo.
I have connected Node-RED to my Wazo instance and the integration shows as active. I created the application in the Wazo UI and configured everything. However, when I make a call, nothing happens in Node-RED—the flow apparently does not execute. The call does not answer automatically, and after 3 seconds it does not hang up automatically either.
I’ve verified that the application is active, Node-RED is connected to the Wazo Event Service, and the credentials are correct. Still, the application_call_entered event does not appear, and no events are received. I’ve also checked with a Debug node in Node-RED, but it doesn’t receive any data.
Has anyone experienced this issue or knows why call events might not reach Node-RED, even when the connection is active?
Also y try making an application in Wazo-ui, but doesn´t appear like an option.
Thanks for your suggestions — I’ve read through all the advice in this thread and followed the steps, but I’m still unable to make Node-RED receive events from Wazo.
I think that the problem is the configuration in wazo, because the node red connects correctly to the websocket, but i cant choose the application in node red, so i´m very confuse where is the problem.
Configuration:
You should check the logs to see if the call flow is as you expect and the events are generated.
You can look at /var/log/wazo-calld.log on your wazo server while testing(you can set debug: true in /etc/wazo-calld/config.yml beforehand to ensure you get verbose logging).
if you can see mentions of application_call_entered event being published, next step is checking the websocket connection side of things. You can look at /var/log/wazo-websocketd.log to see if the wazo-websocketd service is receiving that event and relaying it to subscribed users.
You need to have the proper permissions when you subscribe to the websocket in order to see those events. I assume you would use an admin token to ensure you get all permissions in this case. In a production setting you should create a dedicated external_api account(see credentials/identities section in wazo-ui).
I’m not sure how you’re setupting the websocket and handling the login & subscription flow in node-red, but you need to make sure you use an admin account/token to do that, or one that specifically has the events.applications.# ACL permission(see https://api.wazo.io/documentation/events/application/ for events and their headers for the required_acl for each, # can be used as a wildcard).
