I think the (teamviewer alternative) is a great solution.
I understand that opening the ports is only for me, on the client side, I don't need to open any ports, right?
I think you have a new client, I see that all your work is very professional, and I can't wait for the Teamviewer version, I would love to buy yourself and try this version. (I hope that in the future some update can be done between versions)
Thank you
Juan Carlos
Hello,
Yes correct, you will only need to open port for the host (the side that receives the connection and shares it's screen/data)
But we will take it to the next level where there won't be any need for opening ports by connecting both the server & the client to a middle-ware B4J server. and each side (client & host) will have IDs instead of IP & port
As for the teamviewer alternative, We are currently working on version 3 which will be a customer support website, below are the details :
1- The customer opens a ticket requesting help
2- The system admin will see his/her request details
3- The system admin is able to LIVE chat with the customer
4- The system admin is able to send a remote connection request (.jar file) to the customer, the .jar file will contain the ticket ID and
will only be used once and can't be used again as soon as the .jar file is opened (High security measures)
5- Once the customer runs the .jar file the system admin is able to control the customer's PC/Laptop/Phone without the need to do any configurations (just hit run)
6- Once the connection is established, the customer is able to disconnect the admin at any time , the total connection time limit will be controlled by the customer (count down)
The above solution is amazing for any customer support business
Thank you,
Saif