Understanding the call flows

for the Video Mesh Solution

BRKCOL-2750

Richard Murphy, Technical Marketing Engineer - Technical Leader

@RichardF_Murphy

BRKCOL-2750
 • Overview
• Webex Suite Meetings Platform
• Sizing
• Connectivity to the VMN
• Cascades
Private Meetings
Agenda
•

• Troubleshooting
• APIs

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Overview of
Video Mesh
 The benefits of Video Mesh

Lower bandwidth costs Migrate at your own pace

Attendees connect Enjoy the benefits of the cloud
automatically to the closest data while remaining on-premises
center, reducing bandwidth and securing your investments.
usage and latency.

Simplified management
Enhanced User Experience
Effortlessly deployed and
An enriched calling and meeting
managed through the cloud with
experience while scaling
a centralized portal.
capacity to the cloud as needed.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 5
What is Video Mesh?
• Dockerized deployment of Webex cloud media services on the customer premises for a high-quality
hybrid meeting experience.
• Cisco CMS1000, Cisco CMS2000, or customer’s hardware can be used to install Video Mesh
software, requires VMware also.
• Management, analytics, and troubleshooting via the Webex Control Hub.
• Automatic discovery of media resources and placement of participants in meetings for optimal media
utilization.
• Intelligent overflow of a participant to the Webex cloud when the Video Mesh Node on the customer
premises’ capacity is reached to ensure seamless meeting experience.
• Zero touch upgrades from the cloud to keep in sync with Webex enhancements.
• Secure on-premises Private Meetings to keep all meeting media on the customer’s network.
• Rich set of provisioning and troubleshooting APIs for seamless onboarding, quick fault isolation, and
native integration with the customers’ 3rd party monitoring apps.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
Architecture
Webex Video Mesh

Unified CM Expressway-C Expressway-E

Internet

OR

Webex Video Mesh node Webex Video Mesh node

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
 Webex Video Mesh
Corporate Network
Video
Mesh node
Cascade Link

Webex Meetings &

Webex Apps,
or Skype for Business

On-premises registered Cisco and third-party Webex-registered

Webex-registered devices, and standards-based SIP endpoints and standards-based devices and Webex App
any standards-based SIP/H.323 SIP clients
endpoints

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
 Video Mesh supported devices and apps
Supported Unsupported
✅ Any Webex registered device
• SX, MX, DX, Room series, Webex Board, Webex Share, Desk series
❌Webex Calling-registered phones

✅ Webex App browser client ❌ Webex Meetings client

• web.webex.com
❌ Webex App with the Full Featured
✅Webex App (without the Full Featured Webex Experience Webex Experience
toggle)
• Desktop and Mobile ❌ Webex callback to a SIP URI that is to an
on premises-registered endpoint
✅ Unified CM registered devices
• Calling a Webex scheduled meeting or personal room.
• Edge for Devices with Webex Optimized Experience
• Webex Join Protocol = Webex and Cloud upgrade mode on

• On-premises UCM and UCM cloud

• SX, MX, DX, Room series, Desk series, Jabber

✅ Cisco VCS/Exp. registered devices

• Calling a Webex scheduled meeting or personal room.
• SIP or H.323 (requires Interworking)

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
 Hardware Requirements
Platform Specifications Notes

Cisco Meeting Server 1000 • 72vCPUs

• 60GB main memory
• 80GB local hard disk space

Cisco Meeting Server 2000 • 72vCPUs • Each blade must be a complete Cisco Meeting Server 1000 with
• 60GB main memory dedicated CPU, RAM and hard drives per blade.
• 80GB local hard disk space

OR
• Each blade must have dedicated CPU and RAM.
• 72vCPUs • Peak IOPs (input/output operations per second) for NFS storage
• 60GB main memory is 300 IOPS.
• 80GB of NFS storage

Specification based configuration • 2.6 GHz Intel Xeon E5-2600v3 or later • Each Video Mesh virtual machine must have dedicated CPU,
processor RAM and hard drives.
• 72vCPUs
• 60GB main memory
• 80GB local hard disk space

OR

• 2.6 GHz Intel Xeon E5-2600v3 or later • Each Video Mesh virtual machine must have CPU and RAM
processor reserved for itself.
• 72vCPUs • Peak IOPs (input/output operations per second) for NFS storage
• 60GB main memory is 300 IOPS.
• 80GB of NFS storage

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 10
 Hardware Requirements
Platform Specifications Notes

Cisco Meeting Server 1000 • 72vCPUs

• 60GB main memory
• 80GB local hard disk space

Cisco Meeting Server 2000 • 72vCPUs • Each blade must be a complete Cisco Meeting Server 1000 with
• 60GB main memory dedicated CPU, RAM and hard drives per blade.
• 80GB local hard disk space

OR
• Each blade must have dedicated CPU and RAM.
• 72vCPUs • Peak IOPs (input/output operations per second) for NFS storage
• 60GB main memory is 300 IOPS.
• 80GB of NFS storage

Specification based configuration • 2.6 GHz Intel Xeon E5-2600v3 or later • Each Video Mesh virtual machine must have dedicated CPU,
processor RAM and hard drives.
• 72vCPUs
• 60GB main memory
• 80GB local hard disk space

OR

• 2.6 GHz Intel Xeon E5-2600v3 or later • Each Video Mesh virtual machine must have CPU and RAM
processor reserved for itself.
• 72vCPUs • Peak IOPs (input/output operations per second) for NFS storage
• 60GB main memory is 300 IOPS.
• 80GB of NFS storage

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 11
Capacity – Full Version of software
What can impact capacity of the node?

• Types of devices and clients in the meeting

• Video resolution requirements in the meeting
• Number of participants joining from the cloud
• Topology of the meeting

Scenario Resolution Participant capacity

Meetings with only Webex App participants 720p 100–130*

Meetings and 1-to-1 calls with only Webex App

720p 60–100*
participants

Meetings with only SIP participants 720p 70–80*

