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

[Joshua Nankin]

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/20120628/bfc00ad8/attachment.html