-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: create a simple example using manager.register_event() #26
Comments
I'm sorry, no time right now to do that. |
I'll try to make it by myself and send a PR. I'm a experienced Python developer but a newbie in asyncio/coroutine related subject and that's why I'm asking for some help here. (I'm currently reading the asyncio chapter of Fluent Python book to learn how to use it and I could use panoramisk as an exercise 😄) |
If you are smart enough to handle Asterisk and VoIP in general, AsyncIO and async pattern in general should be considered easy as pie, at least to me ;-) |
Cool! Thanks @tannermkerr! It'll be very useful on my next project: https://github.com/osantana/ami-push It's only a project boilerplate that I started yesterday but the main goal is to create a daemon that listen for AMI events and make http request to an specific URL when some specific event type are triggered. |
no problem glad to help. I was having the same issue as you, while trying to create a custom reporting tool. |
@osantana: good idea with ami-push: Don't hesitate to ping me when it will be done. @tannermkerr: for custom reporting tool, I recommend you to use CEL: https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=5242932 With that and pgsql connector, you can build a reporting tool without AMI. Have a nice day. |
Hi, As I promissed follow a link to my project that make http-posts based on events on AMI: https://github.com/osantana/ami-push Thanks for panoramisk! |
@osantana it looks promising ;-) |
I'm an asyncio "newbie" and really like to see a simple but complete sample of manager.register_event() usage in a "server_forever" loop.
The text was updated successfully, but these errors were encountered: