What firewall settings are required for Voxbi.team to work properly?
To ensure Voxbi functions correctly, you need to open specific ports between the client’s PC and the destinations.
Required general ports
Port | Destination | Purpose |
443 (tcp) | voxbi.team | Voxbi client webpage |
443 (tcp) | hpp.mixvoip.com | Voxbi client API |
443 (tcp) | cdrs.voxbi.com | Voxbi call history API |
443 (tcp) | api-tempus.voxbi.com | Voxbi client Tempus API |
443 (tcp) | cdn.srv.whereby.com | Voxbi client embedded Whereby conferencing |
443 (tcp) | $instance.mixvoip.org | Tempus HR module admin web interface |
123 (udp, tcp) | ntp.mixvoip.com | Network Time Protocol |
3478 – 3479 (udp) | stun.mixvoip.com | NAT Negotiation |
Also required, the destination domain depends on your PBX version
Port | Destination (PBX 2.0) | Destination (PBX 1.x) | Purpose |
80, 443 (tcp) | $instance.voxbi.cloud | $instance.mixpbx.net | Phone Settings |
5060 (udp, tcp) | $instance.voxbi.cloud | $instance.mixpbx.net | Call Signaling (PBX) |
5061 (tcp) | $instance.voxbi.cloud | $instance.mixpbx.net | SIP TLS |
5000 – 50000 (udp) | $instance.voxbi.cloud | $instance.mixpbx.net | RTP (Voice Communication) |
8088 – 8089 (tcp) | $instance.voxbi.cloud | $instance.mixpbx.net | WebRTC Signaling |
Make sure to replace $instance with the proper PBX instance name. If you have a PBX installed on-site, the $instance name resolution will depend on your DNS configuration.
Telephony
SIP Trunk
Call rates
Phone numbers
Mobile
Hardware
Desk phones
Headsets
Wireless phones
Conference systems
Switches and Wi-Fi
Routers & Firewalls
Doorbells & Intercoms
All products
Cloud PBX
Voxbi Cloud PBX
Features
Microsoft Teams
Integrations
Tempus
Pricing
Downloads
Insights
3CX Innovaphone
Wildix
Emios
All Insights
Connectivity
Internet in Luxembourg
Internet in Belgium
Internet in France
Internet in Germany
Internet add-ons
Mobile connectivity
Service Level Agreements
Network and IT
Co-managed LAN
IT services
Cybersecurity
IPTV
Mixvoip
Contact us
About us
Events
Career
Support
Maintenance updates
Newsletter
Resources
Blog
Certification levels
Partner program
Our accreditations
FAQs