Ports Used by the Vodia Phone System

When deploying the Vodia PBX with AWS, Azure, Google Cloud, Digital Ocean it often becomes necessary to set the firewall up for the PBX. Port forward the following ports in your cloud firewall environment in order for your remote uses to connect and register SIP desktop phone as well as eliminating one way audio. The numbers in the table are the default. They can be changed from the PBX web interface. You can also check with netstat what ports are open on the PBX.

Protocol Port Description Requirements
UDP and TCP 5060 Vodia Phone System SIP Used for SIP signaling internal and external for remote users
TCP 80 Vodia default port to phone systems GUI Port 80 is used to generate a Lets encrypt certificate as well as the default port to login into the phone system
TCP 5061 Vodia Phone System SIP (TLS) Used for secure SIP signaling for remote extensions
TCP 443 https secure port access Used for secure https signaling and also used for Webrtc user portal 
UDP Port Range 49152-65535 Vodia RTP ports Vodia RTP ports are used to for SIP signaling.
TCP Port Range 2345-2346 LDAP Ports These ports are used to contact the Vodia LDAP server.

Telling the PBX what address to use 

For servers that don't have a public IP address on their local network interface (e.g. EC2) the PBX needs to know what IP address to present to the SIP devices. In admin mode, navigate to Settings → SIP→ Settings and set the IP routing list.

  • If you want always to present a public IP address, you can just put the IP address there, for example ""
  • If you want to send packets to devices in the private network, you can use the keyword "private". For example "private" would check if the destination is a private IP address and the server has a private IP address in that subnet, then it would use the private IP address. Otherwise it would use
  • If you are using the URL for polling the public IP address, you can use the keyword "public" which will be replaced with the actual public IP address.

Using the SIP IP replacement list is usually not necessary and creates unneeded complexity and problems. If the public IP address keeps changing, the PBX can download the address from a public IP address API (e.g. api.ipify.org). 

Example for IP routing list