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.comThanks for the confirmation Harald.
Best Regard,
Ron Menez
ron.menez at entropysolution.com<mailto:ron.menez at entropysolution.com>
On Mar 18, 2018, at 10:17 PM, Harald Welte <laforge at gnumonks.org<mailto:laforge at 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 at gnumonks.org<mailto:laforge at gnumonks.org>> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180323/c46f7e8b/attachment.htm>