- Joined
- Dec 5, 2010
- Messages
- 22
- Reaction score
- 0
After upgrading to V18 (self hosted) I am trying to check the new Web Client and have a few questions:
1. I sent myself the use welcome email. The URLs specified for the web client are https://<internal ip>:5001/webclient for inside the office and https://<fqdn>:5001/webclient for outside the office. After the V18 upgrade, I have set up in my internal DNS a record so now internally the FQDN resolves to the internal IP of 3CX. How do I change the URL that appears on the welcome email so that inside the office is also pointing to the FQDN?
2. How do I replace the certificate used for the 3CX web client? I have a valid cert for our domain. Where do I place it so that 3CX serves this as the domain cert?
3. Is/Will there be some way to provision the new desktop app without having the client login to the web client only to click the provision button? the config file attached to the welcome email is a very convenient way in my eyes and should continue working with the new desktop app. I am planning on deploying the new desktop app via a GPO but do not want to make each user need to login to the web client only to click the provision button.
1. I sent myself the use welcome email. The URLs specified for the web client are https://<internal ip>:5001/webclient for inside the office and https://<fqdn>:5001/webclient for outside the office. After the V18 upgrade, I have set up in my internal DNS a record so now internally the FQDN resolves to the internal IP of 3CX. How do I change the URL that appears on the welcome email so that inside the office is also pointing to the FQDN?
2. How do I replace the certificate used for the 3CX web client? I have a valid cert for our domain. Where do I place it so that 3CX serves this as the domain cert?
3. Is/Will there be some way to provision the new desktop app without having the client login to the web client only to click the provision button? the config file attached to the welcome email is a very convenient way in my eyes and should continue working with the new desktop app. I am planning on deploying the new desktop app via a GPO but do not want to make each user need to login to the web client only to click the provision button.