all chrome answer sdp like this:
v=0
o=- 6085478416333030883 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video
a=msid-semantic: WMS DqBe4XiXTtcf43SQhEXdOfHhKKtRAnF8GEUz
m=audio 9 UDP/TLS/RTP/SAVPF 0
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:lC9sM/BnFRGrtGRb
a=ice-pwd:f9SdMogUVC+5jOcgzHKN615W
a=fingerprint:sha-256 81:92:9E:A1:25:5B:9C:9F:F3:BE:73:00:82:0F:31:3F:94:D6:E9:DD:EA:D3:6F:63:A5:51:71:B7:E0:9D:EE:63
a=setup:active
a=mid:audio
a=sendrecv
a=rtcp-mux
a=rtpmap:0 PCMU/8000
a=ssrc:2864420842 cname:d0xe8GiQdLcGzxp6
a=ssrc:2864420842 msid:DqBe4XiXTtcf43SQhEXdOfHhKKtRAnF8GEUz 7896b20e-8015-4ad2-81ca-ef31600f4246
a=ssrc:2864420842 mslabel:DqBe4XiXTtcf43SQhEXdOfHhKKtRAnF8GEUz
a=ssrc:2864420842 label:7896b20e-8015-4ad2-81ca-ef31600f4246
m=video 9 UDP/TLS/RTP/SAVPF 107
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:lC9sM/BnFRGrtGRb
a=ice-pwd:f9SdMogUVC+5jOcgzHKN615W
a=fingerprint:sha-256 81:92:9E:A1:25:5B:9C:9F:F3:BE:73:00:82:0F:31:3F:94:D6:E9:DD:EA:D3:6F:63:A5:51:71:B7:E0:9D:EE:63
a=setup:active
a=mid:video
a=sendrecv
a=rtcp-mux
a=rtpmap:107 H264/90000
a=rtcp-fb:107 ccm fir
a=rtcp-fb:107 nack
a=rtcp-fb:107 nack pli
a=rtcp-fb:107 goog-remb
a=fmtp:107 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=ssrc:1651397881 cname:d0xe8GiQdLcGzxp6
a=ssrc:1651397881 msid:DqBe4XiXTtcf43SQhEXdOfHhKKtRAnF8GEUz c005d23d-f1e4-46f1-867f-b5f8be7c4882
a=ssrc:1651397881 mslabel:DqBe4XiXTtcf43SQhEXdOfHhKKtRAnF8GEUz
a=ssrc:1651397881 label:c005d23d-f1e4-46f1-867f-b5f8be7c4882

Any Ideas?

[triage]: hbos@, can you triage and help find an owner?

"when the chrome edition is 53.0.2785.89 m , the chrome work well
but another edition cannot render the remote video, for example , edition 52.0.2743.116 m"
- Does that mean this is working in recent 53+ versions of Chrome? If so this issue has already been fixed?

Is it not working because you're communicating with a version of Chrome that does not have H264 support? It was enabled by default here:
https://chromium.googlesource.com/chromium/src/+/487e16d68766a496d1174e880036e789c927b32d

Is this a problem on the latest version of Chrome?

[triage]: ping wanghb89.

 hbos@
yes, I try the M54, that have such problem !

Thank you for providing more feedback. Adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

wanghb89@gmail.com: just to confirm - you're seeing the problem in M54 as well? Can you share exactly which version you tried? Can you also share a minimized test case that we can try? Like put something up at https://jsfiddle.net/ ?

sorry, I just know how open the chrome webrtc log

my chrome edition is 54.0.2840.34 beta-m 
I show the webrtc decode log,I got this:
h264_decoder_impl.cc(333)] avcodec_decode_video2 error: -1094995529

I test my program on my partner.It work well(I don't read the webrtc decode log,just look it,tomorrow I open the log)

I also test on my firefox.It work well.
can I ask another question:
 why my firefox is can?

I share my package H.264 to rtp program!

Deleted: pakcage.go 1.4 KB

pakcage.go 1.4 KB View Download

I test my programm on my partner computer(chrome:53.0.2785.116 m,OS: win7)

I check the chrome webrtc log, there is no " h264_decoder_impl.cc(333)] avcodec_decode_video2 error: -1094995529"


Does OS have effect on chrome webrtc openH264 config?Or HardWare have effect on?

Depending on machine it could use a hardware or software implementation of H264 decoding. h264_decoder_impl.cc is the SW one. In both cases, it fails to decode/render?

Thank you for providing more feedback. Adding requester "kjellander@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Not sure what more I can ask for, we got the version information.
I'm leaving this to the component owner for now, as our triage process has changed.

Looks like dupe of  issue 645986  to me.