Study guide
8.5 Configuring Webex Cloud Messaging
Cisco 350-801 CLCOR CCNP/CCIE Collaboration Core v2.0
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Collaboration Architecture, Deployment Models, Sizing & Upgrades
1.1 Collaboration Architecture & Deployment Models 1.2 Capacity Planning, Sizing & Bandwidth Considerations 1.3 High Availability, Redundancy & Disaster Recovery 1.4 Cisco Unified CM Cluster Upgrade Process
2 Chapter 2: Edge Architecture, Security & Network Services
2.1 Collaboration Edge Architecture: CUBE & Expressway 2.2 Security Protocols & PKI: SSO, OAuth, TLS & SRTP 2.3 Network Infrastructure Services: DNS, NTP, DHCP & LDAP
3 Chapter 3: Protocols, Codecs & Endpoint Provisioning
3.1 SIP Signaling Architecture & Call Flows 3.2 Session Description Protocol (SDP) & Early Offer vs. Delayed Offer 3.3 Audio/Video Codecs & DTMF Relay 3.4 Endpoint Deployment, Onboarding & Troubleshooting
4 Chapter 4: CUCM Dial Plan Fundamentals & Digit Analysis
4.1 Partitions and Calling Search Spaces (CSS) 4.2 Route Patterns, Route Groups & Route Lists 4.3 Translation Patterns, Transformation Patterns & Digit Manipulation 4.4 Globalized Call Routing & Local Route Group (LRG)
5 Chapter 5: Advanced Call Control, Call Routing & User Management
5.1 Call Admission Control (CAC), Locations & AAR 5.2 Toll Fraud Prevention & Call Privileges 5.3 CUCM User Management, LDAP Integration & RBAC 5.4 Administrative XML (AXL) API & Dial-Plan Troubleshooting Tools
6 Chapter 6: Cisco Unity Connection & Voicemail Integration
6.1 Cisco Unity Connection Architecture & SIP Integration 6.2 Mailbox Provisioning, User Templates & Class of Service 6.3 Message Waiting Indication (MWI) & Troubleshooting 6.4 Call Handlers & Directory Handlers
7 Chapter 7: IOS XE Voice Gateways, CUBE & Media Resources
7.1 Cisco IOS XE Voice Gateways & Dial Peers 7.2 Voice Translation Rules and Translation Profiles 7.3 Cisco Unified Border Element (CUBE) Configuration & Redundancy 7.4 IOS XE Media Resources & DSP Management
8 Chapter 8: Webex Architecture, Control Hub, Meetings & Messaging
8.1 Webex Suite Overview & Control Hub Architecture 8.2 Cloud Identity Management, SCIM & Directory Connector 8.3 Webex Developer Platform & APIs 8.4 Configuring Webex Cloud Meetings 8.5 Configuring Webex Cloud Messaging
9 Chapter 9: Webex Calling Routing, Permissions & PSTN Connectivity
9.1 Webex Calling Architecture, Locations & Number Management 9.2 Webex Calling Routing, Trunks & Dial Plans 9.3 Webex Calling Call Routing Process & Translation Patterns 9.4 Webex Calling Toll Fraud Prevention, Call Permissions & Operating Modes 9.5 PSTN Connectivity: Cloud-Connected PSTN (CC-PSTN) & Cisco Calling Plans 9.6 Webex Calling Local Gateway (LGW) Architecture & Configuration
10 Chapter 10: Webex Hybrid Services & Cloud Connected UC
10.1 Cloud-Connected UC (CCUC) Architecture & Telemetry 10.2 Webex Hybrid Calendar & Hybrid Directory Services 10.3 Webex Video Mesh & Hybrid Data Security
11 Chapter 11: Media Quality, QoS Engineering & Troubleshooting
11.1 Real-Time Media Characteristics & Impairments 11.2 QoS Classification, Marking & Trust Boundaries 11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE 11.4 Troubleshooting Media Quality & Call Failures
8.5 Configuring Webex Cloud Messaging
Key Takeaways Explain This Topic AI
Webex messaging takes place in spaces, and the policies of the organization that owns a group space govern the content shared in it.
External Communication settings allow all external messaging (the default), block selected domains, or allow only listed domains, and can stop users from joining externally owned group spaces.
Collaboration Restrictions can block external file sharing and block file preview, download, or upload by client type, file type, or size; these controls require the Pro Pack.
Files can be stored in Webex or in an enterprise content manager such as OneDrive, SharePoint Online, or Box, and retention, legal hold, and eDiscovery apply to messaging data.
Blocking internal communication between groups (ethical walls) requires the Extended Security Pack, and Webex scans shared files with built-in anti-malware protection.
Last updated: October 2026
8.5 Configuring Webex Cloud Messaging
Blueprint objective 5.6 is Configure cloud messaging . Webex messaging takes place in spaces in the Webex App: one-to-one spaces, group spaces, and team spaces. Administrators configure it in Control Hub, mainly through external communication policies, collaboration restrictions, content storage, and compliance settings.
1. How Messaging Policy Works
Space ownership : Every group space is owned by one organization, normally the organization of the person who created it. The owning organization's policies (retention, file-sharing restrictions, and similar settings) govern the content in that space. A user from another company who joins your space follows your space's rules for that content.
Encryption : Messages and files are encrypted with keys from the Webex Key Management Service. Organizations that must hold their own keys deploy Hybrid Data Security (Section 10.3).
Licensing : Several advanced controls, including external communication restrictions and most collaboration restrictions, require the Pro Pack for Control Hub; blocking internal communication between groups requires the Extended Security Pack .
2. External Communication
In Organization Settings > External Communication , choose one of three policies for messaging with people outside the organization:
Policy Effect
Allow all external messaging (default) Users can message any Webex user in any organization (global federation)
Allow all external messaging except blocked domains A block list stops messaging with specific domains
Allow selected domains only Only domains on the allow list are reachable; an empty allow list blocks all external messaging
Related controls:
Group exemptions let selected groups bypass the allow list, for example a partner-management team.
Externally owned group spaces : Administrators can prevent users from joining group spaces owned by other organizations.
Basic Webex calls (calling another Webex App user) follow the same allow and block rules.
Domain status matters: claiming and verifying your domains (Section 8.2) is what lets these policies identify your users reliably.
3. Collaboration Restrictions (File Sharing)
Under Services > Messaging > Collaboration Restrictions :
Restrict external file sharing so users can share files only internally. Turning this on also enables the option that lets users open whiteboards in a browser through whiteboard.webex.com.
Block file preview, download, and upload by client type , for example allowing downloads on managed desktops but blocking them on mobile devices or the web client. These restrictions do not apply in one-to-one spaces with external users.
Restrict file sharing by file type and size (Pro Pack).
Network location : Defining the organization's public IP ranges lets file controls treat users on the corporate network differently from users elsewhere.
Other messaging settings include link previews and animated GIFs, and Control Hub can set which Webex App clients (desktop, mobile, web) may sign in and how long their tokens last (Pro Pack).
4. Content Storage, Retention, and Protection
Enterprise content management : Files can be stored in Webex or in Microsoft OneDrive, SharePoint Online, or Box. Administrators can allow only approved company instances and block personal folders.
Retention, legal hold, and eDiscovery (Section 8.1) apply to messages and files; retention is indefinite by default.
Ethical walls : Blocking internal communication between selected groups (for example, two departments that must not share information) requires the Extended Security Pack and applies to messaging and basic Webex calling.
Anti-malware : Webex scans shared files and attachments with built-in anti-malware protection; organizations can also connect a third-party data loss prevention tool through the Webex APIs.
5. Bots and Integrations
Bots and integrations (Section 8.3) post messages and react to events in spaces. A bot receives all messages in one-to-one spaces but only messages that @mention it in group spaces. Integrations act with the permissions a user grants them. Because these apps can read space content, review which integrations users may authorize as part of messaging governance.
6. Configuration Scenarios
Requirement Configuration
Employees may message only two partner companies External Communication: Allow selected domains only , with the two partner domains in the allow list
Users must not download files on personal phones Collaboration Restrictions: block file download (and preview, if required) for the mobile client type
Files must stay in the company's SharePoint Online Enterprise content management: enable SharePoint Online for the organization and block other storage
Traders and analysts must not message each other Block internal communication between the two groups (Extended Security Pack)
- All chat must be deleted after three years A retention policy for messaging, managed by a Compliance Officer
- 7. Exam Pointers
The default external policy is to allow all external messaging; restricting it is a deliberate choice that needs the Pro Pack.
Policies follow space ownership , so a user can be subject to a partner's restrictions inside the partner's space and to your restrictions inside yours.
File controls can be granular : preview, download, and upload are separate switches, and each can differ by client type (desktop, mobile, web).
Compliance tools (retention, legal hold, eDiscovery) preserve or remove content; collaboration restrictions decide what users may do with it day to day. Expect questions that ask you to pick the right family of control for a stated requirement.