Meetings with only SIP participants 1080p 30–40*

Meetings with Webex App and SIP participants 720p 75–110*

* Use these numbers as general guidance.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 12
Capacity – VMNLite version of software
What can impact capacity of the node?

• Types of devices and clients in the meeting

• Video resolution requirements in the meeting
• Number of participants joining from the cloud
• Topology of the meeting

Participant capacity with 3 VMNLite

Scenario Resolution
nodes on a CMS 1K server
Meetings with only Webex App
720p 250–300*
participants
Meetings and 1-to-1 calls with only
720p 175–275*
Webex App participants

* Use these numbers as general guidance.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
Webex Suite
Meetings Platform
Webex Suite Meeting Platform

It is the new name for the next generation of the Webex Meeting Platform!
In order to understand why the new platform, we need to understand the history.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
 Cloud

Webex Suite Meetings

Webex Meetings
Cisco Platform
Platform
Collaboration
Cloud

2024

On-Premises

Webex App
Webex Meetings (Full Featured Meetings)
(Mobile and
Desktop)

Webex Teams
Cisco Spark Webex
App
Webex
App
(Teams)

Cisco Jabber

Hybrid Media Video Mesh Node Video Mesh Node

© 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public
Node
Am I on the Webex Meeting Suite Platform?
• Help.Webex.com – information on how to tell if you are on the
platform.
• “Commercial (Webex Suite)”
• Means you are on the platform
• Visible in the downloads page
• Visible in the meeting info

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 17
Webex Meetings Desktop App to Webex App

UPDATE

Webex Meetings Desktop App

Webex App

• Users were updated to the Webex App

• Program ran throughout 2022

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
Webex Meetings Platform Evolution
MC Meeting Platform Webex Suite Meetings Platform
Update

Collection of services delivering a A modern meetings platform delivering

meetings platform to a range of a consistent experience no matter what
endpoint types device a user joins from

Challenges Benefits
• Multiple apps on desktop, mobile and VDI • Single app on desktop, mobile and VDI
• Admins need to track 2 monthly release • Single update schedule for admins to track
schedules • Video Mesh is supported for all Webex
• Video Mesh not supported Meetings
• No native Linux meetings app • Native meetings app on Linux (Webex App)
• Space Meetings vs Webex Meetings • Consistent meetings experience when
• Ephemeral Meetings Chat scheduled from a space or a PMR
• Chats & recordings available post meeting to
continue collaboration
• Increased Video Mesh Capacity
• Faster join experience
• Join from two devices, appear in the roster once
• AI Ready
• more….

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 19
Webex Suite Meetings Platform – Key Changes
In Meetings Chat

• Rich in-meeting messaging is available for

meetings hosted on a site enabled for Webex
Suite Meetings Platform

• In meeting messaging content will be stored

persistently and will be accessible by users from
within their Webex App meetings tab

• In meeting messaging content will be subject to

the organizations Meeting Retention Policy

• Control Hub admin can control this setting

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 20
 Webex Suite Meetings Platform – Key Changes
Polling and Q&A

• Polling and Q&A are delivered via Slido

for meetings hosted on a Webex Suite
Meetings Platform enabled site

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
Meeting Summaries

Meeting
notes

Edit Action

Action items

Chapter Chapter titles Edit Chapter

Chapters
timestamps

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 22
Revolutionizing video with Super Resolution
• Generative AI video will rebuild packets in poor bandwidth conditions

Low resolution video captured at 270p Super Resolution rescales 270p back into 1080p

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 23
Firewall Considerations
Webex
There are some small network changes to consider
when moving to the Webex Suite Meetings Platform

• Allow outbound traffic based on the Firewall 5 tuple

rule
• Source Address
• Source Port
• Transport Protocol
• Destination Address
• Destination Port

• Action may be required to ensure Webex Suite meeting

bound media traffic is allowed through your firewall

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 24
Meeting Center Meeting Firewall Requirements
Meetings signalling and media traffic is Webex App initiated.
Outbound firewall rules only need be applied (Firewall should allow
Webex return traffic from Webex services)

App Process (Windows) atmgr.exe

Protocol UDP

Source Address Local IP Address

*Source Port Audio 52,000 to 52,049

*Source Port Video 52,100 to 52,199

Destination Address See Network Requirements for Webex Services for

media services IP subnets
Destination Port 9000 (fallback: TLS 443)

Windows *Source ports ranges apply only when dedicated source port settings in place. Otherwise,
source ports will be ephemeral

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 25
Webex Suite meeting platform Firewall
Requirements
Meetings signalling and media traffic is Webex App initiated.
Outbound firewall rules only need be applied (Firewall should allow
Webex return traffic from Webex services)

App Process (Windows) ciscocollabhost.exe

Protocol UDP

Source Address Local IP Address

*Source Port Audio 52,000 to 52,049

*Source Port Video 52,100 to 52,199

Destination Address See Network Requirements for Webex Services for

media services IP subnets
Destination Port 5004 (fallback: UDP 9000, TCP 5004, TCP 443)

Windows *Source ports ranges apply only when dedicated source port settings in place. Otherwise,
source ports will be ephemeral

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 26
Quality of Service Voice Traffic

Network
If a Windows application marks a packet with a DSCP value, Windows will remark the Video Traffic Bandwidth
DSCP value to 0
Content Traffic
A Group Policy is required for Windows applications to mark audio, video and screen
share with appropriate DSCP markings
• Audio DSCP: EF
• Video and Screen Share DSCP: AF41

The Group Policy setting typically is configured to mark any packets with a DSCP
Action
markings based on: Update any Webex
• Application Process Path Group Policy to allow
• Source Port DSCP markings for
Action may be required to reimplement a QoS Group Policy, as the in-meeting CiscoCollabHost.exe
Windows process is now different, and source port may be different

Webex App for Mac and mobile can mark audio, video and screen share packets with
appropriate DSCP markings as default

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 27
VMN – Media cascade destination port range
• https://help.webex.com/en-us/article/ndd6sj9/Video-Mesh-port-updates-for-February-2022
Destination Port

