On Mon, Oct 11, 2010 at 5:57 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
100% you should only be setting sip-ip sip-port and rtp-ip
you don't need the ext-* family of params at all.

did you check netstat -na | grep <your ip> to see that it was bound?


The external profile is bound to port 5080 on the specified ip address, maybe the title of my email is somewhat misleading, but the problem is that even though it is bound to that address, it is not sending out any traffic.

 
I think it's a network interface configuration problem more than anything else.


The network interface is actually working fine, I can ping the gateway and telnet to the port where it is configured to listen. Basically, I can communicate with it manually, but not with FS.

 
It could also be iptables which you can prove by disabling it to see
any improvement and then craft appropriate rules.


iptables is actually disabled for these tests, yet this is all I get from tcpdump while trying to originate a call:

tcpdump -nq -s 0 -A -vvv host 200.13.15.220
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

0 packets captured
0 packets received by filter
0 packets dropped by kernel


 

On Mon, Oct 11, 2010 at 4:46 AM, Nicolas Brenner <nico@clickfono.com> 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@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
googletalk:conf+888@conference.freeswitch.org
pstn:+19193869900

_______________________________________________
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