


 



<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://docwiki.cisco.com/w/skins/common/feed.css?270"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://docwiki.cisco.com/w/index.php?title=Special:Contributions/Txavier&amp;feed=atom&amp;limit=50&amp;target=Txavier&amp;year=&amp;month=</id>
		<title>DocWiki - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://docwiki.cisco.com/w/index.php?title=Special:Contributions/Txavier&amp;feed=atom&amp;limit=50&amp;target=Txavier&amp;year=&amp;month="/>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Special:Contributions/Txavier"/>
		<updated>2013-05-25T00:16:16Z</updated>
		<subtitle>From DocWiki</subtitle>
		<generator>MediaWiki 1.16.0</generator>

	<entry>
		<id>http://docwiki.cisco.com/wiki/VXML_Server:_VXML_browser_cannot_stop_the_execution_of_the_audio_node,_when_audio_file_from_the_previous_node_is_missing.</id>
		<title>VXML Server: VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing.</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/VXML_Server:_VXML_browser_cannot_stop_the_execution_of_the_audio_node,_when_audio_file_from_the_previous_node_is_missing."/>
				<updated>2013-05-22T13:23:01Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing. ==&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| When the audio node is executed, the VXML broswer tries to fetch the audio file and simultaneously posts a HTTP request to the new document as well. In Response, the VXML Server returns the next VXMLDocument(which has TTS string to play). As a result the VXML browser gets a badfetch from the Media Server and sends a POST HTTP request with the errorType as bad.fetch to the VXML server.&lt;br /&gt;
