CoPilot VoIP is a cloud-based business phone system that allows you to make and receive calls from anywhere in the world, as well as manage contacts, get call logs and voicemails, transfer calls, and more.
We know you are on the move, and we’re pleased to confirm that CoPilot is operable on any device with a reliable internet connection!
Let’s dive into the details of network settings.
Bandwidth calculations
To ensure the best possible voice quality, we recommend using a high-speed DSL, Broadband, or Fiber-optic connection for all services. This applies to desk phones, CoPilot App, and CRM Integrations
Calculate for each concurrent instance you plan to run:
- Voice: minimum 100kb/sec up/down
- Mobile Voice: minimum 4G (or equivalent wifi access)
- Video 1:1 Calls: minimum of 1.2-1.5Mbps up/down
- Video Meetings: minimum 1.2-1.5Mbps up and 3Mbps down
- Mobile Video (any): 4G+ (or equivalent wifi access)
Routers, switches, and firewalls
CoPilot VoIP does not require a specific brand or mode router, switch or firewall — however, to achieve the best possible quality of service, the Network hardware should have the following capabilities:
- QoS
- Bandwidth Limiting
- SNMP
We also require that the following features to be turned off for CoPilot VoIP traffic (as they can interfere with the service).
- SIP-ALG
- Deep Packet Inspection (DPI)
- Stateful Packet Inspection (SPI)
- AV Client Enforcement on any IP assigned to a phone
- Content Filtering on any IP assigned to a phone
VPN
CoPilot VoIP is not designed to function over a VPN. If your company uses a VPN, please utilize a split tunnel and direct CoPilot VoIP traffic outside of the VPN.
VLAN
A virtual LAN (VLAN) can be used to put your hard-wired phone devices into separate networks, and to manage security and routing policies separately. If you plan to deploy IP phones, they can be placed in a “voice VLAN”.
A voice VLAN is not a network requirement for CoPilot VoIP service but best practices for setting security, DHCP, routing, QoS/CoS a voice VLAN may be used.
Multiple Internet Circuits
If you are utilizing multiple internet circuits, best practice is to set them up as Primary/Failover.
FQDNs
Routing to a Fully Qualified Domain Name (FQDN), allows modern cloud networks flexibility for routing, security, system maintenance and remote device management.
CoPilot VoIP uses FQDNs for managing:
- Registrations
- SIP requests to set up a call
- Device Firmware
- Device Configurations
- Remote Devices
CoPilot VoIP recommends allowing traffic to and from each of the following FQDNs:
- copilotvoip.com
- copilotvoip.net
- *.copilotvoip.com
- *.copilotvoip.net
- *.copilot.ucaas.run
Ports & protocols
Port and protocols used by CoPilot VoIP phones and applications residing in a private network are listed below. Outbound port configurations are needed on the firewall to allow traffic to the destination ports listed in the right-hand side column of the tables. Stateful firewalls (not to be confused with stateful packet inspection!) are recommended for Dialpad deployments. For a stateful firewall, inbound port configurations are not needed as they are automatically opened as a reply to the outbound traffic.
- 5060-5062 UDP – SIP
- 20,000-40,000 UDP – RTP
- 80, 443 TCP – HTTP/HTTPS
- 9002 – TCP – websockets
- 8001 – TCP – dynamic updates
- CoPilot Meetings
- 3443 TCP & UDP
- Text To Speech Services
- 8000 TCP & UDP
- 3001 TCP & UDP
Unsupported Configurations
CoPilot VoIP does not support using our services through the following tools:
- Virtual Machines (VMs)
- Virtual Desktop Interfaces (VDIs)
- Remote Desktop Clients (RDPs)