← Back to team overview

rohc team mailing list archive

Re: rohc performance on lossy media



> I am using Rohc comressor/decomressor pair on a lossy media(sometimes
> at receiver side some packets are lost) and the orderings of the  UDP
> packets are not guaranteed.(packets are not coming in right order all
> the time).
> I am using Unidirectional mode and observe some decomression failures
> about CRC check, malformed packets...
> Any recommendation to overcome these issues?

The ROHC protocol provides several ways to handle packet loss or

a/ Increasing the width of the window used by the W-LSB algorithm
   improves the robustness of the ROHC protocol by sending more bits for
   changing fields. Given a W-LSB width <wlsb_width>, up to
   (<wlsb_width> - 1) packets may be lost without causing additional
   The default width is set to 4 by the ROHC library ; please use the
   rohc_comp_set_wlsb_window_width() function to change the value ; see
   [1] for more details.

b/ Increasing the number of transmissions N required for a changing
   static fields or a changing pattern for a dynamic field ensures that
   the loss of N-1 packets during such a change will cause no
   additional loss.
   The default number of transmissions is set to 3 by the ROHC
   library ; there is no API to change the value at that time, but you
   may change the value of the constant MAX_IR_COUNT in the source file
   src/comp/rohc_comp_internals.h and re-build/re-install the library.

c/ Same as b/ but for lists of extensions headers (such as IPv6
   extension headers, GRE, AH...). Use the function
   rohc_comp_set_list_trans_nr() to change the value ; the default
   value is set to 5 ; see [2] for more details.

d/ You may enable packet/context repair upon CRC failures, so that the
   decompressor tries to fix the context or packet if it detects a
   decompression problem (due to packet loss/reordering for example).
   The feature is disabled by default. Enable it with the function
   rohc_decomp_set_features() and the feature
   ROHC_DECOMP_FEATURE_CRC_REPAIR ; see [3] for more details.

Configuring options a-c is easier if you know the largest number of
consecutive losses that you may expect and/or you want to be protected

Let me know if my explanations are clear enough or if you need more
details. And, of course, let me know if one of the options solves your


[1] documentation of rohc_comp_set_wlsb_window_width():

[2] documentation of rohc_comp_set_list_trans_nr():

[3] documentation of rohc_decomp_set_features():

Follow ups