Description of Cisco configuration files

The Cisco Enablement Pack is controlled by two configuration files:

• The cisco.conf file defines internal drivers (probes) to discover CUCM services and their relationships. In general, the cisco.conf file does not need to be configured.

  On rare occasions, the cisco.conf file can be configured when network latency prevents full discovery and the default timeout needs to be overridden. In addition, very old versions of CCME can be discovered by modifying a parameter as described in “Configuring discovery of older versions of Call Manager Express” on page 22.

• The cert-cisco.conf file defines key, critical, and non-critical processes designated for discovery.

  To customize, you can open the cert-cisco.conf file with the sm_edit utility and modify the lists of processes designated for discovery. In general, however, because the probes have been fully tested and optimized using the default configuration, the recommended guideline is to accept the default lists of processes.

  The probes that discover Cisco applications contain key, critical, and non-critical process designations. At a high level, the CUCM suite is supported, including the following applications:

  • Call Manager (CUCM)—Publisher and subscribers

  • Call Manager Express Emergency Responder (CER)

  • Customer Response Application (CRA)

  • Unity and Unity Express

  • Work Flow Manager

  • Quality Manager

  • Email-Web Integration

  • Nuance RealSpeak

  • OpenSpeech Recognizer

  • Unity Connection

  • Unified Presence

  • Unified Contact Center Enterprise (UCCE)

  • Unified Contact Center Express (UCCX)

    You can easily add more applications by using the same technique provided in the cert-cisco file.

    The VMware Smart Assurance VoIP Management Suite Certification Framework Technical Notes provides complete information about the cert-cisco.conf file.