Hi Juha, thanks for your answer. I just switched from rtpproxy to rtpengine, like you mentioned. It works the usual way (RTP proxied over server) and to me it appears exactly the same as rtpproxy, am I right? Is there any major difference between them? It didn't solve my problem though. I am experiencing an odd issue using Linphone on Android and ICE/STUN, especially when calling another Linphone on a desktop behind the same NAT... My primary goal is to establish a direct connection between two UAs no matter what (NAT, no NAT, 3g network, etc..) Desktop versions work fine with each other, it's just the Android client.. so maybe this is for another thread or mailing list :) But I wanted to know if there is a better way than rtpproxy/rtpengine for ICE.. Thank you! Filip On 16.04.2015 07:52, Juha Heinanen wrote:

Yes I did, I am loading the mediaproxy.so module now instead of rtpproxy.so, I am setting the modparam sock for rtpengine to the locally running instance of rtpengine.. and in the "general routing logic" of kamailio.cfg I am calling rtpengine_manage(), where there was rtpproxy_manage() before. Does rtpengine manage ICE without any flags in rtpengine_manage()? Or shall there be any flags to have it running? When I set no flags, RTP packets get all proxied over the server with no media release.. The only flag that worked like I need is rtpengine_manage("ICE=force-relay"), but this is not working for 100% of all call attempts with sometimes no audio/video on both ends.. Mainly the Android Linphone client doesn't do a very good job regarding ICE I guess.. On 16.04.2015 14:29, Daniel Tryba wrote: