New PLDS license = HTTP request failed

[rcc1000]

Hello everyone,

I have a 9.1.4 system with various ADI license. Trying to install a new PLDS Avaya IP endpoint license for an additional IP Phone. Currently their is 6 ADI IP endpoint licenses.

When trying to load the new license remotely, I get an error pop up saying HTTP request failed ConnectFailure.

I have not tried yet going onsite & trying it. If anyone thinks that might help.

Even when I try going to the Embedded File Management, on that I get HTTP request failed 404 Not Found message.

I've tried a laptop with Manager 11.0 & on another laptop that has Manager 9.1.8 on it. Get the same results from both.

Any ideas???

Thanks

 

[sizbut]

No idea. But if you read back in this forum and others, a mix of ADI and PLDS licenses tends to cause issues.

Stuck in a never ending cycle of file copying.

 

[intrigrant]

Set File Writer IP Address to 0.0.0.0

 

[DaIPOTek]

Had this happen before. You should be able to upload through Web Manager no problem. If all else fails you can rename the PLDS license file to PLDSKeys.xml, upload to the Primary folder with Embedded File Management, and restart the SD card.

 

[rcc1000]

Thanks for the replies everyone.

I just went onsite & plugged into the WAN port & the license loaded the way it should.

I'm assuming a specific port(s) might also be needed (in addition to the ones they have opened for me to have remote access) to load a PLDS license.

Have the new phone up & running.

Thanks again

 

[Mikel82]

I hope you are not pointing Manager at a public static IP address of the firewall and forwarding ports to the IPO. This is a great way to get hacked. Hackers use port scanners that look for open ports that IPO uses. If they detect a response from the IPO they will try accessing using default user names & passwords.


If your not going to it right don't bother doing it at all!

 

[rcc1000]

Thanks Mikel82,

I'm aware of this & seen hackers try to get in our systems before. I always changed the default usernames/password on all our systems & now always have things pointed to only my static IP in my office, instead of the whole world to see.
In the Control Unit Audit now, on all of my systems, no one is getting in trying the default credentials.
Just to have the least number of ports open for me to have remote access, I'll remember I need to go onsite to load a PLDS license for now on.