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/.
Harald Welte laforge at gnumonks.orgHi Holger,
On Fri, Mar 10, 2017 at 03:19:28PM +0100, Holger Freyther wrote:
> as part of looking into early media (and at some point handover
> handling) I would like to use MNCC_RTP_CONNECT and supply "recvonly",
> "sendonly" attributes.
It would make sense to have a bitmask i.e. have one bit for rx and one
for tx, as opposed to an 'arbitrary' enum.
> The content of payload_msg_type currently holds anything between 0x300
> and 0x03ff and I would like to split this field into two uint16_t. The
> reason is not to change the size of the structure (and maybe not dump
> the protocol version). It would be a backward compatible change.
>
> Is anyone open for such tricks? Otherwise I will bump protocol version
> and change the ABI (and try to update the various active users of this
> protocol).
I don't mind.
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)