Skip to content

Would there be a conflict between addIceCandidate Javascript and SIPSorcery? #5

Description

@dorathoto

I tried to do just the initial handshake with signalR, but I can't complete the ICE candidate.

Error:
OperationError: Failed to execute 'addIceCandidate' on 'RTCPeerConnection': Error processing ICE candidate
IN:
main.js
peerConnection.addIceCandidate(candidate);

I thought it could be a RACE condition problem, but it wasn't.

It could be a serialization problem, but apparently not. My candidate serialized by Javascript:

{ 
"candidate": "candidate:42032162 1 udp 2113940223 2804:7f0:9101:239d:895f:27e1:f0b9:da9a 64082 typ host generation 0", 
"sdpMid": "0", 
"sdpMLineIndex": 0, 
"usernameFragment": "PXDL"
}

example from https://webrtc.github.io/samples/src/content/peerconnection/pc1/:

{ 
"candidate": "candidate:437944273 1 udp 2122129151 172.27.80.1 53470 typ host generation 0 ufrag KeeV network-id 1", 
"sdpMid": "0", 
"sdpMLineIndex": 0, 
"usernameFragment": "KeeV"
}

Would there be a conflict between addIceCandidate Javascript and SIPSorcery?

I made a basic example to simulate.

https://github.com/dorathoto/HandShake_SignalR_SIPSorcery

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions