| Scroll export button | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
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. Updated: May 2024 Permalink: https://wildix.atlassian.net/wiki/x/NhXOAQ |
| Table of Contents |
|---|
Cloud PBX
...
Access to external servers:
- wmp.wildix.com, 443 (outbound, TCP)
- pbx-api.wildix.com, 443 (outbound, TCP)
Upgrade
Access to external servers:
- WMS-5.04 and WMS-6.xx
- wmp.wildix.com + packages.wildix.com, 443 (outbound, TCP)
- WMS-5.01-5.03
- wmp.wildix.com + aptly.wildix.com, 443 (outbound, TCP)
- WMS-4.xx
- wmp.wildix.com + apt.wildix.com, 443 (outbound, TCP)
Upgrade of devices
Starting from WMS 6.05, in case of Hardware or Virtual PBX:
...
Access to external server:
- ssl.wildix.com, 443 (outbound, TCP)
Text-to-speech
Access to external servers:
...
Access to external servers:
- operator-01-f.wildix.com 3.123.221.55
- operator-02-f.wildix.com 18.158.245.207
- operator-03-f.wildix.com 18.195.104.178
Port:
- incoming: TCP 443, TCP 5061 or another custom secure port
- RTP: e.g. UDP 10000-15000 (check SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs RTP page)
...
- classound-namelookup.wildix.com, 443 (outbound, TCP) - starting from WMS 6.02.20230201.1 or higher (available for the USA and Canada)
...
Access to external servers:
- api.wildix.com, 443 (outbound, TCP)
Remote provisioning of devices
...
Access to external servers:
- addons.wildix.com
Cloud
...
-stored group chats
Access to external servers:
- authchats1.meet.wildix.com, 443 or another custom secure port (inbound, outbound, TCP)
cognito-idp.eu-central-1.amazonaws.com, 443 or another custom secure port (inbound, outbound, TCP)
- cognito-identity.eu-central-1.amazonaws.com, 443 or another custom secure port (inbound,
- chats2.meet.wildix.com
Port:
- outgoing: TCP 5269
- incoming: TCP 443 or another custom secure port
Geolocation services
- Maps in Collaboration are available only via .*wildixin.com domain
File / image sharing
Access to external servers(both PBX and Client):
- auth.wildix.com, 443 (outbound, TCP)
- stsfs.amazonawswildix.com, 443 or another custom secure port (inbound, 443 (outbound, TCP)
- 3.65.155.111, 443 or another custom secure port (inbound, outbound, TCP)
- 3.65.155.145, 443 or another custom secure port (inbound, outbound, TCP)
kinesis.eu-central-1.amazonaws.com, 443 or another custom secure port (inbound, outbound, TCP)
...
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)
Cloud analytics in Collaboration and x-bees
Access to external servers:
- chats1.meetauth.wildix.com
- chats2.meet.wildix.com
Port:
- outgoing: TCP 5269
- incoming: TCP 443 or another custom secure port
Geolocation services
- Maps in Collaboration are available only via .*wildixin.com domain
File / image sharing
Access to external servers(both PBX and Client):
- auth.wildix.com, 443 (, 443 or another custom secure port (inbound, outbound, TCP)fs.wildix
cognito-idp.eu-central-1.amazonaws.com,
443 (443 or another custom secure port (inbound, outbound, TCP)
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
cognito-identity.eu-central-1.amazonaws.com, 443 or another custom secure port (inbound, outbound, TCP)
sts.amazonaws.com, 443 or another custom secure port (inbound, outbound, TCP)
- 3.65.155.111, 443 or another custom secure port (inbound, outbound, TCP)
- 3.65.155.145, 443 or another custom secure port (inbound, outbound, TCP)
kinesis.eu-central-1.amazonaws.com, 443 or another custom secure port (inbound, outbound, TCP)
WebRTC Kite service
Access to external servers:
- kite.wildix.com, 443 TCP, 5061 TCP, 10000-1500 UDP (outbound)
- ws2sip.wildix.com, 443 TCP or another custom secure port, 10000-15000 UDP (inbound)
iOS/Android
- SIP: TCP 443
- XMPP: TCP 443
- Configuration: TCP 443
...
Access to external servers (both PBX and Client):
- vnc.wildix.com, 443 (outbound, TCP)
- kite.wildix.com, 443 (outbound, TCP)
Screen sharing
Access to external servers (both PBX and Client):
- vnc.wildix.com, 443 (outbound, TCP)
- kite.wildix.com, 443 (outbound, TCP)
Other Services
SMS sending with remote GSM gateway
...
- WMS 6.xx PBXs
- pbxlogging6-<minor version>.wildix.com (dynamic IP list), 20514 (outbound, TCP)
- WMS 5.02+ PBXs
- pbxlogging5-<minor version>.wildix.com (dynamic IP list), 20514 (outbound, TCP)
- WMS 4.0 PBXs
- pbxlogging4-<minor version>.wildix.com (dynamic IP list), 514 (outbound, UDP)
Zabbix monitoring
- TCP 8099 for IP 63.32.222.64
- TCP 10050 for local Zabbix
...
- WMS-4.xx PBXs
- vpn4.wildix.com, 443 (outbound, TCP)
x-bees
x-bees also requires the following external servers to be open on your router/ firewall:
...
transcribe.eu-central-1.amazonaws.com, 443 or another custom secure port (inbound, outbound, TCP)
Firewall Checker
Check open ports
Access to external servers:
- api.wildix.com, 443 (outbound, TCP)
- api.wildix.com, 443 or another custom secure port (inbound, TCP)
Check External IP
Access to external servers:
- checkip.wildix.com, 80 and 443 (outbound, TCP)
| Macrosuite divider macro | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...