Skip to content
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

Notifications should include call context where possible #5

Open
bklang opened this issue Feb 16, 2014 · 2 comments
Open

Notifications should include call context where possible #5

bklang opened this issue Feb 16, 2014 · 2 comments

Comments

@bklang
Copy link
Member

bklang commented Feb 16, 2014

I'm not sure this is possible, and I'm pretty sure it would require some kind of support in Adhearsion. To help troubleshoot, it would be nice if notifications included information from the call object, most importantly, the call ID.

Ping @benlangfeld is this possible? I realize not every exception coming out of Adhearsion will have a call attached to it, but it would be helpful in cases where it is.

@benlangfeld
Copy link
Member

Exceptions in Calls and CallControllers could have the call's available metadata attached, but this would require support in Adhearsion core.

@emcgee
Copy link

emcgee commented Jul 22, 2014

👍

Notifications including the call uuid would make debugging distributed production systems with heavy call traffic much simpler.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants