| Summary: | ASTERISK-02151: Limit number of calls to Agent | ||
| Reporter: | Ryan Courtnage (rcourtna) | Labels: | |
| Date Opened: | 2004-07-30 10:34:35 | Date Closed: | 2011-06-07 14:04:49 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Since outgoinglimit is EOL'd, SetGroup/CheckGroup can be used to ensure that SIP clients will only have a single call at any time. Â Works perfectly for simple calls using Dial(). There appears to be no way to do this for Agents, who get their calls from a Queue(). ****** ADDITIONAL INFORMATION ****** A possible way to solve this is to have the agents app do "SetGroup(extennum)" and "CheckGroup 1" to determine if an agent is free prior to sending a call to it. The sys-admin could then also take care of incrementing SetGroup(extennum) with any non-queue calls that the extension makes/receives. | ||
| Comments: | By: Ryan Courtnage (rcourtna) 2004-07-30 10:36:20 sorry, this belongs in 'Feature Requests', not the SIP category.. By: rwjblue (rwjblue) 2004-07-30 11:06:31 We need this functionality as well. When our agents log in to the Queue they use AgentCallbackLogin. If you supply a special context, for example AgentCallBackLogin(|@intenal-acd), then configured that context to route the calls the way you want and put CheckGroup(${EXTEN}) as one of the first apps to get called. As long as you were to make the appropriate SetGroup() commands for all the other calls routed to the extension wouldn't that work? I am not sure. Just guessing here. By: Mark Spencer (markster) 2004-07-30 11:10:23 We've not decided to EOL the outgoing limit and yes, you can do it with grouping. | ||