HTTPs 443
Signaling
UDP 5004 Media
UDP 50,000 – 53,000
Video Mesh

• Part of the continuous improvements in the Webex platform.

• Added media cascade using UDP 50,000 – 53,000 destination ports.
• VMN continues to use destination UDP 5004 for media cascades.
• Cascade uses:
• 1:1 meetings will use UDP 5004
• Space and Webex meetings will use UDP 50,000 – 53,000
• VMNs test connectivity to all cloud clusters on specific ports in the range every 4 hours

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 28
VMN – Media cascade destination port range
• Port consolidation targeted for late Q1/early Q2 CY24
(date subject to change)

Destination Port

HTTPs 443
Signaling
UDP 5004 Media
UDP 50,000 – 53,000
Video Mesh

• Eliminating the UDP 50,000 – 53,000 range

• All cascades will use UDP 5004.
• Enablement will be automatically done

*subject to change

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 29
Optimize utilization of your Video Mesh deployment
• Cluster setting allowing specific client or device types to optimize the
Video Mesh resources to priority usage for better quality meetings.
• All non selected clients or devices types will overflow to Webex.
• Private Meetings clusters are unable to overflow to Webex.
• Control Hub Analytics of client types landing on the cluster

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 30
SIP Dial-in Flow to VMN UCM
ucdemolab = Webex sitename

Signaling
With SIP Devices disabled EX90 Media
SIP Route Pattern
ucdemolab.webex.com

Route List

Note: A SIP 488 Route Group

Internet (NOT_ACCEPTABLE_HERE) RG_HQ
response tells Unified CM to go
to the next route group
HQ_VMN SIP Trunk

488 response code

 Meeting request (Device Type = SIP) Signaling Media Signaling Media

Response → 409 response code VMN 1 VMN 2

Core Network Cluster

Exclude SIP Devices

© 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public
Webex Suite Meetings Platform
• We are offering early access to the GA release of the Webex Suite meeting
platform via our beta portal. This will allow you to experience the live
platform to prepare your organization for the rollout.
• This enhanced platform improves and streamlines hybrid work with
common architecture, administration, and integrations while incorporating
AI-based experiences before, during, and after your meetings. It combines
the meeting experience across Webex applications and devices with more
potential for continuous collaboration with rich real-time experiences.

• https://gobeta.webex.com/key/WebexSuite-meetingplatform

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 32
Webex Suite Meetings Platform
Requirements List
• Dev / Test Webex Meetings Site. (Cisco will provision a test site if needed)
• You'll be added to a Webex App space, membership to this space will enable you
for the appropriate beta feature toggles.
• Your organization must be configured to allow external communication, or cisco.com
must be added to your organizations "allowed domain list for external messaging".
• Your organization must not be configured to limit access to only join Group Spaces
owned by your organization.
• We are not able to add free consumer Webex accounts or FedRamp Webex
accounts to this Beta program currently.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 33
Sizing
Software packages

Full version VMNLite

Full support of SIP endpoints, Optimized for Webex App and Webex
Webex App and Webex registered video endpoints
registered video endpoints

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 35
VMNLite
• Most customers are not fully utilizing the transcoding CMS 1K – 72 vCPUs
service.
• Transcoding utilizes more CPUs than switching
• Webex App will use the VMN when on the Webex Suite
Meetings Platform
• Customers can increase scale and minimize overflows
• Investment protection of CMS 1K hardware
• One instance of 70 vCPU VMN can be replaced with three 3 - VMNLites on a single CMS1K
instances of VMNLite on the same hardware. VM1 VM2 VM3
23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB
RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD

x.x.x.1 x.x.x.2 x.x.x.3

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 36
Size the VMN clusters
Cluster • What is your cluster utilization over the last 90
Utilization days?

Overflows • Evaluate any downtime of nodes and make

sure that does not impact your utilization.

Deployment Image • Do you have capacity for more call legs?

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 37
Size the VMN clusters
List Clusters Utilization API
Cluster
Utilization • Returns the utilization details of all Video Mesh clusters in an organization.
• https://developer.webex.com/docs/api/v1/video-mesh/list-clusters-utilization

• Visible in Control Hub analytics also

Overflows

Deployment Image

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 38
Size the VMN clusters
Cluster • How many overflows are happening?
Utilization
• Overflows have reasons associated with them,
Overflows for example “Capacity Exceeded”.

Deployment Image

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 39
Size the VMN clusters
List Overflow to Cloud details API
Cluster
Utilization • Returns details of overflows to the cloud in an organization.
• https://developer.webex.com/docs/api/v1/video-mesh/list-overflow-to-cloud-details

• Visible in Control Hub analytics also

Overflows

Deployment Image

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 40
Size the VMN clusters
Cluster • Which image is installed on each node?
Utilization
• VMNLite or VMN Full(CMS1000)
Overflows
• Increased capacity can be gained by moving
CPU resources to VMNLite for Webex
Deployment Image registered devices and the Webex App

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 41
Size the VMN clusters
List Cluster Details API (deployment type)
Cluster
Utilization • Returns the cluster details of all Video Mesh clusters in an organization.
• https://developer.webex.com/docs/api/v1/video-mesh/get-cluster-details

• Visible in the cluster details within Control Hub.

Overflows

• On the node interface

Deployment Image

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 42
Size the VMN clusters
Cluster • Which types of clients and devices are using
Utilization the Video Mesh nodes?

Overflows • Webex App and Webex registered endpoints

use less media vCPUs for processing.

Deployment Image • SIP devices use more media vCPUs for

processing
Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 43
Size the VMN clusters
Cluster List Cluster Client Type Distribution details API
Utilization
• Returns the client type distribution details for all Video Mesh clusters in an organization.
• https://developer.webex.com/docs/api/v1/video-mesh/list-cluster-client-type-
distribution-details
Overflows
• Visible in Control Hub analytics also

Deployment Image

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 44
Size the VMN clusters
Cluster • How many Meetings clients will be moving to
Utilization the Webex Suite Meetings Platform?

Overflows • The peak number of clients used in MC

meetings will be the number to use for
analysis.
Deployment Image

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 45
Size the VMN clusters
List Meeting Usage Reports (totalParticipants)
Cluster
Utilization • List meeting usage reports of all the users on the specified site by an admin. You can specify a date
range and the maximum number of meeting usage reports to return.
• The list returned is sorted in descending order by the date and time the meetings were started.
• https://developer.webex.com/docs/api/v1/meetings-summary-report/list-meeting-usage-
Overflows reports

Deployment Image

Client types

Meetings clients
per day

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 46
Scenario A
• VMN customer A
• Single cluster with 2 nodes using the VMN Full (CMS1000) image
• Peak utilization average about 50% for the last 90 days
• No redirects
• Client types – 50% cloud registered endpoints, 50% Webex App
• On average the peak meeting participants is 225 per day moving to this
Webex site.

How many Video Mesh nodes are required?

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 47
 Recap
Scenario Resolution Participant capacity VMN Full
Meetings with only Webex App participants 720p 100–130*
(CMS1000)
Meetings and 1-to-1 calls with only Webex App
720p 60–100*
participants Let’s use
Meetings with only SIP participants 720p 70–80*

Meetings with only SIP participants 1080p 30–40*

100
for calculations
Meetings with Webex App and SIP participants 720p 75–110*

3 - VMNLites Scenario Resolution

Participant capacity with 3 VMNLite
nodes on a CMS 1K server
Let’s use Meetings with only Webex App
720p 250–300*
participants
250 Meetings and 1-to-1 calls with only
720p 175–275*
for calculations Webex App participants

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 48
Recommendation
(2 x VMN Full) = 200 concurrent participants

Converted to VMNLite = 250 participants

3 - VMNLites on a single CMS1K
Node1 VM1 VM2 VM3
23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB
RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD

x.x.x.1 x.x.x.2 x.x.x.3

Converted to VMNLite = 250 participants

3 - VMNLites on a single CMS1K
Node2
VM1 VM2 VM3
23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB

300 Participant increase with conversion!

RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD

x.x.x.4 x.x.x.5 x.x.x.6

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 49
Recommendation
Cluster

3 - VMNLites on a single CMS1K 3 - VMNLites on a single CMS1K

VM1 VM2 VM3 VM1 VM2 VM3
23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB
RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD

x.x.x.1 x.x.x.2 x.x.x.3 x.x.x.4 x.x.x.5 x.x.x.6

500 participants capacity Require another 225

participants based on the
(500 – 200) – 225 = 50 available
example requirements.
* Use these numbers as general guidance.
Recommendation
– No need for extra Video Mesh nodes at this time
- Change the existing hardware to VMNLite
- Monitor overflows to see if another node is needed in the cluster.
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 50
Scenario B
• VMN customer B
• Single cluster with 4 nodes using the VMN Full (CMS1000) image
• Peak utilization average about 95% for the last 90 days
• Averaging 300 redirects per day
• Client types – 10% cloud registered endpoints, 40% Webex App, 50%
SIP devices
• On average, there are 1000 peak meeting participants per day who are
joining this Webex site.

How many Video Mesh nodes are required?

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 51
Recommendation

(4 x VMN Full) = 400 concurrent participants

Peak 95% utilization = 380 concurrent participants on average

2 x VMN(CMS1000) =
50% SIP = 190 participants 200 participants

40% Webex App = 152 participants

10% Cloud registered = 38 participants

3 - VMNLites on a single CMS1K
VM1 VM2 VM3
23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB

4th Node available for calls

RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD

x.x.x.1 x.x.x.2 x.x.x.3

1- VMNLite = 250 participants

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 52
 Recommendation
Cluster

3 - VMNLites on a single CMS1K

VM1 VM2 VM3
23 vCPU, 20GB 23 vCPU, 20GB 23 vCPU, 20GB
RAM, 80GB HDD RAM, 80GB HDD RAM, 80GB HDD

x.x.x.1 x.x.x.2 x.x.x.3

✅200 - SIP participants capacity Require another 1000

✅250 – Cloud registered participant capacity participants based on the
👀Single Full node left for capacity or convert to VMNLite? example requirements.

Recommendation * Use these numbers as general guidance.

– Convert the 4th VMN to 3 VMNLites

- Add 3 CMS1000 hardware platforms and 3 VMNLites per CMS1000
- Monitor overflows to see if another node is needed in the cluster.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 53
Scenario C
• Customer has on average 10,000 peak daily participants in
meetings
• Not a Video Mesh customer today

• 10,000/ 250 per VMNLite(3) = 120 Video Mesh Nodes

• 40 - CMS1000 hardware devices needed
OR
• 5 – CMS 2000 hardware devices needed

What should you do?

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 54
Thoughts and options to consider
• What percentage of calls do you want keep on premises?
• 100%, 75%, 50%, or other?
• Only allow endpoints to use Video Mesh nodes?
• Create a phased approach of increasing node scale over time while
accepting overflows?
• Use an Edge Connect link to the Webex backbone?
• Install all the new nodes!

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 55
Connectivity to
Video Mesh
Nodes
 VMN = Webex Video Mesh node
Call Control Connectivity
VCS/Exp - C

Cisco
Webex

VMN

OR
Unified CM

Meeting

• Supported with Unified CM version 11.5(1) or higher. Recommend using the latest
version.
• Supported with VCS or Expressway X8.11.4 or higher. Recommend using the latest
version.
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 57
Reference: Video Mesh SIP-based Signaling/
Media Paths
Unified CM Video Mesh
VMN
Management
TCP/443
TCP/5060-1
Signaling TCP/443

Switching Meetings P2P

