unable to change teleworker gateway

[mhumphries]

we have several teleworkers that need to change the teleworker Gateway but it is not allowing them to do that.  it can be enabled/disabled, but not modified.

[mcastle]

On the device themselves or MBG?

[sunspark]

You have to change the gateway on the profile deployment.

[mhumphries]

this is the teleworker gateway not the MiCollab Server that i am trying to change.  on the MiCollab Client itself

[PC77375]

Are these Mitel desk phones or Micollab softphone endpoints? If they are physical desk phone endpoints, then the gateway needs to be changed from the physical device...if I am understanding this correctly, is it the public IP of the MBG that has changed and the endpoints need to be updated to connect to the new IP? What model phones are they?

[sunspark]

as i said , if you talk about the teleworker Gateway in the micollab client setting . you have to change it in the micollab server --> deployement profile.

[sarond]

I have found that the address was sometimes wrong in the MiCollab client and could not be changed from the client itself.

The only way I found to get it to update to the correct address is from the server side.
MiCollab Client Service>Configure MiCollab Client Service>Accounts>{user}>Account Settings>Web RTC Gateway MBG FQDN

Once I added/modified it here it appeared in the client. Just have them restart the client first.

[eugenej]

I have found that the address was sometimes wrong in the MiCollab client and could not be changed from the client itself.

The only way I found to get it to update to the correct address is from the server side.
MiCollab Client Service>Configure MiCollab Client Service>Accounts>{user}>Account Settings>Web RTC Gateway MBG FQDN

Once I added/modified it here it appeared in the client. Just have them restart the client first.

Does this setting not only affect the webRTC setting in the web client for MiCollab?
I thought the deployment profile took care of the actual TW settings in the "fat" clients

[mhumphries]

so we found that on some clients the Micollab setting forcing the Server address.  once we cleared this we were all good