Wrong hour on MMS received

Wrong hour on MMS received SearchSearch
Author Message
svaore
New member
Username: Svaore

Post Number: 4
Registered: 03-2011
Posted on Tuesday, June 20, 2017 - 12:04 pm:   

Greetings

We have just moved our MMSC from an old windows 2003 server to a brand new windows server up to date.
The time on the computer is OK, as are most all of the MMS that we are sending to two destinations that are not ours.
Only on our network destination, do we get a totally wrong time stamp.
For example, if I send an MMS at 14H29, my friend get it à 14H30, but the time on his arrival date is actually 12H30, two hours late.
and the log are showing the same 2 hours lag.
marc bazimon
New member
Username: Marc_orange

Post Number: 50
Registered: 01-2007
Posted on Tuesday, June 20, 2017 - 12:41 pm:   

HI Nowsms support
let me update the previous message from svaore.

application/vnd.openxmlformats-officedocument.wordprocessingml.documenttcpdump from mmsc
pb_horodatage.docx (67.6 k)


here's a screenshot of the tcpdump i made yesterday after the migration.
You can see that the retrieves has got two hours of shift compare to the right time.
The issue is on the retrieve.conf. when we send MMS to through MM4 , the time is OK as we don't retrieve message.
The issue is only when our subscriber get their message.
is it a way to configure the timestamp or timezone.
Not that the trouble appears even if for the migration , i did copy the whole "nowsms" path
i can send you a trace but only with email due to personal information into it.

Br
Marc
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5851
Registered: 08-2008
Posted on Tuesday, June 20, 2017 - 01:24 pm:   

Hi Marc & svaore,

Can you advise all the version numbers involved (Windows Server & MMSC), plus details on time zone as configured in Windows Server.

We did make two fixes last year to time stamp handling, but I don't see any reference to it involving direct MM1 transactions....it was observed in DIAMETER and the event log.

Go ahead and forward logs to nowsms@nowsms.com with Attention: Des in the subject line.

--
Des
NowSMS Support
marc bazimon
Frequent Contributor
Username: Marc_orange

Post Number: 51
Registered: 01-2007
Posted on Tuesday, June 20, 2017 - 01:33 pm:   

Hi Des ,
the windows server ar ewindows server 2012 R2 datacenter and the version of MMSC is v2015.04.27. The Time Zone is (UTC+04:00) Abu Dhabi, Muscat.
i will send you a trace on your email account with the pcap trace.
Br
Marc
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5852
Registered: 08-2008
Posted on Tuesday, June 20, 2017 - 08:56 pm:   

Hi Marc,

I have confirmed with our engineering team that the code which generates the MM1 timestamp was also updated in the 2017 release, so I believe this will address the problem.

Last year, we had several reports of incorrect timestamps affecting only some functions (usually 1 hour off, but one of the reports may have had a 2 hour discrepancy).

To keep a long story short, in the end, we determined that some library functions involved in generating timestamps was off by an hour in some installations. We had a great deal of difficulty replicating the problems, concluding that the issue was some combination of time zone specific and Windows version specific. (All system time is being retrieved from Windows.)

One of the customers reporting issues was in the UAE (GMT -0400) using Windows Server 2012 R2.

--
Des
NowSMS Support
marc bazimon
Frequent Contributor
Username: Marc_orange

Post Number: 52
Registered: 01-2007
Posted on Wednesday, June 21, 2017 - 10:23 am:   

Hi Des
Thanks for your reply,
we should renew the SUA so i guess , we will be able to correct this issue taking the new version.
Br
Marc

Add Your Message Here, or click here to start a new topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message
Action: