sms bugfix

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.org
Sun Apr 17 18:43:25 UTC 2011


Hi Nico,

On Sun, Apr 17, 2011 at 08:06:54PM +0200, Nico Golde wrote:

> But thinking more about this... does it really make sense to store 
> anything but control data and the actual PDU in the database? When sending 
> a message from the vty the message is encoded anyway, so just inserting 
> the PDU + control data should be sufficient. I'm not sure if OpenBSC has 
> to be aware of things like UDHI, UDH, PID and thelike.

well, what you definitely want aside from the PDU is 'valid_until', which is a
result of PDU parsing...

But yes, generally,
* there should be no decoded SMS in the database (and if it is, only for
  debugging, i.e. no code should ever use the human-readable decode
* there should be no direct references to the subscriber table
  (sender_id/receiver_id).  Rather, the actual phone number (MSISDN) should
  be used.

-- 
- 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)




More information about the OpenBSC mailing list