Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



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>

...

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 May 2021

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


Table of Contents

Cloud PBX

...

  • wmp.wildix.com

Port:

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

...

  • api.wildix.com

Port:

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

Remote provisioning of devices

...

  • 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
    • VM/ HW PBX: 10000 - 15000 (SIP-RTP page)
    • Cloud PBX: 10000-59999 

Check open ports

Access to external servers:

...

Access to WMS network nodes between PBXesPBXs.

Port:

  • incoming: udp 1194

Access to external servers:

...

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

Cloud-stored group chats 

...

  • SIP:  443/TLS
  • XMPP: 443 TCP
  • Configuration: 443 TCP

Incoming:

  • 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
    • VM/ HW PBX: 10000-15000 (SIP-RTP page)
    • Cloud PBX: 10000-59999 

Outgoing:

  • 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/ SuperVision, BRI/ PRI media gateway

Access to external server for upgrade of firmware/ applications:

...

Access to external servers (both PBX):

  • tts.wildix.com

Port:

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

Zabbix monitoring

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

...

Access to external server: 

  • ssl.wildix.com

Port:

  • outgoing tcp:443 

CLASSOUND

Access to external servers:

...

  • incoming: tcp:5061
  • RTP: from 10000 to 15000 (SIP-RTP page in WMS Settings -> PBX (VM and HW PBXsRTP PBXs RTP page)


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>

...