[SR-Users] rtpproxy_manage and AWS

[Daniel-Constantin Mierla]

Hello,

afaik, one rtpproxy instance can listen on a single IP for RTP traffic,
or two if started in bridging mode. Typically 0.0.0.0 is about listening
on any and in such cases applications can have different behaviour. If
you want a single RTP relay to listen on many ip addresses and just
forward rtp or do bridging, then look at rtpengine, is more flexible
with these options (at least compared to rtpproxy from 2-3 years ago,
when I used it more, because since its package was removed from debian
stable, no longer having the convenience of apt install for small voip
systems, I just deploy rtpengine).

Cheers,
Daniel

On 24.09.20 22:27, Aymeric Moizard wrote:
> Hi,
>
> A bit of debug in rtpproxy: I found out that if I use  -l
> 10.10.111.234 instead of  -l 0.0.0.0 in the command line, it's working
> as expected.
>
> I'm not able to understand if this is a bug, or an expected behavior.
>
> Sorry that I answered my question alone ;)
> Regards
> Aymeric
>
> Le jeu. 24 sept. 2020 à 17:49, Aymeric Moizard <amoizard at gmail.com
> <mailto:amoizard at gmail.com>> a écrit :
>
>     A bit more information on the rtpproxy and kamailio exchange: this
>     is what I receive on rtpproxy (2.1.0)
>
>     DBUG:GLOBAL:get_command: received command "11479_4 Uc18,8,0,101
>     109865504 90.66.177.103 30250 4178279503;1"
>     INFO:GLOBAL:rtpp_command_ul_handle: new IPv4/IPv4 session
>     109865504, tag 4178279503;1 requested, type strong
>     INFO:109865504:rtpp_command_ul_handle: new session on IPv4 port
>     51694 created, tag 4178279503;1
>
>     Regards,
>     Aymeric
>
>
>     Le jeu. 24 sept. 2020 à 15:33, Aymeric Moizard <amoizard at gmail.com
>     <mailto:amoizard at gmail.com>> a écrit :
>
>
>         Hi,
>
>         I have 2 hosts on AWS behind NAT:
>
>         One with rtpproxy:
>
>         /usr/local/bin/rtpproxy -f -p /run/rtpproxy/rtpproxy.pid -s
>         udp:0.0.0.0:31500 <http://0.0.0.0:31500> -A 15.236.230.177
>         <http://15.236.230.177/15.236.230.177> -l 0.0.0.0
>         <http://0.0.0.0/0.0.0.0> -m 35000 -M 65000 -d DBUG:LOG_LOCAL5
>         -u rtpproxy:rtpproxy -F
>
>         The other one, with a kamailio and using
>         only rtpproxy_manage(); without parameters.
>
>         I'm surprised because in my SDP being modified, kamailio is
>         replacing with its KAMILIO private IP. (not the rtpproxy one)
>
>         I see that rtpproxy and kamailio are exchanging data. Nothing
>         obvious is coming out.
>
>         Any obvious mistakes?
>         Anything you need to help?
>         Should I switch to another rtp engine?
>
>         Regards
>         Aymeric
>
>         -- 
>         Antisip - http://www.antisip.com <http://www.antisip.com>
>
>
>
>     -- 
>     Antisip - http://www.antisip.com <http://www.antisip.com>
>
>
>
> -- 
> Antisip - http://www.antisip.com <http://www.antisip.com>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20200925/fca223fa/attachment.htm>