Also,the HotEvent defined in the application for badfecth throws VXMLDocument(Error.wav) and results in the call being disconnected.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message/Symtom'''&lt;br /&gt;
| Hotevent document is not executed, and as a result call never drops as expected and goes on.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| The nature of the VXML browser is such that once the VXML document starts processing, it cannot be interrupted. This results in the VXML document being executed before the next node which will eventually drop the hotevent VXML document.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| Use a dummyObject which will halt the execution of the browser until object tag finishes. This ensures that the interpreter sends 404 badfetch in the POST request and will process the Hotevent instead of the next node.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| CVP 8.0 ESxx. onwards&lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCug77989. For more information on dummyObject,VXML syntax, see the attachements in CDETS. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/VXML_Server:_VXML_browser_cannot_stop_the_execution_of_the_audio_node,_when_audio_file_from_the_previous_node_is_missing.</id>
		<title>VXML Server: VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing.</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/VXML_Server:_VXML_browser_cannot_stop_the_execution_of_the_audio_node,_when_audio_file_from_the_previous_node_is_missing."/>
				<updated>2013-05-22T13:22:24Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing. ==&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| When a audio node is executed, the VXML broswer tries to fetch the audio file and simultaneously posts a HTTP request to the new document as well. In Response, the VXML Server returns the next VXMLDocument(which has TTS string to play). As a result the VXML browser gets a badfetch from the Media Server and sends a POST HTTP request with the errorType as bad.fetch to the VXML server.&lt;br /&gt;
Also,the HotEvent defined in the application for badfecth throws VXMLDocument(Error.wav) and results in the call being disconnected.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message/Symtom'''&lt;br /&gt;
| Hotevent document is not executed, and as a result call never drops as expected and goes on.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| The nature of the VXML browser is such that once the VXML document starts processing, it cannot be interrupted. This results in the VXML document being executed before the next node which will eventually drop the hotevent VXML document.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| Use a dummyObject which will halt the execution of the browser until object tag finishes. This ensures that the interpreter sends 404 badfetch in the POST request and will process the Hotevent instead of the next node.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| CVP 8.0 ESxx. onwards&lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCug77989. For more information on dummyObject,VXML syntax, see the attachements in CDETS. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/VXML_Server:_VXML_browser_cannot_stop_the_execution_of_the_audio_node,_when_audio_file_from_the_previous_node_is_missing.</id>
		<title>VXML Server: VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing.</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/VXML_Server:_VXML_browser_cannot_stop_the_execution_of_the_audio_node,_when_audio_file_from_the_previous_node_is_missing."/>
				<updated>2013-05-22T13:20:48Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: Created page with &amp;quot;== VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing. ==  {| border=&amp;quot;1&amp;quot; |- ! '''Problem Summary''' | When a audio node i...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== VXML browser cannot stop the execution of the audio node, when audio file from the previous node is missing. ==&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| When a audio node is executed, the VXMLBroswer tries to fetch the audio file and simultaneously POST a HTTP request to the new document as well. In Response the VXML Server returns the next VXMLDocument(which has TTS string to play). As a result VXML browser gets a badfetch from the Media Server and sends a POST HTTP request with the errorType as bad.fetch to VXML server.&lt;br /&gt;
Also,the HotEvent defined in the application for badfecth throws VXMLDocument(Error.wav) and results in the call being disconnected.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message/Symtom'''&lt;br /&gt;
| Hotevent document is not executed, and as a result call never drops as expected and goes on.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| The nature of the VXML browser is such that once the VXML document starts processing, it cannot be interrupted. This results in the VXML document being executed before the next node which will eventually drop the hotevent VXML document.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| Use a dummyObject which will halt the execution of the browser until object tag finishes. This ensures that the interpreter sends 404 badfetch in the POST request and will process the Hotevent instead of the next node.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| CVP 8.0 ESxx. onwards&lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCug77989. For more information on dummyObject,VXML syntax, see the attachements in CDETS. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/UC_Virtualization_Storage_System_Design_Requirements</id>
		<title>UC Virtualization Storage System Design Requirements</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/UC_Virtualization_Storage_System_Design_Requirements"/>
				<updated>2013-05-13T17:32:17Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Cisco Customer Voice Portal (Windows 2008 R2 Server)&amp;amp;nbsp; */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Go to: [[Before You Buy or Deploy - Considerations for Design and Procurement]]'''&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== General Guidelines for SAN/NAS  ==&lt;br /&gt;
&lt;br /&gt;
*Adapters for storage access must follow supported hardware rules ([[UC Virtualization Supported Hardware#IO_Adapters.2C_Controllers_and_Devices_for_LAN_Access_and_Storage_Access|click here]]). &lt;br /&gt;
*Cisco UC apps use a 4 kilobyte block size to determine bandwidth needs. &lt;br /&gt;
*Design your deployment in accordance with the UCS High Availability guidelines (see [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html]). &lt;br /&gt;
*10GbE networks for NFS, FCoE or iSCSI storage access should be configured using [http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/Virtualization/securecldg.html Cisco Platinum Class QOS] for the storage traffic. &lt;br /&gt;
*Ethernet ports for LAN access and ethernet ports for storage access may be separate or shared. Separate ports may be desired for redundancy purposes. It is the customer's responsibility to ensure external LAN and storage access networks meet [[UC Virtualization Supported Hardware#Storage|UC app latency, performance and capacity requirements]]. &lt;br /&gt;
*In absence of UCS 6100/6200, normal QoS (L3 and L2 marking) can be used starting from the first upstream switch to the storage array. &lt;br /&gt;
*With UCS 6100/6200 &lt;br /&gt;
**FC or FCoE: no additional requirements. Automatically handled by Fabric Interconnect switch. &lt;br /&gt;
**iSCSI or NFS: Follow these best practices: &lt;br /&gt;
***Use a L2 CoS between the chassis and the upstream switch. &lt;br /&gt;
***For the storage traffic, recommend a [http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/Virtualization/securecldg.html Platinum class QoS, CoS=5, no drop (Fiber Channel Equivalent)] &lt;br /&gt;
***L3 DSCP is optional between the chassis and the first upstream switch. &lt;br /&gt;
***From the first upstream switch to the storage array, use the normal QoS (L3 and L2 marking). Note that iSCSI or NFS traffic is typically assigned a separate VLAN. &lt;br /&gt;
***iSCSI or NFS:&amp;amp;nbsp;Ensure that the traffic is prioritized to provide the right IOPS. For a configuration example, see the FlexPod Secure Multi-Tenant (SMT) documentation&amp;amp;nbsp; ([http://www.imaginevirtuallyanything.com/us/ http://www.imaginevirtuallyanything.com/us/]). &lt;br /&gt;
*The storage array vendor may have additional best practices as well. &lt;br /&gt;
*If disk oversubscription or storage thin provisioning are used, note that UC apps are designed to use 100% of their allocated vDisk, either for UC features (such as Unity Connection message store or Contact Center reporting databases) or critical operations (such as spikes during upgrades, backups or statistics writes). While thin provisioning does not introduce a performance penalty, not having physical disk space available when the app needs it can have the following harmful effects &lt;br /&gt;
**degrade UC app performance, crash the UC app and/or corrupt the vDisk contents. &lt;br /&gt;
**lock up all UC VMs on the same LUN in a SAN&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== SAN/NAS Link Provisioning and High Availability  ==&lt;br /&gt;
&lt;br /&gt;
Consider the following example to determine the number of physical Fiber Channel (FC) or 10Gig Ethernet links required between your storage array (such as the EMC Clariion CX4 series or NetApp FAS 3000 Series) and SAN switch for example, Nexus or MDS Series SAN Switches), and between your SAN switch and the UCS Fabric Interconnect Switch. This example is presented to give a general idea of the design considerations involved. You should contact your storage vendor to determine the exact requirement. &lt;br /&gt;
&lt;br /&gt;
Assume that the storage array has a total capacity of 28,000 Input/output Operations Per Second (IOPS). Enterprise grade SAN Storage Arrays have at least two service processors (SPs) or controllers for redundancy and load balancing. That means 14,000 IOPS per controller or service processor. With the capacity of 28,000 IOPS, and assuming a 4 KByte block size, we can calculate the throughput per storage array controller as follows: &lt;br /&gt;
&lt;br /&gt;
*14,000 I/O per second * (4000 Byte block size * 8) bits = 448,000,000 bits per second &lt;br /&gt;
*448,000,000/1024 = 437,500 Kbits per second &lt;br /&gt;
*437,500/1024 = ~428 Mbits per second&lt;br /&gt;
&lt;br /&gt;
Adding more overhead, one controller can support a throughput rate of roughly 600 Mbps. Based on this calculation, it is clear that a 4 Gbps FC interface is enough to handle the entire capacity of one Storage Array. Therefore, Cisco recommends putting four FC interfaces between the storage array and storage switch, as shown in the following image, to provide high availability. &lt;br /&gt;
&lt;br /&gt;
[[Image:254783.jpg]] &lt;br /&gt;
&lt;br /&gt;
{{note| Cisco provides storage networking and switching products that are based on industry standards and that work with storage array providers such as EMC, NetApp, and so forth. Virtualized Unified Communications is supported on any storage access and storage array products that are supported by Cisco UCS and VMware. For more details on storage networking, see [http://www.cisco.com/en/US/netsol/ns747/networking_solutions_sub_program_home.html http://www.cisco.com/en/US/netsol/ns747/networking_solutions_sub_program_home.html].}}&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Best Practices for Storage Array LUNs for Unified Communications Applications  ==&lt;br /&gt;
&lt;br /&gt;
There are various ways to create partitions or Logical Unit Numbers (LUNs) in the storage array to meet the IOPS requirement for Cisco Unified Communications applications (see [[IO Operations Per Second (IOPS)]]}. &lt;br /&gt;
&lt;br /&gt;
The best practices mentioned below are meant only to provide guidelines. Data Center storage administrators should carefully consider these best practices and adjust them based on their specific data center network, latency, and high availability requirements. &lt;br /&gt;
&lt;br /&gt;
The storage array Hard Disk Drive (HDD) must be a Fibre Channel (FC) class HDD. These hard drives could vary in size. The current most popular HDD (spindle) sizes are: &lt;br /&gt;
&lt;br /&gt;
*450 GB, 15K revolutions per minute (RPM) FC HDD &lt;br /&gt;
*300 GB, 15K RPM FC HDD&lt;br /&gt;
&lt;br /&gt;
Both types of HDD provide approximately 180 IOPS. Regardless of the hard drive size used, it is important to try to balance IOPS load and disk space usage. &lt;br /&gt;
&lt;br /&gt;
LUN size must be less than 2 terabytes (TB) for the virtual machine file system to recognize it. For Cisco Unified Communications virtual applications, the recommendation is to create a LUN size of between 500 GB and 1.5 TB, depending on the size of the disk and RAID group type used. Also as a best practice, select the LUN size so that the number of Unified Communications virtual machines per LUN is between 4 and 8. Do not allocate more than eight virtual machines (VMs) per LUN or datastore. The total size of all Virtual Machines (where total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore. &lt;br /&gt;
&lt;br /&gt;
LUN filesystem type must be VMFS. Raw Device Mapping (RDM) is not supported. &lt;br /&gt;
&lt;br /&gt;
The following example illustrates an example of these best practices for UC: &lt;br /&gt;
&lt;br /&gt;
For example, assume RAID5 (4+1) is selected for a storage array containing five 450 GB, 15K RPM drives (HDDs) in a single RAID group. This creates a total RAID5 array size of approximately 1.4 TB usable space. This is lower than the total aggregate disk drive storage space provided by the five 450 GB drives (2.25 TB). This is to be expected because some of the drive space will be used for array creation and almost an entire drive of data will be used for RAID5 striping. &lt;br /&gt;
&lt;br /&gt;
Next, assume two LUNs of approximately 720 GB each are created to store Unified Communications application virtual machines. For this example, between one and three LUNs per RAID group could be created based on need. Creating more than three LUNs per RAID group would violate the previously mentioned recommendation of a LUN size of between 500 GB and 1.5 TB. &lt;br /&gt;
&lt;br /&gt;
A RAID group with RAID 1+0 scheme would also be valid for this example and in fact in some cases could provide better IOPS performance and high availability when compared to a RAID 5 scheme. &lt;br /&gt;
&lt;br /&gt;
The above example of storage array design should be altered based on your specific Unified Communications application IOPS requirements. &lt;br /&gt;
&lt;br /&gt;
Below is a graphic of an example configuration following these best practices guidelines, note there are other designs possible. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Image:Docwiki SAN best practices.png]]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= IOPS and other Performance Requirements  =&lt;br /&gt;
&lt;br /&gt;
This page illustrates IOPS under various conditions for Unified Communications applications. This area is under construction. Check back frequently for updates. &lt;br /&gt;
&lt;br /&gt;
Storage performance must support the sum of UC VM OVA IOPS. Note that addressing IOPS requirements may require higher disk/spindle counts, which may result in excess storage capacity &lt;br /&gt;
&lt;br /&gt;
IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability. &lt;br /&gt;
&lt;br /&gt;
== Unified Communications Manager  ==&lt;br /&gt;
&lt;br /&gt;
This section provides the IOPS data for a Cisco Unified Communications Manager system under load. These values are per active VM OVA. Which VM OVAs are active, and how many are active simultaneously, depends on how the CUCM cluster nodes are setup with respect to service activation, redundancy groups, etc. (see www.cisco.com/go/ucsrnd for details). &lt;br /&gt;
&lt;br /&gt;
CUCM storage access is on average 93-98% sequential writes with an IO block size of 4 kilobytes. &lt;br /&gt;
&lt;br /&gt;
*Active call processing: As a reference, the following steady state IOPS were observed at various loads (expressed in Busy Hour Call Attempts):&lt;br /&gt;
&lt;br /&gt;
::*10K BHCA produces ~ 35 IOPS &lt;br /&gt;
::*25K BHCA produces ~ 50 IOPS &lt;br /&gt;
::*50K BHCA produces ~ 100 IOPS &lt;br /&gt;
::*100K BHCA produces ~ 150 IOPS&lt;br /&gt;
&lt;br /&gt;
*Software upgrades during business hours generate 800 to 1200 IOPS in addition to steady state IOPS. &lt;br /&gt;
*CDR/CMR via CDR Analysis and Reporting (CAR) &lt;br /&gt;
**CUCM sending CDR/CMR to the external billing server does not incur any additional IOPS. &lt;br /&gt;
**Enabling CAR continuous loading results in around 300 IOPS average on the system. &lt;br /&gt;
**Scheduled uploads are around 250 IOPS for Publisher's VM only. &lt;br /&gt;
*Trace collection is 100 IOPS (occurs on all VMs for which tracing is enabled). &lt;br /&gt;
*Nightly backup (usually Publisher's VM only) is 50 IOPS.&lt;br /&gt;
&lt;br /&gt;
== Cisco Emergency Responder  ==&lt;br /&gt;
&lt;br /&gt;
This section provides the IOPS Data for a Cisco Emergency Responder System under Load. These tests use published OVA template for Cisco Emergency Responder. &lt;br /&gt;
&lt;br /&gt;
*'''Major Discovery''': IOPS value of 66.&lt;br /&gt;
&lt;br /&gt;
*'''Export/Import''': IOPS value of 325. &lt;br /&gt;
*'''DRS Backup/Restore''': During a backup, the value is 29; during a restore, it reaches 1000 IOPS. &lt;br /&gt;
*'''Upgrade''': IOPS Value of 4.5.&lt;br /&gt;
&lt;br /&gt;
== Cisco Intercompany Media Engine  ==&lt;br /&gt;
&lt;br /&gt;
Use values for Cisco Unified Communications Manager above (they will be conservatively high). &lt;br /&gt;
&lt;br /&gt;
== Cisco Unity Connection  ==&lt;br /&gt;
&lt;br /&gt;
=== Summary of IOPS for Unity Connection  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align: center; width: 75%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! IOPS Type &lt;br /&gt;
! 1vCPU &lt;br /&gt;
! 2vCPU &lt;br /&gt;
! 4vCPU &lt;br /&gt;
! 7vCPU&lt;br /&gt;
|-&lt;br /&gt;
| Avg Total &lt;br /&gt;
| 78.66 &lt;br /&gt;
| 129.01 &lt;br /&gt;
| 217.89 &lt;br /&gt;
| 201.73&lt;br /&gt;
|-&lt;br /&gt;
| Peak Total &lt;br /&gt;
| 760.99 &lt;br /&gt;
| 714.06 &lt;br /&gt;
| 867.88 &lt;br /&gt;
| 773.70&lt;br /&gt;
|-&lt;br /&gt;
| Avg Read &lt;br /&gt;
| 5.90 &lt;br /&gt;
| 19.60 &lt;br /&gt;
| 45.67 &lt;br /&gt;
| 9.53&lt;br /&gt;
|-&lt;br /&gt;
| Peak Read &lt;br /&gt;
| 601.84 &lt;br /&gt;
| 469.46 &lt;br /&gt;
| 693.21 &lt;br /&gt;
| 526.22&lt;br /&gt;
|-&lt;br /&gt;
| Avg Write &lt;br /&gt;
| 72.77 &lt;br /&gt;
| 109.40 &lt;br /&gt;
| 172.22 &lt;br /&gt;
| 192.20&lt;br /&gt;
|-&lt;br /&gt;
| Peak Write &lt;br /&gt;
| 247.14 &lt;br /&gt;
| 293.51 &lt;br /&gt;
| 371.97 &lt;br /&gt;
| 413.50&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== TelePresence Applications  ==&lt;br /&gt;
&lt;br /&gt;
For Cisco TelePresence Manager and Cisco TelePresence Multipoint Switch: 100 IOPS is a good typical value to plan around. Otherwise use values for Cisco Unified Communications Manager above (they will be conservatively high). &lt;br /&gt;
&lt;br /&gt;
=== Cisco TelePresence Video Communication Server (Cisco VCS)&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
This section provides the IOPS data for a Cisco VCS system under load.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The recommended hardware on which to run a Cisco VCS VM is Cisco UCS C200 – M2, UCS C210 – M2, UCS C220 M3, or UCS B200 – M2 with:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Processor supporting AESNI feature &lt;br /&gt;
*6GB of RAM per VM &lt;br /&gt;
*132GB disk space per VM (for a 4GB virtual disk 1 and a 128GB virtual disk 2) &lt;br /&gt;
*R2XX-LBBU (Raid disk battery backup to enable cache) &lt;br /&gt;
*Four hard disks (450GB SAS 15K RPM 3.5in HDD/hot plug/C200 drive sled) &lt;br /&gt;
*PCI card Intel Quad port GbE Controller (E1G44ETG1P20)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Test specifications:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Four individual Cisco VCS VMs running X7.2 &lt;br /&gt;
*Single C220 M3 TRC running ESXi 5.0.0 (update 1)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Test results:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;754&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Activity&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Average IOPS&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Average r/w latency&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Peak read latency&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Peak write latency&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Performance test*&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 5&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 0.5ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 15ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 2ms&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Software upgrade&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 35&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 5ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 300ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 160ms&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Core dump&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 40&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 10ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 100ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 10ms&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Burnin test suite&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 35&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 50ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 400ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 60ms&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Performance test comprised 100 simultaneous interworked and encrypted calls at 768kbp/s&lt;br /&gt;
&lt;br /&gt;
Note that Cisco VCS software X7.2 and later takes advantage of AES acceleration on Intel Advanced Encryption Standard New Instruction set available on the Cisco C2xx family of servers. This provides enhanced performance for encrypted calls.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Cisco TelePresence Conductor (TelePresence Conductor)  ===&lt;br /&gt;
&lt;br /&gt;
This section provides the IOPS data for a TelePresence Conductor system under load. &lt;br /&gt;
&lt;br /&gt;
The recommended hardware on which to run a TelePresence Conductor VM is Cisco UCS C200 – M2, UCS C210 – M2, UCS C220 M3, or UCS B200 – M2 with:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Processor supporting AESNI feature &lt;br /&gt;
*6GB of RAM per VM &lt;br /&gt;
*132GB disk space per VM (for a 4GB virtual disk 1 and a 128GB virtual disk 2) &lt;br /&gt;
*R2XX-LBBU (Raid disk battery backup to enable cache) &lt;br /&gt;
*Four hard disks (450GB SAS 15K RPM 3.5in HDD/hot plug/C200 drive sled) &lt;br /&gt;
*PCI card Intel Quad port GbE Controller (E1G44ETG1P20)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Test specifications:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Four individual TelePresence Conductor VMs running XC1.2 &lt;br /&gt;
*Single C220 M3 TRC running ESXi 5.0.0 (update 1)&lt;br /&gt;
&lt;br /&gt;
Test results: &lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;754&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Activity&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Average IOPS&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Average r/w latency&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Peak read latency&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Peak write latency&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Performance test*&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 5&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 0.5ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 15ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 2ms&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Software upgrade&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 35&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 5ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 300ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 160ms&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Core dump&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 40&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 10ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 100ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 10ms&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | Burnin test suite&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 35&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 50ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 400ms&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 60ms&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Performance test comprised 2400 endpoints, 15 calls per second, 30 MCUs, 2 person conference&lt;br /&gt;
&lt;br /&gt;
== Unified Presence  ==&lt;br /&gt;
&lt;br /&gt;
The CUP 1000 user OVA generates about 60 IOPS during steady-state. Expect similar peaks as CUCM during backups and upgrades. &lt;br /&gt;
&lt;br /&gt;
== Cisco Unified Attendant Consoles  ==&lt;br /&gt;
&lt;br /&gt;
This section provides the IOPS data for Cisco Unified Attendant Consoles (using Enterprise Attendant Console to produce heaviest load). Load test and average operations are represented. These tests use the published OVA&amp;amp;nbsp;template for Cisco Unified Attendant Consoles. &lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;1172&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; bgcolor=&amp;quot;#cccccc&amp;quot; align=&amp;quot;center&amp;quot; colspan=&amp;quot;9&amp;quot; | '''LOAD TESTING'''&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; | '''IOPS (Read)''' &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; | '''IOPS (Write)''' &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Min''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Max''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Average''' &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Min''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Max''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Average''' &lt;br /&gt;
| '''Operating Conditions'''&lt;br /&gt;
|-&lt;br /&gt;
| Cisco Unified Attendant Console Server &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 1013.605 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0.442 &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 1112.87 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 12.121 &lt;br /&gt;
| 5,000 calls per hour, 25 concurrent operators, continuous LDAP&amp;amp;nbsp;sync, full logging&lt;br /&gt;
|-&lt;br /&gt;
| Upgrade &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 320.006 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 3.691 &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 105.001 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 10.341 &lt;br /&gt;
| Major upgrade&lt;br /&gt;
|-&lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; bgcolor=&amp;quot;#cccccc&amp;quot; align=&amp;quot;center&amp;quot; colspan=&amp;quot;9&amp;quot; | '''AVERAGE OPERATIONS'''&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; | '''IOPS (Read)''' &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; | '''IOPS (Write)''' &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Min''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Max''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Average''' &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Min''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Max''' &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | '''Average''' &lt;br /&gt;
| '''Operating Conditions'''&lt;br /&gt;
|-&lt;br /&gt;
| Cisco Unified Attendant Console Server &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 11.6 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0.092 &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 561.05 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 10.82 &lt;br /&gt;
| Synchronized directory, cached BLF, minimum online changes&lt;br /&gt;
|-&lt;br /&gt;
| Upgrade &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 107.001 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 5.751 &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 0 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 50 &lt;br /&gt;
| valign=&amp;quot;middle&amp;quot; align=&amp;quot;center&amp;quot; | 3.57 &lt;br /&gt;
| Minor upgrade&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Cisco Customer Collaboration/Contact Center  ==&lt;br /&gt;
&lt;br /&gt;
=== [[Virtualization for Unified CCE|Cisco Contact Center Enterprise]]&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
The SAN must be able to handle the following Unified CCE application disk I/O characteristics. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
The data below is based on CCE 8.5(3) running on '''Windows Server 2008 R2&amp;amp;nbsp;Enterprise''' &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;1164&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot; style=&amp;quot;width: 1164px; height: 87px&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot; | '''Unified CCE Component''' &lt;br /&gt;
| colspan=&amp;quot;3&amp;quot; | '''IOPS''' &lt;br /&gt;
| colspan=&amp;quot;3&amp;quot; | '''Disk Read KBytes / sec''' &lt;br /&gt;
| colspan=&amp;quot;3&amp;quot; | '''Disk Write KBytes / sec''' &lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot; | '''Operating Conditions'''&lt;br /&gt;
|-&lt;br /&gt;
| '''Peak''' &lt;br /&gt;
| '''Avg.''' &lt;br /&gt;
| '''95th Pct''' &lt;br /&gt;
| '''Peak''' &lt;br /&gt;
| '''Avg.''' &lt;br /&gt;
| '''95th Pct''' &lt;br /&gt;
| '''Peak''' &lt;br /&gt;
| '''Avg.''' &lt;br /&gt;
| '''95th Pct.'''&lt;br /&gt;
|-&lt;br /&gt;
| Router &lt;br /&gt;
| 27 &lt;br /&gt;
| 14 &lt;br /&gt;
| 19 &lt;br /&gt;
| 619 &lt;br /&gt;
| 11 &lt;br /&gt;
| 12 &lt;br /&gt;
| 436 &lt;br /&gt;
| 246 &lt;br /&gt;
| 313 &lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | 12,000 agent;100 CPS, ECC: 5 scalars @ 40 bytes each; 200 Reporting users at max query load&lt;br /&gt;
|-&lt;br /&gt;
| Logger &lt;br /&gt;
| 3662 &lt;br /&gt;
| 917 &lt;br /&gt;
| 1793 &lt;br /&gt;
| 12821 &lt;br /&gt;
| 735 &lt;br /&gt;
| 11571 &lt;br /&gt;
| 38043 &lt;br /&gt;
| 2777 &lt;br /&gt;
| 11832&lt;br /&gt;
|-&lt;br /&gt;
| HDS &lt;br /&gt;
| 1017 &lt;br /&gt;
| 321 &lt;br /&gt;
| 693 &lt;br /&gt;
| 2748 &lt;br /&gt;
| 250 &lt;br /&gt;
| 2368 &lt;br /&gt;
| 19351 &lt;br /&gt;
| 1441 &lt;br /&gt;
| 3879&lt;br /&gt;
|-&lt;br /&gt;
| Router &lt;br /&gt;
| 118 &lt;br /&gt;
| 11 &lt;br /&gt;
| 13 &lt;br /&gt;
| 1681 &lt;br /&gt;
| 14 &lt;br /&gt;
| 5 &lt;br /&gt;
| 971 &lt;br /&gt;
| 66 &lt;br /&gt;
| 172 &lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | 8,000 agents;60 CPS; ECC:5 scalars @ 40 bytes each; 200 Reporting users at max query load&lt;br /&gt;
|-&lt;br /&gt;
| Logger &lt;br /&gt;
| 1614 &lt;br /&gt;
| 502 &lt;br /&gt;
| 1065 &lt;br /&gt;
| 6137 &lt;br /&gt;
| 341 &lt;br /&gt;
| 4993 &lt;br /&gt;
| 30379 &lt;br /&gt;
| 558 &lt;br /&gt;
| 5911&lt;br /&gt;
|-&lt;br /&gt;
| HDS &lt;br /&gt;
| 1395 &lt;br /&gt;
| 165 &lt;br /&gt;
| 541 &lt;br /&gt;
| 1995 &lt;br /&gt;
| 186 &lt;br /&gt;
| 1776 &lt;br /&gt;
| 12525 &lt;br /&gt;
| 1299 &lt;br /&gt;
| 2965&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The data below is based on CCE 8.0(2) running on '''Windows Server 2003 R2''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; | Unified CCE Component &lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; | IOPS &lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; | Disk Read KBytes / sec &lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; | Disk Write KBytes / sec &lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; | Operating Conditions&lt;br /&gt;
|-&lt;br /&gt;
| '''Peak''' &lt;br /&gt;
| '''Avg.''' &lt;br /&gt;
| '''95th Pct.''' &lt;br /&gt;
| '''Peak''' &lt;br /&gt;
| '''Avg.''' &lt;br /&gt;
| '''95th Pct.''' &lt;br /&gt;
| '''Peak''' &lt;br /&gt;
| '''Avg.''' &lt;br /&gt;
| '''95th Pct.''' &lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Router &lt;br /&gt;
| 20 &lt;br /&gt;
| 8 &lt;br /&gt;
| 10 &lt;br /&gt;
| 520 &lt;br /&gt;
| 30 &lt;br /&gt;
| 180 &lt;br /&gt;
| 400 &lt;br /&gt;
| 60 &lt;br /&gt;
| 150 &lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | 8,000 agents; 60 cps; ECC: 5 scalars @ 35 bytes each; No reporting.&lt;br /&gt;
|-&lt;br /&gt;
| Logger &lt;br /&gt;
| 1,000 &lt;br /&gt;
| 600 &lt;br /&gt;
| 700 &lt;br /&gt;
| 4,000 &lt;br /&gt;
| 600 &lt;br /&gt;
| 2,500 &lt;br /&gt;
| 12,000 &lt;br /&gt;
| 3,000 &lt;br /&gt;
| 7,000&lt;br /&gt;
|-&lt;br /&gt;
| HDS &lt;br /&gt;
| 1,600 &lt;br /&gt;
| 1,000 &lt;br /&gt;
| 1,100 &lt;br /&gt;
| 600 &lt;br /&gt;
| 70 &lt;br /&gt;
| 400 &lt;br /&gt;
| 6,000 &lt;br /&gt;
| 2,000 &lt;br /&gt;
| 3,800&lt;br /&gt;
|-&lt;br /&gt;
| Agent PG &lt;br /&gt;
| 125 &lt;br /&gt;
| 40 &lt;br /&gt;
| 70 &lt;br /&gt;
| 300 &lt;br /&gt;
| 5 &lt;br /&gt;
| 20 &lt;br /&gt;
| 2,000 &lt;br /&gt;
| 1,200 &lt;br /&gt;
| 1,500 &lt;br /&gt;
| 2,000 agents, 15 cps &lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| HDS &lt;br /&gt;
| 3,900 &lt;br /&gt;
| 2,500 &lt;br /&gt;
| 3,800 &lt;br /&gt;
| 75,000 &lt;br /&gt;
| 30,000 &lt;br /&gt;
| 50,000 &lt;br /&gt;
| 9,500 &lt;br /&gt;
| 2,200 &lt;br /&gt;
| 5,800 &lt;br /&gt;
| 8,000 agents; 60 cps; 200 reporting users at max query load; ECC: 5 scalars @ 35 bytes each.&lt;br /&gt;
|-&lt;br /&gt;
| ROGGER &lt;br /&gt;
| 610 &lt;br /&gt;
| 360 &lt;br /&gt;
| 425 &lt;br /&gt;
| 2,700 &lt;br /&gt;
| 400 &lt;br /&gt;
| 1,600 &lt;br /&gt;
| 7,500 &lt;br /&gt;
| 2,150 &lt;br /&gt;
| 4,300 &lt;br /&gt;
| 4,000 agents; 30 cps; ECC: 5 scalars @ 35 bytes each&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== [[Virtualization for Unified CCX|Cisco Contact Center Express/IPIVR IOPS]]  ===&lt;br /&gt;
&lt;br /&gt;
The following table lists the IOPS numbers for Unified Contact Center Express/IPIVR. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! IOPS Type &lt;br /&gt;
! 2vCPU&lt;br /&gt;
|-&lt;br /&gt;
| IOPS Avg per VM &lt;br /&gt;
| 150&lt;br /&gt;
|-&lt;br /&gt;
| IOPS Max spike per VM &lt;br /&gt;
| 1500&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== [[Virtualization for Unified CCX|Workforce Optimization (WFO) IOPS]]  ===&lt;br /&gt;
&lt;br /&gt;
The following table lists the IOPS numbers for Cisco Unified Workforce Optimization 8.5(2) onward.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;650&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| '''Workforce Optimization Component''' &lt;br /&gt;
| '''IOPS (Read''') &lt;br /&gt;
| '''IOPS (Write)''' &lt;br /&gt;
| '''Operating Conditions'''&lt;br /&gt;
|-&lt;br /&gt;
| QM 8.5(2+) Base Server &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 4 &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 2 &lt;br /&gt;
| Idle&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 4 &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 12 &lt;br /&gt;
| Recording 300 concurrent calls&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 11 &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 38 &lt;br /&gt;
| During recording upload&lt;br /&gt;
|-&lt;br /&gt;
| QM 8.5(2+) Recording Server or WFM 8.5(2+) &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 1 &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 2 &lt;br /&gt;
| Idle&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 74 &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 187 &lt;br /&gt;
| Recording 300 concurrent calls&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 102 &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | 71 &lt;br /&gt;
| During recording upload&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== [[Virtualization for Cisco MediaSense|Cisco MediaSense]]  ===&lt;br /&gt;
&lt;br /&gt;
The following table lists the IOPS numbers for Cisco MediaSense partitions. &lt;br /&gt;
&lt;br /&gt;
{| cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot; style=&amp;quot;width: 513px; height: 228px&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Media Partitions&amp;lt;br&amp;gt; &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | IOPS Specifications&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
Average IOPS for non-media partitions &lt;br /&gt;
&lt;br /&gt;
| 1700 ops/sec&lt;br /&gt;
|-&lt;br /&gt;
| Average IOPS for media partitions &lt;br /&gt;
| 50 ops/sec&lt;br /&gt;
|-&lt;br /&gt;
| Average bandwidth for non-media partitions &lt;br /&gt;
| 7300 kbytes/sec&lt;br /&gt;
|-&lt;br /&gt;
| Average bandwidth for media partitions &lt;br /&gt;
| 1000 kbytes/sec&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== [[Virtualization for Cisco Finesse|Cisco Finesse]]&amp;amp;nbsp;  ===&lt;br /&gt;
&lt;br /&gt;
The following table lists the IOPS numbers for Cisco Finesse. &lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;300&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| '''IOPS Type''' &lt;br /&gt;
| '''IOPS Specification'''&lt;br /&gt;
|-&lt;br /&gt;
| width=&amp;quot;125&amp;quot; | Max IOPS &lt;br /&gt;
| 160&lt;br /&gt;
|-&lt;br /&gt;
| 95th percentile &lt;br /&gt;
| 150&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager Cisco Unfied Email Interaction Manager and Web Interaction Manager]  ===&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;800&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot; | EIM-WIM component &lt;br /&gt;
| colspan=&amp;quot;3&amp;quot; | IOPS &lt;br /&gt;
| colspan=&amp;quot;3&amp;quot; | Disk Read KBytes / sec &lt;br /&gt;
| colspan=&amp;quot;3&amp;quot; | Disk Write KBytes / sec&lt;br /&gt;
|-&lt;br /&gt;
| Peak &lt;br /&gt;
| 95th Pct. &lt;br /&gt;
| Avg. &lt;br /&gt;
| Peak &lt;br /&gt;
| 95th Pct. &lt;br /&gt;
| Avg. &lt;br /&gt;
| Peak &lt;br /&gt;
| 95th Pct. &lt;br /&gt;
| Avg.&lt;br /&gt;
|-&lt;br /&gt;
| Application Server &lt;br /&gt;
| 11.7 &lt;br /&gt;
| 3.21 &lt;br /&gt;
| 1.55 &lt;br /&gt;
| 51 &lt;br /&gt;
| 1 &lt;br /&gt;
| 0.726 &lt;br /&gt;
| 103 &lt;br /&gt;
| 19 &lt;br /&gt;
| 8.32&lt;br /&gt;
|-&lt;br /&gt;
| File Server &lt;br /&gt;
| 43.65 &lt;br /&gt;
| 25.23 &lt;br /&gt;
| 14.36 &lt;br /&gt;
| 189 &lt;br /&gt;
| 2 &lt;br /&gt;
| 2 &lt;br /&gt;
| 1769 &lt;br /&gt;
| 1025.9 &lt;br /&gt;
| 446&lt;br /&gt;
|-&lt;br /&gt;
| Database Server &lt;br /&gt;
| 736.9 &lt;br /&gt;
| 552 &lt;br /&gt;
| 263.31 &lt;br /&gt;
| 35450 &lt;br /&gt;
| 23184 &lt;br /&gt;
| 3903 &lt;br /&gt;
| 5737 &lt;br /&gt;
| 2872 &lt;br /&gt;
| 1625&lt;br /&gt;
|-&lt;br /&gt;
| Messaging Server &lt;br /&gt;
| 9.15 &lt;br /&gt;
| 2.71 &lt;br /&gt;
| 1.47 &lt;br /&gt;
| 57 &lt;br /&gt;
| 1 &lt;br /&gt;
| 0.7 &lt;br /&gt;
| 88 &lt;br /&gt;
| 15.1 &lt;br /&gt;
| 8&lt;br /&gt;
|-&lt;br /&gt;
| Services Server &lt;br /&gt;
| 11.15 &lt;br /&gt;
| 3.155 &lt;br /&gt;
| 1.53 &lt;br /&gt;
| 55 &lt;br /&gt;
| 1 &lt;br /&gt;
| 0.73 &lt;br /&gt;
| 1.89 &lt;br /&gt;
| 17 &lt;br /&gt;
| 9&lt;br /&gt;
|-&lt;br /&gt;
| Web Server &lt;br /&gt;
| 11.2 &lt;br /&gt;
| 3.36 &lt;br /&gt;
| 1.43 &lt;br /&gt;
| 55 &lt;br /&gt;
| 1 &lt;br /&gt;
| 0.8 &lt;br /&gt;
| 173 &lt;br /&gt;
| 21 &lt;br /&gt;
| 10.24&lt;br /&gt;
|-&lt;br /&gt;
| Cisco Media Blender &lt;br /&gt;
| 12.25 &lt;br /&gt;
| 7.45 &lt;br /&gt;
| 5.51 &lt;br /&gt;
| 47 &lt;br /&gt;
| 0 &lt;br /&gt;
| 0.516 &lt;br /&gt;
| 384 &lt;br /&gt;
| 289 &lt;br /&gt;
| 177.47&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== [http://docwiki-dev.cisco.com/wiki/Cisco_Unified_Intelligence_Center Cisco Unified Intelligence Center]  ===&lt;br /&gt;
&lt;br /&gt;
*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. &lt;br /&gt;
*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs. &lt;br /&gt;
*VM snapshots are not supported in production since they have significant impact on system performance. &lt;br /&gt;
*The SAN must be able to handle the following Cisco Unified Intelligence Center application disk I/O characteristics. &lt;br /&gt;
*Enable hyper threading on all ESXi servers. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The following table lists the IOPS numbers for Cisco Unified Intelligence Center.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
{| cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot; style=&amp;quot;width: 439px; height: 129px&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Details&amp;lt;br&amp;gt; &lt;br /&gt;
| Write (Kilobytes/Sec) &amp;lt;br&amp;gt; &lt;br /&gt;
| Read (Kilobytes/Sec) &amp;lt;br&amp;gt; &lt;br /&gt;
| IOPS &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Maximum &amp;lt;br&amp;gt; &lt;br /&gt;
| 7758.00&amp;lt;br&amp;gt; &lt;br /&gt;
| 466.00 &amp;lt;br&amp;gt; &lt;br /&gt;
| 781.40 &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 95 Percentile &amp;lt;br&amp;gt; &lt;br /&gt;
| 6446.30 &amp;lt;br&amp;gt; &lt;br /&gt;
| 433.10 &amp;lt;br&amp;gt; &lt;br /&gt;
| 628.34&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Average&amp;amp;nbsp; &amp;lt;br&amp;gt; &lt;br /&gt;
| 5727.44&amp;lt;br&amp;gt; &lt;br /&gt;
| 74.32&amp;lt;br&amp;gt; &lt;br /&gt;
| 460.17 &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Minimum&amp;amp;nbsp; &amp;lt;br&amp;gt; &lt;br /&gt;
| 4897.00&amp;lt;br&amp;gt; &lt;br /&gt;
| 0.00&amp;lt;br&amp;gt; &lt;br /&gt;
| 288.75 &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== [[Virtualization for Unified CVP|Cisco Customer Voice Portal (Windows 2003 R2 Server)]]&amp;amp;nbsp;  ===&lt;br /&gt;
&lt;br /&gt;
The following table lists the IOPS numbers for Cisco Unified Customer Voice Portal running on Windows 2003 R2 Server.&lt;br /&gt;
&lt;br /&gt;
'''IOPS Summary: (Unit in Number, Data are Blade-based)''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server component &lt;br /&gt;
! Average &lt;br /&gt;
! MAX &lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| Call Server/VXML Servers &lt;br /&gt;
| 380 &lt;br /&gt;
| 1536 &lt;br /&gt;
| 797&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 692 &lt;br /&gt;
| 3403 &lt;br /&gt;
| 2024&lt;br /&gt;
|-&lt;br /&gt;
| Operation Server &lt;br /&gt;
| NA (Insignificant) &lt;br /&gt;
| NA &lt;br /&gt;
| NA&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== [[Virtualization for Unified CVP|Cisco Customer Voice Portal (Windows 2008 R2 Server)]]&amp;amp;nbsp;  ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''IOPS Numbers''':&lt;br /&gt;
&lt;br /&gt;
The following section lists the IOPS numbers for Cisco Unified Customer Voice Portal running on Windows 2008 R2 Server.&lt;br /&gt;
&lt;br /&gt;
'''The following IOPS metrics are measured in peak load conditions with failover:'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX&lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML/Media Servers &lt;br /&gt;
| 50 &lt;br /&gt;
| 1300&lt;br /&gt;
| 124&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 329&lt;br /&gt;
| 1250 &lt;br /&gt;
| 984&lt;br /&gt;
|-&lt;br /&gt;
| Operations Console&lt;br /&gt;
| 22&lt;br /&gt;
| 100 &lt;br /&gt;
| 80&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''The following IOPS metrics are measured in peak load conditions with no failover:'''&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX&lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML/Media Servers &lt;br /&gt;
| 21 &lt;br /&gt;
| 450&lt;br /&gt;
| 30&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 40&lt;br /&gt;
| 930 &lt;br /&gt;
| 56&lt;br /&gt;
|-&lt;br /&gt;
| Operations Console&lt;br /&gt;
| 22&lt;br /&gt;
| 100 &lt;br /&gt;
| 80&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*'''Read/Write Ratio''':&lt;br /&gt;
&lt;br /&gt;
'''The following table provides Read/Write Ratio:'''&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server&lt;br /&gt;
! Average&lt;br /&gt;
! MAX&lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML/Media Servers &lt;br /&gt;
| 199/327 &lt;br /&gt;
| 2249/1654&lt;br /&gt;
| 411/928&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 3563/3000&lt;br /&gt;
| 14375/15390 &lt;br /&gt;
| 10010/11506&lt;br /&gt;
|-&lt;br /&gt;
| Operations Console&lt;br /&gt;
| 22/21&lt;br /&gt;
| 107/94&lt;br /&gt;
| 67/79&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color: rgb(255,215,0)&amp;quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP</id>
		<title>Virtualization for Unified CVP</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP"/>
				<updated>2013-05-13T17:27:35Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* VM IOPS Measurement */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Updates to this Page  ==&lt;br /&gt;
&lt;br /&gt;
The following is a list of significant updates to this page: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Date &lt;br /&gt;
! Update&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;24,&amp;amp;nbsp;2010 &lt;br /&gt;
| Distribution of Cisco UCS Unified CVP DocWiki for Tech review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;25,&amp;amp;nbsp;2010 &lt;br /&gt;
| Cleaned up IOPS tables, product naming conventions, section consistency with Unified CCE UCS wiki.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;26,&amp;amp;nbsp;2010 &lt;br /&gt;
| Validated links, performed spell check, noted areas still requiring additional technical review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;27,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following areas: Information for Partners, VMWare and Application Software Requirements, UCS Network Configuration, Configuring ESXi datastore.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;28,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following sections: Modified link to Information for Partners; Unified CVP 8.0(1) Support for Virtualization on the ESXi/UCS Platform (Modified bullet that referred to 'Distributed'; Coresidency (Deleted references to realtime; Modified last bullet regarding support on Blade.)&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;30,&amp;amp;nbsp;2010 &lt;br /&gt;
| Unified CVP Virtualization information posted to Unified Communications Virtualization Wiki.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;6,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated links to Unified CVP main page and CVP Reporting Server Configuration sub-page.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated Unified CVP Component Co-Residency section.&lt;br /&gt;
|-&lt;br /&gt;
| December&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated page to note that CVP 8.5(1) features the same level of support for virtualization that is available in CVP 8.0(1)&lt;br /&gt;
|-&lt;br /&gt;
| January&amp;amp;nbsp;12,&amp;amp;nbsp;2011 &lt;br /&gt;
| Added information on using CVP with C-Series servers.&lt;br /&gt;
|-&lt;br /&gt;
| September 1, 2011 &lt;br /&gt;
| Added support for ESXi 4.1.&lt;br /&gt;
|-&lt;br /&gt;
| February 6, 2012 &lt;br /&gt;
| Updated with the CVP support for TCP and UDP on UCS C-series servers.&lt;br /&gt;
|-&lt;br /&gt;
| July 6, 2012 &lt;br /&gt;
| Virtualization support for Release 9.0(1).&lt;br /&gt;
|-&lt;br /&gt;
| September 18, 2012 &lt;br /&gt;
| Unified CVP-Specific VM Installation Information&lt;br /&gt;
|-&lt;br /&gt;
| January 28, 2013&lt;br /&gt;
| CVP Media Server coresidency as general support.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==&lt;br /&gt;
&lt;br /&gt;
'''It is important that partners who are planning to sell UCS products on Unified Cisco Customer Voice Portal, read the [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise Unified CCE DocWiki] page.''' This page contains essential information for partners about the following: &lt;br /&gt;
&lt;br /&gt;
:*Partner Certification Requirements &lt;br /&gt;
:*UCS Server Ordering Information &lt;br /&gt;
:*Important Notes on Cisco UCS Service and Support&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
Starting with Release 9.0(1),all Unified CVP components can be deployed using the single OVA on any CVP supported virtulization hardware. Starting with Release 8.0(1), virtualization of the following deployments and Unified CVP components on Cisco Unified Communications Systems (UCS) B-Series hardware is supported: &lt;br /&gt;
&lt;br /&gt;
:*Unified CVP Call Server &lt;br /&gt;
:*Unified CVP VXML Server &lt;br /&gt;
:*Unified CVP Reporting Server &lt;br /&gt;
:*Unified CVP Ops Console&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following deployments and Unified CVP components have not been qualified and '''are not supported''' in virtualization: &lt;br /&gt;
&lt;br /&gt;
:*H323 Call flow Deployment &lt;br /&gt;
:*Distributed VXML Server and Call Server deployment where each server runs in a separate VM &lt;br /&gt;
:*All in one lab deployment with small reporting server&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following VMware features are not supported with Unified CVP: &lt;br /&gt;
&lt;br /&gt;
:*VMware Physical to Virtual migration &lt;br /&gt;
:*VMware Snapshots &lt;br /&gt;
:*VMware Consolidated Backup &lt;br /&gt;
:*VMware High Availability (HA) &lt;br /&gt;
:*VMware Site Recovery Manager &lt;br /&gt;
:*VMware vCenter Update Manager &lt;br /&gt;
:*VMware vCenter Converter&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Note: Unified CVP components are supported on the UCS platform only in a virtualized environment with ESXi server.''' &lt;br /&gt;
&lt;br /&gt;
== UCS Hardware Requirements  ==&lt;br /&gt;
&lt;br /&gt;
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located [[Unified Computing System Hardware#B-200_M1_Requirements|here]]. &lt;br /&gt;
&lt;br /&gt;
Requirements for C210 hardware are located in the [[Unified Computing System Hardware]]. For UCS C210, CVP supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210M2-VCD2]). Other supported UCS models are at [[Unified Communications Virtualization Supported Applications#Contact_Center_Applications|Unified Communications Supported Applications]] &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1. &lt;br /&gt;
&lt;br /&gt;
For Unified CVP to work on UCS server, UCS firmware has to be 1.4(3c) or later. &lt;br /&gt;
&lt;br /&gt;
== VMware and Application Software Requirements  ==&lt;br /&gt;
&lt;br /&gt;
The following software requirements apply specifically to Unified Customer Voice Portal: &lt;br /&gt;
&lt;br /&gt;
:*VMware ESXi 4.1/5.0, minimum version 4.0U1. Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported. See [[Unified Communications VMware Requirements#VMware_vSphere_ESXi_Version_Support_for_Contact_Center_Applications|Unified Communications VMware requirements]] for a summary and further information. &lt;br /&gt;
:*You need to [[Disable LRO|disable LRO]] for ESXi 4.1/5.0. See [[Implementing Virtualization Deployments]] for more information. &lt;br /&gt;
:*The Windows, Informix, and other third party software requirements for the Unified CVP applications in the ESXi/UCS platform are the same as in the physical server. For such information, refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf Hardware and System Software Specification for Cisco Unified Customer Voice Portal, Release 8.5(1)]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP-Specific VM Installation Information  ==&lt;br /&gt;
&lt;br /&gt;
=== Migrating to Unified CVP Release 8.5(1) or 9.0(1) from Physical to Virtual Server  ===&lt;br /&gt;
&lt;br /&gt;
Migration to Unified CVP 8.5 or 9.0 from physical (MCS) server to any virtual server (UCS or non-UCS) server is not supported. &lt;br /&gt;
&lt;br /&gt;
== UCS Network Configuration  ==&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Customer Voice Portal (Unified CVP) on a virtualized platform, please see below. &lt;br /&gt;
&lt;br /&gt;
'''1) Network adapter setting modification on Reporting Server''' -The customers must modify the &amp;quot;Number of Receive Buffers&amp;quot; setting on the Reporting server to maximize full reporting and call load on the virtualized platform. If this setting is not modified after installing the OS, messages will get backed up on the CallServer and Message Queues will fill up resulting in a sharp drop in cps rate. &lt;br /&gt;
&lt;br /&gt;
*Set the &amp;quot;Number of Receive buffers&amp;quot; on the Reporting Server TCP settings to 4096 (max).&lt;br /&gt;
&lt;br /&gt;
Instructions: &lt;br /&gt;
&lt;br /&gt;
#On Reporting server, click on Control Panel-&amp;amp;gt;Network Connection. &lt;br /&gt;
#Right click on Network Connection. &lt;br /&gt;
#Click on advanced tab. &lt;br /&gt;
#Under property tab, select &amp;quot;Number of Receive Buffers&amp;quot;. &lt;br /&gt;
#In the Value pulldown, enter 4096. &lt;br /&gt;
#Restart the Reporting Server.&lt;br /&gt;
&lt;br /&gt;
'''2)&amp;amp;nbsp;'''The following table provides the transport protocols supported by different CVP versions on virtual and non-virtual (bare metal or MCS servers) deployments. The same transport protocol must be used on all call legs of the SIP comprehensive call flow deployments. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;'''SIP transport protocols supported across various deployments'''&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; width=&amp;quot;80%&amp;quot; align=&amp;quot;left&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Type of Hardware &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Releases prior to CVP 8.5(1) ES6 &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | CVP 8.5(1) ES6 or later releases&lt;br /&gt;
|-&lt;br /&gt;
| UCS C Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;amp;amp; UDP**&lt;br /&gt;
|-&lt;br /&gt;
| UCS B Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;lt;br&amp;gt;UDP***&lt;br /&gt;
|-&lt;br /&gt;
| Non Virtualized (bare metal) &lt;br /&gt;
| TCP &amp;amp;amp; UDP &lt;br /&gt;
| TCP &amp;amp;amp; UDP&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The session transport protocol can be set to tcp or udp in the POTS dialpeer. &amp;lt;br&amp;gt;Any other combinations of the transport protocols other than the ones listed above can cause call setup failures or abnormally long call setup times under heavy load. &lt;br /&gt;
&lt;br /&gt;
'''Footnote:&amp;lt;br&amp;gt;'''*&amp;amp;nbsp;Check the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications Docwiki supported Application] page for the Cisco UCS B-series and C-series hardware models supported by the Unified CVP.&amp;lt;br&amp;gt;**&amp;amp;nbsp;To avoid CPU utilization spikes under load conditions, the time synchronization between virtual machine and the ESX server must be disabled. To disable it, install VMware Tools in the virtual machine, in the Windows task bar, double click on the VM icon, in VMware Tools Properties window, uncheck '''Time synchronization between the virtual machine and the ESX Server''' checkbox.&amp;lt;br&amp;gt;***&amp;amp;nbsp;All the UCS&amp;amp;nbsp;servers listed on the&amp;amp;nbsp;[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications#Contact_Center_Applications Unified Communications Virtualization Supported Applications] page support UDP on both VMWare ESXi 4.1 and ESXi 5.0.&amp;lt;br&amp;gt;'''3) Cisco VLAN trunking to VMWare''' For information on best practices for Cisco VLAN trunking to VMware, refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US VMware website] &lt;br /&gt;
&lt;br /&gt;
=== Support for Unified Communications Manager Clustering Over the WAN with Unified CVP on UCS Hardware  ===&lt;br /&gt;
&lt;br /&gt;
You can deploy the Unified Communications Manager (Unified CM) Clustering Over the WAN deployment model with Unified CVP on UCS hardware. &lt;br /&gt;
&lt;br /&gt;
When you implement this deployment model, be sure to follow the best practices outlined in the section &amp;quot;Multiple Cisco Unified CM Clusters&amp;quot; in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Cisco Unified CVP Solution Reference Network Design (SRND)] &lt;br /&gt;
&lt;br /&gt;
In addition, note the following expectation for UCS hardware points of failure: &lt;br /&gt;
&lt;br /&gt;
*Multiple points of failure on the Unified CVP UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.&lt;br /&gt;
&lt;br /&gt;
==== B-Series Considerations  ====&lt;br /&gt;
&lt;br /&gt;
When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS M81KR Virtual Interface Card is recommended. &lt;br /&gt;
&lt;br /&gt;
New B-Series deployments using Clustering Over the WAN should use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G. &lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS B-Series Hardware with SAN  ==&lt;br /&gt;
&lt;br /&gt;
In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays. &lt;br /&gt;
&lt;br /&gt;
In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore. &lt;br /&gt;
&lt;br /&gt;
Keep the following considerations in mind when deploying Unified CVP applications on UCS B-series hardware with SAN: &lt;br /&gt;
&lt;br /&gt;
'''Compliance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*A dedicated SAN LUN and datastore must be used for Unified CVP database components. This means the CVP SAN LUNs cannot be shared by other applications. The SAN disk/storage array must be configured to meet the CVP IOPS requirements. The FC SAN solution is deployed in a shared environment where multiple applications are contending for storage access. The customers need to monitor the FC SAN performance and take appropriate actions to ensure the CVP IOPS and other UC IOPS requirements that share the same FC SAN systems are met. Should in the process of troubleshooting the SAN itself be identified as the problem, the customer must contact the system integrator or the SAN vendor for resolution.&lt;br /&gt;
&lt;br /&gt;
'''Design Considerations''' &lt;br /&gt;
&lt;br /&gt;
*The SAN must be designed in accordance with the UCS High Availability guidelines documented [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html here]. &lt;br /&gt;
*The SAN design and configuration must meet the Unified CVP IOPS and Performance numbers described in the [[#Performance_Requirements|Performance Requirements]]. &lt;br /&gt;
*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines: &lt;br /&gt;
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, mis-behaving, or mis-configured disk array.&lt;br /&gt;
&lt;br /&gt;
'''Configuration Considerations''' &lt;br /&gt;
&lt;br /&gt;
*For UCS B-series, Virtual Machines must be stored on and booted from the SAN. &lt;br /&gt;
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.&lt;br /&gt;
*The SAN design and configuration must meet the following Windows performance counters on Unified CVP VMs: &lt;br /&gt;
**AverageDiskQueueLength must remain less than (1.5 * (the total number of disks in the array)). &lt;br /&gt;
**&amp;amp;nbsp;%Disktime must remain less than 60%.&lt;br /&gt;
*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CVP applications should be designed for the 95th percentile IOPS values published in this wiki. Refer to the Performance Requirements section below for additional information. For other UC applications, please follow their respective IOPS requirements and guidelines.&lt;br /&gt;
&lt;br /&gt;
'''Storage/Size Considerations''' &lt;br /&gt;
&lt;br /&gt;
*Unified CVP requires application storage to be on VMFS. Raw Device Mapping (RDM) is not supported. &lt;br /&gt;
*The total size of all Virtual Machines on a disk (total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.&lt;br /&gt;
&lt;br /&gt;
'''Input/Output Operations per Second (IOPS) Considerations''' &lt;br /&gt;
&lt;br /&gt;
*IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability. Refer to the Performance Requirements section below for additional information.&lt;br /&gt;
&lt;br /&gt;
'''Maintenance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*To help keep your system running most efficiently, schedule automatic database purging and database backups to run when your system is least busy.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS C-Series Hardware  ==&lt;br /&gt;
&lt;br /&gt;
This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks are either RAID 5 or RAID10. &lt;br /&gt;
&lt;br /&gt;
*Install ESXi 4.0/4.1 on the first disk array group (RAID 1 with disk 1 and disk 2) &lt;br /&gt;
*The creation of the virtual machine for the Reporting Server requires a large virtual disk size. Max disk size for a single VM to be 438GB for the large reporting server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;You must follow the steps described below to configure the ESXi data store block size to 2MB. &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi data store block size to 2MB: &lt;br /&gt;
&lt;br /&gt;
#Boot ESXi 4.0/4.1 and use VMware vSphere Client to connect to the ESXi host. &lt;br /&gt;
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 (or RAID-10 ) configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB. &lt;br /&gt;
#Right-click this data store and delete it. We will add the data store back in the following steps. &lt;br /&gt;
#Click on the “Add Storage…” and select the Disk/LUN. &lt;br /&gt;
#The data store that was just deleted will now be available to add, select it. &lt;br /&gt;
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.&lt;br /&gt;
&lt;br /&gt;
== Steps for Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines. &lt;br /&gt;
&lt;br /&gt;
#Install, setup, and configure the UCS Hardware. &lt;br /&gt;
#Configure the UCS Network. See reference at [[UCS Network Configuration for Unified CCE]]. &lt;br /&gt;
#Install and Boot VMWare ESXi. Refer to the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide]. &lt;br /&gt;
#Create the Unified CVP Virtual Machines from the OVA template available [http://www.cisco.com/cco/cisco/software/release.html?mdfid=270563413&amp;amp;flowid=5229&amp;amp;softwareid=280840592&amp;amp;release=9.0%281%29&amp;amp;relind=AVAILABLE&amp;amp;rellifecycle=&amp;amp;reltype=latest here].&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#Install Windows OS and Websphere Application Server (if using VXML Server with WAS) on the created Virtual Machines. (Note: Microsoft Windows Server 2003 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.) &lt;br /&gt;
#Install Unified CVP Software components on the configured Virtual Machines. See install reference for installing Unified CVP Components in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/installation/guide/CVP85install.pdf CVP Install and Upgrade guide]&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Capacities and VM Configuration Requirements  ==&lt;br /&gt;
&lt;br /&gt;
This section provides details associated with [[Unified Communications VMWare Requirements|VM requirements]] &lt;br /&gt;
&lt;br /&gt;
This table shows the supported Unified CVP components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Unified CVP component VMs. &lt;br /&gt;
&lt;br /&gt;
[[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Customer_Voice_Portal|Table containing Unified CVP component capacities and VM configuration requirements]] &lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Co-Residency and Sample Deployments  ==&lt;br /&gt;
&lt;br /&gt;
You can have one or more Unified CVP VMs co-resident on the same ESXi server.&amp;amp;nbsp; However, you must follow the rules described below: &lt;br /&gt;
&lt;br /&gt;
:*You can have any number of Unified CVP virtual machines and combination of co-residency of Unified CVP virtual machines with other UC applications on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.&amp;amp;nbsp; &lt;br /&gt;
:*You must not have&amp;amp;nbsp;CPU overcommitted on the ESXi server that is running Unified CVP&amp;amp;nbsp;application components .&amp;amp;nbsp; The total number of vCPUs among all&amp;amp;nbsp;the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server.&amp;amp;nbsp; In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8. &lt;br /&gt;
:*You must not have&amp;amp;nbsp;memory overcommitted on the ESXi host that is running UC realtime applications.&amp;amp;nbsp; You must allocate&amp;amp;nbsp;minimum&amp;amp;nbsp;2GB of memory for the ESXi kernel.&amp;amp;nbsp; For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines.&amp;amp;nbsp; The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.&lt;br /&gt;
&lt;br /&gt;
:*VM co-residency with third party applications is not supported unless it is specifically described in this page.&lt;br /&gt;
&lt;br /&gt;
The CVP&amp;amp;nbsp;Media Server VM can use a 2 vCPU VM profile like the CVP Operations Console VM profile. However, this is a third party VM and can be tailored to have a different VM profile to satisfy a particular CVP deployment need. CVP Media Server VM can be co-loaded on the CVP Call Server+VXML Server VM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Creating Virtual Machines from OVA VM Templates  ==&lt;br /&gt;
&lt;br /&gt;
Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances.&amp;amp;nbsp; Files in this format have an extension of .ova. The naming convention for the template is PRODUCT_COMPONENT_USER COUNT_VERSION_VMVER.ova &lt;br /&gt;
&lt;br /&gt;
Follow the instructions in the Downloading OVA Templates section below to download the OVA templates from cisco.com to a local datastore that vSphere Client can access. &lt;br /&gt;
&lt;br /&gt;
=== Downloading OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
:*Proceed to the [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%281%29&amp;amp;mdfid=270563413&amp;amp;sftType=Cisco+Customer+Voice+Portal+Software+Releases&amp;amp;optPlat=&amp;amp;nodecount=2&amp;amp;edesignator=null&amp;amp;modelName=Cisco+Unified+Customer+Voice+Portal&amp;amp;treeMdfId=278875240&amp;amp;treeName=Voice+and+Unified+Communications&amp;amp;modifmdfid=null&amp;amp;imname=&amp;amp;hybrid=Y&amp;amp;imst=N&amp;amp;lr=Y Cisco Download Page for CVP].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*To download a single OVA file, click the '''Download File''' button next to that file. To download multiple OVA files, click the '''Add to Cart''' button next to each file that you want to download, then click on the '''Download Cart''' link. A Download Cart page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Read the Software License Agreement, then click the '''Agree''' button&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Creating Virtual Machines by Deploying the OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Customer_Voice_Portal Unified CVP OVA Templates List] &lt;br /&gt;
&lt;br /&gt;
In the vSphere client, perform the following steps to deploy the Virtual machines. &lt;br /&gt;
&lt;br /&gt;
#Highlight the host or cluster to which you wish the VM to be deployed. &lt;br /&gt;
#Select '''File''' &amp;amp;gt; '''Deploy OVF Template'''. &lt;br /&gt;
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''or''' click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''. &lt;br /&gt;
#Verify the details of the template, and click '''Next'''. &lt;br /&gt;
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''. &lt;br /&gt;
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''. &lt;br /&gt;
#Choose a virtual network for the VM, then click '''Next'''. &lt;br /&gt;
#Verify the deployment settings, then click '''Finish'''.&lt;br /&gt;
&lt;br /&gt;
=== Notes  ===&lt;br /&gt;
&lt;br /&gt;
:*VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. &lt;br /&gt;
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. &lt;br /&gt;
:*You cannot change the computing resource configuration of your VM at any time. &lt;br /&gt;
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates. &lt;br /&gt;
:*It is required that hyperthreading be enabled by default when running CVP on ESXi. ESXi Server hyperthread is enabled by default and this setting should not be modified. Please ensure all VM's with CVP servers has hyperthreading enabled.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remote Control of the Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. &lt;br /&gt;
&lt;br /&gt;
== Installing VMware Tools  ==&lt;br /&gt;
&lt;br /&gt;
The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system. &lt;br /&gt;
&lt;br /&gt;
== Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
You can install the Unified CVP components after the configuration of the VMs. Installation of these Unified CVP components on a VM is the same as the installation of these components on physical hardware. &lt;br /&gt;
&lt;br /&gt;
Refer to the Unified CVP documentation for the steps to install Unified CVP components. You can install the supported Virus Scan software, or any other software in the same way as on physical hardware. Refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf CVP Hardware and System Software Specification] for more information.&lt;br /&gt;
&lt;br /&gt;
== Configuring the ESXi Data Store Block Size for Administration and Data Server  ==&lt;br /&gt;
&lt;br /&gt;
The creation of the virtual machine for the Unified CVP Reporting Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store size to 438 GB for it to handle the Unified CVP Reporting Server data before you deploy the OVAs &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi for CVP Reporting server to RAID10 found at [[CVP Reporting Server Configuration|CVP Reporting Server Configuration]] &lt;br /&gt;
&lt;br /&gt;
== Performance Requirements  ==&lt;br /&gt;
&lt;br /&gt;
:*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. &lt;br /&gt;
:*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs. &lt;br /&gt;
:*VM snapshots are not supported in production since they have significant impact on system performance.&amp;amp;nbsp; &lt;br /&gt;
:*The&amp;amp;nbsp;SAN must be able to handle the following Unified CVP application disk I/O characteristics. &lt;br /&gt;
:*Enable hyperthreading on all ESXi servers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Performance Numbers on UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
'''HTTP Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label (VXML Server on Tomcat) &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''HTTPS Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== VM IOPS Measurement  ==&lt;br /&gt;
&lt;br /&gt;
For information on IOPS numbers for Cisco Unified Customer Voice Portal, see [http://docwiki.cisco.com/wiki/UC_Virtualization_Storage_System_Design_Requirements#Cisco_Customer_Voice_Portal.C2.A0 UC Virtualization Storage System Design Requirements]&lt;br /&gt;
&lt;br /&gt;
== Timekeeping Best Practices for Windows  ==&lt;br /&gt;
&lt;br /&gt;
You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1318 VMware KB:Timekeeping best practices for Windows] &lt;br /&gt;
&lt;br /&gt;
*ESXi hosts and domain controllers should synchronize the time from the same NTP source. &lt;br /&gt;
*When Unified Unified CVP virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time. &lt;br /&gt;
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== System Performance Monitoring Using Windows Perfmon Counters  ==&lt;br /&gt;
&lt;br /&gt;
You must comply with the best practices described in the section titled System Perormance Monitoring in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Unified CVP SRND]. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color: rgb(255,215,0)&amp;quot; | '''Back to [[Unified Communications in a Virtualized Environment]]'''&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP</id>
		<title>Virtualization for Unified CVP</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP"/>
				<updated>2013-04-25T12:09:26Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* VM IOPS Measurement */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Updates to this Page  ==&lt;br /&gt;
&lt;br /&gt;
The following is a list of significant updates to this page: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Date &lt;br /&gt;
! Update&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;24,&amp;amp;nbsp;2010 &lt;br /&gt;
| Distribution of Cisco UCS Unified CVP DocWiki for Tech review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;25,&amp;amp;nbsp;2010 &lt;br /&gt;
| Cleaned up IOPS tables, product naming conventions, section consistency with Unified CCE UCS wiki.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;26,&amp;amp;nbsp;2010 &lt;br /&gt;
| Validated links, performed spell check, noted areas still requiring additional technical review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;27,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following areas: Information for Partners, VMWare and Application Software Requirements, UCS Network Configuration, Configuring ESXi datastore.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;28,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following sections: Modified link to Information for Partners; Unified CVP 8.0(1) Support for Virtualization on the ESXi/UCS Platform (Modified bullet that referred to 'Distributed'; Coresidency (Deleted references to realtime; Modified last bullet regarding support on Blade.)&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;30,&amp;amp;nbsp;2010 &lt;br /&gt;
| Unified CVP Virtualization information posted to Unified Communications Virtualization Wiki.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;6,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated links to Unified CVP main page and CVP Reporting Server Configuration sub-page.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated Unified CVP Component Co-Residency section.&lt;br /&gt;
|-&lt;br /&gt;
| December&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated page to note that CVP 8.5(1) features the same level of support for virtualization that is available in CVP 8.0(1)&lt;br /&gt;
|-&lt;br /&gt;
| January&amp;amp;nbsp;12,&amp;amp;nbsp;2011 &lt;br /&gt;
| Added information on using CVP with C-Series servers.&lt;br /&gt;
|-&lt;br /&gt;
| September 1, 2011 &lt;br /&gt;
| Added support for ESXi 4.1.&lt;br /&gt;
|-&lt;br /&gt;
| February 6, 2012 &lt;br /&gt;
| Updated with the CVP support for TCP and UDP on UCS C-series servers.&lt;br /&gt;
|-&lt;br /&gt;
| July 6, 2012 &lt;br /&gt;
| Virtualization support for Release 9.0(1).&lt;br /&gt;
|-&lt;br /&gt;
| September 18, 2012 &lt;br /&gt;
| Unified CVP-Specific VM Installation Information&lt;br /&gt;
|-&lt;br /&gt;
| January 28, 2013&lt;br /&gt;
| CVP Media Server coresidency as general support.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==&lt;br /&gt;
&lt;br /&gt;
'''It is important that partners who are planning to sell UCS products on Unified Cisco Customer Voice Portal, read the [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise Unified CCE DocWiki] page.''' This page contains essential information for partners about the following: &lt;br /&gt;
&lt;br /&gt;
:*Partner Certification Requirements &lt;br /&gt;
:*UCS Server Ordering Information &lt;br /&gt;
:*Important Notes on Cisco UCS Service and Support&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
Starting with Release 9.0(1),all Unified CVP components can be deployed using the single OVA on any CVP supported virtulization hardware. Starting with Release 8.0(1), virtualization of the following deployments and Unified CVP components on Cisco Unified Communications Systems (UCS) B-Series hardware is supported: &lt;br /&gt;
&lt;br /&gt;
:*Unified CVP Call Server &lt;br /&gt;
:*Unified CVP VXML Server &lt;br /&gt;
:*Unified CVP Reporting Server &lt;br /&gt;
:*Unified CVP Ops Console&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following deployments and Unified CVP components have not been qualified and '''are not supported''' in virtualization: &lt;br /&gt;
&lt;br /&gt;
:*H323 Call flow Deployment &lt;br /&gt;
:*Distributed VXML Server and Call Server deployment where each server runs in a separate VM &lt;br /&gt;
:*All in one lab deployment with small reporting server&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following VMware features are not supported with Unified CVP: &lt;br /&gt;
&lt;br /&gt;
:*VMware Physical to Virtual migration &lt;br /&gt;
:*VMware Snapshots &lt;br /&gt;
:*VMware Consolidated Backup &lt;br /&gt;
:*VMware High Availability (HA) &lt;br /&gt;
:*VMware Site Recovery Manager &lt;br /&gt;
:*VMware vCenter Update Manager &lt;br /&gt;
:*VMware vCenter Converter&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Note: Unified CVP components are supported on the UCS platform only in a virtualized environment with ESXi server.''' &lt;br /&gt;
&lt;br /&gt;
== UCS Hardware Requirements  ==&lt;br /&gt;
&lt;br /&gt;
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located [[Unified Computing System Hardware#B-200_M1_Requirements|here]]. &lt;br /&gt;
&lt;br /&gt;
Requirements for C210 hardware are located in the [[Unified Computing System Hardware]]. For UCS C210, CVP supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210M2-VCD2]). Other supported UCS models are at [[Unified Communications Virtualization Supported Applications#Contact_Center_Applications|Unified Communications Supported Applications]] &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1. &lt;br /&gt;
&lt;br /&gt;
For Unified CVP to work on UCS server, UCS firmware has to be 1.4(3c) or later. &lt;br /&gt;
&lt;br /&gt;
== VMware and Application Software Requirements  ==&lt;br /&gt;
&lt;br /&gt;
The following software requirements apply specifically to Unified Customer Voice Portal: &lt;br /&gt;
&lt;br /&gt;
:*VMware ESXi 4.1/5.0, minimum version 4.0U1. Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported. See [[Unified Communications VMware Requirements#VMware_vSphere_ESXi_Version_Support_for_Contact_Center_Applications|Unified Communications VMware requirements]] for a summary and further information. &lt;br /&gt;
:*You need to [[Disable LRO|disable LRO]] for ESXi 4.1/5.0. See [[Implementing Virtualization Deployments]] for more information. &lt;br /&gt;
:*The Windows, Informix, and other third party software requirements for the Unified CVP applications in the ESXi/UCS platform are the same as in the physical server. For such information, refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf Hardware and System Software Specification for Cisco Unified Customer Voice Portal, Release 8.5(1)]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP-Specific VM Installation Information  ==&lt;br /&gt;
&lt;br /&gt;
=== Migrating to Unified CVP Release 8.5(1) or 9.0(1) from Physical to Virtual Server  ===&lt;br /&gt;
&lt;br /&gt;
Migration to Unified CVP 8.5 or 9.0 from physical (MCS) server to any virtual server (UCS or non-UCS) server is not supported. &lt;br /&gt;
&lt;br /&gt;
== UCS Network Configuration  ==&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Customer Voice Portal (Unified CVP) on a virtualized platform, please see below. &lt;br /&gt;
&lt;br /&gt;
'''1) Network adapter setting modification on Reporting Server''' -The customers must modify the &amp;quot;Number of Receive Buffers&amp;quot; setting on the Reporting server to maximize full reporting and call load on the virtualized platform. If this setting is not modified after installing the OS, messages will get backed up on the CallServer and Message Queues will fill up resulting in a sharp drop in cps rate. &lt;br /&gt;
&lt;br /&gt;
*Set the &amp;quot;Number of Receive buffers&amp;quot; on the Reporting Server TCP settings to 4096 (max).&lt;br /&gt;
&lt;br /&gt;
Instructions: &lt;br /&gt;
&lt;br /&gt;
#On Reporting server, click on Control Panel-&amp;amp;gt;Network Connection. &lt;br /&gt;
#Right click on Network Connection. &lt;br /&gt;
#Click on advanced tab. &lt;br /&gt;
#Under property tab, select &amp;quot;Number of Receive Buffers&amp;quot;. &lt;br /&gt;
#In the Value pulldown, enter 4096. &lt;br /&gt;
#Restart the Reporting Server.&lt;br /&gt;
&lt;br /&gt;
'''2)&amp;amp;nbsp;'''The following table provides the transport protocols supported by different CVP versions on virtual and non-virtual (bare metal or MCS servers) deployments. The same transport protocol must be used on all call legs of the SIP comprehensive call flow deployments. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;'''SIP transport protocols supported across various deployments'''&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; width=&amp;quot;80%&amp;quot; align=&amp;quot;left&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Type of Hardware &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Releases prior to CVP 8.5(1) ES6 &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | CVP 8.5(1) ES6 or later releases&lt;br /&gt;
|-&lt;br /&gt;
| UCS C Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;amp;amp; UDP**&lt;br /&gt;
|-&lt;br /&gt;
| UCS B Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;lt;br&amp;gt;UDP***&lt;br /&gt;
|-&lt;br /&gt;
| Non Virtualized (bare metal) &lt;br /&gt;
| TCP &amp;amp;amp; UDP &lt;br /&gt;
| TCP &amp;amp;amp; UDP&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The session transport protocol can be set to tcp or udp in the POTS dialpeer. &amp;lt;br&amp;gt;Any other combinations of the transport protocols other than the ones listed above can cause call setup failures or abnormally long call setup times under heavy load. &lt;br /&gt;
&lt;br /&gt;
'''Footnote:&amp;lt;br&amp;gt;'''*&amp;amp;nbsp;Check the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications Docwiki supported Application] page for the Cisco UCS B-series and C-series hardware models supported by the Unified CVP.&amp;lt;br&amp;gt;**&amp;amp;nbsp;To avoid CPU utilization spikes under load conditions, the time synchronization between virtual machine and the ESX server must be disabled. To disable it, install VMware Tools in the virtual machine, in the Windows task bar, double click on the VM icon, in VMware Tools Properties window, uncheck '''Time synchronization between the virtual machine and the ESX Server''' checkbox.&amp;lt;br&amp;gt;***&amp;amp;nbsp;All the UCS&amp;amp;nbsp;servers listed on the&amp;amp;nbsp;[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications#Contact_Center_Applications Unified Communications Virtualization Supported Applications] page support UDP on both VMWare ESXi 4.1 and ESXi 5.0.&amp;lt;br&amp;gt;'''3) Cisco VLAN trunking to VMWare''' For information on best practices for Cisco VLAN trunking to VMware, refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US VMware website] &lt;br /&gt;
&lt;br /&gt;
=== Support for Unified Communications Manager Clustering Over the WAN with Unified CVP on UCS Hardware  ===&lt;br /&gt;
&lt;br /&gt;
You can deploy the Unified Communications Manager (Unified CM) Clustering Over the WAN deployment model with Unified CVP on UCS hardware. &lt;br /&gt;
&lt;br /&gt;
When you implement this deployment model, be sure to follow the best practices outlined in the section &amp;quot;Multiple Cisco Unified CM Clusters&amp;quot; in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Cisco Unified CVP Solution Reference Network Design (SRND)] &lt;br /&gt;
&lt;br /&gt;
In addition, note the following expectation for UCS hardware points of failure: &lt;br /&gt;
&lt;br /&gt;
*Multiple points of failure on the Unified CVP UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.&lt;br /&gt;
&lt;br /&gt;
==== B-Series Considerations  ====&lt;br /&gt;
&lt;br /&gt;
When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS M81KR Virtual Interface Card is recommended. &lt;br /&gt;
&lt;br /&gt;
New B-Series deployments using Clustering Over the WAN should use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G. &lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS B-Series Hardware with SAN  ==&lt;br /&gt;
&lt;br /&gt;
In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays. &lt;br /&gt;
&lt;br /&gt;
In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore. &lt;br /&gt;
&lt;br /&gt;
Keep the following considerations in mind when deploying Unified CVP applications on UCS B-series hardware with SAN: &lt;br /&gt;
&lt;br /&gt;
'''Compliance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*A dedicated SAN LUN and datastore must be used for Unified CVP database components. This means the CVP SAN LUNs cannot be shared by other applications. The SAN disk/storage array must be configured to meet the CVP IOPS requirements. The FC SAN solution is deployed in a shared environment where multiple applications are contending for storage access. The customers need to monitor the FC SAN performance and take appropriate actions to ensure the CVP IOPS and other UC IOPS requirements that share the same FC SAN systems are met. Should in the process of troubleshooting the SAN itself be identified as the problem, the customer must contact the system integrator or the SAN vendor for resolution.&lt;br /&gt;
&lt;br /&gt;
'''Design Considerations''' &lt;br /&gt;
&lt;br /&gt;
*The SAN must be designed in accordance with the UCS High Availability guidelines documented [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html here]. &lt;br /&gt;
*The SAN design and configuration must meet the Unified CVP IOPS and Performance numbers described in the [[#Performance_Requirements|Performance Requirements]]. &lt;br /&gt;
*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines: &lt;br /&gt;
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, mis-behaving, or mis-configured disk array.&lt;br /&gt;
&lt;br /&gt;
'''Configuration Considerations''' &lt;br /&gt;
&lt;br /&gt;
*For UCS B-series, Virtual Machines must be stored on and booted from the SAN. &lt;br /&gt;
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.&lt;br /&gt;
*The SAN design and configuration must meet the following Windows performance counters on Unified CVP VMs: &lt;br /&gt;
**AverageDiskQueueLength must remain less than (1.5 * (the total number of disks in the array)). &lt;br /&gt;
**&amp;amp;nbsp;%Disktime must remain less than 60%.&lt;br /&gt;
*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CVP applications should be designed for the 95th percentile IOPS values published in this wiki. Refer to the Performance Requirements section below for additional information. For other UC applications, please follow their respective IOPS requirements and guidelines.&lt;br /&gt;
&lt;br /&gt;
'''Storage/Size Considerations''' &lt;br /&gt;
&lt;br /&gt;
*Unified CVP requires application storage to be on VMFS. Raw Device Mapping (RDM) is not supported. &lt;br /&gt;
*The total size of all Virtual Machines on a disk (total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.&lt;br /&gt;
&lt;br /&gt;
'''Input/Output Operations per Second (IOPS) Considerations''' &lt;br /&gt;
&lt;br /&gt;
*IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability. Refer to the Performance Requirements section below for additional information.&lt;br /&gt;
&lt;br /&gt;
'''Maintenance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*To help keep your system running most efficiently, schedule automatic database purging and database backups to run when your system is least busy.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS C-Series Hardware  ==&lt;br /&gt;
&lt;br /&gt;
This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks are either RAID 5 or RAID10. &lt;br /&gt;
&lt;br /&gt;
*Install ESXi 4.0/4.1 on the first disk array group (RAID 1 with disk 1 and disk 2) &lt;br /&gt;
*The creation of the virtual machine for the Reporting Server requires a large virtual disk size. Max disk size for a single VM to be 438GB for the large reporting server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;You must follow the steps described below to configure the ESXi data store block size to 2MB. &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi data store block size to 2MB: &lt;br /&gt;
&lt;br /&gt;
#Boot ESXi 4.0/4.1 and use VMware vSphere Client to connect to the ESXi host. &lt;br /&gt;
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 (or RAID-10 ) configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB. &lt;br /&gt;
#Right-click this data store and delete it. We will add the data store back in the following steps. &lt;br /&gt;
#Click on the “Add Storage…” and select the Disk/LUN. &lt;br /&gt;
#The data store that was just deleted will now be available to add, select it. &lt;br /&gt;
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.&lt;br /&gt;
&lt;br /&gt;
== Steps for Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines. &lt;br /&gt;
&lt;br /&gt;
#Install, setup, and configure the UCS Hardware. &lt;br /&gt;
#Configure the UCS Network. See reference at [[UCS Network Configuration for Unified CCE]]. &lt;br /&gt;
#Install and Boot VMWare ESXi. Refer to the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide]. &lt;br /&gt;
#Create the Unified CVP Virtual Machines from the OVA template available [http://www.cisco.com/cco/cisco/software/release.html?mdfid=270563413&amp;amp;flowid=5229&amp;amp;softwareid=280840592&amp;amp;release=9.0%281%29&amp;amp;relind=AVAILABLE&amp;amp;rellifecycle=&amp;amp;reltype=latest here].&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#Install Windows OS and Websphere Application Server (if using VXML Server with WAS) on the created Virtual Machines. (Note: Microsoft Windows Server 2003 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.) &lt;br /&gt;
#Install Unified CVP Software components on the configured Virtual Machines. See install reference for installing Unified CVP Components in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/installation/guide/CVP85install.pdf CVP Install and Upgrade guide]&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Capacities and VM Configuration Requirements  ==&lt;br /&gt;
&lt;br /&gt;
This section provides details associated with [[Unified Communications VMWare Requirements|VM requirements]] &lt;br /&gt;
&lt;br /&gt;
This table shows the supported Unified CVP components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Unified CVP component VMs. &lt;br /&gt;
&lt;br /&gt;
[[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Customer_Voice_Portal|Table containing Unified CVP component capacities and VM configuration requirements]] &lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Co-Residency and Sample Deployments  ==&lt;br /&gt;
&lt;br /&gt;
You can have one or more Unified CVP VMs co-resident on the same ESXi server.&amp;amp;nbsp; However, you must follow the rules described below: &lt;br /&gt;
&lt;br /&gt;
:*You can have any number of Unified CVP virtual machines and combination of co-residency of Unified CVP virtual machines with other UC applications on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.&amp;amp;nbsp; &lt;br /&gt;
:*You must not have&amp;amp;nbsp;CPU overcommitted on the ESXi server that is running Unified CVP&amp;amp;nbsp;application components .&amp;amp;nbsp; The total number of vCPUs among all&amp;amp;nbsp;the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server.&amp;amp;nbsp; In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8. &lt;br /&gt;
:*You must not have&amp;amp;nbsp;memory overcommitted on the ESXi host that is running UC realtime applications.&amp;amp;nbsp; You must allocate&amp;amp;nbsp;minimum&amp;amp;nbsp;2GB of memory for the ESXi kernel.&amp;amp;nbsp; For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines.&amp;amp;nbsp; The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.&lt;br /&gt;
&lt;br /&gt;
:*VM co-residency with third party applications is not supported unless it is specifically described in this page.&lt;br /&gt;
&lt;br /&gt;
The CVP&amp;amp;nbsp;Media Server VM can use a 2 vCPU VM profile like the CVP Operations Console VM profile. However, this is a third party VM and can be tailored to have a different VM profile to satisfy a particular CVP deployment need. CVP Media Server VM can be co-loaded on the CVP Call Server+VXML Server VM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Creating Virtual Machines from OVA VM Templates  ==&lt;br /&gt;
&lt;br /&gt;
Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances.&amp;amp;nbsp; Files in this format have an extension of .ova. The naming convention for the template is PRODUCT_COMPONENT_USER COUNT_VERSION_VMVER.ova &lt;br /&gt;
&lt;br /&gt;
Follow the instructions in the Downloading OVA Templates section below to download the OVA templates from cisco.com to a local datastore that vSphere Client can access. &lt;br /&gt;
&lt;br /&gt;
=== Downloading OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
:*Proceed to the [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%281%29&amp;amp;mdfid=270563413&amp;amp;sftType=Cisco+Customer+Voice+Portal+Software+Releases&amp;amp;optPlat=&amp;amp;nodecount=2&amp;amp;edesignator=null&amp;amp;modelName=Cisco+Unified+Customer+Voice+Portal&amp;amp;treeMdfId=278875240&amp;amp;treeName=Voice+and+Unified+Communications&amp;amp;modifmdfid=null&amp;amp;imname=&amp;amp;hybrid=Y&amp;amp;imst=N&amp;amp;lr=Y Cisco Download Page for CVP].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*To download a single OVA file, click the '''Download File''' button next to that file. To download multiple OVA files, click the '''Add to Cart''' button next to each file that you want to download, then click on the '''Download Cart''' link. A Download Cart page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Read the Software License Agreement, then click the '''Agree''' button&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Creating Virtual Machines by Deploying the OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Customer_Voice_Portal Unified CVP OVA Templates List] &lt;br /&gt;
&lt;br /&gt;
In the vSphere client, perform the following steps to deploy the Virtual machines. &lt;br /&gt;
&lt;br /&gt;
#Highlight the host or cluster to which you wish the VM to be deployed. &lt;br /&gt;
#Select '''File''' &amp;amp;gt; '''Deploy OVF Template'''. &lt;br /&gt;
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''or''' click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''. &lt;br /&gt;
#Verify the details of the template, and click '''Next'''. &lt;br /&gt;
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''. &lt;br /&gt;
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''. &lt;br /&gt;
#Choose a virtual network for the VM, then click '''Next'''. &lt;br /&gt;
#Verify the deployment settings, then click '''Finish'''.&lt;br /&gt;
&lt;br /&gt;
=== Notes  ===&lt;br /&gt;
&lt;br /&gt;
:*VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. &lt;br /&gt;
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. &lt;br /&gt;
:*You cannot change the computing resource configuration of your VM at any time. &lt;br /&gt;
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates. &lt;br /&gt;
:*It is required that hyperthreading be enabled by default when running CVP on ESXi. ESXi Server hyperthread is enabled by default and this setting should not be modified. Please ensure all VM's with CVP servers has hyperthreading enabled.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remote Control of the Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. &lt;br /&gt;
&lt;br /&gt;
== Installing VMware Tools  ==&lt;br /&gt;
&lt;br /&gt;
The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system. &lt;br /&gt;
&lt;br /&gt;
== Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
You can install the Unified CVP components after the configuration of the VMs. Installation of these Unified CVP components on a VM is the same as the installation of these components on physical hardware. &lt;br /&gt;
&lt;br /&gt;
Refer to the Unified CVP documentation for the steps to install Unified CVP components. You can install the supported Virus Scan software, or any other software in the same way as on physical hardware. Refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf CVP Hardware and System Software Specification] for more information. &lt;br /&gt;
&lt;br /&gt;
== Configuring the ESXi Data Store Block Size for Administration and Data Server  ==&lt;br /&gt;
&lt;br /&gt;
The creation of the virtual machine for the Unified CVP Reporting Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store size to 438 GB for it to handle the Unified CVP Reporting Server data before you deploy the OVAs &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi for CVP Reporting server to RAID10 found at [[CVP Reporting Server Configuration|CVP Reporting Server Configuration]] &lt;br /&gt;
&lt;br /&gt;
== Performance Requirements  ==&lt;br /&gt;
&lt;br /&gt;
:*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. &lt;br /&gt;
:*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs. &lt;br /&gt;
:*VM snapshots are not supported in production since they have significant impact on system performance.&amp;amp;nbsp; &lt;br /&gt;
:*The&amp;amp;nbsp;SAN must be able to handle the following Unified CVP application disk I/O characteristics. &lt;br /&gt;
:*Enable hyperthreading on all ESXi servers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Performance Numbers on UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
'''HTTP Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label (VXML Server on Tomcat) &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''HTTPS Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== VM IOPS Measurement  ==&lt;br /&gt;
&lt;br /&gt;
'''IOPS Summary: (Unit in Number, Data are Blade-based)''' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''The following IOPS metrics are measured in peak load conditions with no failover:'''&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX &lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML Servers &lt;br /&gt;
| 21 &lt;br /&gt;
| 450&lt;br /&gt;
| 30&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 40&lt;br /&gt;
| 930 &lt;br /&gt;
| 56&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''The following IOPS metrics are measured in peak load conditions with failover:'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX &lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML Servers &lt;br /&gt;
| 18 &lt;br /&gt;
| 637&lt;br /&gt;
| 40&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 334&lt;br /&gt;
| 1121 &lt;br /&gt;
| 952&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Timekeeping Best Practices for Windows  ==&lt;br /&gt;
&lt;br /&gt;
You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1318 VMware KB:Timekeeping best practices for Windows] &lt;br /&gt;
&lt;br /&gt;
*ESXi hosts and domain controllers should synchronize the time from the same NTP source. &lt;br /&gt;
*When Unified Unified CVP virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time. &lt;br /&gt;
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== System Performance Monitoring Using Windows Perfmon Counters  ==&lt;br /&gt;
&lt;br /&gt;
You must comply with the best practices described in the section titled System Perormance Monitoring in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Unified CVP SRND]. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color: rgb(255,215,0)&amp;quot; | '''Back to [[Unified Communications in a Virtualized Environment]]'''&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP</id>
		<title>Virtualization for Unified CVP</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP"/>
				<updated>2013-02-26T06:42:47Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Updates to this Page  ==&lt;br /&gt;
&lt;br /&gt;
The following is a list of significant updates to this page: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Date &lt;br /&gt;
! Update&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;24,&amp;amp;nbsp;2010 &lt;br /&gt;
| Distribution of Cisco UCS Unified CVP DocWiki for Tech review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;25,&amp;amp;nbsp;2010 &lt;br /&gt;
| Cleaned up IOPS tables, product naming conventions, section consistency with Unified CCE UCS wiki.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;26,&amp;amp;nbsp;2010 &lt;br /&gt;
| Validated links, performed spell check, noted areas still requiring additional technical review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;27,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following areas: Information for Partners, VMWare and Application Software Requirements, UCS Network Configuration, Configuring ESXi datastore.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;28,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following sections: Modified link to Information for Partners; Unified CVP 8.0(1) Support for Virtualization on the ESXi/UCS Platform (Modified bullet that referred to 'Distributed'; Coresidency (Deleted references to realtime; Modified last bullet regarding support on Blade.)&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;30,&amp;amp;nbsp;2010 &lt;br /&gt;
| Unified CVP Virtualization information posted to Unified Communications Virtualization Wiki.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;6,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated links to Unified CVP main page and CVP Reporting Server Configuration sub-page.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated Unified CVP Component Co-Residency section.&lt;br /&gt;
|-&lt;br /&gt;
| December&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated page to note that CVP 8.5(1) features the same level of support for virtualization that is available in CVP 8.0(1)&lt;br /&gt;
|-&lt;br /&gt;
| January&amp;amp;nbsp;12,&amp;amp;nbsp;2011 &lt;br /&gt;
| Added information on using CVP with C-Series servers.&lt;br /&gt;
|-&lt;br /&gt;
| September 1, 2011 &lt;br /&gt;
| Added support for ESXi 4.1.&lt;br /&gt;
|-&lt;br /&gt;
| February 6, 2012 &lt;br /&gt;
| Updated with the CVP support for TCP and UDP on UCS C-series servers.&lt;br /&gt;
|-&lt;br /&gt;
| July 6, 2012 &lt;br /&gt;
| Virtualization support for Release 9.0(1). &lt;br /&gt;
|-&lt;br /&gt;
| September 18, 2012 &lt;br /&gt;
| Unified CCX-Specific VM Installation Information&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==&lt;br /&gt;
&lt;br /&gt;
It is important that partners who are planning to sell UCS products on Unified Cisco Customer Voice Portal, read the '''[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise Unified CCE DocWiki]''' page. &lt;br /&gt;
&lt;br /&gt;
This page contains essential information for partners about the following: &lt;br /&gt;
&lt;br /&gt;
:*Partner Certification Requirements &lt;br /&gt;
:*UCS Server Ordering Information &lt;br /&gt;
:*Important Notes on Cisco UCS Service and Support&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
Starting with Release 9.0(1),all Unified CVP components can be deployed using the single OVA on any CVP supported virtulization hardware. Starting with Release 8.0(1), virtualization of the following deployments and Unified CVP components on Cisco Unified Communications Systems (UCS) B-Series hardware is supported: &lt;br /&gt;
&lt;br /&gt;
:*Unified CVP Call Server &lt;br /&gt;
:*Unified CVP VXML Server &lt;br /&gt;
:*Unified CVP Reporting Server &lt;br /&gt;
:*Unified CVP Ops Console&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following deployments and Unified CVP components have not been qualified and '''are not supported''' in virtualization: &lt;br /&gt;
&lt;br /&gt;
:*H323 Call flow Deployment &lt;br /&gt;
:*Distributed VXML Server and Call Server deployment where each server runs in a separate VM &lt;br /&gt;
:*All in one lab deployment with small reporting server&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following VMware features are not supported with Unified CVP: &lt;br /&gt;
&lt;br /&gt;
:*VMware Physical to Virtual migration &lt;br /&gt;
:*VMware Snapshots &lt;br /&gt;
:*VMware Consolidated Backup &lt;br /&gt;
:*VMware High Availability (HA) &lt;br /&gt;
:*VMware Site Recovery Manager &lt;br /&gt;
:*VMware vCenter Update Manager &lt;br /&gt;
:*VMware vCenter Converter&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Note: Unified CVP components are supported on the UCS platform only in a virtualized environment with ESXi server.''' &lt;br /&gt;
&lt;br /&gt;
== UCS Hardware Requirements  ==&lt;br /&gt;
&lt;br /&gt;
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located [http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware#B-200_M1_Requirements/ here]. &lt;br /&gt;
&lt;br /&gt;
Requirements for C210 hardware are located in the '''[[Unified Computing System Hardware]]'''. For UCS C210, CVP supports only the model [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210M2-VCD2]. Other supported UCS models are at [[Unified Communications Virtualization Supported Applications#Contact_Center_Applications|Unified Communications Supported Applications.]] &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1. &lt;br /&gt;
&lt;br /&gt;
For Unified CVP to work on UCS server, UCS firmware has to be 1.4(3c) or later.&lt;br /&gt;
&lt;br /&gt;
== VMware and Application Software Requirements  ==&lt;br /&gt;
&lt;br /&gt;
The following software requirements apply specifically to Unified Customer Voice Portal: &lt;br /&gt;
&lt;br /&gt;
:*VMware ESXi 4.1/5.0, minimum version 4.0U1. Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported. See [[Unified Communications VMware Requirements#VMware_vSphere_ESXi_Version_Support_for_Contact_Center_Applications|Unified Communications VMware Requirements]] for a summary and further information. &lt;br /&gt;
:*You need to [[Disable LRO|Disable LRO for ESXi 4.1/5.0.]] See [[Implementing Virtualization Deployments|Implementing Virtualization Deployments]] for more information. &lt;br /&gt;
:*The Windows, Informix, and other third party software requirements for the Unified CVP applications in the ESXi/UCS platform are the same as in the physical server. For such information, refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf Hardware and System Software Specification for Cisco Unified Customer Voice Portal, Release 8.5(1).]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP-Specific VM Installation Information  ==&lt;br /&gt;
&lt;br /&gt;
=== Migrating to Unified CVP Release 8.5(1) or 9.0(1) from Physical to Virtual Server  ===&lt;br /&gt;
&lt;br /&gt;
Migration to Unified CVP 8.5 or 9.0 from physical (MCS) server to any virtual server (UCS or non-UCS) server is not supported. &lt;br /&gt;
&lt;br /&gt;
== UCS Network Configuration  ==&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Customer Voice Portal (Unified CVP) on a virtualized platform, please see below. &lt;br /&gt;
&lt;br /&gt;
'''1) Network adapter setting modification on Reporting Server''' -The customers must modify the &amp;quot;Number of Receive Buffers&amp;quot; setting on the Reporting server to maximize full reporting and call load on the virtualized platform. If this setting is not modified after installing the OS, messages will get backed up on the CallServer and Message Queues will fill up resulting in a sharp drop in cps rate. &lt;br /&gt;
&lt;br /&gt;
*Set the &amp;quot;Number of Receive buffers&amp;quot; on the Reporting Server TCP settings to 4096 (max).&lt;br /&gt;
&lt;br /&gt;
Instructions: &lt;br /&gt;
&lt;br /&gt;
#On Reporting server, click on Control Panel-&amp;amp;gt;Network Connection. &lt;br /&gt;
#Right click on Network Connection. &lt;br /&gt;
#Click on advanced tab. &lt;br /&gt;
#Under property tab, select &amp;quot;Number of Receive Buffers&amp;quot;. &lt;br /&gt;
#In the Value pulldown, enter 4096. &lt;br /&gt;
#Restart the Reporting Server.&lt;br /&gt;
&lt;br /&gt;
'''2)&amp;amp;nbsp;'''The following table provides the transport protocols supported by different CVP versions on virtual and non-virtual (bare metal or MCS servers) deployments. The same transport protocol must be used on all call legs of the SIP comprehensive call flow deployments. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;'''SIP transport protocols supported across various deployments'''&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; width=&amp;quot;80%&amp;quot; align=&amp;quot;left&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Type of Hardware &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Releases prior to CVP 8.5(1) ES6 &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | CVP 8.5(1) ES6 or later releases&lt;br /&gt;
|-&lt;br /&gt;
| UCS C Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;amp;amp; UDP**&lt;br /&gt;
|-&lt;br /&gt;
| UCS B Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;lt;br&amp;gt;UDP***&lt;br /&gt;
|-&lt;br /&gt;
| Non Virtualized (bare metal) &lt;br /&gt;
| TCP &amp;amp;amp; UDP &lt;br /&gt;
| TCP &amp;amp;amp; UDP&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The session transport protocol can be set to tcp or udp in the POTS dialpeer. &amp;lt;br&amp;gt;Any other combinations of the transport protocols other than the ones listed above can cause call setup failures or abnormally long call setup times under heavy load. &lt;br /&gt;
&lt;br /&gt;
'''Footnote:&amp;lt;br&amp;gt;'''*&amp;amp;nbsp;Check the Docwiki supported Application page:&amp;amp;nbsp;[http://docwiki.cisco.com/wiki/ Unified_Communications_Virtualization_Supported_Applications] for the Cisco UCS B-series and C-series hardware models supported by the Unified CVP.&amp;lt;br&amp;gt;**&amp;amp;nbsp;To avoid CPU utilization spikes under load conditions, the time synchronization between virtual machine and the ESX server must be disabled. To disable it, install VMware Tools in the virtual machine, in the Windows task bar, double click on the VM icon, in VMware Tools Properties window, uncheck '''Time synchronization between the virtual machine and the ESX Server''' checkbox.&amp;lt;br&amp;gt;***&amp;amp;nbsp;all the UCS&amp;amp;nbsp;servers listed on the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications#Contact_Center_Applications/Unified_Communications_Virtualization_Supported_Applications#Contact_Center_Applications/ Unified Communications Virtualization Supported Applications] page support UDP on both&amp;amp;nbsp;VMWare ESXi 4.1 and ESXi 5.0.&amp;lt;br&amp;gt;'''3) Cisco VLAN trunking to VMWare''' For information on best practices for Cisco VLAN trunking to VMware, refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806\ VMwarewebsite]. &lt;br /&gt;
&lt;br /&gt;
=== Support for Unified Communications Manager Clustering Over the WAN with Unified CVP on UCS Hardware  ===&lt;br /&gt;
&lt;br /&gt;
You can deploy the Unified Communications Manager (Unified CM) Clustering Over the WAN deployment model with Unified CVP on UCS hardware. &lt;br /&gt;
&lt;br /&gt;
When you implement this deployment model, be sure to follow the best practices outlined in the section &amp;quot;Multiple Cisco Unified CM Clusters&amp;quot; in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf|Cisco Unified CVP Solution Reference Network Design (SRND).] &lt;br /&gt;
&lt;br /&gt;
In addition, note the following expectation for UCS hardware points of failure: &lt;br /&gt;
&lt;br /&gt;
*Multiple points of failure on the Unified CVP UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.&lt;br /&gt;
&lt;br /&gt;
==== B-Series Considerations  ====&lt;br /&gt;
&lt;br /&gt;
When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS M81KR Virtual Interface Card is mandatory. &lt;br /&gt;
&lt;br /&gt;
New B-Series deployments using Clustering Over the WAN should use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS B-Series Hardware with SAN  ==&lt;br /&gt;
&lt;br /&gt;
In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays. &lt;br /&gt;
&lt;br /&gt;
In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore. &lt;br /&gt;
&lt;br /&gt;
Keep the following considerations in mind when deploying Unified CVP applications on UCS B-series hardware with SAN: &lt;br /&gt;
&lt;br /&gt;
'''Compliance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*A dedicated SAN LUN and datastore must be used for Unified CVP database components. This means the CVP SAN LUNs cannot be shared by other applications. The SAN disk/storage array must be configured to meet the CVP IOPS requirements. The FC SAN solution is deployed in a shared environment where multiple applications are contending for storage access. The customers need to monitor the FC SAN performance and take appropriate actions to ensure the CVP IOPS and other UC IOPS requirements that share the same FC SAN systems are met. Should in the process of troubleshooting the SAN itself be identified as the problem, the customer must contact the system integrator or the SAN vendor for resolution.&lt;br /&gt;
&lt;br /&gt;
'''Design Considerations''' &lt;br /&gt;
&lt;br /&gt;
*The SAN must be designed in accordance with the UCS High Availability guidelines documented at [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html/ here]. &lt;br /&gt;
*The SAN design and configuration must meet the Unified CVP IOPS and Performance numbers described in the [[#Performance_Requirements|Performance Requirements]]. &lt;br /&gt;
*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines: &lt;br /&gt;
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, mis-behaving, or mis-configured disk array.&lt;br /&gt;
&lt;br /&gt;
'''Configuration Considerations''' &lt;br /&gt;
&lt;br /&gt;
*For UCS B-series, Virtual Machines must be stored on and booted from the SAN. &lt;br /&gt;
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.&lt;br /&gt;
*The SAN design and configuration must meet the following Windows performance counters on Unified CVP VMs: &lt;br /&gt;
**AverageDiskQueueLength must remain less than (1.5 * (the total number of disks in the array)). &lt;br /&gt;
**&amp;amp;nbsp;%Disktime must remain less than 60%.&lt;br /&gt;
*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CVP applications should be designed for the 95th percentile IOPS values published in this wiki. Refer to the Performance Requirements section below for additional information. For other UC applications, please follow their respective IOPS requirements and guidelines.&lt;br /&gt;
&lt;br /&gt;
'''Storage/Size Considerations''' &lt;br /&gt;
&lt;br /&gt;
*Unified CVP requires application storage to be on VMFS. Raw Device Mapping (RDM) is not supported. &lt;br /&gt;
*The total size of all Virtual Machines on a disk (total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.&lt;br /&gt;
&lt;br /&gt;
'''Input/Output Operations per Second (IOPS) Considerations''' &lt;br /&gt;
&lt;br /&gt;
*IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability. Refer to the Performance Requirements section below for additional information.&lt;br /&gt;
&lt;br /&gt;
'''Maintenance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*To help keep your system running most efficiently, schedule automatic database purging and database backups to run when your system is least busy.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS C-Series Hardware  ==&lt;br /&gt;
&lt;br /&gt;
This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks are either RAID 5 or RAID10. &lt;br /&gt;
&lt;br /&gt;
*Install ESXi 4.0/4.1 on the first disk array group (RAID 1 with disk 1 and disk 2) &lt;br /&gt;
*The creation of the virtual machine for the Reporting Server requires a large virtual disk size. Max disk size for a single VM to be 438GB for the large reporting server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;You must follow the steps described below to configure the ESXi data store block size to 2MB. &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi data store block size to 2MB: &lt;br /&gt;
&lt;br /&gt;
#Boot ESXi 4.0/4.1 and use VMware vSphere Client to connect to the ESXi host. &lt;br /&gt;
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 (or RAID-10 ) configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB. &lt;br /&gt;
#Right-click this data store and delete it. We will add the data store back in the following steps. &lt;br /&gt;
#Click on the “Add Storage…” and select the Disk/LUN. &lt;br /&gt;
#The data store that was just deleted will now be available to add, select it. &lt;br /&gt;
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.&lt;br /&gt;
&lt;br /&gt;
== Steps for Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines. &lt;br /&gt;
&lt;br /&gt;
#Install, setup, and configure the UCS Hardware. &lt;br /&gt;
#Configure the UCS Network. See reference at [UCS Network Configuration]]. &lt;br /&gt;
#Install and Boot VMWare ESXi. Refer to the appropriate installation guide: [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html\ Cisco UCS B-Series Blade Servers VMware Installation Guide]. &lt;br /&gt;
#Create the Unified CVP Virtual Machines from the OVA template. OVA templates are available [http://www.cisco.com/cco/cisco/software/release.html?mdfid=270563413&amp;amp;flowid=5229&amp;amp;softwareid=280840592&amp;amp;release=9.0%281%29&amp;amp;relind=AVAILABLE&amp;amp;rellifecycle=&amp;amp;reltype=latest/ here].&lt;br /&gt;
&lt;br /&gt;
#Install Windows OS on the created Virtual Machine. (Note: Microsoft Windows Server 2008 R2 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.) &lt;br /&gt;
#Install Unified CVP Software components on the configured Virtual Machines. See install reference for installing Unified CVP Components in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/installation/guide/CVP85install.pdf/ Unified CVP Install and Upgrade guide].&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Capacities and VM Configuration Requirements  ==&lt;br /&gt;
&lt;br /&gt;
This section provides details associated with [[Unified Communications VMWare Requirements|VM requirements]]. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
This table shows the supported Unified CVP components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Unified CVP component VMs. &lt;br /&gt;
&lt;br /&gt;
[[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Customer_Voice_Portal|Table containing Unified CVP component capacities and VM configuration requirements]]&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Co-Residency and Sample Deployments  ==&lt;br /&gt;
&lt;br /&gt;
You can have one or more Unified CVP VMs co-resident on the same ESXi server.&amp;amp;nbsp; However, you must follow the rules described below: &lt;br /&gt;
&lt;br /&gt;
:*You can have any number of Unified CVP virtual machines and combination of co-residency of Unified CVP virtual machines with other UC applications on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.&amp;amp;nbsp; &lt;br /&gt;
:*You must not have&amp;amp;nbsp;CPU overcommitted on the ESXi server that is running Unified CVP&amp;amp;nbsp;application components .&amp;amp;nbsp; The total number of vCPUs among all&amp;amp;nbsp;the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server.&amp;amp;nbsp; In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8. &lt;br /&gt;
:*You must not have&amp;amp;nbsp;memory overcommitted on the ESXi host that is running UC realtime applications.&amp;amp;nbsp; You must allocate&amp;amp;nbsp;minimum&amp;amp;nbsp;2GB of memory for the ESXi kernel.&amp;amp;nbsp; For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines.&amp;amp;nbsp; The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*VM co-residency with third party applications is not supported unless it is specifically described in this page. Currently, the Media Server for CVP is not recommended to be co-loaded on the CVP call server+vxml server VM.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Media Server VM can use a 2 vCPU VM profile like the CVP Operations Console VM profile. However, this is a third party VM and can be tailored to have a different VM profile to satisfy a particular CVP deployment need. &lt;br /&gt;
&lt;br /&gt;
On the other hand, CVP Media Server can be on the CVP Call Server+VXMl Server VM, providing the following conditions are met: &lt;br /&gt;
&lt;br /&gt;
- IIS is used; not Tomcat. &lt;br /&gt;
&lt;br /&gt;
- Audio prompts are cached on the VGW. &lt;br /&gt;
&lt;br /&gt;
- Logging is turned off on the MS&amp;amp;nbsp;media server. &lt;br /&gt;
&lt;br /&gt;
== Creating Virtual Machines from OVA VM Templates  ==&lt;br /&gt;
&lt;br /&gt;
Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances.&amp;amp;nbsp; Files in this format have an extension of .ova. The naming convention for the template is PRODUCT_COMPONENT_USER COUNT_VERSION_VMVER.ova &lt;br /&gt;
&lt;br /&gt;
Follow the instructions in the Downloading OVA Templates section below to download the OVA templates from cisco.com to a local datastore that vSphere Client can access. &lt;br /&gt;
&lt;br /&gt;
=== Downloading OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
:*Proceed to the [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%281%29&amp;amp;mdfid=270563413&amp;amp;sftType=Cisco+Customer+Voice+Portal+Software+Releases&amp;amp;optPlat=&amp;amp;nodecount=2&amp;amp;edesignator=null&amp;amp;modelName=Cisco+Unified+Customer+Voice+Portal&amp;amp;treeMdfId=278875240&amp;amp;treeName=Voice+and+Unified+Communications&amp;amp;modifmdfid=null&amp;amp;imname=&amp;amp;hybrid=Y&amp;amp;imst=N&amp;amp;lr=Y Cisco Download Page for CVP].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*To download a single OVA file, click the '''Download File''' button next to that file. To download multiple OVA files, click the '''Add to Cart''' button next to each file that you want to download, then click on the '''Download Cart''' link. A Download Cart page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Read the Software License Agreement, then click the '''Agree''' button&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Creating Virtual Machines by Deploying the OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Customer_Voice_Portal Unified CVP OVA Templates List] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the vSphere client, perform the following steps to deploy the Virtual machines. &lt;br /&gt;
&lt;br /&gt;
#Highlight the host or cluster to which you wish the VM to be deployed. &lt;br /&gt;
#Select '''File''' &amp;amp;gt; '''Deploy OVF Template'''. &lt;br /&gt;
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''or''' click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''. &lt;br /&gt;
#Verify the details of the template, and click '''Next'''. &lt;br /&gt;
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''. &lt;br /&gt;
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''. &lt;br /&gt;
#Choose a virtual network for the VM, then click '''Next'''. &lt;br /&gt;
#Verify the deployment settings, then click '''Finish'''.&lt;br /&gt;
&lt;br /&gt;
=== Notes  ===&lt;br /&gt;
&lt;br /&gt;
:*VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. &lt;br /&gt;
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. &lt;br /&gt;
:*You cannot change the computing resource configuration of your VM at any time. &lt;br /&gt;
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates. &lt;br /&gt;
:*It is required that hyperthreading be enabled by default when running CVP on ESXi. ESXi Server hyperthread is enabled by default and this setting should not be modified. Please ensure all VM's with CVP servers has hyperthreading enabled.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remote Control of the Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. &lt;br /&gt;
&lt;br /&gt;
== Installing VMware Tools  ==&lt;br /&gt;
&lt;br /&gt;
The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.&lt;br /&gt;
&lt;br /&gt;
== Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
You can install the Unified CVP components after the configuration of the VMs. Installation of these Unified CVP components on a VM is the same as the installation of these components on physical hardware. &lt;br /&gt;
&lt;br /&gt;
Refer to the Unified CVP documentation for the steps to install Unified CVP components. You can install the supported Virus Scan software, or any other software in the same way as on physical hardware. Refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf CVP Hardware and System Software Specification] for more information.&lt;br /&gt;
&lt;br /&gt;
== Configuring the ESXi Data Store Block Size for Administration and Data Server  ==&lt;br /&gt;
&lt;br /&gt;
The creation of the virtual machine for the Unified CVP Reporting Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store size to 438 GB for it to handle the Unified CVP Reporting Server data before you deploy the OVAs &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi for CVP Reporting server to RAID10 found at [[CVP Reporting Server Configuration|CVP Reporting Server Configuration]]&lt;br /&gt;
&lt;br /&gt;
== Performance Requirements  ==&lt;br /&gt;
&lt;br /&gt;
:*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. &lt;br /&gt;
:*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs. &lt;br /&gt;
:*VM snapshots are not supported in production since they have significant impact on system performance.&amp;amp;nbsp; &lt;br /&gt;
:*The&amp;amp;nbsp;SAN must be able to handle the following Unified CVP application disk I/O characteristics. &lt;br /&gt;
:*Enable hyperthreading on all ESXi servers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Performance Numbers on UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
'''HTTP Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label (VXML Server on Tomcat) &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''HTTPS Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== VM IOPS Measurement  ==&lt;br /&gt;
&lt;br /&gt;
'''IOPS Summary: (Unit in Number, Data are Blade-based)''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX &lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML Servers &lt;br /&gt;
| 380 &lt;br /&gt;
| 1536 &lt;br /&gt;
| 797&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 692 &lt;br /&gt;
| 3403 &lt;br /&gt;
| 2024&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Timekeeping Best Practices for Windows  ==&lt;br /&gt;
&lt;br /&gt;
You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;amp;cmd=displayKC&amp;amp;amp;externalId=1318 VMware KB:Timekeeping best practices for Windows].&amp;lt;br&amp;gt;ESXi hosts and domain controllers should synchronize the time from the same NTP source. &lt;br /&gt;
&lt;br /&gt;
*When Unified Unified CVP virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time. &lt;br /&gt;
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== System Performance Monitoring Using Windows Perfmon Counters  ==&lt;br /&gt;
&lt;br /&gt;
You must comply with the best practices described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Unified CVP SRND]. &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color: rgb(255,215,0)&amp;quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP</id>
		<title>Virtualization for Unified CVP</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP"/>
				<updated>2013-01-08T05:07:30Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* UCS Network Configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Updates to this Page  ==&lt;br /&gt;
&lt;br /&gt;
The following is a list of significant updates to this page: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Date &lt;br /&gt;
! Update&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;24,&amp;amp;nbsp;2010 &lt;br /&gt;
| Distribution of Cisco UCS Unified CVP DocWiki for Tech review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;25,&amp;amp;nbsp;2010 &lt;br /&gt;
| Cleaned up IOPS tables, product naming conventions, section consistency with Unified CCE UCS wiki.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;26,&amp;amp;nbsp;2010 &lt;br /&gt;
| Validated links, performed spell check, noted areas still requiring additional technical review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;27,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following areas: Information for Partners, VMWare and Application Software Requirements, UCS Network Configuration, Configuring ESXi datastore.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;28,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following sections: Modified link to Information for Partners; Unified CVP 8.0(1) Support for Virtualization on the ESXi/UCS Platform (Modified bullet that referred to 'Distributed'; Coresidency (Deleted references to realtime; Modified last bullet regarding support on Blade.)&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;30,&amp;amp;nbsp;2010 &lt;br /&gt;
| Unified CVP Virtualization information posted to Unified Communications Virtualization Wiki.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;6,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated links to Unified CVP main page and CVP Reporting Server Configuration sub-page.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated Unified CVP Component Co-Residency section.&lt;br /&gt;
|-&lt;br /&gt;
| December&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated page to note that CVP 8.5(1) features the same level of support for virtualization that is available in CVP 8.0(1)&lt;br /&gt;
|-&lt;br /&gt;
| January&amp;amp;nbsp;12,&amp;amp;nbsp;2011 &lt;br /&gt;
| Added information on using CVP with C-Series servers.&lt;br /&gt;
|-&lt;br /&gt;
| September 1, 2011 &lt;br /&gt;
| Added support for ESXi 4.1.&lt;br /&gt;
|-&lt;br /&gt;
| February 6, 2012 &lt;br /&gt;
| Updated with the CVP support for TCP and UDP on UCS C-series servers.&lt;br /&gt;
|-&lt;br /&gt;
| July 6, 2012 &lt;br /&gt;
| Virtualization support for Release 9.0(1). &lt;br /&gt;
|-&lt;br /&gt;
| September 18, 2012 &lt;br /&gt;
| Unified CCX-Specific VM Installation Information&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==&lt;br /&gt;
&lt;br /&gt;
'''It is important that partners who are planning to sell UCS products on Unified Cisco Customer Voice Portal, read the [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise Unified CCE DocWiki] page.''' This page contains essential information for partners about the following: &lt;br /&gt;
&lt;br /&gt;
:*Partner Certification Requirements &lt;br /&gt;
:*UCS Server Ordering Information &lt;br /&gt;
:*Important Notes on Cisco UCS Service and Support&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
Starting with Release 9.0(1),all Unified CVP components can be deployed using the single OVA on any CVP supported virtulization hardware. Starting with Release 8.0(1), virtualization of the following deployments and Unified CVP components on Cisco Unified Communications Systems (UCS) B-Series hardware is supported: &lt;br /&gt;
&lt;br /&gt;
:*Unified CVP Call Server &lt;br /&gt;
:*Unified CVP VXML Server &lt;br /&gt;
:*Unified CVP Reporting Server &lt;br /&gt;
:*Unified CVP Ops Console&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following deployments and Unified CVP components have not been qualified and '''are not supported''' in virtualization: &lt;br /&gt;
&lt;br /&gt;
:*H323 Call flow Deployment &lt;br /&gt;
:*Distributed VXML Server and Call Server deployment where each server runs in a separate VM &lt;br /&gt;
:*All in one lab deployment with small reporting server&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following VMware features are not supported with Unified CVP: &lt;br /&gt;
&lt;br /&gt;
:*VMware Physical to Virtual migration &lt;br /&gt;
:*VMware Snapshots &lt;br /&gt;
:*VMware Consolidated Backup &lt;br /&gt;
:*VMware High Availability (HA) &lt;br /&gt;
:*VMware Site Recovery Manager &lt;br /&gt;
:*VMware vCenter Update Manager &lt;br /&gt;
:*VMware vCenter Converter&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Note: Unified CVP components are supported on the UCS platform only in a virtualized environment with ESXi server.''' &lt;br /&gt;
&lt;br /&gt;
== UCS Hardware Requirements  ==&lt;br /&gt;
&lt;br /&gt;
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located [[Unified Computing System Hardware#B-200_M1_Requirements|here]].&lt;br /&gt;
&lt;br /&gt;
Requirements for C210 hardware are located in the [[Unified Computing System Hardware]]. For UCS C210, CVP supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210M2-VCD2]). Other supported UCS models are at [[Unified Communications Virtualization Supported Applications#Contact_Center_Applications|Unified Communications Supported Applications]]&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1. &lt;br /&gt;
&lt;br /&gt;
For Unified CVP to work on UCS server, UCS firmware has to be 1.4(3c) or later.&lt;br /&gt;
&lt;br /&gt;
== VMware and Application Software Requirements  ==&lt;br /&gt;
&lt;br /&gt;
The following software requirements apply specifically to Unified Customer Voice Portal: &lt;br /&gt;
&lt;br /&gt;
:*VMware ESXi 4.1/5.0, minimum version 4.0U1. Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported. See [[Unified Communications VMware Requirements#VMware_vSphere_ESXi_Version_Support_for_Contact_Center_Applications|Unified Communications VMware requirements]] for a summary and further information. &lt;br /&gt;
:*You need to [[Disable LRO|disable LRO]] for ESXi 4.1/5.0. See [[Implementing Virtualization Deployments]] for more information. &lt;br /&gt;
:*The Windows, Informix, and other third party software requirements for the Unified CVP applications in the ESXi/UCS platform are the same as in the physical server. For such information, refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf Hardware and System Software Specification for Cisco Unified Customer Voice Portal, Release 8.5(1)]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP-Specific VM Installation Information  ==&lt;br /&gt;
&lt;br /&gt;
=== Migrating to Unified CVP Release 8.5(1) or 9.0(1) from Physical to Virtual Server  ===&lt;br /&gt;
&lt;br /&gt;
Migration to Unified CVP 8.5 or 9.0 from physical (MCS) server to any virtual server (UCS or non-UCS) server is not supported. &lt;br /&gt;
&lt;br /&gt;
== UCS Network Configuration  ==&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Customer Voice Portal (Unified CVP) on a virtualized platform, please see below. &lt;br /&gt;
&lt;br /&gt;
'''1) Network adapter setting modification on Reporting Server''' -The customers must modify the &amp;quot;Number of Receive Buffers&amp;quot; setting on the Reporting server to maximize full reporting and call load on the virtualized platform. If this setting is not modified after installing the OS, messages will get backed up on the CallServer and Message Queues will fill up resulting in a sharp drop in cps rate. &lt;br /&gt;
&lt;br /&gt;
*Set the &amp;quot;Number of Receive buffers&amp;quot; on the Reporting Server TCP settings to 4096 (max).&lt;br /&gt;
&lt;br /&gt;
Instructions: &lt;br /&gt;
&lt;br /&gt;
#On Reporting server, click on Control Panel-&amp;amp;gt;Network Connection. &lt;br /&gt;
#Right click on Network Connection. &lt;br /&gt;
#Click on advanced tab. &lt;br /&gt;
#Under property tab, select &amp;quot;Number of Receive Buffers&amp;quot;. &lt;br /&gt;
#In the Value pulldown, enter 4096. &lt;br /&gt;
#Restart the Reporting Server.&lt;br /&gt;
&lt;br /&gt;
'''2)&amp;amp;nbsp;'''The following table provides the transport protocols supported by different CVP versions on virtual and non-virtual (bare metal or MCS servers) deployments. The same transport protocol must be used on all call legs of the SIP comprehensive call flow deployments. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;'''SIP transport protocols supported across various deployments'''&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; width=&amp;quot;80%&amp;quot; align=&amp;quot;left&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Type of Hardware &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Releases prior to CVP 8.5(1) ES6 &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | CVP 8.5(1) ES6 or later releases&lt;br /&gt;
|-&lt;br /&gt;
| UCS C Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;amp;amp; UDP**&lt;br /&gt;
|-&lt;br /&gt;
| UCS B Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;lt;br&amp;gt;UDP***&lt;br /&gt;
|-&lt;br /&gt;
| Non Virtualized (bare metal) &lt;br /&gt;
| TCP &amp;amp;amp; UDP &lt;br /&gt;
| TCP &amp;amp;amp; UDP&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The session transport protocol can be set to tcp or udp in the POTS dialpeer. &amp;lt;br&amp;gt;Any other combinations of the transport protocols other than the ones listed above can cause call setup failures or abnormally long call setup times under heavy load. &lt;br /&gt;
&lt;br /&gt;
'''Footnote:&amp;lt;br&amp;gt;'''*&amp;amp;nbsp;Check the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications Docwiki supported Application] page for the Cisco UCS B-series and C-series hardware models supported by the Unified CVP.&amp;lt;br&amp;gt;**&amp;amp;nbsp;To avoid CPU utilization spikes under load conditions, the time synchronization between virtual machine and the ESX server must be disabled. To disable it, install VMware Tools in the virtual machine, in the Windows task bar, double click on the VM icon, in VMware Tools Properties window, uncheck '''Time synchronization between the virtual machine and the ESX Server''' checkbox.&amp;lt;br&amp;gt;***&amp;amp;nbsp;All the UCS&amp;amp;nbsp;servers listed on the&amp;amp;nbsp;[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications#Contact_Center_Applications Unified Communications Virtualization Supported Applications] page support UDP on both VMWare ESXi 4.1 and ESXi 5.0.&amp;lt;br&amp;gt;'''3) Cisco VLAN trunking to VMWare''' For information on best practices for Cisco VLAN trunking to VMware, refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US VMware website] &lt;br /&gt;
&lt;br /&gt;
=== Support for Unified Communications Manager Clustering Over the WAN with Unified CVP on UCS Hardware  ===&lt;br /&gt;
&lt;br /&gt;
You can deploy the Unified Communications Manager (Unified CM) Clustering Over the WAN deployment model with Unified CVP on UCS hardware. &lt;br /&gt;
&lt;br /&gt;
When you implement this deployment model, be sure to follow the best practices outlined in the section &amp;quot;Multiple Cisco Unified CM Clusters&amp;quot; in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Cisco Unified CVP Solution Reference Network Design (SRND)] &lt;br /&gt;
&lt;br /&gt;
In addition, note the following expectation for UCS hardware points of failure: &lt;br /&gt;
&lt;br /&gt;
*Multiple points of failure on the Unified CVP UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.&lt;br /&gt;
&lt;br /&gt;
==== B-Series Considerations  ====&lt;br /&gt;
&lt;br /&gt;
When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS M81KR Virtual Interface Card is mandatory. &lt;br /&gt;
&lt;br /&gt;
New B-Series deployments using Clustering Over the WAN should use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS B-Series Hardware with SAN  ==&lt;br /&gt;
&lt;br /&gt;
In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays. &lt;br /&gt;
&lt;br /&gt;
In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore. &lt;br /&gt;
&lt;br /&gt;
Keep the following considerations in mind when deploying Unified CVP applications on UCS B-series hardware with SAN: &lt;br /&gt;
&lt;br /&gt;
'''Compliance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*A dedicated SAN LUN and datastore must be used for Unified CVP database components. This means the CVP SAN LUNs cannot be shared by other applications. The SAN disk/storage array must be configured to meet the CVP IOPS requirements. The FC SAN solution is deployed in a shared environment where multiple applications are contending for storage access. The customers need to monitor the FC SAN performance and take appropriate actions to ensure the CVP IOPS and other UC IOPS requirements that share the same FC SAN systems are met. Should in the process of troubleshooting the SAN itself be identified as the problem, the customer must contact the system integrator or the SAN vendor for resolution.&lt;br /&gt;
&lt;br /&gt;
'''Design Considerations''' &lt;br /&gt;
&lt;br /&gt;
*The SAN must be designed in accordance with the UCS High Availability guidelines documented  [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html here]. &lt;br /&gt;
*The SAN design and configuration must meet the Unified CVP IOPS and Performance numbers described in the [[#Performance_Requirements|Performance Requirements]]. &lt;br /&gt;
*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines: &lt;br /&gt;
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, mis-behaving, or mis-configured disk array.&lt;br /&gt;
&lt;br /&gt;
'''Configuration Considerations''' &lt;br /&gt;
&lt;br /&gt;
*For UCS B-series, Virtual Machines must be stored on and booted from the SAN. &lt;br /&gt;
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.&lt;br /&gt;
*The SAN design and configuration must meet the following Windows performance counters on Unified CVP VMs: &lt;br /&gt;
**AverageDiskQueueLength must remain less than (1.5 * (the total number of disks in the array)). &lt;br /&gt;
**&amp;amp;nbsp;%Disktime must remain less than 60%.&lt;br /&gt;
*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CVP applications should be designed for the 95th percentile IOPS values published in this wiki. Refer to the Performance Requirements section below for additional information. For other UC applications, please follow their respective IOPS requirements and guidelines.&lt;br /&gt;
&lt;br /&gt;
'''Storage/Size Considerations''' &lt;br /&gt;
&lt;br /&gt;
*Unified CVP requires application storage to be on VMFS. Raw Device Mapping (RDM) is not supported. &lt;br /&gt;
*The total size of all Virtual Machines on a disk (total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.&lt;br /&gt;
&lt;br /&gt;
'''Input/Output Operations per Second (IOPS) Considerations''' &lt;br /&gt;
&lt;br /&gt;
*IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability. Refer to the Performance Requirements section below for additional information.&lt;br /&gt;
&lt;br /&gt;
'''Maintenance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*To help keep your system running most efficiently, schedule automatic database purging and database backups to run when your system is least busy.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS C-Series Hardware  ==&lt;br /&gt;
&lt;br /&gt;
This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks are either RAID 5 or RAID10. &lt;br /&gt;
&lt;br /&gt;
*Install ESXi 4.0/4.1 on the first disk array group (RAID 1 with disk 1 and disk 2) &lt;br /&gt;
*The creation of the virtual machine for the Reporting Server requires a large virtual disk size. Max disk size for a single VM to be 438GB for the large reporting server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;You must follow the steps described below to configure the ESXi data store block size to 2MB. &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi data store block size to 2MB: &lt;br /&gt;
&lt;br /&gt;
#Boot ESXi 4.0/4.1 and use VMware vSphere Client to connect to the ESXi host. &lt;br /&gt;
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 (or RAID-10 ) configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB. &lt;br /&gt;
#Right-click this data store and delete it. We will add the data store back in the following steps. &lt;br /&gt;
#Click on the “Add Storage…” and select the Disk/LUN. &lt;br /&gt;
#The data store that was just deleted will now be available to add, select it. &lt;br /&gt;
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.&lt;br /&gt;
&lt;br /&gt;
== Steps for Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines. &lt;br /&gt;
&lt;br /&gt;
#Install, setup, and configure the UCS Hardware. &lt;br /&gt;
#Configure the UCS Network. See reference at [[UCS Network Configuration for Unified CCE]]. &lt;br /&gt;
#Install and Boot VMWare ESXi. Refer to the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide]. &lt;br /&gt;
#Create the Unified CVP Virtual Machines from the OVA template available [http://www.cisco.com/cco/cisco/software/release.html?mdfid=270563413&amp;amp;flowid=5229&amp;amp;softwareid=280840592&amp;amp;release=9.0%281%29&amp;amp;relind=AVAILABLE&amp;amp;rellifecycle=&amp;amp;reltype=latest here].&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#Install Windows OS and Websphere Application Server (if using VXML Server with WAS) on the created Virtual Machines. (Note: Microsoft Windows Server 2003 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.) &lt;br /&gt;
#Install Unified CVP Software components on the configured Virtual Machines. See install reference for installing Unified CVP Components in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/installation/guide/CVP85install.pdf CVP Install and Upgrade guide]&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Capacities and VM Configuration Requirements  ==&lt;br /&gt;
&lt;br /&gt;
This section provides details associated with [[Unified Communications VMWare Requirements|VM requirements]] &lt;br /&gt;
&lt;br /&gt;
This table shows the supported Unified CVP components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Unified CVP component VMs. &lt;br /&gt;
&lt;br /&gt;
[[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Customer_Voice_Portal|Table containing Unified CVP component capacities and VM configuration requirements]]&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Co-Residency and Sample Deployments  ==&lt;br /&gt;
&lt;br /&gt;
You can have one or more Unified CVP VMs co-resident on the same ESXi server.&amp;amp;nbsp; However, you must follow the rules described below: &lt;br /&gt;
&lt;br /&gt;
:*You can have any number of Unified CVP virtual machines and combination of co-residency of Unified CVP virtual machines with other UC applications on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.&amp;amp;nbsp; &lt;br /&gt;
:*You must not have&amp;amp;nbsp;CPU overcommitted on the ESXi server that is running Unified CVP&amp;amp;nbsp;application components .&amp;amp;nbsp; The total number of vCPUs among all&amp;amp;nbsp;the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server.&amp;amp;nbsp; In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8. &lt;br /&gt;
:*You must not have&amp;amp;nbsp;memory overcommitted on the ESXi host that is running UC realtime applications.&amp;amp;nbsp; You must allocate&amp;amp;nbsp;minimum&amp;amp;nbsp;2GB of memory for the ESXi kernel.&amp;amp;nbsp; For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines.&amp;amp;nbsp; The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.&lt;br /&gt;
&lt;br /&gt;
:*VM co-residency with third party applications is not supported unless it is specifically described in this page. Currently, the Media Server for CVP is not recommended to be co-loaded on the CVP call server+vxml server VM.&lt;br /&gt;
&lt;br /&gt;
The Media Server VM can use a 2 vCPU VM profile like the CVP Operations Console VM profile. However, this is a third party VM and can be tailored to have a different VM profile to satisfy a particular CVP deployment need. &lt;br /&gt;
&lt;br /&gt;
On the other hand, CVP Media Server can be on the CVP Call Server+VXMl Server VM, providing the following conditions are met: &lt;br /&gt;
&lt;br /&gt;
- IIS is used; not Tomcat. &lt;br /&gt;
&lt;br /&gt;
- Audio prompts are cached on the VGW. &lt;br /&gt;
&lt;br /&gt;
- Logging is turned off on the MS&amp;amp;nbsp;media server.&lt;br /&gt;
&lt;br /&gt;
== Creating Virtual Machines from OVA VM Templates  ==&lt;br /&gt;
&lt;br /&gt;
Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances.&amp;amp;nbsp; Files in this format have an extension of .ova. The naming convention for the template is PRODUCT_COMPONENT_USER COUNT_VERSION_VMVER.ova &lt;br /&gt;
&lt;br /&gt;
Follow the instructions in the Downloading OVA Templates section below to download the OVA templates from cisco.com to a local datastore that vSphere Client can access. &lt;br /&gt;
&lt;br /&gt;
=== Downloading OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
:*Proceed to the [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%281%29&amp;amp;amp;mdfid=270563413&amp;amp;amp;sftType=Cisco+Customer+Voice+Portal+Software+Releases&amp;amp;amp;optPlat=&amp;amp;amp;nodecount=2&amp;amp;amp;edesignator=null&amp;amp;amp;modelName=Cisco+Unified+Customer+Voice+Portal&amp;amp;amp;treeMdfId=278875240&amp;amp;amp;treeName=Voice+and+Unified+Communications&amp;amp;amp;modifmdfid=null&amp;amp;amp;imname=&amp;amp;amp;hybrid=Y&amp;amp;amp;imst=N&amp;amp;amp;lr=Y Cisco Download Page for CVP].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*To download a single OVA file, click the '''Download File''' button next to that file. To download multiple OVA files, click the '''Add to Cart''' button next to each file that you want to download, then click on the '''Download Cart''' link. A Download Cart page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Read the Software License Agreement, then click the '''Agree''' button&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Creating Virtual Machines by Deploying the OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Customer_Voice_Portal Unified CVP OVA Templates List] &lt;br /&gt;
&lt;br /&gt;
In the vSphere client, perform the following steps to deploy the Virtual machines. &lt;br /&gt;
&lt;br /&gt;
#Highlight the host or cluster to which you wish the VM to be deployed. &lt;br /&gt;
#Select '''File''' &amp;amp;gt; '''Deploy OVF Template'''. &lt;br /&gt;
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''or''' click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''. &lt;br /&gt;
#Verify the details of the template, and click '''Next'''. &lt;br /&gt;
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''. &lt;br /&gt;
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''. &lt;br /&gt;
#Choose a virtual network for the VM, then click '''Next'''. &lt;br /&gt;
#Verify the deployment settings, then click '''Finish'''.&lt;br /&gt;
&lt;br /&gt;
=== Notes  ===&lt;br /&gt;
&lt;br /&gt;
:*VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. &lt;br /&gt;
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. &lt;br /&gt;
:*You cannot change the computing resource configuration of your VM at any time. &lt;br /&gt;
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates. &lt;br /&gt;
:*It is required that hyperthreading be enabled by default when running CVP on ESXi. ESXi Server hyperthread is enabled by default and this setting should not be modified. Please ensure all VM's with CVP servers has hyperthreading enabled.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remote Control of the Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. &lt;br /&gt;
&lt;br /&gt;
== Installing VMware Tools  ==&lt;br /&gt;
&lt;br /&gt;
The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system. &lt;br /&gt;
&lt;br /&gt;
== Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
You can install the Unified CVP components after the configuration of the VMs. Installation of these Unified CVP components on a VM is the same as the installation of these components on physical hardware. &lt;br /&gt;
&lt;br /&gt;
Refer to the Unified CVP documentation for the steps to install Unified CVP components. You can install the supported Virus Scan software, or any other software in the same way as on physical hardware. Refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf CVP Hardware and System Software Specification] for more information.&lt;br /&gt;
&lt;br /&gt;
== Configuring the ESXi Data Store Block Size for Administration and Data Server  ==&lt;br /&gt;
&lt;br /&gt;
The creation of the virtual machine for the Unified CVP Reporting Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store size to 438 GB for it to handle the Unified CVP Reporting Server data before you deploy the OVAs &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi for CVP Reporting server to RAID10 found at [[CVP Reporting Server Configuration|CVP Reporting Server Configuration]]&lt;br /&gt;
&lt;br /&gt;
== Performance Requirements  ==&lt;br /&gt;
&lt;br /&gt;
:*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. &lt;br /&gt;
:*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs. &lt;br /&gt;
:*VM snapshots are not supported in production since they have significant impact on system performance.&amp;amp;nbsp; &lt;br /&gt;
:*The&amp;amp;nbsp;SAN must be able to handle the following Unified CVP application disk I/O characteristics. &lt;br /&gt;
:*Enable hyperthreading on all ESXi servers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Performance Numbers on UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
'''HTTP Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label (VXML Server on Tomcat) &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''HTTPS Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== VM IOPS Measurement  ==&lt;br /&gt;
&lt;br /&gt;
'''IOPS Summary: (Unit in Number, Data are Blade-based)''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX &lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML Servers &lt;br /&gt;
| 380 &lt;br /&gt;
| 1536 &lt;br /&gt;
| 797&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 692 &lt;br /&gt;
| 3403 &lt;br /&gt;
| 2024&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Timekeeping Best Practices for Windows  ==&lt;br /&gt;
&lt;br /&gt;
You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;amp;cmd=displayKC&amp;amp;amp;externalId=1318 VMware KB:Timekeeping best practices for Windows]&lt;br /&gt;
&lt;br /&gt;
*ESXi hosts and domain controllers should synchronize the time from the same NTP source. &lt;br /&gt;
*When Unified Unified CVP virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time. &lt;br /&gt;
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== System Performance Monitoring Using Windows Perfmon Counters  ==&lt;br /&gt;
&lt;br /&gt;
You must comply with the best practices described in the section titled System Perormance Monitoring in the  [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Unified CVP SRND]. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color: rgb(255,215,0)&amp;quot; | '''Back to [[Unified Communications in a Virtualized Environment]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP</id>
		<title>Virtualization for Unified CVP</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP"/>
				<updated>2012-11-26T13:00:35Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Updates to this Page  ==&lt;br /&gt;
&lt;br /&gt;
The following is a list of significant updates to this page: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Date &lt;br /&gt;
! Update&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;24,&amp;amp;nbsp;2010 &lt;br /&gt;
| Distribution of Cisco UCS Unified CVP DocWiki for Tech review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;25,&amp;amp;nbsp;2010 &lt;br /&gt;
| Cleaned up IOPS tables, product naming conventions, section consistency with Unified CCE UCS wiki.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;26,&amp;amp;nbsp;2010 &lt;br /&gt;
| Validated links, performed spell check, noted areas still requiring additional technical review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;27,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following areas: Information for Partners, VMWare and Application Software Requirements, UCS Network Configuration, Configuring ESXi datastore.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;28,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following sections: Modified link to Information for Partners; Unified CVP 8.0(1) Support for Virtualization on the ESXi/UCS Platform (Modified bullet that referred to 'Distributed'; Coresidency (Deleted references to realtime; Modified last bullet regarding support on Blade.)&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;30,&amp;amp;nbsp;2010 &lt;br /&gt;
| Unified CVP Virtualization information posted to Unified Communications Virtualization Wiki.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;6,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated links to Unified CVP main page and CVP Reporting Server Configuration sub-page.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated Unified CVP Component Co-Residency section.&lt;br /&gt;
|-&lt;br /&gt;
| December&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated page to note that CVP 8.5(1) features the same level of support for virtualization that is available in CVP 8.0(1)&lt;br /&gt;
|-&lt;br /&gt;
| January&amp;amp;nbsp;12,&amp;amp;nbsp;2011 &lt;br /&gt;
| Added information on using CVP with C-Series servers.&lt;br /&gt;
|-&lt;br /&gt;
| September 1, 2011 &lt;br /&gt;
| Added support for ESXi 4.1.&lt;br /&gt;
|-&lt;br /&gt;
| February 6, 2012 &lt;br /&gt;
| Updated with the CVP support for TCP and UDP on UCS C-series servers.&lt;br /&gt;
|-&lt;br /&gt;
| July 6, 2012 &lt;br /&gt;
| Virtualization support for Release 9.0(1). &lt;br /&gt;
| September&amp;amp;nbsp;18;&amp;amp;nbsp;2012 &lt;br /&gt;
| Unified CCX-Specific VM Installation Information&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==&lt;br /&gt;
&lt;br /&gt;
'''It is important that partners who are planning to sell UCS products on Unified Cisco Customer Voice Portal, read the ''''''&amp;amp;lt;a href=&amp;quot;http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise&amp;quot;&amp;amp;gt;Unified CCE DocWiki page&amp;amp;lt;/a&amp;amp;gt;.''' &lt;br /&gt;
&lt;br /&gt;
This page contains essential information for partners about the following: &lt;br /&gt;
&lt;br /&gt;
:*Partner Certification Requirements &lt;br /&gt;
:*UCS Server Ordering Information &lt;br /&gt;
:*Important Notes on Cisco UCS Service and Support&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
Starting with Release 9.0(1),all Unified CVP components can be deployed using the single OVA on any CVP supported virtulization hardware. Starting with Release 8.0(1), virtualization of the following deployments and Unified CVP components on Cisco Unified Communications Systems (UCS) B-Series hardware is supported: &lt;br /&gt;
&lt;br /&gt;
:*Unified CVP Call Server &lt;br /&gt;
:*Unified CVP VXML Server &lt;br /&gt;
:*Unified CVP Reporting Server &lt;br /&gt;
:*Unified CVP Ops Console&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following deployments and Unified CVP components have not been qualified and '''are not supported''' in virtualization: &lt;br /&gt;
&lt;br /&gt;
:*H323 Call flow Deployment &lt;br /&gt;
:*Distributed VXML Server and Call Server deployment where each server runs in a separate VM &lt;br /&gt;
:*All in one lab deployment with small reporting server&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following VMware features are not supported with Unified CVP: &lt;br /&gt;
&lt;br /&gt;
:*VMware Physical to Virtual migration &lt;br /&gt;
:*VMware Snapshots &lt;br /&gt;
:*VMware Consolidated Backup &lt;br /&gt;
:*VMware High Availability (HA) &lt;br /&gt;
:*VMware Site Recovery Manager &lt;br /&gt;
:*VMware vCenter Update Manager &lt;br /&gt;
:*VMware vCenter Converter&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Note: Unified CVP components are supported on the UCS platform only in a virtualized environment with ESXi server.''' &lt;br /&gt;
&lt;br /&gt;
== UCS Hardware Requirements  ==&lt;br /&gt;
&lt;br /&gt;
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located &amp;amp;lt;a href=&amp;quot;Unified Computing System Hardware#B-200_M1_Requirements&amp;quot;&amp;amp;gt;here&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
&lt;br /&gt;
Requirements for C210 hardware are located in the &amp;amp;lt;a _fcknotitle=&amp;quot;true&amp;quot; href=&amp;quot;Unified Computing System Hardware&amp;quot;&amp;amp;gt;Unified Computing System Hardware&amp;amp;lt;/a&amp;amp;gt;. For UCS C210, CVP supports only the model (&amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html&amp;quot;&amp;amp;gt;UCS-C210M2-VCD2&amp;amp;lt;/a&amp;amp;gt;). Other supported UCS models are at &amp;amp;lt;a href=&amp;quot;Unified Communications Virtualization Supported Applications#Contact_Center_Applications&amp;quot;&amp;amp;gt;Unified Communications Supported Applications&amp;amp;lt;/a&amp;amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1. &lt;br /&gt;
&lt;br /&gt;
For Unified CVP to work on UCS server, UCS firmware has to be 1.4(3c) or later. &lt;br /&gt;
&lt;br /&gt;
== VMware and Application Software Requirements  ==&lt;br /&gt;
&lt;br /&gt;
The following software requirements apply specifically to Unified Customer Voice Portal: &lt;br /&gt;
&lt;br /&gt;
:*VMware ESXi 4.1/5.0, minimum version 4.0U1. Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported. See&amp;amp;nbsp;&amp;amp;lt;a href=&amp;quot;Unified Communications VMware Requirements#VMware_vSphere_ESXi_Version_Support_for_Contact_Center_Applications&amp;quot;&amp;amp;gt;Unified Communications VMware requirements&amp;amp;lt;/a&amp;amp;gt; for a summary and further information. &lt;br /&gt;
:*You need to &amp;amp;lt;a href=&amp;quot;Disable LRO&amp;quot;&amp;amp;gt;disable LRO for&amp;amp;lt;/a&amp;amp;gt; ESXi 4.1/5.0. See &amp;amp;lt;a _fcknotitle=&amp;quot;true&amp;quot; href=&amp;quot;Implementing Virtualization Deployments&amp;quot;&amp;amp;gt;Implementing Virtualization Deployments&amp;amp;lt;/a&amp;amp;gt; for more information. &lt;br /&gt;
:*The Windows, Informix, and other third party software requirements for the Unified CVP applications in the ESXi/UCS platform are the same as in the physical server. For such information, refer to the &amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf&amp;quot;&amp;amp;gt;Hardware and System Software Specification for Cisco Unified Customer Voice Portal, Release 8.5(1)&amp;amp;lt;/a&amp;amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unified CVP-Specific VM Installation Information  ==&lt;br /&gt;
&lt;br /&gt;
=== Migrating to Unified CVP Release 8.5(1) or 9.0(1) from Physical to Virtual Server  ===&lt;br /&gt;
&lt;br /&gt;
Migration to Unified CVP 8.5 or 9.0 from physical (MCS) server to any virtual server (UCS or non-UCS) server is not supported. &lt;br /&gt;
&lt;br /&gt;
== UCS Network Configuration  ==&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Customer Voice Portal (Unified CVP) on a virtualized platform, please see below. &lt;br /&gt;
&lt;br /&gt;
'''1) Network adapter setting modification on Reporting Server''' -The customers must modify the &amp;quot;Number of Receive Buffers&amp;quot; setting on the Reporting server to maximize full reporting and call load on the virtualized platform. If this setting is not modified after installing the OS, messages will get backed up on the CallServer and Message Queues will fill up resulting in a sharp drop in cps rate. &lt;br /&gt;
&lt;br /&gt;
*Set the &amp;quot;Number of Receive buffers&amp;quot; on the Reporting Server TCP settings to 4096 (max).&lt;br /&gt;
&lt;br /&gt;
Instructions: &lt;br /&gt;
&lt;br /&gt;
#On Reporting server, click on Control Panel-&amp;amp;gt;Network Connection. &lt;br /&gt;
#Right click on Network Connection. &lt;br /&gt;
#Click on advanced tab. &lt;br /&gt;
#Under property tab, select &amp;quot;Number of Receive Buffers&amp;quot;. &lt;br /&gt;
#In the Value pulldown, enter 4096. &lt;br /&gt;
#Restart the Reporting Server.&lt;br /&gt;
&lt;br /&gt;
'''2)&amp;amp;nbsp;'''The following table provides the transport protocols supported by different CVP versions on virtual and non-virtual (bare metal or MCS servers) deployments. The same transport protocol must be used on all call legs of the SIP comprehensive call flow deployments. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;'''SIP transport protocols supported across various deployments'''&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; width=&amp;quot;80%&amp;quot; align=&amp;quot;left&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Type of Hardware &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Releases prior to CVP 8.5(1) ES6 &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | CVP 8.5(1) ES6 or later releases&lt;br /&gt;
|-&lt;br /&gt;
| UCS C Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;amp;amp; UDP**&lt;br /&gt;
|-&lt;br /&gt;
| UCS B Series Virtualized* &lt;br /&gt;
| TCP &lt;br /&gt;
| TCP &amp;lt;br&amp;gt;UDP***&lt;br /&gt;
|-&lt;br /&gt;
| Non Virtualized (bare metal) &lt;br /&gt;
| TCP &amp;amp;amp; UDP &lt;br /&gt;
| TCP &amp;amp;amp; UDP&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The session transport protocol can be set to tcp or udp in the POTS dialpeer. &amp;lt;br&amp;gt;Any other combinations of the transport protocols other than the ones listed above can cause call setup failures or abnormally long call setup times under heavy load. &lt;br /&gt;
&lt;br /&gt;
'''Footnote:&amp;lt;br&amp;gt;'''*&amp;amp;nbsp;Check the Docwiki supported Application page: &amp;amp;lt;a href=&amp;quot;http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications&amp;quot;&amp;amp;gt;docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications &amp;amp;lt;/a&amp;amp;gt;for the Cisco UCS B-series and C-series hardware models supported by the Unified CVP.&amp;lt;br&amp;gt;**&amp;amp;nbsp;To avoid CPU utilization spikes under load conditions, the time synchronization between virtual machine and the ESX server must be disabled. To disable it, install VMware Tools in the virtual machine, in the Windows task bar, double click on the VM icon, in VMware Tools Properties window, uncheck '''Time synchronization between the virtual machine and the ESX Server''' checkbox.&amp;lt;br&amp;gt;***&amp;amp;nbsp;UDP supports all the UCS&amp;amp;nbsp;servers listed on the Unified Communications Virtualization Supported Applications page:&amp;amp;nbsp;&amp;amp;lt;a href=&amp;quot;http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications#Contact_Center_Applications&amp;quot;&amp;amp;gt;docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications#Contact_Center_Applications&amp;amp;lt;/a&amp;amp;gt;&amp;amp;nbsp;for&amp;amp;nbsp; Also, UDP supports UCS B-200 M2 servers on both&amp;amp;nbsp;VMWare ESXi 4.1 and ESXi 5.0.&amp;lt;br&amp;gt;'''3) Cisco VLAN trunking to VMWare''' For information on best practices for Cisco VLAN trunking to VMware, refer to the &amp;amp;lt;a href=&amp;quot;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;amp;cmd=displayKC&amp;amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;amp;cmd=displayKC&amp;amp;amp;externalId=1003806&amp;quot;&amp;amp;gt;VMware website&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
&lt;br /&gt;
=== Support for Unified Communications Manager Clustering Over the WAN with Unified CVP on UCS Hardware  ===&lt;br /&gt;
&lt;br /&gt;
You can deploy the Unified Communications Manager (Unified CM) Clustering Over the WAN deployment model with Unified CVP on UCS hardware. &lt;br /&gt;
&lt;br /&gt;
When you implement this deployment model, be sure to follow the best practices outlined in the section &amp;quot;Multiple Cisco Unified CM Clusters&amp;quot; in the &amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf&amp;quot;&amp;amp;gt;Cisco Unified CVP Solution Reference Network Design (SRND)&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
&lt;br /&gt;
In addition, note the following expectation for UCS hardware points of failure: &lt;br /&gt;
&lt;br /&gt;
*Multiple points of failure on the Unified CVP UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.&lt;br /&gt;
&lt;br /&gt;
==== B-Series Considerations  ====&lt;br /&gt;
&lt;br /&gt;
When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS M81KR Virtual Interface Card is mandatory. &lt;br /&gt;
&lt;br /&gt;
New B-Series deployments using Clustering Over the WAN should use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G. &lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS B-Series Hardware with SAN  ==&lt;br /&gt;
&lt;br /&gt;
In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays. &lt;br /&gt;
&lt;br /&gt;
In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore. &lt;br /&gt;
&lt;br /&gt;
Keep the following considerations in mind when deploying Unified CVP applications on UCS B-series hardware with SAN: &lt;br /&gt;
&lt;br /&gt;
'''Compliance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*A dedicated SAN LUN and datastore must be used for Unified CVP database components. This means the CVP SAN LUNs cannot be shared by other applications. The SAN disk/storage array must be configured to meet the CVP IOPS requirements. The FC SAN solution is deployed in a shared environment where multiple applications are contending for storage access. The customers need to monitor the FC SAN performance and take appropriate actions to ensure the CVP IOPS and other UC IOPS requirements that share the same FC SAN systems are met. Should in the process of troubleshooting the SAN itself be identified as the problem, the customer must contact the system integrator or the SAN vendor for resolution.&lt;br /&gt;
&lt;br /&gt;
'''Design Considerations''' &lt;br /&gt;
&lt;br /&gt;
*The SAN must be designed in accordance with the UCS High Availability guidelines documented at &amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html&amp;quot;&amp;amp;gt;http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
*The SAN design and configuration must meet the Unified CVP IOPS and Performance numbers described in the &amp;amp;lt;a href=&amp;quot;#Performance_Requirements&amp;quot;&amp;amp;gt;Performance Requirements&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines: &lt;br /&gt;
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, mis-behaving, or mis-configured disk array.&lt;br /&gt;
&lt;br /&gt;
'''Configuration Considerations''' &lt;br /&gt;
&lt;br /&gt;
*For UCS B-series, Virtual Machines must be stored on and booted from the SAN. &lt;br /&gt;
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.&lt;br /&gt;
*The SAN design and configuration must meet the following Windows performance counters on Unified CVP VMs: &lt;br /&gt;
**AverageDiskQueueLength must remain less than (1.5 * (the total number of disks in the array)). &lt;br /&gt;
**&amp;amp;nbsp;%Disktime must remain less than 60%.&lt;br /&gt;
*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CVP applications should be designed for the 95th percentile IOPS values published in this wiki. Refer to the Performance Requirements section below for additional information. For other UC applications, please follow their respective IOPS requirements and guidelines.&lt;br /&gt;
&lt;br /&gt;
'''Storage/Size Considerations''' &lt;br /&gt;
&lt;br /&gt;
*Unified CVP requires application storage to be on VMFS. Raw Device Mapping (RDM) is not supported. &lt;br /&gt;
*The total size of all Virtual Machines on a disk (total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.&lt;br /&gt;
&lt;br /&gt;
'''Input/Output Operations per Second (IOPS) Considerations''' &lt;br /&gt;
&lt;br /&gt;
*IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability. Refer to the Performance Requirements section below for additional information.&lt;br /&gt;
&lt;br /&gt;
'''Maintenance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*To help keep your system running most efficiently, schedule automatic database purging and database backups to run when your system is least busy.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS C-Series Hardware  ==&lt;br /&gt;
&lt;br /&gt;
This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks are either RAID 5 or RAID10. &lt;br /&gt;
&lt;br /&gt;
*Install ESXi 4.0/4.1 on the first disk array group (RAID 1 with disk 1 and disk 2) &lt;br /&gt;
*The creation of the virtual machine for the Reporting Server requires a large virtual disk size. Max disk size for a single VM to be 438GB for the large reporting server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;You must follow the steps described below to configure the ESXi data store block size to 2MB. &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi data store block size to 2MB: &lt;br /&gt;
&lt;br /&gt;
#Boot ESXi 4.0/4.1 and use VMware vSphere Client to connect to the ESXi host. &lt;br /&gt;
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 (or RAID-10 ) configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB. &lt;br /&gt;
#Right-click this data store and delete it. We will add the data store back in the following steps. &lt;br /&gt;
#Click on the “Add Storage…” and select the Disk/LUN. &lt;br /&gt;
#The data store that was just deleted will now be available to add, select it. &lt;br /&gt;
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.&lt;br /&gt;
&lt;br /&gt;
== Steps for Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines. &lt;br /&gt;
&lt;br /&gt;
#Install, setup, and configure the UCS Hardware. &lt;br /&gt;
#Configure the UCS Network. See reference at &amp;amp;lt;a href=&amp;quot;Unified Contact Center Enterprise#UCS_Network_Configuration&amp;quot;&amp;amp;gt;UCS Network Configuration&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
#Install and Boot VMWare ESXi. Refer to the appropriate installation guide: &amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html&amp;quot;&amp;amp;gt;Cisco UCS B-Series Blade Servers VMware Installation Guide&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
#Create the Unified CVP Virtual Machines from the OVA template. OVA templates are available&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;a href=&amp;quot;http://www.cisco.com/cco/cisco/software/release.html?mdfid=270563413&amp;amp;amp;flowid=5229&amp;amp;amp;softwareid=280840592&amp;amp;amp;release=9.0%281%29&amp;amp;amp;relind=AVAILABLE&amp;amp;amp;rellifecycle=&amp;amp;amp;reltype=latest&amp;quot;&amp;amp;gt;[n]&amp;amp;lt;/a&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
#Install Windows OS and Websphere Application Server (if using VXML Server with WAS) on the created Virtual Machines. (Note: Microsoft Windows Server 2003 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.) &lt;br /&gt;
#Install Unified CVP Software components on the configured Virtual Machines. See install reference for installing Unified CVP Components in the &amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/installation/guide/CVP85install.pdf&amp;quot;&amp;amp;gt;Unified CVP Install and Upgrade guide&amp;amp;lt;/a&amp;amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Capacities and VM Configuration Requirements  ==&lt;br /&gt;
&lt;br /&gt;
This section provides details associated with &amp;amp;lt;a href=&amp;quot;Unified Communications VMWare Requirements&amp;quot;&amp;amp;gt;VM requirements&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
&lt;br /&gt;
This table shows the supported Unified CVP components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Unified CVP component VMs. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;a href=&amp;quot;Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Customer_Voice_Portal&amp;quot;&amp;amp;gt;Table containing Unified CVP component capacities and VM configuration requirements&amp;amp;lt;/a&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Co-Residency and Sample Deployments  ==&lt;br /&gt;
&lt;br /&gt;
You can have one or more Unified CVP VMs co-resident on the same ESXi server.&amp;amp;nbsp; However, you must follow the rules described below: &lt;br /&gt;
&lt;br /&gt;
:*You can have any number of Unified CVP virtual machines and combination of co-residency of Unified CVP virtual machines with other UC applications on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.&amp;amp;nbsp; &lt;br /&gt;
:*You must not have&amp;amp;nbsp;CPU overcommitted on the ESXi server that is running Unified CVP&amp;amp;nbsp;application components .&amp;amp;nbsp; The total number of vCPUs among all&amp;amp;nbsp;the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server.&amp;amp;nbsp; In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8. &lt;br /&gt;
:*You must not have&amp;amp;nbsp;memory overcommitted on the ESXi host that is running UC realtime applications.&amp;amp;nbsp; You must allocate&amp;amp;nbsp;minimum&amp;amp;nbsp;2GB of memory for the ESXi kernel.&amp;amp;nbsp; For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines.&amp;amp;nbsp; The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*VM co-residency with third party applications is not supported unless it is specifically described in this page. Currently, the Media Server for CVP is not recommended to be co-loaded on the CVP call server+vxml server VM.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Media Server VM can use a 2 vCPU VM profile like the CVP Operations Console VM profile. However, this is a third party VM and can be tailored to have a different VM profile to satisfy a particular CVP deployment need. &lt;br /&gt;
&lt;br /&gt;
On the other hand, CVP Media Server can be on the CVP Call Server+VXMl Server VM, providing the following conditions are met: &lt;br /&gt;
&lt;br /&gt;
- IIS is used; not Tomcat. &lt;br /&gt;
&lt;br /&gt;
- Audio prompts are cached on the VGW. &lt;br /&gt;
&lt;br /&gt;
- Logging is turned off on the MS&amp;amp;nbsp;media server. &lt;br /&gt;
&lt;br /&gt;
== Creating Virtual Machines from OVA VM Templates  ==&lt;br /&gt;
&lt;br /&gt;
Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances.&amp;amp;nbsp; Files in this format have an extension of .ova. The naming convention for the template is PRODUCT_COMPONENT_USER COUNT_VERSION_VMVER.ova &lt;br /&gt;
&lt;br /&gt;
Follow the instructions in the Downloading OVA Templates section below to download the OVA templates from cisco.com to a local datastore that vSphere Client can access. &lt;br /&gt;
&lt;br /&gt;
=== Downloading OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
:*Proceed to the &amp;amp;lt;a href=&amp;quot;http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%281%29&amp;amp;amp;mdfid=270563413&amp;amp;amp;sftType=Cisco+Customer+Voice+Portal+Software+Releases&amp;amp;amp;optPlat=&amp;amp;amp;nodecount=2&amp;amp;amp;edesignator=null&amp;amp;amp;modelName=Cisco+Unified+Customer+Voice+Portal&amp;amp;amp;treeMdfId=278875240&amp;amp;amp;treeName=Voice+and+Unified+Communications&amp;amp;amp;modifmdfid=null&amp;amp;amp;imname=&amp;amp;amp;hybrid=Y&amp;amp;amp;imst=N&amp;amp;amp;lr=Y&amp;quot;&amp;amp;gt;Cisco Download Page for CVP&amp;amp;lt;/a&amp;amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*To download a single OVA file, click the '''Download File''' button next to that file. To download multiple OVA files, click the '''Add to Cart''' button next to each file that you want to download, then click on the '''Download Cart''' link. A Download Cart page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Read the Software License Agreement, then click the '''Agree''' button&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Creating Virtual Machines by Deploying the OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;a href=&amp;quot;http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Customer_Voice_Portal&amp;quot;&amp;amp;gt;Unified CVP OVA Templates List&amp;amp;lt;/a&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
In the vSphere client, perform the following steps to deploy the Virtual machines. &lt;br /&gt;
&lt;br /&gt;
#Highlight the host or cluster to which you wish the VM to be deployed. &lt;br /&gt;
#Select '''File''' &amp;amp;gt; '''Deploy OVF Template'''. &lt;br /&gt;
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''or''' click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''. &lt;br /&gt;
#Verify the details of the template, and click '''Next'''. &lt;br /&gt;
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''. &lt;br /&gt;
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''. &lt;br /&gt;
#Choose a virtual network for the VM, then click '''Next'''. &lt;br /&gt;
#Verify the deployment settings, then click '''Finish'''.&lt;br /&gt;
&lt;br /&gt;
=== Notes  ===&lt;br /&gt;
&lt;br /&gt;
:*VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. &lt;br /&gt;
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. &lt;br /&gt;
:*You cannot change the computing resource configuration of your VM at any time. &lt;br /&gt;
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates. &lt;br /&gt;
:*It is required that hyperthreading be enabled by default when running CVP on ESXi. ESXi Server hyperthread is enabled by default and this setting should not be modified. Please ensure all VM's with CVP servers has hyperthreading enabled.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remote Control of the Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. &lt;br /&gt;
&lt;br /&gt;
== Installing VMware Tools  ==&lt;br /&gt;
&lt;br /&gt;
The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to the &amp;amp;lt;a href=&amp;quot;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;amp;cmd=displayKC&amp;amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;amp;cmd=displayKC&amp;amp;amp;externalId=1003806&amp;quot;&amp;amp;gt;VMware documentation&amp;amp;lt;/a&amp;amp;gt; for instructions on installing or upgrading VMware Tools on the VM with Windows operating system. &lt;br /&gt;
&lt;br /&gt;
== Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
You can install the Unified CVP components after the configuration of the VMs. Installation of these Unified CVP components on a VM is the same as the installation of these components on physical hardware. &lt;br /&gt;
&lt;br /&gt;
Refer to the Unified CVP documentation for the steps to install Unified CVP components. You can install the supported Virus Scan software, or any other software in the same way as on physical hardware. Refer to the &amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf&amp;quot;&amp;amp;gt;CVP Hardware and System Software Specification&amp;amp;lt;/a&amp;amp;gt; for more information. &lt;br /&gt;
&lt;br /&gt;
== Configuring the ESXi Data Store Block Size for Administration and Data Server  ==&lt;br /&gt;
&lt;br /&gt;
The creation of the virtual machine for the Unified CVP Reporting Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store size to 438 GB for it to handle the Unified CVP Reporting Server data before you deploy the OVAs &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi for CVP Reporting server to RAID10 found at &amp;amp;lt;a _fcknotitle=&amp;quot;true&amp;quot; href=&amp;quot;CVP Reporting Server Configuration&amp;quot;&amp;amp;gt;CVP Reporting Server Configuration&amp;amp;lt;/a&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Performance Requirements  ==&lt;br /&gt;
&lt;br /&gt;
:*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. &lt;br /&gt;
:*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs. &lt;br /&gt;
:*VM snapshots are not supported in production since they have significant impact on system performance.&amp;amp;nbsp; &lt;br /&gt;
:*The&amp;amp;nbsp;SAN must be able to handle the following Unified CVP application disk I/O characteristics. &lt;br /&gt;
:*Enable hyperthreading on all ESXi servers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;/dd&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Performance Numbers on UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
'''HTTP Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label (VXML Server on Tomcat) &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''HTTPS Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== VM IOPS Measurement  ==&lt;br /&gt;
&lt;br /&gt;
'''IOPS Summary: (Unit in Number, Data are Blade-based)''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX &lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML Servers &lt;br /&gt;
| 380 &lt;br /&gt;
| 1536 &lt;br /&gt;
| 797&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 692 &lt;br /&gt;
| 3403 &lt;br /&gt;
| 2024&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Timekeeping Best Practices for Windows  ==&lt;br /&gt;
&lt;br /&gt;
You should follow the best practices outlined in the VMware Knowledge Base article &amp;amp;lt;a href=&amp;quot;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;amp;cmd=displayKC&amp;amp;amp;externalId=1318&amp;quot;&amp;amp;gt;VMware KB: Timekeeping best practices for Windows&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
&lt;br /&gt;
*ESXi hosts and domain controllers should synchronize the time from the same NTP source. &lt;br /&gt;
*When Unified Unified CVP virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time. &lt;br /&gt;
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== System Performance Monitoring Using Windows Perfmon Counters  ==&lt;br /&gt;
&lt;br /&gt;
You must comply with the best practices described in the &amp;amp;lt;a href=&amp;quot;http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf&amp;quot;&amp;amp;gt;SRND section System Performance Monitoring&amp;amp;lt;/a&amp;amp;gt;. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color: rgb(255,215,0)&amp;quot; | '''Back to:''' &amp;amp;lt;a href=&amp;quot;Unified Communications in a Virtualized Environment&amp;quot;&amp;amp;gt;Unified Communications in a Virtualized Environment&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;a _fcknotitle=&amp;quot;true&amp;quot; href=&amp;quot;Category:Unified_Customer_Voice_Portal&amp;quot;&amp;amp;gt;Unified_Customer_Voice_Portal&amp;amp;lt;/a&amp;amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-10-16T07:18:00Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary''' &lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes. &lt;br /&gt;
Consider the following scenario: &lt;br /&gt;
&lt;br /&gt;
When a TDM caller makes a call, a callback is offered and accepted. The callback is initiated and the caller answers the call. After 250-260 sec the callback entry on the Reporting Server portal gets erased and as a result no Courtesy Callback is offered. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause''' &lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the callback entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered. This is because the Gateway terminates the VRU leg by sending BYE which Unified CVP uses for any callback. As a result, Unified CVP erases all call details of the call and as result the callback is not made. It is found that a possible SIP session time out causes this behavior.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action''' &lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE: &lt;br /&gt;
  voice service voip&lt;br /&gt;
 sip&lt;br /&gt;
 min-se 7200 session-expires 7200                                                                                             &lt;br /&gt;
&lt;br /&gt;
! &lt;br /&gt;
|-&lt;br /&gt;
! '''Note''' &lt;br /&gt;
| In addition to the above configuration the session expire in the CUCM should also be changed to a higher value (7200), otherwise the callback will fail in Unified CVP due to SIP error response 422(session expire value too low) from Gateway.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release''' &lt;br /&gt;
| Release 9.0(1)&lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #''' &lt;br /&gt;
| CSCua18769&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T08:14:38Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the callback entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
  voice service voip&lt;br /&gt;
  sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
 !&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T08:13:14Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the call entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
  voice service voip&lt;br /&gt;
  sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
 !&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T07:58:12Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the call entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
&lt;br /&gt;
  voice service voip&lt;br /&gt;
  sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
  !&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T07:50:01Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the call entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
  voice service voip&lt;br /&gt;
  sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
 !&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T07:47:03Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the call entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
  voice service voip&lt;br /&gt;
  sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
   !&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T07:33:08Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the call entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
  voice service voip&lt;br /&gt;
  sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
  !&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T07:32:06Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When EWT in the ICM is set more than 30 minutes, the call entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
  voice service voip&lt;br /&gt;
  sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
!&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"/>
				<updated>2012-08-30T07:29:41Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: Created page with &amp;quot;{| border=&amp;quot;1&amp;quot; |- ! '''Problem Summary''' | Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes. |- ! '''Possible Cause''' | Courtesy callback is not...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes, as the call entry on the Reporting Server gets erased.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be made on the Ingress gateway/CUBE:&lt;br /&gt;
voice service voip&lt;br /&gt;
sip&lt;br /&gt;
  min-se 7200 session-expires 7200&lt;br /&gt;
!&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)</id>
		<title>Troubleshooting Tips for Unified CVP 9.0(1)</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)"/>
				<updated>2012-08-29T14:11:34Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* General Troubleshooting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Back:''' [[Troubleshooting Unified Customer Voice Portal]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]] &lt;br /&gt;
&lt;br /&gt;
'''Print PDF:''' [[Create PDF for Unified CVP 9.0(1)]] &lt;br /&gt;
&lt;br /&gt;
The following tips were added by Cisco Documentation: &lt;br /&gt;
&lt;br /&gt;
= General Troubleshooting  =&lt;br /&gt;
&lt;br /&gt;
*[[Graceful shutdown does not work when Call Server is in partial service]]&lt;br /&gt;
&lt;br /&gt;
*[[Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes]]&lt;br /&gt;
&lt;br /&gt;
= Error Message  =&lt;br /&gt;
&lt;br /&gt;
*[[&amp;quot;Failed - Device is using an old Unified CVP version that does not support this operation&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes.</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes."/>
				<updated>2012-08-29T14:09:47Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /*  */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy Callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message'''&lt;br /&gt;
| NA&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| After 300 seconds, the callback entry on the Reporting Server gets cleared, and as result no Courtesy Callback  is offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be added in the Ingress gateway/CUBE:&lt;br /&gt;
   voice service voip&lt;br /&gt;
   sip&lt;br /&gt;
   min-se 7200 session-expires 7200&lt;br /&gt;
   !&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1)&lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes.</id>
		<title>Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes."/>
				<updated>2012-08-29T14:09:15Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: Created page with &amp;quot;== &amp;lt;Courtesy Callback is not offered, when EWT in the ICM is set more than 30 minutes&amp;gt; ==  {| border=&amp;quot;1&amp;quot; |- ! '''Problem Summary''' | Courtesy Callback is not offered, when EWT i...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== &amp;lt;Courtesy Callback is not offered, when EWT in the ICM is set more than 30 minutes&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Courtesy Callback is not offered, when EWT in the ICM is set more than 30 minutes.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message'''&lt;br /&gt;
| NA&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| After 300 seconds, the callback entry on the Reporting Server gets cleared, and as result no Courtesy Callback  is offered.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| The following configuration has to be added in the Ingress gateway/CUBE:&lt;br /&gt;
   voice service voip&lt;br /&gt;
   sip&lt;br /&gt;
   min-se 7200 session-expires 7200&lt;br /&gt;
   !&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1)&lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCua18769&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)</id>
		<title>Troubleshooting Tips for Unified CVP 9.0(1)</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)"/>
				<updated>2012-07-19T10:01:37Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Back:''' [[Troubleshooting Unified Customer Voice Portal]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]] &lt;br /&gt;
&lt;br /&gt;
'''Print PDF:''' [[Create PDF for Unified CVP 9.0(1)]] &lt;br /&gt;
&lt;br /&gt;
The following tips were added by Cisco Documentation: &lt;br /&gt;
&lt;br /&gt;
= General Troubleshooting  =&lt;br /&gt;
&lt;br /&gt;
*[[Graceful shutdown does not work when Call Server is in partial service]]&lt;br /&gt;
&lt;br /&gt;
= Error Message  =&lt;br /&gt;
&lt;br /&gt;
*[[&amp;quot;Failed - Device is using an old Unified CVP version that does not support this operation&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)</id>
		<title>Troubleshooting Tips for Unified CVP 9.0(1)</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)"/>
				<updated>2012-07-19T09:59:52Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* General Troubleshooting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Back:''' [[Troubleshooting Unified Customer Voice Portal]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]] &lt;br /&gt;
&lt;br /&gt;
'''Print PDF:''' [[Create PDF for Unified CVP 9.0(1)]] &lt;br /&gt;
&lt;br /&gt;
The following tips were added by Cisco Documentation: &lt;br /&gt;
&lt;br /&gt;
The following tips were added by Cisco documentation team&lt;br /&gt;
= General Troubleshooting  =&lt;br /&gt;
&lt;br /&gt;
*[[Graceful shutdown does not work when Call Server is in partial service]]&lt;br /&gt;
&lt;br /&gt;
= Error Message  =&lt;br /&gt;
&lt;br /&gt;
*[[&amp;quot;Failed - Device is using an old Unified CVP version that does not support this operation&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP</id>
		<title>Virtualization for Unified CVP</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CVP"/>
				<updated>2012-07-04T06:49:17Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Updates to this Page  ==&lt;br /&gt;
&lt;br /&gt;
The following is a list of significant updates to this page: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Date &lt;br /&gt;
! Update&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;24,&amp;amp;nbsp;2010 &lt;br /&gt;
| Distribution of Cisco UCS Unified CVP DocWiki for Tech review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;25,&amp;amp;nbsp;2010 &lt;br /&gt;
| Cleaned up IOPS tables, product naming conventions, section consistency with Unified CCE UCS wiki.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;26,&amp;amp;nbsp;2010 &lt;br /&gt;
| Validated links, performed spell check, noted areas still requiring additional technical review.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;27,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following areas: Information for Partners, VMWare and Application Software Requirements, UCS Network Configuration, Configuring ESXi datastore.&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;28,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated feedback to the following sections: Modified link to Information for Partners; Unified CVP 8.0(1) Support for Virtualization on the ESXi/UCS Platform (Modified bullet that referred to 'Distributed'; Coresidency (Deleted references to realtime; Modified last bullet regarding support on Blade.)&lt;br /&gt;
|-&lt;br /&gt;
| September&amp;amp;nbsp;30,&amp;amp;nbsp;2010 &lt;br /&gt;
| Unified CVP Virtualization information posted to Unified Communications Virtualization Wiki.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;6,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated links to Unified CVP main page and CVP Reporting Server Configuration sub-page.&lt;br /&gt;
|-&lt;br /&gt;
| October&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated Unified CVP Component Co-Residency section.&lt;br /&gt;
|-&lt;br /&gt;
| December&amp;amp;nbsp;8,&amp;amp;nbsp;2010 &lt;br /&gt;
| Updated page to note that CVP 8.5(1) features the same level of support for virtualization that is available in CVP 8.0(1)&lt;br /&gt;
|-&lt;br /&gt;
| January&amp;amp;nbsp;12,&amp;amp;nbsp;2011 &lt;br /&gt;
| Added information on using CVP with C-Series servers.&lt;br /&gt;
|-&lt;br /&gt;
| September 1, 2011 &lt;br /&gt;
| Added support for ESXi 4.1.&lt;br /&gt;
|-&lt;br /&gt;
| February 6, 2012 &lt;br /&gt;
| Updated with the CVP support for TCP and UDP on UCS C-series servers.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==&lt;br /&gt;
&lt;br /&gt;
'''It is important that partners who are planning to sell UCS products on Unified Cisco Customer Voice Portal, read the ''''''[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise Unified CCE DocWiki page].''' &lt;br /&gt;
&lt;br /&gt;
This page contains essential information for partners about the following: &lt;br /&gt;
&lt;br /&gt;
:*Partner Certification Requirements &lt;br /&gt;
:*UCS Server Ordering Information &lt;br /&gt;
:*Important Notes on Cisco UCS Service and Support&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
Starting with Release 8.0(1), virtualization of the following deployments and Unified CVP components on Cisco Unified Communications Systems (UCS) B-Series hardware is supported: &lt;br /&gt;
&lt;br /&gt;
:*Unified CVP Call Server &lt;br /&gt;
:*Unified CVP VXML Server &lt;br /&gt;
:*Unified CVP Reporting Server &lt;br /&gt;
:*Unified CVP Ops Console&lt;br /&gt;
&lt;br /&gt;
The following deployments and Unified CVP components have not been qualified and '''are not supported''' in virtualization: &lt;br /&gt;
&lt;br /&gt;
:*H323 Call flow Deployment &lt;br /&gt;
:*Distributed VXML Server and Call Server deployment where each server runs in a separate VM &lt;br /&gt;
:*All in one lab deployment with small reporting server&lt;br /&gt;
&lt;br /&gt;
The following VMware features are not supported with Unified CVP: &lt;br /&gt;
&lt;br /&gt;
:*VMware Physical to Virtual migration &lt;br /&gt;
:*VMware Snapshots &lt;br /&gt;
:*VMware Consolidated Backup &lt;br /&gt;
:*VMware High Availability (HA) &lt;br /&gt;
:*VMware Site Recovery Manager &lt;br /&gt;
:*VMware vCenter Update Manager &lt;br /&gt;
:*VMware vCenter Converter&lt;br /&gt;
&lt;br /&gt;
'''Note: Unified CVP components are supported on the UCS platform only in a virtualized environment with ESXi server.''' &lt;br /&gt;
&lt;br /&gt;
== UCS Hardware Requirements  ==&lt;br /&gt;
&lt;br /&gt;
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located [[Unified Computing System Hardware#B-200_M1_Requirements|here]]. &lt;br /&gt;
&lt;br /&gt;
Requirements for C210 hardware are located in the [[Unified Computing System Hardware]]. For UCS C210, CVP supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210M2-VCD2]). &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1.&lt;br /&gt;
&lt;br /&gt;
For Unified CVP to work on UCS server, UCS firmware has to be 1.4(3c) or later.&lt;br /&gt;
&lt;br /&gt;
== VMware and Application Software Requirements  ==&lt;br /&gt;
&lt;br /&gt;
The following software requirements apply specifically to Unified Customer Voice Portal: &lt;br /&gt;
&lt;br /&gt;
:*VMware ESXi 4.0/4.1, minimum version 4.0U1. Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported. You need to [[Disable LRO|disable LRO for]] ESXi 4.1. See [[Implementing Virtualization Deployments]] for more information. &lt;br /&gt;
:*The Windows, Informix, and other third party software requirements for the Unified CVP applications in the ESXi/UCS platform are the same as in the physical server. For such information, refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf Hardware and System Software Specification for Cisco Unified Customer Voice Portal, Release 8.5(1)].&lt;br /&gt;
&lt;br /&gt;
== UCS Network Configuration  ==&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Customer Voice Portal (Unified CVP) on a virtualized platform, please see below. &lt;br /&gt;
&lt;br /&gt;
'''1) Network adapter setting modification on Reporting Server''' -The customers must modify the &amp;quot;Number of Receive Buffers&amp;quot; setting on the Reporting server to maximize full reporting and call load on the virtualized platform. If this setting is not modified after installing the OS, messages will get backed up on the CallServer and Message Queues will fill up resulting in a sharp drop in cps rate. &lt;br /&gt;
&lt;br /&gt;
*Set the &amp;quot;Number of Receive buffers&amp;quot; on the Reporting Server TCP settings to 4096 (max).&lt;br /&gt;
&lt;br /&gt;
Instructions: &lt;br /&gt;
&lt;br /&gt;
#On Reporting server, click on Control Panel-&amp;amp;gt;Network Connection. &lt;br /&gt;
#Right click on Network Connection. &lt;br /&gt;
#Click on advanced tab. &lt;br /&gt;
#Under property tab, select &amp;quot;Number of Receive Buffers&amp;quot;. &lt;br /&gt;
#In the Value pulldown, enter 4096. &lt;br /&gt;
#Restart the Reporting Server.&lt;br /&gt;
&lt;br /&gt;
'''2)&amp;amp;nbsp;'''The following table provides the transport protocols supported by different CVP versions on virtual and non-virtual (bare metal or MCS servers) deployments. The same transport protocol must be used on all call legs of the SIP comprehensive call flow deployments. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;'''SIP transport protocols supported across various deployments'''&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; width=&amp;quot;80%&amp;quot; align=&amp;quot;left&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Type of Hardware &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | CVP 8.5(1) ES6 or later releases &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Releases prior to CVP 8.5(1) ES6&lt;br /&gt;
|-&lt;br /&gt;
| UCS C Series Virtualized* &lt;br /&gt;
| TCP &amp;amp;amp; UDP** &lt;br /&gt;
| TCP&lt;br /&gt;
|-&lt;br /&gt;
| UCS B Series Virtualized* &lt;br /&gt;
| TCP &amp;lt;br&amp;gt;UDP*** &lt;br /&gt;
| TCP&lt;br /&gt;
|-&lt;br /&gt;
| Non Virtualized (bare metal) &lt;br /&gt;
| TCP &amp;amp;amp; UDP &lt;br /&gt;
| TCP &amp;amp;amp; UDP&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The session transport protocol can be set to tcp or udp in the POTS dialpeer. &amp;lt;br&amp;gt;Any other combinations of the transport protocols other than the ones listed above can cause call setup failures or abnormally long call setup times under heavy load. &lt;br /&gt;
&lt;br /&gt;
'''Footnote:&amp;lt;br&amp;gt;'''*&amp;amp;nbsp;Check the Docwiki supported Application page: [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications ]for the Cisco UCS B-series and C-series hardware models supported by the Unified CVP.&amp;lt;br&amp;gt;**&amp;amp;nbsp;To avoid CPU utilization spikes under load conditions, the time synchronization between virtual machine and the ESX server must be disabled. To disable it, install VMware Tools in the virtual machine, in the Windows task bar, double click on the VM icon, in VMware Tools Properties window, uncheck '''Time synchronization between the virtual machine and the ESX Server''' checkbox.&amp;lt;br&amp;gt;***&amp;amp;nbsp;The UDP is supported on VMs on UCS B-200 M2 server with VMWare ESXi 4.1.&amp;amp;nbsp;The UDP support is not qualified on other UCS B-series models and VMWare ESXi versions.&amp;lt;br&amp;gt;'''3) Cisco VLAN trunking to VMWare''' For information on best practices for Cisco VLAN trunking to VMware, refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806 VMware website]. &lt;br /&gt;
&lt;br /&gt;
=== Support for Unified Communications Manager Clustering Over the WAN with Unified CVP on UCS Hardware  ===&lt;br /&gt;
&lt;br /&gt;
You can deploy the Unified Communications Manager (Unified CM) Clustering Over the WAN deployment model with Unified CVP on UCS hardware. &lt;br /&gt;
&lt;br /&gt;
When you implement this deployment model, be sure to follow the best practices outlined in the section &amp;quot;Multiple Cisco Unified CM Clusters&amp;quot; in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf Cisco Unified CVP Solution Reference Network Design (SRND)]. &lt;br /&gt;
&lt;br /&gt;
In addition, note the following expectation for UCS hardware points of failure: &lt;br /&gt;
&lt;br /&gt;
*Multiple points of failure on the Unified CVP UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.&lt;br /&gt;
&lt;br /&gt;
==== B-Series Considerations  ====&lt;br /&gt;
&lt;br /&gt;
When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS M81KR Virtual Interface Card is mandatory. &lt;br /&gt;
&lt;br /&gt;
New B-Series deployments using Clustering Over the WAN should use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS B-Series Hardware with SAN  ==&lt;br /&gt;
&lt;br /&gt;
In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays. &lt;br /&gt;
&lt;br /&gt;
In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore. &lt;br /&gt;
&lt;br /&gt;
Keep the following considerations in mind when deploying Unified CVP applications on UCS B-series hardware with SAN: &lt;br /&gt;
&lt;br /&gt;
'''Compliance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*A dedicated SAN LUN and datastore must be used for Unified CVP database components. This means the CVP SAN LUNs cannot be shared by other applications. The SAN disk/storage array must be configured to meet the CVP IOPS requirements. The FC SAN solution is deployed in a shared environment where multiple applications are contending for storage access. The customers need to monitor the FC SAN performance and take appropriate actions to ensure the CVP IOPS and other UC IOPS requirements that share the same FC SAN systems are met. Should in the process of troubleshooting the SAN itself be identified as the problem, the customer must contact the system integrator or the SAN vendor for resolution.&lt;br /&gt;
&lt;br /&gt;
'''Design Considerations''' &lt;br /&gt;
&lt;br /&gt;
*The SAN must be designed in accordance with the UCS High Availability guidelines documented at [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html]. &lt;br /&gt;
*The SAN design and configuration must meet the Unified CVP IOPS and Performance numbers described in the [[#Performance_Requirements|Performance Requirements]]. &lt;br /&gt;
*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines: &lt;br /&gt;
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, mis-behaving, or mis-configured disk array.&lt;br /&gt;
&lt;br /&gt;
'''Configuration Considerations''' &lt;br /&gt;
&lt;br /&gt;
*For UCS B-series, Virtual Machines must be stored on and booted from the SAN. &lt;br /&gt;
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.&lt;br /&gt;
*The SAN design and configuration must meet the following Windows performance counters on Unified CVP VMs: &lt;br /&gt;
**AverageDiskQueueLength must remain less than (1.5 * (the total number of disks in the array)). &lt;br /&gt;
**&amp;amp;nbsp;%Disktime must remain less than 60%.&lt;br /&gt;
*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CVP applications should be designed for the 95th percentile IOPS values published in this wiki. Refer to the Performance Requirements section below for additional information. For other UC applications, please follow their respective IOPS requirements and guidelines.&lt;br /&gt;
&lt;br /&gt;
'''Storage/Size Considerations''' &lt;br /&gt;
&lt;br /&gt;
*Unified CVP requires application storage to be on VMFS. Raw Device Mapping (RDM) is not supported. &lt;br /&gt;
*The total size of all Virtual Machines on a disk (total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.&lt;br /&gt;
&lt;br /&gt;
'''Input/Output Operations per Second (IOPS) Considerations''' &lt;br /&gt;
&lt;br /&gt;
*IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability. Refer to the Performance Requirements section below for additional information.&lt;br /&gt;
&lt;br /&gt;
'''Maintenance Considerations''' &lt;br /&gt;
&lt;br /&gt;
*To help keep your system running most efficiently, schedule automatic database purging and database backups to run when your system is least busy.&lt;br /&gt;
&lt;br /&gt;
== Notes for Deploying Unified CVP Applications on UCS C-Series Hardware  ==&lt;br /&gt;
&lt;br /&gt;
This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks are either RAID 5 or RAID10. &lt;br /&gt;
&lt;br /&gt;
*Install ESXi 4.0/4.1 on the first disk array group (RAID 1 with disk 1 and disk 2) &lt;br /&gt;
*The creation of the virtual machine for the Reporting Server requires a large virtual disk size. Max disk size for a single VM to be 438GB for the large reporting server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;You must follow the steps described below to configure the ESXi data store block size to 2MB. &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi data store block size to 2MB: &lt;br /&gt;
&lt;br /&gt;
#Boot ESXi 4.0/4.1 and use VMware vSphere Client to connect to the ESXi host. &lt;br /&gt;
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 (or RAID-10 ) configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB. &lt;br /&gt;
#Right-click this data store and delete it. We will add the data store back in the following steps. &lt;br /&gt;
#Click on the “Add Storage…” and select the Disk/LUN. &lt;br /&gt;
#The data store that was just deleted will now be available to add, select it. &lt;br /&gt;
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.&lt;br /&gt;
&lt;br /&gt;
== Steps for Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines. &lt;br /&gt;
&lt;br /&gt;
#Install, setup, and configure the UCS Hardware. &lt;br /&gt;
#Configure the UCS Network. See reference at [[Unified Contact Center Enterprise#UCS_Network_Configuration|UCS Network Configuration]]. &lt;br /&gt;
#Install and Boot VMWare ESXi. Refer to the appropriate installation guide: [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide]. &lt;br /&gt;
#Create the Unified CVP Virtual Machines from the OVA template. OVA templates are available [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%281%29&amp;amp;mdfid=270563413&amp;amp;sftType=Cisco+Customer+Voice+Portal+Software+Releases&amp;amp;optPlat=&amp;amp;nodecount=2&amp;amp;edesignator=null&amp;amp;modelName=Cisco+Unified+Customer+Voice+Portal&amp;amp;treeMdfId=278875240&amp;amp;treeName=Voice+and+Unified+Communications&amp;amp;modifmdfid=null&amp;amp;imname=&amp;amp;hybrid=Y&amp;amp;imst=N&amp;amp;lr=Y here] &lt;br /&gt;
#Install Windows OS and Websphere Application Server (if using VXML Server with WAS) on the created Virtual Machines. (Note: Microsoft Windows Server 2003 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.) &lt;br /&gt;
#Install Unified CVP Software components on the configured Virtual Machines. See install reference for installing Unified CVP Components in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/installation/guide/CVP85install.pdf Unified CVP Install and Upgrade guide].&lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Capacities and VM Configuration Requirements  ==&lt;br /&gt;
&lt;br /&gt;
This section provides details associated with [[Unified Communications VMWare Requirements|VM requirements]]. &lt;br /&gt;
&lt;br /&gt;
This table shows the supported Unified CVP components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Unified CVP component VMs. &lt;br /&gt;
&lt;br /&gt;
[[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Customer_Voice_Portal|Table containing Unified CVP component capacities and VM configuration requirements]] &lt;br /&gt;
&lt;br /&gt;
== Unified CVP Component Co-Residency and Sample Deployments  ==&lt;br /&gt;
&lt;br /&gt;
You can have one or more Unified CVP VMs co-resident on the same ESXi server.&amp;amp;nbsp; However, you must follow the rules described below: &lt;br /&gt;
&lt;br /&gt;
:*You can have any number of Unified CVP virtual machines and combination of co-residency of Unified CVP virtual machines with other UC applications on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.&amp;amp;nbsp; &lt;br /&gt;
:*You must not have&amp;amp;nbsp;CPU overcommitted on the ESXi server that is running Unified CVP&amp;amp;nbsp;application components .&amp;amp;nbsp; The total number of vCPUs among all&amp;amp;nbsp;the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server.&amp;amp;nbsp; In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8. &lt;br /&gt;
:*You must not have&amp;amp;nbsp;memory overcommitted on the ESXi host that is running UC realtime applications.&amp;amp;nbsp; You must allocate&amp;amp;nbsp;minimum&amp;amp;nbsp;2GB of memory for the ESXi kernel.&amp;amp;nbsp; For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines.&amp;amp;nbsp; The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.&lt;br /&gt;
&lt;br /&gt;
:*VM co-residency with third party applications is not supported unless it is specifically described in this page. Currently, the Media Server for CVP is not recommended to be co-loaded on the CVP call server+vxml server VM.&lt;br /&gt;
&lt;br /&gt;
The Media Server VM can use a 2 vCPU VM profile like the CVP Operations Console VM profile. However, this is a third party VM and can be tailored to have a different VM profile to satisfy a particular CVP deployment need. &lt;br /&gt;
&lt;br /&gt;
On the other hand, CVP Media Server can be on the CVP Call Server+VXMl Server VM, providing the following conditions are met: &lt;br /&gt;
&lt;br /&gt;
- IIS is used; not Tomcat. &lt;br /&gt;
&lt;br /&gt;
- Audio prompts are cached on the VGW. &lt;br /&gt;
&lt;br /&gt;
- Logging is turned off on the MS&amp;amp;nbsp;media server. &lt;br /&gt;
&lt;br /&gt;
== Creating Virtual Machines from OVA VM Templates  ==&lt;br /&gt;
&lt;br /&gt;
Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances.&amp;amp;nbsp; Files in this format have an extension of .ova. The naming convention for the template is PRODUCT_COMPONENT_USER COUNT_VERSION_VMVER.ova &lt;br /&gt;
&lt;br /&gt;
Follow the instructions in the Downloading OVA Templates section below to download the OVA templates from cisco.com to a local datastore that vSphere Client can access. &lt;br /&gt;
&lt;br /&gt;
=== Downloading OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
:*Proceed to the [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%281%29&amp;amp;mdfid=270563413&amp;amp;sftType=Cisco+Customer+Voice+Portal+Software+Releases&amp;amp;optPlat=&amp;amp;nodecount=2&amp;amp;edesignator=null&amp;amp;modelName=Cisco+Unified+Customer+Voice+Portal&amp;amp;treeMdfId=278875240&amp;amp;treeName=Voice+and+Unified+Communications&amp;amp;modifmdfid=null&amp;amp;imname=&amp;amp;hybrid=Y&amp;amp;imst=N&amp;amp;lr=Y Cisco Download Page for CVP].&lt;br /&gt;
&lt;br /&gt;
:*To download a single OVA file, click the '''Download File''' button next to that file. To download multiple OVA files, click the '''Add to Cart''' button next to each file that you want to download, then click on the '''Download Cart''' link. A Download Cart page appears.&lt;br /&gt;
&lt;br /&gt;
:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.&lt;br /&gt;
&lt;br /&gt;
:*Read the Software License Agreement, then click the '''Agree''' button&lt;br /&gt;
&lt;br /&gt;
:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.&lt;br /&gt;
&lt;br /&gt;
:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.&lt;br /&gt;
&lt;br /&gt;
=== Creating Virtual Machines by Deploying the OVA Templates  ===&lt;br /&gt;
&lt;br /&gt;
[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Customer_Voice_Portal Unified CVP OVA Templates List] &lt;br /&gt;
&lt;br /&gt;
In the vSphere client, perform the following steps to deploy the Virtual machines. &lt;br /&gt;
&lt;br /&gt;
#Highlight the host or cluster to which you wish the VM to be deployed. &lt;br /&gt;
#Select '''File''' &amp;amp;gt; '''Deploy OVF Template'''. &lt;br /&gt;
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''or''' click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''. &lt;br /&gt;
#Verify the details of the template, and click '''Next'''. &lt;br /&gt;
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''. &lt;br /&gt;
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''. &lt;br /&gt;
#Choose a virtual network for the VM, then click '''Next'''. &lt;br /&gt;
#Verify the deployment settings, then click '''Finish'''.&lt;br /&gt;
&lt;br /&gt;
=== Notes  ===&lt;br /&gt;
&lt;br /&gt;
:*VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. &lt;br /&gt;
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. &lt;br /&gt;
:*You cannot change the computing resource configuration of your VM at any time. &lt;br /&gt;
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates. &lt;br /&gt;
:*It is required that hyperthreading be enabled by default when running CVP on ESXi. ESXi Server hyperthread is enabled by default and this setting should not be modified. Please ensure all VM's with CVP servers has hyperthreading enabled.&lt;br /&gt;
&lt;br /&gt;
== Remote Control of the Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. &lt;br /&gt;
&lt;br /&gt;
== Installing VMware Tools  ==&lt;br /&gt;
&lt;br /&gt;
The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system. &lt;br /&gt;
&lt;br /&gt;
== Installing Unified CVP Components on Virtual Machines  ==&lt;br /&gt;
&lt;br /&gt;
You can install the Unified CVP components after the configuration of the VMs. Installation of these Unified CVP components on a VM is the same as the installation of these components on physical hardware. &lt;br /&gt;
&lt;br /&gt;
Refer to the Unified CVP documentation for the steps to install Unified CVP components. You can install the supported Virus Scan software, or any other software in the same way as on physical hardware. Refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp8_5/reference/guide/851_bom.pdf CVP Hardware and System Software Specification] for more information. &lt;br /&gt;
&lt;br /&gt;
== Configuring the ESXi Data Store Block Size for Administration and Data Server  ==&lt;br /&gt;
&lt;br /&gt;
The creation of the virtual machine for the Unified CVP Reporting Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store size to 438 GB for it to handle the Unified CVP Reporting Server data before you deploy the OVAs &lt;br /&gt;
&lt;br /&gt;
Steps to configure the ESXi for CVP Reporting server to RAID10 found at [[CVP Reporting Server Configuration]] &lt;br /&gt;
&lt;br /&gt;
== Performance Requirements  ==&lt;br /&gt;
&lt;br /&gt;
:*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. &lt;br /&gt;
:*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs. &lt;br /&gt;
:*VM snapshots are not supported in production since they have significant impact on system performance.&amp;amp;nbsp; &lt;br /&gt;
:*The&amp;amp;nbsp;SAN must be able to handle the following Unified CVP application disk I/O characteristics. &lt;br /&gt;
:*Enable hyperthreading on all ESXi servers.&lt;br /&gt;
&lt;br /&gt;
== Performance Numbers on UCS Platform  ==&lt;br /&gt;
&lt;br /&gt;
'''HTTP Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label (VXML Server on Tomcat) &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone with Req ICM Label on WAS &lt;br /&gt;
| 900 &lt;br /&gt;
| 10&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''HTTPS Performance Metrics''' &lt;br /&gt;
&lt;br /&gt;
*The following metrics are measured with full reporting&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Call flow &lt;br /&gt;
! Simultaneous Calls Supported &lt;br /&gt;
! Calls Per Second&lt;br /&gt;
|-&lt;br /&gt;
| SIP Comprehensive &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|-&lt;br /&gt;
| VXML Standalone on WAS &lt;br /&gt;
| 275 &lt;br /&gt;
| 3&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== VM IOPS Measurement  ==&lt;br /&gt;
&lt;br /&gt;
'''IOPS Summary: (Unit in Number, Data are Blade-based)''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! CVP Server &lt;br /&gt;
! Average &lt;br /&gt;
! MAX &lt;br /&gt;
! 95th Percentile&lt;br /&gt;
|-&lt;br /&gt;
| CS/VXML Servers &lt;br /&gt;
| 380 &lt;br /&gt;
| 1536 &lt;br /&gt;
| 797&lt;br /&gt;
|-&lt;br /&gt;
| Reporting Server &lt;br /&gt;
| 692 &lt;br /&gt;
| 3403 &lt;br /&gt;
| 2024&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Timekeeping Best Practices for Windows  ==&lt;br /&gt;
&lt;br /&gt;
You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1318 VMware KB: Timekeeping best practices for Windows]. &lt;br /&gt;
&lt;br /&gt;
*ESXi hosts and domain controllers should synchronize the time from the same NTP source. &lt;br /&gt;
*When Unified Unified CVP virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time. &lt;br /&gt;
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== System Performance Monitoring Using Windows Perfmon Counters  ==&lt;br /&gt;
&lt;br /&gt;
You must comply with the best practices described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/srnd/8_5x/cvp85srnd.pdf SRND section System Performance Monitoring]. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color: rgb(255,215,0)&amp;quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified_Customer_Voice_Portal]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service</id>
		<title>Graceful shutdown does not work when Call Server is in partial service</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service"/>
				<updated>2012-06-20T13:27:45Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Graceful shutdown does not work when Call Server is in partial service.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message'''&lt;br /&gt;
| In OAMP Call Server status shows as &amp;quot;UP&amp;quot; when actual Call server state is &amp;quot;Stopped&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
! '''Description'''&lt;br /&gt;
| Call Server goes to partial state when PIM goes down. When a graceful shutdown is performed in the partial state the above error message appears.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When a graceful shutdown is performed on a Call Server in partial state, it cannot perform the usual task of shutting down PIM and other services as it is already down and it goes to stopped state. However, call server windows service still shows running.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| When the Call Server is in partial service, administrator should always do a normal shutdown instead of graceful shutdown.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCtz61700'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service</id>
		<title>Graceful shutdown does not work when Call Server is in partial service</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service"/>
				<updated>2012-06-20T13:27:00Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Graceful shutdown does not work when Call Server is in partial service.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message'''&lt;br /&gt;
