4 Dec
2020
4 Dec
'20
10:24 p.m.
Ok..that's interesting to know. Thanks for your input Richard. This helps
a lot.
On Fri, Dec 4, 2020 at 2:18 PM Richard Fuchs <rfuchs(a)sipwise.com> wrote:
On 04/12/2020 14.04, Andrew Chen wrote:
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
achen@ <achen(a)thinkingphones.com>fuze.com
--
*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.*
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).
There is no RTP path negotiated through SIP. There is only a number of
possible paths, which are compiled from the list of candidates that each
side advertises. ICE then checks which paths work, and then finally
chooses the one with the highest priority.
The only way to have a single media path that is negotiated through SIP
is if you don't use ICE.
Cheers
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users