Cisco Cisco Expressway Release Notes
■
■
■
When deploying DX Series or IP Phone 78/8800 Series endpoints to register with Cisco Unified Communications
Manager via Mobile and Remote Access, you need to be aware of the following:
Manager via Mobile and Remote Access, you need to be aware of the following:
■
Phone security profile:
If the phone security profile for any of these endpoints has TFTP Encrypted Config
checked, you will not be able to use the endpoint via Mobile and Remote Access. This is because the
MRA solution does not support devices interacting with CAPF (Certificate Authority Proxy Function).
MRA solution does not support devices interacting with CAPF (Certificate Authority Proxy Function).
■
Trust list:
You cannot modify the root CA trust list on these endpoints. Make sure that the Expressway-E's
server certificate is signed by one of the CAs that the endpoints trust, and that the CA is trusted by the
Expressway-C and the Expressway-E.
Expressway-C and the Expressway-E.
■
Bandwidth restrictions:
The Maximum Session Bit Rate for Video Calls on the default region on Cisco
Unified Communications Manager is 384 kbps by default. The Default call bandwidth on Expressway-C is also
384 kbps by default. These settings may be too low to deliver the expected video quality for the DX Series.
384 kbps by default. These settings may be too low to deliver the expected video quality for the DX Series.
Hybrid Services and Expressway/VCS Rebranding
We have changed some terminology in this release:
■
Expressway/VCS base
In previous versions of the Cisco Expressway Series and the Cisco TelePresence Video Communication
Server, the software was always branded as "VCS Control" before you activated it with a release key.
Server, the software was always branded as "VCS Control" before you activated it with a release key.
In X8.7, the product is now called "Expressway/VCS base" when it is in this pre-activation state, which
shows that it can be activated as an Expressway or as a VCS.
shows that it can be activated as an Expressway or as a VCS.
These changes prepare us for a future release that will change the user experience of defining the purpose of
your Expressway.
your Expressway.
■
Hybrid Services
Version X8.6.1 included support for a feature called "Cloud Extensions". That feature has been renamed to
"Hybrid Services" in the UI, documentation, and Cloud Collaboration Management.
"Hybrid Services" in the UI, documentation, and Cloud Collaboration Management.
Hybrid Services is a group name for a family of user services that are delivered in part by the Cisco
Collaboration Cloud and in part by your on-premises equipment.
Collaboration Cloud and in part by your on-premises equipment.
The Expressway/VCS base does not need a release key to register for Hybrid Services. After you register the
Expressway/VCS base, it will be branded "Cisco Expressway base". You don't need to apply a release key for
subsequent upgrades.
Expressway/VCS base, it will be branded "Cisco Expressway base". You don't need to apply a release key for
subsequent upgrades.
Note:
For these reasons, we are requiring new Hybrid Services customers to use version X8.7. If you are using X8.6.1
for Hybrid Services, we strongly recommend upgrading to X8.7.
Hosting on VMWare vSphere 6.0
Expressway virtual machines can now run on VMware vSphere
®
version 6.0. Please be aware that we have noticed a
before
you upgrade.
You can install new Expressway OVAs on the ESXi 6.0 host, or you can migrate existing VMs. If you migrate a virtual
Expressway to a different host, you must shut it down before you move it.
Expressway to a different host, you must shut it down before you move it.
Note:
The virtual Expressway now has virtual hardware version 8. This means that new installations of virtual
Expressway require ESXi 5.0 or later, and will not run on ESX/ESXi 4.x or earlier.
5
Cisco Expressway Release Note
New Features in X8.7