Cisco Meeting Server

2y ago
39 Views
2 Downloads
5.37 MB
167 Pages
Last View : 23d ago
Last Download : 2m ago
Upload by : Camden Erdman
Transcription

Cisco Meeting ServerCisco Meeting Server Release 3.0Single Combined Server Deployment GuideDecember 02, 2020Cisco Systems, Inc.www.cisco.com

ContentsWhat's new81 Introduction91.1 Supported Apps for joining Meeting Server hosted conferences101.2 Using the Cisco Expressway-E as the edge device in Meeting Server deployments 101.3 Using the Cisco Expressway-C with the Meeting Server in the core network111.3.1 Supported deployments121.3.2 Using the Cisco Expressway H.323 gateway component131.4 How to use this guide1.4.1 Commands1.5 Configuring the Meeting Server1416161.5.1 MMP and API Interfaces171.5.2 New tools to ease configuring Meeting Server171.6 Obtaining information on hosted conferences191.6.1 Call Detail Records (CDRs)191.6.2 Events201.7 Cisco licensing201.7.1 Smart Licensing201.7.2 Smart Account and Virtual Account information221.7.3 How Smart licenses work in Meeting Server — overview221.7.4 Expired license feature enforcement actions241.7.5 How to retrieve licensing information (Smart Licensing)251.7.6 Cisco Meeting Server licensing251.7.7 Smart Licensing registration process271.7.8 Obtaining Cisco user licenses using the traditional licensing method281.7.9 Assigning Personal Multiparty licenses to users291.7.10 How Cisco Multiparty licenses are assigned291.7.11 Determining Cisco Multiparty licensing usage291.7.12 Calculating SMP Plus license usage301.7.13 Retrieving license usage snapshots from a Meeting Server311.7.14 License reporting312 General concepts for deployment322.1 Web Admin322.2 Call Bridge332.2.1 Call Bridge licenseCisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments332

2.3 Database332.4 Web Bridge 3332.5 Hosting branding files locally342.6 On screen messaging352.7 TURN server352.8 SIP trunks and routing362.9 Support for Lync and Skype for Business362.9.1 Support for Lync and Skype for Business clients362.9.2 Support for Dual Homed Conferencing372.10 Recording meetings2.10.1 License keys for recording2.11 Streaming meetings3738382.11.1 License keys for streaming382.12 Diagnostics and troubleshooting382.12.1 SIP Tracing392.12.2 Log bundle392.12.3 Ability to generate a keyframe for a specific call leg392.12.4 Reporting registered media modules in syslog403 Prerequisites3.1 Prerequisites41413.1.1 DNS configuration413.1.2 Security certificates413.1.3 Firewall configuration413.1.4 Syslog server413.1.5 Network Time Protocol server423.1.6 Call Detail Record support433.1.7 Host name433.1.8 Other requirements443.1.9 Specific prerequisites for a virtualized deployment444 Configuring the MMP454.1 Creating and managing MMP and Web Admin interface user accounts454.2 Upgrading software454.3 Configuring the Call Bridge464.4 Configuring the Web Admin interface for HTTPS access474.5 Configuring Web Bridge 348Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments3

4.5.1 Useful information to help configure Web Bridge 3484.5.2 Configuring Meeting Server to use Web Bridge 3504.5.3 Configuring Call bridge to use C2W connections524.6 Configuring the TURN server5 LDAP configuration53575.1 Why use LDAP?575.2 Meeting Server settings585.3 Example615.4 Enforcing passcode protection for non-member access to all user spaces626 Dial plan configuration — overview646.1 Introduction646.2 Web Admin Interface configuration pages that handle calls656.2.1 Outbound calls page656.2.2 Incoming call page: call matching666.2.3 Call forwarding676.3 Dial Transforms7 Dial plan configuration — SIP endpoints68707.1 Introduction707.2 SIP video endpoints dialing a meeting hosted on the Meeting Server707.2.1 SIP call control configuration707.2.2 Meeting Server configuration717.3 Media encryption for SIP calls737.4 Enabling TIP support737.5 IVR configuration747.6 Next steps748 Dial plan configuration — integrating Lync/Skype for Business758.1 Lync clients dialing into a call on the Meeting Server758.1.1 Lync Front End (FE) server configuration768.1.2 Adding a dial plan rule on the Meeting Server778.2 Integrating SIP endpoints and Lync clients788.3 Adding calls between Lync clients and SIP video endpoints798.3.1 Lync Front End server configuration798.3.2 VCS configuration808.3.3 Meeting Server configuration80Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments4

