Chapter 1. Getting Started with PortSIP® PBX

1.1 What is PortSIP PBX

PortSIP PBX (also known as PortPBX, PortSIP UC Server) is a software-based Unified Communications system for Windows and Linux that works with SIP standard-based IP Phones, Softphones, SIP Trunks, and VoIP Gateways to provide a complete PBX solution – without the inflated cost and management headaches of an "antiquated" PBX. The SIP PBX supports not only all traditional PBX features but also includes many new mobility and productivity features.
Calls are sent as data packets over the computer data network instead of the traditional phone network. Phones share the network with computers so no separate phone wiring is required. With the use of a VoIP Provider, SIP Trunk, you can connect existing phone lines to the PortSIP PBX to make and receive phone calls via a regular PSTN line. You can also use a VoIP Provider, which removes the requirement for a gateway. PortSIP PBX interoperates with standard SIP softphones, IP phones or smartphones, and provides internal call switching.

1.2 Before Started

Prerequisite knowledge for Linux

Deploying PortSIP PBX in a Linux environment requires planning and knowledge of session initiation protocol (SIP) audio, video call, and presence, Instant Messaging (IM) administration. You should also have knowledge of the following Linux infrastructures:
  • CentOS 7.9 (64-bit)
  • Debian 10.x (64-bit)
  • Ubuntu 18.04 or 20.04 (64-bit)
  • Docker 20.10 or higher
  • IPv4/IPv6
  • Systemd
  • IP tables
  • Firewalld
  • UFW
This document assumes that the Linux OS is already deployed and administrators of PortSIP PBX have been allocated with the root permission to Linux.

Prerequisite knowledge for Windows

Deploying PortSIP PBX in a Windows environment requires planning and knowledge of session initiation protocol (SIP) audio, video call and presence, Instant Messaging (IM) administration. You should also have knowledge of the following Windows infrastructures:
A Windows desktop or Windows server OS:
  • Windows 10 (64-bit)
  • Windows Server 2012 R2
  • Windows Server 2016 R2 or higher
  • IPv4/IPv6
  • Windows firewall
This document assumes that the Windows OS is already deployed and administrators of PortSIP PBX have been allocated with the administrator permission to Windows.

Cloud and Virtualization Environment Supported

To build high-availability communication solution to help clients reducing cost and improving communication performance, PortSIP PBX commits support on cloud services and have confirmed compatibility with following cloud and virtualized environment:
  • VMware ESX 5.X and above.
  • Linux HyperV
  • Microsoft HyperV 20012 R2 and above
  • Microsoft AZURE
  • Amazon AWS
  • Google Could
  • Digital Ocean
  • UCloud

System performance depends on the following key factors

  • Maximum simultaneous calls needed for PBX
  • Maximum online users needed for PBX
  • Recordings for calls
  • Recording audio only or both audio and video
  • Maximum online users for audio/video conferences on PBX
  • Maximum IVRs (Virtual Receptionist) on PBX
  • Maximum Call Queues on PBX
  • Maximum Ring Groups on PBX
Depending on the key features listed above, PortSIP PBX is able to run on PCs and servers with various CPUs ranging from Intel i3 CPUs to Inter Xeon.

Other Requirements

  • Latest Firefox, Google Chrome, Edge browser
  • Microsoft .NET Framework version 4.5 or higher
  • Knowledge of Linux and Linux Internet administration
  • Knowledge of Windows and Windows Internet administration
  • A constant Internet connection to stun4.l.google.com on port 19302
  • Ensure server date-time is synced correctly

FQDN Support

Although PortSIP PBX is designed to be able to run on servers without FQDN specified, we recommend to specifying FQGN with the following advantages:
  • Easier access to Web Portal for PortSIP PBX
  • Easier management of IP phones and clients after IP address change for PBX
  • Convenient access to HTTPS when accessing Web Portal
  • Avoid browser warning when accessing the WebRTC Client
The FQDN you are using must be able to be resolved correctly into the server with PortSIP PBX installed in LAN. If PortSIP PBX is installed on the public network, FQDN must be resolved correctly into the public network address for the server with PBX installed.

1.3 Getting Help and Support Resources

You can find the guide, manual, video tutorials at the PortSIP Knowledge Base, or send an email to [email protected] to obtain the support.