DocWiki - User contributions [en]

How to Use the AFG with the Virtual Floppy Drive

2012-02-28T15:27:32Z

Kemacdon:

'''Go to: '''[[Ongoing Virtualization Operations and Maintenance|'''Ongoing Virtualization Operations and Maintenance''']]

'''Go to: [[Implementing Virtualization Deployments]]''' 

= Using the AFG and Virtual Floppy =

To use the platformConfig.xml file with a virtual machine requires the use of a virtual floppy drive on the virtual machine. 

The platformConfig.xml file can be generated here [http://www.cisco.com/web/cuc_afg/index.html http://www.cisco.com/web/cuc_afg/index.html]

{{note| After the Virtual Floppy image is created with the platformConfig.xml file in it the Virtual Machine boot order should be changed in order to avoid having to manually disconnect the floppy image in the middle of CUCM installation. If the boot order is not change, after the installer ejects the CDROM and reboots the Virtual Machine it will be stuck with "No Boot Disk Found" error while attempting to boot off the still connected Virtual Floppy Image. Set the boot order to CD-ROM Drive then Hard Drive then Removable Devices and Network boot}}

 

== Create A New Virtual Floppy Image ==

=== Windows ===

Follow this procedure to create a new virtual floppy image using the Windows platform.

#Download and install Winimage ([http://www.winimage.com/download.htm http://www.winimage.com/download.htm]). 
#In Winimage, select '''File '''> '''New'''.
#Select '''1.44 MB''' from ''Standard format'' and click '''OK'''.
#Drag the platformConfig.xml file onto the Winimae window.
#Click '''Yes '''when prompted to inject the file into Winimage.
#Select '''File '''> '''Save As'''.
#Select '''Virtual floppy image''' from the ''Save as type ''dropdown list.
#Enter a file name and click '''Save'''.

=== Linux Virtual Machine ===

#Create an empty floppy image of 1.44 MB as root: $ /sbin/mkfs.msdos -C <directory>/<imagefile.img> 1440 
#Create a new directory called floppy1: $ sudo mkdir /media/floppy1/ 
#Mount the directory: $ sudo mount -o loop /path/imagefile.img /media/floppy1/ 
#Copy the XML file to the mounted directory: $ cp platformConfig.xml /media/floppy1 
#Unmount the directory: $ umount /media/floppy1 

=== Mac OS X ===

#On the terminal dd if=/dev/zero bs=1024 count=1440 > floppy.img 
#Open Disk Utility Application. Go to File -> Open Disk Image -> floppy.img (Command + Option + O) You will get an error indicating "no mountable file systems) Click OK 
#The Floppy Image will be added to the list of disks select it and go to the Erase Tab 
#Change Format to MS-DOS (FAT) and Click Erase 
#You can now copy the XML file (platformConfig.xml) to the mounted floppy image and eject it when you are done 

== Upload a Virtual Floppy Image to a Datastore ==

Follow this procedure to upload a virtual floppy image to a datastore:

#Start the vSphere client.
#If the host uses:
##Remote storage (for example, SAN), then select '''View '''> '''Inventory '''> '''Datastores'''.
##Local storage (for example, internal hard drive), then select the host and click the '''Summary '''tab.
#Right-click on a datastore and select '''Browse Datastore'''.
#Navigate to the desired directory and click the '''Upload files to this datastore''' icon.
#Select '''Upload File'''.
#Select the Virtual Floppy Image created in the preceding procedure and click '''Open'''.
#Click '''Yes '''when upload/download operation warning window appears.
#Close the Datastore Browser window. 

== Mount a Virtual Floppy Image ==

Follow this procedure to mount a virtual floppy image:

#Start the vSphere client.
#Select a virtual machine.
#Select '''Inventory '''> '''Virtual Machine''' > '''Edit Settings'''.
#Select '''Floppy drive''' from the ''Hardware ''tab.
#Select '''Use existing floppy image in datastore'''.
#Select '''Browse'''.
#Select '''All files''' from the file type dropdown list, if the virtual floppy image does not use the .flp extension.
#Locate the virtual floppy image and click '''OK'''.
#Enable '''Connected '''and '''Connect at power on''' under ''Device Status''.
#Click '''OK'''.

{{note| As with fresh installs on physical hardware, make sure the CD/DVD device is at the top of the BIOS boot order.}} 

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Troubleshooting Tips for Cisco MediaSense 8.5

2012-02-06T14:47:07Z

Kemacdon: /* Administration */

'''Back:''' [[Troubleshooting Cisco MediaSense]]

'''Additional Troubleshooting Information''': [[Additional troubleshooting information for Cisco MediaSense 8.5]]

'''Add tip:''' [[Create Contact Center Troubleshooting Tips]]

'''Print PDF:''' [[Print Cisco MediaSense 8.5 Troubleshooting Tips]]

----

{{note | '''Cisco MediaSense product documentation reflects the fields and names used in the application user interfaces and application programming interfaces of this product. Effective Release 8.5(2), these names are restricted to Cisco MediaSense and Open Recording Architecture (ORA/ora).'''}}

----

The following tips were added by Cisco Documentation:

== API ==

*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]] 

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions

2012-02-06T14:44:09Z

Kemacdon: Created page with "== Saving an AXL service provider configuration, under certain pre-conditions, will cause an incorrect error message. == {| border="1" |- ! '''Problem Summary''' | Wh..."

== Saving an AXL service provider configuration, under certain pre-conditions, will cause an incorrect error message. ==

{| border="1"
|-
! '''Problem Summary'''
|
When configuring the AXL service Providers List in Administration > Unified CM Configuration, a misleading error message can appear given the following pre-conditions: 

#All AXL service providers are removed from the “Selected AXL service Providers” list 
#Click “Save” to save the configuration with the ''empty'' “Selected AXL service Providers” list 
#Click “OK” on the warning dialog that says "AXL Service Provider List cannot be empty" 
#Move AXL service Providers from the available list to the selected list and Click “Save” to save the configuration. At this point, the following incorrect error message (see below) will appear 

|-
! '''Error Message'''
|
"The AXL Service Provider credentials are incorrect. Verify your ip address, username, and password and re-submit."

''(''Note: This error message is wrong. The credentials are actually correct.) 

|-
! '''Possible Cause'''
| The incorrect message appears because the screen is not refreshed after the warning dialog box is closed. 
|-
! '''Recommended Action'''
| Ignore the message and click the “Reset” button to get the current configuration. 
|-
! '''Release'''
| Release 8.5(4) 
|-
! '''Associated CDETS #'''
| CSCtx75179 
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information

2012-01-27T16:25:59Z

Kemacdon:

== The “show db_synchronization status [db_ora_meta|db_ora_config]” command does not show information when executed on the primary ORA DB server ==

{| border="1"
|-
! '''Problem Summary'''
| When both ORA DB servers are up and you execute the CLI command “show db_synchronization status [db_ora_meta|db_ora_config]” on the primary ORA DB server, the command returns no status information and shows a CLI command prompt only.
 

|-
! '''Error Message'''
| None. 
|-
! '''Possible Cause'''
| When you execute the command, the results come from Informix, and Informix will populate the data from either server.
 

|-
! '''Recommended Action'''
| If both ORA primary and secondary DB servers are up, and you do not get any information by executing the command on the primary ORA DB, execute the command on the secondary ORA DB. If no information is returned by either server, the data is already in sync between the servers and no sync job needs to run. 
|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3), and  Release 8.5(4). 
|-
! '''Associated CDETS #'''
| None. 
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

Troubleshooting Tips for Cisco MediaSense 8.5

2012-01-26T23:23:54Z

Kemacdon:

'''Back:''' [[Troubleshooting Cisco MediaSense]]

'''Additional Troubleshooting Information''': [[Additional troubleshooting information for Cisco MediaSense 8.5]]

'''Add tip:''' [[Create Contact Center Troubleshooting Tips]]

'''Print PDF:''' [[Print Cisco MediaSense 8.5 Troubleshooting Tips]]

----

{{note | '''Cisco MediaSense product documentation reflects the fields and names used in the application user interfaces and application programming interfaces of this product. Effective Release 8.5(2), these names are restricted to Cisco MediaSense and Open Recording Architecture (ORA/ora).'''}}

----

The following tips were added by Cisco Documentation:

== API ==

*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]] 

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Database: Database not updated after event forwarding

