[Home]

Summary:ASTERISK-26622: Call ID in AMI Cdr events
Reporter:Luke Escude (lukeescude)Labels:
Date Opened:2016-11-23 13:13:04.000-0600Date Closed:2020-01-14 11:14:10.000-0600
Priority:TrivialRegression?
Status:Closed/CompleteComponents:
Versions:13.12.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:It would be great if the AMI CDR event would also contain the Call ID of the current phone call. That way, we can programmatically load the debug logs that surround just that one phone call.
Comments:By: Asterisk Team (asteriskteam) 2016-11-23 13:13:05.178-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Rusty Newton (rnewton) 2016-11-23 16:12:41.121-0600

Features requests without patches are not accepted through the issue tracker. Features requests are openly discussed on the mailing lists, forums, and IRC [1]. Please see the Asterisk Issue Guidelines [2] for more information on feature request and patch submission.

[1] http://asterisk.org/community/discuss
[2] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines



By: Rusty Newton (rnewton) 2016-11-23 16:13:37.409-0600

As mentioned in the previous comment, you are welcome to submit a patch and we would be glad to help with any questions regarding that. You can always drop by the #asterisk-dev IRC chat room on irc.freenode.net or the asterisk-dev mailing list.

By: Asterisk Team (asteriskteam) 2016-12-08 12:00:01.303-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines