[Solved] Ooma not working
-
didnt work.
Do i need the Voip tab with a rule for a half assed Voip ??
-
No. Devices do not care what you name your interface. Your device simply needs its internet access. If you plug in a computer into these ports does it get out to the internet?
-
5 port switch had Ooma, port 2 an 3 are Rokus and port 4 is FireTV. Already swappped devices in ports, everything connected exept ooma
-
Does the Ooma have to go out for a TFTP transfer in order to work? You may need to adjust and use the TFTP proxy..
-
not sure. Theres no real documentation on config other then plug into router, turn on, make calls 5 min later
It worked fine with dhcp from cisco router, i dont get it. Other then it not plugged into pfsense, but a switch first
-
Well- VOIP was never intended to be behind any kind of NAT when first implemented. It was hacked into the spec later when services like Vonage came around.
You are trying to double NAT right now. Im not sure why it works with some and not with others but that is the case.
But you could try putting some inbound firewall rules in place pointed at the Ooma device address. You need to find out what the device is trying to connect to by looking at your state table and watching firewall logs.
Who is your VOIP provider?
-
Also- go to System/Advanced.. /system_advanced_firewall.php on your firewall.
Down to "Network Address Translation"
"TFTP Proxy"
Select the interface your Ooma resides on.
Down to the bottom of the page and click "save"
I do not know if you need a reboot or not.
See if that helps.
-
OOma, theyre kinda like vonage
-
Ok..
I thought OOma was just the device.. Im a Voipo guy so know them best..
Let me see if I can find some server info..
-
This post is deleted! -
From system/logs/dhcp : the last 3 lines. Firewall logs have nothing about ooma 10.15.15.2
Jan 13 17:42:05 dhcpd reuse_lease: lease age 1514 (secs) under 25% threshold, reply with unaltered, existing lease for 10.15.15.2
Jan 13 17:42:05 dhcpd DHCPREQUEST for 10.15.15.2 from 00:18:61:2e:8e:7f (myx_0018612E8E7E) via igb1
Jan 13 17:42:05 dhcpd DHCPACK on 10.15.15.2 to 00:18:61:2e:8e:7f (myx_0018612E8E7E) via igb1I did turn on Nat
-
Did you have to make rules for Voipo ?
-
Yep
Inbound rules with the phone as the destination.
Server SIP and RTP ports. No port forwards only firewall rules. I do it with all my customers.
Otherwise SIP traffic can sometimes look like unsolicited traffic and get blocked.
-
ok, where do i dind those ??
-
Looks like the device connects via a VPN..
https://support.ooma.com/home/problems-connecting-to-setup-ooma-com/
Follow this and see. You have to plug into their port.
-
Setup static port on your OOma device address.
Instead of port 5060 in this article do it for port 1194
https://docs.netgate.com/pfsense/en/latest/nat/configuring-nat-for-voip-phones.html#disable-source-port-rewriting
-
OpenVPN shouldn't care about the source port. If they have broken OpenVPN that's an achievement!
However it won't connect at if it's not pulling a DHCP lease. The logs you showed seem to indicate it did pull an IP assuming your have confirmed 00:18:61:2e:8e:7f is the Ooma device?
Does it show a current lease in Status > DHCP Leases?Check the states it has opened. Go to Diagnostics > States and filter using it's IP address, 10.15.15.2 if it has not changed.
Show us what states are open for that if any.Steve
-
@stephenw10 said in Ooma not working:
OpenVPN shouldn't care about the source port. If they have broken OpenVPN that's an achievement!
Im trying to remember but I believe this would not be the first time someone did..
-
Ha, well I could certainly believe that! But OpenVPN is what you choose when your device has to be able to plug into any router and connect out as Oooma does. If they broke the server end so it required a static port that would be some spectacular foot-shooting.
It would also limit them to just one device per public IP which seems like a bad decision.Steve
-
@stephenw10 said in Ooma not working:
It would also limit them to just one device per public IP which seems like a bad decision.
Many VOIP providers skirt this by sequentially numbering the ports. My phone uses 5060, 5062 and 5064 for my three lines right here.
My guess is that if someone wanted more than one OOma device at their house then support would do something similar with their VPNs. I wonder how many do though. Or how many lines that OOma device can do?? two or possibly three depending.
There is a saying that a Ford engineer will step over 20 hookers to screw a mechanic.. Sometimes I believe the same about software and system engineers and IT personnel..
