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

[Nicolas Brenner]

I tried a few more things and discovered that apparently the sip profile
configuration was fine, but the problem has something to do with the
gateway, because when I try originating a call through another gateway, it
generates traffic fine, it doesn't work because is not on the right network
interface, but at least it tries.

This is the configuration of the gateway that is not working (although it
appears fine with sofia status on the console)

<gateway name="somegateway">
        <param name="username" value="someuser"/>
        <param name="password" value="somepass"/>
        <param name="from-domain" value="200.13.15.220:5061"/>
        <param name="realm" value="200.13.15.220:5061"/>
        <param name="proxy" value="200.13.15.220:5061"/>
        <param name="from-user" value="someuser"/>
        <param name="caller-id-in-from" value="false"/>
        <param name="expire-seconds" value="600"/>
        <param name="register" value="false"/>
        <param name="retry_seconds" value="5"/>
        <param name="extension" value="2011"/>
        <param name="context" value="public"/>
        <param name="codec-prefs" value="G729"/>
        <param name="rfc2833-pt" value="101"/>
      </gateway>


Could it be because of the port (5061)?




On Mon, Oct 18, 2010 at 10:33 AM, Nicolas Brenner <nico at clickfono.com>wrote:

> I haven't been able to solve this, but one thing I noticed though, is that
> the internal profile is being aliased to the ip of the interface I'm trying
> to use in the external profile, I'm guessing this causes trouble, the
> problem is that if I disable aliasing, it doesn't make a difference, and
> checking out the list archive, apparently is a bad idea to disable aliasing
> anyway.
>
> How do I prevent the internal profile from aliasing to a specific ip? and
> what ip should the internal profile should alias to if the server has to
> private ("internal") ip?
>
> Thanks.
>
>
>
> On Mon, Oct 11, 2010 at 7:21 PM, Nicolas Brenner <nico at clickfono.com>wrote:
>
>> Yup, here's the output:
>>
>> http://pastebin.freeswitch.org/14203
>>
>>
>> I'm trying to originate a call using the gateway on 200.13.15.220,
>> originating it from 172.26.6.161.
>>
>> Seems like no packets are going out at all, at least tcpdump is not
>> getting any. Oddly, if instead of setting sip-ip and rtp-ip to the ip of the
>> interface I need, I set ext-sip-ip and ext-rtp-ip to that ip, tcpdump starts
>> seeing traffic, but the traffic is originated from the wrong ip/interface
>> (the public one, instead of the one with the ipsec vpn).
>>
>>
>>
>> On Mon, Oct 11, 2010 at 6:50 PM, Michael Collins <msc at freeswitch.org>wrote:
>>
>>> When you do "sofia status" do you see the correct IP address for the
>>> profile in question?
>>> Also, when you make an outbound call can you see where (if?) the packets
>>> are going? Perhaps to another interface?
>>>
>>> -MC
>>>
>>>
>>> On Mon, Oct 11, 2010 at 2:44 PM, Nicolas Brenner <nico at clickfono.com>wrote:
>>>
>>>> The system routes are well configured, I can ping and telnet the gateway
>>>> from bash, all traffic to that gateway's ip is routed through the needed
>>>> interface. Now, are there other routes I should be addressing in FS config
>>>> files?
>>>>
>>>>
>>>> On Mon, Oct 11, 2010 at 6:33 PM, <Russell.Mosemann at cune.org> wrote:
>>>>
>>>>> Another thing to check is that there is only one IP address assigned to
>>>>> the interface. A problem with using the "right" IP address can occur if
>>>>> there is more than one IP address assigned to the same interface.
>>>>> Without
>>>>> routing rules, the operating system chooses the IP address from the
>>>>> interface that it believes is the best one for delivering the traffic,
>>>>> and sometimes it is not the address you want to use.
>>>>>
>>>>> --
>>>>> Russell Mosemann
>>>>>
>>>>>
>>>>>
>>>>> ________________________________________________________
>>>>> Concordia University, Nebraska
>>>>> See http://www.cune.edu/ for the latest news and events!
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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/20101018/87cf44c0/attachment.html