logging SDP from setRemoteDescription / setLocalDescription in a format suitable for text2pcap

NEW
Unassigned

Status

()

P4
enhancement
Rank:
35
2 years ago
a year ago

People

(Reporter: fippo, Unassigned)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
the pcap files that can be generated from https://bugzilla.mozilla.org/show_bug.cgi?id=1343640 could be enhanced by adding the SDP from setRemoteDescription/setLocalDescription (and onicecandidate/addicecandidate) to it, in particular from renegotiations.

Wireshark seems to be fairly happy to interpret things as SIP and dissects things nicely when prefixing the SDP with this:
  'INVITE sip:something-that-identifies-the-pc SIP/2.0\r\nContent-Type:application/sdp\r\nContent-Length: ...\r\n\r\n'

or a 'SIP/2.0 200 OK' instead of the invite. For extra fun, increment Cseq for renegotiation.
Dumping a text protocol into hex... :-(

I'm wondering if there is another way then adding fake SIP messages to get Wireshark to pickup the SDP. Maybe just raw SDP in UDP... the Wireshark disectors are suppose to usable on anything you throw at them, so I don't see why it should be limited to SIP.
backlog: --- → webrtc/webaudio+
Rank: 35
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.