Updates without release notes are ongoing maintenance releases. They are required updates to keep your Video Mesh deployment up to date and secure, but they do not contain changes that affect the functionality or fix specific customer-impacting bugs.

Download the Latest Video Mesh Node Software

For a new installation, always download a fresh copy of the Webex Video Mesh node software image from this link. Do not use an image from a past installation to deploy a Webex Video Mesh node.

For installation directions, go to https://www.cisco.com/go/video-mesh to access the Deployment Guide for Cisco Webex Video Mesh.

2020.11.17.2319m.4

November 25, 2020

  • No release notes for this maintenance upgrade.

2020.11.06.2314m

November 18, 2020

  • Increased the threshold for raising the NTP alarm on Video Mesh Nodes.

  • Increased the verbosity of error messages to help debug future NTP issues on Video Mesh Nodes.

  • Fixed an issue where VMN log uploads were failing.

  • Fixed cascade issues between Video Mesh Nodes and new cloud nodes.

2020.10.16.2305m

October 23, 2020

  • Fixed an issue where maintenance mode would not turn on properly in certain situations.

2020.09.22.2288m.3

October 1, 2020

  • No release notes for this maintenance upgrade.

2020.09.22.2288m

September 30, 2020

  • Added rate limits to the bandwidth tests on the Overview page.

  • Fixed an issue with the TCP reachability test.

  • Corrected latency/round-trip time values in media statistics on the meetings troubleshooting page in Control Hub. (The statistics were off for some calls by a factor of 1000.)

  • Made a change to use only more secure TLS ciphers on some ports.

2020.09.11.2279m

September 18, 2020

  • Added information about the IP address range that is reserved for internal use to the Video Mesh node web interface.

  • Reduced the IP address range that is reserved for Webex Video Mesh Node internal use from the original 172.17.0.0–172.17.255.255 (65,536 addresses) to 172.17.42.0–172.17.42.63 (64 addresses).

2020.08.31.2273m

September 8, 2020

  • Disabled TLS 1.1 on port 33432.

  • Fixed bad statistics shown on IX5000 presentation audio stream when moving between lobby and conference.

  • Added a workaround for an issue where a trusted SIP address longer than 200 characters causes TLS connection failure (CSCvv44969).

2020.08.19.2266m.1

August 26, 2020

  • Added DNS caching option. (See Announcements tab.)

  • Explicitly turned off IPv6 on internal and external interfaces so that nodes do not acquire IPv6 DNS servers.

  • Fixed an issue which led to reachability test failures due to port exhaustion.

  • Improved alarm detail in the case where an upgrade cannot be downloaded due to either blockage by the Zscaler service or because of a transparent inspecting proxy.

  • Fixed an issue where UDP upload/download data were incorrectly displayed in bandwidth test results on the web interface.

2020.08.06.2258m.4

August 18, 2020

  • No release notes for this maintenance upgrade.

2020.08.06.2258m.1

August 13, 2020

  • Fixed an issue where an IX5000 would drop the call when moved from a meeting back to the lobby.

  • Fixed an issue where a node configured to use explicit proxy could lose network connectivity if the Container Network IP address is changed.

2020.07.15.2245m

July 20, 2020

  • Changed the DNS resolution test to increase compatibility with older versions of Microsoft-based DNS servers.

  • Fixed an issue where audio received from the Webex Meetings app may be quieter than expected for the first few seconds after a period of silence.

2020.06.29.2236m.10

July 9, 2020

  • Changed the DNS resolution test behavior. Each configured DNS server now must be able to resolve the test FQDN in order for the DNS test to pass. (In earlier releases, if any DNS server was able to resolve the test FQDN, the test would pass.)

  • Improved media quality in lossy networks.

  • Added network interface MTU configuration options. (See Announcements tab.)

  • Added an alarm if the Video Mesh node isn’t able to reach any of the cloud media servers.

2020.06.18.2231m

