Ringfree Voice Protection Guide – IT Partner Deployment Guide
This guide is intended for IT partners assisting with the deployment of Ringfree Voice Protection Device, our managed SD-WAN service. It outlines supported installation scenarios, pre-deployment requirements, and best practices to ensure a smooth switchover.
Deployment Options
Ringfree supports three onsite deployment topologies. Please refer to the diagrams below for integration details.
- Option 1 (Recommended): ISP connects to both the Ringfree Voice Protection and the client firewall independently. Phones are trunked to the Ringfree Voice Protection via VLAN.
Option 1: (Preferred)
Description: VPD sits outside the firewall; phones are on VLAN separate from data.
Requirements: Managed switches, spare ISP WAN port, total of 2 Static IPs, & VLAN setup.
Advantages: Removes firewall-related issues; Ringfree can access phones via Voice Protection.
Limitations: Requires IT VLAN setup; not possible without managed switch.
IT Partner responsibilities Check list:- Obtain 2 Static IPs from ISP (1 for Firewall and 1 for VPD)
- Set up VLAN
- Option 2: (Drop-In Mode) ISP connects into the Ringfree Voice Protection Device; client firewall routes all traffic (including phones and PCs) through the Ringfree Voice Protection Device.
Option 2: Drop-In Mode
Description: VPD is inline with firewall; traffic passes transparently.
Requirements: Unmanaged switches, & x2 Static WAN IP address
Advantages: Solves ISP issues; transparent to IT partners.
Limitations: Firewall can still impact phone traffic; limited phone access.
IT Partner responsibilities Checklist:- Obtain 2 Static IPs (1 for Firewall, 1 for VPD)
- Configure Firewall
- (Special Note: We can get away with NOT obtaining a Static IP from ISP for Drop in mode.)
Option 2.1: NAT Mode
Description: The VPD is placed inline with the firewall (similar to Drop-In Mode) but acts as a NAT device. The connection scheme is Modem → VPD → Firewall.
Requirements: None, DHCP from ISP is compatible but this also works with one static IP from ISP
Advantages: Faster deployment. Does not require static IPs from ISP.
Limitations: Incompatibility with IPSec VPNs. Requires the IT Partner to access the VPD to configure necessary port forwards to Firewall.
IT Partner Responsibilities: Configure the Firewall to receive IP via DHCP from VP. Inform any necessary port forwarding on the VPD.
- Option 3: All devices connect to the Ringfree Voice Protection Device directly. No client firewall is present.
Option 3: Direct Mode
Description: VPD acts as only a device (for small offices with no firewall).
Requirements: ISP connection only. No Firewall,
LAN IP scheme, WIFI etc.
Advantages: Simplest install for small setups.
Limitations: No network control; not scalable.
Deployment Options – Pros & Cons
| Option | Pros | Cons |
|---|---|---|
| Option 1 (ISP connects to Ringfree VPD & client firewall separately) | ✅ No need to modify firewall rules or allow Ringfree access to the firewall ✅ Reduces the risk of firewall-related issues impacting service ✅ VoIP devices are logically isolated via a dedicated VLAN | ❌ Requires 2 public IP addresses ❌ VLAN configuration is required on the client switch ❌ Slightly more complex to deploy |
| Option 2 (ISP & firewall connect to Ringfree VPD; phones/PCs behind firewall) | ✅ No managed switches or VLAN configuration required ✅ Simpler for small environments with limited network segmentation needs | ❌ Ringfree cannot access phones directly, which may require screen sharing during troubleshooting and can disrupt users ❌ Still requires 2 public IP addresses |
| Option 3 (All devices connect to Ringfree VPD; no firewall) | ✅ Easiest to deploy ✅ No risk of IP conflicts or firewall misconfigurations | ❌ No firewall protection ❌ No network segmentation ❌ Only suitable for small offices or dedicated VoIP deployments |
Switchover Process Expectations
To ensure a smooth cutover and avoid service interruption, please schedule the switchover with Ringfree in advance.
- All devices are pre-configured by Ringfree.
- IT partners should never attempt configuration of the device themselves.
- Devices may arrive before final config is completed — do not plug the device in until confirmed.
Physical Connection Guidance
All devices are clearly labeled. Please connect the appropriate ports as follows:
| Label | Port Function |
|---|---|
| WAN1 | Connect to the primary internet handoff |
| LAN | Connect to client LAN or switch |
If LTE failover is enabled, the SIM is pre-installed and requires no configuration.
Failover Traffic – What We Need From You
By default, only VoIP traffic is failed over during an internet outage.
Please confirm the client’s preferences:
- Should we include only phones in LTE failover?
- Should we include additional applications (e.g., Teams, Zoom, POS, etc.)?
Warning: Failing over all traffic may result in LTE overage charges. Ringfree will only fail over requested traffic.
WAN Information Requirements
Depending on the deployment option selected, the following information may be required:
- Static public IP(s)
- Default gateway address
- Subnet mask
We will request these details at the time of deployment if needed.
Need Help?
If you have questions or need to schedule a switchover, please reach out:
- Email: support@ringfree.com
- Phone: 828-575-0030