Cisco Lab Cms

CCIE Collaboration v2 WISP Lab 2:
Cisco Meeting Server (CMS)

Ad-hoc and Rendezvous
Conference Configuration
Ben Ng, L@C, Cisco CX
Ishan Sambhi, CSE, Cisco CX
Agenda
• Overview of Cisco Meeting Server
• CUCM Rendezvous Conferences Using CMS
• CUCM Adhoc Conferences using CMS
Cisco Meeting Server – Overview
Cisco Meeting server (CMS) Overview
• Cisco Meeting Server brings video, audio, and web communication together to meet the
collaboration needs of the modern workplace. It allows anyone to create and join meetings
easily, from a room or desktop video system, mobile client, or browser.
• Everyone gets a consistent, familiar meeting experience, whether they’re joining a meeting
using a Cisco or third-party video endpoint, a Cisco Jabber® client, Cisco Meeting App, a
WebRTC compatible browser, or Skype for Business.
• Meetings can scale easily, allowing any number of people to join, and bandwidth usage is
optimized in order to reduce cost. Cisco Meeting Server provides a user experience that is
simple and intuitive.
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
4
Cisco Meeting Server Architecture
External
Cisco Meeting App Lync/S4B Direct Cisco Meeting App
Federation WebRTC
Load Balancer TURN Server Web Bridge

Edge Software
XMPP Recording / Core Software
Call Bridge Database
Server Streaming
Internal
Lync FE Cisco Meeting App

Call Control Active Directory
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Confidential SIP / H.323
CMS Basic Components
• Call Bridge (MCU)
• Web Bridge (Jabber Guest)
• Web Admin
• XMPP
• TURN Server
• H.323 Gateway
• Database
• Recording / Streaming Server
6
Callbridge Overview
• Call Bridge service on the Meeting Server is to bridge the conference
connections, enabling multiple participants to join meetings hosted on the
Meeting Server
• Primary component of the solution
• Must exist somewhere in all deployments
• Media processing engine
• API integration point
• Call processing and routing component
• Fully brand-able audio and video prompts
• Supports clustering for distributed calls
7
Webadmin Overview
• Webadmin is the Service to enable Web GUI for Meeting server
• Webadmin is specifically to configure how the Call Bridge talks to other
components
• Required for Call routing configuration
• Required for Clustering configuration
• Required for viewing logs via web and increasing log levels
8
XMPP Overview
• XMPP service to enable the Cisco Meeting Apps such as PC clients and iOS
(iPhone and iPad) device to connect the Meeting Server. The XMPP service
handles signaling to and from Cisco Meeting Apps
• Registration point for Desktop and Mobile clients as well as Web Bridge
• Allows for calls, IM, and presence
• Traversal capable
• Can balance between multiple servers in large deployment
• Requires LDAP source to be configured on Call Bridge with users imported
9
Webbridge Overview
• Webbridge service to enable WebRTC app. The WebRTC app works on
HTMP5-compliance browsers and uses the WebRTC standard for video and
audio
• It equivalent of VCS Jabber Guest solution
• Allows for a guest to join via special link or full access to “web” version of
desktop client
• Based around Web sockets and WebRTC
• Utilizes XMPP signaling (acts similar to desktop client between itself and Call
Bridge)
• Chrome, Firefox, and Opera supported, Chrome is preferred
• Must use different port or IP from Web Admin if on the same server
10
H.323 Gateway
• Allows for external (b2b) calls via H.323 into the solution
• A requirement to provide h.323 support as the Call Bridge only operates in
SIP
• Gateway will convert all inbound H.323 traffic to SIP for internal
communication
• Generally positioned on the Edge server in multi-deployment
• Recommended to use Expressway as H323 gateway as this will be removed
in future release
Database
• Automatically created when a Call Bridge is created
• Stores information regarding spaces and their content
• Supports clustering if desired for redundancy
• When clustered, automatically elects a master which all Call Bridge servers
will talk to
• If 5 consecutive keepalives fail, new master is elected
• A Call Bridge cluster requires a Database cluster
• Database failover can take approx. 1 minute to become operational
• Inter-database communication handled via SSL
Load-balancers and Trunks
• In a split deployment, the XMPP server is located on the core and the “loadbalancer” is located on the edge.
• The trunk provides the connection to the load balancer on the core side to funnel traffic internally to the xmpp
server.
• The loadbalancer does not really distribute load, but rather provides one of potentially multiple points for traffic
to be passed to the XMPP server. In Cisco terms, think of the loadbalancer (on the edge) as the traversal
server, and the trunk (on the core) as the traversal client building a tunnel between the two.
• Multiple trunks and load balancers can be configured on a server via the MMP each with its own certs and
trust bundle.
• Similar to the traversal server and client model, the load balancer never initiates connections, but listens both
internally and externally. The associated ports and interfaces are customizable, but by default internal
communication from the trunk is on port 4999 while external commination from clients is on 5222.
• The external side should also listen on the loopback interface if a Webbridge is on the same server as the
loadbalancer.
Load-balancers and Trunks (Cont’d)
lo:5222
Trunk
CMS Single Combined Deployment
• All components are

