Project

General

Profile

Actions

Bug #4734

closed

Same comportment than BUG #4461 with lastest build

Added by cboutin over 3 years ago. Updated 7 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
osmo-bts-trx
Target version:
-
Start date:
08/28/2020
Due date:
% Done:

0%

Spec Reference:

Description

Hi guys,

On a fresh install with lastest build osmo-bts-trx + osmo-trx-uhd with b210, I got same "RTP clock out of sync with lower layer" than in BUG #4461.

When we have a call:

<0000> rsl.c:813 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) (ss=0) SDCCH Tx CHAN ACT ACK
<0011> lapd_core.c:935 (dl=0x7f94447f96e8) Store content res.
<0000> rsl.c:813 (bts=0,trx=0,ts=1,pchan=TCH/F) (ss=0) TCH_F Tx CHAN ACT ACK
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1517420->1517390)
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0011> lapd_core.c:1506 (dl=0x7f9444816db8) N(S) sequence error: N(S)=0, V(R)=1 (state LAPD_STATE_MF_EST)
<0011> lapd_core.c:1506 (dl=0x7f9444816db8) N(S) sequence error: N(S)=0, V(R)=1 (state LAPD_STATE_MF_EST)
<0000> rsl.c:813 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) (ss=1) SDCCH Tx CHAN ACT ACK
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0004> measurement.c:644 (bts=0,trx=0,ts=1,ss=0) Incorrect number of SUB measurements detected! (4 vs exp 3)
<0011> lapd_core.c:935 (dl=0x7f94447fcfa0) Store content res.
<0000> rsl.c:813 (bts=0,trx=0,ts=2,pchan=TCH/F) (ss=0) TCH_F Tx CHAN ACT ACK
<0000> rsl.c:792 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) (ss=0) SDCCH Tx CHAN REL ACK
<000e> l1sap.c:143 (bts=0,trx=0,ts=2,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1517936->1517906)
<0011> lapd_core.c:1506 (dl=0x7f9444834488) N(S) sequence error: N(S)=0, V(R)=1 (state LAPD_STATE_MF_EST)
<0011> lapd_core.c:1506 (dl=0x7f9444834488) N(S) sequence error: N(S)=1, V(R)=2 (state LAPD_STATE_MF_EST)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 1440 vs 160 (1518274->1518313)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1518313->1518283)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 1440 vs 160 (1518283->1518322)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1518326->1518296)
<0000> rsl.c:792 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) (ss=1) SDCCH Tx CHAN REL ACK
<0011> lapd_core.c:1506 (dl=0x7f9444834488) N(S) sequence error: N(S)=2, V(R)=3 (state LAPD_STATE_MF_EST)
<0011> lapd_core.c:1506 (dl=0x7f9444816db8) N(S) sequence error: N(S)=1, V(R)=2 (state LAPD_STATE_MF_EST)
<0011> lapd_core.c:1506 (dl=0x7f9444816db8) N(S) sequence error: N(S)=1, V(R)=2 (state LAPD_STATE_MF_EST)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 1440 vs 160 (1520389->1520428)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1520432->1520402)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 1440 vs 160 (1520402->1520441)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1520441->1520410)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 1440 vs 160 (1520419->1520458)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1520458->1520428)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 1440 vs 160 (1520428->1520467)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 82594400 vs 160 (1520562->1520532)
<000e> l1sap.c:143 (bts=0,trx=0,ts=1,ss=0) RTP clock out of sync with lower layer: 1440 vs 160 (1520532->1520571)
...

OsmoBTS# show lchan sum
BTS 0, TRX 0, Timeslot 0 CCCH+SDCCH4, Lchan 4, Type CCCH, State ACTIVE - RXL-FULL-ul: 110 dBm
BTS 0, TRX 0, Timeslot 1 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - RXL-FULL-ul: -61 dBm
BTS 0, TRX 0, Timeslot 2 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - RXL-FULL-ul: -47 dBm
OsmoBTS# show lchan 0 0 1 0
BTS 0, TRX 0, Timeslot 1, Lchan 0: Type TCH_F
State: ACTIVE
BS Power: 3 dBm, MS Power: 16 dBm
Channel Mode / Codec: FR or HR
Bound IP: 127.0.0.1 Port 16400 RTP_TYPE2=0 CONN_ID=0
Conn. IP: 127.0.0.1 Port 4068 RTP_TYPE=3 SPEECH_MODE=0x00
LAPDm SAPIs: DCCH 0
, SACCH --
Valid System Information: 0x00000060
MS Timing Offset: 63, propagation delay: 1 symbols
Radio Link Failure Counter 'S': 32
OsmoBTS# show lchan 0 0 2 0
<cr>
OsmoBTS# show lchan 0 0 2 0
BTS 0, TRX 0, Timeslot 2, Lchan 0: Type TCH_F
State: ACTIVE
BS Power: 3 dBm, MS Power: 16 dBm
Channel Mode / Codec: FR or HR
Bound IP: 127.0.0.1 Port 16402 RTP_TYPE2=0 CONN_ID=0
Conn. IP: 127.0.0.1 Port 4076 RTP_TYPE=3 SPEECH_MODE=0x00
LAPDm SAPIs: DCCH 0
, SACCH --
Valid System Information: 0x00000060
MS Timing Offset: 63, propagation delay: -1 symbols
Radio Link Failure Counter 'S': 32
OsmoBTS#

Thanks for your help.


Related issues

Related to OsmoBTS - Bug #4461: RTP clock out of sync with lower layerResolveddexter03/19/2020

Actions
Actions #1

Updated by laforge over 3 years ago

  • Related to Bug #4461: RTP clock out of sync with lower layer added
Actions #2

Updated by fixeria about 1 year ago

  • Status changed from New to Feedback
  • Assignee set to cboutin

@cboutin, can you confirm this is still a problem with recent osmo-bts and osmo-trx?
There has been a lot of development going on during the last few years, so it might have been fixed.

Actions #3

Updated by pespin 7 months ago

  • Status changed from Feedback to Rejected

This ticket is from 3 years ago and there has been no answer for the last 6 months, hence rejecting it.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)