Cisco Cisco Expressway 發佈版本通知
■
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
or the Cisco Single Expressway-C Basic Configuration Deployment Guide available at the
.
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
Table 4 Lync and Skype for Business Support Introduced in X8.8.3
* 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.
Broker for Microsoft SIP Traffic
In some previous versions of our Cisco Expressway and Microsoft Interoperability Deployment Guide, we published
an appendix describing how to get Lync to Jabber messaging working using CPL on a "directory Expressway".
an appendix describing how to get Lync to Jabber messaging working using CPL on a "directory Expressway".
In X8.8, we have improved that deployment by creating an independent broker to perform the task of filtering and
redirecting the messaging and presence traffic coming from the Microsoft infrastructure. This change has the
following benefits:
redirecting the messaging and presence traffic coming from the Microsoft infrastructure. This change has the
following benefits:
■
Maintains the robustness of the SDP parser, by not requiring it to process the non-standard SIP from Microsoft
infrastructure
infrastructure
■
No requirement for a directory Expressway, because the broker is hosted on the Gateway Expressway.
■
The broker is abstracted from the rest of the software so you can disable it if you don't need it.
■
If you were using the CPL deployment, you can now upgrade to X8.8 and benefit from the other features and
improvements since X8.6.
improvements since X8.6.
9
Cisco Expressway Series Release Notes
Features in X8.8