Anyone looking to obtain their CCNP Collaboration? Why not check out my CCNP Collaboration v1 Advanced Technologies on INE!
So I decided to go ahead and do my own videos for the 300-085 CAPPS exam. Online training for this exam is basically non-existent and the official Cisco offering for CAPPS is not great in my opinion and only motivated me even more do my own thing. I hope you enjoy watching them as much as I did making them.
A few things I wanted to bring to your attention if you are thinking of sitting the exam or watching my videos.
- Please make sure you do not go into these videos thinking they are all you need to pass the exam. They are not enough and you will need a combination of methods and resources to pass the exam.
- If there is 1 thing I am trying to get across in the videos, you need to focus on the exam topics and then get stuck into the resources available, such as Cisco dCloud, home labs and also all of the documentation available from Cisco.
- I do not intend on making this videos for any financial reason or to make profit anywhere.
- This videos are my own personal approach for preparing for the CAPPS exam only. Please do not blame me if you fail the exam after just watching my videos and doing nothing else.
Good luck everyone!
- Add new user to TPS for Conductor purposes
- API Access
More cfg than TPS!
- Maintenance + Option Keys – add release keys
- Users -> Admin Accounts
- Add account for CUCM purposes to add conf bridge later
- Add new IPs for adhoc and rendezvous meetings
- Restart Conductor
- Add conf bridge pool (TP MCU or TPS)
- Bridge pool contains conf bridges
- Create conf bridge with credentials from TPS server (Above)
- Service Preferences (Ordered list of bridge pools)
- Conference Template – sets parameters of conference
- Create one for adhoc and one rendezvous
- Add conference alias – point to conference template
- Add a location (Puts it all together!)
Now we go to CUCM….
- Add a SIP Trunk with a Route Patterns to send conf bridges to Conductor
- 1 for Adhoc and 1 for Rendezvous
- Add conf bridge to CUCM – type is Conductor!
- Use the SIP Trunk for either Adhoc or Conductor
- Add credentials we added from Conductor
- Now we need to add the CFB to a MRG and MRGL
- Add a new admin account to Conductor for TMS purposes
- CMR requires TMS PE to be installed and licenses
- 14.4 TMS to see CMR
- Add Conductor to TMS
This topic describes the Cisco TelePresence Management Suite (TMS) Provisioning Extension features.
TMS Provisioning Extension simplifies scaling of video across the enterprise:
|Provisioning Scale||Simplifies management of up to 100,000 telepresence users across disparate locations and networks Automated user account and phone book creation|
|Intuitive Meetings||Intuitive Collaboration Meeting Rooms (CMRs) Configure personal CMR preferences.|
|Intuitive Scheduling||Extend scheduling capability to everyone. Smart Scheduler simplifies the booking process for single and recurring telepresence meetings.|
|Endpoint Support||Quick deployment with predefined templates Low touch provisioning for C, E, EX, MX, and SX Series endpoints and Cisco Jabber Video for TelePresence and iPad|
The figure shows the main features and benefits of the Cisco TMS Provisioning Extension.
Smart Scheduler is a part of Cisco TMS Provisioning Extension.
This topic describes the integration of Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE) with Microsoft Exchange.
Add Exchange mailboxes:
- Create a User mailbox for TMSXE.
- Create a Room mailbox for each endpoint.
- Give the TMSXE user Full Access permission for each endpoint mailbox.
- Configure the endpoint mailbox properties.
- Configure the email address in the endpoint configuration on Cisco Unified Communications Manager.
Set the following on Microsoft Exchange for the endpoint mailbox:
- Automatically accept invitations: True
- Remove the Private flag for all meetings accepted by the mailbox: True
- Delete Meeting Subject: False
- Add organizer to the subject of a booking: False
Then start the TMSXE Configuration setup GUI, which is, in most cases, on a standalone server, and specify the following:
- TMS Server IP address, username, and password
- Exchange Server IP address, username, and password, as well as the email address of the sender
Add the video endpoints and map them to their email addresses.
Use the Cisco TelePresence Management Suite display name as the mailbox name.
Schedule a meeting and test the integration.
This topic describes how to add Cisco TelePresence Video Communication Server (VCS) endpoints to Cisco Unified Communications Manager for scheduling.
- Create an access control group with the following permissions:
- Standard AXL API access
- Standard CTI enabled
- Standard Serviceability
- Standard Cisco Unified Communications Manager Admin users
- Standard RealtimeAndTraceCollection
- Create an application user for Cisco TMS:
- Add the user to the access control group.
- Assign all endpoints that you plan to add to Cisco TMS to the application user.
The application user is a service account that Cisco TelePresence Management Suite (TMS) uses to log into Cisco Unified Communications Manager and to control video endpoints for scheduling.
In Cisco TMS, do the following:
- Add Cisco Unified Communications Manager and specify the application user with its credentials.
- After integrating these systems, select the video endpoints from the received device list.
For Cisco TelePresence Video Communication Server, do the following:
- Add the Cisco VCS endpoint to Cisco TMS, using its IP address.
- Enter the administrator user credentials.
This topic describes the recommended Cisco TelePresence Management Suite (TMS) scheduling deployment mode.
Cisco TMS scheduling deployment models are Microsoft Outlook- and web-based scheduling.
Cisco TMS directly manages multipoint control units and Cisco TelePresence Servers from a scheduling perspective. The Cisco TelePresence Conductor is used with Cisco Unified Communications Manager for nonscheduled conferences and for optimized resource utilization when devices with different capabilities are conferenced together.
The Cisco TMS Extension for Microsoft Exchange (Cisco TMSXE) is another layer for scheduled conferences.
This topic describes the Cisco TelePresence Conductor support.
Conference scheduling is available with Cisco TMS 14.3 and Cisco TelePresence Conductor XC2.2
- Only conference monitoring was available previously.
- Multipoint control unit registered to Cisco VCS is managed by Cisco TelePresence Conductor and scheduled by Cisco TMS.
In future versions, Cisco TelePresence Conductor can be connected with Cisco Unified Communications Manager, and Cisco TelePresence Management Suite (TMS) will be able to schedule conferences as well. With Cisco TelePresence Conductor, the conferencing management is virtualized, separated from the physical hardware, and managed centrally in Cisco TelePresence Conductor.
Limitations and recommendations for Cisco TelePresence Conductor are as follows:
- Cisco TMS cannot properly reserve ports for meetings that are scheduled by Cisco TelePresence Conductor.
- As a result, conference resources are not assured.
- The recommendation for scheduled meetings is to directly manage and schedule the Cisco TelePresence Server and multipoint control units with Cisco TMS.
This topic describes the calendaring options in the Cisco TelePresence Management Suite (TMS).
Cisco TMS extensions are available for the following:
- Microsoft Exchange (TMSXE)
- IBM Lotus Notes (TMSXN)
- TMS Booking API (TMSBA)
Cisco TMS application
- Book from TMS web-based interface
- Smart Scheduler with simplified GUI is part of Provisioning Extension (TMSPE) for self-service
The Cisco TMS scheduling extension products are as follows:
- The Cisco TMS Smart Scheduler interface, included with the Cisco TMS Provisioning Extension (Cisco TMSPE), allows simple, intuitive booking of single-instance and recurrent telepresence meetings.
- Cisco TMS supports Microsoft Exchange Server 2007 and 2010 calendar integration through the Cisco TMS Extension for Microsoft Exchange (Cisco TMSXE).
- Cisco TMS supports IBM Lotus Domino Server calendar integration through Cisco TMS Extension for IBM Lotus Notes (Cisco TMSXN).
- Custom-built scheduling interfaces for other calendaring products are supported through the Cisco TMS Extension Booking API (Cisco TMSBA).
This topic describes the call launch options that are provided by Cisco TelePresence Management Suite (TMS).
The table specifies the call launch options:
|Call Launch Option||Description|
|One Button to Push||Conference dial-in information is automatically presented on endpoints that support OBTP.|
|Automatic Connect||Cisco TMS automatically connects all the participants at the specified time and date.|
|Manual Connect||At the specified time and date, the system listed as the VC master will be prompted to begin the call. The call is automatically connected when the VC master initiates the call.|
|No Connect||This option reserves the room and generates the call route, but does not connect the route. You can start the conference with the participants in the Conference Control Center by clicking Connect.|
|Reservation||This option reserves the room but does not initiate any connections.|
OBTP can be used on the touch control, phone, or with a remote control. This option is the simplest for the user, because the user does not need to know the conference number, ID, or a PIN. The user simply selects the correct meeting, pushes one button, and is connected to the conference. After pushing the button, a call is launched to the multipoint control unit to join the conference.
With Automatic Connect, the multipoint control unit dials the endpoints and the user must answer the call to join the meeting. The default is to try three times to reach the endpoint. You can enable AutoAnswer to automatically connect the endpoint to the conference, but this approach may create “empty rooms” in your conference.
With Manual Connect and No Connect, an administrator must log in and start the meeting. With Reservation, only the room is reserved without a video endpoint.