Validity Period Issue When Switching to Day Light Saving Time
(Doc ID 2494128.1)
Last updated on SEPTEMBER 29, 2023
Applies to:
Oracle Communications Services Gatekeeper - Version 6.0.0 and laterInformation in this document applies to any platform.
Symptoms
On OCSG 6.0.0 with Patch Set 3 installed, user submitted messages with an absolute validity period:
For example:
0000 31 38 31 30 30 37 30 32 32 34 32 39 30 30 30 2b 181007022429000+ 0010 00 .
Which in accordance to SMPP spec YYMMDDhhmmsstnnp would decode to:
18-10-07 02:24:29 0 00+
However when the above is submitted into the platform, it was rejected. From the example, it seems to have rejected all messages with timestamp between 18-10-07 02:00:00 0 00+ to 18-10-07 02:59:59 0 00+, as if it's invalidating time that fell within the day light saving hole (User just changed it's clocked to day light saving, thus jumped from 2 am till 3 am).
But the time are meant to be in UTC thus it should have not been impacted.
This resulted in almost an hour of full rejection of messages as all messages that was set to expire within that hour were all marked as invalid.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |