CE 8.2 code on the DX70 and DX80

***UPDATED***  The Devpack, CE8.2.1 and conversion cop are now available on CCO.

CE 8.2.0 firmware for the DX70 and DX80 posted to CCO today.  (But of course we’re still waiting for the Devpack with the QED that will be released in the next week or so.)  The release notes are here.  The Official Conversion Guide is here.  Any instructions in this guide would override what I’ve said.

I’ve been running the beta for the last few weeks and can absolutely say CE code on the DX is MUCH more responsive, stable and usable than the Android-based code.  (That said the last few builds of 10.2(5) android code have been pretty decent.)

CE 8.2 code is absolutely the code to move to if your primary use for the DX is for video calls.



Why move to CE on the DX?

  • Responsiveness.  No more lag!  It’s snappy.
  • Stability.  Seldom, I had the random crash and full-reboot during video calls with Android.  While it was pretty rare, it was super frustrating.
  • Video-centric user interface.  It run CE codec code now and feels like a Cisco codec (like SX10, 20, etc.) now.  It’s all about the video call.
  • Registration to VCS/Expressway
  • Far-end Camera Control
  • OBTP (one button to press) meeting launch and TMS management
  • Fully customizable wallpaper

Why stay on Android?

  • You need Android applications.  CE doesn’t run any apps, period.
  • You use the built-in Cisco Webex and Jabber Android apps on the DX.
  • You need a local web browser.  CE doesn’t have a web browser built in.
  • You are currently using Wi-Fi or Bluetooth.  The CE code doesn’t yet support Wi-Fi or BT.  (That’s coming in a follow-on release.)
  • You need telephony features on the phone like CFwdAll, Shared Lines, Voicemail button, Auto answer.

What happens to Android?

Android will be supported on the DX70 and Dx80 for the life of the product.  Keep running it if you need features that will always only be specific to Android (local web-browser, Android Apps).  The DX650 will remain Android-only.

Converting to CE Code using CUCM

Note: You have a couple options to convert to CE code.   CUCM of course or, as the conversion guide notes, there is a public TFTP server on the internet provided by Cisco to convert a DX using.  As far as CUCM, you can convert the DX either onnet or connected via MRA registration through Expressway.

  1. Upgrade to the latest build of Android code – 10.2(5)207 by installing the COP file on CUCM, restarting TFTP and rebooting your DXes.  (Either way you want to go to this code because of all of the bugfixes.)
  2. Install the latest (Early July 2016) Devpack:
    CUCM 11.0.1:  cmterm-devicepack-
    CUCM 10.5.2: cmterm-devicepack10.5.2.14076-1.cop.sgn
    CUCM 9.1.2: cmterm-devicepack9.1.2.16137-1.cop.sgn
  3. Install the Devpack on CUCM as well as cmterm-synergy-ce8_2_1_no_defaults.cop.sgn (or latest version) so that it gets the Telepresence DX70 and Telepresence DX80 device type QED installed.  Reboot your cluster.  (Unless you’re on CUCM 11.5 which doesn’t need the immediate reboot!!)  Or bug someone you know for the standalone CE 8.2 QED in the meantime.
  4. This devpack should have the CE 8.2 firmware, but if not install the CE 8.2 COP file – mterm-s52040ce8_2_1.k3.cop.sgn (or current); restart TFTP.
  5. In CUCM, change the Phone Load of the existing DX80 to the CE 8.2 phone load name specified in the conversion guide.  For 8.2.0 it is sipdx80.ce821.rel.loads
  6. The DX80 will take a few minutes (10-15) to upgrade to CE 8.2.1.
  7. Take note of the MAC address of the DX80 in the CUCM device, because you are about to DELETE the DX80 device!
  8. Delete the DX80 device from CUCM.
  9. Create a new Telepresence DX80 device in CUCM and paste in the MAC address of the DX80 you just deleted.  Set the appropriate device settings and add an extension/SIP URI to the device.
  10. On the DX80 itself, run through the startup wizard and pick UCM registration or UCM through Expressway (if your endpoint is registering through Expressway).
  11. You’ve now got a DX80 on CE 8.2 code
  12. Enabled Web Access in CUCM device settings so that you can get to the DX80 GUI.
  13. Login to the GUI and set the admin password.  (This step may not be needed, setting the admin username/password was not available in earlier CE betas via the CUCM device setting page.)


Other Notes

  • The Touch 10 doesn’t work on the DX80 or Dx70, you must use the built-in touch screen on the DX.