NETWORK CONFIGURATION STANDARDS
The following is a general guide with our recommendations and best practices for a VoIP deployment. Prior to installation, it’s essential that the site is ready and optimized for VoIP service. Our network partners can assist with all aspects of site readiness, including installation.
- Ensure there is a labeled Cat5/6 cable for each SIP device or one that can be shared with another device such as a computer or POS
- Ensure there is a location for the DECT base station for cordless devices that is centralized within the building
- If using a fax ATA, please ensure RJ11 jacks and cabling are identified and available for our device
- If integrating a paging system, please ensure appropriate copper pairs are available for use between the amplifier and network and read this article to ensure compatibility
Create a dedicated voice VLAN. Use ID 120 if available.
☐ Ensure network has packet loss < 1% and jitter < 30ms on the line
☐ We recommend your ISP connection is at least 1Mb upload
☐ We recommend a backup connection (like a 4G cellular ISP) in case of the primary line goes down
- Dedicate and label LAN ports to be used for phone devices
- If PCs are not piggybacking on phones, you should set those ports as Access ports with the voice VLAN only
- If PCs are sharing a cable with phones, make sure the ports are Trunk ports with both the voice and data VLANs enabled.
- Create a DHCP scope for phones.
- Use a /24 network to accommodate for growth.
- Most phones support LLDP and CDP by default
- Create and apply a QoS Policy that provides the highest level of priority for voice traffic. Tag all packets as EF.
- You can apply QoS to either the Voice VLAN, the voice subnet, or RTP traffic.
- Allow all traffic outbound from the voice VLAN
- Do not try to restrict outbound traffic as we may add servers, IP ranges, and providers to our cloud service at any time
- If you are forced to whitelist outbound traffic, our IPs are available here: Setting Up Your Firewall for SimpleVoIP Service
- Set up policing and/or traffic throttling policies based on the actual tested bandwidth levels at each location (upload & download).
- Without this, your QoS policy may never kick in and becomes irrelevant.
Regular operation of phones:
- On their very first boot or after a factory reset, phones look for a redirect server at *.yealink.com or *.panasonic.com or *.polycom.com
- Next, they are redirected to our configuration server to download configs and firmware at https://config.simplevoip.us
- Next, they attempt to register with our SBCs at https://*.simplevoip.us