You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Avaya Communication Manager

ACM (Avaya Communication Manager) is an open, extensible IP telephony platform that can be deployed as an IP PBX or feature server supporting a SIP-only environment, or as an evolution server supporting both SIP and non-SIP environments. Communication Manager provides 700+ PBX features, high reliability and scalability, and advanced features for productivity and mobility. Built-in capabilities include conferencing and contact center applications. A wide range of servers, gateways, and analog, digital, and IP-based communication devices is supported.

Managing ACM in real-world environments

ACM can be a challenging platform for IT support staff to monitor, manage and diagnose:

  • When monitoring via SNMP the traps generated broadly cover infrastructure related issues only. Application layer issues more often than not go unreported.
  • The SNMP traps generated only provide advice of incidents once they have occurred, meaning there is little opportunity to be proactive and prevent outages.
  • Most often problems and incidents have to be reported by end-users, after there has been significant business impact, for example loss of call recording or other aspects of integration.
  • Support teams need to enlist specialist engineering knowledge in order to correctly diagnose and remedy issues. Often these skills only reside within the Business Partner or Manufacturer which leads to delays in service restoration.
  • Even with specialist engineering resources involved there are several dependencies that relate to architecture that can vary between deployments and are often misunderstood.
  • Some incidents require access to historic logs that have either not been stored or have been overwritten.
  • Often the root cause of an issue is never truly identified due to time constraints - a simple reboot can restore the operation of mission-critical applications and the business owners put pressure on IT teams to quickly restore service.

VSM and ACM System Health

VSM collects and stores configuration, capacity and availability information relating to the consumption of all essential ACM resources. This data is mined at all levels, from infrastructure through to the ACM application layers. It stores this information for reporting, trending and analytical purposes. VSM specifically targets critical areas in ACM that indicate business-impacting issues.

  1. If any changes are made to the architecture, the dashboard will automatically reconfigure itself to measure and display critical capacity data based on the current configuration.

Items monitored include not only server processor, but also essential aspects of the configuration which have their own specific requirements and capacity limitations. This information is presented by way of several different dashboards within Service Desk.
The purpose of the dashboards is three-fold:

  • To enable IT teams to proactively identify potential issues and prevent outages.
  • To provide a real time view of overall ACM health at a glance without having to rely on end-users reporting problems.
  • In the event of a service-impacting incident to significantly reduce Mean Time to Repair (MTTR) and therefore to reduce the impact on business operations by quickly identifying the root cause.



ACM System Health Dashboard

VSM dashboards run the same diagnostic commands experienced engineers run when they are identifying problems. These commands are run on a minute to minute basis, and the results are displayed on a dashboard, color-coded to reflect solution health. Benefits include:

  • Provides a real time view of ACM health at a glance
  • Significantly reduces time to repair by pin-pointing the underlying cause of issues – the item(s) on the dashboard that are red are the most likely cause of an issue or impending issue


Server Infrastructure
Basic server performance such as processor, memory and disk utilization is displayed. Faults such as memory leaks are easily identified. The dashboard also displays the time since the last reboot, so if there is an IT policy applied to this preventative action, the status is easily seen.
Below is an example of a memory leak. When the memory being used (depicted by the blue line) reaches the maximum available (depicted by the red line) there will be consequences. Typically the application will run slowly, in some cases a restart will result.


  1. This historic report was generated within VSM Capacity Manager.  Read more about Capacity Reports here.



ACM to Media Gateway Connectivity Status
Configuration Manager constantly looks at the architecture and how it is set up to identify the current media gateway connection status. Alarms relating to media gateways as well as elements of their configuration is displayed:

  • Alarms
  • IP Address
  • Network Region
  • Current Media Gateway Controller
  • Media Gateway type


DS1 Connectivity Status
Any DS1 Hardware that is detected in the configuration is automatically checked on a 15-minute cycle for connectivity issues:

  • Errored seconds
  • Bursty errored seconds
  • Severely errored seconds
  • Unavailable failed seconds


These checks show the status of the DS1 connection to the telecommunications carrier. Errors seen here often:

  • Indicate issues with port network or media gateway synchronization
  • Are the cause of noisy calls
  • Are precursors to a trunk-group outage as they indicate a declining state of health of the connection to the central office exchange








Related Dashlets





  • No labels