Re: [SR-Users] how to always use rtpproxy-ng and rtpengine to relay rtp packets

Hi Andrew There is a condition in the NATMANAGE route which tests whether or not to apply rtpproxy_manage() : if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; One way to force this is to make sure that FLT_NATS is always set. That can be done in the NATDETECT route by moving setflag(FLT_NATS) outside of the if(nat_uac_test) condition and putting it just before the return statement, so the flag is always set. Another way would be to remove or comment out the if "!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return;" line from NATMANAGE so that the the rtp_manage() is always called. It might be worth your while upgrading to the 4.2 branch which has renamed the rtpproxy-ng module to rtpengine and made the options in the call to rtpengine_manage() more readable. Depending on why you always want to run the rtp proxy ... you might also want to set : rtpengine_manage(replace-session-sonnection replace-origin ICE=force-relay) to ensure that media always goes through your media proxy and no other connections are negotiated between the endpoints. On 13/10/14 08:36, andrew wrote: