Cisco MediaSense Video on Hold Configuration
First Published: Jan 28, 2014
Last Updated: Feb 11, 2016
This topic provides the configuration information for Cisco MediaSense (MediaSense) Video on Hold (VoH) in contact center deployments.
The intended audience should be able to perform system-level configuration of Cisco components and deployments and be familiar with products.
The configuration information is based primarily on the system tests performed during Cisco Collaboration Systems Release10.0(1) testing.
This topic does not contain detailed step-by-step procedures. For detailed information about installing and configuring MediaSense, refer to MediaSense documentation in Related Documentation section.
For information about design considerations and guidelines to deploy Cisco Unified Communications Manager (Unified CM) and MediaSense, see:
■ Cisco Unified Communications Manager Design Guides: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.html
■ Solution Reference Network Design for Cisco MediaSense: http://www.cisco.com/en/US/products/ps11389/prod_installation_guides_list.html
This section provides information about the MediaSense Video on Hold deployment used for Cisco Collaboration Systems Release 10.0 (1) testing. In the contact center testbed, other system components are installed and tested, including Cisco Unified Contact Center Enterprise (Unified CCE), Cisco Unified Customer Voice Portal (Unified CVP), and gateways.
Cisco MediaSense Video on Hold Deployment
Video on Hold Deployment
In the Contact Center deployment, a MediaSense cluster consists of two nodes which act as a media streaming server for the video on hold solution.
VoH functionality is enabled in call flows from Data Center A and the Remote Site by creating different VoH servers, each with different video streaming IDs.
■ Video on Hold supports load balancing by redistributing video playbacks across multiple MediaSense servers.
■ For load balancing, the MediaSense server sends a "302 Redirect" message with the IP address of the new MediaSense server.
■ Unified CM reroutes the call to the new MediaSense server based on the IP address in "302 Redirect" message.
The following table provides this information:
■ Configuration Tasks: List of high-level configuration tasks
■ System Test Specifics: System test variations from procedures and settings documented in the product documentation.
■ More Information: Links to product documentation for detailed configuration information related to the high-level tasks.
Note: Default and recommended values specified in the product documentation were used during system testing, unless otherwise noted in the System Test Specifics column.
Table 1. Unified Communications Manager Configuration
Table 2. MediaSense Video on Hold Configuration
■ For related information about configuration and troubleshooting, see http://www.cisco.com/en/US/products/ps11389/prod_installation_guides_list.html.
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2016 Cisco Systems, Inc. All rights reserved.