2012-01-26T20:04:26Z

Kemacdon:

== Database not updated after event forwarding ==

{| border="1"
|-
! '''Problem Summary'''
|
When a client receives an event that was forwarded from the other application server and immediately issues a query to the forwarding server to get additional data related to the event, it does not see the updates that were reported in the event.

|-
! '''Error Message'''
|
None.

|-
! '''Possible Cause'''
|
The client is querying the wrong server. If the event is forwarded from the other server, there will be a flag in the event that indicates this. Whenever the client receives such a message and it wishes to immediately query for information related to that event, it must issue the query to the other server, not the forwarding server.

Event forwarding takes place in parallel with database replication. When an event is forwarded from the server in which a database change occurred, the recipient can be sure that the data on that server has already been updated. However, there is no guarantee that the forwarding server's database was also updated.

{{note| The forwarding node's database will be updated and the data will eventually be replicated.}}

|-
! '''Recommended Action'''
|
If the recipient (client) needs to query the metadata immediately after receiving an event, then the client should issue that query to the server which originated the event--not to the server which forwarded the event.

|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3), and Release 8.5(4).
|-
! '''Associated CDETS #'''
| None.
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

Configuration: Conversation after a transfer is not recorded on RT-Lite phones

2012-01-26T20:02:52Z

Kemacdon:

== Conversation after a transfer is not recorded on RT-Lite phones ==

{| border="1"
|-
! '''Problem Summary'''
| No media streams are recorded after a transfer is completed using the RT-Lite (6961) phone with G.729.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| Phone load version is not supported.
|-
! '''Recommended Action'''
| Upgrade to the latest phone load.
|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Releae 8.5(3), and Release 8.5(4).
|-
! '''Associated CDETS #'''
| CSCti71342.
|}

[[Category:Cisco_MediaSense,_Release_8.5]]

RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down

2012-01-25T21:08:56Z

Kemacdon:

== RTMT does not show alarm info if the primary node is down ==

{| border="1"
|-
! '''Problem Summary'''
| The Unified Real Time Monitoring Tool (Unified RTMT) is connected to the secondary node, but after logging in to RTMT, alarm information is not shown. Instead, an error is reported.
|-
! '''Error Message'''
| Error polling alert status - AMC service is down
|-
! '''Possible Cause'''
| By default, the Primary Collector for the Alert Manager and Collector Service (AMC) is configured on the primary node, and the Failover Collector is not active. If the primary node is down, there is no available collector to which RTMT can connect. 
|-
! '''Recommended Action'''
|
 

#When both nodes are in service, sign in to MediaSense Administration on the Primary node, and then enter: '''<nowiki>https://<ip address>:8443/ccmadmin/serviceParamEdit.do</nowiki> '''in the browser address field to access the Unified CM server parameter configuration page.
#Activate the Failover Collector for the Cisco AMC service.

|-
! '''Release'''
|  Release 8.5(1), Release 8.5(2), Release 8.5(3), and Release 8.5(4).
|-
! '''Associated CDETS #'''
|  CSCtx41763
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

Upgrade: Data out of sync after upgrade

2012-01-25T20:42:47Z

Kemacdon:

= Data out of sync after upgrade =

{| border="1"
|-
! '''Problem Summary'''
|
The primary server starts taking calls after the switch verson process completes and the secondary server is still runnning the older version of the software. After you switch the secondary server to the newer version of the software, the data may not be synchronized between the primary and secondary servers.

|-
! '''Error Message'''
|
Data is not synchronized between the primary database and secondary database.

|-
! '''Possible Cause'''
|
Mismatched software versions on the primary and secondary servers may cause this issue if the upgrade process is not completed on both servers.

|-
! '''Recommended Action'''
|
Issue the '''run db_reset_replication '''CLI command on the secondary server to synchronize data between both servers. Use the '''show db_synchronization status''' CLI command to check the data synchronization status.

|-
! '''Release'''
|
Release 8.5(3) and Release 8.5(4). 

|-
! '''Associated CDETS #'''
|
None.

|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

API: Incorrect session or participant duration

2012-01-25T19:38:09Z

Kemacdon:

== Incorrect session or participant duration ==

{| border="1"
|-
! '''Problem Summary'''
| Track, participant, or session duration is incorrect or negative (for example: "sessionDuration":-4776).
|-
! '''Error Message'''
| from /var/log/active/syslog/messages: <pre>Aug 23 02:51:05 pauems01 user 6 ilog_impl: Restarting NTP as time offset is -185.215622 msec.

Aug 23 02:51:07 pauems01 user 6 ilog_impl: NTP servers list: 10.192.254.11 10.192.254.1</pre><pre>Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.11, \
stratum 1, '''offset -185.225332''', delay 0.04140 23

Aug 02:51:07 ntpdate[17992]: step time server 10.192.254.11 ''offset -185.225332 sec'' (rc=0).</pre><pre>Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.1, \
stratum 2, '''offset 0.054938''', delay 0.02736 23

Aug 02:51:07 ntpdate[18001]: adjust time server 10.192.254.1 offset 0.054938 sec (rc=0). </pre>
|-
! '''Possible Cause'''
|
Incorrect duration could have several causes, unsynchronized NTP servers is a known possibility.

The Cisco MediaSense publisher server uses two NTP servers to synchronize time. However, the time on these NTP servers may not be synchronized. As a result, Cisco MediaSense servers switch their times based on the currently-synchronized NTP server.

|-
! '''Recommended Action'''
|
Verify that both NTP servers provide synchronized times.

|-
! '''Release'''
|
Release 8.5(1), Release 8.5(2), Release 8.5(3), and Release 8.5(4).

|-
! '''Associated CDETS #'''
|
None.

|}

[[Category:Cisco_MediaSense,_Release_8.5]]

Runtime: Media server rejects open RTSP session

2012-01-25T19:35:50Z

Kemacdon:

== Media server rejects request to open RTSP session ==

{| border="1"
|-
! '''Problem Summary'''
| The Media Service rejects an RTSP request to open a session, if the DESCRIBE request is received before the first RTP packet.
|-
! '''Error Message'''
| In response to the RTSP DESCRIBE request, you receive the following error:
<code>500 Server Error (Unable to open proxy)<code></code>

|-
! '''Possible Cause'''
| In response to a DESCRIBE request, the Media Service should return the codec details. The codec details will only be known after the Media Service receives the first RTP packet.
|-
! '''Recommended Action'''
| Repeat the DESCRIBE request.
|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3), and Release 8.5(4)
|-
! '''Associated CDETS #'''
| None.
|}

[[Category:Cisco_MediaSense,_Release_8.5]]

Runtime: MediaSense server is unable to keep up with incoming recordings

2012-01-25T18:08:35Z

Kemacdon:

== MediaSense server is unable to keep up with incoming recordings ==

{| border="1"
|-
! '''Problem Summary'''
| The Cisco MediaSense server is unable to keep up with the number of recordings it's supposed to capture.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| By default, if the battery backup is not present or not operational, the write cache is disabled on the RAID controllers in the C-Series. When the write cache is disabled, write throughput is lowered.
|-
! '''Recommended Action'''
| The RAID controllers in the C-Series have an optional battery backup for the write cache. Add the battery backup cache to achieve better performance.
|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3) and Release 8.5(4).
|-
! '''Associated CDETS #'''
| None.
|}

[[Category:Cisco_MediaSense,_Release_8.5]]

Installation: Installation halts with an unrecoverable error

2012-01-25T18:06:29Z

Kemacdon:

== The installation halts with an unrecoverable error ==

{| border="1"
|-
! '''Problem Summary'''
| The installation fails with an unrecoverable error. 
|-
! '''Error Message'''
| Installation has encountered an unrecoverable internal error 
|-
! '''Possible Cause'''
|
The VM Template or the VM configuration does not meet the requirements. See [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all the Software Download page] for a list of supported VM templates.

See the ''Unified MCP-Specific Information for OVA Templates'' section in the [[Virtualization for Cisco MediaSense]] website. 

|-
! '''Recommended Action'''
|
Verify that the VM configuration meets the minimum system requirements such as number of CPUs and other requirements specified in the read-me file for each supported VM template.

Cisco MediaSense, beginning with Release 8.5(2), only supports the VM templates listed in [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all the Software Download page]. 

|-
! '''Release'''
| Release 8.5(2), Release 8.5(3), and Release 8.5(4). 
|-
! '''Associated CDETS #'''
| None. 
|}

[[Category:Cisco_MediaSense,_Release_8.5]]

General: RTSP live monitoring sessions fail when using CUBE

2012-01-25T18:03:48Z

Kemacdon:

== RTSP live monitoring sessions fail when using CUBE ==

{| border="1"
|-
! '''Problem Summary'''
| When using a mixed load in a CUBE deployment, multiple RTSP live monitoring sessions failed (RTSP packets were dropped). Recordings may also sound very choppy on playback.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| CUBE may be using a lower Ethernet cable connection (for example, 100 MB connection) instead of the suggested 1 GB Ethernet cable connection. Under a heavy load, this connection may cause multiple IP packets to drop.
|-
! '''Recommended Action'''
| If your CUBE deployment is running heavy loads, verify that the Ethernet cable connecting CUBE to the switch is 1 GB. 
|-
! '''Release'''
| Release 8.5(3), Release 8.5(4).
|-
! '''Associated CDETS #'''
| None.
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

General: Performance issues as a result of hardware failure

2012-01-25T18:02:22Z

Kemacdon:

== Performance issues as a result of hardware failure ==

{| border="1"
|-
! '''Problem Summary'''
| You may see performance issues (like recording errors) when a hardware failure has occurred.
|-
! '''Error Message'''
| None. You start seeing recording errors more frequently.
|-
! '''Possible Cause'''
| Hardware failures: For example, the disk drives attached to your host begin failing (most frequently seen). 
|-
! '''Recommended Action'''
|
Perform the following checks: 

#Check the vSphere client.
#Look for alarms generated against the VM host where you see the failure.
#Replace the faulty hardware using the instructions applicable to your failure.

|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3), and Release 8.5(4).
|-
! '''Associated CDETS #'''
| None.
|}

[[Category:Cisco_MediaSense,_Release_8.5]]

Administration: Unknown request error display

2012-01-25T17:57:45Z

Kemacdon:

== Unknown request error display ==

{| border="1"
|-
! '''Problem Summary'''
| Once you successfully login to the Cisco MediaSense Administration, an unknown request error displays in the UI.
|-
! '''Error Message'''
| <pre>You have reached this page in error. Most likely you typed a wrong URL in the address bar of your browser.
If the problem persists, please contact your Administrator.</pre>
|-
! '''Possible Cause'''
|
This error is known to display if you login to the Cisco MediaSense Administration immediately after implementing the post-installation setup procedure. 

If you wait for a few minutes after the post-installation setup and then login to the Cisco MediaSense Administration, you may not see this error. 

|-
! '''Recommended Action'''
| Ignore this error and continue with your configuration. You only see this error once. You will not see this error when you login again.
|-
! '''Release'''
| Release 8.5(3), 8.5(4). 
|-
! '''Associated CDETS #'''
| None.
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

Administration: Unable to access Administration and Serviceability UI on a newly installed system

2012-01-25T17:55:03Z

Kemacdon:

== Unable to access Administration and Serviceability UI on a newly installed system ==

{| border="1"
|-
! '''Problem Summary'''
| Administrator cannot access Cisco MediaSense Administration and Cisco MediaSense Serviceability Administration on a newly installed system, if they do not use port numbers in the URLs.
|-
! '''Error Message'''
| Cannot contact the Server. Try again.
|-
! '''Possible Cause'''
| Cisco Security Agent intermittently blocks access to Ports 80 and 443.
|-
! '''Recommended Action'''
| Use port numbers as specified below:
*HTTP URL for Administration: <pre>http://<ip address>:8080/oraadmin</pre>
*HTTP URL for Serviceability: <pre>http://<ip address>:8080/oraservice</pre>
*HTTPS URL for Administration: <pre>https://<ip address>:8443/oraadmin</pre>
*HTTPS URL for Serviceability: <pre>https://<ip address>:8443/oraservice</pre>

|-
! '''Release'''
| Release 8.5(1), 8.5(2), 8.5(3), 8.5(4).
|-
! '''Associated CDETS #'''
| CSCtj94150
|}

[[Category:Cisco_MediaSense,_Release_8.5]]

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2012-01-25T17:00:37Z

Kemacdon:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

= Supported Virtual Machine OVA Templates =

A virtual machine template defines the configuration of the virtual machine's virtual hardware. Open Virtualization Format (OVF) is an open standard for describing a virtual machine template, and Open Virtualization Archive (OVA) is an open standard to package and distribute these templates. Files in OVA format have an extension of ".ova".

Cisco Unified Communications applications '''must''' use one of the supported virtual machine configurations in the tables below in order to be supported. The OVAs contain virtual hard disks with pre-aligned disk partitions. Using the OVA is the only way to deploy the UC applications on aligned disks. Using the OVA also guarantees that all configuration of the virtual machine is correct and supported.

In the tables below '''users''' refers to the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] for the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. Actual capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools.

 See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed correspond to physical CPU cores and physical CPU core speeds. Both are required to be met to support a full load VM OVA. At this time, only core speed for full load is defined. Do not use lower physical CPU core speeds until Cisco defines minimum speed for lower load levels. Cisco TAC will not troubleshoot a VM that is not receiving sufficient CPU cycles.

== Unified Communications Manager ==

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 General OVA Template Download Location] 
*[[OVA Template Details for Unifed CM Release 8.0]] 
*[[OVA Template Details for Unifed CM Release 8.5]] 
*[[OVA Template Details for Unifed CM Release 8.6]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 12,000 users (C200 only)]
| 2 @ 2.13 GHz each (600 MHz reserved)
| 4 GB (4 GB reserved)
| 1 x 80 GB
| 1
|
Use on C200 M2 TRC#1 only.

Limits:

:*12,000 IP phones
:*2,500 analog phones
:*1,200 roaming phones (per Emergency Responder cluster)
:*500 LAN switches
:*30,000 switch ports
:*3,000 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 20,000 users]
| 1 @ 2.55 MHz (600 MHz reserved)
| 2.25 GB (2.304 GB reserved)
| 1 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*20,000 IP phones
:*5,000 analog phones
:*2,000 roaming phones (per Emergency Responder cluster)
:*1,000 LAN switches
:*60,000 switch ports
:*7,500 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 30,000 users]
| 2 @ 2.55 MHz each
| 6 GB
| 2 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*30,000 IP phones
:*10,000 analog phones
:*3,000 roaming phones (per Emergency Responder cluster)
:*2,000 LAN switches
:*120,000 switch ports
:*10,000 ERLs

