The SBC will automatically create the following transports:
TCP 5069 – Communication with PBX
TLS 5067 – Microsoft Teams Direct Routing
WSS 5065 – WebRTC services
UDP 5066 – Standard SIP services
Disabling automatic transport creation is not recommended unless you are performing a custom configuration.
Click OK.
The SBC will restart automatically and log you out.
Step 5: Restart the PBX
Execute the command below to restart the SBC:
Step 6: Generate the SBC Access Token in PBX
Sign in to the PBX Web Portal: https://uc.portsip.cc:8887
Navigate to Servers > SBC.
Click Generate to create an access token.
Click Copy to copy the token.
Step 7: Configure PBX Connection in SBC
Sign in to the SBC Web Portal: https://uc.portsip.cc:8883
Navigate to Settings > PBX.
Configure the following:
PBX Access Token: Paste the copied token
PBX IPv4 Address:192.168.1.72
(If PBX runs in HA mode, enter the PBX Virtual IP)
Prefer Transport:TCP
PBX Port:5063
Click OK to save.
Step 8: Access the WebRTC Client
Open the following URL in your browser: https://uc.portsip.cc:10443/webrtc, the WebRTC client will launch.
Scan the user’s QR code to register with the PBX and place or receive calls.
Configure PortSIP SBC on a Separate Server
Follow these steps if the PortSIP SBC is installed on a separate server from the PortSIP PBX.
A trusted wildcard SSL certificate (not self-signed) must be installed for the domain: portsip.cc
Step 2: Sign In to the SBC Web Portal
Open the following URL in your browser: https://66.175.221.120:8883
Log in using the default credentials:
Username:admin
Password:admin
Ignore the browser SSL certificate warning and continue.
Step 3: Upload the TLS Certificate
Navigate to Settings > TLS Certificates.
Click Add.
Enter the following values:
Description:SBC Host Name (example)
TLS Domain:sbc.portsip.cc
Open the portsip.pem file in a text editor and copy its contents into the Certificate Context field.
Open the portsip.key file and copy its contents into the Private Key Context field.
Enable This is SBC Web Domain Certificate.
Click OK to save the certificate.
Step 4: Configure Network Settings
Navigate to Settings > Network.
Configure the following fields:
Web Domain:sbc.portsip.cc
Private IPv4:192.168.1.73
Public IPv4:66.175.221.120
Ensure Create default transports automatically is enabled.
When this option is enabled, the SBC automatically creates the following transports:
TCP 5069 – Communication with the PBX
TLS 5067 – Microsoft Teams Direct Routing
WSS 5065 – WebRTC services
UDP 5066 – Standard SIP services
Turning off automatic transport creation is not recommended unless you are performing an advanced custom configuration.
Click OK.
The SBC will restart automatically and log you out.
Step 5: Restart the PBX
After the SBC restarts, restart the PBX to ensure proper connectivity.
Step 6: Generate the SBC Access Token in the PBX
Sign in to the PBX Web Portal: https://uc.portsip.cc:8887
Navigate to Servers > SBC.
Click Generate to create an SBC access token.
Click Copy to copy the generated token.
Step 7: Configure PBX Connection in the SBC
Sign in to the SBC Web Portal: https://sbc.portsip.cc:8883
Navigate to Settings > PBX.
Configure the following fields:
PBX Access Token: Paste the copied token
PBX IPv4 Address:192.168.1.72
(If the PBX is deployed in HA mode, enter the PBX Virtual IP instead)
Prefer Transport:TCP
PBX Port:5063
Click OK to save the configuration.
Step 8: Access the WebRTC Client
Open the following URL in your browser: https://sbc.portsip.cc:10443/webrtc, the WebRTC client will launch.
Scan the user’s QR code to register with the PBX and make or receive calls.
Step 9: Add the SBC IP Address to the PBX Whitelist
To prevent the PBX from rate-limiting requests from the SBC, you must whitelist the SBC IP address.
Sign in to the PBX Web Portal as a System Administrator.
Navigate to IP Blacklist.
Click Add.
Enter the SBC IP address (192.168.1.73 or the public IP if applicable).
Set a long expiration date.
Save the configuration.
Check Open Firewall Ports
The following commands can be used to verify which firewall ports are currently open on the server hosting the PortSIP SBC.