Upgrading Polycom CX700 Phone within a Microsoft Office Communications Server 2007 R2 Environment
http://POOL01.contoso.com/DeviceUpdateFiles_Int/UCPhone/Polycom/CX 700/A/ENU/1.0.522.101/CPE
+Element: XmlElement:<ExternalBaseURL> - https://ocsrp.fabrikam.com/DeviceUpdateFiles_Ext/UCPhone/Polycom/C
X700/A/ENU/1.0.522.101/CPE
Scenario
The upgrade instructions in this document assume the following conditions:
•Starting state for a Polycom CX700 phone is software release 1.0.199.123
•Test account is OCSTest1 (for example, ocstest1@fabrikam.com)
•Pool running Device Update Service is pool01.contoso.com
•Test Device is Tanjay01
•Domain Controller is dc01.contoso.com
•DHCP / DNS / WINS / Certificate Authority / NTP run on the domain controller
•There is an internal DNS zone called fabrikam.com (i.e., the <SIPDomain>) created manually and populated with autodiscover (pointed to Exchange UM) and sip A records. It also contains _sipinternaltls._tcp and _ntp._udp SRV records.
•There is an Active Directory DNS zone called contoso.com (i.e., the <DHCPDomain>) and created automatically during setup. It will contain the pool and
•There are corresponding external DNS zones for contoso.com and fabrikam.com.
•There is a reverse proxy that is publishing the pool locations for DeviceUpdateFiles_Ext and RequestHandlerExt (refer to Device Update File Storage on page
•Software release 1.0.522.101 is set to “Approved” and software release 3.5.6907.35 is set to “Pending”. To upgrade from 1.0.522.101 to 3.5.6907.35, the phones are added to the Test Devices tab to limit the upgrade to just the targeted devices.
Background
When trying to figure out why one or more steps in the upgrade process are not working, it is helpful to know how it is supposed to work. This section provides a brief explanation of the components involved and how a Polycom CX700 phone interacts with DNS, Pool, Web Components service and the Device Update service.
15
