Html |
---|
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script> |
Html |
---|
<div class="fb-like" data-href="https://confluence.wildix.com/x/MwOIAQ" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div> |
...
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: April 2021May 2024 Permalink: https://confluencewildix.wildixatlassian.comnet/wiki/x/MwOIAQNhXOAQ |
Table of Contents |
---|
Cloud PBX
Outgoing ports:
- Outgoing traffic towards Cloud PBX to the Internet is not limited: any port from 1-65536 range
Incoming ports:
- tcp:TCP 80 HTTP
- tcp: 443 TCP 443 HTTPS
- udp: 1194, 1028 N2N
- tcp: 389 LDAP
- all types ICMP
- tcp: TCP 5060-5061 SIP
- udpUDP: 5060 SIP
- udp: 10000UDP 10000-59999 RTP
- udp: 123 UDP 123 NTP
- tcp: 5222TCP 5222-5223, 5269, 5280 ejabberd
- tcp: 7008 TCP 7008 smsd
- tcpTCP/ udp: UDP 3478 turn
- tcp: 4222 TCP 4222 gnats
- tcp: 10050 TCP 10050 zabbix
- tcpTCP/ udp: UDP 514 rsyslog
Virtualization
...
Access to external servers:
- addons.wildix.com (also for HW / VM PBXs)
License activation / check
Access to external servers:
- wmp.wildix.com
Port:
- outgoing tcp:443
- incoming: tcp:443 or custom secure port, 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
Port:
- outgoing tcp:443
- incoming: tcp:443 or custom secure port
- , 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 servers:
...
- vpn3firmwares-cdn.wildix.com - used by WMS-3.xx PBXs
- vpn4.wildix.com - used by WMS-4.xx PBXs
Port:
- outgoing tcp:443
- incoming: tcp:443 or custom secure port
- , 443 (outbound, TCP)
- wps.wildix.com, 443 (outbound, TCP)
WMS network
- Enable the port TCP 443 (or another custom secure port) and UDP 1194 on the side of the Server PBX
Access to WMS network nodes between PBXs.
Port:
- incoming: UDP 1194
Note |
---|
Starting from WMS v 5.03.20210826.1, the following ports must be opened for the correct work of calls between nodes: 443 (or custom secure port) + RTP ports (on SIP-RTP page). |
Access to external servers:
- pbxlogging4-03turn.wildix.com - used by WMS 4.0 PBXspbxlogging5-02(to find a PBX public IP address for WMS Network correct functioning)
SSL certificate renew
Access to external server:
- ssl.wildix.com - used by WMS 5.0 PBXs
Port:
- outgoing: udp:514 - prior to WMS 5.02
- outgoing: tcp:20514 - starting from WMS 5.02
SIP Trunks registration
Outgoing:
- 5060 UDP , 443 (outbound, TCP)
Text-to-speech
Access to external servers:
- tts.wildix.com, 443 (outbound, TCP)
SIP Trunk / VoIP Provider
SIP Trunks registration
- "PBX_NAME".wildixin.com, 5060 or another custom port specified in trunk settings
...
- settings (outbound, UDP)
CLASSOUND
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:
- outgoing: tcp:443
- incoming: tcp:TCP 443, TCP 5061 or another custom secure port
Remote provisioning of devices
Incoming:
- 443 TCP (default) or another external secure port (RTP: e.g. UDP 10000-15000 (check SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs );
- 5060 UDP – 5061 TCP for SIP registration
- RTP: from 10000 to 15000 (SIP- RTP page)
...
Contact lookup during incoming/outgoing CLASSOUND calls
Access to external servers:
...
- apiclassound-namelookup.wildix.com
Port:
- outgoing: tcp:443
- incoming: tcp:443 or custom secure port
- , 443 (outbound, TCP) - starting from WMS 6.02.20230201.1 or higher (available for the USA and Canada)
Remote Wildix IP Phones
Devices sync with portal
Access to external servers:
- checkipapi.wildix.com
Port:
- outgoing: tcp:443, tcp:80
WMS network
- Enable the port 443 TCP (or another custom secure port) and 1194 UDP on the side of the Server PBX
Access to WMS network nodes between PBXes.
Port:
- incoming: udp 1194
Access to external servers:
- turn.wildix.com (to find a PBX public IP address for WMS Network correct functioning) , 443 (outbound, TCP)
Remote provisioning of devices
Incoming:
- TCP 443 (default) or another external secure port (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs)
- UDP 5060 – TCP 5061 for SIP registration
- RTP:
- VM/ HW PBX: e.g. UDP 10000 - 15000 (Note: The range depends on the number and type of licenses on the PBX; check SIP-RTP page for details)
- Cloud PBX: UDP 10000-59999
Multicast paging uses
- IP 224.0.0.1 or IP 239.1.1.10 (2N support)
- Ports 9000-9009
SMS sending with remote GSM gateway
- Open the incoming port 7008 TCP on the side of the PBX
WIService
(Wildix Integration Service, used by CDR-View, Screen Sharing, 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)
Contact look up during incoming/outgoing calls
Access to external servers:
- namelookup.wildix.com
Port:
- outgoing: tcp:443
Collaboration and Web Phone
...
Vision/ SuperVision
- SIP: TCP 443
- XMPP: TCP 443
- 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
- RTP:
- VM/ HW PBX: e.g. UDP 10000 - 15000 (Note: The range depends on the number and type of licenses on the PBX; check SIP-RTP page for details)
- Cloud PBX: UDP 10000-59999
Access to external server for upgrade of firmware/ applications:
- firmwares.wildix.com
Remote Collaboration Apps
Collaboration and Web Phone
- TCP 443 (default) or another external secure port (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs);
- RTP: from 10000 to 15000 (:
- VM/ HW PBX: e.g. UDP 10000 - 15000 (Note: The range depends on the number and type of licenses on the PBX; check SIP-RTP page for details)
- Cloud PBX: UDP 10000-59999
Access to external servers:
- addons.wildix.com
Cloud-stored group chats
Access to external servers:
- chats1.meet.wildix.com
- chats2.meet.wildix.com
Port:
- outgoing: tcp:TCP 5269
- incoming: tcp: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):
- Authauth.wildix.com, 443 (outbound, TCP)
- fs.wildix.com
Port:
- outgoing: tcp:443
Screen sharing
Access to external servers (both PBX and Client):
- vnc.wildix.com
- kite.wildix.com
Port:
- outgoing: tcp:443, 443 (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:
- auth.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, 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: 443/TLSTCP 443
- XMPP: 443 TCP 443
- Configuration: 443 TCP Custom 443
Incoming:
- TCP 443 or another external secure port (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs): add
- Add the port manually on the app login page: Account > Domain, example: pbx.wildixin.com:443 (for iOS works only with public IP)
- RTP: from 10000 to 15000 (:
- VM/ HW PBX: e.g. UDP 10000 - 15000 (Note: The range depends on the number and type of licenses on the PBX; check SIP-RTP page for details)
- Cloud PBX: UDP 10000-59999
Outgoing:
For push notifications: 443
TLSTCP to
pushnotifications.wildix.com; PBX must be connected to the internet and be able to communicate
with pushwith notifications.wildix.com server
- Android: a direct, unproxied connection to the Google Cloud Messaging server on these ports: TCP 5228; TCP 5229; TCP 5230 and TCP 443
- iOS: a direct, unproxied connection to the Apple Push Notification servers from smartphone is necessary on ports TCP 5223; TCP 2195; TCP 2196; TCP 443
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
Vision
Access to external server for upgrade of firmware/ applications:
- firmwares
Note Note: Starting from WMS 6.06.20240425.1, the service used for sending push notifications was changed from push.wildix.com
WebRTC Kite service
Access to external servers:
- kite
ws2sipto notifications.wildix.com
. Make sure to use notifications.wildix.com
Port:
- outgoing: tcp:443, tcp:5061, udp:10000-15000
- incoming: tcp:443 or custom secure port, udp:10000-15000
for WMS 6.06.20240425.1 and higher.
Video Conference
WebRTC Wizyconf videoconference
Access to external servers (both on the PBX's and on the Client's side):
- conference.wildix.com
- videobridge.wildix.com - no longer needed after May 31, 2021
- videobridge-it.wildix.com - no longer needed after May 31, 2021
- videobridge-it2.wildix.com - no longer needed after May 31, 2021
- videobridge-usa.wildix.com - no longer needed after May 31, 2021
- videobridge-usa2.wildix.com - no longer needed after May 31, 2021
- videobridge-de.wildix.com
- File / image sharing
- Kite (sip calls)
...
- - no longer needed after May 31, 2021
Ports to open (both on the PBX's and on the Client's side):
- outgoing: tcp:TCP 443, udp: 10000-15000TCP 4443, UDP 10000 (to any remote address)
Note: TCP 4443 and UDP 10000 need to be open on the Client's side only. - incoming: tcp:TCP 443 or custom secure port
...
- another custom secure port (from any remote address)
For support of SIP access from the PBX, enable the rules specified in this section: WebRTC Kite service.
For file/ image sharing, enable the rules specified in this section: File / image sharing.
Screen sharing
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):
- ttsvnc.wildix.com
Port:
- outgoing: tcp:443
- incoming: tcp:443 or custom secure port
Zabbix monitoring
- 8099 TCP , 443 (outbound, TCP)
- kite.wildix.com, 443 (outbound, TCP)
Other Services
SMS sending with remote GSM gateway
- Open the incoming port TCP 7008 on the side of the PBX
Rsyslog
Access to external servers:
- 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 TCP for local Zabbix
...
Remote support
Access to external server:
...
servers:
...
- WMS-4.xx PBXs
- vpn4.wildix.com
Port:
- outgoing tcp:443
- , 443 (outbound, TCP)
x-bees
x-bees also requires the following external servers to be open on your router/ firewall:
- app.x-bees.com
- api.x-bees.com
- login.x-bees.com
- chat.wildix-chat.com
- avatars.wildix.com
- cognito-idp.eu-central-1.amazonaws.com
- wda.wildix.com
- wda-ws.wildix.com
- wim.wildix.com
- fs.wildix.com
Transcription
transcribe.eu-central-1.amazonaws.com, 443 or another custom secure port (inbound, outbound, TCP)
Firewall Checker
Check open ports
Access to external servers:
- operator-k1api.wildix.comoperator-k2, 443 (outbound, TCP)
- api.wildix.com
- operator-k3.wildix.com
Port:
- incoming: tcp:5061
- RTP: from 10000 to 15000 (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXsRTP page)
...
- , 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 | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Button macro | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|