[Freeswitch-users] Binding to virtual interface (ipsec vpn)

[Nicolas Brenner]

Here's the output of ifconfig -a:

http://pastebin.freeswitch.org/14199

This is the output of route:

http://pastebin.freeswitch.org/14200


This is the external.xml file under sip_profiles (is the default, only
modified sip-ip and rtp-ip):

http://pastebin.freeswitch.org/14201


This is somegateway.xml file under sip_profiles/external/

http://pastebin.freeswitch.org/14202


Output of sofia status from cli (tried with alias=true and alias=false on
internal profile):

http://pastebin.freeswitch.org/14203


This is the cli output with loglevel all set to 9 and siptrace on for
external profile:

http://pastebin.freeswitch.org/14204


Thanks


On Mon, Oct 11, 2010 at 2:33 PM, Brian West <brian at freeswitch.org> wrote:

> If you set the IP in sip-ip and rtp-ip that is abound to eth0:3 then it
> should bind to that interface/ip and use that... I haven't see anything out
> of the usual when doing this.
>
> Show me your profile config and the output of ifconfig -a
>
> /b
>
> On Oct 11, 2010, at 4:46 AM, Nicolas Brenner wrote:
>
> > Hello everyone,
> >
> > I'm having trouble binding FS to another ip on a virtual interface
> (eth0:3). The virtual interface's ip address is the gateway to an ipsec vpn,
> and the only way to access this voip provider's sip server, is through the
> vpn.
> >
> > I tried setting up an additional sip profile, with rtp-ip and sip-ip as
> the virtual interface's ip, but when I do that, no packets are sent at all
> when trying to make a call with originate through the cli (according to
> tcpdump). I tried also setting ext-rtp-ip and ext-sip-ip to the same virtual
> interface's ip, but nothing happened, still no packets being sent (according
> to tcpdump) when trying to make a call. Finally I tried only setting
> ext-rtp-ip and ext-sip-ip to the virtual interface's ip, and leave rtp-ip
> and sip-ip to $${local_ip_v4}, then tcpdump started seeing some traffic
> (when trying to originate a call) which I was able to capture. When I loaded
> the trace on wireshark though, I noticed the source ip being used to send
> all the (sip) packets, is the one from eth0 (public ip), and not eth0:3's ip
> (private ip for vpn).
> >
> > Has anyone had any similiar experiences? how were you able to solve it?
> >
> > Thanks for your help!
> >
> >
> > Nico
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20101011/d99f9fd9/attachment.html