Even then, that syslog/RTMT message only sends when it encounters overage, not 
in advance of, correct?

Ben Amick
Unified Communications Analyst

From: Erick Bergquist <[email protected]>
Sent: Thursday, March 29, 2018 1:02 PM
To: Ben Amick <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] Automated capacity notification for CUCM/UCCX/QM?


Security Notice: This is an EXTERNAL email. Please exercise caution and DO NOT 
open attachments or click links from unknown or unexpected senders.
I’m not aware of any. I wish ELM/PLM had way to monitor elm/plm directly (snmp 
polling, etc) but it is up to application to alert.

There is a bug on call manager where cucm does not send syslog for 
ciscosystemoverage alert and it doesn’t trigger for 7 days in RTMT. The RTMT 
email alert is only way to get notified of cucm 9.x-11.x license issue 
proactively unless you log in and see the warning message. I’ve had a few cisco 
cases on this bug trying to get them to fix it. I’m told it’s a enhancement but 
unity and cer send syslog fine for license overages.


On Wed, Mar 28, 2018 at 1:52 PM Ben Amick 
<[email protected]<mailto:[email protected]>> wrote:
Does anyone know of any tools, either inside the cisco product or ELM, or low 
cost external tools, that will enable any sort of alerting for capacity 
management ahead of time? I know CUCM and CUC will both pop the alert at the 
top of the header when you exceed your licensing, and UCCX will deny logins, 
and QM will stop allowing you to enable users or will send alerts if a 
recording server is going high on capacity, but I’ve been asked to provide 
proactive alerting that lets us know when we have <X licenses free in any of 
our systems, and provide a monthly report of such

Ben Amick
Unified Communications Analyst


Disclaimer: The information contained in this transmission and any attachments 
may contain privileged and confidential information including patient 
information protected by federal and state privacy laws. This transmission is 
sent for the sole use of the intended recipient. If you are not the intended 
recipient, please immediately (1) notify the sender via reply email; (2) do not 
open or read the message or any attachments; and (3) delete this message and 
any attachments. The review, dissemination, distribution, or duplication of 
this transmission by anyone other than the intended recipient is strictly 
prohibited.
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to