Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [Solved] Ooma not working

    Scheduled Pinned Locked Moved General pfSense Questions
    50 Posts 5 Posters 8.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • X
      x88dually
      last edited by

      Screenshot_2020-01-13 MyRouter localdomain - Firewall Rules 1_GIG_LAN.png

      1 Reply Last reply Reply Quote 0
      • X
        x88dually
        last edited by

        saw my pic and went in to change protocol to any

        1 Reply Last reply Reply Quote 0
        • chpalmerC
          chpalmer
          last edited by

          😉

          Triggering snowflakes one by one..
          Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

          1 Reply Last reply Reply Quote 0
          • X
            x88dually
            last edited by

            didnt work.

            Do i need the Voip tab with a rule for a half assed Voip ??

            1 Reply Last reply Reply Quote 0
            • chpalmerC
              chpalmer
              last edited by

              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?

              Triggering snowflakes one by one..
              Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

              1 Reply Last reply Reply Quote 0
              • X
                x88dually
                last edited by x88dually

                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

                chpalmerC 1 Reply Last reply Reply Quote 0
                • chpalmerC
                  chpalmer @x88dually
                  last edited by

                  @x88dually

                  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..

                  Triggering snowflakes one by one..
                  Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                  1 Reply Last reply Reply Quote 0
                  • X
                    x88dually
                    last edited by x88dually

                    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

                    1 Reply Last reply Reply Quote 0
                    • chpalmerC
                      chpalmer
                      last edited by

                      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?

                      Triggering snowflakes one by one..
                      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                      1 Reply Last reply Reply Quote 0
                      • chpalmerC
                        chpalmer
                        last edited by

                        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.

                        Triggering snowflakes one by one..
                        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                        1 Reply Last reply Reply Quote 0
                        • X
                          x88dually
                          last edited by

                          OOma, theyre kinda like vonage

                          1 Reply Last reply Reply Quote 0
                          • chpalmerC
                            chpalmer
                            last edited by

                            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..

                            Triggering snowflakes one by one..
                            Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                            1 Reply Last reply Reply Quote 0
                            • X
                              x88dually
                              last edited by

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • X
                                x88dually
                                last edited by x88dually

                                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 igb1

                                I did turn on Nat

                                1 Reply Last reply Reply Quote 0
                                • X
                                  x88dually
                                  last edited by

                                  Did you have to make rules for Voipo ?

                                  1 Reply Last reply Reply Quote 0
                                  • chpalmerC
                                    chpalmer
                                    last edited by

                                    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.

                                    Triggering snowflakes one by one..
                                    Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                                    1 Reply Last reply Reply Quote 0
                                    • X
                                      x88dually
                                      last edited by

                                      ok, where do i dind those ??

                                      1 Reply Last reply Reply Quote 0
                                      • chpalmerC
                                        chpalmer
                                        last edited by chpalmer

                                        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.

                                        Triggering snowflakes one by one..
                                        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                                        1 Reply Last reply Reply Quote 0
                                        • chpalmerC
                                          chpalmer
                                          last edited by

                                          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

                                          Triggering snowflakes one by one..
                                          Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            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

                                            chpalmerC 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.