Skip to end of banner
Go to start of banner

Ports used by Wildix services

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

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 2021

Permalink: https://confluence.wildix.com/x/MwOIAQ


Cloud PBX

Outgoing ports:

  • Outgoing traffic towards Cloud PBX is not limited: any port from 1-65536 range

Incoming ports:

  • tcp:80 HTTP
  • tcp: 443 HTTPS
  • udp: 1194, 1028 N2N
  • tcp: 389 LDAP
  • all types ICMP
  • tcp: 5060-5061 SIP
  • udp: 5060 SIP
  • udp: 10000-59999 RTP
  • udp: 123 NTP
  • tcp: 5222-5223, 5269, 5280 ejabberd
  • tcp: 7008 smsd
  • tcp/ udp: 3478 turn
  • tcp: 4222 gnats
  • tcp: 10050 zabbix
  • tcp/ udp: 514 rsyslog

Virtualization

License activation / check

Access to external servers:

  • wmp.wildix.com

Port:

  • outgoing tcp:443
  • incoming: tcp:443 or custom secure port

Upgrade

Access to external servers:

  • wmp.wildix.com

Port:

  • outgoing tcp:443
  • incoming: tcp:443 or custom secure port

Remote support 

Access to external servers:

  • vpn3.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

Rsyslog

Access to external servers:

  • pbxlogging4-03.wildix.com - used by WMS 4.0 PBXs
  • pbxlogging5-02.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 or another custom port specified in trunk settings

Devices sync with portal

Access to external servers:

  • api.wildix.com

Port:

  • outgoing: tcp:443
  • incoming: tcp:443 or custom secure port

Remote provisioning of devices

Incoming:

  • 443 TCP (default) or another external secure port (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)

Check open ports

Access to external servers:

  • api.wildix.com

Port:

  • outgoing: tcp:443
  • incoming: tcp:443 or custom secure port

Check External IP

Access to external servers:

  • checkip.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) 

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

  • 443 TCP (default) or another external secure port (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs);
  • RTP: from 10000 to 15000 (SIP-RTP page)

Cloud-stored group chats 

Access to external servers:

  • chats1.meet.wildix.com
  • chats2.meet.wildix.com 

Port:

  • outgoing: tcp:5269
  • incoming: tcp:443 or 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
  • 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

iOS/Android

  • SIP:  443/TLS
  • XMPP: 443 TCP
  • Configuration: 443 TCP
  • Custom secure port (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXs): add 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 (SIP-RTP page)
  • For push notifications: 443 TLS to push.wildix.com; PBX must be connected to the internet and be able to communicate with push.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.wildix.com

WebRTC Kite service

Access to external servers:

  • kite.wildix.com
  • ws2sip.wildix.com

Port:

  • outgoing: tcp:443, tcp:5061, udp:10000-15000
  • incoming: tcp:443 or custom secure port, udp:10000-15000

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 - no longer needed after May 31, 2021

Ports to open:

  • outgoing: tcp:443, tcp:4443, udp:10000
  • incoming: tcp:443 or custom secure port

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

Text-to-speech

Access to external servers (both PBX):

  • tts.wildix.com

Port:

  • outgoing: tcp:443
  • incoming: tcp:443 or custom secure port

Zabbix monitoring

  • 8099 TCP for IP 63.32.222.64
  • 10050 TCP for local Zabbix

SSL certificate renew

Access to external server: 

  • ssl.wildix.com

Port:

  • outgoing tcp:443 

CLASSOUND

Access to external servers:

  • operator-k1.wildix.com
  • operator-k2.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)


  • No labels