Release Notes for Cisco Media Blender, Release 7.

July 23, 2010

• • • • • • • • • • •

Introduction, page 2 System Requirements, page 2 Related Documentation, page 2 Installation Notes, page 3 New and Changed Information, page 16 Limitations, page 17 Administration User Interface, page 18 Resolved Caveats in this Release, page 22 Open Caveats in This Release, page 24 Obtaining Documentation, Obtaining Support, and Security Guidelines, page 24 Documentation Feedback, page 25

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

© 2010 Cisco Systems, Inc. All rights reserved.


Cisco Media Blender (CMB), Release7.1(2) is delivered as a Maintenance Release (MR) along with Cisco Unified Interaction Manager MR 4.3(2). Patch installer is used to upgrade the CMB Release 7.1 base release version to CMB 7.1(2). These release notes describe the new information and caveats for CMB Release 7.1(2). The CMB, Release 7.1(2) is the first MR for the base release 7.1. For a list of the open and resolved caveats in this release, see the Resolved Caveats in this Release, page 22 and the Open Caveats in This Release, page 24. Updates for these release notes occur with every maintenance, minor, and major releases. CMB, Release 7.1(2) can be installed on a CMB Base Release 7.1 only.

System Requirements
Hardware Requirements
There are no specific hardware requirements for CMB, Release 7.1(2) as it is installed on the same server where CMB, Release 7.1 is installed. Ensure that the hard drive where CMB, Release 7.1 is installed has sufficient (minimum of 500 Megabytes) free disk space.

Software Requirements
CMB, Release 7.1(2) release requires JDK version 1.6.0 Update 17 and Apache Tomcat version 5.5.28. These updates are installed by the CMB 7.1(2) MR installer. If the CMB 7.1(2) MR installer detects that the required third party software(s) are already installed, the installer will skip the third party software installation.

Related Documentation
For more information on Cisco Media Blender Base Release 7.1, see the following installation and administration guides.
• •

Cisco Media Blender Installation Guide for Cisco Unified Contact Center Enterprise & Hosted Editions version 7.1 Cisco Media Blender Administration Guide for Cisco Unified Contact Center Enterprise & Hosted Editions version 7.1

Release Notes for Cisco Media Blender, Release 7.1(2)


