[Freeswitch-users] FS not receiving incoming calls

Ignacio Durli ignaciodurli at cinchcast.com
Fri Nov 18 21:12:16 MSK 2016


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 at 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 at 192.168.99.103:5080            RUNNING (0)
                 external             profile           sip:mod_sofia at 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 at 192.168.99.103:5060            RUNNING (0)
                 internal              profile           sip:mod_sofia at 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 at 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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20161118/2a67a9bf/attachment-0001.html 


Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users mailing list