rohc team mailing list archive

[Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>]

Hi again,

Making my concerns more real, I am pinging here seeing the IR first time only.

[ 2023.847886] (Wrn):Sending IR
[ 2024.300407] (Wrn):Sending IR
[ 2024.305257] (Wrn):Feedback queued 5
64 bytes from 192.168.0.2: seq=0 ttl=64 time=101
[ 2024.311619] (Wrn):1.718 ms
[ 2024.312191] (Wrn) Feedback sent!
[ 2024.329481] (Wrn):Feedback receive 5
[ 2024.336070] Feedback data: f4 2e aa 11 82
64 bytes from 192.168.0.2: seq=1 ttl=64 time=603.621 ms
64 bytes from 192.168.0.2: seq=2 ttl=64 time=470.661 ms
64 bytes from 192.168.0.2: seq=3 ttl=64 time=500.293 ms
64 bytes from 192.168.0.2: seq=4 ttl=64 time=530.625 ms
64 bytes from 192.168.0.2: seq=5 ttl=64 time=560.058 ms
64 bytes from 192.168.0.2: seq=6 ttl=64 time=590.550 ms
64 bytes from 192.168.0.2: seq=7 ttl=64 time=473.033 ms
64 bytes from 192.168.0.2: seq=8 ttl=64 time=502.544 ms
64 bytes from 192.168.0.2: seq=9 ttl=64 time=532.960 ms
64 bytes from 192.168.0.2: seq=10 ttl=64 time=562.420 ms
64 bytes from 192.168.0.2: seq=11 ttl=64 time=444.888 ms
64 bytes from 192.168.0.2: seq=12 ttl=64 time=475.333 ms
64 bytes from 192.168.0.2: seq=13 ttl=64 time=504.803 ms
64 bytes from 192.168.0.2: seq=14 ttl=64 time=534.627 ms
64 bytes from 192.168.0.2: seq=15 ttl=64 time=564.732 ms
64 bytes from 192.168.0.2: seq=16 ttl=64 time=447.184 ms
64 bytes from 192.168.0.2: seq=17 ttl=64 time=477.670 ms
64 bytes from 192.168.0.2: seq=18 ttl=64 time=507.109 ms
64 bytes from 192.168.0.2: seq=19 ttl=64 time=536.570 ms
64 bytes from 192.168.0.2: seq=20 ttl=64 time=566.975 ms
64 bytes from 192.168.0.2: seq=21 ttl=64 time=449.446 ms
64 bytes from 192.168.0.2: seq=22 ttl=64 time=479.788 ms
64 bytes from 192.168.0.2: seq=23 ttl=64 time=510.292 ms
64 bytes from 192.168.0.2: seq=24 ttl=64 time=539.719 ms
…

Didn’t the IR being sent message after 12s and my CHANGE_TO_FO_TIME is 6000, CHANGE_TO_IR_TIME is 12000.

Init call of rohc_comp_set_periodic_refreshes_time happens after the following init sequence of calls,

rohc_comp_new2
rohc_comp_set_traces_cb2
rohc_comp_disable_profiles
rohc_comp_set_mrru
rohc_comp_set_rtp_detection_cb
rohc_decomp_new2
rohc_decomp_set_traces_cb2
rohc_decomp_enable_profiles
rohc_decomp_set_features

Regards,
Yakir

From: Rohc <rohc-bounces+yakir.matusovsky=mimomax.com@xxxxxxxxxxxxxxxxxxx> on behalf of Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>
Date: Friday, 8 June 2018 at 2:10 PM
To: ROHC Library <rohc@xxxxxxxxxxxxxxxxxxx>
Subject: [Rohc] Compression forced down to IR state
Resent-From: Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>

Hey

To clarify please, I am using functions like
rohc_comp_set_periodic_refreshes and rohc_comp_set_periodic_refreshes_time
to force compressor to go down once in a while.

Should this after compressor sends an IR packet, generate a feedback from decompressor side? In other words, should I expect feedback sent periodically from decompressor every CHANGE_TO_IR_COUNT/TIME pkts/ms?

Regards
Yakir