June 26, 2020

  • Improved aspect ratio selection for bandwidths around 1.5Mbps when 1080p is enabled.

  • Added the ability to filter packet captures by network interface, by host, and by port.

  • Fixed a bug where you get an error if you start and then quickly stop packet capture.

  • Added support for VMNLite deployments. (See Announcements tab.)

  • Removed the default NTP configuration. A valid NTP configuration is now required to register a node. Added alarms if the NTP configuration is empty or the node is not able to reach a configured NTP server.

  • Fixed an issue where the proxy connectivity test would incorrectly report a failure due to a timeout that was too short.

  • Added shutdown and reboot functionality to the Video Mesh node web interface.

2020.05.26.2200m.3

June 10, 2020

  • Added the ability to toggle Maintenance Mode on and off from the Video Mesh node web interface Administration page.

  • Removed alarms and checks for Amazon ECR server connectivity from the node web interface Overview page.

  • Added an uptime counter to the node web interface Overview page.

  • Removed CPU utilization from the node web interface Overview page.

  • Disabled proxy connectivity tests to port 444 as part of transitioning cascade signaling to port 443.

2020.05.13.2195m

May 27, 2020

  • Fixed an issue where a third-party browser autofill extension could interfere with the Webex Video Mesh node web interface.

2020.04.16.2176m.2

May 8, 2020

  • Solved an issue where the port 444 connection checker would erroneously report a failure when behind certain types of proxies.

  • Fixed an issue where a mismatched server certificate was allowed to be installed if a correctly matched certificate was previously uploaded.

  • Disabled the websocket connectivity test after an issue was found with it when the node is behind an explicit proxy.

2020.04.16.2176m.1

April 24, 2020

  • Removed support for TLS1.1.

  • Added more Cloud Connectivity checks on the Overview page of the Webex Video Mesh node web interface.

  • Fix for an issue that was causing a false invalid hostname DNS alarm.

  • Added a key length constraint on the Server Certificate page, with an error message if an administrator uploads a server certificate of less than 2048 bits.

  • Improved handling of situations where an administrator enters a private key of less than 2048 bits or a private key with no passphrase. In these cases, the Video Mesh node will use a self-signed certificate.

2020.03.11.2143m.8

April 17, 2020

  • Fixed an issue that caused some clients to only get audio from the top two active speakers when someone is sharing content audio.

  • Fixed an issue that could cause call failures when lots of call attempts are made in a short period of time.

2020.03.11.2143m.7

April 6, 2020

  • Increased the bandwidth for 1080p calls from 3.25M to 4M.

  • Increased the timeout for multistream signalling for dual-screen calls.

  • Reduced the number of requests to the identity service.

  • Changed the way we handle OAuth verification to be more resilient to delayed responses.

2020.03.11.2143m.3

March 24, 2020

  • No release notes for this maintenance upgrade.

2020.03.11.2143m.9—Urgent upgrade

March 22, 2020

  • Added more logging for debug support.

2020.03.11.2143m—Urgent upgrade

March 11, 2020

  • Disabled the periodic call health checks and the corresponding alarm (mf.callHealth.fail) that was reported on the node and in Control Hub if failures occurred on the node beyond a certain threshold.

2020.03.02.2132m

March 6, 2020

  • Added support for NTLMv2 proxy authentication. (Video Mesh automatically detects the version, you do not need to specify it when configuring your proxy.)

  • Added an alarm that is reported on the node and in Control Hub if periodic call health test failures occur on the node beyond a certain threshold.

    Alarm id: 'mf.callHealth.fail', severity: "warning", title: 'Call Health Check has Failed'

2020.02.09.2120m.1

February 28, 2020

  • No release notes for this maintenance upgrade.

2020.01.30.2115m

February 7, 2020

  • Fixed CSCvs70769"NGINX HTTP Request Smuggling Vulnerability"

  • The Opus codec is enabled for 1:1 meetings and calls.

2020.01.12.2091m