|}

 

== Session Manager Edition ==

{| border="1"
|+ '''Supported OVA Templates: Session Manager Edition'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N Use CUCM "7500 users"]
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
|
|}

 

== Unified Attendant Consoles ==

{| border="1"
|+ '''Supported OVA Templates: Unified Attendant Consoles'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! OVA for CUxAC
| 1 @ 2.55 GHz
| 2 GB
| 1x 80GB
| 1
| Note: Cisco does not provide preconfigured OVA files for CUxAC. Please build manually using these requirements. CUxAC requires a VM to meet or exceed minimum physical server specs described [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html on the CUxAC datasheet]
|}

 

== Cisco Intercompany Media Engine ==

{| style="width: 712px; height: 416px" border="1"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 

 

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! 5000 users
| 2 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*48 ports
:*36 text-to-speech ports

|-
! 15,000 users
| 4 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*144 ports
:*36 text-to-speech ports

|}

 

== Cisco Unified Presence ==

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 
*[[OVA Template Details for Unified Presence Release 8.6(4)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Intelligent Voice Response (IP IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

See also:

*[[Virtualization for Unified CCX]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest| Unified CCX OVA Templates]: {{Note| Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)}}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: rgb(229,228,226)"
! colspan="2" | Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 100 agents] (Release 8.5(1))
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 300 agents] (Release 8.0(2) and Release 8.5(1))
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 400 agents] (Release 8.5(1))
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=latest Single OVA] (Release 8.5 (1) or later)
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage )

