Network and Firewall Requirements for TIPS Phones
As with all internet-connected technology, there are some requirements and best practices to be aware of when installing True IP phones.
Requirements
The phones must be able to communicate with our servers on specific ports. Please open the following ports to each of our server's IP addresses for VOIP communications.
SIP IP Addresses and Ports
Server | Alias/Registration Proxy | IP Address |
atlanta-nms.trueipsolutions.com | atlanta.outbound.tips | 72.28.115.4 |
atl2-nms.trueipsolutions.com | atl2-nms.outbound.tips | 72.28.115.5 |
charlotte-nms.trueipsolutions.com | charlotte.outbound.tips | 198.24.51.162 |
dal-nms.trueipsolutions.com | dallas.outbound.tips | 192.235.96.195 |
mcnc1-nms.trueipsolutions.com | mcnc1.outbound.tips | 152.46.24.12 |
mcnc2-nms.trueipsolutions.com | mcnc2.outbound.tips | 152.46.24.13 |
mcnc3-nms.trueipsolutions.com | mcnc3.outbound.tips | 152.46.24.14 |
mcnc4-nms.trueipsolutions.com | mcnc4.outbound.tips | 152.46.24.29 |
Purpose | Protocol | Port(s) |
SIP Registration | TCP/UDP | 5060 |
SIP TLS Registration | TCP | 5061 |
| RTP (Audio) Traffic | UDP | 5000-60000 |
| Application Communication | TCP | 8001 |
Webphone Communication | TCP | 9002 |
DISCLAIMER: SIP Trunks and other SIP Devices that are not using the Registration Proxy FQDN and are using the IP Address for Registration will not automatically fail over to an alternate server in the event the primary registration server goes down.
Provisioning and Troubleshooting Servers
True IP Solutions Provisioning Server
Server | IP Address |
ndp.trueipsolutions.com | 72.28.115.6 |
Yealink Remote Provisioning
Server | Domain Name | IP Address | Port | Description |
| Redirection Provisioning Service | rps.yealink.com rpscloud.yealink.com | 20.242.144.0 20.242.144.1 52.71.103.102 | 443 (HTTPS), 5061 (phone_rps) | Yealink redirection service, for example, redirecting to our auto-provisioning server. |
There are some requirements related to the autoprovisioning of the phones as well as some maintenance and troubleshooting functions. Our provisioning server does not require any specific ports to be opened for inbound communication, simply allow the phones to contact 72.28.115.6 for provisioning.
Yealink Management and Cloud Services
Yealink maintains several servers that we use for advanced troubleshooting, provisioning, and maintenance, please whitelist the following IP addresses and ports.
Updated 12/5/25
Server | Domain Name | IP Address | Port | Description |
| Device Connection | us-device-scheduler.ymcs.yealink.com | 20.242.144.3 | 443 (HTTPS) | Used for routing to the corresponding data center when devices are first connected. |
| us-app-scheduler.ymcs.yealink.com | 20.88.189.229 | 443 (HTTPS) | App report address | |
| redirect.ymcs.yealink.com | 20.19.104.34 | 443 (HTTPS) | Used for routing to the corresponding data center when YRC/YUC devices are first connected. | |
| us-device.ymcs.yealink.com | 20.242.144.4 | 8110 (Device Management protocol) | Device connection address | |
us-device-req.ymcs.yealink.com | 20.85.145.227 | 443 (HTTPS) | Hardware HTTP request address, used to distinguish between hardware long and short connection requests. | |
us-device-compat.ymcs.yealink.com | 20.242.144.6 | 8110 (Device Management protocol) | Compatible with MD5 certificate for device connection | |
us-device-compat-req.ymcs.yealink.com | 20.242.144.6 | 443 (HTTPS) | Compatible with MD5 certificate for device connectionf | |
Update Service | update.yealink.com | 20.19.104.34 | 443 (HTTPS) | Address for firmware detection in the device's automatic update service. |
File upload/download | yiotbackenduseast1.blob.core.windows.net | 443 (HTTPS) | File upload address. | |
cdn-us-resource.ymcs.yealink.com | 443 (HTTPS) | File download address. | ||
us-resource.ymcs.yealink.com | 20.85.145.227 | 443 (HTTPS) | Resource storage address. | |
Reserved | 20.242.144.0/29 | 443,8110,8443,8445,8446 | Reserved |
Note: Yealink advises that the above IP addresses are subject to change without warning and suggests that network administrators whitelist the domains instead. We will make every effort to keep this table updated.
Domain |
*.ymcs.yealink.com |
*.yealink.com |
Fax Servers
Server | IP Address |
faxback1.trueipsolutions.com | 198.24.51.177 |
faxback2.trueipsolutions.com | 192.235.96.196 |
Policy-Based Routing Requirements
Please be aware that our servers require that each phone is provisioned from the same public IP address as where it is registered. Some networks have policies in place to route SSL traffic through traffic inspectors, such as Zscaler, which often causes the SSL traffic to exit the network from a different interface than the SIP packets. This will cause auto-provisioning errors, specifically with our Per-Device Password security protocol. Please ensure that all HTTP and HTTPS/TLS traffic going to any of the servers listed under the "Provisioning and Troubleshooting Servers" section exits your network from the same public IP address as the SIP traffic for each phone.
MCNC Customers
If you are a customer that connects through MCNC in North Carolina, there are additional steps necessary to ensure proper auto-provisioning of your phones. MCNC applies a default policy to all of the networks they manage that sends all HTTPS traffic through an interface tied to Zscaler. This causes problems with provisioning on our end because the registration IP address is different from the provisioning IP. You will have to contact MCNC and ask for a Zscaler bypass policy for your phone subnet(s). This is a policy we have worked with MCNC to help craft that ensures the SIP registration and the provisioning traffic all come out of the same interface. It only bypasses Zscaler for traffic sent to one of our servers. To request this policy, you can email the below to your MCNC rep:
Per our hosted VOIP provider, True IP Solutions, we need to request a Zscaler bypass for SIP and SSL traffic from our VOIP phones to our provider's provisioning servers. This bypass has been previously applied in other MCNC-managed networks, see MCNC technician Campbell Baker for details. Please email support@trueipsolutions.com with any additional questions regarding the policy.
True Talk+ (Mobile Application)
If users will be using the True Talk+ mobile application on networks you control, there are several IP addresses and ports that need to be whitelisted to allow incoming calls and notifications while the application is in the background or the phone is asleep.
SIPIS Whitelist
DNS Addresses |
| all.sipis.acrobits.cz |
Ports |
443/TCP |
4998/UDP |
4998/TCP |
24998/TCP |
If your firewall can't whitelist FQDNs, you may whitelist the following IP addresses instead.*
IPv4 |
| 167.99.119.244 |
| 159.65.251.173 |
| 159.65.252.186 |
| 167.99.48.91 |
| 159.65.253.49 |
| 159.65.186.176 |
165.227.184.188 |
167.99.119.203 |
165.227.65.164 |
165.227.182.9 |
165.227.190.186 |
159.65.167.207 |
165.227.115.186 |
159.89.179.103 |
165.227.210.221 |
165.227.223.68 |
143.198.16.177 |
167.71.161.233 |
64.225.12.13 |
167.99.112.57 |
174.138.70.189 |
159.65.189.13 |
174.138.91.89 |
157.245.211.111 |
165.227.108.121 |
104.131.30.133 |
159.89.179.105 |
159.203.80.157 |
159.203.81.60 |
165.227.220.197 |
167.71.175.215 |
167.172.251.36 |
IPv6 |
2604:a880:800:a1::1777:f001 |
2604:a880:800:a1::176e:5001 |
2604:a880:800:a1::172e:b001 |
2604:a880:800:a1::176e:3001 |
2604:a880:800:a1::174f:e001 |
2604:a880:800:a1::172b:7001 |
2604:a880:800:a1::1ad:1 |
2604:a880:800:a1::1777:e001 |
2604:a880:800:10::7e:d001 |
2604:a880:800:10::292:1 |
2604:a880:800:10::5db:1 |
2604:a880:800:10::790:4001 |
2604:a880:800:10::160:1 |
2604:a880:800:10::72d:b001 |
2604:a880:800:10::69d:5001 |
2604:a880:800:10::62b:1001 |
2604:a880:800:14:0:1:c62b:c000 |
2604:a880:800:14:0:1:c62b:a000 |
2604:a880:800:14:0:1:c62b:b000 |
2604:a880:800:14:0:1:c62b:d000 |
2604:a880:800:14:0:1:c62b:e000 |
2604:a880:800:14:0:1:c62b:f000 |
2604:a880:800:14:0:1:c62c:0 |
2604:a880:800:14:0:1:c62c:1000 |
2604:a880:800:14:0:1:c62c:2000 |
2604:a880:800:14:0:1:c62c:3000 |
2604:a880:800:14:0:1:c62c:7000 |
2604:a880:800:14:0:1:c62c:9000 |
2604:a880:800:14:0:1:c62c:8000 |
2604:a880:800:14:0:1:c62c:b000 |
2604:a880:800:14:0:1:c62c:a000 |
2604:a880:800:14:0:1:c62c:c000 |
*Every effort will be made to keep this list up-to-date, however it can be verified at any time by resolving "all.sipis.acrobits.cz". Alternatively, you can use the below links to check the IP list online:
Register URL
The following address and port will also need to be whitelisted for registration purposes.
FQDN | IPv4 | IPv6 | Port |
reg.acrobits.cz | 165.227.103.7 | 2604:a880:800:a1::12f9:c001 | 443/TCP |
Notes
- Phones do use LLDP and CDP by default. If not configured on your network it may need to be disabled on the phone.
- Phones can be tagged on a specific VLAN by way of configuration overrides from our servers if needed.
- Many firewalls employ SIP ALG in some form. This is harmful to SIP traffic more often than helpful. Research your firewall to determine the best way to disable SIP ALG.
Related Articles
TIPS Fax Platform
Navigating the True IP Solutions Fax Platform This article goes over how to setup faxing within the TIPS User Portal. Office Manager is required to set faxing for their end users. Users that use MFPs or fax machines will need an ATA provided by TIPS. ...TIPS Mobile for iOS
TIPS Mobile is a SIP soft client that extends VoIP functionality provided by True IP Solutions beyond the land line or desk top. It brings features of the TIPS platform directly to end-user's mobile devices as a Unified Communications solution. With ...TIPS Webphone
Prerequisites To utilize the Webphone feature, please ensure you have the following: A microphone/headset Your TIPS Portal Username and Password - Please submit a ticket if you need us to reset/provide. Google Chrome Logging In Go to ...Video: Phones
Bulk Editing Users within TIPS Portal
We have introduced a new feature that will allow you to bulk edit multiple users within the TIPS Portal. Items that can be bulk edited are as follows - Site Department Scope (Office Manager, Call Center Agent, Call Center Supervisor) Caller ID ...