January 22, 2020

  • Added factory reset to the web interface for Video Mesh nodes. For more information, see "Manage Video Mesh Node from the Web Interface" in the deployment guide at https://www.cisco.com/go/video-mesh.

  • Fixed an issue (CSCvs28104), where low quality video could be shown on some screens of an immersive three-screen endpoint.

  • Fixed an issue where some SIP calls experienced delayed setup.

2019.12.15.2053m

January 8, 2020

  • Fixed an issue where meetings (that included at least one Webex Board) sent low resolution video streams from SIP devices to Webex endpoints.

2019.12.03.2042m

December 12, 2019

  • Fixed an issue where the meeting join screen remained blank when *.clouddrive.com was blocked on a customer network. While the meeting join screen is no longer blank in this scenario, we still require that you unblock this URL on your network to avoid unintended side effects.

  • Added admin password management to the web interface for Video Mesh nodes. For more information, see "Manage Video Mesh Node from the Web Interface" in the deployment guide at https://www.cisco.com/go/video-mesh.

2019.11.06.1992m

November 14, 2019

  • Fixed CSCvr92794"Incorrect error msg on FQDN validation against node IP."

  • Fixed an issue where nodes were not quiescing properly and were using a short timeout, which happened only when other nodes in the cluster were moved to maintenance mode in Control Hub, leading to reduced capacity and dropped calls.

2019.10.21.1973m.1

November 1, 2019

2019.10.11.1964m.1

October 23, 2019

  • Fixed CSCvr39819"Vulnerable Software Version".

  • Fixed CSCvr39878"X.509 Self-Signed Certificate whose common name does not match the issuing server (SSL/TLS)". Made a change where the common name of the certificate on the node gives the node's FQDN (if available) or the IP address.

  • Added a new "Subject Alternative Name(s):" field to the CSR creation form in the web interface.

2019.09.19.1956m

September 26, 2019

  • Added network settings to the Video Mesh node web user interface (UI). For more information, see Configure Network Settings from Webex Video Mesh Node Web Interface.

  • Changed this alarm's severity from critical to warning: "The Video Mesh Node was not able to download the required software from the Cisco cloud provider. The problem can happen because of multiple issues that are related to the network. Check your network connectivity to the public network (.amazonaws.com) and check your DNS settings. This can also happen because of changes to the firewall that is present between Video Mesh nodes and the internet."

  • Fixed an issue where reflector server ports were not being released even after the reflector tool is stopped in the node's web UI.

  • Fixed a vulnerability that affected the Ping and Check NTP APIs where an attacker could launch a command injection attack if they had access to authenticated APIs.

  • Improved the codec selection for transmitted video.

  • Server certificates that are signed with weak ciphers (like MD2 or MD5) are no longer accepted in the Video Mesh node certificate UI.

2019.08.21.1941m.2

September 13, 2019

  • Fixed an issue where the node CPU levels spiked and wouldn't return to acceptable levels.

  • Fixed an issue where content sent by participants connected to a cloud node would not be received by participants connected to on-premises nodes, if there is a Palo Alto Networks (PAN) firewall in the network.

  • Added a network configuration page to the node software image. Admins can specify the network settings during first time setup of the node virtual machine. See Install Webex Video Mesh Node Software in the deployment guide for more information.

2019.08.14.1937m

August 16, 2019

  • Added support for explicit proxies with no-auth, basic, digest, or NTLM authentication. For more information, see Proxy Support for Video Mesh and other relevant updates in the deployment guide.

  • Added a config changes that prevents some overflow of calls to the cloud.

2019.08.01.1929m

August 8, 2019

  • Fixed two issues:

    • Packet capture from the web UI was failing to start successfully but no error message appeared.

    • Packet capture wouldn't run because Ubuntu URLs were blocked. (With this fix, no URL changes are required on your firewall.)

2019.07.12.1917m

