Cisco Cisco Expressway Release Notes
■
Registrations from outside the network are proxied to the Expressway-C by the Expressway-E. The
Expressway-E cannot accept direct registrations.
Expressway-E cannot accept direct registrations.
■
Device provisioning and FindMe are supported with Cisco TelePresence Management Suite.
■
H.323 registrations are not currently supported.
■
The Medium VM (or CE1100 with 1 GBps NIC) can support up to 2500 registrations. The Large VM (or CE1100
with 10 GBps NIC) can support up to 5000 registrations.
with 10 GBps NIC) can support up to 5000 registrations.
Local registrations, proxy registrations (via Expressway-E), and MRA registrations (proxied to CUCM), all count
towards this number.
towards this number.
Implications of the new licensing model:
■
Rich Media Session license usage has been reduced, following the principle that if you have already paid for a
registration license you should not also pay for the Rich Media Session.
registration license you should not also pay for the Rich Media Session.
■
Calls between registered systems do not use RMS licenses. Here, "registered systems" means systems
registered directly to the Expressway-C, by proxy to the Expressway-C through the Expressway-E, or by proxy
through the Expressway pair (MRA) to neighbored Unified CMs.
registered directly to the Expressway-C, by proxy to the Expressway-C through the Expressway-E, or by proxy
through the Expressway pair (MRA) to neighbored Unified CMs.
■
Calls from registered systems (as above) to Cisco infrastructure do not use RMS licenses. Currently, this
extends only to Cisco Meeting Server, or to TelePresence Server when managed by TelePresence Conductor.
extends only to Cisco Meeting Server, or to TelePresence Server when managed by TelePresence Conductor.
■
Calls from registered systems (as above) to Cisco Collaboration Cloud do not use RMS licenses.
■
Calls from registered systems to all other systems will use one RMS license, whenever those calls require the
Expressway to process the media streams. This includes, but is not limited to, the following call types:
Expressway to process the media streams. This includes, but is not limited to, the following call types:
—
Business to business calls: previously required two RMS licenses, now require one on Expressway-E
—
Business to consumer calls (Jabber Guest): previously required two RMS licenses, now require one on the
Expressway-E
Expressway-E
—
Interoperability gateway calls (including Microsoft Lync / Skype for Business and third-party call control
servers where interworking is required): require one RMS license on the Expressway-C.
servers where interworking is required): require one RMS license on the Expressway-C.
For more information, see the Cisco Expressway Administrator Guide available at
To order registration licenses for the Expressway, see Cisco Expressway version X8.8 and Cisco TelePresence Video
Communication Server (VCS) version X8.8 Ordering Guide at
Communication Server (VCS) version X8.8 Ordering Guide at
Skype for Business 2016 and Skype for Business Mobile Support
We have updated our support for Microsoft client and server combinations. The Gateway Expressway deployment is
now interoperable with the following Microsoft collaboration products:
now interoperable with the following Microsoft collaboration products:
Clients
On Lync Server 2013
On Skype for Business Server 2015
Skype for Business 2016 (Windows desktop)
Supported
Supported
Skype for Business 2015 (Windows desktop)
Supported
Supported
Skype for Business for iOS
Not supported
Limited support*
Skype for Business for Android
Not supported
Limited support*
Table 4 Lync and Skype for Business Support Introduced in X8.8
* We do not support these clients in calls to MCU bridges. We do support them in other call scenarios, including calls
to TelePresence Server bridges.
to TelePresence Server bridges.
6
Cisco Expressway Series Release Notes
New Features in X8.8