1(2) 3 .1(2) MR from Cisco. Release The License Agreement screen appears.1(2) MR.) Double-click the CMB MR installer exe file to begin the installation.1(2) MR Follow these steps to install the Cisco CMB 7. Release Notes for Cisco Media Blender.3(2) media to a local directory in the CMB server. Step 1 Step 2 Copy the CMB 7.1(2) MR from CIM 4. The welcome screen appears. (You can also download th CMB 7. Figure 1 Welcome Screen Step 3 Click Next.Installation Notes Installation Notes Installing Cisco CMB 7.

1(2) 4 . Release 7. Click Next.Installation Notes Figure 2 License Agreement Step 4 Step 5 Read the software license agreement and select I accept the terms of license agreement. Release Notes for Cisco Media Blender. The Ready to Install the Program screen appears.

Installation Notes Figure 3 Ready to Install the Program Step 6 Click Install to begin the installation. Release Notes for Cisco Media Blender. Release 7. The Choose Folder window appears.1(2) 5 .

1 base release and you cannot install JDK at this location. The installation screens (Figure 5 and Figure 6) appear. Choose a location and click OK.1(2) 6 .6.0_17. By default. Note Step 8 Release Notes for Cisco Media Blender. Ensure that you do not select the <C:\CiscoMB> location to install JDK.Installation Notes Figure 4 Choose Folder to Install java JDK Step 7 The Installer prompts you to choose a location to install Java JDK 1. <Windows Drive>:\Program Files path is selected. Release 7. This is the product install location for CMB 7.

1(2) 7 . The Apache Tomcat License Agreement screen appears. Release 7. Release Notes for Cisco Media Blender.Installation Notes Figure 5 Installing Java JDK Figure 6 Apache Tomcat Setup Welcome Step 9 In the Apache Tomcat Setup Welcome screen. click Next.

The Choose Components screen appears. Release Notes for Cisco Media Blender. Figure 8 Apache Tomcat Installation: Choose Components Step 11 Select the components you want to install and click Next. Release 7.1(2) 8 . The Choose Install Location screen appears.Installation Notes Figure 7 Apache Tomcat License Agreement Step 10 Read the agreement and select I Agree.

Click Next.Installation Notes Figure 9 Apache Tomcat: Choose Install Location Step 12 Step 13 By default. Figure 10 Apache Tomcat Setup: Configuration Options Step 14 By default. Click Next to continue. Release 7. Release Notes for Cisco Media Blender. To access Tomcat administration pages. the destination folder is specified.1 Connector Port is set as 8080. the HTTP/1. The Apache Tomcat Setup: Java Virtual Machine Path Selection screen appears. click Browse and choose an appropriate folder. provide an username and password. If you want to change the destination folder.The Apache Tomcat Setup: Configuration Options screen appears.1(2) 9 .

1(2) 10 . Release 7. is displayed. enter the correct JRE installation path and click Next to continue the installation (Figure 12 and Figure 13).0 update 17 is installed. If this is not the correct location.Installation Notes Figure 11 Apache Tomcat Setup: Java Virtual Machine Path Selection Step 15 By default.6. Release Notes for Cisco Media Blender. the path where JRE 1.

Installation Notes Figure 12 Apache Tomcat Setup: Installation Figure 13 Apache Tomcat Setup: Installation Complete Step 16 Click Finish to complete the installation. Release Notes for Cisco Media Blender. The CMB Installation Wizard Complete screen appears.1(2) 11 . Release 7.

Installation Notes Figure 14 CMB Installation Wizard Complete Step 17 Choose an appropriate option on this page and click Finish to complete the installation. Release 7. Note Uninstalling Cisco CMB 7. re-patch files (if required) based on previous status. Release Notes for Cisco Media Blender.1(2)” and click Remove. You are prompted to confirm the uninstallation. will skip the third-party software installation if they are already installed . you recover from the failure by re-running the patch installer again.1(2) 12 . Select “Cisco CMB Maintenance Release CMB 7. The patch installer will detect the installation status at the time of failure and upon re-run.1(2) MR: Step 1 Step 2 Choose Start > Control Panel> Add or Remove Programs. For system failures such as downtime of server during the installation process.1(2) MR Follow these steps to uninstall Cisco CMB 7. and completes the installation.

1(2): Uninstallation Screen I Step 3 Click Yes.Installation Notes Figure 15 Cisco CMB Maintenance Release CMB 7.1(2) 13 . Release Notes for Cisco Media Blender. Release 7. The uninstallation screens appear.

1(2): Uninstallation Screen II Step 4 After the uninstallation is complete. Release 7.1(2) 14 .Installation Notes Figure 16 Cisco CMB Maintenance Release CMB 7. the Uninstall Complete screen appears. Release Notes for Cisco Media Blender.

Installation Notes Figure 17 Unistall Complete Step 5 Click Finish to complete the uninstallation. Release 7. Note Ensure that you start the IIS/WWW services if you do not want to re-boot the system. Release Notes for Cisco Media Blender.1(2) 15 .

where multiple CIM application instances connect to multiple CMBs. CMB. The use of Tomcat as an application server is a well understood concept within the organization as it is currently utilized in multiple existing products including Unified CCE. Multiple CMB instances connecting to same peripheral CMB. Release 7. page 16 Migration from JDK 1.4. Release 7. page 16 Migration from IIS/ServletExec to Apache Tomcat. JDK versions 1. Migration from IIS/ServletExec to Apache Tomcat CMB.1 runs on the ServletExec/IIS platform using New Atlanta ServletExec 5. Release 7.1(2).New and Changed Information New and Changed Information This section discusses in detail the new information for this release. Release 7. Release7.4 to 1.6. Apache Tomcat is available as open source and is widely accepted as the preferred web server for java based applications. The supported peripherals are Avaya ACD and Cisco Unified Call Manager (Unified CM). • • • Migration from JDK 1. For more information about this feature and related configuration.4 and lower versions are end-of-life/end-of-support. enhanced for each loop.6.6 are Autoboxing & Unboxing. generics. and provides improved performance along with better logging and debugging capabilities.1(2) 16 . Some features provided by 1.0 update 17 CMB. Release 7. the JDK version is upgraded to version 1. and scalability. For CMB. This feature supports appropriate routing of the callback and blended collaboration requests in cluster based environments. and no patches/fixes will be provided for defects/issues found in earlier JDK versions. CMB.1 Release Notes for Cisco Media Blender.1(2) supports multiple CMB servers connecting to a single peripheral. Release 7.4 to 1. This new feature requires configuration changes to the CMB and ICM script.1 supports a single CMB instance connecting to a single peripheral. CMB.1(2) will require web server/application server (that is.0 update 17. concurrency utilities. This migration to higher JDK version is beneficial in terms of new features. page 16 Multiple CMB instances connecting to same peripheral.1(2) will use Apache Tomcat as the web server/servlet container. see the Cisco Media Blender Administration Guide. Release 7.0 as the servlet container and Microsoft Internet Information Services 6.0 update 17. Release 7. These CMBs are in turn connected to a single ACD peripheral.0 as the web server. better performance. and son on.1 uses JDK 1.6. Tomcat) to be running at all times.

0. The agent recovers from such a symptom by dropping the voice call and will be "AVAILABLE" again for routing. Impact: The blended collaboration activity will be affected since the web session will not be established. and so on. Unified CCE performs the routing of the blended collaboration activity to an available agent. This symptom is observed for less than 1 percentage of the total blended collaboration activities handled by the system and is normally in the range of 0. the assignment of web session fails and as a result. This issue will be observed only for Avaya based deployments where the "Predictive" CTI call strategy is used and will not impact blended collaboration sessions which use other CTI call strategies like PhantomWaitRelease. If the symptom of session assignment failure is observed. Under heavy and persistent load conditions. the customer and agent can continue "talking" over the voice path or end the blended collaboration session by dropping the voice call. there is no impact to Blended collaboration activities in IPCC based deployments where Cisco Unified Call Manager is deployed as the peripheral. PhantomWaitNoRelease. CIM will not synchronize the agent's browser with the customer and the agent remains logged in without getting connected to the customer over the web media. but the collaboration (web chat) session between the agent and customer is not established.001 . There is no impact to web callback since there is no collaboration involved and callback is a VOICE only activity. CMB sends a session assigned event to CIM. Also. The customer will be connected to the agent over the voice path but the collaboration will not be initiated through the web interface. The voice path is initiated by the CMB and the call is connected through the Avaya ACD (ACD selects an available ACD agent and connects the caller with the selected agent).003 percentage. Release Notes for Cisco Media Blender. in a few intermittent cases. If the symptom is observed and the agent is connected ONLY on the voice path with the customer. the voice path between the customer and agent is established.1(2) 17 . Release 7. In Avaya based Unified CCE deployments (integrated with CIM). it is observed that for a few blended collaboration activities. After the voice path is established. the customer and agent will never collaborate over the web medium. the voice path between the agent and the customer will remain unaffected. Also. the blended collaboration activity is initiated by CIM through the Media Routing interface. CIM connects the caller and the selected agent over the web collaboration medium. the agent will not be routed another BC activity since the ACD finds the agent in "TALKING" state. Workaround: There are no workarounds for this issue. However. The customer "talks" to a customer service agent and simultaneously collaborates with the same agent through the web medium. it is observed that the session assigned event is sent by CMB with an incorrect peripheral number which also results in the failure of web collaboration session. Since CIM never receives the session assigned event for the selected agent.Limitations Limitations Web session not established for blended collaboration with Avaya ACD Symptom: For blended collaboration activities under heavy load conditions (600 agents handling 10 blended collaboration sessions per hour). Detailed Description: A blended collaboration activity is a combination of web callback and web collaboration.

1 release except for few changes. Release 7. wait for some time (approximately four minutes) to allow Apache Tomcat to start and deploy the CMB application before accessing the CMB administration console. You can access the CMB.1(2) administration user interface: 1.1(2) administration user interface is similar to the CMB.1(2) 18 . Release 7. Administration User Interface CMB.1(2) administration pages using the URL: http://<hostname>:8080/cmb. Blended collaboration activity belongs to the CISCO_VOICE MRD in Unified CCE and the voice path is always established first before the session assignment failure. There will be no impact to Unified CCE reports since for Avaya based deployments. Release 7. Welcome to Media Blender Administration page Welcome to Media Blender Administration Figure 18 Release Notes for Cisco Media Blender. Following are the sample screens for CMB. BC activities which do not get assigned to the agent as a result of this symptom will be reported as "Abandoned". After Tomcat service is initiated. Release 7. Note Ensure that Apache tomcat service is started and running before accessing the URL (http://<hostname>:8080/cmb). Release 7.Administration User Interface Impact to Reporting: In CIM reporting.

1(2) 19 . Release 7. Cisco Media Blender Administration and Online Help Page Cisco Media Blender Administration and Online Help Figure 19 Release Notes for Cisco Media Blender.Administration User Interface 2.

1(2) 20 .Administration User Interface 3. Cisco Media Blender Administration Welcome Page Welcome to Cisco Media Blender Administration Welcome Figure 20 Release Notes for Cisco Media Blender. Release 7.

Cisco Media Blender Administration Online Help Cisco Media Blender Administration Online Help Figure 21 Release Notes for Cisco Media Blender. Release 7.Administration User Interface 4.1(2) 21 .

1.1(2) in IPCC Not able to start the blender after enable the application path id. Note Defects.2 Failed CMB 7. Release 7. enhancements and features are cumulative and apply both to the current maintenance version and to previous maintenance versions. Release 7. Table 1 Resolved Caveats for Cisco Media Blender. Webpage cannot be displayed shown when we click on BackButton in CMB 712 Page not found error shown in the CMB 7.1(2) Patch installer (754) fails with a tomcat error CMB712 Drop2 installer shown as failed at the END screen of the installe "Could not find apppathid" is not prinitng the CMB log for BC activity. AcceptDrop=true functionality is not working for Avaya if we end Voice Logs are getting overwritten once the log file reaches 5000 line.1.2 showing wrong Providing wrong Password in CMB admin UI throws IE Exception. Defects are listed by component and then by identifier.1(2) 22 .2 online help Wrong version of Install & Admin guide is linked in online help CMB 712 Installation of CMB 7. unless otherwise noted. CD 6 observed during Multi peripheral Blended Collaboration load testing Copyrights of CMB 7.1.1 Change web server used by Cisco Media Blender to Apache Tomcat Release Notes for Cisco Media Blender.Resolved Caveats in this Release Resolved Caveats in this Release This section contains a list of defects resolved in this release.1(2) Identifier CSCtf10366 CSCtf79982 CSCtg11506 CSCtf06223 CSCth28269 CSCtf05328 CSCtf05342 CSCtg49762 CSCtf68139 CSCtf68356 CSCtf03099 CSCtf16127 CSCtf32952 CSCtf90707 CSCtf05962 CSCte16254 CSCte16262 Component acd-ipcc acd-lucent acd-lucent bapi bapi admin-ui admin-ui admin-ui documentation documentation installation installation installation acd-lucent admin-ui infrastructure infrastructure Sev 1 1 2 2 2 3 3 3 3 3 3 3 3 4 4 6 6 Headline License error seen in CMB7. Wrong CMB version shown in CMB Online Help Window Upgrade JDK version used by CMB 7.

Release 7. click (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.1(2) 23 . To look for information about a specific problem. and so on.Resolved Caveats in this Release Using Bug Toolkit In general. enter the bug ID number in the “Search for Bug ID” field You need an account with Cisco. Release Notes for Cisco Media Blender. log onto http://tools. create bug user ID and Log in with your Cisco. which is an online tool that is available for customers to query defects according to their own needs. click Help in the Bug Toolkit For information about how to search for bugs. you can find the latest caveat information through Bug Toolkit.  To access the Bug Toolkit. go to user ID and password Procedure To use the Software Bug Toolkit. you need the following items: • • • Tips Internet connection Web browser create saved To access Bug Toolkit. follow these steps: Step 1 Step 2 Step 3 To access the Bug Toolkit.

Release Notes for Cisco Media Blender. and Security Guidelines For information on obtaining documentation. Table 2 Identifier CSCtg96370 CSCtg58123 Component acd-lucent bapi Sev 2 2 Headline Wrong Peripheral number received for 12 activities in SessionAssignedEve For 5 activities Session Assign Events were not sent from CMB Obtaining Documentation.Open Caveats in This Release Open Caveats in This Release This section contains a list of defects that are currently pending in CMB for this release. and also recommended aliases and general Cisco documents. access Bug Toolkit and follow the instructions as described in Using Bug Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. Obtaining Support. be aware that the following table reflects a snapshot of the defects that were open at the time this report was compiled.1(2) 24 . Note Because defect status continually changes. obtaining support. For an updated view of open defects. at: http://www. Release 7. security guidelines. see the monthly What’s New in Cisco Product Documentation. which also lists all new and revised Cisco technical documentation. page 23.0. The RSS feeds are a free service and Cisco currently supports RSS version 2. Defects are listed by component and then by identifier. providing documentation

Any use of actual IP addresses in illustrative content is unintentional and coincidental. All rights reserved. Release 7. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES. INFORMATION. The use of the word partner does not imply a partnership relationship between Cisco and any other company. We appreciate your comments. WITHOUT LIMITATION. All rights reserved. CONSEQUENTIAL. THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Copyright 1981. INCLUDING. and/or its affiliates in the U. ALL STATEMENTS. 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.Documentation Feedback Documentation Feedback You can provide comments about this document by sending e-mail to the following address: mailto:ccbu_docfeedback@cisco. The Cisco implementation of TCP headercompression is an adaptation of a program developed by the University of FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING.command display output. Copyright 2010 Cisco Systems. SPECIAL. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN. A listing of Cisco's trademarks can be found at www. Any examples.1(2) 25 . Release Notes for Cisco Media Blender. Cisco and the Cisco Logo are trademarks of Cisco Systems. Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. USAGE. Regents of the University of California. ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. EXPRESS OR IMPLIED. WITHOUT LIMITATION.S. CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. THOSE OF MERCHANTABILITY. Inc. LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. Inc. EXPRESSED OR IMPLIED. and other countries. AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY Third party trademarks mentioned are the property of their respective owners. (1005R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT. OR INCIDENTAL DAMAGES. and figures included in the document are shown for illustrative purposes only. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY.

Documentation Feedback Release Notes for Cisco Media Blender.1(2) 26 . Release 7.