So it looks like this product is dying a slow death, due to the support complaints. I sent an email in and not sure if I’ll get a reply. I also just paid to renew the mobile support, and we never got mobile working quite right when it was installed months ago (when we moved from Amazon AWS to Google Cloud Compute Engine).
We have AVChat3 running on a linux VM server with Red5 and WordPress running on a second linux VM server.
I have port 8081 and 1935 open (tcp incoming and I believe out also), on the chat server. And the server was setup with SSL.
Desktop users can login fine. It’s mobile users who login with the [chat] shortcode, who are registered members, will have their username recognized when connecting to chat, but then there is a "Connection Lost” error. This seems to be a common issue, reading your forums. But I have been unable to solve it.
We ended up create a “mobile link” on our chat page, that goes to: http://www.derekandromaine.com/wp-content/plugins/avchat-3-pro/ws/ws-chat.php - but even this works quirky. Using this link, a chat window will open on the mobile device and it will start with an error “Username is mandatory. Connection Rejected. Go To Login Page.”
Once we get to the login page, it defaults the username to a random “Visitor_##” username.
Users who are paying members of the site, get to that point and then will backspace over “Visitor_##” and put their WordPress username in. Then they can get into the chat on their mobile device. However it does not do any authentication between the chat server and wordpress at that point - to make sure a valid authenticated wordpress user has logged in. I can login as any of our usernames and masquerade as them.
Sometimes even people trying to login with “Visitor_##” cannot login as visitors. Or if they do get it, sometimes desktop chat users who are already in the chat room, cannot see the visitors. But the visitors can see the other chatters.
I’d like to get this fixed primarily so mobile users can enter using the [chat] link, which I believe should properly authenticate them. We also do not want unauthenticated visitors in the chat.
Can anyone help with this?