Cisco Cisco Expressway 發佈版本通知
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.1
* 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.
■
There is a new document to help you get Cisco Jabber integrated with Microsoft Skype for Business clients.
Note that this integration relies on Lync Server 2013 or 2010; Skype for Business Server 2015 is not yet fully
supported across all Cisco infrastructure in this deployment.
Note that this integration relies on Lync Server 2013 or 2010; Skype for Business Server 2015 is not yet fully
supported across all Cisco infrastructure in this deployment.
See Cisco Jabber and Microsoft Skype for Business Infrastructure Configuration Cheatsheet on the
Multistream Support
The Expressway now supports passthrough of encrypted and unencrypted multistream calls. It also supports
passthrough of the encrypted iX protocol required for the ActiveControl feature used by endpoints interacting with the
TelePresence Server.
passthrough of the encrypted iX protocol required for the ActiveControl feature used by endpoints interacting with the
TelePresence Server.
There is a new "Multistream mode" on all zone types that can potentially handle media. The mode is enabled by
default, but it only applies when the zone passes media to or from the back to back user agent. The signaling of
multistream calls is always passed through, irrespective of the zone's multistream mode setting.
default, but it only applies when the zone passes media to or from the back to back user agent. The signaling of
multistream calls is always passed through, irrespective of the zone's multistream mode setting.
Note:
■
The Expressway does not encrypt the iX protocol on behalf of other entities; iX must either be encrypted from
end to end, with the endpoints and TelePresence Server doing the encryption, or it must be unencrypted from
end to end.
end to end, with the endpoints and TelePresence Server doing the encryption, or it must be unencrypted from
end to end.
Service Setup Wizard
The Expressway can be used in different ways, some of which do not work together. Version X8.8 improves the user
experience of configuring the Expressway for its chosen purpose in your environment.
experience of configuring the Expressway for its chosen purpose in your environment.
9
Cisco Expressway Series Release Notes
Features in X8.8