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.

On Fri, Dec 4, 2020 at 9:20 AM Richard Fuchs <rfuchs@sipwise.com> wrote:
On 04/12/2020 09.11, Andrew Chen wrote:
> So for Yuriy's comment:
>
> I did issue ICE=force parameter but, as you can see my paste, it's
> still sending RTP sequence packets to the ICE candidate, which is not
> what I want to do.
>
> Richard,
>
> So our current setup is this:
>
> SIP
> client -> kamailio -> freeswitch
> RTP
> client -> freeswitch
>
> What I want to accomplish is this:
>
> SIP
> client -> kamailio -> freeswitch
> RTP (bypass ICE)
> client -> rtpengine -> freeswitch

I still don't understand. What does "bypass ICE" mean?

If you see rtpengine forwarding media packets as per the log you posted,
what makes you think that media is not going through rtpengine?

Cheers


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


--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)


*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*