[asterisk-bugs] [JIRA] (ASTERISK-20743) COMPLETEAGENT
Michael L. Young (JIRA)
noreply at issues.asterisk.org
Tue Dec 18 09:57:45 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200812#comment-200812 ]
Michael L. Young commented on ASTERISK-20743:
---------------------------------------------
Understood. This helps us to troubleshoot and to track down what is happening as well as understand if it was the same bug report as the other issue. This way we only focus on one issue rather than two issues and avoid having two different people working on the same issue. Thanks for the feedback.
> COMPLETEAGENT
> -------------
>
> Key: ASTERISK-20743
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20743
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_queue
> Affects Versions: 1.8.18.0
> Environment: A - caller. B - queue member (SIP / XXXX).
> A call to the queue. B is responsible. But after a conversation B hung up. In queue_log written COMLETECALLER!
> Reporter: call
> Assignee: call
>
> A - caller. B - queue member (SIP / XXXX).
> A call to the queue. B is responsible. But after a conversation B hung up. In queue_log written COMLETECALLER!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list