Introduction: Firewall test checks if outbound communication to the LiveVox application ports is permitted by your network devices. | Info |
|---|
| Outbound communication to the LiveVox application ports is required for the platform to function correctly. Blocked ports may result in the loss or degradation of service. |
Objective: Ports must not be blocked. Test: In the Firewall Results section of the email, check if the ports are reported as blocked. Issue Resolution: If the ports are reported as blocked, contact the LiveVox Customer Care Team. | Info |
|---|
| The following table describes the standard use of each port. | Port | Use |
|---|
| TCP 443 | Web traffic (HTTPS). | | TCP 8080 | WebRTC traffic (web and audio paths established simultaneously). | | UDP 5060 | SIP-Trunks when your PBX does not support encryption with TLS version 1.2. | | TCP 5061 | SIP-Trunks when your PBX supports encryption with TLS version 1.2. Also used for sLVC. | | TCP 5071 | sLVT (hard-phones supported: Polycom VVX-310 and SoundPoint-331). | | UDP 15000-30000 | RTP streams (audio). |
|
| Note |
|---|
| A blocked port can be considered to be the cause of the issue depending on your implementation (that is, how you have established the audio path). If the port that is intended for establishing the audio path is reported as blocked, you must enable it. For example, if you cannot establish the audio path via WebRTC and the test result shows that the port TCP 5061 8080 is blocked but TCP 8080 is enabled, you must configure TCP 8080 for webRTC traffic (and not TCP 5061). enable the port. |
| Warning |
|---|
| If you are asked to enable a port, ensure that the port is enabled only in the outbound direction. |
|