rohc

Problem with RTP streams with Padding bit set

Bug #1092660 reported by Didier Barvaux
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rohc
Status tracked in Rohc-main
1.3.x
Won't Fix
Medium
Didier Barvaux
rohc 1.3.5
1.4.x
Won't Fix
Medium
Didier Barvaux
rohc 1.4.3
Rohc-1.5.x
Won't Fix
Medium
Didier Barvaux
rohc 1.5.2
Rohc-main
Fix Released
Medium
Didier Barvaux
rohc 1.6.0

Bug Description

If one RTP stream has the RTP Padding (P) bit set for one (or more) of its packet, the ROHC library fails to compress/decompress it correctly if one IR/IR-DYN packet type is not select by chance.

Extension 3 (and one of the packet type that supports extension 3) is required to transmit the RTP Padding bit if the IR or IR-DYN packet type is not select for another reason.

The attached PCAP file contains one RTP stream whose 8th packet got Padding bit set.

Tags: library rtp
Revision history for this message
Didier Barvaux (didier-barvaux) wrote :
Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Confirmed on main branch.

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Fixed on main branch. See http://bazaar.launchpad.net/~didier-barvaux/rohc/main/revision/631

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Additional fix on main branch: The RTP Padding bit shall be stored in the compressor context because it is a STATIC field. It does not work as the RTP Marker field that is set to 1 only if transmitted in the ROHC header. If the RTP Padding bit is not present in the ROHC header, the one from the context is used.

Enhance the bug1092660-rtp-padding-bit non-regression test to cover the case where the Padding field is set again to 0 after being set to 1.

See http://bazaar.launchpad.net/~didier-barvaux/rohc/main/revision/635

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Bug won't be fixed on branch 1.5.x: too invasive and compatibility between 1.5.x releases would be broken.
See http://bazaar.launchpad.net/~didier-barvaux/rohc/1.5.x/revision/569

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Bug won't be fixed on branch 1.4.x: too invasive and compatibility between 1.4.x releases would be broken.
See http://bazaar.launchpad.net/~didier-barvaux/rohc/1.4.x/revision/368

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Bug won't be fixed on branch 1.3.x: too invasive and compatibility between 1.3.x releases would be broken.
See http://bazaar.launchpad.net/~didier-barvaux/rohc/1.3.x/revision/217

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.