| In OAMP Call Server status shows as &amp;quot;UP&amp;quot; when actual Call server state is &amp;quot;Stopped&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
! '''Description'''&lt;br /&gt;
| Call Server goes to partial state when ICM PIM goes down. When a graceful shutdown is performed in the partial state the above error message appears.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When a graceful shutdown is performed on a Call Server in partial state, it cannot perform the usual task of shutting down PIM and other services as it is already down and it goes to stopped state. However, call server windows service still shows running.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| When the Call Server is in partial service, administrator should always do a normal shutdown instead of graceful shutdown.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCtz61700'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service</id>
		<title>Graceful shutdown does not work when Call Server is in partial service</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service"/>
				<updated>2012-06-20T13:26:38Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Graceful shutdown does not work when Call Server is in partial service.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message'''&lt;br /&gt;
| In OAMP Call Server status shows as &amp;quot;UP&amp;quot; when actual Call server state is &amp;quot;Stopped&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
! '''Description'''&lt;br /&gt;
| Callserver goes to partial state when ICM PIM goes down. When a graceful shutdown is performed in the partial state the above error message appears.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When a graceful shutdown is performed on a Call Server in partial state, it cannot perform the usual task of shutting down PIM and other services as it is already down and it goes to stopped state. However, call server windows service still shows running.&lt;br /&gt;
|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| When the Call Server is in partial service, administrator should always do a normal shutdown instead of graceful shutdown.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCtz61700'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service</id>
		<title>Graceful shutdown does not work when Call Server is in partial service</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Graceful_shutdown_does_not_work_when_Call_Server_is_in_partial_service"/>
				<updated>2012-06-20T13:25:34Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! '''Problem Summary'''&lt;br /&gt;
| Graceful shutdown does not work when Call Server is in partial service.&lt;br /&gt;
|-&lt;br /&gt;
! '''Error Message'''&lt;br /&gt;
| In OAMP Call Server status shows as &amp;quot;UP&amp;quot; when actual Call server state is &amp;quot;Stopped&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
! '''Description'''&lt;br /&gt;
| Callserver goes to partial state when ICM PIM goes down. When a graceful shutdown is performed in the partial state the above error message appears.&lt;br /&gt;
|-&lt;br /&gt;
! '''Possible Cause'''&lt;br /&gt;
| When a graceful shutdown is performed on a Call Server in partial state, it cannot perform the usual task of shutting down PIM and other services as it is already down and it goes to stopped state. However, call server windows service still shows running.|-&lt;br /&gt;
! '''Recommended Action'''&lt;br /&gt;
| When the Call Server is in partial service, administrator should always do a normal shutdown instead of graceful shutdown.&lt;br /&gt;
|-&lt;br /&gt;
! '''Release'''&lt;br /&gt;
| Release 9.0(1) &lt;br /&gt;
|-&lt;br /&gt;
! '''Associated CDETS #'''&lt;br /&gt;
| CSCtz61700'''&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Replace this entire line with the required category or categories.&amp;gt;&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)</id>
		<title>Troubleshooting Tips for Unified CVP 9.0(1)</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)"/>
				<updated>2012-06-17T12:39:47Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Agent Whisper */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Back:''' [[Troubleshooting Unified Customer Voice Portal]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]] &lt;br /&gt;
