| Summary: | ASTERISK-23309: [patch] Failed to pause/unpause already paused/unpaused realtime queue member | ||||
| Reporter: | Vladimir Astafiev (vldmr) | Labels: | patch | ||
| Date Opened: | 2014-02-14 07:35:50.000-0600 | Date Closed: | 2018-01-02 08:44:27.000-0600 | ||
| Priority: | Major | Regression? | Yes | ||
| Status: | Closed/Complete | Components: | Applications/app_queue | ||
| Versions: | 11.7.0 11.21.2 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) 23309-jira-asterisk.patch | |||
| Description: | Now when we pause already paused realtime queue member _update_realtime_member_field()_ failed and as result manager event not generated an queue_log entry not written.
I think _update_realtime_member_field()_ must be executed only when paused state of agent really changed. It's no reason to update unchanged realtime entry. For example, in my solution agents can change their statuses from paused with reason "Call processing" to paused with reason "Lunch" or to paused without reason. It's needed to logging agents worktime. | ||||
| Comments: | By: Joshua C. Colp (jcolp) 2017-12-18 10:47:04.659-0600 It appears the underlying code here changed. Is this still applicable? By: Asterisk Team (asteriskteam) 2018-01-02 08:44:27.242-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 | ||||