| 2
|
Capacities

:*300 named users
:*150 concurrent users
:*150 voice recordings, for all recording types (desktop, server and network)
:*150 voice+screen recordings, for all recording types (desktop, server and network)

|}

== UC Management Suite (PM, OM, SM, SSM) ==

There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments.

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! IOPS (avg) (1)
! IOPS (max) (1)
! vNIC
! Notes
! 
|-
! CUPM up to 1K phones (VM-CUCMS_1S)
| 1
| 2 GB
| 1x 30 GB
| 100
| 500
| 1
| 
|-
! CUPM 1K to 10K phones
| 4
| 4 GB
| 1x 40 GB (2)
| 100
| 500
| 1
| 
|-
! CUPM 10K to 60K phones app server
| 4
| 4 GB
| 1x 30 GB(3)
| 100
| 500
| 1
| requires DB VM
|-
! CUPM 10K to 60K phones database server
| 4
| 8 GB
| 1x 120 GB(3)
| 100
| 500
| 1
| requires App VM
|-
! CUOM/SM 1K phones
| 1
| 3 GB
| 1x 50 GB
| 6
| 15
| 1
| 
|-
! CUOM 10K phones (VM-CUCMS_2L)
| 2
| 8 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
|
|
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUCMS 10K phones Co-resident (VM_CUCMS_8)
| 8
| 16 GB
| 1x 320 GB (2)
| 100
| 500
| 1
| 
|}

Notes: (1) IOPS are for each CM publisher synced in parallel. If only one CM publisher then IOPS are 100/500. The maximum figures would be expected during nightly Infrastructrure or Subscriber syncs. (2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) (3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K Server OVA]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K to 10K Server OVA]
| 4
| 4 GB
| 1x 40 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K App/Web Server OVA]
| 4
| 4 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K Database Server OVA]
| 4
| 8 GB
| 1x 120 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283884662&flowid=28561&softwareid=282773197&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest OM, SM, SSM OVAs] CPU/Memory in table above.
|
|
|
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&flowid=20421&softwareid=282773197&release=8.0&rellifecycle=&relind=AVAILABLE&reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&SM_1K)]
| 1
| 3 GB
| 1x 50 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&flowid=19121&softwareid=281934350&release=2.2&rellifecycle=&relind=AVAILABLE&reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|}

== Unified Contact Center Enterprise ==

See also:

*[[Unified Contact Center Enterprise]]
*[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates]
*See also [http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]

Templates are available for Windows Server 2003 and Windows Server 2008 R2. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download] the appropriate OVA file for the Windows OS that you are configuring. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

 

{| border="1" cellspacing="3" cellpadding="3"
|- style="background: rgb(229,228,226)"
! Configuration Name
! vCPU Cores
! vRAM / Memory (GB)
! vDisk (GB)
! vNIC 
! Notes
|-
| colspan="7" | '''Note: Windows Server 2008 R2 configurations are contained in the UCCE_8.5_win2008_vmv7_v1.1.ova file, Windows Server 2003 configurations are contained in the UCCE_8.5_win2003_vmv7_v1.1.ova file'''
|-
| '''Router 8000 agents'''
| 2
| 4
| 1 x80
| 2
|  
|-
| '''Logger 8000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Rogger 4000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Agent PG – CTIOS 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 1000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CTIOS 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 297 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''MR PG 2000 agents 10 pims'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''MR PG 1000 agents 5 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 9600 ports 10 pims'''
| 2
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 1200 ports 4 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Avaya ACD PG'''
| 2
| 4
| 1x 80
| 2
| See the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted] for capacity information.
|-
| '''TDM ACD PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''TDM ACD PG 250 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Administration Client'''
| 1
| 2
| 1x 40
| 1
|  (Client AW)
|-
| '''Administration Server - AW'''
| 1
| 2
| 1x 40
| 1
|  
|-
| '''AW-HDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''AW-HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
| (200 reporters.) The two vDisks can be in the same datastore  
|-
| '''CCMP single box 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP Web/App Svr 8000 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP with Config AW 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP DB only 8000 agents'''
| 8
| 4
| 1x 250
| 1
|  
|}

== Unified Customer Voice Portal ==

See also:

*[[Unified Customer Voice Portal]]
*[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Unified Customer Voice Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions. See CVP co-residency section for detail)
| 4
| 4 GB
| 1x 146 GB
| 1
| Template Name: Cisco Unified CVP Call Server-VXML Server.ova
|-
! Unified CVP Reporting Server (Large)
| 4
| 4 GB
| Disk 1 - 72 GB, Disk 2 - 438 GB
| 1
| Template Name: Cisco Unified CVP Reporting Server.ova
|-
! Unified CVP Operations Console
| 2
| 2 GB
| 1x 20 GB
| 1
| Template Name: Cisco Unified CVP Operations Console.ova
|}

== Cisco MediaSense ==

See also:

