[Freeswitch-users] Multiple network interfaces, can't force freeswitch to use one.

[Joshua Nankin]

Hi Eugene.

So, you are correct, I have configured my network to forward SIP and RTP
traffic to my 192.* IP, and this is working as intended.  I have also now
manually put in the 192.* IP into the sofia external.xml and internal.xml
for sip-ip and rtp-ip.

Again, on this virtual machine there are two interfaces (eth0=10.* ip, and
eth1=192.* ip).  After restarting freeswitch and doing the lsof -i that you
suggested, I get the following for freeswitch:

freeswitc 17227 freeswitch   23u  IPv4  61949      0t0  UDP
192.168.1.10:5080
freeswitc 17227 freeswitch   26u  IPv4  61950      0t0  TCP
192.168.1.10:5080 (LISTEN)
freeswitc 17227 freeswitch   30u  IPv6  61957      0t0  UDP
ip6-localhost:5080
freeswitc 17227 freeswitch   31u  IPv6  61958      0t0  TCP
ip6-localhost:5080 (LISTEN)
freeswitc 17227 freeswitch   35u  IPv4  62707      0t0  UDP 192.168.1.10:
sip
freeswitc 17227 freeswitch   36u  IPv4  62708      0t0  TCP 192.168.1.10:sip
(LISTEN)
freeswitc 17227 freeswitch   37u  IPv4  61960      0t0  UDP 10.0.2.15:33908
->chic-cns.area4.il.chicago.comcast.net:domain
freeswitc 17227 freeswitch   40u  IPv4  61964      0t0  TCP
localhost:zope-ftp (LISTEN)

I'm not sure where that 10.0.2.15 is configured in freeswitch, or even what
that port is for.

So, below I've linked to two packet captures for both eth0 and eth1.
 You'll notice that the intial INVITE is occuring on eth0, but that we're
receiving traffic from the sip provider on eth1 that is not being responded
to by freeswitch.  I still can't figure out why that is happening (both why
eth0 is even being used, and why freeswitch is not responding to traffic
directed at the other IP).

http://joshnankin.com/tcpdump0.pcap
http://joshnankin.com/tcpdump1.pcap

Thanks again for all of your help.


On Thu, Jun 28, 2012 at 7:31 PM, Joshua Nankin <jnankin at gmail.com> wrote:

> I'm stumped.  Do you think it would be possible to use a sofia alias to
> get the profile to listen to the other ip (192.x) as well?
>
>
> On Thu, Jun 28, 2012 at 5:10 PM, curriegrad2004 <curriegrad2004 at gmail.com>wrote:
>
>> That could be causing the problems right there if Vagrant is doing
>> some NATing or mangling the IP packets
>>
>> On Thu, Jun 28, 2012 at 2:48 PM, Joshua Nankin <jnankin at gmail.com> wrote:
>> > Right, but freeswitch is still getting packets to 192.168.1.7, but
>> sending
>> > from 10.0.2.15.
>> >
>> > Not sure if this makes a difference, but this is a Vagrant virtual
>> machine
>> > with a bridged interface.  The 10.x address is an internal Vagrant ip,
>> but
>> > the 192 is from my router DHCP.  I've set the external sip and rtp ips
>> to my
>> > public IP address, and that IP is what appears for the profile in sofia
>> > status.
>> >
>> >
>> >
>> > On Thu, Jun 28, 2012 at 4:36 PM, Joshua Nankin <jnankin at gmail.com>
>> wrote:
>> >>
>> >> I did a sudo /etc/init.d/freeswitch restart.  That should be enough
>> >> correct?
>> >>
>> >> On Thu, Jun 28, 2012 at 4:08 PM, Joshua Nankin <jnankin at gmail.com>
>> wrote:
>> >>>
>> >>> sip-ip and rtp-ip in both external.xml and internal.xml were set to
>> >>> $${local_ip_v4}.  I figured that setting the ip in vars.xml would be
>> enough.
>> >>>
>> >>> I manually set sip-ip and rtp-ip and both of those files, but that
>> still
>> >>> did not solve the problem.
>> >>>
>> >>> Any other ideas?
>> >>>
>> >>>
>> >>> On Thu, Jun 28, 2012 at 3:41 PM, Joshua Nankin <jnankin at gmail.com>
>> wrote:
>> >>>>
>> >>>> I have two interfaces on my machine, eth0=10.0.2.15 and
>> >>>> eth1=192.168.1.7.  I'm trying to get freeswitch to only use eth1.
>>  I've put
>> >>>> the following at the top of my vars.xml:
>> >>>>
>> >>>> <X-PRE-PROCESS cmd="set" data="local_ip_v4=192.168.1.7"/>
>> >>>>
>> >>>> However, this does not seem to be working.  When I originate a call,
>> I
>> >>>> see that the initial invite is originating from 10.0.2.15, but
>> incoming
>> >>>> packets from my sip provider are going to 192.168.1.7 and are not
>> being
>> >>>> responded to by freeswitch.  Shouldn't freeswitch be listening on
>> >>>> 192.168.1.7 and sending packets from there as well?
>> >>>>
>> >>>> What am I doing wrong?
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120629/4f8b2a6e/attachment-0001.html