Ports used by Wildix services
Make sure that these ports are open on your router / firewall in order to be able to access and use different Wildix services.
It is recommended to open incoming custom secure port or default 443 from outside on PBX.
Created: June 2018
Updated: August 2025
Permalink: https://wildix.atlassian.net/wiki/x/NhXOAQ
- 1 CDS
- 2 Cloud analytics in Collaboration and x-bees
- 3 Cloud PBX
- 4 Firewall Checker
- 5 NAT IP List
- 6 Remote Collaboration Apps
- 6.1 WIService
- 6.2 iOS/Android
- 7 Remote Wildix IP Phones
- 8 SIP Trunk / VoIP Provider
- 9 Video Conference
- 10 WMS Network
- 11 x-bees
- 12 Other Services
- 12.1 Cloud integrations
- 12.2 Remote support
- 12.3 Rsyslog
- 12.4 SMS sending with remote GSM gateway
- 12.5 Zabbix monitoring
CDS
Access to external servers:
Service / Purpose | Protocol | Port | Destination |
|---|---|---|---|
To upload files | TCP | 443, outbound |
|
To display CDS usage statistics in WMS interface | TCP | 443, outbound |
|
Other | TCP | 443 or another custom secure port, inbound, outbound |
|
TCP | 443 or another custom secure port, outbound |
| |
TCP | 443, outbound |
|
Cloud analytics in Collaboration and x-bees
Access to external servers:
Service / Purpose | Protocol | Port | Destination |
|---|---|---|---|
Cloud analytics (CDR-View 2.0) | TCP | 443 or another custom secure port, inbound, outbound |
|
TCP | 443, outbound |
|
Cloud PBX
Outgoing ports:
Outgoing traffic towards Cloud PBX to the Internet is not limited: any port from 1-65536 range
Incoming ports:
Service / Purpose | Protocol | Port | Destination |
|---|---|---|---|
Cloud PBX | TCP |
|
|
| UDP |
|
|
Access to external servers |
|
|
|
Also, give access to the following external servers:
Service / Purpose | Protocol | Port | Destination |
|---|---|---|---|
License activation / check | TCP | 443, outbound |
|
Authorization | TCP | 443, outbound |
|
Upgrade | TCP | 443, outbound | WMS-5.04, WMS-6.xx and WMS-7.xx:
WMS-5.01-5.03:
WMS-4.xx:
|
Upgrade of devices (starting from WMS 6.05, in case of Hardware or Virtual PBX) | TCP | 443, outbound |
|
SSL certificate renew | TCP | 443, outbound |
|
Text-to-speech | TCP | 443, outbound |
|
Speech-to-text | TCP | 443, outbound |
|
Firewall Checker
Access to external servers:
Service / Purpose | Protocol | Port | Destination |
|---|---|---|---|
Check open ports | TCP | 443, outbound |
|
TCP | 443 or another custom secure port, inbound |
| |
Check External IP | TCP | 80 and 443, outbound |
|
NAT IP List
Access to the following NAT IPs should be allowed:
Service / Purpose | Protocol | Port | NAT IP |
|---|---|---|---|
WIM | TCP | 443 or another secure port, outbound |
|
x-bees | TCP | 443 or another secure port, outbound |
|
x-hoppers | TCP | 443 or another secure port, outbound |
|
Remote Collaboration Apps
Service / Purpose | Protocol | Port | Destination |
|---|---|---|---|
Collaboration and Web Phone | TCP |
|
|
UDP |
| ||
Cloud-stored group chats | TCP |
|
|
File / image sharing (both PBX and Client) | TCP | 443, outbound |
|
Geolocation services |
|
|
|
WebRTC Kite service | TCP |
|
|
UDP | 10000-1500, outbound | ||
TCP | 443 or another custom secure port, inbound |
| |
UDP | 10000-1500, inbound |
WIService
(Wildix Integration Service, used by CDR-View, Screen Sharing, Headset Integration, Fax printer, Click2call from Windows, Popup App and other Wildix applications):
Make sure that FQDN “wildixintegration.eu” is correctly resolved with the IP: 127.0.0.1 by your DNS (on the user PC or on the router side)
iOS/Android
Service / Purpose | Protocol | Port | Destination / Notes |
|---|---|---|---|
SIP, XMPP, Configuration | TCP | 443 |
|
Incoming: | TCP | 443 or another external secure port (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs) | Add the port manually on the app login page: Account > Domain, example: pbx.wildixin.com:443 (for iOS works only with public IP) |
| UDP | 10000 - 15000 (Note: The range depends on the number and type of licenses on the PBX; check SIP-RTP page for details) |
|
| UDP | 10000-59999 |
|
Outgoing: |
|
|
|
| TCP | 443 | To notifications.wildix.com; PBX must be connected to the internet and be able to communicate with notifications.wildix.com server |
| TCP |
|
|
| TCP |
|
|
Important: use a transparent port forwarding scheme between the external port on the firewall and the external custom secure port on the PBX, example: 4443 – 4443
Note: Starting from WMS 6.06.20240425.1, the service used for sending push notifications was changed from push.wildix.com to notifications.wildix.com. Make sure to use notifications.wildix.com for WMS 6.06.20240425.1 and higher.
Remote Wildix IP Phones
Access to external servers:
Service / Purpose | Protocol | Port |
|---|