enabled & configured
on Same server
• No scalability or
resiliency
• Only configure the
components that are
appropriate to your
deployment
CMS Single Split Deployment
• Core and Edge components
are separated
• Edge Server is placed in DMZ
for devices from internet to
use meeting server features
• No scalability or resiliency
• Only configure the
components that are
appropriate to your
deployment
CMS Scalability & Resilience Deployment
• Several components of the
same type to work as one
resilient “unit” and increase
capacity
• Database Cluster
• Spaces, Users, Dial Plan, Cluster-
wide configuration
• Provides Resiliency
• Call Bridge Cluster

• Distributed calls for capacity &
resiliency
• XMPP Cluster
• Provides Resiliency
CMS – Expressway Deployment
• Supported with Expressway X
8.9.2 / CMS 2.1.4
• Only WebRTC Clients can be
used with Expressway
• CMA Support to be included
in future Expressway software
CMS Management and Administration Tools
CLI / MMP WebAdmin API SFTP

ssh, (Web GUI)
console, Most for licenses,
VM console Dial Plan and configuration certificates,
Call Bridge that’s not in logs, backups
admin MMP upgrades
CMS Certificate Requirements
• WebAdmin
• XMPP
• WebBridge
Certificate types:
Components • Callbridge
that need a • Loadbalancer • Self-signed by CMS
certificate: • Trunk • Private CA Signed
• Database Cluster • Public CA Signed
• Recording server
• Streaming server
Plan certificates in advance and combine where possible!
Cisco Meeting Server Spaces
Ad hoc conference with UCM
• Escalate 1:1 calls to add participants
Personal meetings
• Invite others to your personal meeting using your own join details
Scheduled meetings
• Cisco TelePresence Management Suite (including Microsoft Outlook integration)
• One-Button-to-Push support
CMS
SIP Endpoints Dial: WebRTC: https://join.domain.com

conference@domain.com
CMA: Your Personal Space
Spaces
Phone Dial: Skype for Business
+1(408) 555-5555 Click:
LDAP Integration
• No local users (except for admin and api access)
• LDAP Mapping can create personal Spaces with a primary and
secondary Space and user URI
 Should not overlap with other URIs in the network
 Multiple LDAP sources can be configured using API
Active CallBridge
Directory Database
AD
+ Space
Key parameters for mapping

User (XMPPID & URI) jim@conf.cms.com
Username: $sAMAccountName$@conf.cms.com
Space URI jim.space@conf.cms.com 2nd
Space URI user part: $sAMAccountName$.space
Space URI 75267755@conf.cms.com
Space secondary URI user part: 7$telephoneNumber$
CMS Call Processing
• CMS only looks at the domain in the SIP Request-URI field
• If the SIP INVITE is destined to sip:user@domain.com, CMS only cares
about the domain.com
Incoming Call Rules Forwarding Rules Outgoing Call Rules
• Is the call for this CMS ? • Should the call be • Destination?

