- Joined
- May 10, 2017
- Messages
- 20
- Reaction score
- 7
Hi all,
One of my users discovered this issue with the Windows Client when trying to share a link with a customer for a Meeting.
He uses Windows Client and wanted to have a webmeeting with an external customer so he clicked on the button os "Start a 3CX WeebMeeting now".
A new browser window poped-up and BY MISTAKE he shared the url of the browser instead of the shareable link of the meeting. I mean, he shared the url that the Windows Client generated (format like
What happened was that our customer was able to initate a Meeting with the name of my user and also capable to invite people to the reunion...
Plus that link is active, there is no way do deactivate it (I tryed ending reunion, deactivating in the extension the possibility of organazing webmeetings...)
We assume that it was our user's mistake but the issue and possibility of this is there.
This situation doesn't happen with the web client because the meeting remains on the same fqdn ""local"" url.
We wait for comments and suggestions, always valuable. Take care!
One of my users discovered this issue with the Windows Client when trying to share a link with a customer for a Meeting.
He uses Windows Client and wanted to have a webmeeting with an external customer so he clicked on the button os "Start a 3CX WeebMeeting now".
A new browser window poped-up and BY MISTAKE he shared the url of the browser instead of the shareable link of the meeting. I mean, he shared the url that the Windows Client generated (format like
https://ourFQDN.3cx.net/webrtc/join/tdD_EfLq56hhjjjjjjFB8IIII).What happened was that our customer was able to initate a Meeting with the name of my user and also capable to invite people to the reunion...
Plus that link is active, there is no way do deactivate it (I tryed ending reunion, deactivating in the extension the possibility of organazing webmeetings...)
We assume that it was our user's mistake but the issue and possibility of this is there.
This situation doesn't happen with the web client because the meeting remains on the same fqdn ""local"" url.
We wait for comments and suggestions, always valuable. Take care!