- Hey, everyone! I'm new to the Polycom family of products, so I'm hoping someone can help me out. We purchased two new CX700 and they came with Firmware v1.0.522.34. We're currently running Lync Enterprise Server 2013, and I've read online about how you can't jump right to the latest firmware; you.
- Aug 07, 2012 Hi, please update firmware with Microsoft Lync 2010 Phone Edition for Polycom CX700 and LG-Nortel IP Phone 8540. Best regards, Tuesday, November 23, 2010 7:21 AM.
A long and sad story about trouble upgrading the firmware in Office Communication Server enabled phones, specifically the Polycom CX700. This particular problem manifests itself as follows: The phone logs on to the server successfully and gets almost to the end of the login process. Then it crashes and automatically reboots. This goes on in an endless loop, and is caused by the phone running software not compatible with OCS 2007 R2. I post this hoping that it will be of help to others on a similar quest.
The problem
The Polycom CX700 IP Phone is designed specifically for use with Microsoft Office Communications Server 2007. The CX700 IP Phone is a standalone telephone that does not require a connection to a PC. Re: Upgrade CX700 - Lync 2013 (On Premise) Hello alccc, Polycom and other manufacturers produce these optimized for Microsoft® Lync® or Skype® for Business devices after a reference design and the embedded OS running on the phones is provided, supported and maintained by our partner Microsoft®. Apr 28, 2017 Microsoft® Lync™ Phone Edition for Polycom® CX500, Polycom® CX600 and Polycom® CX3000 is the first generation of software designed specifically for the phones from Polycom to interoperate with Microsoft® Lync™ Server 2010 and Microsoft® Lync™ Server 2013. Lync Phone Edition provides traditional and advanced telephony features, integrated security, manageability and much more.
For about a year now, since we started our OCS pilot, I’ve had a Polycom CX700 on my desk. Actually, it has spent the bulk of that time on a shelf at my desk. It was purchased as a test device along with a collection of headsets and other OCS enabled devices. Most of them worked fine, but this one I just couldn’t seem to get working. After a lot of fiddling about I was able to log in successfully with a test user that had never ever logged on to any other device or computer. I happily thought I had it fixed, but as soon as I switched to another user it went back to the same old pattern: logon, crash and reboot in an endless loop.
Giving up
Pretty early in the process I was informed that the firmware (1.0.522.73) was built for OCS 2007, and as we were running 2007 R2 it would not work. Later, I was told by Polycom support that it was impossible to update this version to a 2007R2 compatible firmware without having an OCS 2007 device update server. At that point I gave up, put it on the shelf and concluded that we had to swap it for another one with newer firmware.
But the phone was still there. It just sat there on my shelf, and from time to time this annoyed me to the point that I researched it further. I am not accustomed to giving up, especially not on a technical problem. Mulling at the back of my head was the feeling that there had to be a solution somewhere, some hack to fix it or a bug blocking my path. But no matter what I tried, I had no luck.
At some point in my search I came across these articles on TechNet blogs by Rui Silva: http://blogs.technet.com/b/ucspotting/archive/2009/04/16/how-to-upgrade-polycom-cx700-1-0-452-0-using-the-ocs-2007-r2-device-update-service.aspx
I followed them both in detail (several times) since they describe a problem similar to mine, but to no avail. It just wouldn’t budge, it refused to give in. I had all the device update websites set up correctly, and the RequestHandlerAuditLog listed the device as connecting and identifying itself, but it never requested nor downloaded any updates. As far as I could tell everything was set up correctly at the server side, so the phone had to be the source of my trouble.
A new hope
I was close to giving it up for good, but then suddenly I had an epiphany: The RequestHandlerAuditLog samples other people were posting online always listed a request stating it was currently running version 0.0.0.0;01-01-1601 00:00:00, before it requested the interim version(1.0.522.103) which is the bridge version from OCS 2007 to OCS 2007R2.
But my CX700 never got past this, it never requested the interim version, and still it reported 0x0;200 as the last update status. That means the server thinks the phone does not require any updates, even though clearly it does. The first number is a hexadecimal WinInet error code, and the second is a standard http status code. 0x0 translates to no error, and http status 200 means the request succeeded. See this site for an explanation of the last update status codes. Rui Silva mentions changing the UCPHONE client version filter to allow any 1.522 version which I did a long time ago, but then I thought: What if the server believes the phone is actually running version 0.0.0? To test this, I removed the UCPHONE client version filter completely, thus allowing anything identifying itself as a compatible phone to download updates. I then reset the phone to trigger an update attempt and logged in with the special phone test OCS user mentioned above. Nothing happened. It just contacted device update as usual , which resulted in a 0x0;200. I went home and meant to try again the next morning, but other more pressing problems required my time so the phone was just left untouched on my desk. Suddenly, about 22 hours after the last reset I noticed the screen on the phone blinked. Then it rebooted, and lo and behold; it was now running version 3! I had read online that the upgrade process could be slow, but that it could take 22 hours to complete didn’t occur to me. The phone had been left on for several days earlier though, so removing the client version filter seams to be the magic bullet. The successful RequestHandlerAuditLog:
And the IIS log:
As far as I can tell, the phone goes directly from 1.0.522.073 to 3.5.6907.222. I guess 1.0.522.073 is a beta or RC of the interim version.
The solution
To sum it up, this is the key steps of what got it working for me:
Polycom Cx700 Firmware Upgrade Lync Update
- Make sure to log in to the phone using a complete domain name, e.g. “domain.localusername”. If I used domainusername I received certificate download errors on the phone. The same error occurred if I tried [email protected], but according to Microsoft this should work. I suppose this is a bug.
- Remove the UCPHONES client version filter from the update server
- Set the default client filter to Allow
- Use a special upgrade user that has NEVER been logged in anywhere other than on the phone.
- Leave the phone on, signed in and untouched for at least 24 hours
Experience 1080p “around-the-table” video calls with Microsoft Skype for Business
Polycom Cx700 Microsoft Teams
Specifications
Dimensions
- Footprint (W x D): 369 x 325 mm
- Height: 348 mm (privacy cap closed), 401 mm (privacy cap extended)
- Weight: 2.44 kg (exclusive of cables)
- Power Data Box
- Size (W x H x D): 209.5 x 300 x 56 mm (excluding stand)
- Weight: 2.9 kg
- Size (W x H x D): 520 x 430 x 430 mm
- Weight: 9.29 kg
Power
- Power consumption: 110 watts, typical
- Universal power supply 100–240 V AC, 50–60 Hz
Video performance
- Panoramic video resolutions supported:
- 1920 x 288 pixels (requires USB 3.0 and Lync 2013 or Skype for Business)
- 1280 x 192 pixels (requires USB 3.0 and Lync 2013 or Skype for Business)
- 1056 x 144 pixels
- HD 1080: 1920 x 1080 pixels (requires USB 3.0 & Lync 2013 or Skype for Business)
- HD 720: 1280 x 720 pixels
- VGA: 640 x 480 pixels
- CIF: 352 x 288 pixels
- Frame rate for panoramic and active speaker video, maximum
- 30 frames per second with 60 Hz AC power
- 25 frames per second with 50 Hz AC power
- Maximum frame rates with systems prior to Lync 2013 will be limited to 15 fps (12.5 @ 50 Hz)
Audio performance
- Frequency response: 160 Hz–22 kHz
- Volume: adjustable to 88 dBA SPL (peak) volume at 0.5 meters
- Console microphones
- 3 microphones for omnidirectional coverage
- Frequency response: 160 Hz–22 kHz
Telephony Performance
- Full Duplex (Class 1) with noise suppression
- Comfort noise fill
- DTMF tone generation/DTMF event RTP payload
- Low-delay audio packet transmission
- Adaptive jitter buffers
- Packet loss concealment
- Acoustic echo cancellation
- Background noise suppression
- Supported codecs are G.711 (A-law and μ-law), G.729AB, G.722, G.722.1, G.722.1C, G.719
Call handling features
- Call timer
- Call transfer, hold, divert (forward), pickup
- Called, calling, connected party information
- Local three-way conferencing
- One-touch speed dial, redial
- Call waiting
- Remote missed call notification
- Automatic off-hook call placement
- Do not disturb function
- Lync client device synchronization
- Lync USB call control for Answer, Reject, End Call, Hold, Resume and Swap
Protocol support
- IETF SIP (RFC 3261 and companion RFCs)
Network and provisioning
- IP Address Configuration: DHCP and Static IP
- Time synchronization with SNTP server
- FTP/TFTP/HTTP/HTTPS serverbased central provisioning for mass deployments. Provisioning server redundancy supported.
- Web portal for individual unit configuration
- QoS Support—IEEE 802.1p/Q tagging (VLAN), Layer 3 TOS and DSCP
- Network Address Translation (NAT) support—static
- RTCP support (RFC 1889)
- Event logging
- Local digit map
- Hardware diagnostics
- Status and statistics
- User selectable ringer tones
- Convenient volume adjustment keys
- Field upgradeable
Security
- Transport Layer Security (TLS)
- Encrypted configuration files
- Digest authentication
- Password login
- Support for URL syntax with password for boot server
- HTTPS secure provisioning Support for signed software executables
User interface
- 3 mute buttons with mute/in-call indication lamps
- Camera on/off indication lamp
- Captive privacy cap with integrated on/ off switch for client synch
- Gesture based, multi-touch capable capacitive touchscreen for voice calls
- 4.3in LCD (480 x 272 pixels) resolution
- User-configurable contact directory and call history (missed, placed, and received)
- Customizable call progress tones
- Wave file support for call progress tones
Console connectivity
- Proprietary system port for connection to Power Data Box
- USB 3.0 Type A port for proprietary connection to Power Data Box
- USB 3.0 Type B port for connection to PC
- USB 2.0 Type A port for diagnostics/ software update
- 2 extension microphone ports
Power data box connectivity
- Proprietary system port for connection to console
- USB 3.0 Type A interface for proprietary connection to console or to Lync appliance
- USB 2.0 Type A for diagnostics/software update
- Ethernet: RJ-45 10/100/1000 Mbit
- Audio RCA jacks (reserved for future use)
- AC power input
Physical security
- Kensington-style lock slot on Console and Power Data Box
Extension microphones (optional accessory)
- Frequency response: 160 Hz–22 kHz
- Mute button and indicator lamp
Regulatory compliance
- UL 60950-1
- EN 60950-1
- CSA C22.2 60950-1
- IEC 60950-1
- AS/NZS 60950-1
- GB4943-2011 (China)
- KCC approval (Korea)
- EMC
- CISPR 22 Class B (FCC, ICES, AS/NZS)
- VCCI Class B
- EN 55022 Class B
- EN 55024
- GB9254:2008, YD/T993-1998 (China)
- KCC approval (Korea)
- ANATEL (Brazil)
Environmental requirements
- Operating temperature: 0–40ºC
- Relative humidity: 15–85% (non-condensing)
- Storage temperature: -40–60ºC
- Recommended room conditions
- RT60 <0.600 seconds
- Ambient noise level: <50 dBA SPL
- Optimal lighting conditions: 300 lux, with a single lighting temperature (no mixed lighting)
Warranty
- 12 months
CX5500 ships with
- Tabletop console with integrated 360º camera
- Power data box with stand
- Quick setup card
- Cables
- Proprietary system cable
- USB 3.0 Type A–Type A cable
- USB 3.0 Type A–Type B cable
- Ethernet cable
- AC power cord with local plug
Optional accessories
- Extension microphone kit with pair of microphones and cables
- Cable length is 25 ft (7.6 meters)