Hi 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@entropysolution.commailto:ron.menez@entropysolution.com
Hi ron,
On Sun, Mar 18, 2018 at 02:05:56PM +0000, Ron wrote:
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.
This is correct.
Can this be configured in OSMO-BSC or OSMO-BTS-TRX? Or the configuration of this is hard coded?
No, this is not configurable at this point. If it should be added, my guess would be that it's best to add to osmo-mgw so it could serve as an "entry point" converting between different RTP payload formats, avoiding that we have to implement it natively in all programs (such as osmo-bts). But in any case, no matter where it's added, somebody would have to develop the related code first and contribute it.
Thanks for the confirmation Harald.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Mar 18, 2018, at 10:17 PM, Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> wrote:
Hi ron,
On Sun, Mar 18, 2018 at 02:05:56PM +0000, Ron wrote: 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.
This is correct.
Can this be configured in OSMO-BSC or OSMO-BTS-TRX? Or the configuration of this is hard coded?
No, this is not configurable at this point. If it should be added, my guess would be that it's best to add to osmo-mgw so it could serve as an "entry point" converting between different RTP payload formats, avoiding that we have to implement it natively in all programs (such as osmo-bts). But in any case, no matter where it's added, somebody would have to develop the related code first and contribute it.
-- - Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
-
Harald Welte -
Ron