Download CCNA Collaboration Implementing Cisco Video Network Devices (CIVND).testkings.210-065.2019-01-30.1e.235q.vcex

The subnet mask configured on the codec is 255.255.255.128, when it should be 255.255.255.0.

Software upgrades 
Automated software upgrade helps ensure the latest software updates and release key retrieval for supported devices with minimal administrative intervention. 
Cisco TMS offers an administrator-defined schedule for bulk software upgrades of supported systems. 
Reference: http://www.cisco.com/c/en/us/products/collateral/conferencing/telepresence-management-suite-tms/data_sheet_c78-707529.html

Section 1 - Basic Endpoint configuration 
Step 1 - Prior to setting up the traversal zone you will need to get all of your endpoints registered to your video network. There are several ways to do this for simplicity we will walk you through just one option. 
a. On your lab laptop open a web browser and navigate to your Telepresence Management Suite (TMS) instance at: http://tms.collab.com/tms
b. Login as 

  

  

Figure 1 TMS Login 
Step 2 -Navigate to Systems → Navigator (Figure 1) 
Step 3 - Click the "Endpoints" folder on the left side of the window and click "add systems" as depicted below in Figure 2 

  

Figure 2 Adding Endpoints 
Step 4 - Enter the IP address of your C60, and the EX60 that is not registered to CUCM into the Specify Systems text field, separating each with a comma as depicted in Figure 3below. 
Make sure that you: Leave the ISDN and IP zones "Collab Demo"
Ensure that the time zone is set to "Eastern" 
You can find the IP address of your EX60s via the system information screen on the touch panel. 
For the C60 press the home key then the far right smart button to bring up your System information screen. 

  

Figure 3 Adding Endpoints to TMS 
Step 5 - Click next, a progress window will appear as TMS reaches out to each endpoint. Once completed you see the "Add Result" screen showing that the endpoints were successfully discovered. 
Step 6 - Finally click "Finish Adding Systems" as depicted in Figure 4. 
NOTE: If your endpoints throw warnings click the check box next to them to view and correct the warnings or click "Add system despite Warnings" if available

  

Reference: http://ciscovideolab.com/mediawiki/index.php?title=Lab1
http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tms/admin_guide/Cisco-TMS-Admin-Guide-14-6.pdf

Switching policy: Two types of switching policy are available:
◦     Room switching: Room switching switches the video from all table segments of a room to all other rooms in a meeting. If the active speaker (loudest speaker for approximately 2 seconds) changes, all table segments in the new active speaker's room will be displayed in all other rooms at the same time, replacing the previously active room.
◦     Speaker switching: Speaker switching allows each segment to be switched independently, so that at any given time the three active segments, in one or multiple rooms, are displayed in all Cisco TelePresence rooms. If the active speaker changes, the speaker's table segment will be displayed in all other rooms on the corresponding screen, as shown in Figure 2.
Figure 2.      Room and Speaker Switching 

  

Reference: http://www.cisco.com/c/en/us/products/collateral/conferencing/telepresence-multipoint-switch/white_paper_c11-610159.html

Picture Mode 
The video  layout to use for a conference with more than two participants: 
Continuous Presence: split screen and view all participants continuously.
Voice Switched: see only the participant currently talking.
Enhanced CP: the MCU will al so use layouts such as 5+1 and 7+1.
Reference: http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tmsxe/user_guide/Cisco_TMSXE_User_Guide_2-3.pdf

Multiway system requirements 
Your deployment must have the following components:
  Cisco TelePresence endpoints that support Multiway™ 
  Cisco TelePresence Video Communication Server (VCS) 
  Cisco TelePresence MCU 
E: http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cuipph/8941_8945/8_5/english/qsg/QSG_8941_8945_en_851.pdf

  

Reference:
http://www.cisco.com/c/en/us/td/docs/telepresence/infrastructure/articles/cisco_telepresence_mcu_configure_multiway_kb_166.html

  

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Multiway_Deployment_Guide_X6.pdf

Understanding Recording Aliases 
The Content Server records calls and can produce the resulting recordings in a range of formats and sizes for users to watch or download. Creators of recordings can make recordings available to all or selected users. 
To make recordings, creators must use a recording alias. A recording alias defines several properties, including ones related to dialing the Content Server from an endpoint for the recording session; specifying recording outputs; and indicating viewing and editing permissions (see Recording Alias Properties). 
There are two types of recording alias:
System recording aliases, which can be used by any user in the creator or site manager role. 
Personal recording aliases, which have owners in the creator role. Owners can edit certain parts of their recording aliases: recording settings, default recording information, and default recording permissions.
Reference: http://www.cisco.com/c/en/us/td/docs/telepresence/tcs/5_0/administration/guide/tcs_5_0/recording_aliases.html#wp999176