| Summary: | ASTERISK-00967: [request] No way to automagically log out non-answering synamic agents | ||
| Reporter: | ewieling (ewieling) | Labels: | |
| Date Opened: | 2004-02-01 06:15:45.000-0600 | Date Closed: | 2011-06-07 14:04:52 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | There is no way to automagically remove an agent logged in using QueueMember when the agent forgets to logout of the queue and goes to lunch or leaves for a meeting or whatever. | ||
| Comments: | By: Brian West (bkw918) 2004-02-01 12:59:33.000-0600 you can use the "n" option on the queue to fall out once it reaches the end of the queue. By: ewieling (ewieling) 2004-02-01 14:13:36.000-0600 That does not prevent the lazy agent from getting future calls. By: Brian West (bkw918) 2004-02-01 14:35:17.000-0600 nope when you use the dynamic stuff they will still get calls but it should roll around to the next agent if you use random or round robin. The other methods are broken. By: ewieling (ewieling) 2004-02-01 15:01:29.000-0600 How about automagically logging out non-dynamic agents? Regardless this is not a solution to not being able to automagically log out dynamic agents. What I'm trying to set up is an Operator Queue and the customers wants to minimize wait time to under 30 seconds. By: Brian West (bkw918) 2004-04-18 01:34:18 Their is a patch on bugs to allow queue to dial more than one agent at a time. Or you can cvs co ICD and play with that. I think its semi functional at this point. bkw | ||