*[http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense Virtualization for Cisco MediaSense]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco MediaSense OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense'''
|-
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! CMS_6T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 146 GB (thick provisioning)
| 1
| rowspan="3" | Release 8.5(1)
|-
! CMS_12T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 300 GB (thick provisioning)
| 1
|-
! CMS_expansion_server_v8.5_vmv7
| 7 
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 150 GB (thick provisioning) 
| 1
| rowspan="4" |
Release 8.5(2)

Release 8.5(3)

Release 8.5(4)

|-
! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 300 GB (thick provisioning) 
| 1
|-
! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 600 GB (thick provisioning) 
| 1
|-
! CMS_expansion_server_v8.5.2_vmv7
| 7
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

== Cisco Unified Intelligence Center ==

See also:

*[[Cisco Unified Intelligence Center]]
*[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Intelligence Center'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=283776220&release=8.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 GB
| 1
|
|}

== Cisco Unified Contact Center Management Portal ==

See also:

*[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
*[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CCMP (1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (DB Only) (8000 Agents)
| 8
| 4 GB
| 1x 250 GB
| 1
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&softwareid=283733464&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Standard Production Server
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
| 
|}

== Cisco Unfied Email Interaction Manager and Web Interaction Manager ==

  

{| border="1" cellspacing="1" cellpadding="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
|
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_1_v2.0] 

Deployment Option:

100 agents - Email Only 

| Application, Services Server ,File server Messaging Server ,Web Server and Database server
| 1
| 2 
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_2_v2.0] 

Deployment Option:

140 agents - Email Only

 

| Application, Services Server ,File server Messaging Server and Web server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_3_v2.0] 

Deployment Option:

100 agents - Chat only or

100 agents - Email and Chat  

| Application, Services Server ,File server Messaging Server and Database server
| 1
| 2
| 1 x 80GB
| 4
|-
| Web Server
| 1
| 1
| 1 x 80GB
| 2 
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_4_v2.0] 

Deployment Option:

250 Agents - Email and Chat or 120 Agents - BC and CallBack

 

 

 

 

| Web Server
| 1
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2 
| 1 x 80 GB for OS, 1 x 150 GB for DB
| 4
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_5_v2.0] 

Deployment Option:

500 Agents - Email and Chat or 240 Agents - BC and CallBack 

 

| Web Server
| 2 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 8
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 1
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_6_v2.0] 

Deployment Option:

750 Agents - Email and Chat or 360 Agents - BC and CallBack 

| Web Server
| 3
| 1
| 1 x 80GB
| 1
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16 
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_7_v2.0] 

Deployment Option:

1000 Agents - Email and Chat or 480 Agents - BC and CallBack 

| Web Server
| 4
| 1
| 1 x 80GB
| 1
|-
| Application server
| 4 
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_8_v2.0] 

Deployment Option:

1250 Agents - Email and Chat or 600 Agents - BC and CallBack 

| Web Server
| 5 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 5
| 2
| 1 x 80GB
| 2 
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|}

 

== Cisco Media Blender ==

{| style="width: 1054px; height: 102px" border="1" cellspacing="1" cellpadding="1" width="1054" align="center"
|-
|
 '''Application, OVA Capacity and Notes+Download Link'''

|         '''Contents    '''  
| '''No of VM's to deploy of each component'''
| '''vCPU'''
| '''vDisk'''
| '''vRAM/Memory'''
|-
|
 [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all Cisco Media Blender]

|
 

Cisco Media Blender

|
 1

|
 2

|
 1 x 80GB

|
 2

|}

 

== Cisco Finesse ==

See also:

*[[Virtualization for Cisco Finesse|Cisco Finesse]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613135&flowid=30701&softwareid=284236523&release=8.5.3&relind=AVAILABLE&rellifecycle=&reltype=latest Cisco Finesse OVA Templates] 

{| border="1"
|+ '''Supported OVA Templates: Cisco Finesse'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Finesse_2000_agents_v1.0_vmv7 
| 4
| 8 GB
| 1x 146 GB
| 1
| Release 8.5(3)
|}

  

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Virtualization for Cisco MediaSense

2012-01-19T22:24:17Z

Kemacdon:

{{note| Product documentation may reflect varying names that appear in the application user interfaces and application programming interfaces of this product. These names may include Cisco Unified Media Capture Platform (Unified MCP), Media Capture Platform (MCP/mcp), or Open Recording Architecture (ORA/ora).}} 

= Updates to this Page =

The following is a list of significant updates to this page:

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| January 2012
| Updated page with information on support for Release 8.5(4).
|-
| October 2011
| Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| June 2011
| Updated all links to align with the new Virtualization strucutre at [[Unified Communications in a Virtualized Environment]].
|-
| April 2011
| Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| November 2010
| Virtualization of Cisco MediaSense on UCS C Series hardware.
|-
| December 2010
| Updated OVA template download link.
|}

= Information for Partners about Cisco MediaSense Deployments =

See [[Unified Communications in a Virtualized Environment]].

= VM-Specific Cisco MediaSense Hardware Requirements =

See [[Tested Reference Configurations (TRC)]].

Before you install the Cisco MediaSense software in any server, you must address the following requirements:

*Only Cisco MediaSense must be running on this VM host. No other product can be installed on this server.
*If you are performing a fresh install of Cisco MediaSense in any deployment, be sure to verify that the virtual machine is also fresh (no previously-installed OS is present in the VM).

= Cisco MediaSense-Specific Details for VMware Requirements =

See [[Unified Communications VMWare Requirements]]

*Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation.
*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense]. 

== Cisco MediaSense, Release 8.5(1)  and 8.5(2) ==

All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).

*Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1).
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.

 

== Cisco MediaSense, Release 8.5(3) ==

{{note| Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] for more information.}}

Up to 60 terabytes of media storage is supported per cluster, divided into up to six 2TB virtual disks in each of five servers. This assumes that all nodes are B-series servers, for which Cisco MediaSense supports SAN storage. C-series servers, for which only direct attached drives are currently supported, are limited to two 2TB media storage partitions each. Also, no single media partition may be smaller than 200GB.

See the following links for more information:

*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications
*See the Compatibility Matrix section in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] guide for more information. 

== Cisco MediaSense, Release 8.5(4) ==

In addition to approved UCS servers, Cisco MediaSense 8.5(4) can also be installed on a Services Ready Engine (SRE) module inside a router. An SRE module is a router blade that has its own processors, storage, network interfaces, and memory. Support for SRE requires SRE v2.0 software. For more information about approved SRE models, see the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(4)]. 

If you are using ESXi 5.0, make sure that you [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 5.0 host.

= Cisco MediaSense-Specific Information for OVA Templates =

If your partitions (VM disk configuration) are not aligned, your data replication between the primary and secondary servers may get congested and result in your data being out of sync. To avoid these problems, only use the VM templates provided by Cisco MediaSense. 

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.2&relind=AVAILABLE&rellifecycle=&reltype=latest Cisco MediaSense OVA Templates]

 

{{caution| If your VM template or VM configuration does not meet the Cisco MediaSense requirements, it is possible for your installation to halt due to an unrecoverable error. See [[Installation: Installation halts with an unrecoverable error]].}}

 

{{note| Configure the primary server and secondary server in your Cisco MediaSense deployment to have identical hardware in terms of CPU configuration (number of CPUs and speed of the CPU), storage configuration (number of disks, speed of disk, and RAID setup), and memory. Be sure to keep both servers in the same network and run the same version of VMWare Hypervisor on both servers.}}

= Cisco MediaSense-Specific Information for Sizing Guidelines =

The VM-specific sizing informaton required for Cisco MediaSense is additional virtual disks for media storage. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense] for further information.

= How to Dump Install Logs to the VM Serial Port =

See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]].

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

[[Category:Cisco_MediaSense]]

RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down

2012-01-19T20:08:54Z

Kemacdon:

== RTMT does not show alarm info if the primary node is out of service ==

{| border="1"
|-
! '''Problem Summary'''
| The Unified Real Time Monitoring Tool (Unified RTMT) is connected to the secondary node, but after logging in to RTMT, alarm information is not shown. Instead, an error is reported.
|-
! '''Error Message'''
| Error polling alert status - AMC service is down
|-
! '''Possible Cause'''
| By default, the Primary Collector for the Alert Manager and Collector Service (AMC) is configured on the primary node, and the Failover Collector is not active. If the primary node is down, there is no available collector to which RTMT can connect. 
|-
! '''Recommended Action'''
|
 

#When the primary node is in service, sign in to MediaSense administration, and then enter: '''<nowiki>https://<ip address>:8443/ccmadmin/serviceParamEdit.do</nowiki> '''in the browser address field to access the Unified CM server parameter configuration page.
#Activate the Failover Collector for the Cisco AMC service.

|-
! '''Release'''
|  Release 8.5(1), Release 8.5(2), Release 8.5(3), Release 8.5(4)
|-
! '''Associated CDETS #'''
|  CSCtx41763
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]
'''

RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down

2012-01-19T19:45:35Z

Kemacdon:

Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state

2012-01-18T21:04:39Z

Kemacdon:

== Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state ==

{| border="1"
|-
! '''Problem Summary'''
| When configuring community strings (using the Cisco Unified Serviceability pages) the SNMP Master Agent restarts when the configuration is saved. During the SNMP Master Agent restart, the Host Resource Agent hangs.
|-
! '''Error Message'''
| A CriticalServiceDown alert is seen every 30 seconds in RTMT, and delivered by email if email alerts are configured.
|-
! '''Possible Cause'''
| SNMP is not supported in MediaSense.
|-
! '''Recommended Action'''
|
1. Remove/Clear the SNMP configuration

2. Reboot the MediaSense server

|-
! '''Release'''
| Release 8.5(1), 8.5(2), 8.5(3), 8.5(4) 
|-
! '''Associated CDETS #'''
| CSCtu21764
|}

 

