Polycom 1725-31424-001 - Manual (Page 26)

Deployment Guide for the Polycom CX700 IP Phone
20
17. Polycom CX700 phone attempts HTTP request
to download RootCA cert chain using Kerberos
(SPNEGO)
(Kerberos Auth fails)
18. Polycom CX700 phone attempts HTTP request
to download RootCA cert chain using Kerberos
(SPNEGO) w/different key
(Kerberos Auth succeeds)
19. DC streams Base64 certificate chain to Polycom
CX700 phone via HTTP
(URL: /certsrv/certnew.p7b, Using SPNEGO
Authentication)
20. Polycom CX700 phone initiates a TLS
connection to the pool’s IP address with the
Ciphers it supports
(Client Hello) Note: SHA2 is not supported
21. Pool responds with negotiated Cipher spec to
complete the TLS handshake
(Server Hello) Note: TLS connection is now
established.
22. Polycom CX700 phone queries DNS for
autodiscover. A record
(fabrikam.com) Returns IP address of Exchange CAS
if configured.
23. Polycom CX700 phone initiates TLS connection
with Exchange 2007 CAS
(Used for missed call notification)
24. Polycom CX700 phone sends HTTP 80 POST to
pool. for
/RequestHandler/ucdevice.upx
• Note: This would be an HTTPS 443 POST to
pool. for
/RequestHandlerExt/ucdevice.upx for an external
OCPE device
(Payload contains phone vendor info)
25. Pool responds with current firmware upgrade
version and Internal / External file path info
(These values are blank if WMI settings were not
populated)
• -
http://pool01.contoso.com/DeviceUpdateFiles_Int/UCPhone/Polycom/CX700/A/ENU/1.0.522.101/CPE
• -
https://ocsrp.fabrikam.com/DeviceUpdateFiles_Ext/UCPhone/Polycom/CX700/A/ENU/1.0.522.101/CPE
26. Polycom CX700 phone issues an HTTP GET for CPE file if it’s newer than the currently installed version
• (HTTP:Request, GET
/DeviceUpdateFiles_Int/UCPhone/Polycom/CX700/A/ENU/1.0.522.101/CPE/CPE.nbt)
27. Pool begins streaming CPE.nbt to Polycom
CX700 phone as a binary/octet-stream (approx.
15MB)
(You will see a lot of TCP traffic)
28. Polycom CX700 phone issues one last HTTP Get
and the pool responds with 200 to indicate
download is complete
(Success!!)