July 25, 2019

  • Removed cascades information from the Call Status card in the node web interface until better metrics are available.

  • Added OS version to the Node Details card in the node web interface.

  • Redesigned the user interface for the Troubleshooting page on the node web interface. (See the deployment guide for more information.)

  • Added connectivity checks using ping, traceroute, and NTP verification in the node web interface. (See the deployment guide for more information.)

  • Improved resolution and framerate choice for presentation streams.

  • Fixed an issue where too much bandwidth was sometimes sent to switched participants.

  • Fixed an issue where no unmute option was available for some participant types when they were muted by the host.

  • Improved the pacing of media for transcoded presentations.

2019.06.13.1907m.7

July 12, 2019

  • Fixed an issue that sometimes caused video resolution to drop even when no packets were lost and latency was low.

  • Fixed an issue where split audio sometimes occurred when participants were muted by the host and then unmuted.

2019.06.13.1907m.3

June 20, 2019

  • Fixed an issue where the presentation sharing state was incorrect if an endpoint tried to share while on the lobby screen.

  • Added an enhancement to speed up the start of presentation sharing when transcoded.

2019.06.13.1907m.1

June 14, 2019

  • Fixed an issue where some Video Mesh nodes were not automatically rebooting after an upgrade, which disabled the node's troubleshooting features and led to missing information on the overview page.

  • Added a requirement that node hostnames cannot contain an underscore (_) character.

  • Fixed an issue where packet loss resilience sometimes did not work for the first few minutes of a meeting.

  • Fixed an issue with media resilience that sometimes caused the bandwidth in use to significantly exceed the negotiated bandwidth for a brief period of time.

2019.05.20.1892m1

May 24, 2019

  • Added new serviceability features to the Video Mesh node web interface (packet capture generation, log generation, and overview page enhancements). For more information about these features, see the "Manage Webex Video Mesh" chapter in the deployment guide at https://www.cisco.com/go/video-mesh.

  • Added new alarm as part of the upcoming migration to the Amazon elastic container registry: "The Video Mesh Node was not able to download the required software from the Cisco cloud provider. The problem can happen because of multiple issues that are related to the network. Check your network connectivity to the public network and check your DNS settings. This can also happen because of changes to the firewall that is present between Video Mesh nodes and the internet."


    Video Mesh nodes will continue to upgrade, but you should take appropriate action to ensure that Video Mesh nodes can access the URL. For more information, see the Announcements tab.

  • Fixed an issue where Skype for Business meetings incorrectly showed "l2sip-UA" as the meeting title and participant name.

2019.04.29.1873m.4

May 13, 2019

  • Fixed an issue that caused content sharing to sometimes not be available when using SIP dial-out.

  • Fixed an issue that caused cascades to sometimes not be recreated after temporary network issues, which led to split meetings.

  • Fixed an issue that caused content share to fail in some scenarios.

2019.04.29.1873m

April 30, 2019

  • No release notes for this maintenance upgrade.

2019.04.18.1869m.1

April 26, 2019

  • Fixed an issue that caused wireless share from Webex Teams for Windows to not work in some cases.

2019.03.22.1829m.2

April 2, 2019

  • Fixed an issue that sometimes caused UDP bandwidth tests to fail.

  • Fixed an issue where NTP alarms on Control Hub didn't get removed once a faulty NTP server started functioning.

2019.03.19.1826m

March 22, 2019

  • To make any configuration changes on a registered node, you must now put the node in maintenance mode first.

  • The overview status page reports the connectivity check result for the Amazon container registry (ECR).

  • Fixed an issue where there was a delay on some clients when switching active speakers and corrupted video when there was packet loss.

  • Fixed CSCvo93454"One Way Video when Immersive System joins Webex."

  • Fixed CSCvo87069"Video Mesh SIP Trusted Sources not Populating"

2019.02.14.1788m.1

