We deploy the 3CX Windows App v20 via msix.
Unfortunately every user has to enter the 3CX URL at first start. Most users don't know the url and don't read our manual.
It would be great if at least the 3CX URL could somehow be provided via DHCP, DNS, GPO, Powershell or a file on C: ...., so that users don't have to type it in themselves when they first start the 3CX windows app
Perhaps similar to IGEL? There you can create a DNS entry “igelrmserver” that points to the actual IGEL server. Perhaps the 3CX app could also try to call up a defined DNS entry such as “3cxserver” at startup?
Unfortunately every user has to enter the 3CX URL at first start. Most users don't know the url and don't read our manual.
It would be great if at least the 3CX URL could somehow be provided via DHCP, DNS, GPO, Powershell or a file on C: ...., so that users don't have to type it in themselves when they first start the 3CX windows app
Perhaps similar to IGEL? There you can create a DNS entry “igelrmserver” that points to the actual IGEL server. Perhaps the 3CX app could also try to call up a defined DNS entry such as “3cxserver” at startup?
Upvote
8