• For spaces, users, IVR ? forwarded? • Standards-based or
• Is the call for Lync ? • If domain not matched, Lync
by default reject the trunk type
• If no match for domain, call
check Forwarding rules • Any transformation?
Cisco Meeting Server – Accessing
the Lab
Accessing the Lab: VPN Details
• Open Cisco Any Connect VPN client
• Connect to server: cll-live.cisco.com
• Username: collab#, where # is your pod number**
• Password: Ci$co123
**You should have received your pod number from

your WISP proctor.
25
Accessing the Lab
• Go to Settings ; Uncheck the “Block Connections to untrusted servers”
• Check the “Allow local (LAN) access when using VPN (if configured)”
26
Accessing the Lab PCs
• Once connected Lab network through VPN, you can access PCs below
 Windows PC 1 RDP: 172.16.50.15x:3319, where x is your pod number
e.g. To access pod1’s PC1, RDP to 172.16.50.151:3319
To access pod2’s PC1, RDP to 172.16.50.152:3319
• Windows PC Username / password : admin / cisco
27
Accessing the Lab
• Once are connected to the PCs using RDP, you can access the CMS and
CUCM server using the following IP addresses:
 CMS : 10.10.10.17 Username / password: admin / cisco
 CUCM: 10.10.10.11 Username / password: administrator / cisco
• The PCs has the following internal IP addresses:
 Windows PC 1: 10.10.12.19
 Windows PC 2: 10.10.12.20
 Windows PC 3: 10.10.12.21
• All PC Username / password : admin / cisco
28
Rendezvous Conference from
CUCM to CMS
Rendezvous Conference
• CUCM registered endpoints directly dial into CMS Space by number / URI
• CUCM Configuration
• Create a SIP trunk to CMS Callbridge (secure or non-secure)
• Create a Route pattern or SIP route pattern
• Upload the callbridge CA certificate as CUCM-trust
• Create a Secure SIP profile with X.509 as callbridge FQDN
• CMS Configuration
• Create a Incoming Rule to match CMS IP / domain
• Same Configuration can be used for TMS Scheduled calls (OBTP)
30
Rendezvous Conference - CUCM Configuration
• Open a Web Browser and access to CUCM 10.10.10.11
• Login to CUCM Web Interface
• Create a SIP trunk Security Profile in CUCM
• System  Security  SIP trunk security Profile
LABCOL-1008 31
• Click Add New
• Enter Name: Secure SIP Trunk Profile CMS
• Device security Mode : Encrypted
• X.509 Subject Name : callbridge.cmslab.com,
webadmin.cmslab.com
• Click Save
32
Rendezvous Conferences - CUCM Configuration
• Create a SIP trunk from CUCM to CMS server
• Click on Device  Trunk
• Click Add New
• Select Trunk Type: SIP Trunk
• Click Next
• Enter Name: CMS-Trunk
• Select Device Pool: Default
• Scroll Down to SIP Information
33
• Under SIP Information provide following:
• Enter 10.10.10.17
• Destination Port: 5061
• Select SIP Trunk Security Profile Secure SIP

