| Summary: | ASTERISK-25850: Channel related AMI messages are arriving after the CHAN_END and LINKEDID_END CEL messages. | ||
| Reporter: | Richard (rpettitt) | Labels: | |
| Date Opened: | 2016-03-16 13:27:28 | Date Closed: | 2016-03-17 06:18:18 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | CEL/cel_manager Core/ManagerInterface Core/Stasis |
| Versions: | 13.6.0 13.7.2 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Operating System: CentOS 7 64 bit CPU: Intel Xeon CPU E5-2403 RAM: 12 GB HD: 250 Gb | Attachments: | ( 0) ami.out ( 1) ami-abridged.out ( 2) cel.conf ( 3) debug.log ( 4) extensions.conf ( 5) manager.conf ( 6) queues.conf ( 7) sip.conf ( 8) summary.txt |
| Description: | AMI message relating to a specific channel are arriving after the CHAN_END and LINKEDID_END CEL messages. We received the AMI Hangup message after the LINKEDID_END CEL event for a given channel in the telnet output log attached to this bug. There have also been instances where we received the QueueCallerAbandon and Hangup events after the LINKEDID_END CEL event for a given channel. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-03-16 13:27:28.769-0500 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: Richard (rpettitt) 2016-03-16 13:34:42.430-0500 The conf files were used to reproduce the issue in asterisk The ami.out file is the output from an AMI telnet session and contains 7 examples of the issue The ami-abridged.out file contains only the affected channels debug.log contains the asterisk log including debug information summary.txt contains the number of calls made and the number of affected channels and their linked ids By: Joshua C. Colp (jcolp) 2016-03-17 06:18:18.504-0500 This is not a bug. There is no guaranteed ordering or delivery time between both CEL and AMI events for when each will arrive. | ||