I am in the middle of setting one of these things up (VMWare ADS 2.0) and it's a bit of a mess... From the start everything appears to be easy/setup but we are unable to control phones, and most of our subnet scans result is finding less phones then we know that is available. I have been banging my head on the screen for days trying to get the simple functions to work but I am missing something between the server and phones (And the corresponding 46xxsettings.txt file), and that is counting the number of half written guides and troubleshooting hints I have used. The whole Certs thing is a bit of a pain. Have you been able to get this up and running smoothly?
James E. Davis
I just finished setting up ours as a standalone system. It seems to find all my hardware but having issues getting the agent remote portion setup correctly. Documentation on testing and anything past initiall setup is quite vague at best.
Hello Kyle -
We finally got this working (kinda) and it was a pain... First it all centers around certificates both on the phone and on ADS. So depending on how your CA is setup, this could be part of the problem. We are testing at this time so we opted to use the Demo Cert, but will be moving to change that in the near future (As Avaya has stated they will not support the Demo cert moving forward with ADS).
You might have to fiddle with the 46xxsettings.txt file to accecpt the CA (And even turn on the SLA Agent on the phone). So below I will just ramble a few items that we had issues with.
The 46xxsettings that come into play are:SLMSTAT
Of these settings, I have found (My experinces and my opinion) that you don't want to wander from the default port on SLMPORT, and the example for SLMSRVR seemed wrong, as it just needs an IP Address (No other setting). There also seems to be a delay on when a phone gets rebooted to take these settings, and when it can be found/reconized/work on the Remote Agent. I had phones take over 2 to 4 hours to become usable (And we are running near the latest loads of firmwares on these 96xx Phones).
Also check how you have the Trusted Certificate on the settings file setup. Here is one way we got it to work:
Last but not least, this feature doesn't work on 16xx type IP phones... I know it seems obvious if you read the documents, but I have found that sometimes obvious is not that easy! :)
I agree with the issues with documention. I deployed it as an VMWare ova and all went well. I generated a self-signed cert rootCA.pem as documented in the ever famous Chapter 6 of the admin guide. I deployed the rootCA cert via Utility Server and updated the 46xxssettings file to enable slamon and included the cert in TRUSTEDCERT as the first cert. Rebooted a phone but never saw it download the cert. In the app it cannot find the agent on the set.
Digging further...there is an agentcom-slamon.conf which is strangely confusing as most of the settings are commented out (#). I've attempted to vi the settings but ultimately it breaks the server-client cert and you have to recreate a new self-signed cert to recover.
I've got the server setup to allow access. But it still wont find an agent. I'd really like to find a way to verify the phones slamon agent is active and the rootCA.pem is on the phone. On that note, did the phones ship with a demo rootCA.pem file? If so, apparently the phone will not download a new file with the same name...so perhaps recreate a new rootCA.pem with a different name? UGH
AVAYA is aware of the cert issues and I can say they will address this issue asap for the next release (or sooner) of ADS. I have spoken with the lead dev several times regarding this and it's my hope they make the cert selection and setup a part of some post-install web-gui wizard, but that may need to wait for a new version...they should, however be able to create a couple of scripts that work like the demo cert script.
I was finally successful in getting my certs deployed. I'm not sure if it was the name of the cert file or that I had placed the settings into a group in the 46xxsettings file. I had recalled reading somewhere that if the phone already has a file that matches the one you are trying to push (ex. rootCA.pem) the phone will not download the file. Renamed the cert file and placed the SLAMon settings in the common settings of the 46xxsettings and all is well.
did the name of the .pem need to match on both the agent and the server? I have the ADS up and running with self-signing, but am having a hell of a time getting the agents to be recognized (get a Certificate error on the agent screen) -
Any logs you know of that can be viewed to see if the error is on the agent or the server?
I know the contents have to be the same, I wasn't sure if the name of the file had to be the same - I was going to rename the .pem on the HTTP (Phone) side, as I am not sure the phone is downloading the new rootCA.pem that is uploaded
For anyone having issues with the certs on the SLA Monitor - check avaya support. they just released a certificate wizard - I downloaded and ran it - and had my test phones connected to SLA Monitor in under 10 mins. Huge headache relieved.
Dang it, that cert script locks up on stopping the services and I end up having to terminate it.
Didn't for me, did you stop the services yourself before hand? Try it with the services running and let the wizard stop them for you.
Or check with the Services Council chair :)
Hello, I just installed ADS as a virtual appliance, version 2.0. I have a problem with the license in the grace period. I would like to test the server for 30 days, but... After restart I see 30days grace period, but after 5minutes more, both - Monitoring :Disabled Diagnostics :Disabled . Do you have any ideea? Please help. Thank you!
In Reply to Gary Rogerson:
Has anyone implemented ADS? If so, what is your experience with it? Also, if implemented what version are you using?
Older deployment guide Release 1 states NAT (Network Address Translation) between SLA Mon server and endpoints is NOT supported, does anyone know if this has changed? I can't find mention of it in newer docs.
ADS would be useful for us if it could communicate with VPN phones.
450 10th Circle N
Nashville, TN 37203
Site Designed by Brightfind