This article lists everything needed to deploy and connect VoIP Detective: the supported virtual environments, the resources the virtual machine needs, and the network ports required to receive call data from each supported platform.
Supported Platforms
VoIP Detective is a virtual appliance. It runs on any one of the following virtual environments:
Virtual Environment | Minimum Version |
VMware ESXi | 5.5+ |
VMware Workstation | 15+ |
VMware Player | Supported |
Microsoft Hyper-V | Hyper-V 10+ / Windows Server 2016+ |
Proxmox | Supported |
Nutanix | Supported |
Linux KVM | Supported |
Phone system: Cisco Unified Communications Manager 8 or later. (Webex Calling, Microsoft Teams, and Cisco CUBE are also supported as call data sources – see Connectivity below.)
Virtual Machine Requirements
Resource | Requirement |
vCPU | 2 |
Memory | 16 GB |
Storage | 1 TB (may be thin provisioned) |
Internet access | Outbound access to *.voipdetective.com (see Connectivity). PRO users may bypass this with an offline license. |
ℹ️ Tip: Storage is the resource most affected by call volume and retention. Thin provisioning lets you start small and grow as your call database fills up.
Connectivity
Open the following ports so VoIP Detective can receive call data. Each platform is independent – you only need the ports for the platforms you use.
Cisco Call Manager (CUCM)
Port | Direction | Purpose |
22 | CUCM → VoIP Detective | VoIP Detective has a built-in SFTP server. Once you add it as a “billing server” in CUCM, CUCM pushes CDR/CMR files to it over port 22 (SFTP). |
8443 | VoIP Detective → CUCM | Optional. Read-only AXL access used to import end-user names and device data. |
Cisco CUBE
Configure CUBE (Cisco Unified Border Element) to send its CDRs to VoIP Detective over FTP or SFTP (port 22 for SFTP).
Microsoft Teams
Teams reporting requires outbound access (port 443) from VoIP Detective to retrieve call records:
Purpose | Endpoint |
Call data (Microsoft Graph) | https://graph.microsoft.com |
OAuth / authentication | https://login.microsoftonline.com/ |
Webex Calling
Webex Calling reporting requires outbound access (port 443) from VoIP Detective to your Webex region. The endpoint depends on your location:
Region | Endpoint |
Token exchange (all regions) | oauth.voipdetective.com |
United States | analytics-calling.webexapis.com |
European Union | analytics-calling-eu.webexapis.com |
Asia Pacific | analytics-calling-in.webexapis.com |
Government | analytics-calling-gov.webexapis.com |
Outbound – Product Services
VoIP Detective Free contacts the following over port 443. PRO users can remove this requirement with an offline license.
Destination | Purpose | Port |
www.voipdetective.com | Tests whether internet access is working and notifies the administrator when an update is available. | 443 |
update.voipdetective.com | Provides upgrade details and delivers upgrades, applied from the GUI. | 443 |
license.voipdetective.com | Contacted about every 7 days to verify the license is still active. | 443 |
Outbound – Optional Services
- SMTP server – to send scheduled reports and alerts by email.
- Microsoft 365 OAuth2 - for users of Microsoft 365 email.
- Linux OS updates – if you update the underlying Alma Linux OS from the command line, the yum package manager needs access to standard Linux repositories over ports 80 and 443.
Important: VoIP Detective is not designed to be internet-facing. Ensure it is not reachable directly from the internet and is not placed in your organization’s DMZ.
Related Articles
- Overview of VoIP Detective
- Data Privacy and Connectivity – full list of outbound domains and security options.
- Installation guides for VMware, Hyper-V, Proxmox, Nutanix, and Linux KVM.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article