&lt;br /&gt;
'''Print PDF:''' [[Create PDF for Unified CVP 9.0(1)]] &lt;br /&gt;
&lt;br /&gt;
The following tips were added by Cisco Documentation: &lt;br /&gt;
&lt;br /&gt;
= General Troubleshooting  =&lt;br /&gt;
&lt;br /&gt;
*[[Graceful shutdown does not work when Call Server is in partial service]]&lt;br /&gt;
&lt;br /&gt;
= Error Message  =&lt;br /&gt;
&lt;br /&gt;
*[[&amp;quot;Failed - Device is using an old Unified CVP version that does not support this operation&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)</id>
		<title>Troubleshooting Tips for Unified CVP 9.0(1)</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)"/>
				<updated>2012-06-17T12:39:33Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Agent Greeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Back:''' [[Troubleshooting Unified Customer Voice Portal]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]] &lt;br /&gt;
&lt;br /&gt;
'''Print PDF:''' [[Create PDF for Unified CVP 9.0(1)]] &lt;br /&gt;
&lt;br /&gt;
The following tips were added by Cisco Documentation: &lt;br /&gt;
&lt;br /&gt;
= General Troubleshooting  =&lt;br /&gt;
&lt;br /&gt;
*[[Graceful shutdown does not work when Call Server is in partial service]]&lt;br /&gt;
&lt;br /&gt;
= Error Message  =&lt;br /&gt;
&lt;br /&gt;
*[[&amp;quot;Failed - Device is using an old Unified CVP version that does not support this operation&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
= Agent Whisper  =&lt;br /&gt;
&lt;br /&gt;
*[[Agent Whisper - Call Fails]] &lt;br /&gt;
*[[Agent Whisper - Poor Caller Rington Quality]] &lt;br /&gt;
*[[Caller Hears Silence Before the Greeting Plays]] &lt;br /&gt;
*[[Canned AG.ICMS Script Fails to Play VRU Script when the Call needs to be Queued]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - Call.WhisperAnnouncement variable set without]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - B2BUA is not configured]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - During Transfer Request]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - No Default Label Configured]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - Whisper Call Setup Failed]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - Whisper Prompt Playback Failed]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)</id>
		<title>Troubleshooting Tips for Unified CVP 9.0(1)</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Unified_CVP_9.0(1)"/>
				<updated>2012-06-05T09:34:40Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* General */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Back:''' [[Troubleshooting Unified Customer Voice Portal]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]] &lt;br /&gt;