Trunk Profile CMS
• Select SIP Profile Standard SIP Profile for
TelePresence Conferencing
• Click Save and Reset
34
• Check SIP trunk Status
• It should be Full Service
35
• Create a Route pattern 900X in CUCM to dial CMS Meeting
• Click on Call Routing  Route/Hunt  Route Pattern
• Click on Add new
• Enter Route Pattern: 900X
• Choose Gateway/Route List : CMS-Trunk
• Save
36
Creating a New Meeting Room (CoSpace)
• Create a New Cospace (meeting Room)
• Go to Configuration  spaces
• Add Name: CoSpaceTest , URI user Part: 9001 , Call ID: 9001
• Click Add New
• New meeting room “CoSpaceTest” has been created
37
Rendezvous Conference - CMS Configuration
• Create an Inbound rule in CMS to receive calls from CUCM
• Click on Configuration  Incoming calls
• Keep domain name : 10.10.10.17, Priority : 10 and click Add new
38
Rendezvous Conference – Test & Verify
• Login in to Window PC 3 (RDP to 172.16.50.15x:3321)
• Click on Cisco Jabber , login with user : cucmuser1@cmslab.com, Pwd:12345
• Once login, Dial 9001
• It connects to CMS Meeting
39
• Login to Window PC1 (172.16.50.15x:3319)
• Open a Chrome browser and type
https://join.cmslab.com
• Click on Sign in
40
• Sign in with user credentials
• User name: cmsuser1@cmslab.com Password: Cisco123
41
• Click on NEW to add NEW call
42
• Click on call
• Dial 9001@10.10.10.17 and Press Enter, Select Video option to connect “CoSpaceTest”
Meeting room
• It will be connected CoSpaceTest Meeting room
43
• Login in to Window PC 2 (172.16.50.15x:3320 )
• Click on Cisco Meeting Icon to Launch the CMS App
• Sign in with user credentials
• User Name: cmsuser2@cmslab.com Password: Cisco123
44
• Click on New call
• Dial 9001@10.10.10.17 and Enter, It will be connected CoSpaceTest Meeting room
45
Rendezvous Conferences – Test & Verify
• CMS user1 (webRTC client), CMS user2 (CMS APP) and CUCM Jabber clients are connected
CoSpaceTest Meeting Room
• Click Status  Calls, Displays 3 active calls
• After test Disconnect All calls from Meeting Room
46
Adhoc Conference from CUCM to
CMS
Adhoc Conference
• Escalation of 1:1 call to add more participants
• Uses CMS as CUCM Media resource to escalate to conference calls
• CUCM uses CMS API to create / manage conferences (HTTPS Mandatory)
• CMS 2.0+ supports CUCM Adhoc calls
• CA Signed certificates are required for CMS components
• Certificates should have Server and Client roles enabled
48
Adhoc Conference
• CUCM Configuration
• Create a SIP trunk to CMS Callbridge (secure or non-secure)
• Upload the callbridge CA certificate as CUCM-trust
• Create a Secure SIP profile with X.509 as callbridge FQDN
• Upload CMS Webadmin certificate as tomcat-trust
• Create a Conference bridge Media Resource as Cisco Meeting Server
• Add Conference bridge to MRGL and assign it to Device pool and
endpoints directly
• CMS Configuration
• Create a Incoming Rule to match CMS IP
Adhoc Conference – CUCM Configuration
• Login to CUCM (10.10.10.11)
• Click on Media Resources  Conference Bridge

• Click on Add new
• Select conference Bridge Type : Cisco Meeting Server
• Conference Bridge Name : CMS-adhoc
• Select SIP Trunk as: CMS-Trunk
• Check “Override SIP Trunk Destination as HTTP Address”
• Hostname/IP address: webadmin.cmslab.com
• Username: admin
• Password: cisco
• HTTPS Port : 445
• Click Save and Reset
50
• Verify the Conference bridge Status
• Status should be “Registered with CUCMPub”
51
• Create MRG
• Click on Media Resources  Media Resource Group
• Click on Add New
• Name: CMS-MRG
• Move CMS-adhoc from Available Media Resources to Selected Media Resources
• Click Save
52
• Create MRGL
• Click on Media Resources  Media Resource Group List
• Name: CMS-MRGL
• Move CMS-MRG from Available Media Resource Groups to Selected Media Resource Groups
• Click Save
53
• Create another MRG for Software conference bridge
• Click on Media Resources  Media Resource Group
• Name: Software-MRG
• Move CFB_2 from Available Media Resources to Selected Media Resources
• Click Save
54
• Create another MRGL for CUCM software resources
• Click on Media Resources  Media Resource Group List
• Name: Software-MRGL
• Move Software-MRG to Selected Media Resource Groups