UDP/ 50-53k UDP/5004
Transcoding UDP/9000
TCP/5004
TLS/443
UDP/52500-59499
• SIP signaling will determine which Video Mesh cluster is used
TCP/5060-1 UDP/63000-64667
• Media node selection still managed by Webex
• Cascade uses WSS (RFC 6455) for two-way communication
over a single HTTPS connection. SIP
• Server Name Indication (SNI) is leveraged for establishing TLS HTTPS
connection on cascade link (Defined in RFC 6066 TLS
Extensions) Media
• SIP endpoints are handled by the Transcoding microservice.
Cascade
• Allows for all participants to be multi-stream capable.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 58
 SIP Dial-in Flow to VMN ucdemolab = Webex sitename

Signaling

[email protected] Media
UCM

EX90
SIP Route Pattern SIP Route Pattern
ucdemolab.webex.com Non-Video Mesh sites

Route List Route List

Route Group Route Group

(top down)

HQ_VMN SIP Trunk

VCS-C/Exp- C

Signaling Media Signaling Media

VMN 1 VMN 2

HQ Cluster Internet
Meeting request -->
<-- create meeting on VMN 1

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 59
 SIP Dial-in Flow to VMN ucdemolab = Webex sitename

Signaling
Media
Media goes UCM
directly to VMN 1
EX90
SIP Route Pattern SIP Route Pattern
ucdemolab.webex.com Non-Video Mesh sites

Route List Route List

Route Group Route Group

(top down)

HQ_VMN SIP Trunk

VCS-C/Exp- C

Signaling Media Signaling Media

Meeting
VMN 1 VMN 2

HQ Cluster Internet

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 60
 SIP Dial-in Flow to VMN ucdemolab = Webex sitename

Signaling

[email protected] Media
UCM

EX90
SIP Route Pattern
ucdemolab.webex.com

Route List

Route Group
RG_HQ

HQ_VMN SIP Trunk

Full Full
Signaling Media Signaling Media

VMN 1 VMN 2

HQ Cluster Internet
Meeting request -->

<-- Response

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 61
 SIP Dial-in Flow to VMN ucdemolab = Webex sitename

Signaling

[email protected] Media
UCM

EX90
SIP Route Pattern SIP Route Pattern
ucdemolab.webex.com Non-Video Mesh sites

Route List Route List

Note: A SIP 488 Route Group Route Group

(NOT_ACCEPTABLE_HERE) RG_HQ RG_Internet Route Group
response tells Unified CM to go
to the next route group
HQ_VMN SIP Trunk Internet SIP Trunk

488 response code

VCS-C/Exp- C

Full Full
Signaling Media Signaling Media

VMN 1 VMN 2

HQ Cluster Internet
Meeting request -->

<-- Response

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 62
 SIP Dial-in Flow to VMN ucdemolab = Webex sitename

Signaling
Media
Media goes UCM
out the VCS or
EX90 Exp C/E pair to
SIP Route Pattern SIP Route Pattern
the Webex
ucdemolab.webex.com Non-Video Mesh sites
media nodes

Route List Route List

Route Group Route Group

RG_HQ RG_Internet Route Group

HQ_VMN SIP Trunk Internet SIP Trunk

VCS-C/Exp- C

Full Full
Signaling Media Signaling Media

VMN 1 VMN 2

HQ Cluster Internet
Media
Meeting

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 63
 SIP Dial-in Flow to VMN ucdemolab = Webex sitename

Signaling
Media
[email protected]
UCM

EX90
SIP Route Pattern SIP Route Pattern
ucdemolab.webex.com Non-Video Mesh sites

Route List Route List

Note: A 488 Route Group Route Group Route Group

(NOT_ACCEPTABLE_HERE) RG_HQ RG_Internet
Route Group
RG_Backup
response tells Unified CM to go to
the next route group
HQ_VMN SIP Trunk Internet SIP Trunk

488 response code

VCS-C/Exp- C

Full Full
Signaling Media Signaling Media Signaling Media Signaling Media
Meeting
VMN 1 VMN 2 VMN 1 VMN 2
Interne
HQ Cluster Backup Cluster t
Meeting request -->
<-- Response

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 64
Webex App and Cloud Registered Endpoints
Registration

Corporate network- AUS Internet

Cloud1 Cloud2

Sydney1 Sydney2

1. Webex App and Webex device Cluster - Sydney Cluster - Cloud

register to their organization.
Node – Sydney1 Node – Cloud2
2. Webex responds with the clusters
available for the users. Randomly selects a node in each cluster

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 65
 Webex App and Cloud Registered Endpoints
Cluster Reachability Test
Corporate network- AUS Internet

Cloud1 Cloud2

Note: Checks are performed:

a) At the launch of the Webex App
Sydney1 Sydney2 b) Network change event
c) Cache expiration (2 hours)
3. Webex App and Webex devices do reachability tests to the Video Mesh nodes.
4. Webex App and Webex devices send their test results to Webex at call start.
Cluster - Sydney Cluster - Cloud
Randomly selects a
Node – Sydney1 (RTD = 10) Node – Cloud2 (RTD = 220) node in each cluster

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 66
 Webex App and Cloud Registered Endpoints
Registration

Corporate network- AUS Internet

Cloud1 Cloud2

Sydney1 Sydney2

• Webex App and Webex devices connect to a Video mesh node.

• Video Mesh node Sydney1 hosts the meeting.
• If additional participants join later, they follow the same process.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 67
 Webex App and Cloud Registered Endpoints
Meeting with Overflow
Corporate network- AUS Internet

Cloud1 Cloud2
Full Full

Sydney1 Sydney2

• Webex App and Webex devices connect to a Video Mesh node.

• Video Mesh node Sydney1 hosts the meeting.
• If additional participants join later, they follow the same process.
• Sydney 1 and Sydney 2 are full.
• Overflow to the cloud and an automatic cascade is created from Sydney1 to Webex.
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 68
 Video Mesh Webex App-based Signaling/Media Paths
