Micollab FQDN

[johnp]

I inherited a site that was installed with a .local domain. This customer is currently using the 7.3 client but wants to get external/mobile applications working. Just seeing if anyone know if I change to a true FQDN and add the .local as a second domain, whtehr the 7.3 clients will function without having to modify their settings. This would only be internal until moved to new client

[ZuluAlpha]

Would you just change it on the customer firewall? As long as the FQDN points internally I can't see an issue but I'm not speaking from experience. Are they using mobile softphones? That might get trickier.

[sunspark]

OK then ,

change your micollab.mycompagny.local to micollab.mycompagny.com.

in the DNS entries, make the association between the ip of your micollab and the new fqdn.

where it is more complicated / to test:

1- quit the Micollab client and reconnect, if it works all the better otherwise:

you have to relaunch the client installation wizard to change the fqdn of your micollab to .com instead of .local ( you can do that with GPO if you have many users)

2 you can also go to c/program files x86 / Mitel /unfied communicator advanced 7.3 / UCA.exe.config  then change the value = micollab.mycompagny.local  by .com

this configuration is valid in lan mode only.

[johnp]

Thanks, I know how to change the client settings. I am installing a new system and think I'll try it there

[johnp]

I tested this and it does need that FQDN to be in the certificate

[sunspark]

If you are in lan mode only, you don't need a certificat for legacy clients