We are getting ready to upgrade from Unity 4.0.5 to CUC 7.1.5. We have already run the COBRAS export on Unity box and the Unity Connetion box is being prepared for the import. I was looking at the data using the COBRAS data viewer, and noticed that all messages had a timestamp that was 7 hours off (ahead). I looked at the log file of the export itself, and the messages have the right timestamp according to what I see in that log file. No issues on the old Unity box in terms of messages having the wrong time. Only see this in the Data Viewer.
Has anyone else seen this before? I assume it's not normal and was going to import just a couple of users and see what their message timestamp looks like, but I thought I would ask to see if someone might have had the same problem as us here.
I'm guessing the Unity server you backed up was in GMT -7 hours (Arizona or Mountain time perhaps?).
The message time stamps are stored in UDT (like GMT without daylight savings time) - the client that presents them (Outlook, Connection voice messaging service etc...) are responsible for translating them into whatever time zone they should be in. When you restore those to Unity or Connection the timezone of the server will be reflected properly when you access the messages.
Sounds like you have seen this scenario before. I hope you're right. I checked on the servers and they're in the correct Pacific (GMT -8) timezone, so I guess they should have been off 8 hours? I can double check, but I thought I was off 7 hours. Tomorrow is when I find out how this import will work. I'll update this post after I go through that.
Just to be clear, this isn't an issue... and yes, I've seen it before, I wrote COBRAS.
That's how the messages are stored in in the message database - COBRAS does no translation or changing of timestamps of any kind - that's the message info as it comes out of the Unity (Exchange/Domino) or Connection (SQL) data stores raw.
UDT and GMT aren't the same thing - UDT does not use daylight savings time so will be an hour off half the year.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...