8.4 Integrating web app with SIP and Lync clients828.5 Integrating Lync using Lync Edge service838.5.1 Lync Edge call flow838.5.2 Configuration on Meeting Server to use Lync Edge848.6 Direct Lync federation868.7 Calling into scheduled Lync meetings directly and via IVR878.8 Choosing Call Bridge mode to connect participants to Lync conferences899 Office 365 Dual Homed Experience with OBTP Scheduling909.1 Overview909.2 Configuration909.3 In-conference experience9111 Web Admin interface settings for the TURN server9311.1 TURN server connections9311.2 TURN server settings9612 Settings for Web Bridge 39712.1 Web Bridge 3 connections12.1.1 Web Bridge 3 call flow12.2 Web Bridge 3 settings12.2.1 How to create and apply a web bridge profile example13 Recording and Streaming meetings13.1 Feature benefits of the new internal SIP recorder and streamer97989910010210213.2 Points to note when implementing the new internal SIP recorder and streamer: 10213.3 Recording overview10313.3.1 Third-party external SIP recorder support10413.3.2 Meeting Server internal SIP recorder component support10413.4 Example of deploying the new internal SIP recorder component on a VM server 10613.5 Configuring an external third-party SIP recorder10913.6 Finding out recording status11013.7 Recording indicator for dual homed conferences11013.8 Recording with Vbrick11113.8.1 Prerequisites for the Meeting Server11113.8.2 Configuring the Meeting Server to work with Vbrick11213.9 Streaming meetings11413.10 Deploying the new SIP streamer component on a VM server115Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments5

13.10.1 Known Limitations14 Support for ActiveControl11811914.1 ActiveControl on the Meeting Server11914.2 Limitations11914.3 Overview on ActiveControl and the iX protocol11914.4 Disabling UDT within SIP calls12014.5 Enabling iX support in Cisco Unified Communications Manager12014.6 Filtering iX in Cisco VCS12114.7 iX troubleshooting12215 Additional security considerations & QoS12315.1 Common Access Card (CAC) integration12315.2 Online Certificate Status Protocol (OCSP)12315.3 FIPS12315.4 TLS certificate verification12415.5 User controls12415.6 Firewall rules12415.7 DSCP12516 Diagnostic tools to help Cisco Support troubleshoot issues12616.1 Log bundle12616.2 Ability to generate a keyframe for a specific call leg12616.3 Reporting registered media modules in syslog127Appendix A DNS records needed for the deployment128Appendix B Ports required for the deployment130B.1 Configuring the Meeting Server130B.2 Connecting services131B.3 Using Meeting Server components131B.4 Ports open on loopback134Appendix C Call capacities by Cisco Meeting Server platformC.1 Cisco Meeting Server web app call capacitiesC.1.1 Cisco Meeting Server web app call capacities — external calling135137137C.1.2 Cisco Meeting Server web app capacities — mixed (internal external) calling137Appendix D Activation key for unencrypted SIP mediaCisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments1396

D.1 Unencrypted SIP media mode139D.2 Determining the Call Bridge media mode140Appendix E Dual Homed Conferencing141E.1 Overview141E.2 Consistent meeting experience in dual homed conferences141E.2.1 Summary of user experiences142E.3 Mute/unmute meeting controls in dual homed conferences143E.4 Configuring the Dual Homed Lync functionality144E.4.1 Troubleshooting144Appendix F More information on LDAP field mappings146Appendix G Using TURN servers behind NAT148G.1 Identifying candidates148G.1.1 Host candidate148G.1.2 Server Reflexive candidate148G.1.3 Relay candidate149G.2 Checking connectivity151G.3 NAT in front of the TURN server152G.4 TURN server, NAT and the web app154Appendix H Using a standby Meeting Server158H.1 Backing up the currently used configuration158H.2 Transferring a backup to the standby server158Appendix I Web Admin Interface — Configuration menu options161I.1 General161I.2 Active Directory161I.3 Call settings162I.4 Outbound calls and Incoming calls163I.5 CDR settings163I.6 Spaces164I.7 API164Cisco Legal Information166Cisco Trademark167Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments7

What's newWhat's newVersionChangeDecember 02,2020Minor correction.October 07,2020Minor correction.September 02,2020Minor edit to clarify VM minimum requirement to 4 vCPU cores for Recorder/Streamer.August 17,2020New version for 3.0.Removed deprecated components listed in 3.0 Release Notes.Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments8

