[asterisk-bugs] [JIRA] (ASTERISK-25850) Channel related AMI messages are arriving after the CHAN_END and LINKEDID_END CEL messages.
Richard (JIRA)
noreply at issues.asterisk.org
Wed Mar 16 13:34:56 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard updated ASTERISK-25850:
-------------------------------
Attachment: summary.txt
sip.conf
queues.conf
manager.conf
extensions.conf
debug.log
cel.conf
ami-abridged.out
ami.out
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
> Channel related AMI messages are arriving after the CHAN_END and LINKEDID_END CEL messages.
> -------------------------------------------------------------------------------------------
>
> Key: ASTERISK-25850
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25850
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: CEL/cel_manager, Core/ManagerInterface, Core/Stasis
> Affects Versions: 13.6.0, 13.7.2
> Environment: Operating System: CentOS 7 64 bit
> CPU: Intel Xeon CPU E5-2403
> RAM: 12 GB
> HD: 250 Gb
> Reporter: Richard
> Severity: Minor
> Attachments: ami-abridged.out, ami.out, cel.conf, debug.log, extensions.conf, manager.conf, queues.conf, sip.conf, summary.txt
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list