Video Mesh
VMN
Management
Media
UDP/5004 Signaling TCP/443
Fallback UDP/9000, TCP/5004, TLS/443
Switching
Meetings P2P
Transcoding UDP/50-53k UDP/5004
UDP/9000
TCP/5004
TLS/443

1. Request list of media TCP/443

clusters
2. Provide list of TCP/443
available clusters
HTTPS
3. Perform STUN ping UDP/5004*
Triggers: tests Media
1. Start of the Webex app
4. Provide reachability TCP/443 Cascade
2. Network event change data to Webex
3. Cache expiry (2 hours) * STUN ping tests TCP and TLS ports also

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 69
Intracluster Connectivity
• Communication between cluster nodes is required, no Firewalls!
• Specific ranges for signaling and media.
• Source IP – Video Mesh Node’s IP address
HQ cluster
• Signaling – HTTPS 443
• Media: UDP
10,000 –
• Source port range – random 40,000
• Destination port range – UDP 10,000 – 40,000

• Must allow nodes to communicate or calls will fail.

• VMN nodes perform media port connectivity checks every 6 hours.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 70
VMN
Architecture
Centralized and
Distributed
Deployments
Regional offices • 3 internal devices and 1 Webex
App dial into a Webex Meeting
Centralized Video Mesh cluster – Centralized Internet • Signaling goes to Unified CM
and then to Video Mesh
• Video Mesh signaling
communicates with Webex
Internet

WAN WAN

SIP Trunk SIP Trunk

SIP Trunk

Singapore London
Signaling
Media
New York Registration

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 72
 Regional offices • 3 internal devices and 1 Webex
App dial into a Webex Meeting
Centralized Video Mesh cluster – Centralized Internet • Media goes to the Video Mesh
Benefits: New York
• Single exit point for cascades to
Webex Internet
• Eliminates hub and spoke
cascades between clusters
• Media traverses across QoS
enabled corporate network
WAN WAN

Meeting

Singapore London
Signaling
Media
New York Registration

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 73
 • New external participant joins
Regional offices • Media cascade between Video
Mesh and Webex established
Centralized Video Mesh cluster – Centralized Internet
New York

Internet

Cascade

WAN WAN

Meeting

Singapore London
Signaling
Media
Registration
New York
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 74
Regional offices • 3 internal devices and 1 Webex
App dial into a Webex Meeting
Regional Video Mesh clusters – Centralized Internet • Signaling goes to Unified CM
and then to Video Mesh or for
New York the Webex App directly the
cloud
• Video Mesh signaling
Internet
communicates with Webex

Cascade
signaling

WAN WAN

SIP Trunk

SIP Trunk SIP Trunk

London
Signaling
Media
Registration
Singapore New York
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 75
Regional offices • 3 internal devices and 1 Webex
App dial into a Webex Meeting
Regional Video Mesh clusters – Centralized Internet • Media goes to the Video Mesh in
each cluster
New York • Hub and Spoke design with
media cascades to each VMN
cluster
Internet

Cascades

WAN WAN

Meeting Meeting

London
Signaling
Media

Singapore New York Registration

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 76
Regional offices • 3 internal devices and 1 Webex
App dial into a Webex Meeting
Regional Video Mesh clusters – Local Internet • Signaling goes to Unified CM
and then to Video Mesh or for
the Webex App directly the
Singapore cloud
New York
• Video Mesh signaling
Internet Internet
communicates with Webex

WAN WAN

SIP Trunk

SIP Trunk SIP Trunk

London
Signaling
Media
Registration
Singapore New York
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 77
Regional offices • 3 internal devices and 1 Webex
App dial into a Webex Meeting
Regional Video Mesh clusters – Local Internet • Media goes to the Video Mesh in
each cluster
• Hub and Spoke design with
Singapore media cascades to each VMN
New York
cluster
Internet Internet

WAN WAN

Meeting Meeting

London
Signaling
Media
Registration
Singapore New York
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 78
External Meetings • 2 different organizations have a
meeting.
• In Control Hub, the Media 1
Meeting Hosted on an external Webex site Resource Type is set to “Video
1 Mesh” for NYcorp.webex.com
Singapore (This means the site accepts
New York NYcorp.webex.com VMN cascades.)
Internet Internet • Media goes to the Video Mesh in
each cluster
• Hub and Spoke design with
media cascades to each VMN
cluster

WAN
1 NY Corp
Meeting Sing Corp NY Corp
Meeting

Webex site:
London NYcorp.webex.com
Signaling
Media
Webex site: Webex site: Registration
Singapore New York
Singcorp.webex.com NYcorp.webex.com
© 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public
External Meetings • 2 different organizations have a
meeting.
Meeting Hosted on an external Webex site • In Control Hub, the Media
Resource Type is set to “Cloud”
for NYcorp.webex.com (This
NYcorp.webex.com means the site does not accept
Internet Internet VMN cascades.)
• Media from SingCorp and
NYCorp goes to Webex because
of the Media Resource setting.
This is an overflow situation
Singapore New York
because the VMN media
cascade can not be established.

Sing Corp NY Corp • Problem: I want to use my VMNs

for all meetings. Why is my
usage dictated by the meeting
VMN is not VMN is not host site’s setting?
used in this used in this
meeting meeting • Answer: Change the behavior to
allow the admin to chose what
happens in this scenario.
Signaling • The Control Hub VMN
Media cluster setting, “Prefer
Registration
Video Mesh for All
External Webex
Webex site: Webex site:
Singapore New York Meetings”, is used to
NYcorp.webex.com
Singcorp.webex.com manipulate
© 2024 Cisco and/or its affiliates. All rights this behavior.
reserved. Cisco Public
 Prefer Video Mesh for All External Webex
Meetings
➢ Go to the Global Video Mesh Cluster settings
• Enabled - means use my Video Mesh
• Disabled - means by-pass my Video Mesh and use Webex cloud resources (default)

