Asked by:
About the software updater service in R2

Question
-
Hi
Is there any documentation on that tool and the general working of it? I uploaded the latest cab file I found and finally managed to connect the first Tanjay phone.. but when connected it still showed a 1.x software revision whereas the one on OCS is much newer. I'm also having OCS bitching about Comos (even when version checking is disabled.. interestingly this only happens when you connect via Edge.. internal connections are fine).
I'm also interested about the different CPE versions.. I suppose each means a different device but what is what?
Regards
Stephan
Wednesday, February 11, 2009 10:02 PM
All replies
-
Re: Update Service...If the Tanjay build is lower than 522.98 then R2 will send it 522.103, which is an interim build compatible with the upgrade to the R2 builds. Once that is complete it will follow the normal upgrade cycle to the new version that you uploaded.
Re: CoMo...Did you disable version checking on the Edge as well?
Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mikeThursday, February 12, 2009 12:20 AMModerator -
Como: Yes I disabled version checking and restarted the service. Interestingly enough, it can connect in the internal network even if the version checking is enabled.
And the Tanjay didn't download anything. Two other Tanjays even completely freaked out and can't contact the time server anymore even though it's both in the DHCP response, plus there's the SRV record as well. Since we cannot access the logs on the phone (that really makes no sense if you ask me.. what's better than logs to trace down a problem) I'll have to use a packet sniffer to get to the bottom of this.
And I still don't understand how the software update service is supposed to work. I take it it runs on the HTTP server of the OCS.. but how are devices (be it hardware or software) supposed to realize they need updating?Thursday, February 12, 2009 12:02 PM -
I would check your IIS logs for assistance with the device update troubleshooting. Here's the process that the devices use:
How Devices Obtain Updates from Device Update ServiceDevice Update Service supports two UC devices: Office Communications Server 2007 R2 Communicator Phone Edition and RoundTable. RoundTable must be manually configured to connect to the Device Update Service, as described in Appendix D: Configuring RoundTable to use Device Update Service. In the default configuration, Communicator Phone Edition connects to Device Update Service in the following manner:
- The first time a user starts Communicator Phone Edition and signs in, the device gets in-band provisioning information from the server or Enterprise pool hosting the device user account. The information contains the internal and external URL of the server running Device Update Service.
If the device is turned on, but no user signs on, and no user has ever previously signed on to the device, the device sends a DNS lookup request to ucupdate.R2.<SIP domain> and obtains the internal and external URL of the server running Device Update Service.
- Thereafter, when the device is turned on as well as every 24 hours by default, Communicator Phone Edition checks for updates by sending an HTTP request over port 443 to the Web Components Server hosting Device Update Service. The request includes the current version that Communicator Phone Edition is running.
- Device Update Service returns a response containing one of the following:
- If no approved updates exist for the current version of the firmware, the response contains downloads=0. For test devices, updates must be pending rather than approved for this to occur.
- If an approved update exists for the current version, the response contains an internal and external URL for Device Update Service. For test devices, updates must be pending rather than approved for this to occur.
- If no approved updates exist for the current version of the firmware, the response contains downloads=0. For test devices, updates must be pending rather than approved for this to occur.
- In the latter case, Communicator Phone Edition sends an HTTPS update request over port 443 to Device Update Service.
- The update image is downloaded to the device.
- The device waits for five minutes of idle activity, and then restarts to complete the update.
Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mikeThursday, February 12, 2009 1:56 PMModerator - The first time a user starts Communicator Phone Edition and signs in, the device gets in-band provisioning information from the server or Enterprise pool hosting the device user account. The information contains the internal and external URL of the server running Device Update Service.
-
.Mike Stacy said:
Re: Update Service...If the Tanjay build is lower than 522.98 then R2 will send it 522.103, which is an interim build compatible with the upgrade to the R2 builds. Once that is complete it will follow the normal upgrade cycle to the new version that you uploaded.
Dear Mike,
Is this interim build pushed by the R1 update service, or the R2 update service. As discussed in the article http://social.microsoft.com/Forums/en-US/communicationsserversetup/thread/4f96708a-b653-48b1-ae40-2327c4ee04b1 we are a bit stuck at upgrading the Tanjays....
Thanks for your help,
Best Regards
WimWednesday, March 25, 2009 7:44 AM