1 Introduction1 IntroductionThe Cisco Meeting Server software can be hosted on specific servers based on Cisco UnifiedComputing Server (UCS) technology or on a specification-based VM server. Cisco MeetingServer is referred to as the Meeting Server throughout this document.Note: Cisco Meeting Server software version 3.0 onwards does not support X-Series servers.This guide covers the Meeting Server deployed as a combined server deployment, thedeployment has no scalability or resilience. The server comprises a number of components, seeFigure 1.Note: All of the Meeting Servers in the deployment must run the same version of software.Note: Meeting Server 3.0 introduces a mandatory requirement to have Cisco MeetingManagement 3.0 (or later). Meeting Management handles the product registration andinteraction with your Smart Account (if set up) for Smart Licensing support. For more details onSmart Licensing, see Section 1.7.Figure 1 shows the components available in a combined server deployment. Note that theRecorder, Uploader and Streamer components should be enabled on a separate server to thathosting the meetings. The Cisco Meeting Server 2000 schematic assumes that CiscoExpressway provides the TURN services.Figure 1: Combined server deploymentNot all of these components need to be configured, you only need to configure the componentsthat are appropriate to your deployment. This is discussed in Chapter 2.Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments9

1 Introduction1.1 Supported Apps for joining Meeting Server hosted conferencesThe Cisco Meeting Server web app and Cisco Jabber are the supported apps to join MeetingServer hosted conferences. This is in addition to SIP endpoints, and Lync/Skype for Businessclients in dual homed conferences.1.2 Using the Cisco Expressway-E as the edge device in Meeting ServerdeploymentsCisco Expressway software's edge features have been developed to enable the CiscoExpressway-E to be used as the edge device in Meeting Server deployments. Use the TURNserver capabilities in Cisco Expressway-E to enable:nparticipants using the browser based Meeting Server web app to join conferences hosted onthe Meeting Server,nremote Lync and Skype for Business clients to join conferences hosted on the MeetingServer.In addition, the Cisco Expressway-E can be used as a SIP Registrar to register SIP endpoints orto proxy registrations to the internal call control platform (Cisco Unified CommunicationsManager or Cisco Expressway-C).CAUTION: Important notes for Expressway usersIf you are deploying Web Bridge 3 and web app you must use Expressway version X12.6 orlater, earlier Expressway versions are not supported by Web Bridge 3.Table 1 below indicates the configuration documentation that covers setting up CiscoExpressway-E to perform these functions. Table 2 below shows the introduction of the featuresby release.Note: Cisco Expressway-E can not be used between on premises Microsoft infrastructure andthe Meeting Server. In deployments with on-premises Microsoft infrastructure and the MeetingServer, the Meeting Server must use the Microsoft Edge server to traverse Microsoft calls intoand out of the organization.Note: If you are configuring dual homed conferencing between on-premises Meeting Serverand on-premises Microsoft Skype for Business infrastructure, then the Meeting Serverautomatically uses the TURN services of the Skype for Business Edge.Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments10

1 IntroductionTable 1: Documentation covering Cisco Expressway as the edge device for the Meeting ServerEdge featureConfiguration covered in this guideConnect remote browser based Meeting Server webappsCisco Expressway Web Proxy for Cisco Meeting ServerDeployment GuideConnect remote Lync and Skype for Business clientsCisco Meeting Server with Cisco Expressway Deployment GuideSIP Registrar or to proxy registrations to the internalcall control platformCisco Expressway-E and Expressway-C Basic Configuration (X12.6)Table 2: Expressway edge support for the Meeting ServerCiscoExpresswayE versionEdge featureMeetingServerversionX12.6Supports Cisco Meeting Server web app. See Cisco Expressway Web Proxy for CiscoMeeting Server (X12.6)2.9 andlaterX8.11Supported:- load balancing of clustered Meeting Servers,- Microsoft clients on Lync or Skype for Business infrastructure in otherorganizations, or Skype for Business clients on Office 365 (not "consumer" versionsof Skype).- interoperability between on-premise Microsoft infrastructure and on-premiseMeeting Server, where no Microsoft calls traverse into or out of the organization.- standards based SIP endpoints.- standards based H.323 endpoints.- Cisco Meeting App thin client (Web RTC app) using TCP port 443.2.4 to2.8Not supported:- off premise Cisco Meeting App thick clients (Windows/Mac desktop or iOS).- interoperability between on-premise Microsoft infrastructure and on-premiseMeeting Server where Microsoft calls traverse into or out of the organization, in thisscenario, the Meeting Server must use the Microsoft Edge server to traverseMicrosoft calls into and out of the organization.See Cisco Meeting Server with Cisco Expressway Deployment Guide (2.4/X8.11.4).1.3 Using the Cisco Expressway-C with the Meeting Server in the corenetworkIn addition to deploying Cisco Expressway-E at the edge of the network, Cisco Expressway-Ccan be deployed in the core network with the Meeting Server. If deployed between the MeetingServer and an on-premises Microsoft Skype for Business infrastructure, the Cisco ExpresswayC can provide IM&P and video integration. In addition the Cisco Expressway-C can provide thefollowing functionality:Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments11

