IP Communicator Synchronization Problem

[ebode]

CCM ver 3.3(3)

Client OS ver Windows XP Pro

I am having a problem with getting IP Communicator to update its time on a user's laptop. We are in the testing phase of the software rollout. Different Date/Time Group (than CMLocal) has been created and assigned to the Device Pool, after which the time updated fine on 2 other users' laptops.

Is anyone aware of any application (e.g.security-related) local to the client that could cause this problem?

Calls (and quality) to/from the Communicator go through very well.

Please help.

[mchin345]

I haven't heard of such kind of problem. Check the software you are testing

[cairns-a]

I had a problem with the IP Communicator keeping the correct time. I am running CM 3.3(3). I found that you have to have the IP Communicator in a Date/Time Group. Not the default Date/Time Group.

Hope this helps

Trae

[ebode]

I have done this. It corrected the bug on 2 out of 3 machines. As it turns out it is a bigger problem than just the Date/Time Group issue. This Communicator is simply not synchronizing with CallManager.

We are still looking at it.