[[Category:Cisco_MediaSense,_Release_8.5]]

Troubleshooting Tips for Cisco MediaSense 8.5

2012-01-18T21:00:09Z

Kemacdon:

'''Back:''' [[Troubleshooting Cisco MediaSense]]

'''Additional Troubleshooting Information''': [[Additional troubleshooting information for Cisco MediaSense 8.5]]

'''Add tip:''' [[Create Contact Center Troubleshooting Tips]]

'''Print PDF:''' [[Print Cisco MediaSense 8.5 Troubleshooting Tips]]

----

{{note | '''Cisco MediaSense product documentation reflects the fields and names used in the application user interfaces and application programming interfaces of this product. Effective Release 8.5(2), these names are restricted to Cisco MediaSense and Open Recording Architecture (ORA/ora).'''}}

----

The following tips were added by Cisco Documentation:

== API ==

*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]

== General ==

*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]] 

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state

2011-11-18T02:40:05Z

Kemacdon: Created page with "== Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state == {| border="1" |- ! '''Problem Summary''' | When configuring community strings (using ..."

== Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state ==

{| border="1"
|-
! '''Problem Summary'''
| When configuring community strings (using the Cisco Unified Serviceability pages) the SNMP Master Agent restarts when the configuration is saved. During the SNMP Master Agent restart, the Host Resource Agent hangs.
|-
! '''Error Message'''
| A CriticalServiceDown alert is seen every 30 seconds in RTMT, and delivered by email if email alerts are configured.
|-
! '''Possible Cause'''
| SNMP is not supported in MediaSense.
|-
! '''Recommended Action'''
|
1. Remove/Clear the SNMP configuration

2. Reboot the MediaSense server

|-
! '''Release'''
| Release 8.5(1), 8.5(2), 8.5(3)
|-
! '''Associated CDETS #'''
| CSCtu21764
|}

 [[Category:Cisco MediaSense, Release 8.5]]

API: MediaSense application sign-in fails with administration credentials

2011-11-15T13:59:28Z

Kemacdon:

==  MediaSense application sign-in fails with administration credentials ==

{| border="1"
|-
! '''Problem Summary'''
| When using administration credentials to access the MediaSense APIs, the sign-in fails.
|-
! '''Error Message'''
| Your login credentials (username or password ) are invalid
|-
! '''Possible Cause'''
| The user attempts an application sign-in using administration credentials.
|-
! '''Recommended Action'''
|
MediaSense application sign-in requires a separate API User with credentials that are different from the Administration Credentials. An API user can be specified using the MediaSense Administration interface (API users can be imported from the list of Unified CM users). 

In Unified CM you should choose (or configure) one or more ''end users ''that will be used as MediaSense API users. After you do this, use the following steps to specify the Unified CM end users as API users in MediaSense:

#Sign in to Cisco MediaSense administration by pointing your browser to http://servername/oraadmin, where servername is the IP address of the MediaSense server
#Choose Administration > MediaSense User Configuration
#Click '''Manage MediaSense Users''', to display the ''Unified CM Users ''list and the ''MediaSense API Users'' list
#Select and import the Unified CM users that you want to specify as API users

|-
! '''Release'''
| Release 8.5(1), 8.5(2), 8.5(3), 8.5(4).
|-
! '''Associated CDETS #'''
| None
|}

   

[[Category:Cisco_MediaSense,_Release_8.5]]

Installation: Installation halts with an unrecoverable error

2011-11-03T17:49:43Z

Kemacdon:

== The installation halts with an unrecoverable error ==

{| border="1"
|-
! '''Problem Summary'''
| The installation fails with an unrecoverable error. 
|-
! '''Error Message'''
| Installation has encountered an unrecoverable internal error 
|-
! '''Possible Cause'''
|
The VM Template or the VM configuration does not meet the requirements. See [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all the Software Download page] for a list of supported VM templates.

See the ''Unified MCP-Specific Information for OVA Templates'' section in the [[Virtualization for Cisco MediaSense]] website. 

|-
! '''Recommended Action'''
|
Verify that the VM configuration meets the minimum system requirements such as number of CPUs and other requirements specified in the read-me file for each supported VM template.

Cisco MediaSense, beginning with Release 8.5(2), only supports the VM templates listed in [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all the Software Download page]. 

|-
! '''Release'''
| Release 8.5(2) and Release 8.5(3).
|-
! '''Associated CDETS #'''
| None. 
|}

[[Category:Cisco_MediaSense,_Release_8.5]]

Set Call Data API Request does not invoke CALL DATA UDPATE

2011-07-05T14:32:45Z

Kemacdon:

== Set Call Data API Request does not invoke CALL_DATA_UDPATE ==

