_Spring2012_Labs_Lab2 - Cisco Video Lab

7/24/2015 /Spring2012/Labs/Lab2 - Cisco Video Lab

http://ciscovideolab.com/mediawiki/index.php?title=/Spring2012/Labs/Lab2 1/11

/Spring2012/Labs/Lab2From Cisco Video Lab

Lab written by:

Greg Schalmo, Collaboration CSE

[email protected]

Background

Configuring native interopThe CTS 500 has already been upgraded to support CTS 1.9 code which supports native interop (any CTS code 1.8 or later will supportnative interop). Let's begin the interop lab by verifying that CUCM and VCS can talk to each other by placing a call from the CTS 500-32(EXT 1000) to Natasha at EXT 2000.

Click here for the lab prerequisites

Introduction Lab Topology Fall 2012 Lab Topology Spring 2012 Lab Manual - Spring 2012 Lab Manual - Fall 2012 Lab ProctorsWiki Home

http://ciscovideolab.com/mediawiki/index.php?title=/Spring2012/Intro

http://ciscovideolab.com/mediawiki/index.php?title=File:Grschalm.jpg

http://ciscovideolab.com/mediawiki/index.php?title=File:Lab2Banner.jpg



Step 1 - Verify the quality of the connection by going under settings and viewing the call. Press -> More → Settings

Figure 1 - Press More

Figure 2 – Call Status

On the call status screen you should notice the call rate is set to 1152 and the quality is very good.

Step 2 - By default CUCM has a default video bandwidth of 384K, not conducive to making good video calls. Prior to the lab, the lab teammodified the default video bandwidth under the service parameters in CUCM. Below is a screen shot of the changes. If you are going toimplement video on your own CUCM to either modify the default video bandwidth as indicated in Figure 3, or make sure to modify thebandwidth between the regions accordingly.

Figure 3

Step 3 - Now we are going to try presenting content. Place a call from the VCS EX60 (EXT 2000) to EXT 1000. Once the call isestablished, share content from the EX60.

http://ciscovideolab.com/mediawiki/index.php?title=File:Lab2-image002.png





You should be able to see the content and video on both endpoints, but you will notice on the CTS-500 that you are unable to change thecontent position or swap video for content.

Step 4 - On your EX60 press the MORE → SETTINGS → Call Status and you will see that the presentation is set to off.

Figure 4

Your CTS-500 should look very similar in screen layout to the screen shot below:

Figure 5

By default CTS units will negotiate to other endpoints, but content sharing via BFCP is not enabled and must be configured either on a unitby unit basis or you can enable it on all units by configuring a template. In the lab we will configure the CTS-500 to enable BFCP

Step 5 - We need to log into the CUCM now. Open a web browser on your student laptop and go to http://10.5.0.60 orhttp://cucm.collab.com. Log in with the following credentials:

Username: administrator Password: Cisco12345

Step 6 - From the main screen go to Devices → Phone



http://cucm.collab.com/

http://10.5.0.60/



Figure 6

Step 7 - Click the FIND button

Figure 7

Step 8 - From the list of endpoints select your CTS-500

Figure 8

Step 9 - Once you have selected the endpoint scroll down to the Protocol Specific Information sections and check the Allow PresentationSharing using BFCP box






Figure 9

Step 10 - Now click SAVE → Reset → RestartStep 11 - When the CTS500 reregisters, call from VCS EX60 (EXT 2000) call the CTS-500 (EXT 1000) and share content from the EX60to the CTS-500. Your screen should look similar to the one below, notice the content window now appears to be layered into theconversation vs. being composited together.

Figure 10

Step 12 - You should now be able to on your control panel for the CTS-500 to select the presentation button and see options to change howthe presentation is being received, try changing the layout and see what you like better. If you had a secondary content display attached tothe CTS-500 the content would now be displayed on the separate monitor vs. the same image on both.





Figure 11

You can verify that you have in fact configured BFCP successfully very easily. On the EX60 control panel by pressing the MORE →Settings → Call Status and looking at the presentation status on the panel. You should now see a separate content channel as below withthe full sharing information

Figure 12

If your feeling ambitions repeat the calls from the CTS to the VCS registered EX60 (EXT 2000) and this time share content while pluggedinto the CTS-500, see what the results are.

You have now successfully integrated your CTS-500 infrastructure for full native interop as well as enabled BFCP for content sharing. Thiswill allow your CUCM registered devices that have BFCP capabilities to share audio, video, and content so they may interop with any otherstandards based endpoint.





For information onlyNOTES: - DO NOT DO THIS IN THE LAB – THIS IS FOR YOUR OWN EDIFICATION!!!

In previous releases of CUCM (8.5 and 8.6) and CTS 1.8.X it is possible to configure native interop between CTS endpoints and VCS. Itdoes require a different configuration of CUCM and of the endpoints because in previous releases BFCP had to be applied to the SIPprofiles of the units and the trunks between CUCM and the VCS.

To reconfigure this we would need to enable BFCP on CUCM and VCS.

Step 1 - Login back into CUCMStep 2 - First we need to create a new SIP Profile that supports BFCP.Step 3 - Click under Device-> Device Settings -> SIP Profile

Figure 9 - SIP Profile

Step 4 - Now add a new SIP Profile. Give it a name of SIP Profile - BFCP, make sure Allow Presentation Sharing using BFCP, then clickSaveNow add a new SIP Profile. Give it a name of SIP Profile - BFCP, make sure Allow Presentation Sharing using BFCP, then clickSave.




Figure 10 - Add SIP Profile

Step 5 - Now we need to apply this setting to the SIP Trunk going toward VCS and verify that a BFCP profile was already applies to the7975 and CTS. We already applied a profile like the one we had you create to save you from a 10 minute reboot of the CTS codec.

First go to the Phone devices page Device->Phone and search for your CTS unit and its phone which should show as registered.

Figure 11 - Search for CTS

http://ciscovideolab.com/mediawiki/index.php?title=File:Lab2-image030.jpg




Figure 12 - Click on CTS

Step 6 - On the CTS endpoint descend the page and verify that the the BFCP profile has been applied for you already. DO NOT CHANGEthe one already applied as it will cause a reset of the CTS.

Step 7 - Now repeat this process on the trunk. Go under Device-> Trunk. Do a find and then click the VCS trunk

Figure 13 - Click VCS

Step 8 - Go down the page and change the SIP profile to the one you created previously as pictured in Figure 13.

Now login to VCS at http://vcs.collab.com or http://10.5.0.70

USER PASSWORDadmin Cisco12345

Step 9 - Click on VCS configuration -> Zones

http://vcs.collab.com/


http://10.5.0.70/




Figure 17 - VCS Zones

Figure 18 - CUCM Zone

Step 10 - Now we need to change the Zone profile on the trunk to support BFCP. The default using Communications Manager as the profilefilters BFCP to and from CUCM. To enable this we set this to custom which allows this.

Figure 19

Step 11 - Now retry your test call from the CTS to 3300 and again share content. You should see a separate presentation and video.






Figure 20 - Separate Video and Presentation

Step 12 - Check the call status and you should now see presentation on the receive side.

Figure 21 - Call Status Presentation

Retrieved from "http://ciscovideolab.com/mediawiki/index.php?title=/Spring2012/Labs/Lab2&oldid=1155"

This page was last modified on 22 May 2012, at 16:58.This page has been accessed 7,727 times.



http://ciscovideolab.com/mediawiki/index.php?title=/Spring2012/Labs/Lab2&oldid=1155

Documents

_Spring2012_Labs_Lab2 - Cisco Video Lab