[asterisk-bugs] [JIRA] (ASTERISK-20742) [patch] Log callers entering/leaving MOH.

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200253#comment-200253 ] 

Richard Mudgett commented on ASTERISK-20742:
--------------------------------------------

Yes you are setting precedent here for queue_log.  You are passing information to res_musiconhold from app_queue in the IN_QUEUE and IN_QUEUE_MEMBERNAME channel variables.  chan_agent does not get any information from another module to queue_log when agents log in and log out.

You have misunderstood my suggestion.  What I was trying to get across was to make res_musiconhold always queue_log when a channel starts and stops playing MOH.  This way res_musiconhold is still independent of app_queue because res_musiconhold does not get any information from app_queue to produce its logs.  Then _like_ CEL you can do post processing on queue_log to determine the length of time a caller was placed on hold.
                
> [patch] Log callers entering/leaving MOH.
> -----------------------------------------
>
>                 Key: ASTERISK-20742
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20742
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: SVN, 12
>         Environment: all
>            Reporter: Steve Murphy
>            Severity: Trivial
>         Attachments: qonhold.trunk.diff, qonholdv2.trunk.diff
>
>
> This patch will allow incoming calls to track the time they are put on hold (MOH). This does not count MOH played before an agent accepts the call.

--
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