2 Configure the PortSIP SBC
Last updated
Last updated
In this guide, we will assume that the SBC is installed on a server with a static private IP of 192.168.1.73 and a static public IP of 66.175.221.120, and that the domain sbc.portsip.cc has been resolved to the IP 66.175.221.120 .
The PBX is located on the same LAN as the SBC server, and the private IP is 192.168.1.72. The PBX is required to support the Path Header which is defined in RFC3327.
After the PortSIP SBC has been installed successfully, use your browser to access the web portal at https://sbc.portsip.cc:8883. The sign-in page looks like the one in the screenshot below. Enter "admin" for both the username and password to log in.
Please follow this topic to prepare the TLS Certificates.
Choose "Settings > TLS Certifidates" from the menu, click Add button, and type "SBC Host Name" for the "Description" field as an example; fill the sbc.portsip.cc in the "TLS Domain" field. Open the "portsip.pem" file in Windows Notepad and copy the contents into the "Certificate Context" field. Copy and paste the contents of the "portsip.key" file into the "Private Key Context" field. Click the OK button to save the certificates.
Select "Settings > Network" from the menu, and fill in the "Web Domain" field with sbc.portsip.cc, the "Private IPv4" field with192.168.1.73, and the "Public IPv4" field with 66.175.221.120. By default, the "Create default transports automatically" option is turned on, and the SBC will create the default transports after successfully setting up the SBC IP address.
TCP on port 5069 : it's used to communicate with PBX;
TLS on port 5067 : it's used to communicate with Microsoft Teams;
WSS on the port 5065 : it's used to provide the WebRTC service.
UDP on the port 5066: it's used to provide the normal SIP service.
You can turn off this option to prevent the SBC from automatically creating default transports, but this is not recommended.
The private IPv4 address must be entered; if your server does not have a private IP, please enter the public IP instead.
By default, the SBC uses UDP ports 25000–35000 for the RTP transmission. You can feel free to change the port range but ensure other applications do not use the ports, we suggest keeping the default settings.
When you click the OK button, SBC will restart automatically and immediately sign you out.
If you change the default RTP ports, please ensure they are not used by other applications and add firewall rules for them.
If the PBX is PortSIP PBX, please follow the below steps.
Sign in to the PBX web portal, https://uc.portsip.cc:8887, and click the menu "Advanced > SBC". Click the "Generate" button to generate the token for the SBC's access. Click the Copy button to copy the token.
Sign in to the PortSIP SBC Web Portal https://sbc.portsip.cc.cc:8883. Choose Settings > PBX from the menu. You have to set up the PBX information here then the SBC will communicate with the PortSIP PBX. Paste the copied token to the "PBX Access Token" field, and enter the PBX private IP 192.168.1.72 for the "PBX IPv4 Address" field. Since the TCP transport is created on the port 5063 in the PortSIP PBX, please choose the TCP for "Prefer to transport to communicate with PBX", and enter "5063" for "PBX Port".
If the PBX is NOT PortSIP PBX, please follow the below steps.
Create a TCP transport on 5063 in your PBX
Sign in to the PortSIP SBC Web Portal https://sbc.portsip.cc:8883. Choose Settings > PBX from the menu. You have to set up the PBX information here then the SBC will communicate with the PortSIP PBX. Enter the PBX private IP 192.168.1.72 for the "PBX IPv4 Address" field. If If the TCP transport is created on the port 5063 in the 3rd PBX, please choose the TCP for "Prefer to transport to communicate with PBX", and enter "5063" for "PBX Port". If your PBX TCP transport is not 5063 but it's 5061 for example, then you will need to enter the 5061 for the "PBX Port" in SBC Web Portal.
If your PBX TCP transport is not 5063 but it's 5061, then you will need to enter the 5061 for the "PBX Port" in SBC Web Portal.
Choose "Settings > Transports" from the menu. The SBC requires adding four types of transport here.
A TCP transport for the SBC to communicate with the PBX
A TLS transport for the SBC to communicate with the Microsoft Teams
A WSS transport for the SBC to provide WebRTC service
A UDP transport for the SBC to provide normal SIP service
One is for the SBC to communicate with the PBX, one is for Microsoft Teams, and one is for the WebRTC clients. After the above step 2.2 is completed with the "Create default transports automatically" option on, the SBC will create the default transport automatically.
These default transports aren't recommended to be changed, we recommend keeping the "Create default transports automatically" option turned on in the above step 2.2.
This step is unnecessary if you keep using the default transport. If you wish to create your own transport, you can delete the existing transport.
Add a "WSS" transport for WebRTC clients as in the below screenshot, please choose the "SBC public IP" for the "Network Interface".
Add a "TLS" transport for the SBC to communicate with Microsoft Teams as in the below screenshot, please choose the "SBC public IP" for the "Network Interface".
Add a "UDP" transport for the SBC to provide the normal SIP service as in the below screenshot, please choose the "SBC public IP" for the "Network Interface".
Add the "TCP" transport for SBC to communicate with the PBX, please refer to the below screenshot, and choose the "SBC private IP" for the "Network Interface";
If you created your own transports rather than using the default transport, please open the ports of your transport on the firewall with the below commands. For example, if you create a UDP transport on port 5066, TCP transport on port 5071, TLS transport on port 5072, and WSS transport on port 5075, please execute the below commands.
The below commands are used to check currently opened ports for PortSIP SBC.
Create the Windows Firewall Rules as the Windows Guide.
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.
If the SBC runs on a cloud platform such as AWS and the cloud platform has a firewall itself, you must open the ports on the cloud platform firewall as well.
If the PBX is PortSIP PBX, please follow the below steps.
Select the menu "Settings > PBX", and click the SYNC NOW button, the PBX will synchronous the PBX SIP domains automatically. You can refresh the page to see the sync result, the "200 OK " means successfully synced.
If the PBX is NOT a PortSIP PBX, please follow the below steps.
Select the menu "Settings > Domains", click the Add button, and enter a friendly name for the "Description" field.
Copy your PBX SIP domain and paste it to the "SIP Domain" field and click the OK button to save the SIP domain.
Please add the SIP domains of all tenants to the SBC as described above if your PBX is a multi-tenant PBX.
The PortSIP SBC allows you to rebrand the SBC in an easy way, you can get your own SBC with just a few clicks.
Select the menu "Settings > Rebranding", you can change the company name, product name, and likes, and upload your logo and favicon, click the "OK" button to save the settings.
