Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong RTP header extension parsing when it includes a direction

See original GitHub issue

The following valid RTP header extension attribute:

a=extmap:1/sendonly urn:ietf:params:rtp-hdrext:ssrc-audio-level

produces the following parsed object:

{
  uri:   "urn:ietf:params:rtp-hdrext:ssrc-audio-level",
  value: "1/sendonly"
}

It’s wrong. value should be 1 (numeric) and a new direction key should be sendonly.

BNF spec: https://tools.ietf.org/html/rfc5285#section-7

Issue Analytics

State:
Created 7 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

cluxcommented, Feb 16, 2017

Yeah, ended up bumping the major just to be sure. Hate it when patch bumps break my code underneath me 😃

sdp-transform@2.0.0 out now.

Thanks again.

0reactions

ibccommented, Feb 16, 2017

Great, thanks!

Top Results From Across the Web

A General Mechanism for RTP Header Extensions RFC 8285

Standards Track [Page 2] RFC 8285 RTP Header Extensions October 2017 1. ... A direction attribute MAY be included in an "extmap"; without...

parse/read video orientation from extended headers #278

Is there a reason reading the video orientation from the rtp extended header is not included in mediasoup v2; All the other extended...

RFC 3550: RTP: A Transport Protocol for Real-Time Applications

To cope with these impairments, the RTP header contains timing information and a sequence number that allow the receivers to reconstruct the timing...

rtp.h File Reference - Janus WebRTC Server - Meetecho

Helper to parse a dependency descriptor RTP extension (https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension) ...

Question on the structure of RTP Extension headers as ...

This probably dates back to RFC 3550. Specifying the length field explicitly like this allows clients that do not understand extensions to ...