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.9k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      If you really have the conflicting subnets shown in your other thread then it's not surprising. I'd be surprised if anything worked if that's the case.

      Steve

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

        You're answering me in my Renaming Interface thread. So we should finish there ?

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

          Well dhcp probably wasn't even starting with those conflicts. Check the logs and status > service page to make sure it is after correcting the subnets.
          Check the dhcp status page.

          Steve

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

            Dhcp was working for Rokus and they are connected to internet and Lan.

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

              in dhcp leases page 3 ip's and there 3 reservations, dont have a trash can icon.

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

                Ok so if they are all connected to OPT1 as shown in your diagram and the Roku devices did pull an IP then other devices in that subnet should also. Assuming they are configured as dhcp clients that is.
                Not sure what connection to LAN they had if they're are on OPT1 but that would be routed if you have rules to pass it.

                Steve

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

                  opt1 has a rule going to Wan

                  When i reset ip's i made rules for them to see each other and Wan

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

                    that didnt help

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

                      VoipRules.jpg

                      Your outbound rules should show up like this. Not with destination to WAN NET or Address.

                      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's not Voip the way Freepbs is.
                        its a box that plugs into network. Has a phone jack on the back next to lan port.

                        If this doesnt matter, why did it matter with cisco router?

                        i dont have a VoIP tab up there, or routing, i only have, floating, wan, lan, and opt1 and 2. How do i get that up there ?

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

                          I showed you an example. You need to use a little logic. Whatever interface your phone thing is plugged into has to have access through the interface. The above example is how you do it.

                          Can you show a screenshot of your interface rules?

                          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

                            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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.