VOIP

Home » CentOS » VOIP
CentOS 4 Comments

Hello,

I changed ISPs a few weeks ago and now I’m on cable. In doing so, I lost the ability to use the DSL as a FAX line.

So, I bought an OOMA. Turns out it uses a number of ports, three of which are reserved, 53 TCP/UDP, 110 TCP and 443 TCP. These ports have already been port forwarded from my cable modem/router to my server.

I’m thinking this isn’t going to work unless I change some ports on my server, which I’m not willing to do.

I spent over 30 minutes with their support people last night. It appears the ports cannot be changed on the OOMA device.

Are there any work arounds?

TIA

4 thoughts on - VOIP

  • Try connecting it up behind your existing router, and see if it connects and works. I used to have a Vonage device, and it did the same exact nonsense, yet it still worked fine when behind the NAT in the main router. The web server and rest of the networked devices all still remained connected to the original router. You may need to forward some UDP ports, such as these from the OOMA website, UDP 1194,UDP 3386, UDP 3480, UDP 10000-30000.

    http://support.ooma.com/home/advanced-connections-and-service-ports

    Whenever I needed to configure the Vonage, I had to connect a notebook to the Vonage Ethernet ports to gain access to the web server port.

    Al

  • list. She

    Geeez!! I had to install Google/NSA Chrome to access the interface to get ooma working. Hope I can uninstall Google/NSA Chrome before my system is breeched!!