| Summary: | ASTERISK-25399: app_queue: AgentComplete event has wrong reason | ||
| Reporter: | Kevin Harwell (kharwell) | Labels: | |
| Date Opened: | 2015-09-17 12:08:20 | Date Closed: | 2015-09-19 16:29:09 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | 13.5.0 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When a queued caller transfers an agent to another extension sometimes the raised AgentComplete event has a reason of "caller" and sometimes "transfer". Since a transfer has taken place this should always be transfer.
Steps to reproduce (may take several times for it to happen): 1. alice gets queued and then bridged with member bob. 2. alice then does an attended transfer of bob to charlie. 3. observe the AgentComplete event's reason This occurs because sometimes the stasis hangup event arrives before the transfer event thus writing a different reason out. | ||
| Comments: | |||