Only getting CHANNEL_EXECUTE_COMPLETE events
See original GitHub issueWe have been using node-esl on Debian without any issues, however, we needed to run one up on Ubuntu and when we do we are only getting back CHANNEL_EXECUTE_COMPLETE events from Freeswtich.
To start with am just trying to output all events to console via:
conn.on('esl::event::*::**', function(event) {
eventName = event.getHeader('Event-Name');
console.log(eventName);
});
The installed nodejs version is 4.2.6, Freeswitch 1.6 and Ubuntu 16.04
Any ideas as to what could be the issue?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Go: one channel with multiple listeners - Stack Overflow
When I issue an API call to create an event I just get output from the processEmail function. Its whatever go routine is...
Read more >Getting Started with Channels and Events
Now start a process instance, select the Gather Data task, fill in the form and click on Complete . Now go to the...
Read more >Make active channel display events from 90 days ago?
For this purpose, we need to make it so that our "Critical events" active channel can display events from 90 days ago. However,...
Read more >Receiving data multiple times · Issue #273 · pusher/pusher-js
It would seem that channel can get instantiated multiple times during the lifecycle of our app. It does not exist more than one...
Read more >Pusher Channels Docs | What is an event?
Events can be bound to directly on a channel. This means you will only receive an event if it is sent on that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Setting up the listeners (
connection.on
) outside the callback is totally fine as all that does is register a callback in JS land (no fsw interaction), butconnection.events()
send messages to freeswitch. If you aren’t connected, it can’t send those events, and therefore will not work before the ready callback is called.So, the issue I was having was that I was trying to
subscribe
or do anevents
call outside the scope of thenew esl.Connection
callback. Not sure if this is the same problem @kieranhackshall was having. But, this might help someone else.If I do this:
only CHANNEL_EXECUTE_COMPLETE shows up.
But, if I leave my
events
call inside the scope of the callback for thenew esl.Connection
connection, everything works. No need to changethis.reqEvents
to['ALL']
.