Hi Ignacio, 

Please remember to always reply to the thread.

Can you check the sip-ip and/or ext-sip-ip of your active profiles?

Looks like the issue could be there.



On Fri, Nov 18, 2016 at 1:13 PM, Ignacio Durli <ignacio.durli@gmail.com> wrote:
Thanks for your reply Joel. Here's the output, I see that the FS process is binding 10.X interface with port 5060, but I don't know why that doesn't match what sofia status is showing:

root@osboxes:~# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
root@osboxes:~# netstat -putan | grep -i freeswitch
tcp        0      0 10.0.3.15:5080          0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 10.0.3.15:5081          0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 10.0.3.15:5060          0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 10.0.3.15:5061          0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 0.0.0.0:8082            0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 10.0.3.15:7443          0.0.0.0:*               LISTEN      3519/freeswitch 
tcp        0      0 192.168.99.103:59607    192.168.99.103:3306     ESTABLISHED 3519/freeswitch 
tcp        0      0 192.168.99.103:59606    192.168.99.103:3306     ESTABLISHED 3519/freeswitch 
tcp        0      0 192.168.99.103:59611    192.168.99.103:3306     ESTABLISHED 3519/freeswitch 
tcp6       0      0 ::1:5080                :::*                    LISTEN      3519/freeswitch 
tcp6       0      0 ::1:5081                :::*                    LISTEN      3519/freeswitch 
tcp6       0      0 ::1:5060                :::*                    LISTEN      3519/freeswitch 
tcp6       0      0 ::1:5061                :::*                    LISTEN      3519/freeswitch 
tcp6       0      0 ::1:8081                :::*                    LISTEN      3519/freeswitch 
tcp6       0      0 ::1:8082                :::*                    LISTEN      3519/freeswitch 
tcp6       0      0 :::8021                 :::*                    LISTEN      3519/freeswitch 
udp        0      0 10.0.3.15:5060          0.0.0.0:*                           3519/freeswitch 
udp        0      0 10.0.3.15:5080          0.0.0.0:*                           3519/freeswitch 
udp        0      0 0.0.0.0:1337            0.0.0.0:*                           3519/freeswitch 
udp6       0      0 ::1:5060                :::*                                3519/freeswitch 
udp6       0      0 ::1:5080                :::*                                3519/freeswitch 




On Fri, Nov 18, 2016 at 10:36 AM, Joel Serrano <joel@gogii.net> wrote:
Output of:

# iptables -L -n
# netstat -putan | grep -i freeswitch

Please :)

On Fri, Nov 18, 2016 at 10:12 AM, Ignacio Durli <ignaciodurli@cinchcast.com> wrote:

I upgraded to FS 1.6.12 which I installed in a new Debian 8 instance ran in VirtualBox. After compiling and running all the config scripts I’m not able to establish a SIP call. After some troubleshooting I found that calls are being answered on my eth1 interface (10.0.x.x) but not on my eth0 interface (192.168.99.x).

 

The IP is configured in vars.xml properly and sofia status is showing:

 

freeswitch@freeswitch> sofia status

                     Name                 Type                                         Data               State

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

            external-ipv6        profile                    sip:mod_sofia@[::1]:5080        RUNNING (0)

            external-ipv6        profile                    sip:mod_sofia@[::1]:5081        RUNNING (0) (TLS)

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

                 external             profile           sip:mod_sofia@192.168.99.103:5081            RUNNING (0) (TLS)

           192.168.99.103        alias                                       internal             ALIASED

            internal-ipv6         profile                    sip:mod_sofia@[::1]:5060        RUNNING (0)

            internal-ipv6         profile                    sip:mod_sofia@[::1]:5061        RUNNING (0) (TLS)

                 internal              profile           sip:mod_sofia@192.168.99.103:5060            RUNNING (0)

                 internal              profile           sip:mod_sofia@192.168.99.103:5061            RUNNING (0) (TLS)

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

4 profiles 1 alias

 

 

Which looks fine. Also the ifconfig of the new Debian instance seems OK, since it’s the same that I have on another VM where an older FS version is running.

 

root@osboxes:/usr/local/freeswitch/bin# ifconfig

eth0      Link encap:Ethernet  HWaddr 08:00:27:3a:f0:c6 

          inet addr:192.168.99.103  Bcast:192.168.99.255  Mask:255.255.255.0

          inet6 addr: fe80::a00:27ff:fe3a:f0c6/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2482 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1034 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:353837 (345.5 KiB)  TX bytes:227253 (221.9 KiB)

 

eth1      Link encap:Ethernet  HWaddr 08:00:27:f7:f1:24 

          inet addr:10.0.3.15  Bcast:10.0.3.255  Mask:255.255.255.0

          inet6 addr: fe80::a00:27ff:fef7:f124/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:4298 errors:0 dropped:0 overruns:0 frame:0

          TX packets:7037 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:437241 (426.9 KiB)  TX bytes:829683 (810.2 KiB)

 

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:49100 errors:0 dropped:0 overruns:0 frame:0

          TX packets:49100 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:8431576 (8.0 MiB)  TX bytes:8431576 (8.0 MiB)

 

 

I honestly don’t know what’s going on. Acls are fine, and I don’t see any error in the FS log. I traced the network traffic and when trying to call to 192.168.99.103:5060 I get an ICM (Destination unreachable) which doesn’t make sense according to what sofia status is showing. Any hint on this?


_________________________________________________________________________
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