Virtualization for Unified CVP

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
m (1 revision)
(17 intermediate revisions not shown)
Line 40: Line 40:
| September 1, 2011  
| September 1, 2011  
| Added support for ESXi 4.1.
| Added support for ESXi 4.1.
 +
|-
 +
| February 6, 2012
 +
| Updated with the CVP support for TCP and UDP on UCS C-series servers.
 +
|-
 +
| July 6, 2012
 +
| Virtualization support for Release 9.0(1).
|}
|}
 +
 +
|}
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==
== Information for Partners about Cisco Unified CVP on UCS Deployment Certification and Ordering  ==
Line 54: Line 62:
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==
== Unified CVP Support for Virtualization on the ESXi/UCS Platform  ==
-
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:  
+
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:  
:*Unified CVP Call Server  
:*Unified CVP Call Server  
Line 83: Line 91:
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located [[Unified Computing System Hardware#B-200_M1_Requirements|here]].  
Requirements for Cisco Unified Customer Voice Portal using UCS B200 M1 hardware are located [[Unified Computing System Hardware#B-200_M1_Requirements|here]].  
-
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]).  
+
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]].<br>
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1.  
'''Note:''' Unified CVP does not support UCS C200 and UCS-C210-M1.  
 +
 +
For Unified CVP to work on UCS server, UCS firmware has to be 1.4(3c) or later.
== VMware and Application Software Requirements  ==
== VMware and Application Software Requirements  ==
Line 91: Line 101:
The following software requirements apply specifically to Unified Customer Voice Portal:  
The following software requirements apply specifically to Unified Customer Voice Portal:  
-
:*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.  
+
:*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&nbsp;[[Unified Communications VMware Requirements#VMware_vSphere_ESXi_Version_Support_for_Contact_Center_Applications|Unified Communications VMware requirements]] for a summary and further information.
 +
:*You need to [[Disable LRO|disable LRO for]] ESXi 4.1/5.0. See [[Implementing Virtualization Deployments]] for more information.  
:*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)].
:*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)].
Line 98: Line 109:
'''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.  
'''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.  
-
'''1) TCP Setting modification on Reporting Server''' It is highly recommended that customers modify the default "Number of Receive Buffers" 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.  
+
'''1) Network adapter setting modification on Reporting Server''' -The customers must modify the "Number of Receive Buffers" 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.  
*Set the "Number of Receive buffers" on the Reporting Server TCP settings to 4096 (max).
*Set the "Number of Receive buffers" on the Reporting Server TCP settings to 4096 (max).
Line 111: Line 122:
#Restart the Reporting Server.
#Restart the Reporting Server.
-
'''2) Use TCP protocol over UDP for SIP Comprehensive call flow as a SIP Best Practice''' Use TCP for SIP Comprehensive call flows. Using UDP may cause call setup failures or may result in abnormally long calls under heavy load. Typically TCP should be set on all call legs, but it is a requirement on the ingress leg. This can be set on the POTS dialpeer by setting the session transport to tcp.  
+
'''2)&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.  
-
'''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&cmd=displayKC&externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806 VMware website ].  
+
<u>'''SIP transport protocols supported across various deployments'''</u>:
 +
 
 +
{| border="1" cellspacing="1" cellpadding="1" width="80%" align="left"