Failed to unprotect SRTP / RTP packet

567 views
Skip to first unread message

Fernando Bernal

unread,
Dec 21, 2015, 4:59:08 AM12/21/15
to discuss-webrtc

Hi all,


I'm having a problem unprotecting the SRTP RTP streams, anyone knows something about this problem? Basically if I use VP8 codec I have no problem, but if I use H264 enconding I have a lot of traces showing this error. the video is delayed and it is decoded wrong.


Warning(srtpfilter.cc:576): Failed to unprotect SRTP packet, err=9

Error(channel.cc:642): Failed to unprotect video RTP packet: size=1149, seqnum=14794, SSRC=2664851050


is there any reason that the used codec can influence on this?


Thanks,

Fernando.

Christoffer Jansson

unread,
Dec 21, 2015, 5:05:01 AM12/21/15
to discuss-webrtc, pb...@google.com, hb...@google.com
+Peter Boström +Henrik Boström do any of you have an idea of what this could be?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/e138f0e5-78f8-4b92-99cc-a307cce269f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Marcello Vezzelli

unread,
Dec 21, 2015, 5:05:01 AM12/21/15
to discuss...@googlegroups.com
Il 21/12/2015 10:59, Fernando Bernal ha scritto:

Hi all,

I'm having a problem unprotecting the SRTP RTP streams, anyone knows something about this problem? Basically if I use VP8 codec I have no problem, but if I use H264 enconding I have a lot of traces showing this error. the video is delayed and it is decoded wrong.


Hi,
can you give more details about your environment? Are you testing with browsers or just WebRTC library?

regards
Marcello Vezzelli

Fernando Bernal

unread,
Dec 21, 2015, 5:17:25 AM12/21/15
to discuss-webrtc
I'm using the C++ webrtc implementation, just testing the library and adding a H264 codec by myself. I'm no using browser just an application. The H264 codec have been implemented using Gstreamer.

Peter Boström

unread,
Dec 21, 2015, 8:37:01 AM12/21/15
to discuss-webrtc
I'm not sure if repeat timestamps are enough to be considered a replay attack, but are you settings _timeStamp in the outgoing EncodedImage? Not sure what the implications of missing fields are, but you can compare to the MediaCodec implementation: https://chromium.googlesource.com/external/webrtc/+/9d3ab61325c5ed216ea52bc829f1d8c81347459b/talk/app/webrtc/java/jni/androidmediaencoder_jni.cc#908

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

Fernando Bernal

unread,
Dec 21, 2015, 9:03:01 AM12/21/15
to discuss-webrtc
Yes, I'm setting the timestamp param and also the capture_time_ms_
Reply all
Reply to author
Forward
0 new messages