Support & Forums
Labs & Sandboxes
|[+] Avaya Aura Basic Development Environment (Archive - Oct 2013 and earlier) » CM unable to aquire license, 29/10/2013 11:21:41 » Go to message|
This was installed on Friday, so it has never worked. At that time the 2 XML license files were applied. I had previously tested the VMs in VMWare Player just to confirm that there were no major snags following though the network configuration document sent with the BDE.
I had not worried about the error under player because I had not yet applied the license files.
Both VM's have been rebooted a couple of times since then as I was trying to troubleshoot this issue. The CM was also rebooted once because I used the "Stop DADS" Button after getting the console working.
Also because I saw that the CM gets its licenses from the AES, I have always been bringing up the AES to a login prompt before launching the CM instance. I don't believe that was explicitly started anywhere, but this is one of several projects I am taking over.
The two files we received were:
ExpirationDate 2014/01/31 throughout both documents.
|[+] Avaya Aura Basic Development Environment (Archive - Oct 2013 and earlier) » CM unable to aquire license, 28/10/2013 19:05:45 » Go to message|
I look a look at our setup, ecs.conf is looking in
The license server is there on the AE, is just not responding the way the CM expects. I can ping between the hosts, and running WGET from the CM to AE pulls the license server splash screen. I also have to use WGET --no-check-certificate because of the certificate ip/name mismatch.
wget -S --no-check-certificate https://192.168.51.253:443/WebLM/LicenseServer
When the CM is requesting the License file, I take it is requesting to read the installed XML document from the AE server which I provided to the AE server Licensing Application at registration?
I think the file is either not named the way the CM is expecting or is not in the location it is looking for.
As I mentioned before, uploading the XML was flawless an everything shows as being good from the AE's perspective, the CM just isn't seeing it.
|[+] Avaya Aura Basic Development Environment (Archive - Oct 2013 and earlier) » CM unable to aquire license, 28/10/2013 12:58:04 » Go to message|
We are running the AE and CM VMs in corporate lan mode,
Our licenses are installed into the AE server but the CM is not able to reach them with the following error.
CommunicaMgr License Mode: Normal
Unable to contact WebLM Server at the specified URL.
checking application CommunicaMgr version R016x.00.0.345.0
WebLM server used for License: https://192.168.51.253:443/WebLM/LicenseServer
Module ID is 1
System ID is 1
When I look at the WebLM server (WebLM v4.6) on 192.168.51.253:443 I see it and am prompted to login which I can do successfully.
Application Enablement (CTI) -- License installed on: Oct 25, 2013 5:05:28 PM MDT
Call Center -- License installed on: Oct 25, 2013 5:05:35 PM MDT
Communication Manager -- License installed on: Oct 25, 2013 5:05:35 PM MDT
In the AE server the WebLM Server address is set to 127.0.0.1:8443, but I don't get any response on that port. I also changed the listed port to 443 and restarted all of the AE's services with no change from the CM.
What should be my next troubleshooting steps?