2 Configuring the PortSIP PBX
After the PortSIP PBX has been installed successfully, use your browser to access the web portal at https://66.175.221.120:8887. If the browser displays the SSL certificate warning, simply ignore it and proceed; Enter "admin" for both the username and password to log in. Leave the domain blank. The PBX dashboard page should look like the one in the screenshot below.
If you have not completed the setup wizard yet, it will appear automatically after you sign in to the web portal. To make the PBX work, some settings must be configured.
If the PBX server has a static public IP address, enter it for "Public IPv4". If the PBX server does not have a static public IP, do not enter "Public IPv4".
The private IPv4 address must be entered, if your server is without the private IP, please enter the public IP instead.
The public IP and private must be reachable by your SIP client. The IP address entered here is the SIP server IP address for PBX. It is required when a SIP client or IP phone registers to PortSIP PBX should be configured as the "Outbound Proxy Server".
If the PBX is located on the cloud, both the "Private IPv4" and "Public IPv4" should be entered here. If located in LAN, just enter the "Private IPv4" only.
The loopback interface (127.0.0.1) is unacceptable for the private IP. Only the static IP for the LAN where the PBX is located is allowed (do not use DHCP dynamic IP).
In order to support TLS transport for SIP, and provide HTTPS access for the Web Portal and REST API, we must have a trusted SSL certificate and upload it to PBX in this step.
You will need to have a web domain, for example, purchase a domain from a domain provider such as Godaddy, and resolve the domain to your PBX IP.
You will also need to purchase a trusted SSL certificate for this domain to avoid the browser warning. The certificate provider Digicert, GeoTrust, Godaddy, or other certificate providers are recommended.
If you don't have the domain or certificate, you can simply enter the PBX IP as the Web Domain, and accept the default certificate here. By default, the PortSIP PBX uses a self-signed certificate, which will cause the browser to block the connection and pop-up the warning information.
Please follow up this guide for purchase the SSL certificate: Preparing TLS Certificates for TLS/HTTPS/WebRTC.
You have two certificate files.
- portsip.key
- portsip.pem
Enter
uc.portsip.cc in the Web Domain field; open the portsip.pem file in Windows Notepad and copy all contents to the "Certificate File" field; and copy the contents of the portsip.key file to the "Private Key File" field. 
You can set the transport layer protocol for SIP signaling by clicking the Add button. By default, the transport ports are:
- UDP: 5060
- TCP: 5063
- TLS: 5061
You can feel free to change the default port to a new port that you prefer, but the port should not be used by other applications.
Once a new transport has been added, you have to change the firewall rule to allow the transport port. The IP Phone client app will connect to the PBX via transport and port.
To enable email notifications with PortSIP PBX for sending some system alert messages, the SMTP details must be configured.
If you using the Google SMTP server, please make sure that you have “less secure” enabled for your Gmail account. Please refer to the below links for more details:
You also need to select SSL or TLS security protocol if you’re using Google SMTP Server.
Once the PBX occurs some critical event, the alert email will be sent to "Recipients".
If you uploaded the trusted certificate rather than the self-signed certificate in step 2.2, please use the below commands to restart the PBX to make the certificate take effect.
cd /opt/portsip
/bin/sh pbx_ctl.sh restart
For Windows, just simply restart the server.
Last modified 1mo ago