nomaddefense.blogg.se - Cisco cucm 8.6 release notes

#CISCO CUCM 8.6 RELEASE NOTES INSTALL#
#CISCO CUCM 8.6 RELEASE NOTES SERIES#

If you configure a trunk towards CUCM 8.6, you must create a custom SIP trunk that does not remove BFCP lines towards CUCM.

#CISCO CUCM 8.6 RELEASE NOTES INSTALL#

We recommend that you install and assign the Cisco Unified CM "vcs-interop" SIP Normalization script to make secure calls between CTS endpoints and endpoints and devices registered to VCS.įor more information about the conditions required for secure calls, see this document:įor more information about the Cisco Unified CM script, see this document:įor more information about configuring Unified CM and VCS to interoperate via a SIP trunk, see Cisco VCS and CUCM Deployment Guide.įor more information about products that are compatible with systems running CTS 1.10 software, refer to the Cisco TelePresence System Software Version Compatibility - 1.10 Releases document at the following URL: Ĭisco TelePresence System Quick Set C20, Cisco TelePresence Codec C40, Cisco TelePresence Codec C60, Cisco TelePresence Codec C90, Cisco TelePresence System EX60, Cisco TelePresence System EX90, Cisco TelePresence MX200, Cisco TelePresence MX300, Cisco TelePresence SX20 Quick Set, Cisco TelePresence System Integrator C Series, Cisco TelePresence System EX Series, Cisco TelePresence MX Seriesīoth Assent and H.460.18/.19 traversal technologies are supported This caveat is fixed in Unified CM 9.1(1) and appears in the Release Notes for Cisco TelePresence System Software Release 1.9. Caveat that tracks this issue: CSCtx16122.

x endpoint registered to VCS X7.1 or X7.0, an intermittent loss of audio can occur. In an H.323 call between a TX 6.0 endpoint registered to a UCM server running 8.6(2a)SU3 and a TC 5. Tested to work if the system running CTS software is registered to Cisco Unified Communications Manager Version 9.1(1) or 8.6(2a)SU3. If you choose CUCM as profile in the VCS, BFCP will be removed and dual stream (BFCP) will not be possible between CUCM and VCS. If you configure a trunk towards CUCM 8.6 or 9.0, you must create a custom SIP trunk that does not remove BFCP lines towards CUCM.

#CISCO CUCM 8.6 RELEASE NOTES SERIES#

An endpoint, for example CTS, may end up in a half encrypted call where the call leg from CTS > CUCM > VCS is unencrypted and the call leg from VCS > MCU is encrypted.Ĭisco TelePresence C Series, Cisco TelePresence MX Series, Cisco TelePresence SX20 Quick Set, Cisco TelePresence System EX Series, Cisco TelePresence System Integrator C Series.

This is because the first endpoint is not aware that streaming has ended and is expecting to receive further content.

If a call is made between an endpoint and an MCU, with the endpoint using SIP and the MCU using H.323, and a second endpoint joins the conference and sends a content stream (any protocol) to the MCU, the first endpoint display will freeze or go black when the second endpoint stops streaming content.

4200 series, 4500 series, 8000 series, Cisco TelePresence MCU Series products