uPBX Hosted PBX Network Requirements

  • Updated

The following document outlines the requirements of the uPBX Hosted PBX platform.

It is highly recommended that your network environment meets or exceeds the below requirements in all areas listed.

Unexpected issues may arise if your network environment is not compatible with the below requirements.

Note: IPv6 is not supported by the Hosted PBX SIP servers.

Customer Environment Requirements

Customer Environment Requirements Description
IP Routing and hardware
  • Connection to an NBN n25 speed tier or better (ethernet or fibre highly recommended) Internet connection.
  • Available bandwidth of 100Kbps per concurrent call (both download and upload).
  • A TP-Link VR1600v, similar or better for 4 or less concurrent users.
  • Business-grade gateway/firewall (e.g. Draytek, Cisco, etc.) or better for 5 or more concurrent users.
  • SIP ALG protocol must be disabled.
  • QoS enabled to provide high priority Hosted PBX traffic to/from the Hosted PBX server ranges on the following IP subnets: 203.201.155.0/24, 203.22.70.0/24, 27.127.227.0/24, 27.127.233.0/24, 203.201.159.0/24 (any packet inspection should also be disabled).
  • Full IP connectivity to the Hosted PBX registration servers on the following ranges – 203.201.155.0/24, 27.127.227.0/24, 27.127.233.0/24, 203.201.159.0/24 (any packet inspection should also be disabled).
  • Full IP connectivity to the Hosted PBX provisioning servers on the following range – 203.22.70.0/24 (any packet inspection should also be disabled).
  • Full IP connectivity to the Hosted PBX softphone registration servers on the following range – 203.201.157.0/24 (any packet inspection should also be disabled).
  • A static public IP address that has been added to the Firewall Rules management section in the Hosted PBX portal. This is the public IP address used by the Hosted PBX phones.
LAN Environment
  • Cabling (Category 5e cable or better) between compatible PoE network switch and handset.
  • Connectivity to a switch (with uplink for Internet access) via an RJ-45 port using Category 5e or better cabling.
  • Power over Ethernet (PoE) allowing for a draw of 2.4W to 10.5W per phone, or individual power packs and general power outlets (GPO) per phone.
  • DHCP server with available IP addresses in a subnet with Internet connectivity.
  • DHCP Server providing option 66 and option 160 if auto-provisioning is to be used.
  • A single VLAN for both data and phones, or a voice VLAN and data VLAN both with Internet connectivity.
  • IP connectivity between PCs and phones.
  • LAN switches able to cope with a high count of Packets Per Second (50 to 100 packets per call per user).
Webhooks
  • Port 80,443 to 203.22.70.0/24 must be accessible for webhook integrations to function.
  • If using SSL, you do not require port 80.


Firewall Rules

The firewall configurations outlined in the table below are required for Hosted PBX phones to successfully register to the Hosted PBX registration servers and successfully receive/initiate inbound and outbound calls.

Note: These rules are only necessary if you are using a firewall that has been hardened to block any non-specific ports. Most small business routers will not require these ports to be whitelisted as they are open by default, so no changes are required.

Firewall Ports Network Protocol Application Protocol Description
5060 UDP & TCP SIP UAS Used for SIP signalling (Standard SIP Port, for default Internal Profile)
0 - 65536 UDP RTP / RTCP multimedia streaming Used for audio/video data in SIP and other protocols.
5061 UDP & TCP SIP Used for SIP signalling (Standard SIP Port, for default Internal Profile)
443 TCP HTTPS Webhooks, CRM Integrations
80 TCP HTTP Webhooks, CRM Integrations
22 TCP SFTP Access to stored recordings
21 TCP FTP Access to stored recordings


Auto Provisioning

Phones on the Hosted PBX platform can be enabled for auto-provisioning.
The following DHCP options will be required for auto-provisioning to work correctly:

DHCP Option Value Support Phones
66 ps.mycloudpbx.com.au Cisco & Linksys
160 ps.mycloudpbx.com.au Polycom

Additionally, for the phones to successfully download their configuration files, it is required that the following protocols be enabled for inbound and outbound communication:

Protocol Support Phones
TFTP Cisco, Linksys & Yealink
HTTP Cisco, Linksys & Yealink
FTP Polycom


YMCS Network Requirements

If you use the uPBX Hosted PBX platform, you may also want to allow access to your phones via the Yealink Cloud Management Platform, the requirements can be found here.

Related to