Hey Richard,

So that's what I thought too until I saw this in rtpengine logs for one of my test calls:

Dec 3 18:05:47 ashmainrtpe42 rtpengine[8505]: DEBUG: [ep1sbnkk9tikhg4kpmot]: Forward to sink endpoint: 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71:59827 (RTP seq 25423 TS 0)

unless I misunderstood what this line means.

On Fri, Dec 4, 2020 at 9:34 AM Richard Fuchs <rfuchs@sipwise.com> wrote:

On 04/12/2020 09.24, Andrew Chen wrote:
> Hey Richard,
>
> So it is true rtpengine is handling rtp between kamailio and receiver
> (freeswitch). I'm trying to understand if there is a way to not
> forward rtp to any of the ICE candidates in the original INVITE
> request from the client side. In other words, have the client rtp
> forward directly to the rtpengine and not any of the STUN servers (or
> ICE candidates). i honestly thought putting ICE=force in the
> rtpengine_answer would help in this case...but I don't see this part
> working.

But that is what's happening, isn't it? What other media would rtpengine
be sending to the client if not the media received from the other
client? So your A client is sending to rtpengine, and rtpengine is
forwarding that to B, while your B client is also sending to rtpengine,
which then forwards it to A. Where do you not see that working?

Cheers

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users