<![CDATA[Client Continues to Receive Messages After Logout]]>We have noticed that occasionally when the user logs out of the FOP2 server but leaves the browser open, that he continues to get messages from the server. He tells us that he hears the ringing sound when a queue call is received.

I checked the FOP2 server log and verified that the close message was received by the server.

One thing I noticed is when I attempt to replicate the problem, I see what appear to be entries in the log that support the close request.

<= <msg data="19|close||a51774713f90db99bb7ebe652561d2c8" />
-- PROCESS_FLASH_COMMAND origen 19 accion close destino password a51774713f90db99bb7ebe652561d2c8
Client Disconnection - remove client on error from socket AnyEvent::Handle=HASH(0xe5ac120) (75.85.118.107:52967)
Client disconnection, user 4159672901 logged off
Discarding from status notifications as it is not a permitted possition (19).
No context defined for AnyEvent::Handle::destroyed=HASH(0xe5ac120) (unauthenticated or connection failed), skip online status notification.

However, when I check the user's logout, all I see is the close request, but no additional entries after it.

<msg data="232|close||27b6226a159a2293f8e746543f18464d" />

I don't know if this indicates an error in the close request or something else.

Can you think of a reason that the server would continue to send messages to a client after logout? There is a possibility that another user is logged into FOP2 with the same extension.

]]>http://localhost:4567/topic/1908/client-continues-to-receive-messages-after-logoutRSS for NodeTue, 27 Oct 2026 04:38:14 GMTWed, 11 Feb 2015 16:20:57 GMT60<![CDATA[Reply to Client Continues to Receive Messages After Logout on Mon, 16 Feb 2015 20:23:14 GMT]]>Confirmed the problem... I am working on a fix (to be included in the upcoming 2.29 version).

]]>http://localhost:4567/post/8323http://localhost:4567/post/8323Mon, 16 Feb 2015 20:23:14 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Sat, 14 Feb 2015 15:25:07 GMT]]>I reloaded the original 2.28 fop2.js and was able to reproduce the problem, albeit a bit differently.

This time, open the browser, navigate to the fop2 login page, and enter a correct extension with an invalid password. The client sends the auth request, gets the incorrect return, and redisplays the login dialog.

uncion init
VM97:1 sends auth 1234 y ieRMoKueUKgRfm9Q9nK1RoAGzbSAX
VM97:1 ws send <msg data="1|auth|4159672901|1da254f595f949a51b0aa5232a19a020" />
VM97:1 0,incorrect=0 en slot
VM97:1 show sec box
VM97:1 limpia todo
VM97:1

At this point, do the update in FreePBX. The fop2 server will start sending messages to the client that never logged in.

]]>http://localhost:4567/post/8322http://localhost:4567/post/8322Sat, 14 Feb 2015 15:25:07 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Fri, 13 Feb 2015 02:26:57 GMT]]>I cannot reproduce the issue. Maybe your modifications have something to do? When I click close , the web page is actually refreshed. The javascript application is completely reloaded. All variables are reset. Perhaps you are passing the extension via uri parameters?

]]>http://localhost:4567/post/8321http://localhost:4567/post/8321Fri, 13 Feb 2015 02:26:57 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Fri, 13 Feb 2015 02:10:04 GMT]]>[root@ASTERISK18 ~]# /usr/local/fop2/fop2_server --version
fop2_server version 2.28

]]>http://localhost:4567/post/8320http://localhost:4567/post/8320Fri, 13 Feb 2015 02:10:04 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Thu, 12 Feb 2015 19:46:39 GMT]]>What fop2 version are you using? I have just make a quick test with my trunk version, I have no issues with it. Once I log off from fop2, the page itself refreshes and I have the login box again, and there are no events being received in it after doing a fop2 reload, or an asterisk reload.

]]>http://localhost:4567/post/8319http://localhost:4567/post/8319Thu, 12 Feb 2015 19:46:39 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Thu, 12 Feb 2015 19:39:17 GMT]]>I forgot to add that we have made some modifications to fop2.js so there will be some messages you do not recognize.

]]>http://localhost:4567/post/8318http://localhost:4567/post/8318Thu, 12 Feb 2015 19:39:17 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Thu, 12 Feb 2015 19:37:18 GMT]]>I was finally able to replicate this problem consistently. The problem occurs in both Chrome and Firefox (the only two browsers we use).

To replicate the problem:

  1. log into FOP2
  2. log out
  3. In FreePBX, I updated the permissions of my user, clicked on Submit Changes, and then Apply Configuration Changes.
  4. At this point, the FOP2 server starts sending messages to my logged off client again.

I have attached the console log that shows this. I added
=====> Here I am logged out and have the login dialog <=====
to the log so you can see where I am logged off. There are a couple pings after this, and then a whole slew of messages from the FOP2 server.

]]>http://localhost:4567/post/8317http://localhost:4567/post/8317Thu, 12 Feb 2015 19:37:18 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Thu, 12 Feb 2015 15:18:47 GMT]]>What browser are you using? Any way I can use to try to replicate the issue myself?

]]>http://localhost:4567/post/8316http://localhost:4567/post/8316Thu, 12 Feb 2015 15:18:47 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Thu, 12 Feb 2015 14:01:29 GMT]]>The console log continues to show messages sent from the server.

]]>http://localhost:4567/post/8315http://localhost:4567/post/8315Thu, 12 Feb 2015 14:01:29 GMT<![CDATA[Reply to Client Continues to Receive Messages After Logout on Wed, 11 Feb 2015 21:30:46 GMT]]>What do you see in the javascript console after login out? any activity at all ?

I mean, you mention that a call enters the queue and the notification sound is fired, do you see any logs in the javascript console at that point? Even if the fop2 display shows a login box?

]]>http://localhost:4567/post/8314http://localhost:4567/post/8314Wed, 11 Feb 2015 21:30:46 GMT