go-ari-proxy has been archived, would it be of value to implement something in this library?
There are a few design decisions that need to be made:

• Pluggable communication layer built as separate artefact as to minimise dependancies if the proxy is not used
• Does the proxy abstract the complexity of which Asterisk box or do we pass some of that to the application using this library
• How many queues/topics, (similar to go-ari-proxy or 1 for server and 1 for each client)
• Which message broker should be implemented and supported - RabbitMQ is what go-ari-proxy used and I've used in other projects...