Closed Bug 896439 Opened 11 years ago Closed 11 years ago

Random error: "Unable to set remote offer description : INTERNAL_ERROR Could not process offer SDP; cause = ERR"

Categories

(Core :: WebRTC: Signaling, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 896429

People

(Reporter: standard8, Assigned: ehugg)

References

Details

Attachments

(1 file)

Attached file remote-desc-fail.zip
[This may be related to bug 896429]

We've been seeing some random errors on our Talkilla automated tests, and I've just been trying to get some more information out.

The issue we've seen that I'm filing here is during trying to create a peer connection with only a data channel. We are effectively doing:

1) Create a new peer connection
2) Create a new data channel on the pc, with id = 0, negotiated = true
3) call createOffer
4) Send offer to the other side, then on the other side (same machine):

a) create peer connection
b) create new data channel on the pc, with id = 0, negotiated = true
c) call setRemoteDescription with the offer received from the other side.

We've overridden media.peerconnection.default_iceservers to be [] and media.peerconnection.use_document_iceservers to be false in preferences.

The error seen on the console is at the receiving end and states:

[13:55:19.168] "Unable to set remote offer description : INTERNAL_ERROR Could not process offer SDP; cause = ERR"

The SDP is:

v=0o=Mozilla-SIPUA-25.0a1 3877 0 IN IP4 0.0.0.0s=SIP Callt=0 0a=ice-ufrag:ef3e236ca=ice-pwd:9a973da45f26f8607af88b3a38ae78b0a=fingerprint:sha-256 75:18:F4:35:4F:A5:65:BB:D9:1B:2D:00:5C:80:F8:20:79:22:43:69:F3:7E:13:61:E6:82:DA:A6:DE:E2:3F:38m=application 65467 DTLS/SCTP 5000 c=IN IP4 192.168.1.3a=fmtp:5000 protocol=webrtc-datachannel;streams=16a=sendrecva=candidate:0 1 UDP 2113601791 192.168.1.3 65467 typ hosta=candidate:0 2 UDP 2113601790 192.168.1.3 51315 typ host

Attached are the signaling:6 logs for both sides of the failure.
See Also: → 896429
Found these in the first log:

493580288[121c952d0]: [GSM Task|sdp_config] sdp_config.c:27: SDP: Invalid Config pointer: 0x0 (magic=0x0)
493580288[121c952d0]: [GSM Task|ccsip] ccsip_sdp.c:120: SIP : sipsdp_create : SDP allocation failure

and they come before this:
493432832[121c951a0]: [SIPStack task|sdp_config] sdp_config.c:101: SDP: Initialized config pointer: 0x104520be0 (magic=0xABCDABCD)

Which leads me to believe it's the same problem as Bug 896429

Not going to mark as dupe until I figure out a solution.
Assignee: nobody → ethanhugg
Convinced now this is the same problem as Bug 896429
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: