Before Started
The PortSIP PBX v16.0 is an ALL NEW major release, which means it can't be upgraded from the PortSIP PBX v12.x installation automatically. Version 16.0 must be installed on a new server which no v12.x installed.
Deploying PortSIP PBX in a Linux environment requires planning and knowledge of session initiation protocol (SIP), audio and video calls, presence, and Instant Messaging (IM) administration.
You should also have knowledge of the following Linux infrastructures and popular Linux distributions:
- CentOS 7.9 (64-bit)
- Debian 10.x, 11.x (64-bit)
- Ubuntu 18.04, 20.04, or 22.04 (64-bit)
- Docker 20.10 or higher.
- IPv4/IPv6
- Systemd
- IP tables
- Firewalld
- HTTP
This document assumes that the Linux OS is already deployed and administrators of PortSIP PBX have been granted root permission to Linux.
If your Linux server has installed PortSIP PBX v12.x, please follow the below steps before installing v16.0. These steps will delete all your PBX data. You can back up the
/var/lib/portsip directory first.sudo docker stop portsip-pbx
sudo docker rm portsip-pbx
cd /var/lib/ && sudo rm -rf portsip
The above commands deleted the PBX v12.x
docker instance. Now let us list the PortSIP PBX v12.x docker image .// This command will list all docker images
sudo docker image list
// You can use the docker image rm command to delete the PortSIP PBX image, the "1a0c"
// is the first 4 characters of the image tag id.
sudo docker image rm 1a0c
Deploying PortSIP PBX in a Windows environment requires planning and knowledge of session initiation protocol (SIP), audio, video call, presence, and Instant Messaging (IM) administration. You should also have knowledge of the following Windows infrastructure.
A Windows desktop or Windows server OS:
- Windows 10/11 (64-bit)
- Windows Server 2016/2019/2020/2022
- IPv4/IPv6
- Windows firewall
This document assumes that the Windows OS is already deployed and administrators of PortSIP PBX have been granted administrator permission to Windows.
If your Windows server has installed PortSIP PBX v12.x, please follow the below steps before installing v16.0. These steps will delete all your PBX data. You can back up the
C:\ProgramData\PortSIP directory first.- 1.Uninstall the PortSIP PBX v12.x
- 2.Delete the
C:\ProgramData\PortSIPdirectory - 3.Delete the
C:\Program Files\PortSIPdirectory
To build a high-availability communication solution to help clients reduce cost and improve communication performance, PortSIP PBX commits support to cloud services and has confirmed compatibility with the following cloud and virtualized environments:
- VMware ESX 5.X and above.
- Linux HyperV
- Microsoft HyperV 2016 R2 and above
- Microsoft AZURE
- Amazon AWS
- Google Could
- Digital Ocean
- ALI Cloud
- 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 Receptionists) 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 Xeon.
- 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.
Although PortSIP PBX is designed to be able to run on servers without FQDN specified, we recommend 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 warnings 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.
When there is a need for additional security of the SIP traffic, the Transport Layer Security (TLS) is used to secure the device's SIP signaling connections. In TLS protocol, the data is encrypted and protected. TLS communication requires certificate to authenticate recipient of the secured data.
PortSIP PBX and SBC use certificates to deliver secured SIP traffic and services and support WebRTC and Microsoft Teams Direct Routing. In addition, certificates are used to provide secure access to the device, and Web (HTTPS) sessions.
Last modified 1mo ago