I have an application that needs to listen to events and the developers would like to use HTTP to connect. Seems that the options are ARI or AMI-over-HTTP, or do like FreePBX does and run a little node.js daemon that listens to the manager and offers an HTTP interface.
I’m not keen on the third option. Is there a way to get more events to ARI (specifically, within the realm of FreePBX; i.e. not using a Stasis app) so that we can take advantage of the websocket interface? Is the AMI-over-HTTP too deprecated or unsupported to consider?
Last resort I’ll open the manager interface for a TCP socket but really prefer not to.
ARI is a subset of events, if the events aren’t documented on the docs site then they don’t exist in ARI. You CAN use AMI-over-HTTP but it was created long ago and just keeps on trucking along with a handful of people using it, so it could have quirks on usage.
You got any where with this? I’ve messed around with this both using sockets and HTTP. Is this going to be used via a GUI or will you be listening for the events and acting on them in the background?