| Summary: | ASTERISK-02129: issues with wrapuptime | ||
| Reporter: | jesses (jesses) | Labels: | |
| Date Opened: | 2004-07-27 14:10:07 | Date Closed: | 2011-06-07 14:11:55 |
| Priority: | Trivial | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Seems like if I change the wrapuptime without restarting asterisk completely, then every agent who is already logged in (AgentCallbackLogin) has to log out and then log back in for the new wrapuptime to take effect. Is there any way to make the changes take effect without logging back in? | ||
| Comments: | By: Mark Spencer (markster) 2004-07-27 15:28:23 Nothing in the code seems to suggest that agents would need to logoff and back on to change their wrapuptime. Are you executing a "reload" though? By: jesses (jesses) 2004-07-27 15:39:28 I did reload and then reload all just to be sure, and I observed none of the agents experiencing a wrapup time, but having the agents log out and in fixed it for whatever reason By: jesses (jesses) 2004-07-27 16:00:03 Also if a single agent is logged into two queues that both have the wrapuptime set to the same value... 1) Call from Queue 1 goes to agent 2) Agent hangs up 3) Call from Queue 2 goes to agent with no wrapuptime By: Mark Spencer (markster) 2004-07-27 17:07:41 Actually the agents.conf one is the one you want. | ||