<![CDATA[Agent is not removed from Queue upon logout]]>Using the Queue Plugin.
Agents get logged in to the queues that I select when I log in, but they do not get removed upon logout from FOP2.

On queue show in Asterisk CLI, I still see the extensions in the queue.

]]>http://localhost:4567/topic/2120/agent-is-not-removed-from-queue-upon-logoutRSS for NodeTue, 27 Oct 2026 08:29:07 GMTSat, 05 Dec 2015 15:53:50 GMT60<![CDATA[Reply to Agent is not removed from Queue upon logout on Wed, 07 Dec 2016 13:14:16 GMT]]>Unfortunately the queue login plugin won't work if you use the chrome extension (as the chrome extension will keep the agent logged all the time, there would not be a logout event if you use it). I did not find a way around that yet.

Best regards,

]]>http://localhost:4567/post/9331http://localhost:4567/post/9331Wed, 07 Dec 2016 13:14:16 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Wed, 07 Dec 2016 03:05:21 GMT]]>Hello, i am just opening up this discussion to possibly see if you were able to get the agent logout to work the chrome extension being enabled.

I suppose the solution would be to allow agents to just status themselves as DND but there are some old dogs here...

please let us know if there was ever a fix for this.
thanks!!

]]>http://localhost:4567/post/9330http://localhost:4567/post/9330Wed, 07 Dec 2016 03:05:21 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Thu, 03 Mar 2016 15:40:49 GMT]]>@admin Did you find a way for logout to work with the chrome extension running?

]]>http://localhost:4567/post/9329http://localhost:4567/post/9329Thu, 03 Mar 2016 15:40:49 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Tue, 29 Dec 2015 13:33:16 GMT]]>Yes, that is the problem. There is no way to make both work. What happens is this: the plugin checks for logout events, but if it sees the user still being logged/connected, it won't execute the logout actions. The plugin will log you in and keep you connected, no matter if you logout from the main fop2 display. And so the logout actions won't kick in.

The problem here is that I had to make the logout actions only work when no sessions were active because different browser versions could have erratic management of websocket sessions, where you could have two sessions open at the same time (but only one actual session working), and one of them is then killed by the browser after some time. If the server detects that ang logs you off, while you still have a valid connected session, the result is unexpected and wrong.

When using the Chrome extension, you do have two valid connections using the same extension, and hence you are never logged out (unless you close/deactivate the chrome extension).

There is no easy way to make them work together. A plugin upgrade is not enough. But I will see if I can work on something for a next release, trying to identify chrome extension clients from regular browser clients and work from there.

]]>http://localhost:4567/post/9328http://localhost:4567/post/9328Tue, 29 Dec 2015 13:33:16 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Tue, 29 Dec 2015 13:32:12 GMT]]>Yes, that is the problem. There is no way to make both work. What happens is this: the plugin checks for logout events, but if it sees the user still being logged/connected, it won't execute the logout actions. The plugin will log you in and keep you connected, no matter if you logout from the main fop2 display. And so the logout actions won't kick in.

The problem here is that I had to make the logout actions only work when no sessions were active because different browser versions could have erratic management of websocket sessions, where you could have two sessions open at the same time (but only one actual session working), and one of them is then killed by the browser after some time. If the server detects that ang logs you off, while you still have a valid connected session, the result is unexpected and wrong.

When using the Chrome extension, you do have two valid connections using the same extension, and hence you are never logged out (unless you close/deactivate the chrome extension).

There is no easy way to make them work together. A plugin upgrade is not enough. But I will see if I can work on something for a next release, trying to identify chrome extension clients from regular browser clients and work from there.

]]>http://localhost:4567/post/9327http://localhost:4567/post/9327Tue, 29 Dec 2015 13:32:12 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Wed, 23 Dec 2015 02:39:58 GMT]]>Yes I am. Guess that's the problem.
Any way to make both work?

]]>http://localhost:4567/post/9326http://localhost:4567/post/9326Wed, 23 Dec 2015 02:39:58 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Tue, 22 Dec 2015 13:50:32 GMT]]>Do you use the chrome extension also?

]]>http://localhost:4567/post/9325http://localhost:4567/post/9325Tue, 22 Dec 2015 13:50:32 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Mon, 21 Dec 2015 01:18:49 GMT]]>My user logs in automatically into the queue upon fop2 login, but does not log out. I have set Queue Plugin to"Automatically Login To All Queues: YES"

]]>http://localhost:4567/post/9324http://localhost:4567/post/9324Mon, 21 Dec 2015 01:18:49 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Mon, 21 Dec 2015 01:17:04 GMT]]>I press this "Logout" button:
[attachment:56775306c2f11]

]]>http://localhost:4567/post/9323http://localhost:4567/post/9323Mon, 21 Dec 2015 01:17:04 GMT<![CDATA[Reply to Agent is not removed from Queue upon logout on Sat, 05 Dec 2015 18:34:19 GMT]]>How do you logout from FOP2?

]]>http://localhost:4567/post/9322http://localhost:4567/post/9322Sat, 05 Dec 2015 18:34:19 GMT