4 Dec
2020
4 Dec
'20
6:39 p.m.
So my next question would be:
My 200 OK back to the client should have rtpengine as the only ICE
candidate. Shouldn't it use that one instead?
On Fri, Dec 4, 2020 at 10:18 AM Richard Fuchs <rfuchs(a)sipwise.com> wrote:
On 04/12/2020 09.40, 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.*
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.
I think you did. It means rtpengine has received a media packet from one
side and has forwarded it to the other side. Of course it's one of the
ICE candidates from the SDP because that's where the peer said it wants
to receive the media from rtpengine.
Cheers
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users