This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Ron ron.menez at entropysolution.comHi Support, In Half Rate configuration of OSMO-BSC, is there a way to used ETSI TS 101 318 standard for its RTP Payload Format? As per testing, the RTP Payload format used by OSMO is RFC5993. Can this be configured in OSMO-BSC or OSMO-BTS-TRX? Or the configuration of this is hard coded? Logs from OSMO-BTS-TRX: [0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) [0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14) TIA! Best Regard, Ron Menez ron.menez at entropysolution.com<mailto:ron.menez at entropysolution.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180318/212c22c6/attachment.htm>