&lt;br /&gt;
'''Print PDF:''' [[Create PDF for Unified CVP 9.0(1)]] &lt;br /&gt;
&lt;br /&gt;
The following tips were added by Cisco Documentation: &lt;br /&gt;
&lt;br /&gt;
= General Troubleshooting  =&lt;br /&gt;
&lt;br /&gt;
*[[Graceful shutdown does not work when Call Server is in partial service]]&lt;br /&gt;
&lt;br /&gt;
= Error Message  =&lt;br /&gt;
&lt;br /&gt;
*[[&amp;quot;Failed - Device is using an old Unified CVP version that does not support this operation&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
= Agent Greeting  =&lt;br /&gt;
&lt;br /&gt;
*[[Agent Desktop Does Not Enable Login]] &lt;br /&gt;
*[[Agent Greeting Enable/Disable Button is Grayed]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - ICM Router Event ID: 64 EnterpriseAgent PIM Event ID: 27]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - Agent PIM log has no route request]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - Agent greeting disabled for agent]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - CRITICAL: Failed to resolve hostname]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Error ID: 41]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Error ID: 42]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Error ID: 43]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Event ID: 36]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Event ID: 38]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Event ID: 40]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Event ID: 49]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Event ID: 52]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - EnterpriseAgent PIM Event ID: 57]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - ICM Router Error Code: 63 EnterpriseAgent PIM Event ID: 27]] &lt;br /&gt;
*[[Agent Greeting Fails to Play - ICM Router Event ID: 637]] &lt;br /&gt;
*[[Agent Greeting Playback Gets Cut Off]] &lt;br /&gt;
*[[Agent Greeting Record Application Fails]] &lt;br /&gt;
*[[Agent Greeting Recording Fails - Check Required Information,exit,no ftp server]] &lt;br /&gt;
*[[Agent Greeting Recording Fails - FTP Deployment Error,enter]] &lt;br /&gt;
*[[Agent Greeting Recording Fails - Record Greeting With Confirm,exit,max disconfirmed]] &lt;br /&gt;
*[[Agent Greeting Recording Fails - Record Greeting With Confirm,exit,max noinput]] &lt;br /&gt;
*[[Agent Greeting Recording Fails - Record Greeting With Confirm,exit,max nomatch]] &lt;br /&gt;
*[[Agent Greeting Recording Fails - Script aborts at the RunExternalScript node]] &lt;br /&gt;
*[[Agent Unable to Record Greeting - ICM Router Event ID: 63, 66 EnterpriseAgent PIM Event ID: 43]] &lt;br /&gt;
*[[Agent Unable to Record Greeting - ICM Router Event ID: 63, 66 EnterpriseAgent PIM Event ID: 44]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Agent Whisper  =&lt;br /&gt;
&lt;br /&gt;
*[[Agent Whisper - Call Fails]] &lt;br /&gt;
*[[Agent Whisper - Poor Caller Rington Quality]] &lt;br /&gt;
*[[Caller Hears Silence Before the Greeting Plays]] &lt;br /&gt;
*[[Canned AG.ICMS Script Fails to Play VRU Script when the Call needs to be Queued]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - Call.WhisperAnnouncement variable set without]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - B2BUA is not configured]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - During Transfer Request]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - No Default Label Configured]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - Whisper Call Setup Failed]] &lt;br /&gt;
*[[Whisper Announcement Fails to Play - Whisper Prompt Playback Failed]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_Whisper_Prompt_Playback_Failed</id>
		<title>Whisper Announcement Fails to Play - Whisper Prompt Playback Failed</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_Whisper_Prompt_Playback_Failed"/>
				<updated>2012-06-05T09:22:12Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Whisper Announcement Fails to Play - &amp;quot;Whisper Prompt Playback Failed&amp;quot; */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Whisper Announcement Fails to Play - &amp;quot;Whisper Prompt Playback Failed&amp;quot; ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper Announcement fails to play &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Central controller event viewer and Router log shows:&lt;br /&gt;
Unable to find Whisper Announcement media file &amp;lt;filename&amp;gt; &lt;br /&gt;
CVP logs show:&lt;br /&gt;
Whisper Prompt Playback failed. Check the media name and address. VXML gateway logs can provide more detail with 'deb voip appl err' trace on. [id:5010]&lt;br /&gt;
[ICM_EVENT_REPORT], dialogueId=119, sendSeqNo=4, eventId=ANSWER, causeCode=CAUSE_WHISPER_MEDIA_ERROR,, &lt;br /&gt;
&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper Announcement wav file was not found &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Check that the ICM script has the correct wav file listed and check that the file exists in the media server &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_Whisper_Call_Setup_Failed</id>
		<title>Whisper Announcement Fails to Play - Whisper Call Setup Failed</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_Whisper_Call_Setup_Failed"/>
				<updated>2012-06-05T09:21:18Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Whisper Announcement Fails to Play - &amp;quot;Whisper Call Setup Failed&amp;quot; */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Whisper Announcement Fails to Play - &amp;quot;Whisper Call Setup Failed&amp;quot; ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper Announcement fails to play &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
CVP logs show: &lt;br /&gt;
[INBOUND] Whisper Call Setup Failed. Check the routing and dial plan configuration. [id:5010] &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
ringtone/whisper DN is shutdown.&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Do &amp;quot;no shut&amp;quot; in the ringtone/whisper Dial Number.&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_No_Default_Label_Configured</id>
		<title>Whisper Announcement Fails to Play - No Default Label Configured</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_No_Default_Label_Configured"/>
				<updated>2012-06-05T09:20:34Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Whisper Announcement Fails to Play - No Default Label Configured */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Whisper Announcement Fails to Play - No Default Label Configured ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper fails to play on an internally routed transferred/conferenced call to another agent. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Router log (or Router log viewer) shows &amp;quot;No default label configured for &amp;lt;CCM PG routing client&amp;gt;&amp;quot; &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Since the route request in this call scenario originates from the agent, a type 10 VRU label must be configured for this routing client as well. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Configure a type 10 VRU label for the CCM PG routing client in addition to the VRU label configured for the VRU PG routing client. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_During_Transfer_Request</id>
		<title>Whisper Announcement Fails to Play - During Transfer Request</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_During_Transfer_Request"/>
				<updated>2012-06-05T09:19:57Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Whisper Announcement Fails to Play - During Transfer Request */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Whisper Announcement Fails to Play - During Transfer Request ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper fails to play on an internally routed transferred/conferenced call to another agent. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Call fails out of &amp;quot;Send to VRU&amp;quot; node or &amp;quot;Run External script&amp;quot; node at the start of the ICM script which runs as a result of the transfer request. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Missing Route Pattern to send the call to the CVP SIP trunk. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Configure a route pattern which matches the type 10 VRU label provided by ICM to send the call to the desired CVP SIP trunk. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_B2BUA_is_not_configured</id>
		<title>Whisper Announcement Fails to Play - B2BUA is not configured</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_B2BUA_is_not_configured"/>
				<updated>2012-06-05T09:19:12Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Whisper Announcement Fails to Play - &amp;quot;B2BUA is not configured...&amp;quot; ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper Announcement fails to play &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
CVP logs show: &lt;br /&gt;
%CVP_8_5_SIP-3-SIP_ERROR_SNMP: B2BUA is not configured with a route for making calls to [9191919100]. Please add this route. [id:5010]&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
missing static route &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
add a static route for the Whisper Dial Nunber (9191919100) &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_Call.WhisperAnnouncement_variable_set_without</id>
		<title>Whisper Announcement Fails to Play - Call.WhisperAnnouncement variable set without</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play_-_Call.WhisperAnnouncement_variable_set_without"/>
				<updated>2012-06-05T09:18:14Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Whisper Announcement Fails to Play - &amp;quot;Call.WhisperAnnouncement variable set without...&amp;quot; ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper Announcement fails to play &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Central Controller event viewer and Router log shows: &lt;br /&gt;
Call.WhisperAnnouncement variable set without enabling target re-query or targeted agent is not CUCM agent, Whisper Announcement will be disabled &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Requery was not enabled on the node which targeted the agent &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Requery must be enabled on the queue, select, queue to agent, etc. node. Enable requery to re-enable whisper. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play</id>
		<title>Whisper Announcement Fails to Play</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_Fails_to_Play"/>
				<updated>2012-06-05T09:17:22Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Whisper Announcement Fails to Play */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Whisper Announcement Fails to Play ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper fails to play on an internally routed transferred/conferenced call to another agent. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None.&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Call must be sent back to the VRU (CVP) within the ICM script which runs as a result of the transfer request. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Insert a &amp;quot;Send to VRU&amp;quot; node or &amp;quot;Run external script&amp;quot; node at the start of the ICM script which runs as a result of the transfer request. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Canned_AG.ICMS_Script_Fails_to_Play_VRU_Script_when_the_Call_needs_to_be_Queued</id>
		<title>Canned AG.ICMS Script Fails to Play VRU Script when the Call needs to be Queued</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Canned_AG.ICMS_Script_Fails_to_Play_VRU_Script_when_the_Call_needs_to_be_Queued"/>
				<updated>2012-06-05T09:16:33Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* The Canned AG.ICMS script fails to play VRU script when the call needs to be  queued */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Canned AG.ICMS script fails to play VRU script when the call needs to be  queued ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
media server is not set in the routing script &lt;br /&gt;
&lt;br /&gt;
CVP logs shows: &lt;br /&gt;
92: 10.86.136.245: Oct 01 2010 15:09:28.917 -0400: %CVP_8_5_IVR-3-CALL_ERROR:  CALLGUID=5A120D800001000000000002F288560A DNIS=155552191994 Media Fetch Error for URL=file://../MediaFiles/en-us/app/ICMWait4NextAvail.wav (Client: 10.86.139.70) [id:3023] &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Attempting to resolve hostname &lt;br /&gt;
[noexist.cisco.com] to IP address (gethostbyname). &lt;br /&gt;
The following trace message displayed in the CTI OS client log: &lt;br /&gt;
09/28/10 10:04:22.234 3688 CTI OS Softphone Thd( 176) CRITICAL: Failed to resolve hostname [noexixt.cisco.com] to IP address (gethostbyname). &lt;br /&gt;
&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Default media server needs to be configured in CVP &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
In CVP configuration, Device Management &amp;gt; Media server, add the media server IP address and configure FTP for Agent Greeting. &lt;br /&gt;
Also select the media server in the  Default Media Server list. Then click Set button to set it as default media server. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Caller_Hears_Silence_Before_the_Greeting_Plays</id>
		<title>Caller Hears Silence Before the Greeting Plays</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Caller_Hears_Silence_Before_the_Greeting_Plays"/>
				<updated>2012-06-05T09:14:40Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Caller hears silence before the greeting plays */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Caller hears silence before the greeting plays  ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Caller hears silence before the greeting plays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
The copying of Agent Greeting files to the media server is slow due to: &lt;br /&gt;
Large files are being transferred OR the network connection to the FTP server is slow OR there are multiple FTP servers. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
In CVP &amp;gt; Call Studio &amp;gt; FTP_Client Element, consider implementing VXML 'fetchaudio' functionality in the element before the FTP element. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Whisper_-_Poor_Caller_Ringtone_Quality</id>
		<title>Agent Whisper - Poor Caller Ringtone Quality</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Whisper_-_Poor_Caller_Ringtone_Quality"/>
				<updated>2012-06-05T09:13:59Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Poor Caller Ringtone Quality */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Poor Caller Ringtone Quality == &lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Caller experiences poor ring tone quality from CVP on the caller ringback leg of a Whisper Announcement call. The ring tone may sound simply like a series of clicks &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None.&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Media Termination Point is enabled on the SIP trunk in UNIFIED CM &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Disable MTP on the SIP trunk &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Whisper_Announcement_-_Call_Fails</id>
		<title>Whisper Announcement - Call Fails</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Whisper_Announcement_-_Call_Fails"/>
				<updated>2012-06-05T09:12:29Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Agent Whisper - Call Fails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Agent Whisper - Call Fails ==&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Whisper call fails. A Queue node fails where you would expect it to connect to the agent and play the whiser. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
&amp;quot;B2BUA is not configured for a route to 9191919100, please add this route.&amp;quot;appears in the CVP error log. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Media Termination Point is enabled on the SIP trunk in UNIFIED CM &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Modify your dial plan to cover the Whisper Announcement ring back and whisper service numbers (by default, 91919191 and 9191919100). &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Category:Unified_CVP,_Release_9.0</id>
		<title>Category:Unified CVP, Release 9.0</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Category:Unified_CVP,_Release_9.0"/>
				<updated>2012-06-05T09:09:50Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: Created page with &amp;quot;{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; !style=&amp;quot;background-color:#FFE0C8;&amp;quot;| Introduction  |- |This page lists all troubleshooting tips applicable to Unified CVP, Release 9.0(1). The init...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!style=&amp;quot;background-color:#FFE0C8;&amp;quot;| Introduction &lt;br /&gt;
|-&lt;br /&gt;
|This page lists all troubleshooting tips applicable to Unified CVP, Release 9.0(1). The initial list contains the tips listed in Unified CVP Release 9.0. &lt;br /&gt;
|-&lt;br /&gt;
|If you encounter the following scenarios, feel free to add to our initial list:&lt;br /&gt;
* You find a new, valid tip and would like to share it with other Unified Expert Advisor users. &lt;br /&gt;
* You discover an easier solution/process/workaround to an existing issue. &lt;br /&gt;
|-&lt;br /&gt;
|If you want to '''ask a question''', '''post a comment''', or '''discuss an issue''' regarding a specific article:&lt;br /&gt;
&lt;br /&gt;
::# Log in&lt;br /&gt;
::# Navigate to the article in question&lt;br /&gt;
::# Click the '''Discussion''' tab at the top of the page&lt;br /&gt;
::# Edit the Discussion page as described above under Editing&lt;br /&gt;
::# To start a different thread under a new subheading on the Discussion page, click the '''+''' tab at the top of the page instead of the Edit tab.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!style=&amp;quot;background-color:#FFE0C8;&amp;quot;|  '''Navigation''' &lt;br /&gt;
|-&lt;br /&gt;
|'''Back:''' [[Troubleshooting Unified Customer Voice Portal]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Category:Unified_CCE,_Release_9.0</id>
		<title>Category:Unified CCE, Release 9.0</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Category:Unified_CCE,_Release_9.0"/>
				<updated>2012-06-05T09:07:52Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: Created page with &amp;quot;{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; !style=&amp;quot;background-color:#FFE0C8;&amp;quot;| Introduction  |- |This page lists all troubleshooting tips applicable to Unified Expert Advisor, Release 9.0(1...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!style=&amp;quot;background-color:#FFE0C8;&amp;quot;| Introduction &lt;br /&gt;
|-&lt;br /&gt;
|This page lists all troubleshooting tips applicable to Unified Expert Advisor, Release 9.0(1). The initial list contains the tips listed in UCCE Release 9.0. &lt;br /&gt;
|-&lt;br /&gt;
|If you encounter the following scenarios, feel free to add to our initial list:&lt;br /&gt;
* You find a new, valid tip and would like to share it with other Unified Expert Advisor users. &lt;br /&gt;
* You discover an easier solution/process/workaround to an existing issue. &lt;br /&gt;
|-&lt;br /&gt;
|If you want to '''ask a question''', '''post a comment''', or '''discuss an issue''' regarding a specific article:&lt;br /&gt;
&lt;br /&gt;
::# Log in&lt;br /&gt;
::# Navigate to the article in question&lt;br /&gt;
::# Click the '''Discussion''' tab at the top of the page&lt;br /&gt;
::# Edit the Discussion page as described above under Editing&lt;br /&gt;
::# To start a different thread under a new subheading on the Discussion page, click the '''+''' tab at the top of the page instead of the Edit tab.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
!style=&amp;quot;background-color:#FFE0C8;&amp;quot;|  '''Navigation''' &lt;br /&gt;
|-&lt;br /&gt;
|'''Back:''' [[Troubleshooting Unified CCE]] &lt;br /&gt;
&lt;br /&gt;
'''Add tip:''' [[Create Contact Center Troubleshooting Tips]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Unable_to_Record_Greeting_-_ICM_Router_Event_ID:_63,_66_EnterpriseAgent_PIM_Event_ID:_44</id>
		<title>Agent Unable to Record Greeting - ICM Router Event ID: 63, 66 EnterpriseAgent PIM Event ID: 44</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Unable_to_Record_Greeting_-_ICM_Router_Event_ID:_63,_66_EnterpriseAgent_PIM_Event_ID:_44"/>
				<updated>2012-06-05T09:01:16Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Agent Unable to Record Greeting  =&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;3&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| '''Problem Summary''' &lt;br /&gt;
| &lt;br /&gt;
Agent Unable to Record Greeting&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| '''Error Message''' &lt;br /&gt;
| &lt;br /&gt;
When the Agent Greeting record button is pressed, desktop shows &amp;quot;Routing error while trying to record Agent Greeting.&amp;quot; ICM Router Event ID: 63, 66 EnterpriseAgent PIM Event ID: 44&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| '''Possible Cause''' &lt;br /&gt;
| &lt;br /&gt;
The script for this Dialed Number &amp;quot;RecordAgentGreeting&amp;quot; was not properly scheduled or &amp;quot;RecordAgentGreeting&amp;quot; DN is not associated with the script.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| '''Recommended Action''' &lt;br /&gt;
| &lt;br /&gt;
Associate &amp;quot;RecordAgentGreeting&amp;quot; DN with the proper script and the script is scheduled.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| '''Release''' &lt;br /&gt;
| &lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| '''Associated CDETS&amp;amp;nbsp;#''' &lt;br /&gt;
| &lt;br /&gt;
None.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified_CCE,_Release_9.0]] [[Category:Unified_CVP,_Release_9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Unable_to_Record_Greeting_-_ICM_Router_Event_ID:_63,_66_EnterpriseAgent_PIM_Event_ID:_43</id>
		<title>Agent Unable to Record Greeting - ICM Router Event ID: 63, 66 EnterpriseAgent PIM Event ID: 43</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Unable_to_Record_Greeting_-_ICM_Router_Event_ID:_63,_66_EnterpriseAgent_PIM_Event_ID:_43"/>
				<updated>2012-06-05T08:59:37Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: /* Agent Unable to Record Greeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Agent Unable to Record Greeting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent Unable to Record Greeting&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
When the Agent Greeting record button is pressed, desktop shows &amp;quot;No recording Dialed Number is configured.&amp;quot; &lt;br /&gt;
The Unified CCE Peripheral Gateway indicates &amp;quot;Failed to play Agent Greeting since the special dialed number 'Record Agent Greeting' is not configured on the routing client for the peripheral.&amp;quot; (EnterpriseAgent PIM Error ID: 43 ) &lt;br /&gt;
ICM Router Event ID: 63, 66 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
The Dialed Number &amp;quot;RecordAgentGreeting&amp;quot; was not properly configured. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Create the ICM Dialed Number &amp;quot;RecordAgentGreeting&amp;quot; for the correct peripheral and schedule an appropriate script for it. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Script_aborts_at_the_RunExternalScript_node</id>
		<title>Agent Greeting Recording Fails - Script aborts at the RunExternalScript node</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Script_aborts_at_the_RunExternalScript_node"/>
				<updated>2012-06-05T08:57:52Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Agent Greeting Recording Fails  ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent Greeting Recording Fails. &lt;br /&gt;
Script aborts at the RunExternalScript node that invokes the CVP recording application. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None.&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
The CVP ECC variables for recording are not created and set correctly in the routing script: &lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
1. If you are using the NON-default media server, check the user.microapp.media_server ECC variable is set correctly in the recording routing script. &lt;br /&gt;
2. Check the user.microapp.app_media_lib ECC variable is set correctly to the agent greeting path on the media server in the recording routing script. The default path should be &amp;quot;app/ag_greeting&amp;quot;. &lt;br /&gt;
3. Check the user.microapp.ToExtVXML[] ECC variable is set to the correct VXML application. The default should be &amp;quot;application=RecordAgentGreeting&amp;quot;. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Record_Greeting_With_Confirm,exit,max_nomatch</id>
		<title>Agent Greeting Recording Fails - Record Greeting With Confirm,exit,max nomatch</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Record_Greeting_With_Confirm,exit,max_nomatch"/>
				<updated>2012-06-05T08:57:16Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Agent Greeting Recording Fails =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent Greeting Recording Fails &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
VXMLServer/applications/RecordAgentGreeting/logs/ActivityLog shows: &lt;br /&gt;
Record Greeting With Confirm,exit,max_nomatch&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent entered a number other than 1 or 2 after recording their greeting &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent must enter 1 to confirm or 2 to re-record. Any other number will result in no_match error. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Record_Greeting_With_Confirm,exit,max_noinput</id>
		<title>Agent Greeting Recording Fails - Record Greeting With Confirm,exit,max noinput</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Record_Greeting_With_Confirm,exit,max_noinput"/>
				<updated>2012-06-05T08:56:29Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Agent Greeting Recording Fails =  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent Greeting Recording Fails &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
VXMLServer/applications/RecordAgentGreeting/logs/ActivityLog shows: &lt;br /&gt;
Record Greeting With Confirm,exit,max_noinput&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent did not confirm their recording. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent must press # when they are done recording and then press 1 to confirm their greeting &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Record_Greeting_With_Confirm,exit,max_disconfirmed</id>
		<title>Agent Greeting Recording Fails - Record Greeting With Confirm,exit,max disconfirmed</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_Record_Greeting_With_Confirm,exit,max_disconfirmed"/>
				<updated>2012-06-05T08:55:50Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Agent Greeting Recording Fails  =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent Greeting Recording Fails &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
VXMLServer/applications/RecordAgentGreeting/logs/ActivityLog shows: &lt;br /&gt;
Record Greeting With Confirm,exit,max_disconfirmed &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent tried to re-record their greeting too many times &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Start the Agent Greeting recording again&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	<entry>
		<id>http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_FTP_Deployment_Error,enter</id>
		<title>Agent Greeting Recording Fails - FTP Deployment Error,enter</title>
		<link rel="alternate" type="text/html" href="http://docwiki.cisco.com/wiki/Agent_Greeting_Recording_Fails_-_FTP_Deployment_Error,enter"/>
				<updated>2012-06-05T08:55:10Z</updated>
		
		<summary type="html">&lt;p&gt;Txavier: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Agent Greeting Recording Fails = &lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Problem Summary''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Agent Greeting Recording Fails &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Error Message''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
VXMLServer/applications/RecordAgentGreeting/logs/ActivityLog shows: &lt;br /&gt;
FTP Deployment Error,enter, &lt;br /&gt;
&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Possible Cause''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Unable to access FTP server because the ip is invalid or the username and password are incorrect &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Recommended Action''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Verify that the media server configuration (IP address, credentials) in CVP's OpsConsole Server is correct. Verify that a &amp;quot;Deploy Media Servers&amp;quot; operation has been executed in CVP's OpsConsole Server. &lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Release''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
Release 9.0(1)&lt;br /&gt;
&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt; &amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt; '''Associated CDETS&amp;amp;nbsp;#''' &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&lt;br /&gt;
None. &lt;br /&gt;
&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Unified CCE, Release 9.0]]&lt;br /&gt;
[[Category:Unified CVP, Release 9.0]]&lt;/div&gt;</summary>
		<author><name>Txavier</name></author>	</entry>

	</feed>