⚠️ Network Test Requirement
IMPORTANT: To ensure optimal network performance for your VoIP services, please run the network test tool available at https://www.peerlogic.com/networktest. After completing the test, please take screenshots of the results, including the advanced view, and send them to support@peerlogic.com.
⚙️ Essential Network Configurations
To prevent common VoIP issues like dropped calls, poor call quality, audio delays, and phone disconnections, please implement the following:
-
Remove Double NATs: A double Network Address Translation (NAT) typically occurs when two routers are on the same local network. This setup must be disabled or the secondary router configured to ‘bridge mode’. A reboot is required for this change to take effect.
-
Disable SIP ALG: If configured on your router, please disable SIP Application Layer Gateway (ALG). A reboot is also required after disabling.
✅ Allowing VoIP Traffic (Firewall/ACL Whitelist)
To ensure smooth communication for your Peerlogic phones, please whitelist the following IP addresses and allow traffic on the specified ports:
IP Addresses to Whitelist:
| IP Address | Server Location |
|---|---|
| 23.111.152.182 | Atlanta |
| 66.165.245.114 | NYC |
| 149.255.35.90 | LAX |
| 199.231.167.178 | Chicago |
| 23.29.123.118 | Dallas |
| 91.191.218.146 | Seattle |
Ports to Allow:
- Allow TCP/UDP ports 5060, 5061, and 5068 (for SIP)
- Allow TLS port 5061 (for SIP)
- Allow UDP ports 8500–59999 (for RTP)
- Allow UDP port 123 (for NTP)
- Allow TCP port 80 (for HTTP)
- Allow TCP port 2208 (for HTTP: Business Communicator)
- Allow TCP ports 443–450 (for HTTP)
- Allow TCP port 8001 (for web app)
💻 Internal Network Traffic
Please ensure traffic is allowed between office computers and desk phones. This is sometimes necessary for Peerlogic to remotely connect and directly configure phones via their IP address.
📞 Yealink YMCS (Yealink Management Cloud Service) Requirements
If the practice uses Yealink devices, you’ll need to open the following domain names, IP addresses, and ports to facilitate bidirectional traffic between YMCS and your devices. This ensures uninterrupted service and feature use.
| Service Type | IP Address | Port (TCP) |
|---|---|---|
| Web portal | 20.85.145.227 | 443 (HTTPS) |
| Device connection | 20.242.144.3 | 443 (HTTPS) |
| 20.88.189.229 | 443 (HTTPS) | |
| 20.19.104.34 | 443 (HTTPS) | |
| 20.242.144.4 | 8110 (DM protocol) | |
| 20.85.145.227 | 443 (HTTPS) | |
| 20.19.104.34 | 443 (HTTPS) | |
| 20.242.144.6 | 8110 (DM protocol), 443 (HTTPS) | |
| Update Service | 20.19.104.34 | 443 (HTTPS) |
| 20.85.145.227 | 443 (HTTPS) | |
| RPS | 20.242.144.0 | 443 (HTTPS), 5061 |
| 20.242.144.1 | 443 (HTTPS), 5061 | |
| 52.71.103.102 | 443 (HTTPS), 5061 | |
| API | 20.157.214.64 | 443 (HTTPS) |
| Remote Control | 20.242.144.2 | 9701 (TCP) |
| 20.242.144.2 | 9713-9724 (TCP) | |
| 20.242.144.2 | 9725-9736 (TCP/UDP) |
📧 Communications
For email communications, please whitelist anything from *.peerlogic.com or noreply@peerlogic.com.
If you are currently onboarding with us and have questions about these recommendations, please contact your Implementation Manager immediately. Addressing potential network issues proactively will help ensure a smooth phone installation.
🚫 Services NOT Supported
- IPv6: We only support IPv4 protocols and addressing.
- Starlink: While it may work with a custom-configured third-party router (managed by your IT), we cannot guarantee proper functionality due to the satellite connection’s inherent unreliability for voice traffic. Call quality may be inconsistent, and calls may drop intermittently.
- Cellular office networks, (e.g., T-Mobile, Verizon): These networks typically use proprietary routers that cannot be optimized for VoIP. This often leads to phones failing to register or unreliable call quality with intermittent drops.
- ISP failovers: Our systems are compatible with ISP failover configurations. However, the setup and management of ISP failovers are solely owned by your IT team and fall outside of Peerlogic’s scope of support.
Unsupported Firewalls/Gateways
List of firewalls Peerlogic does NOT support*:
- Apple Airport Xtreme
- Belkin (Any)
- Linksys BEFSR41/81
- Linksys WRT120N WRT180 VPN firewall
- Cisco DPC3939B and DPC3941B Gateway (Modem/Router) *Capable of being bridged
- Actiontec PK5000 Gateway (Modem/Router) *Capable of being bridged
- Motorola Surfboard DOCSIS Gateway (Modem/Router) *Capable of being bridged
- Time Warner UBEE DOCSIS Gateway (Modem/Router) *Capable of being bridged
*Capable of being bridged (or placed in bridge mode) means that the gateway (modem/router) can be converted into a stand-alone modem. These gateways can be converted to a stand-alone modem by enabling bridge mode. Once in bridge mode, you can use a supported router.
Important: If you have a SonicWall Firewall, please inform your Implementation Manager as soon as possible. We have specific instructions to ensure compatibility.
Important: If you have a Comcast Business Router, please reach out to Comcast Support to set bridged mode settings to standard bridged mode instead of the default hybrid bridged mode.
🔗 NexHealth Synchronizer Requirements
The NexHealth Synchronizer integrates your Practice Management System with your Peerlogic account. This enables “Aimee” and allows us to identify existing patients in your EHR. Please ensure the following are whitelisted:
Ports
- 4506, 4505, and 443
File Paths
C:\NexHealth*C:\Program Files\Salt Project\Salt*
Domain Names
*.nexhealth.info*.nexhealth-it.com*.nexhealth.comhttp://nexhealth-backend-state-cache-development-us-east-1.s3.amazonaws.com/