Thanks for the good answers.I tried to show/suggest 3 problems/suggestion and You answered 2 times 3. But I found a lot of information in all of Your answers. Thanks. Maybe my poor english cause some misunderstanding. Sorry. "1. We support both formats. In order to use your own primary domain (eg: conference.mydomain.com) you would need to add a DNS record that resolves the domain to the IP address of the nefsis.com web server. Note that using a custom primary domain will result in the browser address not matching the SSL certificate if a user browses to your portal page securely."Is this means if we will change our settings at PersonalPage-URL then the Personal Page and the Conference links both will be appear in mydomain.com format? (Of course I need to point DNS to nefsis server before)
Or Do we need to change at My Deployment-General-Domain for conference link?2. I'm not sure I understand this issue. We would like to think users would be more concerned with the performance and usability of the software than the server which provides web content. Is this not the case?We are generally satisfied with performance and usability.
My idea is in deep relation in with the second 2. number where You answered: VCS web server is not proper place for Personal Page. I accept this answer.
3. This is intentional. The URL that appears on the Start tab is the same URL that will be sent in any of the invitation options on the Start tab.Not definitelly same. I asked my users to send link without &password.... The password for participation on a meeting is part of trustship of the customer and avoid unauthorized participation. As I told You we are a law office. We using conferences (for example) to providing and documenting stakeholder meetings, where only authorized people should be participate. The password for this conferences are separately handled. Not in the mail of invitation and reminder. Documenting means recording, member identification and after electronic signing of recorded file we store as evidence for public or court - as necessary.
This issue is answered below in number 3. From my part I support link without password and the password should be entered at the prompt of conference for everyone. Tha password will define the role we play in the conference. But every button in the GUI are welcome. 1. We're reviewing the format of the URLs created and used by Nefsis, especially in regards to deployments. We've found a few inconsistencies that result in different invitation formats depending on how the invitation is created.2. The VCS does have a minimalist web server which is only intended to assist participants with installation of the conferencing client and getting them connected to a conference. Hosting the portal content locally is not really feasible.3. This is intended, but in the process of being refined. There are several different URLs that will allow you to join a conference. Our aim is to be more consistent with what links we use regardless of how the invitation is created.Summary: I preparing to point DNS as suggested. Then I will try the possibility of using mydomain.com format for Personal page and Conference link. I understood the problem with SSL cert. I forget VCS as webserver.