Voice Quality Statistics time stamp

[Billz66]

3300 Mxe 4.1 Sp2
I have been checking the Voice Quality Statistics on this controller . It appears that the time stamp is not from the local Controller ?

Is it referenced to GMT or is there a setting somewhere to sync these stats to the local time on the Controller?

 

[IrwinMFletcher]

It should be the same. What is the controller saying the time is versus the VQ Stats?

 

[Billz66]

Way out , We are in Melbourne Australia and the Stats time looks roughly like GMT
- ie we are GMT+10 for controller time

 

[Supernova99]

I know this is a long shot but bear with me.

I have experienced a similar issue with smtp forwarding time stamp being different than the the system clock.

I am not sure if they are linked or not but it is worth checking because it sounds so similar.

If you have embedded voicemail then go to the voicemail networking option and add your local system (by default it is blank) fill out the details and select local node lastly you will see a time zone drop down adjust this to your locale, then try your VQ stats again.

Share what you know - Learn what you don't

 

[IrwinMFletcher]

Are these stats from the phones, or the E2T? The E2T uses the system time, and if this is an expanded MXe, then perhaps the system time isn't set properly on the E2T card.

 

[Billz66]

Ok its not an expanded , bbut while we are on the subject how do you set the time on the e2t card.

Yes i thought that network vm server timezone might be relevant but thats already set to the same timezone as the controller.

 

[IrwinMFletcher]

writedatetime should set the clocks on both cards, to verify, just connect to the shell of each and do a getdatetime.

I have a 4.1SP1 system that I just tested it on, and it works fine. Simple setup, just some IP trunks, SIP trunks and EMEM. Perhaps there is something else that you've programmed that affects this?

On my test system, the Date and Time form shows the same time that the VQ stats report.

Also, you haven't mentioned the source of the logs. Are these from phones? MBG? or the E2T? Post one of the logs if you can.

 

[DoubleUT]

We've seen the same issue and this is being solved in the load 4.2