Problem about RTCPeerConnection
Reported by
cuizhe96...@gmail.com,
Mar 8 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Example URL: Steps to reproduce the problem: 1. I have a desktop application which can video meeting with webbrowser client. It uses geckofx and xulrunner. 2. When I connect using RTCPeerConnection on chrome, Send sdp with "UDP/TLS/RTP/SAVPF". What is the expected behavior? What went wrong? Connection target(application) occurs errors like this. INVALID_SESSION_DESCRIPTION Could not process offer SDP: cause = SDP_PARSE_FAILED | SDP Parsing Error: Warning: Group attribute type unsupported (BUNDLE). | SDP Parsing Error: Warning: Unrecognized attribute (maid-semantic) | SDP Parsing Error: Warning: Transport protocol type unsupported (UDP/TLS/RTP/SAVPF). | SDP Parsing Error: Invalid port format(9) specified for transport protocol (Unsupported), parse failed. 3. How can I fix this problem? Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? N/A Chrome version: 48.0.2564.116 Channel: n/a OS Version: 6.3 Flash Version: Shockwave Flash 20.0 r0
,
Mar 14 2016
Follow up questions for the reporter: a) To be clear, were the errors you mentioned in the "What went wrong" section generated from Chrome, or from the desktop application? b) At least from Chrome, and from the desktop application if you can get it, can you copy/paste (or attach) the full offer and answer? At least in Chrome, you should be able to get this from chrome://webrtc-internals -> setLocalDescription and setRemoteDescription.
,
Mar 24 2016
Friendly ping to the original reporter to answer the questions/requests in comment #2.
,
Mar 28 2016
It's been two weeks since the questions in #2 were posted, and we haven't received a response. Therefore, I'm closing this bug. |
|||
►
Sign in to add a comment |
|||
Comment 1 by yini...@chromium.org
, Mar 10 2016