javascript - NW.js: Failed to parse SessionDescription. Failed to parse audio codecs correctly - Stack Overflow

admin管理员组

文章数量:1332345

We are building a video chat with peerjs (Webrtc). We have a nodewebkit version and a chrome version. But for some reason, if chrome start a mediastream to nodewebkit, We get the follow errors in nw.

PeerJS:  Creating RTCPeerConnection.
peer.min.js:1 PeerJS:  Listening for ICE candidates.
peer.min.js:1 PeerJS:  Listening for `negotiationneeded`
peer.min.js:1 PeerJS:  Listening for data channel
peer.min.js:1 PeerJS:  Listening for remote stream
peerJS:  Setting remote description RTCSessionDescription {sdp: "v=0↵o=- 2956768960815374026 2 IN IP4 127.0.0.1↵s…5525 label:87a9904d-945d-4393-ad98-68be98482104↵", type: "offer"}
peer.min.js:1 PeerJS:  ERROR Error: Failed to parse SessionDescription.  Failed to parse audio codecs correctly.
callingManager.js:293 webrtc:Failed to parse SessionDescription.  Failed to parse audio codecs correctly.
peer.min.js:1 PeerJS:  Failed to setRemoteDescription,  Failed to parse SessionDescription.  Failed to parse audio codecs correctly.
8peer.min.js:1 Uncaught SyntaxError: Failed to execute 'addIceCandidate' on 'RTCPeerConnection': The ICE candidate could not be added.

So the error is:

Error: Failed to parse SessionDescription.  Failed to parse audio codecs correctly.

nodewebkit to Chrome works well.

Nw Version: v0.12.3 Chrome version: 46

Is this a media condec problem? Can anyone help? Thank you!

We are building a video chat with peerjs (Webrtc). We have a nodewebkit version and a chrome version. But for some reason, if chrome start a mediastream to nodewebkit, We get the follow errors in nw.

PeerJS:  Creating RTCPeerConnection.
peer.min.js:1 PeerJS:  Listening for ICE candidates.
peer.min.js:1 PeerJS:  Listening for `negotiationneeded`
peer.min.js:1 PeerJS:  Listening for data channel
peer.min.js:1 PeerJS:  Listening for remote stream
peerJS:  Setting remote description RTCSessionDescription {sdp: "v=0↵o=- 2956768960815374026 2 IN IP4 127.0.0.1↵s…5525 label:87a9904d-945d-4393-ad98-68be98482104↵", type: "offer"}
peer.min.js:1 PeerJS:  ERROR Error: Failed to parse SessionDescription.  Failed to parse audio codecs correctly.
callingManager.js:293 webrtc:Failed to parse SessionDescription.  Failed to parse audio codecs correctly.
peer.min.js:1 PeerJS:  Failed to setRemoteDescription,  Failed to parse SessionDescription.  Failed to parse audio codecs correctly.
8peer.min.js:1 Uncaught SyntaxError: Failed to execute 'addIceCandidate' on 'RTCPeerConnection': The ICE candidate could not be added.

So the error is:

Error: Failed to parse SessionDescription.  Failed to parse audio codecs correctly.

nodewebkit to Chrome works well.

Nw Version: v0.12.3 Chrome version: 46

Is this a media condec problem? Can anyone help? Thank you!

• javascript
• google-chrome
• webrtc
• node-webkit
• peerjs

Share Improve this question Follow edited Oct 23, 2015 at 11:30 SaschaDeWaal asked Oct 22, 2015 at 15:16 SaschaDeWaalSaschaDeWaal 13922 silver badges1818 bronze badges

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 10

Chrome 46 changed the protocol in the SDP m-line from "RTP/SAVPF" to "UDP/TLS/RTP/SAVPF". It seems node-webkit is on a really old webrtc version (>1 year) that can't deal with this.

This has been announced for quite a while. See https://twitter./juberti/status/656535175635963904 et al.

Munge your SDP and replace "UDP/TLS/RTP/SAVPF" with "RTP/SAVPF".

本文标签： javascriptNWjs Failed to parse SessionDescription Failed to parse audio codecs correctlyStack Overflow