Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OneX, Web Collaboration and Communicator Time Issue

Status
Not open for further replies.

ThePhoneMn

Vendor
Apr 11, 2005
400
US
Hi all,

I have an issue with time on OneX, Web Collaboration and Communicator. I use Communicator, and my missed calls are showing 4 hours ahead of my time. OneX portal also shows 4 hours ahead on missed calls. Finally, and this is where it all started, Web Collaboration will not start conference's at the designated time because, I assume, it doesnt know what time it is.

New application server running 9.1.1
IPO 500 V2 on 9.1.1
Communicator downloaded from the 9.1 section of support.avaya.com
Server Web Control shows correct time and time zone
I displayed "date" from linux prompt and it shows the correct time
IPO time is correct

I looked around the OneX Administrator portal and did not see anywhere to set time.

Any suggestions?



Been there, done that
 
Sounds like the time zone is set wrong in IPO. Be aware that you can set time zones based on configured "Locations". So if you have a VPN overseas you can configure another location for that extension and the user will see the right time for his location in the phone display and the same time will be used for Voicemail/OneX Portal.
 
I confirmed it is an issue with my extension. Other users on OneX are showing correct time on missed calls in OneX portal. I checked my extension/ Location and it was set to Automatic. I added a location with my time zone (Same as system) and added it to my extension. Still same problem.

Just to point back to OneX... If I stop OneX services and restart my Communicator, the missed calls time is correct, as if it pulled the call log from the IPO. I start OneX services and all the times in Communicator reset to 4 hours fast. Why does OneX think I am in a different time zone?



Been there, done that
 
Just to update this. I am a remote user on our system using Avaya Communicator, the call log times were 4 hours off from all other users. I had coworker log me into physical phone at office and log me out. I logged back into Communicator and now the time is okay.

Still have issue with Scheduling conference's through OneX portal. All conferences are starting 4 hours later than scheduled time, this is happening for all users. Schedule conference for 12pm, outlook invites are sent and accepted by all parties, nothing happens at 12pm. At 4pm, conference bridge calls all users and... well, still doesnt work. We hear our voicemail saying how many messages we have. There are multiple threads on this problem with VM Pro missing REQUESTPIN option.

I have been working this thing over for 2 days to prepare for a customer demo, and I don't think it will happen, not looking good.

If anyone has input on why conferences are not starting at correct time, let me know your thoughts.

Thanks

Been there, done that
 
I had a similar problem with an incorrect time of the AppServer caused by a wrong time of the hosting ESXi server...
 
Thank you for the response derfloh. I checked the linux time at command prompt and it was okay, and checked the time on the BIOS. Where was your time wrong on your ESXi server?

Thanks

Been there, done that
 
me For was if one hour and off so the VMPro conditions didn't work like they should. trWtried a workaround by configuring a 'wrong' time zone in AppServer but that didn't have an effect since IPO had been set to the correct time zone.

I checked the Linux time on console, too and saw the wrong server time..
 
I wanted to update this thread with the fix. My coworkers found that setting the IPOffice Time to SNTP and using the same timer server address (0.pool.ntp.org in this case) the Application Server is using fixed the time issue.

Both times were okay on the surface, but I guess something in the Avaya sauce didnt like the IPOffice using VMPro/Manager for Time Setting Config Source.

Been there, done that
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top