Skip to main content
Your IT team must prepare each office network before Peerlogic Voice is installed. Peerlogic does not make direct changes to your routers, firewalls, or internet service.
Network changes can interrupt internet and phone service. Your IT team should review, apply, and test every change.

​
Run the network test

  1. Run the Peerlogic network test from each office location that will use Peerlogic Voice.
  2. Capture screenshots of the complete results, including the advanced view.
  3. Send the screenshots to support@peerlogic.com.
The network-test link downloads a Windows executable. Ask your IT team to run and review the tool according to your organization’s software policies.

​
Core network requirements

​
Use IPv4

Peerlogic Voice supports IPv4. IPv6 is not supported.

​
Remove double NAT

A double network address translation (NAT) configuration commonly occurs when two routers operate on the same local network. Disable routing on the secondary device or place the appropriate gateway in bridge mode. Restart the affected network equipment after changing NAT or bridge-mode settings.

​
Disable SIP ALG

Disable SIP Application Layer Gateway (ALG) on routers and firewalls that process Peerlogic Voice traffic. Restart the affected network equipment after disabling SIP ALG.

​
Allow local traffic

Allow traffic between office computers and desk phones. Do not place Peerlogic Voice devices on an isolated guest network when a workstation must communicate with a phone.

​
Peerlogic Voice firewall requirements

Allow the following Peerlogic Voice IP addresses through your firewall or access control list. Allow the following ports for Peerlogic Voice traffic. If your practice uses Yealink devices, allow bidirectional traffic between the devices and Yealink Management Cloud Service (YMCS).

​
Email requirements

Allow email from *.peerlogic.com and noreply@peerlogic.com. See Allow Peerlogic email through your filters for additional email-delivery guidance.

​
Internet connections and failover

  • Starlink: Peerlogic does not guarantee service quality over Starlink. A third-party router managed by your IT team may improve compatibility, but satellite latency and instability can cause inconsistent audio or dropped calls.
  • Cellular office networks: Peerlogic does not support cellular office networks such as T-Mobile or Verizon fixed-wireless service. Their provider-managed routers may prevent VoIP optimization and cause registration or call-quality problems.
  • ISP failover: Peerlogic Voice can operate with ISP failover. Your IT team owns the failover configuration and must verify that it preserves the IPv4, NAT, firewall, and voice-quality requirements on this page.

​
Unsupported firewalls and gateways

Peerlogic does not support the following devices:
  • Apple AirPort Extreme
  • Belkin routers and gateways
  • Linksys BEFSR41 and BEFSR81
  • Linksys WRT120N and WRT180 VPN firewall
  • Cisco DPC3939B and DPC3941B gateways
  • Actiontec PK5000 gateway
  • Motorola Surfboard DOCSIS gateway
  • Time Warner UBEE DOCSIS gateway
The Cisco, Actiontec, Motorola, and Time Warner gateways above may be usable when your internet provider places them in bridge mode and your IT team installs a supported router.
If you use a SonicWall firewall, tell your Peerlogic Implementation Manager before installation so the required compatibility settings can be reviewed.
For a Comcast Business router, ask Comcast Support to use standard bridge mode instead of the default hybrid bridge mode.

​
Verify the network

After your IT team applies the requirements:
  1. Confirm that each phone registers after a restart.
  2. Place inbound and outbound test calls.
  3. Confirm that audio works in both directions.
  4. Check for delay, distortion, or dropped calls.
  5. Repeat the test at every office location and over each configured failover connection.
If a test fails, record the office location, device model, time, call direction, and symptoms before contacting Peerlogic Support. Do not include patient information.