February 21, 2019

  • Fixed an issue where three-screen endpoints were not being remotely muted by the Webex host.

  • Fixed an issue where muting and unmuting sometimes didn't work for SIP endpoints.

  • Video Mesh nodes now attempt to access a new URL for testing access to the Amazon-hosted container registry (https://615440818562.dkr.ecr.us-east-1.amazonaws.com/).

  • Added new alarms that are generated on the Video Mesh nodes and are displayed in Control Hub when DNS query response time exceeds 1.5s in these scenarios:

    • When DNS server query time is longer than 1.5s: “DNS server <x>’s query response time of <number> ms exceeeds the maximum response time of 1500 ms.”

    • Alarm text for when DNS server query time is longer than 1.5s while resolving an NTP server: “While resolving <ntp-server>; DNS server(s) <x>’s query response time of <number> ms exceeeded the maximum response time of 1500 ms.”

2019.02.12.1786m

February 15, 2019

  • This version is the candidate release for the TLS SIP trunk and transparent inspecting/non-inspecting proxy support for Video Mesh. For more information, see the deployment guide at https://www.cisco.com/go/video-mesh.

  • Fixed CSCvo26600"Token validator doesn't get token validation key if initial CI request fails"

2019.01.29.1773m

February 6, 2019

  • This version is the candidate release for the dual network interface feature. For more information, see the deployment guide at https://www.cisco.com/go/video-mesh.

  • Added new checks to periodically verify the validity of NTP servers that are configured on the Video Mesh nodes. Invalid NTP server warning messages are displayed on the Video Mesh admin interface on login and as alarms in Control Hub.

2019.01.14.1764m.1

January 18, 2019

  • Fixed an issue where video was only transmitted one way during a meeting and some devices or clients couldn't see the video stream.

2018.10.04.1692m

October 5, 2018

  • No release notes for this maintenance upgrade.

This page covers announcements to help you prepare your Webex Video Mesh deployment for new releases.

Go to https://www.cisco.com/go/video-mesh to access the Deployment Guide for Cisco Webex Video Mesh.

August 26, 2020

DNS Caching

If you notice that DNS responses to your Video Mesh nodes regularly take more than 750 ms, or if the Cisco TAC recommends it, you can enable DNS caching. With DNS caching on, the node caches DNS responses locally, making requests less prone to delay or timeouts that can lead to connectivity alarms, call drops or call quality issues. DNS caching can also reduce the load on your DNS infrastructure.

DNS caching is currently disabled by default. To turn it on, see the Enable or Disable DNS Caching section in the deployment guide at https://www.cisco.com/go/video-mesh.

Webex Events Support

Webex Video Mesh now supports Webex Events.

August 7, 2020

Short Video Address Format for Webex Meetings

On WBS39.9 and later sites, users can join meetings using the shorter <meeting_number>@webex.com video address format (instead of <meeting_number>@<site_name>.webex.com). Video Mesh now supports this shorter address format.

The deployment guide at https://www.cisco.com/go/video-mesh has been updated with instructions on handling the shorter format when setting up a Video Mesh deployment.

To use the short video address format with an existing Video Mesh deployment, you may need to add a route or dial pattern to handle the format. See the step that includes "short video address" in the appropriate section of the guide, depending on how you configured your call control environment:

By default, meeting invitations currently still use the longer format. To change this for your Webex site, see Display the Short Video Address Format for Webex Meetings and Events.

July 9, 2020

New Network Interface MTU Configuration Settings in the Video Mesh Node Web Interface

You can now manually set the maximum transmission unit (MTU) size on the internal network interface and the MTU on the external network interface, if enabled.

All Webex Video Mesh nodes have path MTU (PMTU) discovery enabled by default. With PMTU, the node can detect MTU issues and adjust the MTU size automatically. When PMTU fails because of firewall or network issues, the node can have connectivity issues to the cloud because packets larger than the MTU drop. Manually setting a lower MTU size can fix this issue.

You can find the manual MTU settings on the network settings page Advanced tab in the Webex Video Mesh Node web interface. For more information, see the deployment guide at https://www.cisco.com/go/video-mesh.

June 26, 2020

New VMNLite Deployment Option

If your Webex Video Mesh deployment mainly includes Webex Teams and cloud-registered endpoints, your nodes utilize more switching and fewer transcoding resources than the standard configuration provides. Deploying more, smaller virtual machines on the host optimizes resources for this scenario.

For this reason, we’re introducing a new "VMNLite" option for deploying multiple Webex Video Mesh Nodes to your host server running VMware ESXI or vCenter. VMNLite requires the following specifications for each virtual machine:

  • 23 vCPUs for Webex Video Mesh Node

  • 20 GB main memory

  • 80 GB local hard disk space

With these specifications, you can deploy (or replace a singe existing virtual machine with) multiple instances, depending on the hardware:

Cisco Meeting Server 1000

(CMS 1000)

3 VMNLite virtual machines

(3 Video Mesh Nodes)

Cisco Multiparty Media 410v server

2 VMNLite virtual machines

(2 Video Mesh Nodes)

Our testing shows a 50% improvement in switched call performance with 3 VMNLite nodes on a single CMS1000 compared to deploying a single virtual machine.

As with the standard configuration, coresidency with other services is not permitted on VMNLite virtual machines.

For more information, see the deployment guide at https://www.cisco.com/go/video-mesh. For steps to replace your standard configuration with VMNLite, see the "Manage and Troubleshoot Webex Video Mesh" chapter.

June 9, 2020

New Weekly Automatic Software Upgrade Option for Video Mesh Clusters

You can now schedule automatic software upgrades on your Video Mesh clusters to happen on a weekly basis instead of daily (the default). You can postpone an upgrade one time. If you set a weekly schedule, postponing means the upgrade will occur during the following week's upgrade window.

You can set the upgrade schedule while registering a new cluster, or modify the schedule of an existing cluster. For more information, see the Video Mesh documentation at https://www.cisco.com/go/video-mesh.

April 24, 2020

New Network Configuration Options (External Network Interface, Routing Rules, Container Network) in the Video Mesh Node Web Interface

The Webex Video Mesh web interface contains more new features to make handling network changes easier. You can enable the external interface in a dual network interface (NIC) deployment from the web interface. You can then fine tune the routing for Video Mesh nodes by adding user-defined route rules for external and internal interfaces. And you can change the container bridge IP address and subnet.

For more information about how to access the updates to the web interface, see the "Manage and Troubleshoot Webex Video Mesh" chapter in the deployment guide at https://www.cisco.com/go/video-mesh.

March 20, 2020

Cisco Webex Teams EMEAR Data Residency Support

Webex Video Mesh is now supported for organizations in the Cisco Webex Teams European data residency region. This support includes both newly created phase 2 EMEAR organizations and existing phase 1 EMEAR organizations.

For more information, see Data Residency in Cisco Webex Teams.

November 4, 2019

New Enhancements to Video Mesh Reports: Analytics and Recent Resource Usage

You can now access two categories of reports to help you manage your Video Mesh deployment: analytics and recent resource usage.

The analytics are new interactive reports that provide a long-term trend (up to 3 months of data) in the categories of engagement, resource usage, and bandwidth usage.

The recent resource usage reports were previously available and are moved to the Troubleshooting page in Control Hub. They provide a near-realtime view of activity in your organization.

You can filter these reports on specific data that you're looking for and save them as various file types directly from Control Hub. For more information, see the Video Mesh documentation at https://www.cisco.com/go/video-mesh.

August 16, 2019

Support for Explicit Proxies

Cisco Webex Video Mesh now supports explicit proxies, in addition to transparent inspecting and non-inspecting proxies. You can tie these proxies to your Webex Video Mesh deployment so that you can secure and monitor traffic from the enterprise out to the cloud. This feature sends signaling and management https-based traffic to the proxy. For transparent proxies, network requests from Video Mesh nodes are forwarded to a specific proxy through enterprise network routing rules. You can use the Webex Video Mesh admin interface for certificate management and the overall connectivity status after you implement the proxy with the nodes.


Media does not travel through the proxy. You must still open the required ports for media streams to reach the cloud directly.

For more information, see Proxy Support for Video Mesh and other relevant updates in the deployment guide.

July 25, 2019

New Troubleshooting Features (Ping, Trace Route, NTP Server, Reflector Server, and Debug Account) in the Video Mesh Node Web Interface

The Webex Video Mesh web interface contains more new features to make troubleshooting easier. You can run various network tests (ping, trace route, and NTP server verification) from the web interface. You can also verify that the applicable ports are opened on your network by using the Reflector Server. When you need help from Cisco support engineers, you can create a temporary debug user account so they can troubleshoot your deployment.

For more information about how to access the updates to the web interface, see the "Manage and Troubleshoot Webex Video Mesh" chapter in the deployment guide at https://www.cisco.com/go/video-mesh.

May 24, 2019

New Troubleshooting Features (Logs, Packet Captures) and Revamped Overview in the Video Mesh Node Web Interface

The Webex Video Mesh web interface now contains new features to make troubleshooting easier. You can generate logs and packet captures from the node itself and submit them to Cisco support when they're ready.

The web interface also contains a redesigned Overview page that contains helpful information about the node, such as node health, registration information, connectivity test results, and so on.

For more information about how to access the updates to the web interface, see the "Manage and Troubleshoot Webex Video Mesh" chapter in the deployment guide at https://www.cisco.com/go/video-mesh.

Migration From Docker Hub to Amazon Elastic Container Registry

In an effort to reduce the number of different domains accessed by the Video Mesh node, we are moving from the Docker hub domains (.docker.io and .docker.com) to the Amazon elastic container registry (*.amazonaws.com). This migration will occur in approximately 6–8 weeks from the time of this posting. As a preparatory step, you must ensure that Video Mesh node registered to your Webex organization can communicate with the *.amazonaws.com domain, otherwise future upgrades of the Video Mesh Node containers will fail. Check your firewall and/or proxy settings to ensure traffic from the Video Mesh node is allowed out to the *.amazonaws.com domain.

After you make the change to your firewall or proxy, you can check the connectivity to the *.amazonaws.com domain by logging into the Video Mesh node web interface. The connectivity checking capability to Amazon was included in the 2019.03.19.1826m software release and you must be running this software in order to validate your connectivity to the *.amazonaws.com domain.

  1. Navigate to your Video Mesh node web interface (https://%VMN_IP%/setup), and choose Overview.

  2. In the Connectivity Details section check the status of Cloud Connectivity Check.


    If the connectivity details are red, this indicates the connectivity check to Amazon failed and further remediation is required.

February 15, 2019

Secure SIP Trunk and Transparent Proxy Support

Webex Video Mesh now supports a secure trunk connection from Unified CM to Video Mesh nodes and secure exchange of certificates. With this option, end-to-end encryption is required from the cloud down to the premises registered endpoints.

Webex Video Mesh also supports transparent inspecting and non-inspecting proxies so that you can secure and monitor enterprise to cloud traffic.

For more information on using these features in a Video Mesh node deployment, see the deployment guide at https://www.cisco.com/go/video-mesh.

February 7, 2019

Dual Network Interface for Video Mesh Nodes

For a DMZ deployment, you can now set up the Video Mesh nodes in a cluster with the dual network interface (NIC). This deployment option lets you segregate the enterprise network traffic from cloud network traffic on the Video Mesh node: the internal (enterprise-facing) NIC is used for inter-box communication, cascades between node clusters, and to access the node's management interface, whereas the external (cloud-facing) NIC is used primarily for connectivity to the outside world and cascades to the cloud.

For more information on using this feature in a Video Mesh node deployment, see the deployment guide at https://www.cisco.com/go/video-mesh.

September 18, 2018

Quality of Service (QoS) Enhancements for Webex Video Mesh

Webex Video Mesh nodes now conform to recommended quality of service (QoS) best practices by enabling port ranges that allow you to differentiate audio and video streams in all flows to and from the Video Mesh nodes. This change will let you create QoS policies and effectively remark traffic to and from the Video Mesh Nodes.

Accompanying these port changes are QoS changes. Webex Video Mesh nodes automatically mark media traffic from SIP registered endpoints (on-premises Unified CM or VCS Expressway registered) for both audio (EF) and video (AF41) separately with appropriate class of service and use well-known port ranges for specific media types.

The source traffic from the on-premises registered endpoints is always determined by the configuration on the call control (Unified CM or VCS Expressway).

For more information, see the QoS table at Ports and Protocols Used by Webex Video Mesh and the steps to enable or disable QoS in the Video Mesh Deployment Task Flow in the Deployment Guide for Cisco Webex Video Mesh (https://www.cisco.com/go/video-mesh).


Cisco Webex Teams apps continue to connect to Webex Video Mesh nodes over shared ports 5004 and 5006. These ports are also used by Cisco Webex Teams apps and endpoints for STUN reachability tests to Webex Video Mesh nodes. Webex Video Mesh node to Webex Video Mesh node for cascades use a destination shared port of 5004 or 5006.

February 12, 2018

Multistreaming Support for All Participants in Cisco Spark and Cisco WebEx Meetings

If you host meetings on local hybrid media nodes through Cisco Spark Hybrid Media Service, you can take advantage of features included in multistreaming support. Multistream provides better bandwidth utilization on average, particularly for the cascade link between the Hybrid Media Service nodes and the Cisco Spark public cloud media nodes.

For more information, see Multistreaming Support for All Participants in Cisco Spark and Cisco WebEx Meetings.

January 5, 2018

Support for Cisco WebEx and Cisco Spark Meetings, Port Changes, and OVA Update

Cisco Spark Hybrid Media Service now supports on-premises SIP registered endpoints joining Cisco WebEx meetings and Cisco Spark meetings. The service also includes new usage and adoption reports in Cisco Webex Control Hub. You must make sure your WebEx site is on the Cisco WebEx video platform version 2.0 to take full advantage of Hybrid Media Service. (You can verify that your WebEx site is on video platform version 2.0 if it has the Media Resource Type list available in the Cloud Collaboration Meeting Room site options.)

Port Changes

  • The Hybrid Media Service now requires a new destination port (5006).

  • TCP/UDP Port 33434 is no longer supported by the service.

For a full list, see "Ports and Protocols Used by Hybrid Media Service" in the Deployment Guide for Cisco Spark Hybrid Media Service.

OVA Update

The service requires you to download and install the latest OVA update on your Hybrid Media Nodes. To download the latest OVA, from the customer view in https://admin.ciscospark.com, go to Services > Hybrid Media > Set Up > Settings.

Upgrade each Hybrid Media Node in your cluster by doing the following steps:

  1. Move the node to maintenance mode. See Move a Hybrid Service Node in to Maintenance Mode.

  2. Deregister the node. See "Deregister Hybrid Media Node" in the Deployment Guide for Cisco Spark Hybrid Media Service.

  3. Delete the Hybrid Media Node VM from the VMware vSphere client or from vCenter.

  4. Install the new Hybrid Media Service OVA and software, set the newtork configuration, and reregister the Hybrid Media Node to the Cisco Collaboration Cloud. See "Deploy Hybrid Media Service" in the Deployment Guide for Cisco Spark Hybrid Media Service.

  5. Move the node out of maintenance mode. See Move a Hybrid Service Node in to Maintenance Mode.

To read about all the feature changes, new deployment steps, and guidance for preparing the WebEx site, see the Deployment Guide for Cisco Spark Hybrid Media Service at https://www.cisco.com/go/hybrid-services-media. The New and Changed Information section of the guide links to updated sections.