• Click Save
55
• Assign MRGL to Phones
• Click on Device  Phone
• Click Find
• Select Jabber1
• Assign CMS-MRGL
• Click Save and Reset the phone
• Repeat Same steps to Jabber2 and Jabber3 Phones
56
Adhoc Conference – Test & Verify
• Click Cisco Jabber , login with user : cucmuser1@cmslab.com, Pwd:12345
57
Adhoc Conferences – Test & Verify
• Make a call from PC1
• Dial 1003 from CUCM User 1
• Login to PC2 and answer the call, CUCM user1 and CUCM user2 are connected
• From CUCM user1, Click on More  conference  Dial 1004
• Login to PC3 and answer the call, once connected
• From CUCM user1 Click on conference to Merge the calls
58
Adhoc Conferences – Test & Verify
• CUCM User1(1002), User2(1003) and User3(1004) are in conference now
• Verify the same by checking the active calls on CMS server
• After test Disconnect All calls

59
References
CMS Documentation
• Install Guides
https://www.cisco.com/c/en/us/support/conferencing/meeting-server/products-installation-guides-list.html
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-meeting-
server.html
• Configuration Guides
https://www.cisco.com/c/en/us/support/conferencing/meeting-server/products-installation-and-configuration-guides-list.html
• API / MMP / Customization Guides

https://www.cisco.com/c/en/us/support/conferencing/meeting-server/products-programming-reference-guides-list.html
• Knowledge Articles
https://www.cisco.com/c/en/us/support/conferencing/meeting-server/products-configuration-examples-list.html
https://kb.acano.com/
• Troubleshooting Tools
https://cway.cisco.com/tools/CollaborationSolutionsAnalyzer/
BER1738685 61
Components Required
Audio / Video Geo
Spaces WebRTC External Access CMA
/ S4B GW Distribution
✅ Clustered ✅Core
Call Bridge ✅Core ✅Core ✅Core
Web Admin ✅Core ✅Core ✅Core ✅Core
XMPP Server ✅Core ✅Core ✅Core
Web Bridge ✅Edge

Database
✅
(HA & Scale)
Load Balancer ✅Edge ✅Core
Turn Server ✅Expressway 8.9 ✅Expressway 8.9
Cisco Meeting Server Certificate Requirements
Component Certificate Type Comments
WebAdmin self-signed
Public CA Signed
WebBridge self-signed Public CA signed certificate required only if
Public CA Signed CMA WebRTC isused
CallBridge self-signed Self-signed certificates cannot be used in a

Public CA Signed Skype/Lync deployment.
Deployments with TLS SIP Trunks cannot use self
signedcertificates.
Trunk self-signed
Public CA Signed
LoadBalancer self-signed
Public CA Signed
Database Cluster Public CA Signed Self-signed certificates cannot be used in a

clustered deployment
Recorder Server self-signed Applications that interf ace to external devices require Public CA
certificates. Applicatio ns that interface internally in the Cisco
Streaming Server self-signed Meeting Server only require certificates signed by an Internal CA.
Self-signed certificates can be created via the MMP interface on Cisco
Meeting however it is strongly recommended that self-signed
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Confidential certificates only be used for test environments.
Cisco Meeting Server DNS Requirements
Record Type Example Resolves to Description
SRV (*) _xmpp-client._ tcp.example.com The A record xmpp.example.com below. Used by clients to login. The SRV record must
Usually this is port 5222. correspond to the domain used in your XMPP
usernames
SRV (*) _xmpp-server._ tcp.example.com The A record xmpp.example.com below. Used to federate between XMPP servers. The
Usually this is port 5269 SRV record must correspond to the domain used
in your XMPP usernames
A xmpp.example.com IP address of either the XMPP server or a Used by clients to login
Load Balancer which is configured to trunk
to the XMPP server.
A / AAAA join.example.com IP address of Web Bridge This record is not used by the CMS directly;
however, it is common practice to provide an end
user with an FQDN to type into the browser which
resolves to the Web Bridge. There is no restriction
or requirement on the format of this record.
A / AAAA ukcore1.example.com IP address of the Call Bridge Used by the Lync FE server to contact the Call
nycore1.example.com Bridge
A / AAAA IP address of the MMP Interface This record is used purely for admin pur- poses;
ukcoreadmin.example.com
when system administrators prefer a FQDN to
remember for each MMP interface.
If you have an FE pool, you can have multiple
SRV (*) _sipinternaltls._tcp.fe.lync-domain.com The A record of the Lync FE server or
FE records pointing to individual FE servers
FE Pool within the pool
You will need one record for each individual FE
A / AAAA fe.lync-domain.com IP address of the Lync FE server
server

