Recent content by derfloh

You should use a certificate authority that generates the certificates and avoid using the self signed certificates from IPO security settings.

Manager cannot create that file… That made me laugh today…

On a hardware server it should stay the same. If you setup a virtual one the host ID will change. But if you have access to the licenses in PLDS, it’s not a big deal to rehost them to the new WebLM.

There are various settings to do in IPO and DNS and you will also have to care about the correct certificates. I did it many times. It’s hard to get it only from docs but without experience.Getting instructions while setting it up is the best way to learn.

Even if I prefer ARS it should work without ARS by directly using the SIP trunk line group ID within short codes. As long as you don’t slow your short codes, we will not find the reason.

It only binds the extension to an specific IP. It is I’ll not avoid registration of another extension to that device.

First of all you should check what cake is you send in this case.

I would think of the option to connect the new server and replace the old one by keeping the old IP. Nonetheless, the phone update their configuration from 46xxsettings.tx/46xxspecials.txt in intervals. See this to adjust it...

Since user buttons and user status are usually (similar to Workplace Client) updated by SIP notify messages this should work, even if I have no experience. I don’t know how that function is called by Yealink.

It‘s not the worst idea. And relatively easy for the secondary Server

Correct, it will find the correct system where the extension is set up.

Try to start service “webcontrol” via SSH and connect to the server with port 7071. Then try to reinstall the IP Office package.

No response… probably a certificate issue or a blocking firewall. The second last line looks like a certificate problem.

you don’t have little to no knowledge about IP Office, right?

Maybe Microsip is forgiving if a certificate is not valid. IPO isn’t.