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!
Hello 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@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!
thanks, i will take a look into it.
On Wed, Aug 23, 2017 at 7:54 PM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Hello 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@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
On Wed, Aug 23, 2017 at 02:54:55PM +0300, Alexander Chemeris wrote:
Hello 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
Ugh. This branch is from the stone age, 2014.
We already have status reports upstream, and many things I see there are already fixed upstream. This includes SMPP and nitb modes.
Sorry to say, but I see nothing on that branch... I wouldn't use it myself.
Hi Pablo,
On Wed, Aug 23, 2017 at 8:07 PM, Pablo Neira Ayuso pablo@gnumonks.org wrote:
On Wed, Aug 23, 2017 at 02:54:55PM +0300, Alexander Chemeris wrote:
Hello 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
Ugh. This branch is from the stone age, 2014.
Yes, it was a long time ago, so even I forgot what was there. It's not related to the topic in question, but this patch is not yet merged and I don't see this properly supported in master branch still? https://cgit.osmocom.org/openbsc/commit/?h=achemeris/sms-validity-fix&id...
But after looking a bit more into this, the patches which I *actually* meant are in the related libosmocore: https://cgit.osmocom.org/libosmocore/log/?h=achemeris/sms-fixes https://cgit.osmocom.org/libosmocore/log/?h=daniel/scts-fixes
Again, I don't see this merged upstream or somehow else implemented there unless I'm missing something?
Thank you all for the help!
I was able to solve the timestamp issue by upgrading to the latest nightly build. My previous installation does not yet have the recent patch that Neels mentioned.
On Thu, Aug 24, 2017 at 4:41 AM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Hi Pablo,
On Wed, Aug 23, 2017 at 8:07 PM, Pablo Neira Ayuso pablo@gnumonks.org wrote:
On Wed, Aug 23, 2017 at 02:54:55PM +0300, Alexander Chemeris wrote:
Hello 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
Ugh. This branch is from the stone age, 2014.
Yes, it was a long time ago, so even I forgot what was there. It's not related to the topic in question, but this patch is not yet merged and I don't see this properly supported in master branch still? https://cgit.osmocom.org/openbsc/commit/?h=achemeris/sms-validity-fix&id... c70e1282d692e376542b3f789e5340d02af78f17
But after looking a bit more into this, the patches which I *actually* meant are in the related libosmocore: https://cgit.osmocom.org/libosmocore/log/?h=achemeris/sms-fixes https://cgit.osmocom.org/libosmocore/log/?h=daniel/scts-fixes
Again, I don't see this merged upstream or somehow else implemented there unless I'm missing something?
-- Regards, Alexander Chemeris. CTO/Founder, Fairwaves, Inc. https://fairwaves.co
On Wed, Aug 23, 2017 at 04:34:21PM +0800, Mille Fiore 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.
I think Keith has fixed this upstream:
http://git.osmocom.org/openbsc/commit/?id=b4962dcf115148834478744e35fe1a888e...
On Wed, Aug 23, 2017 at 07:03:27PM +0200, Pablo Neira Ayuso wrote:
On Wed, Aug 23, 2017 at 04:34:21PM +0800, Mille Fiore 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.
I think Keith has fixed this upstream:
http://git.osmocom.org/openbsc/commit/?id=b4962dcf115148834478744e35fe1a888e...
Sorry, actually it's this one for libosmocore:
http://git.osmocom.org/libosmocore/commit/?id=733810c656fa9ec50a4223b0c15070...
On 23/08/2017 19:14, Pablo Neira Ayuso wrote:
Sorry, actually it's this one for libosmocore:
http://git.osmocom.org/libosmocore/commit/?id=733810c656fa9ec50a4223b0c15070...
Yes, athough that is only for the SMS timestamps. It's possible a similar fix might apply for the general setting of the time, although I haven't seen this problem, In fact, I've seen quite the opposite - the phones setting their clock to the machine running osmo-notb timezone.
One thing I do notice from Alex's branch is setting TP-SCTS on the delivery report to the datetime of the original submit. I wasn't able to find the correct spec. here, I used the delivery time. I also don't have a phone that cares.
On Wed, Aug 23, 2017 at 04:34:21PM +0800, Mille Fiore 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.
This sounds like it may be fixed by the recently merged patch, which changes the SMS' time stamp from UTC to the server's local time: https://gerrit.osmocom.org/3551 (This came to my attention because yesterday I noticed msc_vlr unit tests exhibiting differing H-M-S values for a timestamp of zero and needing adjustment.)
It should already be effective in the nightly builds. https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds
Also, if the basic phone will do an auto-update of date and time from the network, it will use the time in UTC.
(not sure about this one, might be worth opening an issue for on osmocom.org)
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.
To prepare for the (almost complete) move to separate osmo-msc and osmo-bsc processes, I have moved the timezone settings up from BTS level to the 'net' level: https://git.osmocom.org/openbsc/commit/?id=7398395cc01977aa9b41c2d433b487154... However, I'm not that familiar with what effect it has. All I can say is that the timezone configured on network level is used in all places where previously the bts timezone setting was employed.
~N
-
Alexander Chemeris -
eprueves eprueves -
Keith -
Mille Fiore
-
Neels Hofmeyr -
Pablo Neira Ayuso