https://help.webex.com/en-us/article/nzvixgk/Keep-your-media-on-Video-Mesh-for-all-external-Webex-meetings

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 81
 Regional Datacenters • Architecture has 2 locations near
each other with a low latency
Low latency connection between the sites connection.
• 2 VMN clusters are defined in
Control Hub.
Device RTT Cluster • Client cluster reachability is
<=25ms difference between the
Internet
Webex App/Endpoint - HQ 22 Primary clusters.
• A meeting starts and the Webex
Webex App/Endpoint - HQ 38 Backup App and video endpoint join.
• Media from the clients can go to
any Video Mesh nodes in either
cluster because the cloud
LAN architecture interprets the
Meeting 2
clusters as a single cluster
Meeting 1
because of the client reachability
Backup DC Primary DC
results of <= 25ms difference
between the clusters.
• Recommendation is to combine
the VMNs into a single cluster at
one location to eliminate
suboptimal routing.
• Cisco does not support
clustering Video Mesh nodes
over the WAN.
Signaling
Media
New York – Remote office New York - HQ Registration
BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 82
Inter-Cluster Cascade Beta
•
Webex meetings follows a hub and spoke cascade
design with Webex cloud as the hub and the on-premises
Video Mesh clusters as the spokes. These cascades would
go over the Internet or the Edge Connect link to Webex.
•
The Inter-Cluster Cascade feature intends to improve call
quality and bandwidth utilization by enabling direct
cascades between Video Mesh clusters of an organization.
•
Customers will be vetted to make sure they meet the
requirements before enablement of this feature.
•
Requirements:
1.
Ensure sufficient WAN bandwidth (20mbs) between
Video Mesh clusters of your organization before enabling
Inter-Cluster Cascades.
2.
All clusters in the organization must have more than one
VMN node.
https://gobeta.webex.com

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 83
Enabled of Inter-cluster cascades
1. Login to Control Hub ->Hybrid -> Edit Settings on the Video Mesh card.
2. Scroll down to Inter-Cluster Cascade. The toggle will be disabled by default. Click
on the toggle to enable it.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 84
Reporting of Inter-cluster Cascades
• Login to Control Hub ->Analytics -> Video Mesh.
• Click on the Bandwidth Usage tab. You will find Inter-Cluster Cascade reports
nested under this tab.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 85
Analytics -> Bandwidth Usage -> Inter-Cluster
Monitoring Inter-Cluster Cascades:
1. Total cascaded data usage by cluster
2. Total cascaded bandwidth usage by
cluster trend
3. Total cascaded data usage by data
transmission
4. Total cascaded bandwidth usage by data
transmission trend
5. Total cascaded data usage by stream
6. Total cascaded bandwidth usage by
stream trend

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 86
Private Meetings
 Typical meeting
Corporate network Internet

Conf_Room1

HQ1_VMN Media
Conf_Room2 Registration

Problem:
• How does executive leadership, research and development, lawyers, etc. securely meet?

Corporate Requirements:
• Needs to keep communications on the corporate network.
• Need to keep communications in a region.
• Don’t trust cloud meetings for these discussions.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 88
 Private meeting
Corporate network Internet

Conf_Room1

HQ1_VMN Media
Conf_Room2 Registration

Solution:
• Remove the media connection to Webex meetings services in the cloud
• Allow only on-premises devices to join the meeting

This is a new feature – Private Meetings

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 89
 Private Meetings
Corporate network Internet

MRA device

Conf_Room1

HQ1_VMN
Conf_Room2

VPN to Corporate

PSTN Signaling
Media
Registration

• Allows for participants media to stay on the corporate network.

• VMN does not cascade media to Webex, but VMN still needs cascade signaling communication.
• Allows only authenticated users and devices to the Webex organization hosting the meeting to join the meeting.
• On-premises apps and devices – allowed • Off-net users/devices – not allowed
• VPN - allowed • PSTN or Edge Audio – not allowed
• MRA – allowed © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public
 Private Meetings
Corporate network Internet

MRA device

Conf_Room1

HQ1_VMN
Conf_Room2

VPN to Corporate

PSTN Signaling
Media
Registration

• Because media is not sent to Webex, this impacts cloud-based services within the Webex meeting.
• The meeting is unable to use or do the following:
• 2-way whiteboarding (1-way whiteboarding by devices is available)
• Webex Meeting recordings (local recording is available)
• Webex Assistant
• Transcription and translation of the meeting
• Webex breakout rooms © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public
 Private Meetings – Intercluster cascade
Corporate network Internet

Conf_Room1

HQ1_VMN_Cluster
Conf_Room2

Intercluster
cascade
Signaling
Media
Remote1_VMN_Cluster Registration

• Participants in the same meeting can be connected to the HQ1 or Remote1 VMN cluster.
• An intercluster cascade is formed in a Private Meeting allowing connections of the HQ1 and Remote1 VMNs.
• Keep in mind geographic and network paths when deploying to avoid latency issues.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 92
Control Hub - Cluster Configuration
• VMN clusters can be designated for Private Meeting
• Allows for dedicated resources for private meetings
• Private Meeting cluster can have VMNLite or any full VMN software
versions with any combination of each in the cluster.
• Failover to non-private cluster happens automatically when the private
cluster is full and needs resources for another participant.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 93
Session Type
• Private Meetings are supported for scheduled meetings only.
• New session type in Webex, “Private Meeting (Video Mesh only)”,
which is used for private meetings.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 94
 Enabling a User to Schedule a Private Meeting

1
2

1. Select the user you want to enable.

2. Click on the “Meetings” tab.
3. Slide the toggle to the right to enable Private Meeting scheduling for that user.
4. Click “Save”

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 95
Scheduling via the browser example

• Private Meeting session type needs to be chosen.

• Information box is displayed indicating this is a private meeting

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 96
Outlook Invite
• Calendar invite to the host
and attendees includes the
normal information on how
to join, Join button, hyperlink
to join via the browser and
SIP dial string.
• Provides helpful information
on how to join the private
meeting at the top of the
invite.
• No option to Join by phone

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 97
Private Meetings – Error messages examples

