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.comHello Mille, I made a bunch of fixes for time handling in SMS back in 2014, but those patches have never been merged master I think. If you want to rebase them onto the current master, they may help you (or may not - they have fixed a lot, but I don't remember about this issue specifically). The patches reside in the achemeris/sms_fixes branch of openbsc: https://cgit.osmocom.org/openbsc/log/?h=achemeris/sms_fixes On Wed, Aug 23, 2017 at 11:34 AM, Mille Fiore <eprueves at gmail.com> wrote: > Hello openbsc community! > > We are encountering the ff issue: When using basic phones, we have observed > that the timestamps on the SMS are in UTC, even if we changed the linux > system timezone to a different one. Also, if the basic phone will do an > auto-update of date and time from the network, it will use the time in UTC. > > Do you have suggestions on how to change the network timezone configuration > for the osmo-nitb? There is a timezone command mentioned in the osmo-nitb > vty reference manual (timezone <-19-19> (0|15|30|45), ex. timezone 8 0 ). > > If we put that config under the BTS level (in osmo-nitb.cfg), osmo-nitb will > complain that there is a config error. If we put that under the network > level, osmo-nitb does not complain, but it doesn't seem to work as expected. > > Let me know if addtl info is needed. Thank you in advance! > > > > -- Regards, Alexander Chemeris. CTO/Founder, Fairwaves, Inc. https://fairwaves.co