Single-site VoIP deployment discovered by VoIP Availability Manager—example is an example of a single-site VoIP deployment that VoIP Availability Manager, working with IP Availability Manager, is able to discover, monitor and analyze. VoIP Availability Manager is capable of managing many other types of VoIP deployments, including:

  • Multi-site VoIP deployments with centralized call processing

  • Multi-site VoIP deployments with distributed call processing

    A VoIP deployment contains many hardware entities, including call servers and media servers, media gateways, media modules, circuit packs, telephones including speakerphones, and Ethernet switches. Some host servers, such as the call server providing the Call Manager service, contain applications for database management, device initialization, device control, voice mail, and software conferencing. While some host servers, called dedicated servers, run only a single application.

    Upon importing device topology from IP Availability Manager, VoIP Availability Manager performs its own discovery on the devices to gather critical VoIP application information. It instantiates this information as logical topology objects in its repository, and maps the logical topology to the underlying physical transport topology discovered by IP Availability Manager.


    VoIP Availability Manager discovery automatically occurs after IP Availability Manager discovery has completed. To ensure topology consistency between VoIP Availability Manager and IP Availability Manager, you should never invoke discovery for VoIP Availability Manager from the Domain Manager Administration Console attached to VoIP Availability Manager.

    Figure 1. Single-site VoIP deployment discovered by VoIP Availability Manager—example