On screen message

Webex App
message

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 98
What happens at capacity limits of the VMN?
Corporate network Internet

MRA device
FULL

Conf_Room1

Signaling
HQ1_VMN Media
Conf_Room2 Registration

VPN to Corporate

PSTN

• Capacity reached notification on the endpoint

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 99
 Private Meeting Analytics
• Does not appear in Control Hub by default .
• Requires a Private Meeting to finish before the charts will appear in
Control Hub.
Three reports for Private Meetings: Meeting Type = Private or Non-Private
1. Call Legs by Meeting Type
2. On-Premises Meetings by Meeting Type
3. Maximum Call Distribution of Private Meetings by Cluster

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 100
Video Mesh
Monitoring Tool
Video Mesh Monitoring Tool
• Troubleshooting -> Video Mesh

• This tool is a synthetic Webex call simulator natively available on

every Video Mesh node.
• Signaling, media, and cascade failure detection to increase Mean
time to Resolution.
• Can run on one or every VMN node in a cluster. Recommended to
be enabled on at least 1 node per cluster.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 102
Video Mesh Monitoring Tool Schedule
periodic or on
demand tests

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 103
 Video Mesh Monitoring Tool Schedule
periodic or on
demand tests

Cluster

Hover to reveal test

Nodes
details

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 104
Video Mesh Monitoring Tool

Click to reveal test

details

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 105
Video Mesh Monitoring Tool
Timeline
Results

Test
Category
Results

Historical average
success of test
results BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 106
ThousandEyes Within Video Mesh Node Beta
• The Video Mesh platform is now integrated
with the ThousandEyes Enterprise Agent
enabling the admin to perform end-to-end
monitoring across the customer’s hybrid
digital ecosystem.
• This integration equips the admin with a
wide array of network monitoring tests
opening visibility into many areas of the
network path.
• Issues anywhere along a customer's
network infrastructure can be narrowed
down and diagnosed with greater precision,
improving the efficiency of their deployment
• https://gobeta.Webex.com

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 107
Video Mesh APIs
Video Mesh API Framework
1. Metrics and Logs uploaded to Webex
2. Customer uses APIs to get the data
3. Customer created displays or alerts
Webex Video can be made
Mesh Service
Video Mesh APIs
(Webex Developer
Platform)
Integrate with existing Dashboards

2
Metrics/logs

1 Customer’s
API Monitoring 3
Webex Application
App

Alert
Email
Webex Device

Generate Customized alerts and email

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 109
 Sample Client Application
The Video Mesh API Client is an example of a 3rd-party application built using the Webex Video Mesh APIs.

The application is a simple simulation of how the APIs can be used to track organization data and retrieves and
displays data such as Cluster Details, Cluster and Node Availability, Cluster Utilization, Call Redirects and
Overflows, Media Health Monitoring and Reachability Test Results.

Video Mesh API - Sample Client Application

Grafana Visualizations
Webex
Developer Portal
API Request
Video Mesh APIs
API Response Web App
Customized
Alerting
Github Link : https://github.com/CiscoDevNet/video-
mesh-api-client
Timescale DB

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 110
Video Mesh API
• The Video Mesh Developer APIs is a
way to retrieve analytics and
monitoring data from the enterprise
Video Mesh deployment.
• Webex Developer Portal shows the
available APIs and constructs of the
API.
• Developer.webex.com
• Login
• Go to Documentation
• Scroll down to Video Mesh

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 111
Video Mesh API
• Allows API access to the data capture from the Video Mesh Monitor
tool and Connectivity tests shown on the Video Mesh Webpage

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 112
List Reachability Test results (example)

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 113
Video Mesh
Provisioning
Automation
Installation Options
1. Manual provisioning via Control Hub
• Recommended for a small number of nodes being deployed
• Installer must configure all parameters individually on each Video Mesh node

2. Bulk provisioning via APIs

• Used for more than one node installation.
• Saves time for the installer
• All configuration parameters can be configured with the script.

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 115
Video Mesh Nodes Provisioning Automation
• The script automates the deployment of Video Mesh Nodes on VMWare ESXi servers.
• Uses Ovftool API to manage machines on the ESXi
• Configuration files used to deploy the VMN
• https://github.com/CiscoDevNet/webex-video-mesh-node-provisioning

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 116
Video Mesh Nodes Day 2 tasks
• Make network changes to nodes that are already registered to their clusters and
organizations.
• Change these common settings: hostname, domain, DNS servers, NTP servers, DNS
Caching and MTU.
• https://github.com/CiscoDevNet/webex-video-mesh-node-provisioning#network

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 117
Video Mesh Nodes Day 2 tasks
• Make certificate changes to nodes that are already registered to their clusters and
organizations.
• Improves the certificate management process for the customers by reducing the amount of
overall overhead and manual installation.
• Creates multiple CSRs in parallel depending on the input provided by the customers.
• Upload and install the CA signed certificates and the private keys in bulk.
• NOTE: This feature does not support separate certificate management for dual NIC.
• https://github.com/CiscoDevNet/webex-video-mesh-node-
provisioning/blob/main/server_cert_management/README.md

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 118
Video Mesh Reference Links

Deployment Guide http://www.cisco.com/go/video-mesh

https://help.webex.com/en-us/jgobq2/Cisco-Webex-
Release Notes Video-Mesh-Release-Notes

https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA
Preferred Architecture /WbxEdge/PAEdgeVMN.pdf

https://help.webex.com/en-us/n0rlwxe/Analytics-for-Your-Cloud-
Video Mesh Analytics Collaboration-Portfolio#Cisco_Concept.dita_a07f1228-c4a7-
445c-952a-e4d0f97cc23d

https://help.webex.com/en-us/WBX000028782/Network-
Network requirements Requirements-for-Webex-Teams-Services

BRKCOL-2750 © 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public 119
Thank you