Decompression failure caused by RTP stream with lost packet but irregular IP-ID
Bug #1080055 reported by
Didier Barvaux
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
rohc | Status tracked in Rohc-main | |||||
1.3.x |
Invalid
|
Undecided
|
Didier Barvaux | |||
1.4.x |
Invalid
|
Undecided
|
Didier Barvaux | |||
Rohc-1.5.x |
Fix Released
|
High
|
Didier Barvaux | |||
Rohc-main |
Fix Released
|
High
|
Didier Barvaux |
Bug Description
The attached PCAP file contains a RTP stream with a lost packet (SN = 8) and next packet contains an irregular IP-ID:
...
packet #7: SN = 7, TS = 350, IP-ID = 7
packet #8 is lost, should be SN = 8, TS = 400, IP-ID = 8
packet #9: SN = 9, TS = 450, IP-ID = 8
The IP-ID of packet #9 should be 9 instead of 8. The compressor chooses packet UO-1-ID instead of UOR-2-ID. The decompressor then fails to decompress the packet.
To post a comment you must log in.
Fixed in main branch. See http:// bazaar. launchpad. net/~didier- barvaux/ rohc/main/ revision/ 572