[SR-Users] Kamailio & rtpproxy with more than one external IP interfaces

Leonid Fainshtein leonid.fainshtein at xorcom.com
Wed Apr 22 21:03:54 CEST 2020


David,
My problem is actually rtpproxy. I have to use a particular IP as the
source address for RTP sending.
Best regards,
Leonid Fainshtein
Xorcom Ltd


On Wed, Apr 22, 2020 at 9:51 PM David Villasmil <
david.villasmil.work at gmail.com> wrote:

> Hello,
>
> In terms of private/public IP addresses,in kamailio you would need to
> "advertise" the public IP address, such that:
>
> listen=udp:192.168.0.10:5060 ADVERTISE 123.123.123.123:5060
>
> So kamailio, when sending out, utilises that public (advertise) IP address
> as its own address.
> I don't know of any mechanism that allows you to set two different public
> IP addresses as advertised addresses.
>
> You _can_ receive  from multiple public IPs by setting multiple aliases,
> like:
>
> alias=123.123.123.123:5060
> alias=213.213.213.213:5060
>
> and kamailio would process them as its own IPs.
> But when sending out, it will use the ADVERTISED address.
>
> So the correct thing to do is to have multiple private address mapped
> one-to-one to public ip address, i.e.:
>
> listen=udp:192.168.0.10:5060 ADVERTISE 123.123.123.123:5060
> listen=udp:192.168.0.20:5060 ADVERTISE 213.213.213.213:5060
>
> This _would_ work properly.
>
> Regards,
>
> David Villasmil
> email: david.villasmil.work at gmail.com
> phone: +34669448337
>
>
> On Wed, Apr 22, 2020 at 7:04 PM Leonid Fainshtein <
> leonid.fainshtein at xorcom.com> wrote:
>
>> Can you elaborate a little? I didn't understand you.
>> Best regards,
>> Leonid
>>
>>
>>
>> On Wed, Apr 22, 2020 at 6:53 PM David Villasmil <
>> david.villasmil.work at gmail.com> wrote:
>>
>>> I think mapping IPs is a one-to-one relationship
>>>
>>> On Wed, 22 Apr 2020 at 16:18, Leonid Fainshtein <
>>> leonid.fainshtein at xorcom.com> wrote:
>>>
>>>> Hi,
>>>> My server has several external IP interfaces and one internal
>>>> interface. For some calls I would like to handle RTP via Ext1<->Int
>>>> interfaces and for other calls: via Ext2<->Int.
>>>> In order to achieve this,  I don't define the '-l' rtpproxy parameter,
>>>> and depending on the call, I set the required IP address as a parameter of
>>>> rtpproxy_manage().
>>>> I didn't succeed to get the desired result.
>>>> On my testbed, I have the following interfaces:
>>>> Ext1: 192.168.0.31
>>>> Ext2: 192.168.0.32
>>>> Int:     10.159.65.1
>>>>
>>>> When I try to create Ext2<->Int (192.168.0.32<-> 10.159.65.1), the
>>>> packets that accepted on the internal interface are sent out from the
>>>> Ext1(192.168.0.31) instead of Ext2 (192.168.0.32). It looks like the
>>>> decision about the source address is made based on the IP routing table
>>>> information (?).
>>>> Also, I would like to have an advertised address for at least one
>>>> external interface.
>>>>
>>>> Is it achievable with just one instance of rtpproxy? Or, it is
>>>> necessary to run two rtpproxies in the bridged mode wit configured
>>>> advertize addresses?
>>>>
>>>> Thank you in advance,
>>>> Leonid
>>>>
>>>> _______________________________________________
>>>> Kamailio (SER) - Users Mailing List
>>>> sr-users at lists.kamailio.org
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>> --
>>> Regards,
>>>
>>> David Villasmil
>>> email: david.villasmil.work at gmail.com
>>> phone: +34669448337
>>> _______________________________________________
>>> Kamailio (SER) - Users Mailing List
>>> sr-users at lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20200422/f72e400c/attachment.html>


More information about the sr-users mailing list