Anyone using SLA Mon? We have it running and it can see the phones and their firmware etc. but they fail to connect to them to run tests and packet capture.
-
-
Does the 46xxsettings.txt file enable the SLA features and direct the phones to the correct CA certificate?Meridian IT - Senior Engineer
-
1. In the 46xxsettings.txt file on our Https server we set the TRUSTCERTS parameters like this: SET TRUSTCERTS rootCA.pem,av_prca_pem_2033.txt
2. Then we reboot the phones.
3. To turn on the SLA Mon features on the endpoints, we configured the following
parameters in the phones settings file, 46xxsettings.txt, on our Https server (mentioned above) to which the phones point to .
SET SLMSTAT 1 1= Enables the Agent
SET SLMCAP 2 2= Enables Packet Capture
SET SLMCTRL 1 1=Enables Remote Control
SET SLMPERF 1 1=Enables Event Monitoring
SET SLMPORT 43210 The SLA mon control port to receive phone discovery info
SET SLMSRVR 10.x.x.x:50011 (Example) IP address of the SLA Monitor ServerComment
-
What firmware version are the phones running?
Default SLMPORT is UDP 50011. That can be changed, but you need to edit the /opt/avaya/slamon/bundleconf/agentcom-slamon.conf file and then restart SLA Mon services. Has that been done?
I'd try using the default port to start with.Meridian IT - Senior Engineer
Comment
-
I got it to work. I had all the settings in the 46XX file correct it was a cert problem. I was cutting and pasting to a text file as it said to do but once I copied the actual rootCA.pem to the HTTPS server and got it to reload to the phones it worked like a charm. Thanks for the responses.Comment
Comment