by default we figure out the IPv4 address which would route to the Internet and we set that to a variable.  you can override this, check out vars.xml, it should be documented in there

On Saturday, July 11, 2015, Joli Martinez <mrjoli021@gmail.com> wrote:

freeswitch@internal> sofia status 

                     Name   Type                                       Data State

=================================================================================================

            192.168.1.250   alias                                   internal ALIASED

           192.168.21.250   alias                                   internal ALIASED

                 external profile           sip:mod_sofia@99.58.100.184:5080 RUNNING (0)

            internal-ipv6 profile           sip:mod_sofia@99.58.100.184:6693 RUNNING (0)

                 internal profile           sip:mod_sofia@99.58.100.184:6693 RUNNING (0)

=================================================================================================

3 profiles 2 aliases


freeswitch@internal> 



192.168.21.250 is the interface for FS.  192.168.1.250 is Lan2.  LAN2 should not be connected to FS.

How can I fix this?



On Sat, Jul 11, 2015 at 3:52 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:

What do you see in "sofia status" output? It should list the IP addresses and ports where it binds.

Also "netstat -an" is useful for troubleshooting.

On Jul 11, 2015 9:37 PM, "Joli Martinez" <mrjoli021@gmail.com> wrote:
Hello,

I have installed Freeswitch and fusionPBX.  My LAN network is 192.168.21.0/24.  PBX is 250.  I am trying to register a phone to Freeswitch.  When I do tcpdump on the LAN interface on port 5060, I see traffic hitting the box from the phone, but on the Freeswitch CLI I see nothing.  I am assuming an ACL is blocking the traffic.  Where can I allow the LAN side to register?

I have tried the acl.xml and added the following and it still doesn't work.  After I did this I reloaded the ACL and also restarted FS.

<list name="lan" default="allow">
      <!-- <node type="deny" cidr="192.168.21.0/24"/> -->
      <node type="allow" cidr="192.168.21.0/24"/>
    </list>

    <!--
        This will traverse the directory adding all users 
        with the cidr= tag to this ACL, when this ACL matches
        the users variables and params apply as if they 
        digest authenticated.
    -->
    <list name="domains" default="deny">
      <!-- domain= is special it scans the domain from the directory to build the ACL -->
      <node type="allow" domain="$${domain}"/>
      <node type="allow" cidr="192.168.21.1/32"/>
      <!-- use cidr= if you wish to allow ip ranges to this domains acl. -->
      <node type="allow" cidr="192.168.21.0/24"/>

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org