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

    Freeswitch question

    pfSense Packages
    2
    2
    1.7k
    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.
    • S
      scottnguyen
      last edited by

      Now that 1.2.3 is out, I was beginning to try out the FS package.  I saw here that a comment to try it internally it was said "To make this work locally only, bind ext/int/lan to the LAN IP" and Make sure turn off/configure your local machine's firewall too.

      Q 1.  Exactly how do BIND the EXTernal / INTerfaces interfaces?

      Q 2.  If I turn of the firewall, then obviously that feature is off, what is the better way to test this only INTERNALLY?  I wish to test the features with no public DNS or IP Address yet.

      Thanks.

      1 Reply Last reply Reply Quote 0
      • C
        cybrsrfr
        last edited by

        @scottnguyen:

        Now that 1.2.3 is out, I was beginning to try out the FS package.  I saw here that a comment to try it internally it was said "To make this work locally only, bind ext/int/lan to the LAN IP" and Make sure turn off/configure your local machine's firewall too.

        Q 1.  Exactly how do BIND the EXTernal / INTerfaces interfaces?

        If you want both internal and external profiles to bind to a particular ip address. Then there is a variable local_ip_v4 that is usually determined automatically however you can override the value by setting it at the top of the variables page.
        <x-pre-process cmd="set" data="local_ip_v4=192.168.0.1">If you want to adjust only a single sip profile you edit it and remove the ${local_ip_v4} and replace it with IP you want FreeSWITCH to bind to.
        <param name="rtp-ip" value="${local_ip_v4}">
        <param name="sip-ip" value="${local_ip_v4}">

        By default local_ip_v4 detect the WAN IP and therefore binds the internal and external profile to the WAN IP. But it is still protected by the firewall. So by default only people on the LAN can access it.

        @scottnguyen:

        Q 2.  If I turn off the firewall, then obviously that feature is off, what is the better way to test this only INTERNALLY?  I wish to test the features with no public DNS or IP Address yet.

        Set it up in the LAN or wherever you want and get a phone or soft phone and register to it.

        P.S The project has finally gotten a name. Its called fusionpbx and it is now multi-platform and the website is http://www.fusionpbx.com. pfSense package for the latest version is in the development.</x-pre-process>

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