# Vmware Appliance Quick Start

Every new release is automatically built based on Red Hat CentOS 9 Stream. All security updates are applied automatically on each build, and you can update any package as needed using the norma Red Hat tools like dnf update.

Download the OVA Appliance Now (opens new window) and import to Vmware ESXi.

RHEL and Alternatives

  • You can provide your own RHEL 9.x server and license, and run a script to install the Call Telemetry Appliance. Reach out to support for information.
  • AlmaLinux 9.3 is in beta testing as an appliance model.

# Vmware Requirements:

  • ESXi 6.5 or higher
  • 2 vCPU
  • 4GB RAM
  • 60GB Disk Space

# Importing the OVA to Vmware

Choose Thick mode for disk provisioning if prompted. Choose Bridged Networking mode for the network adapter.

# Networking Requirements

Many users install the appliance on the same subnet as their voice or Cisco Callmanager servers. The basic requirement is that the appliance have communication with the Cisco Callmanagers.

Ports used if you are planning using Firewalls between systems, please review the requirmenents below.

From Call Telemetry to Voice networks:

  • TCP 8443 to Callmanager
  • TCP 80 to Cisco IP Phones

From Voice Networks to Call Telemetry:

  • TCP 22 from Callamanger
  • TCP 2222 from external SSH management
  • TCP 80 for CURRI API
  • TCP 443 for HTTPS management

# Networking and Air Gapped Offline support

The appliance is self-contained and does not require internet access to operate. It can be used in an air-gapped or secure environment with no outside access.

# Capacity and Sizing

The default OVA is sized with capacity for most installations, up to about 20,000 Cisco IP Phones, and 200 inspection of constant load of 200 calls per second (12,000 calls per minute). More information on Capacity planning and Performance is available if you are planning a for a larger deployment.

# OS Defaults

IP: DHCP
Username: calltelemetry
Password: calltelemetry
(please change the password)

# First Bootup Steps

# Configure Networking - Static or DHCP IP Address

The appliance boots up as DHCP by default, and tries to obtain an IP address from your network. To assign as static IP, login and use the CentOS utility 'nmtui' - make sure run it as 'sudo nmtui' to get root permissions.

  • Click Edit Connection
  • Choose Eth0
  • Scroll to IPV4 Config
  • Choose Manual
  • Choose OK
  • Choose Back
  • Activate Eth0
  • Exit
  • Reboot - 'sudo reboot' to refresh the discovered IP address shown on the web page and banners.
Screen of IP Networking configuration :::

The appliance displays it's discovered IP (if it gets DHCP) on the console on bootup. Just open a web browser to https://IPADDRESS and create a new login.

If you don't see a Web Page, give it just a moment, but try these:

# Accessing the SSH Management Console

Port 22 is dedicated for SFTP only, no user can login to it.

To access the normal SSH Management of the box use port 2222.

WARNING

Please change the password for your Call Telemetry appliance after login. The command is standard linux:

passwd

# Integration with Cisco Callmanager

To get the most out of Call Telemetry, you will need to integrate one or more Cisco Callmanagers. These are the recommended integrations:

Once completed, you can start configuring some features. Here are some quick links to getting started guides for some of the features

# Next Step - Learn about Call Policy Design

Last Updated: 3/8/2024, 7:02:40 PM