Actions
Bug #3299
closedosmo_ortp: scheduler is not started
Start date:
05/29/2018
Due date:
% Done:
100%
Spec Reference:
Description
Apparently the scheduler of ortp is not started. Presumably older versions did not require starting the scheduler explicitly, so we just do not call the relevant function:
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(101600): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(80640): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(101760): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(80800): ERROR! Tue May 29 15:41:00 2018 <0000> rsl.c:2633 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP Tue May 29 15:41:00 2018 <0000> rsl.c:2550 (bts=0,trx=0,ts=3,ss=0) chan_num:11 Tx MEAS RES valid(2), flags(03) Tue May 29 15:41:00 2018 <0000> rsl.c:2568 (bts=0,trx=0,ts=3,ss=0) Send Meas RES: NUM:20, RXLEV_FULL:63, RXLEV_SUB:63, RXQUAL_FULL:0, RXQUAL_SUB:0, MS_PWR:56, UL_TA:0, L3_LEN:18, TimingOff:0 Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(101920): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 Cannot use the scheduled mode: the scheduler is not started. Call ortp_scheduler_init() at the begginning of the application.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 can't guess current timestamp because session is not scheduled.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:145 osmo-ortp(16386): timestamp_jump, new TS 0, resyncing Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(80960): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 Cannot use the scheduled mode: the scheduler is not started. Call ortp_scheduler_init() at the begginning of the application.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 can't guess current timestamp because session is not scheduled.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:145 osmo-ortp(16384): timestamp_jump, new TS 0, resyncing Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102080): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81120): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102240): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81280): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102400): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81440): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102560): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81600): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102720): ERROR! Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(82080): ERROR!
Actions