If you plan to use phones or to access Switchvox from remote locations, you must forward certain ports back to Switchvox. A good resource for documentation on how to forward ports on most routers is:www.portforward.com.
To enable port forwarding, open
Setup > Networking > IP Configuration
The following table lists the TCP/UDP port assignments and how Switchvox uses them.
| Ports | Allowed From | Switchvox Usage |
| 5060/udp+tcp | Service Providers, Peered Switchvox, Peered VoIP PBX |
SIP signaling port needed for phones outside your network |
| 5062/udp+tcp | Service Providers, Peered Switchvox, Peered VoIP PBX | SIP signaling port needed for phones for configuration communications (Digium Phones only) |
|
10000-20000/udp |
Any | RTP audio ports needed for phones outside your network |
| 4569/udp | Service Providers, Peered Switchvox, Peered VoIP PBX | IAX Signalling Port needed for communicating with IAX provider |
| 4000-4999/udp | Service providers or T.38 fax services | UDPTL ports for T.38 faxing over SIP |
| 80/tcp | Users, and phone network, port is redirected to 443 for browsers. | HTTP port for remote web admin, API, and phone-firmware access |
| 443/tcp | Remote Admins, API integrations, users | HTTPS port for remote web admin and API access |
| 5222 & 843/tcp | Remote Switchboard users | Ports for using the Switchboard remotely |
| 5269/tcp |
Remote Switchboard (chat) users |
Port for remote XMPP (Jabber/chat) access (Extensible Messaging and Presence Protocol) |
| 1194/udp | Outbound only!! | Outbound traffic for Digium / Switchvox technical support vpn. |
| 161/udp+tcp | Remote Monitoring Services | SNMP for remote monitoring |
While the Switchvox provides an ACL to restrict access to specific services offered by the Switchvox, you should make these settings at your firewall to restrict access and not overburden the PBX system which can cause call quality issues. You should define groups of who should have access to what port(s) and take every effort to avoid allowing ALL users access.