Skip to end of metadata
Go to start of metadata


Dec 14, 2018 18:22

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.

Updated: June 2018

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


Cloud PBX

  • RTP port range on outgoing traffic towards Cloud PBX: 10000-59999

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:

  • vpn2.wildix.com
  • vpn3.wildix.com
  • vpn4.wildix.com

Port:

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

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);
  • 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

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 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
  • incoming: tcp:443 or custom secure port

Collaboration and Web Phone

  • 443 TCP (default) or another external secure port (SIP-RTP page);
  • RTP: from 10000 to 15000 (SIP-RTP page)

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
  • incoming: tcp:443 or custom secure port

Screen sharing

Access to external servers (both PBX and Client):

  • vnc.wildix.com
  • kite.wildix.com

Port:

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

iOS/Android

  • SIP:  443/TLS
  • XMPP: 443 TCP
  • Configuration: 443 TCP
  • Custom secure port (SIP-RTP page): 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 ubiconf videoconference

Access to external servers (both PBX and Client):

  • conference.wildix.com
  • videobridge.wildix.com
  • File / image sharing
  • Kite (sip calls)

Port:

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

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 52.18.154.170 
  • 10050 TCP for local Zabbix


Not finding the help you need?
Join the Facebook group to ask a question!
facebook_tech-wizards