1 Introductionna SIP Registrar,nan H.323 Gatekeeper,ncall control in Meeting Server deployments with Call Bridge groups configured to loadbalance conferences across Meeting Server nodes.Table 3:Additional documentation covering Cisco Expressway-C and the Meeting ServerFeatureConfiguration covered in this guideCall control device to load balance clusteredMeeting ServersCisco Meeting Server 2.9, Load Balancing Calls Across CiscoMeeting ServersSIP RegistrarCisco Expressway-E and Expressway-C Basic Configuration(X12.6)H.323 GatekeeperCisco Expressway-E and Expressway-C Basic Configuration(X12.6)1.3.1 Supported deploymentsFigure 2 and Figure 3 illustrate recommended Meeting Server deployments.Both deployments show an Expressway pair (Expressway-C and Expressway-E) being used asthe edge device for the Meeting Server. The Expressway-E is located in the DMZ, while theExpressway-C is located in the internal network between the Meeting Server and Cisco UnifiedCommunications Manager.The Cisco Meeting Server web app connects via the TURN server on the Expressway-E.Figure 3 illustrates Microsoft infrastructure added to the deployment to support dual homedconferencing.Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments12

1 IntroductionFigure 2: Cisco Unified Communications Manager-centric deployment exampleFigure 3: Cisco and Microsoft Infrastructure on-premises deployment example1.3.2 Using the Cisco Expressway H.323 gateway componentIn line with Cisco’s goal of a single Edge solution across the Cisco Meeting Server and CiscoExpressway, Cisco has removed the H.323 Gateway component from version 3.0 of theCisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments13

1 IntroductionMeeting Server software. Customers are encouraged to migrate to the more mature H.323Gateway component in the Cisco Expressway.Any H.323 endpoints registered to Expressway-E or Expressway-C will not consume RichMedia Session (RMS) licenses when calling into the Cisco Meeting Server from Expresswayversion X8.10 onwards.1.4 How to use this guideThis deployment guide follows on from the appropriate Installation Guide for your server, andassumes that you have completed the installation instructions already. This guide should be readand used in conjunction with the appropriate Certificate Guidelines.In addition to this deployment guide and the Certificate Guidelines, the reference materialshown in the figure below can be found on the Cisco Meeting Server documentation page.Note: Throughout this guide, the term coSpace has been renamed space.Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments14

1 IntroductionFigure 4: Overview of guides covering the Meeting ServerCisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments15

1 IntroductionNote: The address ranges we use in Cisco user documentation are those defined in RFC 5737which are explicitly reserved for documentation purposes. IP addresses in Meeting Server userdocumentation should be replaced with correct IP addresses routable in your network, unlessotherwise stated.1.4.1 CommandsIn this document, commands are shown in black and must be entered as given—replacing anyparameters in brackets with your appropriate values. Examples are shown in blue and mustbe adapted to your deployment.1.5 Configuring the Meeting ServerThere are two layers to the Cisco Meeting Server software: a Platform and an Application.nThe Platform is configured through the Mainboard Management Processor (MMP). The MMPis used for low level bootstrapping, and configuration via its command line interface. Forexample, the MMP is used to enable the Web Bridge, Database clustering and various othercomponents.nThe Application runs on the MMP platform. Administration of the application level (call andmedia management) can be done via the Call Bridge's Web Admin interface or through theApplication Programming Interface (API) if you prefer. The API uses HTTPS as a transportmechanism and is designed to be scalable in order to manage the potentially very largenumbers of active calls and spaces available in a deployment.From version 2.9, the application level administration can all be done via the Call Bridge’sWeb Admin Interface both for single and clustered Meeting Servers.Note: Prior to version 2.9 software you need to configure multiple Call Bridges using the APIand third party API tools, such as POSTMAN; only use the Web Admin interface forconfiguring a single Call Bridge.Cisco Meeting Server Release 3.0 : Single Combined Meeting Server Deployments16

