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@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 -A 15.236.230.177 -l 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


--
Antisip - http://www.antisip.com