Sure...I understand ICE has its own setup workflow than SIP but it's also important that rtpengine uses the rtp path that's negotiated in the SIP or else it can cause confusion (to those who don't understand ICE very well like me).
On 04/12/2020 13.36, Andrew Chen wrote:
> Hmm..that's interesting. You would guess that the rtpengine binary
> process shouldn't start connecting ICE candidates once the SIP part is
> fully negotiated, which should trigger the rtpengine module on the
> Kamailio to tell rtpengine binary.."ok..you can start associating now..."
Not really. Why would you think that? ICE and SIP are really largely
unrelated, and ICE processing starts as soon as possible so that media
can flow as soon as possible. Any delay in ICE processing leads to
delays in establishing the call or the media flows. (Trickle ICE exists
partly for that reason.) In particular early media would break if ICE
had to wait for SIP to finish.
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.*