Ooma using default ports I need for other things?
I just purchased an Ooma Telo and successfully set it up. As per the recommendations in the instructions, I connected it directly behind my Comcast cable modem, and put my Ubiquiti Edgerouter-X firewall after it.
I just realized that since setting that up, I'm unable to connect to a "NextCloud" server I run that uses https on port 443, and I'm also unable to use my OpenVPN software on my iPhone to create a secure VPN tunnel back to my home network on port UDP 1194.
The info I found online says the Telo uses both of those ports (among other ones). Can these be changed?
I just realized that since setting that up, I'm unable to connect to a "NextCloud" server I run that uses https on port 443, and I'm also unable to use my OpenVPN software on my iPhone to create a secure VPN tunnel back to my home network on port UDP 1194.
The info I found online says the Telo uses both of those ports (among other ones). Can these be changed?
Re: Ooma using default ports I need for other things?
Put the Telo behind your router. Both of mine have been there since 2009.
I don't understand your port 443 complaint. Every server on the planet that supports https uses port 443.
https means use port 443 just like http means use port 80.
I don't understand your port 443 complaint. Every server on the planet that supports https uses port 443.
https means use port 443 just like http means use port 80.
Customer since January 2009
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
Re: Ooma using default ports I need for other things?
Murphy,
I can put the Ooma behind my router and "pinhole" all of the ports it needs. That's definitely doable. I just didn't start out that way because the instructions claimed it would handle prioritizing the traffic for phone calls when one came in or was established, if it was the first device after the modem.
What I'm saying, though, is that I run a couple of servers here. My router has "port forwarding" set up to direct incoming connections to them. Port 443 gets redirected to my NextCloud server, which serves everything as https secure web pages. From what I'm reading about Ooma Telo's requirements -- it, too, needs port 443 (probably for the web server in it to serve configuration pages).
If I redirect 443 to my NextCloud box, it sounds like even with the Telo behind my router, there will no longer be a way to access its web pages. I would rather custom configure the Telo to serve them on a non-standard port than go through all the work involved to configure NextCloud to do that.
And a similar issue came up with UDP port 1194, which is the standard default port used by OpenVPN. It seems odd that the Ooma Telo requires UDP and TCP 1194, unless it actually uses OpenVPN somehow itself, to communicate back to the company? This one should be easier for me to change on my OpenVPN server though -- since it just involves one configuration change on the server side, and editing the config file used by my VPN clients.
I can put the Ooma behind my router and "pinhole" all of the ports it needs. That's definitely doable. I just didn't start out that way because the instructions claimed it would handle prioritizing the traffic for phone calls when one came in or was established, if it was the first device after the modem.
What I'm saying, though, is that I run a couple of servers here. My router has "port forwarding" set up to direct incoming connections to them. Port 443 gets redirected to my NextCloud server, which serves everything as https secure web pages. From what I'm reading about Ooma Telo's requirements -- it, too, needs port 443 (probably for the web server in it to serve configuration pages).
If I redirect 443 to my NextCloud box, it sounds like even with the Telo behind my router, there will no longer be a way to access its web pages. I would rather custom configure the Telo to serve them on a non-standard port than go through all the work involved to configure NextCloud to do that.
And a similar issue came up with UDP port 1194, which is the standard default port used by OpenVPN. It seems odd that the Ooma Telo requires UDP and TCP 1194, unless it actually uses OpenVPN somehow itself, to communicate back to the company? This one should be easier for me to change on my OpenVPN server though -- since it just involves one configuration change on the server side, and editing the config file used by my VPN clients.
Re: Ooma using default ports I need for other things?
Communication between the Telo and the Ooma servers is via a vpn. That is how they provide security for the connection.
The Telo does not use any reserved incoming ports. Incoming ports are dynamically assigned when an outbound connection is set up.
The ports that they specify in their document are all outgoing ports and are only a problem if you have an outgoing firewall. Multiple outbound connections using port 443 are possible because they are going to different IP addresses.
The Telo does not use any reserved incoming ports. Incoming ports are dynamically assigned when an outbound connection is set up.
The ports that they specify in their document are all outgoing ports and are only a problem if you have an outgoing firewall. Multiple outbound connections using port 443 are possible because they are going to different IP addresses.
Customer since January 2009
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
- focuspuller
- Posts:175
- Joined:Fri Sep 04, 2009 2:45 pm
- Location:Third Planet From The Sun
Re: Ooma using default ports I need for other things?
Maybe put the Telo in the DMZ and that way it is clear of everything
One if by Land
Two if by Sea
Three if by Limo
Two if by Sea
Three if by Limo