SMS RP-Data spec violation. Somebody wants to fix it?

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/.

Holger Hans Peter Freyther holger at freyther.de
Wed Feb 5 08:27:06 UTC 2014


Hi,

I just looked at a trace and saw that the RP-MessageReference we
assign is hardcoded to 42. It should be a sequence number going
from 0 to 255. It is somehow idiotic as there can only be one SMS
per direction and there is the transaction identifier as well.

I would propose a patch that does:
Change gsm411_send_sms to ask the subscriber connection/transaction
code for a message reference. For added bonus also "put" the number
so we could verify to not re-use the number too early.

anyones wants to come up with a fix?


holger




More information about the OpenBSC mailing list