1 Introduction1.5.1 MMP and API InterfacesTable 4: Network interfaces configured for the MMP and API on the different Meeting Server platformsPlatformAccess to MMPAccess to Web Admin interface and APICisco MeetingServer 2000Serial over LAN (SoL)connection on blade 1.Interface A created during the configuration of MMP. It is avirtual connection that is connected to the externalnetwork through uplinks configured on Port 1 of the FabricInterconnect modules.Note: Before accessing theMMP you need to configure thenetwork settings for the FabricInterconnect modulesCisco MeetingServer 1000 andother virtualizeddeploymentsVirtual interface ANote: Cisco Meeting Server 2000 platform does notsupport more tha

13.2 Points to note when implementing the new internal SIP recorder and streamer: 102 13.3 Recording overview 103 13.3.1 Third-party external SIP recorder support 104 13.3.2 Meeting Server internal SIP recorder component support 104 13.4 Example of deploying the new internal SIP recorder component on a VM server106

Related Documents:

Cisco ASA 5505 Cisco ASA 5505SP Cisco ASA 5510 Cisco ASA 5510SP Cisco ASA 5520 Cisco ASA 5520 VPN Cisco ASA 5540 Cisco ASA 5540 VPN Premium Cisco ASA 5540 VPN Cisco ASA 5550 Cisco ASA 5580-20 Cisco ASA 5580-40 Cisco ASA 5585-X Cisco ASA w/ AIP-SSM Cisco ASA w/ CSC-SSM Cisco C7600 Ser

Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unified Computing System (Cisco UCS), Cisco UCS B-Series Blade Servers, Cisco UCS C-Series Rack Servers, Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS

Cisco Webex Meeting Server (CWMS) 0. 9. Cisco Webex Meeting Server (CWMS) CWMS IRP On-Premises. Remote Cisco Meeting Server (CMS) / Meeting Management (CMM) On-Premises. Expressway MRA. 1. Cisco Meeting Server (CMS) 1. 1 . Expressway MRA is an optional feature.

Supported Devices - Cisco SiSi NetFlow supported Cisco devices Cisco Catalyst 3560 Cisco 800 Cisco 7200 Cisco Catalyst 3750 Cisco 1800 Cisco 7600 Cisco Catalyst 4500 Cisco 1900 Cisco 12000 Cisco Catalyst 6500 Cisco 2800 Cisco ASR se

Cisco Nexus 1000V Cisco Nexus 1010 Cisco Nexus 4000 Cisco MDS 9100 Series Cisco Nexus 5000 Cisco Nexus 2000 Cisco Nexus 6000 Cisco MDS 9250i Multiservice Switch Cisco MDS 9700 Series Cisco Nexus 7000/7700 Cisco Nexus 3500 and 3000 CISCO NX-OS: From Hypervisor to Core CISCO DCNM: Single

Cisco Nexus 7706 Cisco ASR1001 . Cisco ISR 4431 Cisco Firepower 1010 Cisco Firepower 1140 Cisco Firepower 2110 Cisco Firepower 2130 Cisco FMC 1600 Cisco MDS 91485 Cisco Catalyst 3750X Cisco Catalyst 3850 Cisco Catalyst 4507 Cisco 5500 Wireless Controllers Cisco Aironet Access Points .

Sep 11, 2017 · Note: Refer to the Getting Started with Cisco Commerce User Guide for detailed information on how to use common utilities for a record in Cisco Commerce. See Cisco Commerce Estimates and Configurations User Guide for more information.File Size: 664KBPage Count: 5Explore furtherSolved: Cisco Serial Number Lookups - Cisco Communitycommunity.cisco.comHow to view and/or update your CCO profilewww.cisco.comSolved: How do I associate a contract to my Cisco.com .community.cisco.comHow do I find my Cisco Contract Number? - Ciscowww.cisco.comPower calculator tool - Cisco Communitycommunity.cisco.comRecommended to you b

Apr 05, 2017 · Cisco 4G LTE and Cisco 4G LTE-Advanced Network Interface Module Installation Guide Table 1 Cisco 4G LTE NIM and Cisco 4G LTE-Advanced NIM SKUs Cisco 4G LTE NIM and Cisco 4G LTE-Advanced NIM SKUs Description Mode Operating Region Band NIM-4G-LTE-LA Cisco 4G LTE NIM module (LTE 2.5) for LATAM/APAC carriers. This SKU is File Size: 2MBPage Count: 18Explore furtherCisco 4G LTE Software Configuration Guide - GfK Etilizecontent.etilize.comSolved: 4G LTE Configuration - Cisco Communitycommunity.cisco.comCisco 4G LTE Software Configuration Guide - Ciscowww.cisco.comCisco 4G LTE-Advanced Configurationwww.cisco.com4G LTE Configuration - Cisco Communitycommunity.cisco.comRecommended to you b