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/.
Alexander Chemeris alexander.chemeris at gmail.comHi Holger, On Sun, Mar 9, 2014 at 10:36 AM, Holger Hans Peter Freyther <holger at freyther.de> wrote: > On Sat, Mar 08, 2014 at 10:11:03PM +0100, Alexander Chemeris wrote: >> In a production system we should not store messages longer than >> needed, as it will quickly bloat our DB. In case one wants to store >> messages for debug purposes, we could add one of the following >> capabilities later: >> - hexdump to a log file >> - send to an SMPP entry on delivery >> - send to Wireshark > > there are several aspects in "production". There is billing and > privacy. For privacy we should clear the text/user_data after the > SMS has been delivered. For billing one might need to keep the meta > data up to X (e.g. 90) days. As we don't have a "CDR" mdoule the only > way to handle it is to keep that in the DB. > > So I wouldn't want to remove this right now. If you want billing, you could route all messages to SMPP, route/ACL/bill there and send them back to the internal SMSC. That's what Rhizomatica guys are doing and it works well. In this outside SMPP entity you could do whatever CDR and storage you want, without touching the OpenBSC code, which is in line with our discussions with Harald. PS I have more DB changes pending. One is storing Message Reference in the DB to be able to generate delivery reports (commited to my branch). The other is not finished yet, which will allow store delivery reports in the DB. -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. / ООО УмРадио https://fairwaves.co