Microsoft did release an update package for the Office Communicator Phone Edition. The version will be upgraded to 1.0.522.71. More information available on the link below:
this is the second update? hmm we're still not able to make this work for us, phones are not getting updated. email@example.com
Can you give us more specific information? I think as far I can remember that this is the third major update for the Office Communicator Phone Edtion 2007. Correct me if I'm wrong.
we're using the pre-RTM lg-nortel tanjays, we setup the update server according to the documentation provided by m'soft, but the phones doesn't pull the updates from the update server. at first we thought the problem would be the hardware, but we took a couple units to m'soft malaysia and see if the phones are able to update and they updated. one thing we notice is that the time on the phone is wrong, we're at +0800 GMT, but the phones shows a different time. we tried manually going into the control panel and changing the time and then reset the phone, but it keeps going back to a different time. how do i check if my time server is setup right?thanksalvin(firstname.lastname@example.org)
The NTP provider is the standard time provider included with Windows Server 2003. The NTP provider in the Windows Time service consists of the following two parts: • NtpServer output provider. This is a time server that responds to client time requests on the network. • NtpClient input provider. This is a time client that obtains time information from another source, either a hardware device or an NTP server, and can return time samples that are useful for synchronizing the local clock. Although the actual operations of these two providers are closely related, they appear independent to the time service. By default, when a computer that is running Windows Server 2003 is connected to a network, it is configured as an NTP client. Communicator Phone Edition searches for a NTP Server in DNS• NTP SRV record (UDP port 123)o _ntp._udp.SIP domain pointing to NTP ServerIf it cannot find the NTP SRV record it will attempt to use http://time.windows.com as an NTP Server. • NTP A record o time.windows.comSource: the Phone Edition Deployment Guide ver 1.0
hmm yeah we have that setup already but somehow this version 1.0.199(1.23) doesn't seem to pickup and synchronise the local time on the phone display. it instead shows time from a different time zone. and the sus and wss is properly setup but its not pickup any logs or events from the tanjays on the network, we have like 15 with the same firmware version on the network in testing, they all can login and work make calls but time doesn't sync and updates doesn't go thru. any thoughts/ideas? help is much appreciated.thanksalvin(email@example.com)
I had an discussion with someone at Microsoft. When you can sign in the Phone Edition the time is synchronized otherwise the certificate cannot be validated. The reason you cannot download the update can have multiple reasons. Make sure the SharePoint is correctly registered in the WMI setting. Look in the latest Deployment Guide.
Post a Comment