{| border="1"
|-
! '''Problem Summary'''
| The Set Call Data API request returns a successful reponse, but no CALL_DATA_UPDATE is received.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| You have sent a Set Call Data API request with one or more invalid variable parameters and ''no'' valid variable parameters. (For example, you sent the variable field as callWrapUpData instead of callWrapupData. This is invalid due to the difference in case for the letter 'u'.)
The SET_CALL_DATA_REQ must cause a change in a valid call variable. Finesse does not verify fields sent in a SET CALL DATA API request. Sending an invalid variable does not prompt a CALL_DATA_UPDATE from CTI unless other valid variables are sent along with it. A successul response indicates that the request was received, but does not mean that the request has changed the variables.
|-
! '''Recommended Action'''
| Verify the syntax of the variable and resend the request.
|-
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Offhook Behavior in Agent Desktop

2011-07-05T14:27:16Z

Kemacdon:

== Desktop: Offhook Behavior in Agent Desktop ==

{| border="1"
|-
! '''Problem Summary'''
| The agent takes the phone off hook. The Finesse Desktop shows the agent state as Talking but shows no call appearance.
|-
! '''Error Message'''
| N/A
|-
! '''Possible Cause'''
| This release does not support the SERVICE_INIT event. Therefore, taking the phone off hook does not send an event to the desktop.
|-
! '''Recommended Action'''
| A call appears on the desktop once the agent originates a call.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Desktop Tools are Unresponsive or Disabled

2011-07-05T14:25:36Z

Kemacdon:

== Desktop: Desktop Tools are Unresponsive or Disabled ==

{| border="1"
|-
! '''Problem Summary'''
| The desktop components are non-responsive.
|-
! '''Error Message'''
| HTTP 500 or HTTP 503
|-
! '''Possible Cause'''
| A 500 error indicates that a connection to the CTI server is lost, or it is in OUT_OF_SERVICE status.
A 503 error indicates that the connection is in the PARTIAL_SERVICE status.
|-
! '''Recommended Action'''
| Try these actions in the sequence listed:
* This disabled condition might be temporary. The agent can sign out of the desktop and then sign in again.
* The Administrator can check the network connections.
* The Administrator can launch the Serviceability Console to check the status of the service and to perform a Restart if necessary.
* The Administrator can run CLI commands to view that status, and if needed, to restart the services.
* The Administrator can check to see if the CTI Server is up and running.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
|None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Desktop Does Not Recognize Calls Active during Sign In or Browser Refresh

2011-07-05T14:23:42Z

Kemacdon:

== Desktop: Desktop Does Not Recognize Calls Active during Sign In or Browser Refresh ==

{| border="1"
|-
! '''Problem Summary'''
| The Finesse desktop does not show calls that are active while the agent is signing in or refreshing the browser.
|-
! '''Error Message'''
| N/A
|-
! '''Possible Cause'''
| This release of Finesse does not support the Call Snapshot API.
|-
! '''Recommended Action'''
| None. These calls are not recognized in the current 8.5(1) release.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Button Behavior is Incorrect or Generates Errors

2011-07-05T14:20:24Z

Kemacdon:

== Desktop: Button Behavior is Incorrect or Generates Errors ==

{| border="1"
|-
! '''Problem Summary'''
| Clicking a button on the desktop does not result in the expected action or generates an error.
|-
! '''Error Message'''
| Various
|-
! '''Possible Cause'''
| This can happen when the Finesse Web Service disconnects and then reconnects to the CTI server at a time when no actions are occurring in the desktop. The desktop is unaware of the disconnect/reconnect and continues to show the "stale" state before the disconnect/reconnect.
|-
! '''Recommended Action'''
| Restore the desktop to a normal state by signing out and signing back in.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Agent State Spontaneous Change to Not Ready

2011-07-05T14:18:58Z

Kemacdon:

== Desktop: Agent State Spontaneous Change to Not Ready ==

{| border="1"
|-
! '''Problem Summary'''
| The agent is signed in and engaged in operations when the Agent State changes to Not Ready.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| This can happen when the Agent PG recycles or when there is a reconnect between CTIServer and the PIM, or between the PIM and OPC, or between OPC and the router. While the call might be maintained, the Agent State changes to Not Ready.
|-
! '''Recommended Action'''
| This is a temporary condition and should be resolved if the agent signs out and then signs back in.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Agent State Spontaneous Change to Not Ready

2011-07-05T14:15:29Z

Kemacdon:

== Desktop: Agent State Spontaneous Change to Not Ready ==

{| border="1"
|-
! '''Problem Summary'''
| The agent is signed in and engaged in operations when the Agent State changes to Not Ready.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| This can happen when the Agent PG recycles or when there is a reconnect between CTIServer and the PIM, or between the PIM and OPC, or between OPC and the router. While the call might be maintained, the Agent State changes to Not Ready.
|-
! '''Recommended Action'''
| This is a temporary condition and should be resolved after the agent signs out and then signs back in.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Agent State Changes

2011-07-05T14:13:11Z

Kemacdon:

== Desktop: Agent State Changes ==

{| border="1"
|-
! '''Problem Summary'''
| What valid state changes can an agent make from the agent state dropdown menu?
|-
! '''Error Message'''
| Invalid state change.
|-
! '''Possible Cause'''
| N/A
|-
! '''Recommended Action'''
| All agents can change their states as follows:
* From: Ready (Available) To: Not Ready
* From: Not Ready To: Ready (Available)
* From: Not Ready To: Logout
* From: Not Ready To: Not Ready with a different Reason Code
* From: Talking on an incoming or outbound call To: Not Ready
* From: Talking on an incoming or outbound call To: Ready (Available) if wrapup is not allowed or is optional.
* From: Work (CCE only) on an incoming or outbound call To: Not Ready
* From: Work (CCE only) on an incoming or outbound call To: Ready (Available) if wrapup is required or is optional.

{{note| The WORK_NOT_READY agent state is not supported in Cisco Finesse.}}

The following supported states are changed as a result of call events. The agent does not control them or actively select them in the Desktop:
* Busy Other(CCE only)
* Reserved
* Unknown (CCE only)
* Active (CCE only)
* Paused (CCE only)
* Interrupted (CCE only)
* Not Active (CCE only)

|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Agent Signs In with Multiple Browser Sessions

2011-07-05T14:11:48Z

Kemacdon:

== Desktop: Agent Signs In with Multiple Browser Sessions ==

{| border="1"
|-
! '''Problem Summary'''
| An agent signs in to the Finesse Desktop using more than one simultaneous browser session.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| Various
|-
! '''Recommended Action'''
| Sign out of all browser sessions but one. Results are unpredictable otherwise.
|-
! '''Release'''
| Release number 8.5(1)
|-
! '''Associated CDETS #'''
|N/A'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Agent Password Required for Sign In

2011-07-05T14:10:04Z

Kemacdon:

== Desktop: Agent Password Required for Sign In ==

{| border="1"
|-
! '''Problem Summary'''
| The agent enters an ID and extension but no password on the Cisco Finesse Sign In page. The agent then clicks Sign In. The screen displays a message that "The Desktop is connecting ... ", but the desktop does not open.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| The agent was created in Unified CCE with no password. Agent Password is an optional field in Unified CCE configuration. It is a ''required field'' for Cisco Finesse.
|-
! '''Recommended Action'''
| Launch the Unified CCE Configuration Manager. Open Agent Explorer. Locate the agent from the list of agents in the left pane. See the corresponding Agent tab on the right pane. Enter a password for this agent and save the record. Cisco Finesse will recognize the password instantly.
|-
! '''Release'''
| Release 8.5(1).
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Agent Password Required for Sign In

2011-07-05T14:08:54Z

Kemacdon:

== Desktop: Agent Password Required for Sign In ==

{| border="1"
|-
! '''Problem Summary'''
| The agent enters an ID and extension but no password on the Cisco Finesse Sign In page. The agent then clicks Sign In. The screen displays a message that "The Desktop is connecting ... ", but the desktop does not open.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| The agent was created in Unified CCE with no password. Agent Password is an optional field in Unified CCE configuration. It is a ''required field'' for Cisco Finesse.
|-
! '''Recommended Action'''
| Launch Unified CCE Configuration Manager. Open Agent Explorer. Locate the agent from the list of agents in the left pane. See the corresponding Agent tab on the right pane. Enter a password for this agent and save the record. Cisco Finesse will recognize the password instantly.
|-
! '''Release'''
| Release 8.5(1).
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Errors: Network Connections

2011-07-05T14:06:53Z

Kemacdon:

== Desktop Errors: Network Connections ==

{| border="1"
|-
! '''Problem Summary'''
| The following errors might appear in the desktop for various network issues.
|-
! '''Error Message'''
| 1. The desktop is having trouble connecting to the server, please check your network connection.

2. The desktop is having trouble making network requests. Please contact the administrator.

3. The desktop is having trouble connecting to the notification server. Please try refreshing the page or sign back in. Contact your administrator if the problem persists.

|-
! '''Possible Cause''
| Various. See below.
|-
! '''Recommended Action'''
| 1. This error indicates that your network is offline.

2. The Finesse server is in a bad state and cannot process the request. There might have been a network timeout or an internal server error such as a lost connection to the CTI server. Refer to the HTTP Errors topic in the Cisco Finesse Web Services Developer Guide. Addressing the error code and restarting the Finesse server could resolve the issue.

3. This is an indication that the Finesse Notification Service is down or misconfigured. In most cases, a reload of the page or signing in again will resolve the issue. If it does not, access the Serviceability console (//<HOST ADDRESS>/cfservice) and restart the Cisco Finesse Notification Service and/or Cisco Finesse Web Services.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Errors: Call Control

2011-07-05T14:05:47Z

Kemacdon:

== Desktop Errors: Call Control ==

{| border="1"
|-
! '''Problem Summary'''
| The following errors might appear in the agent desktop for call control issues.
|-
! '''Error Message'''
|
# Unavailable in current state.
# Error making call.
# Operation failed. Try phone controls for this action. If the problem persists, sign out and sign in again after your calls. (holding / retrieving / conferencing / transferring / ending call)

|-
! '''Possible Cause'''
|
# This means that the agent tried to take an action that is not allowed until he is in a certain state - for example, an agent cannot place a call from the READY state.
# The destination may be busy or the number may be wrong.
# There is a race condition. You already tried to perform an action on the call but the event did not come through.
|-
! '''Recommended Action'''
|
# Avoid actions which are not allowed in a given state.
# You may need to disconnect the call and retry.
# Verify if your intended operation is complete. If yes, the call appearance on the UI should be updated accordingly. If not, then try hard phone controls for the intended action. If the UI is not updated accordingly, then sign out and sign back in after you have completed your call.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
|None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Error: Invalid Session. Your session has expired.

2011-07-05T14:04:52Z

Kemacdon:

== Desktop Error: Invalid Session. Your session has expired. ==

{| border="1"
|-
! '''Problem Summary'''
| The following error message is displayed while you are signed in to the Finesse desktop.
|-
! '''Error Message'''
| "Your session has expired. Please sign in again."
|-
! '''Possible Cause'''
| You have been signed in and inactive for longer than 24 hours.
|-
! '''Recommended Action'''
| Sign-out and then sign-in again.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Error: Invalid Session. Your session has expired.

2011-07-05T14:04:30Z

Kemacdon:

== Desktop Error: Invalid Session. Your session has expired. ==

{| border="1"
|-
! '''Problem Summary'''
| The following error message displays while you are signed in to the Finesse desktop.
|-
! '''Error Message'''
| "Your session has expired. Please sign in again."
|-
! '''Possible Cause'''
| You have been signed in and inactive for longer than 24 hours.
|-
! '''Recommended Action'''
| Sign-out and then sign-in again.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Errors: Server Authentication Failure

2011-07-04T18:46:57Z

Kemacdon:

== Desktop Errors: Server Authentication Failure ==

{| border="1"
|-
! '''Problem Summary'''
| The agent sees this error when attempting to sign in to the Cisco Finesse Desktop.
|-
! '''Error Message'''
| Server authentication failure. Please try again or contact your system administrator.
|-
! '''Possible Cause'''
| There are several possible causes for this error. Recommended actions are listed below.
|-
! '''Recommended Action'''
|
* Ensure that the device associated with the agent extension is active.
* Ensure that all Finesse Services are started. To do this, sign in to the Serviceability Console.
* Ensure that forward and reverse DNS are set up correctly and that a valid host and domain were entered during the installation.
* Ensure that you are using Unified Contact Center Enterprise and Unified CM, Release 8.5(1).
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Errors: Call Control

2011-07-04T18:45:40Z

Kemacdon:

== Desktop Errors: Call Control ==

{| border="1"
|-
! '''Problem Summary'''
| Errors might appear in the agent desktop for call control issues.
|-
! '''Error Message'''
|
# Unavailable in current state.
# Error making call.
# Operation failed. Try phone controls for this action. If the problem persists, sign out and sign in again after your calls. (holding / retrieving / conferencing / transferring / ending call)

|-
! '''Possible Cause'''
|
# This means that the agent tried to take an action that is not allowed until he is in a certain state - for example, an agent cannot place a call from the READY state.
# The destination may be busy or the number may be wrong.
# There is a race condition. You already tried to perform an action on the call but the event did not come through.
|-
! '''Recommended Action'''
|
# Avoid actions which are not allowed in a given state.
# You may need to disconnect the call and retry.
# Verify if your intended operation is complete. If yes, the call appearance on the UI should be updated accordingly. If not, then try hard phone controls for the intended action. If the UI is not updated accordingly, then sign out and sign back in after you have completed your call.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
|None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Error: Invalid Session. Your session has expired.

2011-07-04T18:42:38Z

Kemacdon:

== Desktop Error: Invalid Session. Your session has expired. ==

{| border="1"
|-
! '''Problem Summary'''
| This error message displays while you are signed in to the Finesse desktop.
|-
! '''Error Message'''
| "Your session has expired. Please sign in again."
|-
! '''Possible Cause'''
| You have been signed in and inactive for longer than 24 hours.
|-
! '''Recommended Action'''
| Sign-out and then sign-in again.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop Error: Invalid Session. Your session has expired.

2011-07-04T18:42:14Z

Kemacdon:

== Desktop Error: Invalid Session. Your session has expired. ==

{| border="1"
|-
! '''Problem Summary'''
| This error message displays while you are signed in to the Finesse desktop.
|-
! '''Error Message'''
| "Your session has expired. Please sign in again."
|-
! '''Possible Cause'''
| You have been signed in and inactive for longer than 24 hours.
|-
! '''Recommended Action'''
| Sign-out and sign-in again.
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]

Desktop: Agent Password Required for Sign In

2011-07-04T18:41:06Z

Kemacdon:

== Desktop: Agent Password Required for Sign In ==

{| border="1"
|-
! '''Problem Summary'''
| The agent enters an ID and extension but no password on the Cisco Finesse Sign In page. The agent then clicks Sign In. The screen displays a message that "The Desktop is connecting ... ", but the desktop does not open.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| The agent was created in Unified CCE with no password. Agent Password is an optional field in Unified CCE configuration. It is a ''required field'' for Cisco Finesse.
|-
! '''Recommended Action'''
| Launch Unified CCE Configuration Manager. Open Agent Explorer. Locate the agent from the list of agents in the left pane. See the corresponding Agent tab on the right pane. Enter a password for this agent and save the record. Cisco Finesse will recognize the password instantly.
|-
! '''Release'''
| Release 8.5(1).
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]