Cisco Lab Cms

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Cisco Lab Cms

Încărcat de

Drepturi de autor:

Formate disponibile

CCIE Collaboration v2 WISP Lab 2:

Cisco Meeting Server (CMS)

Load Balancer TURN Server Web Bridge

Lync FE Cisco Meeting App

• All components are

• Call Bridge Cluster

CLI / MMP WebAdmin API SFTP

Plan certificates in advance and combine where possible!

SIP Endpoints Dial: WebRTC: https://join.domain.com

CMA: Your Personal Space

Key parameters for mapping

Incoming Call Rules Forwarding Rules Outgoing Call Rules

• Is the call for this CMS ? • Should the call be • Destination?

• Connect to server: cll-live.cisco.com

• Username: collab#, where # is your pod number**

**You should have received your pod number from

• Login to CUCM Web Interface

• Create a SIP trunk Security Profile in CUCM

• System  Security  SIP trunk security Profile

• Enter Name: Secure SIP Trunk Profile CMS

• Device security Mode : Encrypted

• X.509 Subject Name : callbridge.cmslab.com,

• Click on Device  Trunk

• Click Add New

• Select Trunk Type: SIP Trunk

• Enter Name: CMS-Trunk

• Select Device Pool: Default

• Scroll Down to SIP Information

• Destination Port: 5061

• Select SIP Trunk Security Profile Secure SIP

• It should be Full Service

• New meeting room “CoSpaceTest” has been created

• Click on Configuration  Incoming calls

• Keep domain name : 10.10.10.17, Priority : 10 and click Add new

• Click on Cisco Jabber , login with user : cucmuser1@cmslab.com, Pwd:12345

• Once login, Dial 9001

• It connects to CMS Meeting

• Open a Chrome browser and type

• User name: cmsuser1@cmslab.com Password: Cisco123

• Click on Cisco Meeting Icon to Launch the CMS App

• Sign in with user credentials

• User Name: cmsuser2@cmslab.com Password: Cisco123

• Dial 9001@10.10.10.17 and Enter, It will be connected CoSpaceTest Meeting room

• After test Disconnect All calls from Meeting Room

• Click on Media Resources  Conference Bridge

• Move Software-MRG to Selected Media Resource Groups

• Repeat Same steps to Jabber2 and Jabber3 Phones

• Click Cisco Jabber , login with user : cucmuser1@cmslab.com, Pwd:12345

• Login in to Window PC 2 (172.16.50.15x:3320 )

• Click Cisco Jabber , login with user : cucmuser2@cmslab.com, Pwd:12345

• Login in to Window PC 3 (172.16.50.15x:3321 )

• Click Cisco Jabber , login with user : cucmuser3@cmslab.com, Pwd:12345

• Verify the same by checking the active calls on CMS server

• After test Disconnect All calls

• API / MMP / Customization Guides

Web Admin ✅Core ✅Core ✅Core ✅Core

XMPP Server ✅Core ✅Core ✅Core

Web Bridge ✅Edge

Turn Server ✅Expressway 8.9 ✅Expressway 8.9

CallBridge self-signed Self-signed certificates cannot be used in a

Database Cluster Public CA Signed Self-signed certificates cannot be used in a

S-ar putea să vă placă și