http://docwiki.cisco.com/w/index.php?title=Special:Contributions/Cchetty&feed=atom&limit=50&target=Cchetty&year=&month= 2013-05-22T19:26:29Z From DocWiki MediaWiki 1.16.0 http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 2011-10-13T22:38:18Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''&lt;br&gt;<br /> <br /> ----<br /> <br /> Version compatibility of virtualized Cisco Unified Communications applications with various server/storage hardware options are listed below. <br /> <br /> *Support information below is as of the release date of '''Cisco Unified Communications 8.6(1)''', which updated '''8.0, 8.5 and 8.6''' support policies.<br /> <br /> *Ensure your deployment follows the rules listed [[High-level Checklist for Design and Implementation|here]].<br /> <br /> *Click on the application name for additional product-specific requirements and information (if any).<br /> <br /> *&quot;TRC&quot; = &quot;Tested Reference Configuration&quot; as described [[Unified Computing System Hardware|here]].<br /> <br /> &lt;br&gt;<br /> <br /> == Call Processing and System Management Applications&lt;br&gt; ==<br /> <br /> {| style=&quot;width: 1076px; height: 476px&quot; class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | Unified Communications Manager (1) <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]] <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> &lt;br&gt;<br /> <br /> |-<br /> | Cisco Emergency Responder <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | Session Manager Edition <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | Not supported <br /> &lt;br&gt;<br /> <br /> |-<br /> | Intercompany Media Engine <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> |-<br /> | Unified Attendant Consoles <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.0(3) <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> |-<br /> | UC Management Suite (OM, SM, SSM, PM) <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later<br /> |}<br /> <br /> &lt;br&gt;(1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes. <br /> <br /> == Messaging and Presence Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS)&lt;br&gt;<br /> |-<br /> | Cisco Unity Connection <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later<br /> |-<br /> | Cisco Unity <br /> | 7.0(2) and later <br /> | 7.0(2) and later <br /> | Not supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not Supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]] <br /> | 8.6(1) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Contact Center Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] &lt;br&gt;<br /> | 8.5(1) and later&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later&amp;nbsp;<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | 8.5(1) and later<br /> |-<br /> | [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO), Quality Management (QM), and WorkForce Management (WFM)] <br /> | 8.5(2) and later&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later<br /> |-<br /> | [[Unified Contact Center Enterprise]] &lt;br&gt;<br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below<br /> |-<br /> | - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tool,&amp;nbsp;limited/hybrid support for Unified ICME/CCH/ICMH <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported<br /> |-<br /> | - Progger, Outbound Option with SCCP Dialer, Webview, EIM/WIM, Expert Advisor, RSM, Unified CRM Connector <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | 8.0(3) and later <br /> | 8.5(2) and later&amp;nbsp; <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | Not supported<br /> |-<br /> | [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]&amp;nbsp; <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Unified Customer Voice Portal]] (all components) &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco MediaSense|Cisco MediaSense]] <br /> | Not supported&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]] <br /> | 8.5(3) and later &lt;br&gt;<br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later<br /> |-<br /> | [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager Unified Email Interaction Manager and Web Interaction Manager] <br /> | 4.4(1) and later<br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/SocialMiner_Feeds_-_Errors_saving_Groovy_scripts 2011-10-13T22:24:39Z

<p>Cchetty: 1 revision</p> <hr /> <div>== SocialMiner Feeds - Errors saving Groovy scripts ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary'''<br /> | You see errors when you import a Groovy script.<br /> |-<br /> ! '''Error Message'''<br /> | The User Interface will show this error: “The following fields are invalid: Script Source: Invalid input”<br /> <br /> Logs will show &quot;Unexpected char&quot; errors similar to this: <br /> , Message=startup failed: Script1.groovy: 1: unexpected char: '\' @ line 1, column 2. ^<br /> |-<br /> ! '''Possible Cause'''<br /> | You did not save the file as plain text.<br /> |-<br /> ! '''Recommended Action'''<br /> | Check to make sure that the file was not saved as &quot;rich text,&quot; which will insert special characters. Resave the file as plain text and retry the Import.<br /> |-<br /> ! '''Release'''<br /> | Release 8.5(4)<br /> |-<br /> ! '''Associated CDETS #'''<br /> | None<br /> |-<br /> |}<br /> [[Category:Cisco SocialMiner, Release 8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/SocialMiner_Feeds_-_Error_on_Twitter_Authorization 2011-10-13T22:24:39Z

<p>Cchetty: 1 revision</p> <hr /> <div>== SocialMiner Feeds - Error on Twitter Authorization ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary'''<br /> | You authorize a Twitter feed with incorrect credentials and see an error from Twitter. You try the authorization again with the correct credentials and see an error from SocialMiner.<br /> |-<br /> ! '''Error Message'''<br /> | Typical errors are Wrong UserName or Wrong Password.<br /> |-<br /> ! '''Possible Cause'''<br /> | Twitter presents an error message on your first attempt to log in with incorrect credentials. SocialMiner does not process the Twitter error correctly and gives an error on your second attempt. SocialMiner then clears the error after your second attempt.<br /> |-<br /> ! '''Recommended Action'''<br /> | Try the authorization a third time. <br /> |-<br /> ! '''Release'''<br /> | Release 8.5(4)<br /> |-<br /> ! '''Associated CDETS #'''<br /> | None<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Cisco SocialMiner, Release 8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/SocialMiner_Release_8.5(4) 2011-10-13T22:24:39Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''CONTENTS''' <br /> <br /> [[#Introduction|Introduction]] <br /> <br /> [[#What.27s_New_in_Release_8.5.284.29|What's New in SocialMiner Release 8.5(4)]] <br /> <br /> [[#Upgrading_to_SocialMiner_Release_8.5.284.29|Upgrading to SocialMiner Release 8.5(4)]] <br /> <br /> [[#Signing_In_to_SocialMiner|Signing In to SocialMiner]] <br /> <br /> [[#The_Home_Tab|Home Tab and Settings]] <br /> <br /> [[#Feeds|Feeds]] <br /> <br /> [[#Campaigns|Campaigns]] <br /> <br /> [[#Filters|Filters]] <br /> <br /> [[#System_Administration|System Administration]] <br /> <br /> [[#Notifications|Notifications]] <br /> <br /> [[#Reply_Templates|Reply Templates]] <br /> <br /> [[#SocialMiner_Reporting|SocialMiner Reporting]] <br /> <br /> [[#Downloading_and_Installing_Language_Packs|Downloading and Installing Language Packs]] <br /> <br /> [[#System_Backup_and_Restoration|System Backup and Restoration]] <br /> <br /> [[#Design_Guidance|Design Guidance]] <br /> <br /> [[#Developer_Information|Developer Information]] <br /> <br /> [[#Copyright_Notes|Copyright Notes]] <br /> <br /> __NOTOC__ <br /> <br /> &lt;br&gt;<br /> <br /> = Introduction =<br /> <br /> Cisco SocialMiner is a customer-care system that provides capture, filtering, workflow, queuing, and reporting for social media engagement teams. Internet postings captured by SocialMiner are referred to as '''Social Contacts'''. SocialMiner stores the social contacts and groups them into user-defined '''Campaigns'''. Each Campaign obtains social contacts from one or more '''Feeds'''. SocialMiner presents the social contacts to social media customer care personnel who can review, categorize, and respond to the postings. SocialMiner also produces reporting metrics on the handling of the social contacts. <br /> <br /> == Technology and Packaging ==<br /> <br /> SocialMiner is a server software application that is packaged as a software appliance. The appliance runs as one VMWare® virtual machine containing all of the following components: <br /> <br /> *Cisco Unified Communications Operating System (Unified OS), a Redhat Linux based Operating System <br /> *Informix® embedded database. This database contains the SocialMiner Configuration and the SocialMiner reporting data. <br /> *[http://cassandra.apache.org/ Cassandra datastore]. This datastore contains the social contacts. <br /> *Cisco SocialMiner runtime software <br /> *OpenFire server for XMPP BOSH eventing<br /> <br /> Setup and administration are done through a browser-based interface that uses [http://en.wikipedia.org/wiki/OpenSocial OpenSocial Gadgets]. SocialMiner is installed with the [http://shindig.apache.org/Apache Shindig gadget container] to render the gadgets; however the SocialMiner gadgets can also be rendered in [[#Advanced_UI_Options|other standard OpenSocial containers]] such as Cisco Quad or iGoogle. All system features and setup can also be performed by [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] APIs. <br /> <br /> SocialMiner supports integration with most user-generated content sites using standard [http://en.wikipedia.org/wiki/RSS RSS]. SocialMiner also supports direct integrations to [http://www.twitter.com Twitter®] and [http://www.facebook.com Facebook®]. Setup and configuration of SocialMiner to monitor Twitter and Facebook requires good working knowledge of those sites. For background information on these sites, review the following Mashable resources: <br /> <br /> [http://mashable.com/guidebook/twitter/ The Twitter Guide Book] <br /> <br /> [http://mashable.com/guidebook/facebook/ The Facebook Guide Book]<br /> <br /> = What's New in Release 8.5(4) =<br /> <br /> Cisco SocialMiner Release 8.5(4) provides the following new features and enhancements: <br /> <br /> '''Bookmarklet''' <br /> <br /> SocialMiner 8.5(4) adds the [[#Adding Feeds using the Feed Bookmarklet|Bookmarklet]] feature for easy creation of Twitter Search and RSS feeds.<br /> Creating a feed using the Bookmarklet&amp;mdash;rather than completing the SocialMiner feed dialog box&amp;mdash;provides a one-click alternative for adding feeds. Once you create a feed using the bookmarklet, you can add it to a campaign and you can edit it in the Feeds gadget&amp;mdash;just as you would a manually-created feed. <br /> <br /> '''Extension Fields''' <br /> <br /> Extension fields are a collection of custom name/value pairs that can be added social contacts using the [[#Push Feed|Push feed]] <br /> sample code. You can add social contact data to email and IM notifications by including extension fields as [[#Notification Body Variables|Notification Body Variables]]. <br /> <br /> '''Filter State Icons'''<br /> <br /> The table on the Filters gadget now includes a '''State''' column, similar to that on the Feeds gadget. Icons in the '''State''' column show if the filter is working successfully (green) or if there is an error for it (red). Hover over the icons for more information.<br /> <br /> '''Script Filter''' <br /> <br /> This is an enhancement for developers. A new filter type&amp;mdash;[[#Script Filters|Script Filter]]&amp;mdash;allows you to upload customer-developed Groovy scripts that modify or take an action on social contacts as they enter the system. A Script filter can integrate with external systems to leverage services such as performing translation or invoking a Klout score. <br /> <br /> Cisco Support and the SocialMiner Forum on the Cisco Developer Network do not assist with Groovy script issues. Direct all troubleshooting requests to your script developer.<br /> <br /> '''Twitter Account Feed&amp;mdash;Reauthorize and Save''' <br /> <br /> When you open a Twitter Account feed in Edit mode, you now see two buttons: '''Save''' and '''Reauthorize and Save'''. A simple edit to a field requires only a '''Save'''. However, if the icon next to the feed is red and the hover text for that red icon indicates authorization issues, select [[#Reauthorize and Save in Edit Mode|Reauthorize and Save]] to initiate the Twitter authorization process.<br /> <br /> = Upgrading to SocialMiner Release 8.5(4) =<br /> <br /> Topics: <br /> <br /> [[#Upgrading_using_Cisco_Unified_Operating_System_Administration|Upgrading using Cisco Unified Operating System Administration]] <br /> <br /> [[#Upgrading_using_the_Command_Line_Interface|Upgrading using the Command Line Interface]] <br /> <br /> &lt;br&gt;SocialMiner Release 8.5(4) is an upgrade to release 8.5(1). Upgrades are cumulative and must be installed over the base release. This means that: <br /> <br /> *You must have installed the base release &amp;mdash;SocialMiner Release 8.5(1). SocialMiner 8.5(1) installation is documented in the [http://docwiki.cisco.com/wiki/SocialMiner_Release_8.5(1) SocialMiner 8.5(1) User Guide.] <br /> *You can upgrade directly from Release 8.5(1) to Release 8.5(4). Release 8.5(4) includes all features and changes of Release 8.5(2) and Release 8.5(3). Features added in Release 8.5(2) are documented here: [http://docwiki.cisco.com/wiki/SocialMiner_Release_8.5(2) What's New in Release 8.5(2).] Features added in Release 8.5(3) are documented here: [http://docwiki.cisco.com/wiki/SocialMiner_Release_8.5(3) What's New in Release 8.5(3).]<br /> *If you are on Release 8.5(2) or Release 8.5(3) you can upgrade directly to Release 8.5(4).<br /> <br /> You can upgrade using the Software Upgrades tool in Cisco Unified Operating System Administration. You can also upgrade using the Command Line Interface (CLI). <br /> <br /> The upgrade can run unattended and might take over an hour to complete. <br /> <br /> == Upgrading using Cisco Unified Operating System Administration ==<br /> <br /> Open Cisco Unified Operating System Administration from the Administration tab &amp;gt; Platform Administration. You can also use this URL <br /> &lt;pre&gt;http://&amp;lt;servername&amp;gt;/cmplatform&lt;/pre&gt;<br /> where ''servername'' is the Hostname or IP address of your SocialMiner server. <br /> <br /> #Select Software Upgrade &amp;gt; Install/Upgrade. <br /> #On the Software Installation /Upgrade dialog box: <br /> ##If you burned the files to CD/DVD: <br /> ###Source = DVD/CD. <br /> ###Directory = the directory for DVD/CD. Use forward slashes. For example, if the installation file is located on the root directory of a CD that is on Drive D, type /D. <br /> ###Server = leave blank. <br /> ###User Name = leave blank. <br /> ###Password = leave blank.<br /> ##If the files are on a remote file server: <br /> ###Source = Remote Filesystem. <br /> ###Directory = the path to the files. Use forward slashes. For example, /SocialMiner/Installation. <br /> ###Server = the IP address of the remote server. <br /> ###User Name = the user name to access the remote server. <br /> ###Password = the password to access the remote server.<br /> #Click Next. <br /> #Choose the iso file from the Software Location field. <br /> #Click Next. <br /> #At the Software Installation/Upgrade screen, select Reboot to Upgraded Partition. <br /> #Click Next.<br /> <br /> You see a series of messages as the upgrade installation proceeds. <br /> <br /> When the upgrade is complete, verify that the system restarts, the correct version is active, and the server status on the System Administration tab shows green checkboxes.<br /> <br /> As a best practice, [http://docwiki.cisco.com/wiki/SocialMiner_User_Interface_-_Clear_Cache_and_Cookies_to_Troubleshoot_Unexpected_Results clear the cache and cookies] after the upgrade.<br /> <br /> == Upgrading using the Command Line Interface ==<br /> <br /> #Download the 8.5(4) Release from Cisco.com and place the file on an FTP or SFTP server. You can also burn the ISO file to DVD. <br /> #SSH to your SocialMiner system and log in with the platform administration account. <br /> #Using the Command Line Interface (CLI), run the command &lt;tt&gt;utils system upgrade initiate&lt;/tt&gt; <br /> #Follow the instructions provided by the &lt;tt&gt;utils system upgrade initiate&lt;/tt&gt; command. An example of executing the command follows:<br /> &lt;pre&gt;admin:utils system upgrade initiate <br /> <br /> Warning: Do not close this window without first canceling the upgrade.<br /> <br /> Source:<br /> <br /> 1) Remote Filesystem via SFTP<br /> 2) Remote Filesystem via FTP<br /> 3) Local DVD/CD<br /> q) quit<br /> <br /> Please select an option (1 - 3 or &quot;q&quot; ): 2<br /> Directory [q]: /FTP/PATH/TO/UPGRADE/IOS<br /> Server [q]: FTP_HOSTNAME<br /> User Name [q]: FTP_USERNAME<br /> Password: ********<br /> Checking for valid upgrades. Please wait...<br /> <br /> <br /> Available options and upgrades in &quot;/FTP/PATH/TO/UPGRADE/IOS&quot;:<br /> <br /> 1) UCSInstall_CCP_8_5_1_UCOS_8.5.4.10000-XX.sgn.iso<br /> q) quit<br /> <br /> Please select an option (1 - 1 or &quot;q&quot; ): 1<br /> Accessing the file. Please wait...<br /> Downloaded XXXX MB.<br /> Checksumming the file...<br /> Downloaded XXXX MB.<br /> A system reboot is required when the upgrade process completes or is canceled. This will ensure services affected by the upgrade process are functioning properly.<br /> <br /> Downloaded: UCSInstall_CCP_8_5_1_UCOS_8.5.4.10000-X.sgn.iso<br /> File version: 8.5.4.10000-X<br /> File checksum: CHECKSUM<br /> <br /> Automatically switch versions if the upgrade is successful (yes/no): yes<br /> <br /> Start installation (yes/no): yes<br /> The upgrade log is install_log_2011-03-10.09.52.58.log<br /> Upgrading the system. Please wait...<br /> 06/10/2011 09:53:00 file_list.sh|Starting file_list.sh|&amp;lt;LVL::Info&amp;gt;<br /> ...<br /> [Many lines of upgrade scripts running]<br /> ...<br /> 06/10/2011 11:41:31 upgrade_install.sh|Upgrade Complete -- (0)|&amp;lt;LVL::Info&amp;gt;<br /> <br /> Successfully installed UCSInstall_CCP_8_5_1_UCOS_8.5.4.10000-XX.sgn.iso<br /> <br /> The system upgrade was successful. A switch version request has been submitted. <br /> &lt;/pre&gt;<br /> <br /> This can take a long time depending on the platform and database size. <br /> Please continue to monitor the switchover process from the Cisco Unified Communications OS Platform [[#Command Line Interface|Command Line Interface (CLI).]] <br /> <br /> The system reboots after the upgrade is complete.<br /> <br /> Please verify that the system restarts, the correct version is active, and the server status on the System Administration tab shows green checkboxes.<br /> <br /> As a best practice, [http://docwiki.cisco.com/wiki/SocialMiner_User_Interface_-_Clear_Cache_and_Cookies_to_Troubleshoot_Unexpected_Results clear the cache and cookies] after the upgrade.<br /> <br /> = Signing In to SocialMiner =<br /> <br /> To launch SocialMiner, use a web browser&lt;sup&gt;*&lt;/sup&gt; to access the root of the web server. Enter <br /> &lt;pre&gt;http://&amp;lt;servername&amp;gt; &lt;/pre&gt;<br /> where ''servername'' is the name or IP address of your SocialMiner server. <br /> <br /> &lt;sup&gt;*&lt;/sup&gt;See [[SocialMiner Browsers|SocialMiner Browsers]] for information on supported browsers. [[Image:SocialMiner login.png|thumb|right|450px|Signing In]] <br /> <br /> Entering the URL opens a sign-in page where you type your username and password. The first time you sign in, you must use the credentials established during the installation for the application user.<br /> <br /> If you have [[#Downloading_and_Installing_Language_Packs|downloaded and installed language files]], the sign in page also has a drop-down for selecting your language. <br /> <br /> When you see a &quot;trusted certificate&quot; warning, acknowledge it&amp;mdash;for example, by clicking ''Continue to Web Site'' in Internet Explorer or ''I understand the Risk'' in Mozilla Firefox. This saves the certificate to the browser. For some browsers, you may want to [[#Obtaining_a_CA-Signed_Certificate|obtain and upload a CA-Signed certificate]] so that the security warnings do not persist. <br /> <br /> A successful sign-in presents the SocialMiner interface to the Home tab. Most users see one other tab: the Configuration tab. Administrators also see an Administration tab.<br /> <br /> = The Home Tab =<br /> <br /> Topics: <br /> <br /> [[#Reviewing_Social_Contacts_By_State|Reviewing Social Contacts By State]] <br /> <br /> [[#Replying_to_Social_Contacts_from_the_Home_Tab|Replying to Social Contacts]] <br /> <br /> [[#Tagging_Social_Contacts|Tagging Social Contacts]] <br /> <br /> [[#Settings|Settings]] <br /> <br /> [[#Training Bayesian Filters|Train Filters]] <br /> <br /> [[Image:SocialMinerHome.png|thumb|right|450px|Administrators see three SocialMiner tabs]] <br /> <br /> The SocialMiner Home tab is a dynamic &quot;Inbox&quot; for viewing and responding to [[#What_is_a_Social_Contact.3F|social contacts]]. No social contacts appear on this tab until you: <br /> <br /> #Configure at least one [[#Feeds|Feed]]. <br /> #Configure at least one [[#Campaigns|Campaign]]. <br /> #Add the Feed to the Campaign. <br /> #Select the Campaign from the drop-down menu on the upper-left.<br /> <br /> You can show social contacts that are in specific states (Open, Handled, or Discarded). You can also open [[#Settings|Settings]] to show only those social contacts with specific tags or to enable training mode for a Bayesian filter. <br /> <br /> The SocialMiner Home tab is dynamic in these ways: <br /> <br /> *A bar appears periodically at the top of the page indicating that there are one or more new social contacts in the campaign. You can click the bar to refresh the results, or click the refresh icon at the upper-right. <br /> *State changes and new tags made by one agent are immediately visible to all agents working in that campaign.<br /> <br /> '''VIDEO:''' View a [http://www.youtube.com/watch?v=iteoPj6B52g&amp;hd=1 video] about handling social contacts on the Home tab. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information.<br /> == What is a Social Contact? ==<br /> <br /> The term Social Contact refers to a post collected by SocialMiner. A social contact can be a Tweet, a Facebook wall post, a Blog, or a Forum post. <br /> <br /> For example: <br /> <br /> #When a customer tweets and the tweet matches the Feed criteria of SocialMiner campaign, that tweet is captured by SocialMiner and stored in the datastore as a social contact. <br /> #An agent's reply to that tweet is captured and saved as another social contact. <br /> #The customer reply to the agent's reply is captured as a third social contact.<br /> <br /> A social contact remains in the datastore until it is [[#Purge_Settings|purged]]. <br /> <br /> SocialMiner stores the following for each social contact: <br /> <br /> *Author&amp;mdash;the username of the person who posted <br /> *Creation Date&amp;mdash;date stored in SocialMiner <br /> *Title <br /> *Description <br /> *Published Date&amp;mdash;date it was published on the Internet (Not all feeds have this.) <br /> *Source type&amp;mdash;the type of feed that collected the social contact <br /> *Tags&amp;mdash;tags applied by SocialMiner users<br /> <br /> == Reviewing Social Contacts By State ==<br /> <br /> A social contact can be in one of four states: Unread, Reserved, Handled, and Discarded. Use the drop-down on the Home tab to show contacts of only that state: <br /> <br /> '''Show Open''' - Open social contacts are those in the ''Unread'' or the ''Reserved'' state. They have not yet been acted on. All social contacts captured by SocialMiner are initially in the Unread state and appear when you Show Open. <br /> <br /> '''Show Handled''' - These social contacts have been handled by an agent. If the social contacts from an RSS feed, the agent has opened them. If the social contacts are from a Twitter or Facebook feed, the agent has replied to them. <br /> <br /> '''Show Discarded''' - These social contacts have been discarded by an agent, perhaps because they do not require response. Discarded contacts remain in the system until they are deleted by the next [[#Purge Settings|purge.]] <br /> <br /> === Working with Social Contacts ===<br /> <br /> A social contact state can be changed by any user at any time by a click of a social contact state button. The name of the last user to change a state appears next to the social contact as soon as the change occurs: for example, ''Discarded: User2''. <br /> <br /> State changing can be done by different agents. For example, Agent1 can reserve a social contact, and Agent2 can handle it. <br /> <br /> '''To undo a state change''', show the list for that state, locate the social contact, and click the icon again to reverse the state. <br /> <br /> For example, if you set a social contact to Handled and then change your mind about handling it: <br /> <br /> #Select Show Handled. <br /> #Locate that social contact. <br /> #Click the Handle icon. This toggles the state of that social contact back to Unread. It is removed from the Show Handled list immediately and returns to the Show Open list within a few seconds.<br /> <br /> Social contact state is universal across the SocialMiner system. For example, if one user handles a social contact, the social contact appears as handled in the browser interface for all other users. This is the case even if the social contact appears in multiple campaigns.<br /> <br /> == Replying to Social Contacts from the Home Tab ==<br /> <br /> [[Image:CampaignResultsCiscoTwitterReply.png|thumb|right|450px|Twitter Reply Template]] <br /> <br /> SocialMiner lets you reply to social contacts using [[#Reply_Templates|Reply Templates]]. There are two system-defined templates: Cisco Twitter and Cisco Facebook. Administrators can add custom reply templates. <br /> <br /> You can select only one reply template per feed, and you do this on the Add/Edit Feed page for each Feed Type. <br /> <br /> === Replying to a Twitter Social Contact ===<br /> <br /> Ways to reply are to: <br /> <br /> *direct-message the author of the Tweet.<br /> <br /> *create an &quot;@&quot; reply that is viewable to everyone on Twitter.<br /> <br /> *configure the feed to respond with the Cisco Twitter reply template, which allows you to follow the recipient of the message if you are not currently following them.<br /> <br /> To reply to a tweet using the Cisco Twitter reply template: <br /> <br /> '''1.''' Select a Twitter Account social contact and click Reply. The Cisco Twitter template opens and provides the following fields: <br /> <br /> *Account: Select the Twitter Account from which you are replying. All Twitter Accounts configured on this system appear in the dropdown menu. <br /> *Once the account is selected, the system checks the Follow status of the intended recipient. If the account is not already following the recipient, you can click Follow to begin following. <br /> *For your convenience, the conversation history of the social contact is listed below the selected social contact. You can reply, retweet, or Direct Message to any tweet in the conversation. The social contact that was originally reserved is marked as handled even if you do not reply to the most recent tweet in the conversation. The status of the other social contacts (tweets) in the conversation does not change. <br /> *Select the type of reply: either Direct Message, retweet, or reply. A pop-up text box appears where you can enter your message. Note: You can only Direct Message a Twitter user if the intended recipient is following you. Replies and retweets are posted to the timeline of the Twitter account. A Direct Message is sent directly to the poster of the tweet. <br /> *Enter your reply in the pop-up text box. Text input is limited to 140 characters. The current character count is listed at the upper right of the text box.<br /> <br /> '''2.''' Click Send to send the reply. This marks the social contact as Handled. <br /> <br /> Note that the reply template is customizable. The instructions above pertain to the default Cisco Twitter template. If your administrator has provided a custom reply template, the steps for replying may be different. <br /> <br /> === Replying to a Facebook Fan Page ===<br /> <br /> Ways to reply are to: <br /> <br /> *click the link on the social contact to open the post or comment and enter your comment.<br /> <br /> *configure the feed to use the Cisco Facebook reply template and respond directly to the Fan Page from SocialMiner.<br /> <br /> Facebook accepts content from a Facebook Reply Template only if the person who [[#Facebook_Fan_Page_Feed_Type|added the Faceboook Fan Page feed]] received authorization from Facebook by clicking '''Get Post Authorization'''. Facebook ensures that the user is a fan of the page and has permission to post.<br /> <br /> '''1.''' Select a Facebook social contact. Click the Reply button. <br /> <br /> The Cisco Facebook Reply form opens to show: <br /> <br /> *the name of the person who posted or commented on the Facebook page. <br /> *a text area for your comment. <br /> *a Like indicator.<br /> <br /> If you have never replied, or if you have previously replied with an Unlike, the template shows Like. If you have previously replied with Like, the template shows Unlike. You can reply without selecting Like or Unlike. <br /> <br /> '''2.''' Click Send to send the reply. This marks the social contact as Handled. <br /> <br /> The instructions above pertain to the default Cisco Facebook reply template. If your administrator has created and configured a custom reply template for Facebook, the steps for replying may be different.<br /> <br /> === Replying to an RSS Social Contact ===<br /> <br /> You cannot reply directly to a social contact from an RSS feed. You can, however, tag the RSS contact and set notifications so that an agent receives an email or an Instant Message for the social contact.<br /> <br /> = Tagging Social Contacts =<br /> <br /> Tags are labels that allow you to categorize social contacts, to track workflow, and to set up [[#Notifications|notifications]]. <br /> <br /> For example, all social contacts that mention billing concerns could be tagged with ''Billing''. You could then set up notifications to email social contacts with that tag to Customer Service. <br /> <br /> You can tag similar social contacts with the same tag, then use the [[#Settings|Settings page]] to filter the list of social contacts to show only social contacts with a particular tag. <br /> <br /> '''Adding Tags''' <br /> <br /> When you hover over a social contact, you see a text box and a '''Tag''' button. <br /> <br /> To enter a tag, click the text box and type the tag. Then press '''Enter''' or click '''Tag'''. The new tags are immediately visible to all users who view that social contact. You can add a maximum of twenty tags to a social contact. Use commas to separate multiple tags.<br /> <br /> Social contacts are not duplicated even when they appear in multiple campaigns. When a user tags a social contact in one campaign, the tag appears to other users who are viewing that social contact from another campaign. <br /> <br /> '''Suggested Tags:''' <br /> <br /> A maximum of ten common or recently used tags for the selected campaign appear as 'suggested tags' links to the right of the Tag button. You might need to click Refresh to see newly-added suggested tags. To add one or more of these suggested tags to the social contact. click the link for the suggested tag. These suggestions provide one-click tagging for commonly used tags. The suggestions are specific to the campaign, not to the entire SocialMiner system, and are only updated on a refresh. <br /> <br /> '''Deleting Tags''' <br /> <br /> To delete a tag from a social contact, click the small, grey x at the right of the tag name. <br /> <br /> '''Automatic Tags''' You can also configure up to ten automatic tags for a feed. All social contacts pulled in for that feed have these auto-tags. See [[#Automatic_Tags_for_Feeds|Automatic Tags for Feeds]]. <br /> <br /> '''VIDEO''': View a [http://www.youtube.com/watch?v=Sy6CIKDyYIM&amp;hd=1 video] about using tags.<br /> Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information.<br /> <br /> = Settings =<br /> <br /> Click the Settings icon at the top right of the Home tab open the Settings page. Use this page to show or hide social contacts by tag and to enable training for a [[#Bayesian Filters|Bayesian filter.]] Although tags and Bayesian filters are global (all users can see them), settings are user-specific. Your changes to Settings determine what ''you'' see for the campaign but do not do not effect what others see in the campaign.<br /> <br /> = Training Bayesian Filters =<br /> <br /> If you have [[#Filters|added a Bayesian filter]], you can select it on the Settings page to activate training mode. <br /> <br /> ''None'' is the default on the Settings page. Selecting a Bayesian filter enables filter training and changes the campaign display on the Home tab to show Plus (+) and Minus (-) training buttons for each social contact. <br /> <br /> *Click the Plus button to mark the social contact as being ''in'' this filter. (This tells SocialMiner: ''Keep social contacts similar to this one. Do not filter out social contacts like this''.)<br /> <br /> *Click the Minus button to mark this social contact as &quot;out&quot; of this filter. (This tells SocialMiner: ''Do not include social contacts like this one''.)<br /> <br /> To disable training mode, return to the Settings page and select ''None''. <br /> <br /> Training settings are user-specific. Your changes to enable training mode do not effect what others see for the campaign.<br /> <br /> = Feeds =<br /> <br /> [[Image:SocialMinerfeeds854.png|thumb|right|300px|SocialMiner Feeds]] <br /> <br /> Topics: <br /> <br /> *[[#Feed States|Feed States]]<br /> *[[#Adding_and_Editing_Feeds|Adding and Editing Feeds]] <br /> *[[#Adding Feeds using the Feed Bookmarklet|Adding Feeds using the Feed Bookmarklet]]<br /> *[[#Feed_Types|Feed Types]] <br /> **[[#RSS_and_Authenticated_RSS_Feeds|RSS and Authenticated RSS Feeds]] <br /> **[[#Facebook_Fan_Page_Feed|Facebook Fan Page Feed]] <br /> **[[#Push_Feed|Push Feed Type]] <br /> **[[#Twitter_Account_Feed|Twitter Account Feed]] <br /> **[[#Twitter_Stream_Feed|Twitter Stream Feed]]<br /> *[[#Polling_Interval_for_Feeds|Polling Interval for Feeds]] <br /> *[[#Minimum_Age_for_Feeds|Minimum Age for Feeds]] <br /> *[[#Automatic_Tags_for_Feeds|Automatic Tags for Feeds]] <br /> *[[#Deleting_Feeds|Deleting Feeds]]<br /> <br /> &lt;br&gt;The Feeds gadget is on the SocialMiner Configuration tab. <br /> <br /> A '''Feed''' is a configured source for capturing social contacts&amp;mdash;a view set of specific data you want to capture. Setting up feeds is a foundational step for your SocialMiner system. You see no social contacts on the Home tab until you configure at least one feed and add it to a campaign. <br /> <br /> '''Note''' If your server is behind a firewall, the administrator may need to configure SocialMiner to use a proxy to reach the internet. See [[#Proxy_settings|Proxy Settings]]. <br /> <br /> '''Note also that''': SocialMiner uses a process called de-duplication to automatically remove duplicate social contacts. For example, if a user configures several ''overlapping'' feeds that capture the same result, then SocialMiner does not capture the same social contact twice. The de-duplication functionality relies on the unique URL of the post. For example, each Tweet or blog has a unique URL. Before SocialMiner creates a new social contact in the datastore, it first verifies that the URL of that social contact is not already in the datastore. <br /> <br /> == Feed States ==<br /> <br /> Icons are used as visual indicators to display the state of each feed. Hover the cursor over the icon to display a tool tip that explains the state.<br /> <br /> == Adding and Editing Feeds ==<br /> <br /> To create a feed, click '''Add''' in the feed list view. To edit the settings for a feed, click its name. <br /> <br /> Select the feed type and complete the fields for the feed type. The fields vary by feed type. <br /> <br /> Social contacts retrieved by feeds are time-limited by the number of days defined in the Purge Social Contacts older than (days) setting of the [[#Purge_Settings|Purge Settings tool]]. (This tool is on the Administration tab and is used by Administrators only.) <br /> <br /> If you change a feed (for example, to rename it, change the URL, or change the polling interval), you do not need to re-add it to the campaign.<br /> <br /> == Adding Feeds using the Feed Bookmarklet ==<br /> <br /> Release 8.5(4) supports creating Twitter Search and RSS feeds using a [http://en.wikipedia.org/wiki/Bookmarklet Bookmarklet]. <br /> <br /> Bookmarklets are &quot;smart bookmarks&quot; that include JavaScript. Creating a feed using the Feed Bookmarklet is a one-click method for adding feeds to SocialMiner and eliminates the need to complete fields on the Add Feed form and to copy/paste the URL.<br /> <br /> '''To get and use the Bookmarklet:''' <br /> <br /> 1. From the Feed Configuration gadget, drag the ''Feed Bookmarklet'' link at the bottom of the gadget to the Mozilla Firefox Bookmarks toolbar. (If you click the Feed BookMarklet link directly, you see a message instructing you to drag the link to the toolbar.) The Feed Bookmarklet remains on the toolbar unless you delete it, although there is no reason to do so. <br /> <br /> 2. Navigate to a Twitter ad-hoc or saved Search result page or to a website with RSS feeds.<br /> <br /> 3. From that page, click the Feed Bookmarklet bookmark that you dragged to the Bookmarks toolbar. A message displays if the page has no feeds.<br /> <br /> 4. If you are prompted to log in, enter your SocialMiner login credentials. You must authenticate once per browser session. <br /> <br /> 5. For Twitter Searches, a SocialMiner window opens indicating that a feed for the search was saved, along with the Name and URL of the feed. If the feed was not saved, you see a message indicating the problem. <br /> <br /> 6. For websites with RSS feeds, the SocialMiner window captures all feeds on the page and filters them with icons indicating whether they are standard feeds or possible feeds.<br /> *A green checkmark displays for standard feeds. SocialMiner qualifies RSS feeds as &quot;standard&quot; when their URLs are indicated as such by the website. <br /> *A blue question mark indicates that the feed is possibly an RSS feed, but may not be. SocialMiner qualifies RSS feeds as &quot;possible&quot; when their URLs simply contain &quot;rss&quot;, &quot;atom&quot;, or &quot;feed&quot;.<br /> Note that some URLs may be filtered out of the list even if they meet the above criteria&amp;mdash;for example, they will not be captured and displayed if they include embedded scripting. <br /> <br /> 7. Click the link that you want to add as a feed. The SocialMiner window updates to indicate that the feed was saved, along with the Name and URL of the feed. You see an error message if there was a problem saving the feed. <br /> <br /> 8. Close and re-open the Feed Bookmarklet for each URL in the list that you want to save. You see an error if you try to save a duplicate feed (a feed with the same Name as one that is already saved). <br /> <br /> 9. After saving a feed, navigate to the SocialMiner Configuration tab. The feed displays in the Feed gadget list. Feed names are truncated at 85 characters. <br /> <br /> 10. Proceed as you would with any feed to edit the name, description, polling interval, and minimum age; and to add automatic tags. <br /> <br /> 11. Add the feed to a campaign.<br /> <br /> == Feed Types ==<br /> <br /> SocialMiner supports the following types of Feeds. Each feed type has unique settings, which are described in the sections below: <br /> <br /> *[[#RSS_and_Authenticated_RSS_Feeds|RSS and Authenticated RSS]] <br /> *[[#Facebook_Fan_Page_Feed|Facebook Fan Page]] <br /> *[[#Push_Feed|Push Feed]] <br /> *[[#Twitter_Account|Twitter Account]] <br /> *[[#Twitter_Stream|Twitter Stream - Administrators only]]<br /> <br /> &lt;br&gt;<br /> <br /> === RSS and Authenticated RSS Feeds ===<br /> <br /> RSS is one of the simplest and most widely-available means for SocialMiner to capture social contacts, because there are many forum and blog sites that support [http://en.wikipedia.org/wiki/RSS RSS]. You can create an RSS feed as described below; you can also create a feed using the [[#Adding_Feeds_as_Bookmarklets|Feed Bookmarklet]]. <br /> <br /> SocialMiner supports the following RSS Feed standards: <br /> <br /> *[http://validator.w3.org/feed/docs/rss1.html RSS 1.0] <br /> *[http://validator.w3.org/feed/docs/rss2.html RSS 2.0] <br /> *[http://tools.ietf.org/html/rfc4287 ATOM 1.0]<br /> <br /> The Authenticated RSS feed type is similar to RSS but requires [http://en.wikipedia.org/wiki/Basic_access_authentication basic authentication]. The username and password are encrypted and stored in the SocialMiner configuration database. <br /> <br /> '''VIDEOS:''' <br /> <br /> *View a [http://www.youtube.com/watch?v=YneS1h1catg&amp;hd=1 video] about adding RSS Feeds. <br /> *View a [http://www.youtube.com/watch?v=L9YhIEpKC5c&amp;hd=1 video] about adding Authenticated RSS Feeds.<br /> <br /> Although these videos were created for an earlier version of SocialMiner and show an older user interface, they present accurate information. <br /> <br /> &lt;br&gt;'''About Paging from RSS Feeds''' <br /> <br /> SocialMiner does not support the reading of multiple &quot;pages&quot; from an RSS feed. SocialMiner captures the posts that are presented on the first (main) page returned by a site. This limitation prevents the system from capturing posts prior to the current page of results and allows SocialMiner to capture all results going forward as long as the site generates a page or less of results in each interval. <br /> <br /> Some sites allow the URL to specify the number of results on a page. If you use this feature to set the number of results to return and you also regulate the polling interval, you can optimize system performance and reduce load on the site, while ensuring all posts are captured. <br /> <br /> '''Configuring RSS and Authenticated RSS''' <br /> <br /> To configure an RSS or Authenticated RSS feed: <br /> <br /> #Access the Feed gadget. <br /> #Click Add. <br /> #Select RSS or Authenticated RSS feed type, and enter the following fields:<br /> <br /> *Type—Required <br /> *Name—Required <br /> *Description <br /> *URL—Required. This must be a valid RSS Feed <br /> *Username—Username for the feed. Required for Authenticated RSS feed. Not Applicable to RSS Feed. <br /> *Password—Password for the feed. Optional for the Authenticated RSS feed. Not Applicable to RSS Feed. <br /> *[[#Polling_Interval_for_Feeds|Polling Interval]]—Number of minutes to wait between refreshing this feed. <br /> *[[#Minimum_Age_for_Feeds|Minimum age]]—The number of hours old a post must be before it is included as a result. This allows you to exclude recent posts.<br /> <br /> 4. Optionally, provide [[#Automatic_Tags_for_Feeds|Automatic Tags]] for the feed. <br /> <br /> 5. Click '''Save''' to save the feed.<br /> <br /> === Facebook Fan Page Feed ===<br /> <br /> '''About Facebook Fan Page Feeds''' <br /> <br /> The Facebook Fan Page Feed type captures all wall posts and comments on wall posts that are posted to a Fan Page. <br /> <br /> Fan Pages are public, and no username or password is required to capture the postings on a Facebook Fan Page. This means it is possible to capture postings on Fan Pages operated by a company as well as Fan Pages set up by independent parties or even competitors. <br /> <br /> Facebook wall posts and comments are captured by SocialMiner and rendered in a time-sorted stream. This rendering differs from the standard Fan Page layout. The goal of this layout is to ensure that 100% of the wall posts and comments are noticed by the consumer of the results. It is more difficult to achieve this goal when viewing the wall posts and comments directly on Facebook, as they are grouped by wall post instead of time-sorted. <br /> <br /> When displayed in SocialMiner, Facebook wall posts and comments are differentiated by the format of the title: <br /> <br /> *''Facebook post from [first name] [last name]''<br /> <br /> *''Facebook comment from [first name] [last name] for &quot;[post]&quot;''<br /> <br /> The link in the title provides a direct link to the wall post on Facebook. Note that Facebook does not anchor comments, therefore the link takes the browser to the wall posts to which the comment refers and not directly to the comment. <br /> <br /> '''SocialMiner requires a clean Fan Page &quot;Vanity URL&quot;.''' You will notice that Facebook appends certain parameters to a URL depending on how you navigated to the URL. For example, when you find the Cisco Contact Center Fan Page through Facebook search, you see this URL: http://www.facebook.com/#!/CiscoCC?ref=ts. However the direct URL for the fan page is http://www.facebook.com/CiscoCC. This base URL is what Facebook refers to as the &quot;Vanity URL&quot;. The name &quot;CiscoCC&quot; was registered by the administrator of this page. <br /> <br /> '''Note that''' some Fan Pages that have a number instead of a text name. (This is not common.) These are pages that have not yet registered a Vanity URL. In this case, the URL with the number satisfies the requirements of SocialMiner configuration. <br /> <br /> '''Configuring a Facebook Fan Page Feed''' <br /> <br /> '''VIDEO''': View a [http://www.youtube.com/watch?v=xHCjtcHbNws&amp;hd=1 video] about configuring a Facebook Fan Page Feed. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information. <br /> <br /> &lt;br&gt;To configure a Facebook Fan Page feed: <br /> <br /> #Access the Feed gadget. <br /> #Click Add. <br /> #Select Facebook Fan Page feed type, and enter the following fields:<br /> <br /> *Type—Required <br /> *Name—Required <br /> *Description <br /> *URL—Required. This must be a valid Facebook Fan page The URL must start with &lt;tt&gt;http://www.facebook.com&lt;/tt&gt; <br /> *[[#Polling_Interval_for_Feeds|Polling Interval]]—Number of minutes to wait between refreshing this feed. <br /> *[[#Minimum_Age_for_Feeds|Minimum age]]—The number of hours old a post must be before it is included as a result. This allows you to exclude recent posts. <br /> *Reply template—The reply template to be used for replying to social contacts obtained from this feed. Defaults to the Cisco Facebook Reply Template. <br /> *Optionally, provide [[#Automatic_Tags_for_Feeds|Automatic Tags]] for the feed.<br /> <br /> 4. When you complete the fields, you must '''Authorizing the Feed'''. To do this: <br /> <br /> *Click '''Get Post Authorization''' to request authorization from Facebook that allows SocialMiner to post to the fan page. This opens Facebook. <br /> *Sign in with your organization's Facebook username and password. Then click '''Allow''' to allow the Cisco Facebook Reply Template to post to the Facebook Fan Page.<br /> <br /> Successful Authorization creates and saves the feed. <br /> <br /> Posted replies will appear as being from the user who authenticated the posting. For example, if the posting was authorized by the Facebook account for Harrison Dental and employee Dr. Lee replies to a social contact, her reply is from Harrison Dental and not from her own Facebook account.<br /> <br /> === Push Feed ===<br /> <br /> The push feed type allows you to &quot;push&quot; social contacts directly to SocialMiner through HTTP GET requests. A push feed is an interface for generating a social contact through a web form. <br /> <br /> Using the Feed gadget, create a new feed and select the '''Push''' feed type. <br /> <br /> '''1.''' Enter or edit the following fields. <br /> <br /> *Type—Required <br /> *Name—Required <br /> *Description <br /> *Reply template - The reply template to be used for replying to social contacts obtained from this feed. <br /> *Optionally, provide [[#Automatic_Tags_for_Feeds|Automatic Tags]] for the feed.<br /> <br /> '''2.''' Save the Push Feed. <br /> <br /> '''3.''' Click the saved Push Feed from the list of Feeds to open it in Edit mode. You see a Sample Code link. The sample link contains working HTML code that displays the form fields you want for the GET request for your feed. These include Title, Author, and Description, Tags, and one Extension Field. Extension fields are a collection of custom name/value pairs for a social contact. In the default code, there is one Extension Field—Remarks. You can add additional Extension Fields. See [[#What.27s_New_in_Release_8.5.284.29|What's New in SocialMiner Release 8.5(4)]] for more on Extension Fields. The code also includes ''&amp;lt;input type='submit' value='Submit'/&amp;gt;'' <br /> <br /> &lt;br&gt;<br /> &lt;pre&gt;&amp;lt;style type='text/css'&amp;gt;span { display: inline-block; width: 100px; }&amp;lt;/style&amp;gt;<br /> &amp;lt;form action='http://10.86.141.251/ccp-webapp/ccp/pushfeed/100011' method='get'&amp;gt;<br /> &amp;lt;span&amp;gt;Title:&amp;lt;/span&amp;gt;&amp;lt;input type='text' name='title' /&amp;gt;&amp;lt;br/&amp;gt;<br /> &amp;lt;span&amp;gt;Author:&amp;lt;/span&amp;gt;&amp;lt;input type='text' name='author' /&amp;gt;&amp;lt;br/&amp;gt;<br /> &amp;lt;span&amp;gt;Description:&amp;lt;/span&amp;gt;&amp;lt;input type='text' name='description' /&amp;gt;&amp;lt;br/&amp;gt;<br /> &amp;lt;span&amp;gt;Tags:&amp;lt;/span&amp;gt;&amp;lt;input type='text' name='tags' /&amp;gt;&amp;lt;br/&amp;gt;<br /> &amp;lt;span&amp;gt;Remarks:&amp;lt;/span&amp;gt;&amp;lt;input type='text'name='extensionField_remarks'/&amp;gt;&amp;lt;br/&amp;gt;<br /> value='sample value' /&amp;gt;&amp;lt;br&amp;gt;<br /> &amp;lt;input type='submit' value='Submit'/&amp;gt;<br /> &amp;lt;/form&amp;gt;<br /> &lt;/pre&gt;<br /> '''4.''' Copy this code and save it as HTML. Edit the fields; then click Submit from the HTML form. <br /> <br /> The code is authenticated against SocialMiner, and a URL to the new social contact is returned. The social contact will appear in the campaign that includes the Push Feed. <br /> <br /> If the tags in the Push feed code are associated with notification rules, the notifications will trigger immediately when the social contact is submitted. <br /> <br /> You can have multiple independent Push feeds on one SocialMiner system. <br /> <br /> The Push Feed must be associated with a campaign in order to activate. As a best practice, create a test campaign prior to testing your Push Feed.<br /> <br /> === Twitter Account Feed ===<br /> <br /> '''About the Twitter Account Type Feed''' <br /> <br /> '''VIDEO''': View a [http://www.youtube.com/watch?v=9sIUUVp-WOo&amp;hd=1 video] about configuring a Twitter Account Feed. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information. <br /> <br /> See also [http://docwiki.cisco.com/wiki/SocialMiner_Twitter SocialMiner Twitter.] <br /> <br /> The Twitter Account Feed Type uses the [http://apiwiki.twitter.com/Twitter-API-Documentation Twitter REST API]. This Feed type captures all of the Mentions and Direct Messages for a Twitter account. Twitter Account Feeds include all of the tweets that include &quot;@USERNAME&quot; as well as all of the Direct Messages to the @USERNAME account. This Feed type also captures tweet type, for example ''retweet'' or ''in-reply-to''. You can have only one Twitter Account for the same user per SocialMiner system. <br /> <br /> The Twitter Account feed is configured using [http://en.wikipedia.org/wiki/OAuth OAuth]. During the feed configuration, SocialMiner redirects the user to Twitter to validate the Twitter account. This provides a security benefit, as using OAuth avoids the storage of the user's Twitter account information on the SocialMiner server. Clicking Save opens the Twitter authentication service in a new browser window. (You might need to authorize pop-ups in your browser.) Follow the directions on the screen to authorize SocialMiner to access the Twitter account. <br /> <br /> If you are already signed in to Twitter using the same account you entered in the Feed configuration, click Allow. <br /> <br /> If you are not signed in at all, you will be prompted to enter the Twitter Username and Password for the account. It is also possible that you are logged in to a different Twitter account, perhaps your personal account. If that is the case, click sign out, then sign in with the correct account and click Authorize app. After you click Authorize app, the browser window closes and you return to the Feed Configuration gadget with your new feed successfully created. <br /> <br /> You have now authorized SocialMiner to access all Twitter functionality for this account. <br /> <br /> Note that Twitter Accounts are [https://dev.twitter.com/docs/rate-limiting/faq rate-limited] by Twitter. <br /> <br /> Based on their authorization, Twitter provides SocialMiner with a key to enable access to the account. From this point forward, SocialMiner will be able to use the Twitter account. If any issues arise, you can [[#Reauthorize_and_Save_in_Edit_Mode|Reauthorize and Save in Edit Mode.]] <br /> <br /> Twitter provides a list of applications (connections) that have been granted access to a Twitter account. A Twitter user can revoke access at any time. See http://twitter.com/settings/connections. <br /> <br /> '''Configuring a Twitter Account Feed''' <br /> <br /> #Access the Feed Gadget. <br /> #Click Add. <br /> #Select the Twitter Account feed type, and enter or following fields:<br /> <br /> *Type—Select the Twitter Account feed type from the dropdown. Required <br /> *Name—The name of the feed. Required <br /> *Description <br /> *Username—Required. A valid Twitter username for the user you will be posting as. '''Note:''' Only one Twitter Account Feed per Twitter username per SocialMiner server is allowed. <br /> *[[#Polling_Interval_for_Feeds|Polling Interval]]—Number of minutes to wait between refreshing this feed. <br /> *[[#Minimum_Age_for_Feeds|Minimum age]]—The number of hours old a post must be before it is included as a result. This allows you to exclude recent posts. <br /> *Reply template—The reply template to be used for replying to social contacts obtained from this feed. Defaults to the Cisco Twitter Reply Template. <br /> *Optionally, provide [[#Automatic_Tags_for_Feeds|Automatic Tags]] for the feed.<br /> <br /> 4. Click '''Save'''. <br /> <br /> '''Save''' redirects you to the Twitter authentication service, which allows you to approve the use of this application with your Twitter account. Follow the directions on the screen to enter credentials to authorize access to the Twitter account. <br /> <br /> ==== Reauthorize and Save in Edit Mode ====<br /> <br /> When you edit a Twitter Account feed, you see two buttons: Save and Reauthorize and Save. <br /> <br /> If the icon next to a Twitter Account feed is red and the hover text for that icon reports authorization issues, open the Feed to edit it. Click Reauthorize and Save to initiate the Twitter authorization process. <br /> <br /> If there is no indication that you need to reauthorize but you want to edit the feed for other reasons—for example, to change the Polling Interval—make the change and click Save.<br /> <br /> === Twitter Rate Limit ===<br /> <br /> Twitter Rate Limit <br /> <br /> Note that [https://dev.twitter.com/docs/rate-limiting/faq Twitter Accounts are rate-limited by Twitter,] with the following limits: <br /> <br /> *Direct Messages: 250 per day. <br /> *Updates: 1,000 per day. The daily update limit is further broken down into smaller limits for semihourly intervals. Retweets are counted as updates. <br /> *Changes to Account Email: 4 per hour. <br /> *Following (daily): 1,000 per day. Please note that this is a technical account limit only, and there are additional rules prohibiting aggressive following behavior. <br /> *Following (per account): After an account is following 2,000 other users, additional follow attempts are limited by account-specific ratios.<br /> <br /> &lt;br&gt;When the Twitter rate limit has been reached, the hover text for the feed warning icon shows text similar to this: &quot;Rate limit reached. Feed will reactivate at 10:39 AM Last successful fetch time was 2 minutes ago, Success rate is 50%.”. <br /> <br /> === Twitter Stream Feed ===<br /> <br /> '''About the Twitter Stream Feed''' <br /> <br /> &lt;font color=&quot;#ff0000&quot;&gt;'''Important: Only one Twitter Stream per SocialMiner server is supported.'''&lt;/font&gt; Your server IP will be blacklisted by Twitter if you configure multiple Twitter Stream feeds. If your IP is blacklisted by Twitter, you must delete all Twitter Stream feeds and wait approximately 2 hours to remove your IP from the Twitter blacklist. <br /> <br /> If you require multiple Twitter Streams, you must discuss this need with Twitter or deploy two SocialMiner systems. If you have more than one SocialMiner system going through a single proxy, or you are using some other software system that uses Twitter Streams through that same proxy, your Proxy will be blacklisted by Twitter. <br /> <br /> The Twitter Stream feed type uses the [http://dev.twitter.com/pages/streaming_api Twitter Stream API] or what is sometimes referred to as the &quot;firehose&quot; interface on Twitter to provide realtime access to Tweets. This interface provides different capabilities than the [http://search.twitter.com/ Search API.] A benefit of this Twitter Stream is the speed and efficiency of capturing greater tweet volume at faster speeds. There is no polling interval since the interface pushes the Tweets to the SocialMiner server. The Twitter Stream API also provides more meta-data associated with the tweets then the Search API. For example, the Twitter Stream API provides the indication that a Tweet is in-reply-to another Tweet (this is not available via RSS). <br /> <br /> A downside of the Twitter stream API is that it provides less searching/filtering capability then the search API. The interface supports keyword searching but, for example, it does not support exclusion of keywords. This limited searching capability results in more on-board filtering by the SocialMiner server. Also, the Twitter Stream reply does not provide historical results; therefore downtime in the SocialMiner system could result in missed Tweets. <br /> <br /> The Twitter Stream API requires authentication. A Twitter account username and password is required to configure this type of feed. '''Note: Twitter only allows one Twitter Stream connection per account'''. If there are unrelated Twitter keyword searches required then you must configure multiple Twitter accounts, since adding unrelated keywords to one stream makes SocialMiner Campaign and Filter configuration difficult. <br /> <br /> When Tweets are captured by SocialMiner using the Twitter Stream, the heading in the social contact indicates the type of Tweet. For example, the heading indicates if the social contact is a &quot;Tweet&quot; or &quot;ReTweet&quot; or if it is &quot;in-reply-to&quot;. This type of context is not available when capturing Tweets via RSS. <br /> <br /> See also [http://docwiki.cisco.com/wiki/SocialMiner_Twitter SocialMiner Twitter.] <br /> <br /> &lt;br&gt;'''Configuring a Twitter Stream Feed Type''' <br /> <br /> '''VIDEO''': View a [http://www.youtube.com/watch?v=E_JXmPaNiFk&amp;hd=1 video] about configuring a Twitter Stream Feed. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information. <br /> <br /> &lt;br&gt;<br /> <br /> #Access the Feed gadget. <br /> #Click '''Add'''. <br /> #Select the Twitter Stream feed type, and enter following fields.<br /> <br /> *Type—Required <br /> *Name—Required <br /> *Description <br /> *Search Keywords—Required. A comma separated listed of search words to search on. Up to 200 keywords can be defined for a total limit of 2000 bytes. <br /> **Each keyword must be between 1-60 bytes. <br /> **At least one keyword must be defined. <br /> **Commas in the keyword search stand for OR. Spaces in the keyword search stand for AND. You cannot search for exact strings. For example, if you enter &quot;Cisco Telepresence&quot; then the social contact returned contains Cisco and Telepresence in them, but not necessarily the phrase Cisco Telepresence. <br /> **Do Not Use a Space after a Comma. If you use a space after a comma then only the first keyword is matched against.<br /> *Username—Required. A valid Twitter username. <br /> *Password—Required. Password for the Twitter username. <br /> *Reply template - The reply template to be used for replying to social contacts obtained from this feed. Defaults to the Cisco Twitter Reply Template. <br /> *Optionally, provide [[#Automatic_Tags_for_Feeds|Automatic Tags]] for the feed.<br /> <br /> 4. Click '''Save''' to save the feed.<br /> <br /> === Polling Interval for Feeds ===<br /> <br /> The ''polling interval'' controls how often the SocialMiner system requests the feed. A shorter polling interval provides more frequent updates but creates more load on the SocialMiner server and on the sites publishing the feed. Some sites may have recommendations or restrictions on frequent polling and could block an application that polls too frequently. <br /> <br /> The default SocialMiner polling interval for feeds is five minutes. <br /> <br /> === Minimum Age for Feeds ===<br /> <br /> Use the minimum age setting to filter out recent posts. <br /> <br /> This feature was implemented for forum sites that publish feeds of &quot;unanswered posts.&quot; If you configure the &quot;unanswered posts&quot; feed URL in SocialMiner and set a long Minimum Age, for example 24 hours, the system only captures posts that are both unanswered (based on the RSS feed) and are older than 24 hours (based on the Minimum Age). This offers a simple way to implement the business strategy of light touch forum moderation. <br /> <br /> Minimum Age is not applicable for Push Feeds or Twitter Stream Feeds.<br /> <br /> === Automatic Tags for Feeds ===<br /> <br /> All feeds support the Automatic tags feature, which allows you to specify up to ten tags that are applied to new social contacts for a feed across all campaigns that include that feed. <br /> <br /> To add an automatic tag to the feed, enter one or more tags into the Automatic Tags text box (separated by commas), then click Add. <br /> <br /> To remove an automatic tag from the feed, click the small x next to the tag name.<br /> <br /> == Deleting Feeds ==<br /> <br /> Select the checkbox to the left of one or more Feed Names and click Delete. A confirmation dialog box appears. Click OK to confirm deletion of the selected feed(s).<br /> <br /> = Campaigns =<br /> <br /> Topics: <br /> <br /> [[#Campaign_List|Campaign List]] <br /> <br /> [[#Add_and_Editing_Campaigns|Add and Editing Campaigns]] <br /> <br /> [[#Deleting_Campaigns|Deleting Campaigns]] <br /> <br /> The Campaigns gadget is on the SocialMiner Configuration tab. <br /> <br /> The purpose of a campaign is to group social contacts for handling by the social media customer care team. Social contacts are included in a campaign when one or more [[#Feeds|feeds]] are configured and are selected to be part of the campaign. When a feed becomes part of a campaign, new social contacts that arrive on that feed are immediately added to the campaign and appear on the Home tab. Optionally, campaigns can also have [[#Filters|filters]], which are used to narrow or modify the set of social contacts that are added to the campaign. <br /> <br /> Social contacts can be discarded, but they are not actually removed from a campaign until they are [[#Purge Settings|purged]] or the campaign is deleted. <br /> <br /> '''VIDEO''': View a [http://www.youtube.com/watch?v=6B28gxnFYtI&amp;hd=1 video] about Campaigns, Campaign usage, and Campaign configuration. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information.<br /> <br /> <br /> == Campaign List ==<br /> <br /> For all SocialMiner campaigns, the Campaign Gadget shows: <br /> <br /> *the name of the campaign <br /> *the number of social contacts in the campaign <br /> *a description of the campaign, and <br /> *an RSS feed icon that is a link to the RSS feed ''from'' SocialMiner. The RSS feed allows someone to capture all the social contacts in a campaign using a RSS reader.<br /> <br /> This list updates in real time. For example, it updates when another user adds a new campaign to the system, and the social contact count increments when new social contacts are retrieved for a campaign.<br /> <br /> == Add and Editing Campaigns ==<br /> <br /> To add a campaign, click Add in the campaign list view. Fill out the following fields, then click Save to save the new campaign. <br /> <br /> #Enter a Name (required)<br /> # Enter a Description (optional) <br /> # Use the arrows in the Feeds and Filters panels to move one or several feeds and filters between the Available and Selected panes. You can save a campaign without adding a feed, but no social contacts will be retrieved for a campaign that has no feeds. [[#Filters|Filters]] are optional.<br /> #Click Save.<br /> <br /> Note: Once you click Save, the social contacts for the configured feeds are added to the campaign. Once added, social contacts can be discarded but cannot be removed from the campaign except by a [[#Purge Settings|purge.]] If a feed is removed from a campaign, new social contacts captured by that feed are no longer added to the campaign, but the social contacts previously included are not removed until the purge. <br /> <br /> '''Note:''' if a feed is accidentally added to a campaign, and the social contacts MUST be immediately removed from that campaign, the only recourse is to delete the entire campaign and recreate it. <br /> <br /> Adding a feed to multiple campaigns does not duplicate the social contacts in the datastore. The social contacts for that feed are simply counted in both campaigns.<br /> <br /> == Deleting Campaigns ==<br /> <br /> To delete a campaign, select the checkbox to the left of one or more campaign names and click Delete. A confirmation dialog box appears. Click OK to confirm deletion of the selected campaign(s).&amp;nbsp;<br /> <br /> = Filters =<br /> <br /> Topics: <br /> *[[#Filter States|Filter States]]<br /> *[[#Types_of_Filters|Types of Filters]]<br /> *[[#Adding_and_Editing_Filters|Adding and Editing Filters]] <br /> *[[#Deleting_Filters|Deleting Filters]]<br /> <br /> The purpose of a filter is to modify and take action on social contacts as they enter the system and before they appear on the Home tab, allowing the social media customer-care team to focus on the most actionable social contacts.<br /> <br /> Filters are run against social contacts as they enter a campaign. Filters do not run retroactively against social contacts that are already in a campaign. <br /> <br /> You ''create'' filters in the Filter gadget on the Configuration tab. <br /> <br /> You ''apply'' filters to campaigns in the Campaign Gadget by moving them between the Available and Selected panes, similar to adding and removing feeds. SocialMiner allows a total of 20 filters, and you can add a maximum of 10 filters to a campaign. Applying multiple filters to a campaign creates opportunities to layer filtering strategies to fine-tune results. <br /> <br /> '''Note:''' When multiple filters are applied to a campaign, they are processed simultaneously. For this reason, you might have unexpected results for social contacts that have been processed by multiple filters.<br /> <br /> <br /> == Filter States ==<br /> <br /> Icons are used as visual indicators to display the state of each filter. Hover the cursor over the icon to display a tool tip that explains the state.<br /> <br /> *A green icon means the filter is working properly.<br /> <br /> *A red icon means an error occurred in the uploaded script filter, or the script filter violates SocialMiner security restrictions. Hover over the error icon to display a tool tip with the error text. '''NOTE''' that Cisco Support and the SocialMiner Forum on the Cisco Developer Network do not assist with Groovy script issues. Direct all troubleshooting requests to your script developer.<br /> <br /> *A blue icon appears during a brief interim state while SocialMiner checks the status of the filter, after which the icon changes to red or green.<br /> <br /> == Types of Filters ==<br /> <br /> SocialMiner supports three types of filters: <br /> <br /> *[[#Bayesian Filters|Bayesian]] <br /> *[[#Author Filters|Author]]<br /> *[[#Script Filters|Script]]<br /> <br /> === Bayesian Filters ===<br /> <br /> '''VIDEO''': View a [http://www.youtube.com/watch?v=a1s5VTPaj6g&amp;hd=1 video] about using Bayesian Filters. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information.<br /> <br /> <br /> The Bayesian filter is a trainable filtering technology based on a [http://en.wikipedia.org/wiki/Bayesian_probability Bayesian] statistical probability model. <br /> Bayesian filters are not pre-programmed or configured with business rules. You must apply a Bayesian filter to a campaign and then train the filter to recognize the content of &quot;good&quot; social contacts. When training a Bayesian Filter, you have the option to &quot;train in&quot; or &quot;train out&quot; each social contact in a campaign. After a sufficient amount of training, the filter begins to exclude unwanted social contacts from a campaign. See [[#Train Bayesian Filters on the Home Tab |Train Bayesian Filters on the Home Tab]].<br /> <br /> The Bayesian filters can be used to for many reasons. <br /> <br /> *A filter can take a broad keyword search and narrow the results down to the posts related to a specific brand. For example, a search for &quot;Finesse&quot; could return posts about hair products, Cisco software, and contract bridge. If the purpose of the campaign is to capture posts about the Cisco Finesse, the Bayesian Filter can be trained to exclude the social contacts about haircare and bridge.<br /> <br /> *A filter can be trained to look for social contacts with negative sentiment (or positive sentiment), focusing the work of a customer support or marketing team.<br /> <br /> *Filters can also be trained to include or exclude social contacts written in specific languages.<br /> <br /> The training includes the complete text of the post, not just certain keywords, and therefore offers much more sophisticated filtering capability then a keyword exclusion approach to filtering. <br /> <br /> [[Image:SocialMinerCampaignResultsTrainingMode853.png|thumb|right|450px|Training a Bayesian Filter]] <br /> <br /> You can train a Bayesian filter using any campaign. Choose a campaign with some social contacts and open the Settings page to select the Bayesian filter you want to train. Then Save and close the Setting page. This puts you in training mode. <br /> <br /> The name of the filter you've selected is at the top left of the Home tab, and you see a &quot;+&quot; and &quot;-&quot; button for each social contact. Click the &quot;+&quot; to &quot;Train In&quot; the social contact, indicating that this is the type of contact you would like the Filter to keep in the Campaign. Click the &quot;-&quot; to &quot;Train Out&quot; the social contact, indicating that this is the type of contact you would like the filter to reject. <br /> <br /> The training does not impact the campaign until you [[#Add_and_Editing_Campaigns|edit the campaign]] and move the filter from Available to Selected. <br /> <br /> As a best practice, create a test campaign that mirrors an existing &quot;in production&quot; campaign. Add several feeds to the test campaign - some that you know will have relevant posts and some with irrelevant posts. Create the filter and set the test campaign to training mode. The more you train the filter, the better the filter will perform, so it is important to do a significant amount of training before applying your filter to the &quot;production&quot; campaign.<br /> <br /> === Author Filters ===<br /> <br /> View a [http://www.youtube.com/watch?v=9RafH_8KV5c&amp;hd=1 video] about using Author Filters. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information.<br /> <br /> <br /> The Author filter allows you to exclude specific social-contact authors. Social contacts posted by an author identified in an Author filter do not enter a campaign. For example, you may want to filter out your own posts or posts from team members. <br /> <br /> Configuring an Author filter keeps your posts from showing up in your campaign and therefore reduces the number of posts you need to handle. It also improves the accuracy of the reporting metrics by excluding your own posts.<br /> <br /> === Script Filters ===<br /> <br /> A script filter is custom code that system developers can create in the Groovy Scripting language. A script filter can apply tags, can change content, and can integrate with external systems to leverage services such as performing translation or invoking a Klout score for a social contact retrieved from a Twitter Account feed. <br /> <br /> You can upload multiple Groovy scripts and attach each to a SocialMiner Script filter. There are examples of script filters in the SocialMiner 8.5(4) Developers Guide and on the Cisco Developer Network (CDN).<br /> <br /> SocialMiner runs scripts in Groovy 1.8.<br /> <br /> '''NOTE:''' During the upload, SocialMiner performs a basic syntactic validation but cannot validate that the script will work as expected. For this reason, test your scripts on a lab system before using them in production. SocialMiner also performs security checks on each script. For example, a script will not run if it will shut down the system, take longer than 30 seconds to execute, or access the SocialMiner file system. <br /> <br /> For more on Script Security, refer to the SocialMiner Developers Guide. Scripts errors are visible when you hover the cursor over the filter icons on the [[#Filters|Filters gadget.]] You can also open the Runtime Error logs in the [[#System Logs|Log Directory]] to view the list of security breaches. Under the filename ''runtime/'', open the ''Error-runtime'' log and search for SCRIPT_FILTER_EXCEPTION.<br /> <br /> [[Image:SocialMinerLogs.png|thumb|none|450px|SocialMiner Logs]]<br /> <br /> You will be able to upload scripts that fail the security model and apply them to campaigns, but they will have no effect on the social contacts. The [[#Filters|Filters gadget.]] will show a red (failure) icon for the insecure script.<br /> <br /> == Adding and Editing Filters ==<br /> <br /> '''To add a Bayesian filter:'''<br /> #Click Add. <br /> #Select Type&amp;mdash;Bayesian from the drop-down&amp;mdash;Required. <br /> # Enter a Name&amp;mdash;Required. Name must be unique.<br /> # Enter a Desciption&amp;mdash;Some text to describe this filter.<br /> #Click Save.<br /> <br /> '''To edit a Bayesian filter,''' click the filter's name. <br /> <br /> '''To add an Author filter:'''<br /> #Click Add. <br /> #Select Type&amp;mdash;Author from the drop-down&amp;mdash;Required. <br /> #Enter a Name&amp;mdash;Required. It must be unique.<br /> #Enter a Description&amp;mdash;Some text to describe this filter.<br /> #Authors&amp;mdash;Required. Enter an author to exclude from the feed; then click Add, Repeat to add another author. <br /> #Click Save.<br /> <br /> '''To edit an Author filter,''' click the filter's name. <br /> <br /> '''To add a Script filter:'''<br /> #Click Add. <br /> #Select Type&amp;mdash;Script from the drop-down&amp;mdash;Required. <br /> #Enter a Name&amp;mdash;Required. It must be unique.<br /> #Enter a Description&amp;mdash;Some text to describe this filter.<br /> #Click the Browse/Choose File button&amp;mdash;Required. Button name varies by browser. Navigate to the groovy file on your local machine or network. Select it.<br /> #Click Save.<br /> <br /> '''To edit a Script filter,''' click the filter's name.<br /> <br /> Click the Show Source button to open the groovy script file in a separate window where you can review and select/copy (but cannot edit) the source. You can also upload a new script file in Edit mode. If you do this, you can retain or change the Name and Description, as needed.<br /> <br /> == Deleting Filters ==<br /> <br /> Select the check box to the left of one or more Filter Names and click Delete to delete the filter. A confirmation dialog box appears. Click OK to confirm deletion of the selected filter(s).<br /> <br /> = System Administration =<br /> <br /> '''&lt;font color=&quot;#ff0000&quot;&gt;Only the SocialMiner Administrator, who is the Application User created during install time, can use this gadget on the Administration Tab.&lt;/font&gt;''' <br /> <br /> [[Image:SocialMinerSystemAdministration853.png|thumb|right|300px|System Administration Gadget]] The System Administration gadget on the Administration tab provides the following system configuration and serviceability tools: <br /> <br /> *[[#System_Status_and_Statistics|System Status and Statistics]] <br /> *[[#Active_Directory|Active Directory]] <br /> *[[#Mail_Server|Mail Server]] <br /> *[[#Proxy_Settings|Proxy Settings]] <br /> *[[#XMPP_Server|XMPP Server]] <br /> *[[#Purge_Settings|Purge Settings]] <br /> *[[#Reporting_Configuration|Reporting Configuration]] <br /> *[[#RTMT_Download_Links|RTMT Download Links]] <br /> *[[#Platform_Administration|Platform Administration]] <br /> *[[#System Logs|System Logs]]<br /> <br /> &lt;br&gt;<br /> <br /> == System Status and Statistics ==<br /> <br /> The top section of the gadget has three sections of system status and statistical information:<br /> <br /> *Version Information showing the Application Software Version (the version of SocialMiner) and the Operating System Active and Inactive Software Versions (the version of the Cisco Unified OS).<br /> <br /> *Server status for the main services&amp;mdash;Datastore, Indexer, Runtime, and Eventing&amp;mdash;and for the Hardware profile. You also see the status of the Mail Server and the external XMPP Server used for Instant Messaging notifications, if those servers have been configured. <br /> <br /> *Two graphical meters showing the number of incoming social contacts per hour and the number of logged-in users. These meters help you determine if the incoming rate of contacts or the number of users are nearing the limits allowed by the server. If a meter is completely red, consider asking users to log out or modifying your feeds to reduce the amount of incoming social contacts.<br /> <br /> == Active Directory ==<br /> <br /> SocialMiner uses Active Directory to manage and administrate user access to the system. All users, with the exception of the Administration and Reporting users, must be configured on a Microsoft Active Directory server to be able to access SocialMiner. <br /> <br /> The Active Directory connection permits users configured on the AD to access SocialMiner. You can configure the connection to allow all users on the AD to access SocialMiner, or to allow access to only a group of users. Multiple, independent groups that require isolated security and permissions should each deploy their own SocialMiner system. <br /> <br /> '''Note''': If Twitter Account feeds are configured on the system, all users are able to see Direct Messages to the configured Twitter Accounts and all users can post from these accounts. SocialMiner tracks which users make which posts. Companies that want to restrict who can make posts need to implement that by configuring SocialMiner to authenticate with a specific role. If SocialMiner is authenticated with a specific Active Directory role, then only those Active Directory users with that role can use SocialMiner. <br /> <br /> &lt;br&gt;To configure Active Directory, open the Administration gadget and click Edit. Enter or modify the following fields. Click Save when finished. <br /> <br /> *'''Enabled''': (checkbox) When checked, the Active Directory connection is active. If not checked, then only the administrator can log into SocialMiner. <br /> *'''Host''': Required if Enabled is checked. Provide the Host name or IP address and Port of the Active Directory server. <br /> *'''Port''': Required if Enabled is checked. Provide the port for Active Directory. The default Active Directory port is 3268. If using SSL the default port is 3269. <br /> *'''Use SSL''': (checkbox). Check to use SSL. Note you must also exchange security certificates with the AD server before SSL can work. <br /> *'''Manager Distinguished Name''': Required if Enabled is checked. Enter the Manager Distinguished Name used to login to the Active Directory server, for example, on a default installation of Microsoft AD, the name is&amp;nbsp;:''&lt;tt&gt;CN=Administrator, CN=users, DC=MYSERVER, DC=COM&lt;/tt&gt;''. Replace MYSERVER and COM with your respective hostname. <br /> *'''Manager Password''': Required if Enabled is checked. The password for the AD Manager account. <br /> *'''Role Name''': (optional) The Active Directory role or Active Directory group of users who are allowed to access SocialMiner. If this setting is blank or * then all users in Active Directory are allowed access to SocialMiner.<br /> <br /> === Exchanging Security Certificates with AD ===<br /> <br /> To enable SSL for the Active Directory connection you must first exchange security certificates between the two servers. Enabling SSL is optional, but if you do not enable SSL then username and password information is not transmitted securely between SocialMiner and the Microsoft AD server. <br /> <br /> To exchange security certificates: <br /> <br /> On the Active Directory server: <br /> <br /> #Verify that the Active Directory has the Certificate Services service installed. <br /> #Select '''All Programs &amp;gt; Administrative Tools &amp;gt; Certificate Authority'''. <br /> #Expand the domain node and select Issued Certificates. <br /> #Double click the certificate to open it. <br /> #Open the Details tab and click Copy to file. <br /> #An Export wizard appears. In the wizard select DER encoded binary. <br /> #Using the wizard to select a location to save the file. <br /> #Click Finish.<br /> <br /> On the SocialMiner Server: <br /> <br /> #Open the Cisco Unified Operating System Administration page. The link is available from the gadget. <br /> #Select Security &amp;gt; Certificate Management. <br /> #Click Upload Certificate. <br /> #For the Certificate Name, select tomcat-trust. <br /> #In the Upload File field, select the file to upload by clicking Browse... Select the certificate file you saved from the Active Directory server. <br /> #Click Upload File. <br /> #Restart the Cisco Tomcat service. Using the CLI, run the command utils service restart Cisco Tomcat<br /> <br /> === Adding Users ===<br /> <br /> The Administration user (configured at install) and Reporting user accounts are the only accounts explicitly configured on SocialMiner. The social media customer care representatives are configured in Microsoft Active Directory. As these users sign into SocialMiner, successfully authenticate against Active Directory, and begin to take actions on the system, their actions are associated with their Active Directory User ID.<br /> <br /> == Mail Server ==<br /> <br /> Mail Server settings allow you to configure the SMTP information for a Mail Server. You must configure a mail server if you intend to use the email notification feature. <br /> <br /> To configure the Mail Server, click Edit at the bottom of the Mail Server setting and edit the following: <br /> <br /> *Enabled: Check to enable the Mail Server connection <br /> *Mail Server Host: Required if Enabled is checked. The IP address or Hostname of the Mail Server. <br /> *Mail Server Port: Required if Enabled is checked. The port for the mail server. This is set for port 25 by default. The mail server may open port 465 instead for SSL/TLS connections. For example, the Gmail SMTP server (smtp.gmail.com) uses port 465. <br /> *From Email Address: Required if Enabled is checked. The email address from which emails are sent. <br /> *Use Authentication: Check to user SMTP authentication to connect to this mail server. The following two fields are editable only when Use Authentication is checked. <br /> *User Name: Required if Use Authentication is checked. The user name for signing in. <br /> *Password: Required if Use Authentication is checked. The password for the User Name. <br /> *Use SSL|TLS&amp;nbsp;: Defaults to unchecked. Check this if a secure connection is preferred and is supported by the mail server. The mail server certificate is not validated for this release. You must check this if you are using the Gmail SMTP server (smtp.gmail.com).<br /> <br /> Click '''Save''' to save your changes.<br /> <br /> == Proxy Settings ==<br /> <br /> [[Image:SocialMinerFeedsProxySettings.png|thumb|right|300px]] <br /> <br /> Consult your Network Administrator for the proxy name and port. The same proxy is used across all feeds. <br /> <br /> The link for proxy settings is available in the Administration gadget. <br /> <br /> To configure the proxy, click the Proxy Configuration link, and edit the following field. Click '''Save''' when finished. <br /> <br /> *'''Enable Proxy''' (checkbox)&amp;mdash;When checked, feeds are accessed through the provided proxy server. <br /> *'''Hostname'''&amp;mdash;Required when Enable Proxy is checked. The IP address or hostname of the proxy server. <br /> *'''Port'''&amp;mdash;Required when Enable Proxy is checked. The port for the proxy server. <br /> *'''Exclusion Patterns'''&amp;mdash;You can add and remove hostname or IP addresses for servers not requiring a proxy. <br /> **To add an exclusion, type the exclusion into the text box and click Add. <br /> **To remove an exclusion, click the red X to the right of the exclusion. <br /> **Wildcards are supported, for example *.cisco.com excludes all servers with a cisco.com hostname and 10.86.* excludes all IP addresses starting with 10.86<br /> <br /> Click Save to save the settings and return to the Feed gadget page.<br /> <br /> '''Notes''': <br /> <br /> *Proxy changes may take up to 30 seconds to take effect. <br /> *The exclusion list is limited to 255 total characters. There is an additional character per item in the list that acts as a separator. <br /> *SocialMiner should only need to access a proxy server if it sits behind a corporate network firewall and has to use a http/https proxy server for accessing an outside network. You should not need to give SocialMiner a private NAT address, and doing so is not currently supported.<br /> <br /> == XMPP Server ==<br /> <br /> XMPP Server settings allow you to configure an XMPP Server so SocialMiner can utilize Instant Messaging (IM) notifications. You must configure an XMPP server if you intend to use the IM notification feature. <br /> <br /> To configure the XMPP Server, click Edit at the bottom of the XMPP Server setting and edit the following: <br /> <br /> *Enabled: Check to enable the XMPP Server connection <br /> *XMPP Service Lookup: Check to enable XMPP Service Lookup. When enabled, the User Name's domain is used to connect to the correct XMPP Server. <br /> *XMPP Server Host: The IP address or Hostname of the XMPP Server. Not applicable is XMPP Service Lookup is checked. <br /> *XMPP Server Port: The port for the mail server. This is set for port 5222 by default. Not applicable if XMPP Service Lookup is checked. <br /> *User Name: The user name is used to sign in to the XMPP Server. <br /> *Password: The password for the above User Name. NOTE: If you change your XMPP password for any reason&amp;mdash;intentionally or to comply with network policy&amp;mdash;change it here.<br /> <br /> Click '''Save''' to save your changes.<br /> <br /> == Purge Settings ==<br /> <br /> Database purges are required to remove old data from the datastore so that the disk does not fill up. Datastore purges occur on a continuous basis (every hour) based on the age of the social contacts and disk usage. <br /> <br /> '''Important'''! Purge settings take effect as soon as you click '''Save'''. If any of the criteria are met, such as Emergency purge when disk usage exceeds (%), the purge starts immediately. <br /> <br /> To configure purge settings, click Edit at the bottom of the purge settings tool and edit the following: <br /> <br /> '''DataStore Purge Settings:''' <br /> <br /> *Purge Social Contacts older than (days): Social contacts older than this number of days are purged. Valid values are 1 - 30. <br /> *:'''Important!:''' SocialMiner will not retrieve social contacts older than this setting.<br /> *Emergency purge when disk usage exceeds (%): Begin an emergency purge if disk usage exceeds this value. Valid values are 60 - 90. When an emergency purge executes, social contacts older than the days specified above are removed. If disk usage is still above the setting for this field, the purge continues removing social contacts (one day at a time) until the disk usage is below the threshold for emergency purge.<br /> <br /> '''Reporting Purge Settings:''' <br /> <br /> *Purge start time (HH:mm 24 hour format): The time, in 24 hour format (00:00 to 23:59), that the purge starts based on the local server time. By default this is set to 01:00 (1am) local server time. <br /> *Purge Social Contacts older than (days): Reporting records for social contacts older than this number of days are purged when the reporting purge starts.<br /> <br /> Click '''Save''' to save your changes.<br /> <br /> == Reporting Configuration ==<br /> <br /> Reporting configuration allows you to set or change the Informix password for the reporting user. You cannot change the reporting user's username. It is set to ''reportinguser''. <br /> <br /> The reporting user is used by Cisco Unified Intelligence Center (CUIC) and third-party applications to access the reporting database. Details on the tables in the reporting database are available in the SocialMiner Developers Guide. <br /> <br /> To set or change the password for the reporting user, enter a new password in each of the password fields and click Save. <br /> <br /> This section also displays the Reporting Server and Database information. This information is required for third-party connection to the database. The details include: <br /> <br /> *Reporting Host&amp;mdash;The hostname to use when connecting to the reporting database. <br /> *Reporting Port&amp;mdash;The port for the reporting database server. <br /> *Reporting Server&amp;mdash;The Informix server name for the reporting database. When configuring Cisco Unified Intelligence Center, this is the ''Instance''. <br /> *Reporting Database&amp;mdash;The Informix database name for reporting. <br /> *Database Type &amp;mdash;The type of database (Informix). <br /> *Username&amp;mdash;The reporting username is fixed at 'reportinguser' and cannot be changed. <br /> *Password/Re-enter New Password&amp;mdash;The password for the reporting user.<br /> <br /> When configuring Cisco Unified Intelligence Center, you must select UTF-8 as the character set.<br /> <br /> == RTMT Download Links ==<br /> <br /> Links are provided to download the Cisco Unified Real Time Monitoring Tool (RTMT). SocialMiner uses the same RTMT as the one used for Cisco Unified Communications Manager. <br /> <br /> Details on Installing and Configuring RTMT can be found on the Cisco web site: [http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/8_0_1/rtmt/rtinst.html Installing and Configuring Cisco Unified RTMT] <br /> <br /> == Platform Administration ==<br /> <br /> Platform Administration provides links to the following interfaces of Cisco Unified OS: <br /> <br /> *''Cisco Unified Operating System Administration''&amp;mdash;Use tools on this interface to upgrade software and to import certificates. <br /> *''Cisco Unified Serviceability'' <br /> *''Disaster Recovery System''&amp;mdash;Use tools on this interface to back up and restore.<br /> <br /> SocialMiner uses the same platform administration tools as Cisco Unified Communications Manager. Detailed online help is available in the tools.<br /> <br /> == System Logs ==<br /> <br /> The System Logs tool provides links to access the '''Log Directory''' of SocialMiner or to perform a '''System Health Snapshot'''. <br /> <br /> '''Important!''' Do not click the System Health Snapshot link unless directed to by Cisco TAC. Accessing this link forces the system to stream all system parameters into a large XML file for download. System performance is impacted while the snapshot is occurring.<br /> <br /> = Notifications =<br /> <br /> '''&lt;font color=&quot;#ff0000&quot;&gt;Only the SocialMiner Administrator, who is the Application User created during install time, can use this gadget on the Administration Tab.&lt;/font&gt;''' <br /> <br /> '''VIDEO:''' View a [http://www.youtube.com/watch?v=gqhkQlHW4Cs&amp;hd=11 video] about configuring Instant Message Notifications. View a [http://www.youtube.com/watch?v=I_GbeTwt7zo&amp;hd=1 video] about configuring Email Notifications. Although this video was created for an earlier version of SocialMiner and shows an older user interface, it presents accurate information.<br /> <br /> The Notification gadget on the Administration Tab lets you view, delete, edit, and add notification rules. Set up notification rules to send messages in reference to tagged social contacts.<br /> <br /> If a reply template is associated with the social contact for which the notification is sent, the person who clicks the link in the IM or email opens SocialMiner to that reply template.<br /> <br /> You can also send notifications to a mobile phone using an SMS Gateway service. Here is a list of [http://en.wikipedia.org/wiki/List_of_SMS_gateways SMS Gateways by carrier.] <br /> <br /> '''Notes:''' <br /> <br /> Establishing a notification rule for email requires that the administrator has [[#Mail_Server|configured a Mail Server]] in the System Administration gadget.<br /> <br /> Establishing a notification rule for IM requires that the administrator has [[#Xmpp_Server|configured an XMPP Server]] in the System Administration gadget.<br /> <br /> Notifications are triggered by tags. For email and IM, you have set up tags for social contacts. See [[#Tagging_Social_Contacts|Tagging Social Contacts on the Home tab]] and [[#Automatic_Tags_for_Feeds|Automatic Tags]]. <br /> <br /> IM and Email Notifications do not accept replies. The intent is to notify, not to open a dialog.<br /> <br /> Auto-tagging or adding multiple tags at the same time (in one operation) generates multiple notifications to the same recipients list. <br /> <br /> <br /> Using the Notification Gadget you can: <br /> <br /> *delete a notification, by checking the box next to the notification name and clicking Delete. <br /> *edit a notification, by clicking the notification's name. <br /> *add a notification, by clicking Add.<br /> <br /> To configure a notification, provide or edit the following fields in the Notification gadget. <br /> <br /> #Type&amp;mdash;Required. The type of notification. Notifications can be: <br /> ##Email&amp;mdash;Notification is sent over email - A Mail Server must be configured in the System Administration gadget to send Email notifications. <br /> ##IM&amp;mdash;Notification is sent over IM - An XMPP server must be configured in the System Administration gadget to send IM notifications. <br /> ##HTTP&amp;mdash;Reserved for developer applications that deliver social contact data to an external application.<br /> #Name&amp;mdash;Required. The name of the notification. <br /> #Description&amp;mdash;A brief description of the notification. <br /> #Campaign&amp;mdash;Required. Select a campaign to which you are associating this notification. <br /> #Tag&amp;mdash;Required. Enter a tag for this notification and click '''Add'''. Repeat for each tag. Notifications are sent when a social contact is tagged with this tag and exists in the Campaign above. To remove a tag, click the x at the right of the field.<br /> #Addresses&amp;mdash;Enter an address and click '''Add''' to add an address to this notification. Repeat for multiple addresses. Addresses must be in the format &lt;tt&gt;user@domain.com&lt;/tt&gt;. Used only for Email and IM Notifications, for which it is Required. To remove an address, click the x at the right of the field.<br /> #Subject&amp;mdash;The email subject for this notification. This field is only available for Email notifications. Subject is optional and is blank by default. As a best practice, enter a subject for email notifications.<br /> #Body&amp;mdash;The body for this notification. HTML tags are supported for Email Notifications. IM notifications are sent using plain text. The body of the message supports variables so you can customize the information sent in the notification. See &quot;Notification Body Variables&quot; below.<br /> <br /> &lt;br&gt;<br /> <br /> == Notification Body Variables ==<br /> <br /> The notification body for emails and instant messages can contain keywords in the syntax ${KEYWORD}. These keywords will be replaced with values from the Social Contact. Keywords are listed here in uppercase, but they are case-insensitive. <br /> <br /> Note: By default, the body of the message contains the URL of the social contact—the '''${SC_SCREEN_URL}'''. You can add the following variables to the body of the notification to include the value of the variable in the notification. For Email Notifications, you can also use HTML tags to stylize the notification. IM notifications are sent using plain text. <br /> <br /> *${SC_AUTHOR}—the Social Contact Author (not available in all feeds) <br /> *${SC_CREATED_DATE}—Date the Social Contact was created in the system. <br /> *${SC_DESCRIPTION}—The description of the social contact. Typically this is the tweet, RSS post, facebook fan page post, etc. <br /> *${SC_PUBLISHED_DATE}—The publish date of the social contact (not available in all feeds) <br /> *${SC_SCREEN_URL}—The URL to the social contact in the results gadget. Clicking this URL allows you to instantly reserve/reply to the social contact. <br /> *${SC_SOURCE_TYPE}—The feed type of the social contact, for example; RSS, Twitter Stream, Twitter Account, FaceBook <br /> *${SC_TAGS}—The tags for this social contact. <br /> *${SC_TITLE}—The title of the social contact. <br /> *${SC_EXTENSION_FIELDS.&amp;lt;fieldname&amp;gt;}—This variable adds a specific, named extension field for the social contact. You can add a maximum of 100 extension fields, up to one megabyte of information. <br /> *${SC_EXTENSION_FIELDS}—This variable adds all extension fields that exist for the social contact. They appear in the body in alphabetical order by name, in the format ''Name: Value''. If no value was defined, you see ''Name: (&amp;mdash;)''. If there are no extension fields, the variable is removed from the message body. <br /> <br /> If the body an email notification includes: <br /> <br /> :The author of this Social Contact is: &amp;lt;strong&amp;gt;${SC_AUTHOR}&amp;lt;/strong&amp;gt; &amp;lt;br /&amp;gt; <br /> :The message contents are as follows: &amp;lt;strong&amp;gt;${SC_DESCRIPTION}&amp;lt;/strong&amp;gt; &amp;lt;br /&amp;gt; <br /> :You can Reserve/Reply to the Social Contact &amp;lt;a href=&quot;${SC_SCREEN_URL}&quot;&amp;gt;here&amp;lt;/a&amp;gt;.<br /> <br /> The actual email notification sent would appear as: <br /> <br /> The author of this Social Contact is: Joe Somebody<br /> The message contents are as follows: This is a TWEET!<br /> You can Reserve/Reply to the Social Contact here.<br /> <br /> = Reply Templates =<br /> <br /> '''&lt;font color=&quot;#ff0000&quot;&gt;Only the SocialMiner Administrator, who is the Application User created during install time, can use this gadget on the Administration Tab.&lt;/font&gt;''' <br /> <br /> The SocialMiner Reply Templates gadget on the Administration Tab lists all available Reply Templates. The gadget displays the two installed system-provided templates and allows you to configure custom reply templates to be used with the system. <br /> <br /> '''System Templates''': <br /> The two system-defined templates cannot be edited or deleted. They are: <br /> <br /> *Cisco Twitter Reply Template&amp;mdash;Used for [[#Twitter Account Feed Type|Twitter Account]] and [[#Twitter Stream Feed Type|Twitter Stream]] feeds only, for which it is the default option. This template opens when you reply to a tweet on the Home tab.<br /> <br /> *Cisco Facebook Reply Template&amp;mdash;Used for [[#Facebook_Fan_Page_Feed_Type|Facebook Fan Page feeds]] only, for which it is the default option. This template opens when you reply to a Facebook Fan Page on the Home tab. <br /> <br /> '''Custom Templates''': <br /> An administrator can develop custom reply templates and use them for RSS, Twitter, or Facebook feeds. Until you create a custom template, ''No reply template'' is the only reply template option for a Push or RSS feed.<br /> <br /> '''To add a custom template:'''<br /> #Click Add.<br /> #Enter a name (Required).<br /> #Enter the URL for the location of the custom template code (Required).<br /> <br /> An example of code for a reply template is provided on the system at <br /> &lt;pre&gt;http://&amp;lt;servername&amp;gt;/templates/reply/twitter_reply_sample.jsp&lt;/pre&gt;<br /> The source code is commented and provides details on the SocialMiner javascript functions required. <br /> <br /> See also [http://docwiki.cisco.com/wiki/SocialMiner_Labs#Lab_8_Using_Reply_Templates the Custom Reply training lab]. <br /> <br /> '''To delete a custom template:'''<br /> #Select it.<br /> #Click Delete.<br /> #Confirm the deletion.<br /> <br /> Reply templates must conform to the OpenSocial gadget standard. Some tips for converting existing HTML pages into OpenSocial gadgets can be found [http://code.google.com/apis/gadgets/docs/fundamentals.html#Existing here.] <br /> <br /> After you have created your Reply Template, host it on a webserver that is accessible by SocialMiner, and use the Reply Template gadget to provide a name for the Reply Template and its location.<br /> <br /> = SocialMiner Reporting =<br /> <br /> SocialMiner maintains metrics on social contact volume and agent activities. These metrics are stored in a [http://en.wikipedia.org/wiki/SQL SQL] database for up to 18 months. The reporting database can be accessed using any SQL reporting tool including Cisco Unified Intelligence Center. Access to this database requires configuration of a reporting user in the SocialMiner system administration. <br /> <br /> There are two main categories of reports: <br /> <br /> *Campaign Reports - These metrics provide an indication of the total posting volume by customers as well as the responsiveness to customers. These are what could be described as &quot;customer facing&quot; metrics. <br /> *Agent Reports - These metrics provide an indication of the agent productivity. These metrics could be used to evaluate agent speed or they could be used to measure total workload as a basis for staffing forecasts.<br /> <br /> The Cisco Unified Intelligence Center templates for SocialMiner are available for download here: http://www.cisco.com/cisco/software/release.html?mdfid=283613136&amp;amp;catid=278875240&amp;amp;softwareid=283733464 <br /> <br /> '''Note''': For Cisco Unified Intelligence Center releases prior to 8.0(3), you must extract the templates from the zip file before importing them into Unified Intelligence Center. For release 8.0(3) and later, you can import the zip file directly and Unified Intelligence Center extracts all the templates it finds inside the zip file. <br /> <br /> The following screen captures are examples of the Cisco Unified Intelligence Center Reports daily reports: <br /> <br /> [[Image:SocialMiner Campaign Daily Report.jpg|center|800px|SocialMiner Campaign Daily Report]] <br /> <br /> *ASR - Average Speed of Reserved. For the social contacts that were Reserved, this is the average time between capture by SocialMiner and the time they are marked as reserved. This provides an indication of how much time passes before someone first views the customer's post. <br /> *ASA - Average Speed of Answer. For the social contacts that were Handled, this is the average time between capture by SocialMiner and the time they are marked handled. This provides an indication of how of how much time passes before the customer gets a response. <br /> *ASD - Average Speed of Discard. For the social contacts that were Discarded, this is the average time between capture by SocialMiner and the they are marked discarded. This provides an indication of how much time passes before someone chooses to discard the customer's post. Note: &quot;Discard&quot; doesn't necessarily mean the post is disregarded. The distinction between &quot;Discard&quot; and &quot;Handled&quot; depends on how the agents are using SocialMiner. For example, they might mark posts that are read as &quot;discarded&quot; and posts that are responded too as &quot;handled&quot;. In this case, discarded means that they were &quot;read&quot;.<br /> <br /> &lt;br&gt;[[Image:SocialMiner Agent Daily Report.jpg|center|800px|SocialMiner Agent Daily Report]] <br /> <br /> &lt;br&gt;The complete SocialMiner reporting database schema is documented in the [http://developer.cisco.com/web/socialminer SocialMiner Developer Guide] <br /> <br /> &lt;br&gt;<br /> <br /> *AHT - Average Handle Time. For social contacts that were handled by this agent, this is the average time between Reserved and Handled. This provides and indication of how much time it takes this agent to respond to a social contact. <br /> *ADT - Average Discarded Time. For social contacts that were discarded by this agent, this is the average time between Reserved and Discarded. This provides an indication of how much time it takes this agent to discard a social contact. <br /> *ACT - Average Completed Time. For social contacts that were Handled or Discarded, this is the average time between capture by SocialMiner and the first time they were marked Handled or Discarded. This provides an indication of how of how much time it takes for this agent to complete work for a social contact.<br /> <br /> == Configuring the SQL Connection to the SocialMiner Reporting Database ==<br /> <br /> Connection to the SocialMiner Informix reporting database can be made through JDBC using the following format: <br /> <br /> &lt;tt&gt;jdbc:informix-sqli://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;/&amp;lt;databasename&amp;gt;:INFORMIXSERVER=&amp;lt;informixserver&amp;gt;;user=&amp;lt;informixuser&amp;gt;;password=&amp;lt;informixpassword&amp;gt;;&lt;/tt&gt; <br /> <br /> *The reporting database &amp;lt;port&amp;gt; is 1526. <br /> *The &amp;lt;databasename&amp;gt; is &quot;mmca_data&quot;. <br /> *The &amp;lt;informixserver&amp;gt; name is based on the hostname of the server with &lt;tt&gt;_mmca&lt;/tt&gt; append to the end of the hostname. Additional, any dashes (&quot;-&quot;) in the hostname are replace by underscores (&quot;_&quot;). <br /> *The UTF-8 Charset is required to get Cisco Unified Intelligence Center (CUIC) able to connect. <br /> *The content of INFORMIXSERVER is the instance name. Must be lowercase. <br /> *The databasehost can be socialminer with all lowercase and the instances should also be with lowercase.<br /> <br /> For example, if your server's hostname is my-server.mycompany.com, then the INFORMIXSERVER name is &lt;tt&gt;my_server_mmca&lt;/tt&gt;. The complete JDBC URL would be: <br /> <br /> &lt;tt&gt;jdbc:informix-sqli://my-server.mycompany.com:1526/mmca_data:INFORMIXSERVER=my_server_mmca;user=reportinguser;password=&amp;lt;informixpassword&amp;gt;;&lt;/tt&gt; <br /> <br /> Note that when authenticating, the informix username is always &lt;tt&gt;reportinguser&lt;/tt&gt; and the informix password is the password you created in the Administration Gadget. <br /> <br /> = Downloading and Installing Language Packs =<br /> <br /> Do this only if you require the SocialMiner interface in a language other than English. <br /> <br /> A downloadable zip file of internationalized SocialMiner user interface and online help files will be available on [http://www.cisco.com cisco.com] shortly after the English-language version of SocialMiner 8.5(4) is released. <br /> <br /> The filename is SocialMiner-languagePack-8.5.4.zip. <br /> <br /> Downloading and unzipping the file gives you 18 language packs with the file extension of ''##.cop.sgn''. The zip file also contains a Readme.txt with instructions on installing COP files.<br /> <br /> Note that the Cisco authorization process for File Download has changed. You may need to access [http://eman-core.cisco.com/SERVICE/OnRamp/index.pcgi OnRamp] to request Software Download Access. (New Account Request -&gt; Request For Myself -&gt; Customer Advocacy -&gt; Software Download and Special File Publishing Access -&gt; Software Download Access)<br /> <br /> '''IMPORTANT''': Do not change the name of the files. <br /> <br /> {| border=&quot;1&quot; cellspacing=&quot;1&quot; cellpadding=&quot;1&quot; width=&quot;400&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Language <br /> ! scope=&quot;col&quot; | LanguagePack<br /> |-<br /> | Chinese (Simplified) <br /> | ccp-language-zh_CN-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Chinese (Traditional) <br /> | ccp-language-zh_TW-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Danish <br /> | ccp-language-da_DK-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Dutch <br /> | ccp-language-nl_NL-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Finnish (France) <br /> | ccp-language-fi_FI-8.5.3.1000-1.cop.sgn<br /> |-<br /> | French (France) <br /> | ccp-language-fr_FR-8.5.3.1000-1.cop.sgn<br /> |-<br /> | French (Canadian) <br /> | ccp-language-frCAFR-8.5.3.1000-1.cop.sgn<br /> |-<br /> | German <br /> | ccp-language-de_DE-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Italian <br /> | ccp-language-it_IT-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Japanese <br /> | ccp-language-ja_JP-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Korean <br /> | ccp-language-ko_KR-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Norwegian <br /> | ccp-language-nb_NO-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Polish <br /> | ccp-language-pl_PL-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Portuguese (Brazil) <br /> | ccp-language-pt_BR-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Russian <br /> | ccp-language-ru_RU-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Spanish <br /> | ccp-language-es_ES-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Swedish <br /> | ccp-language-sv_SE-8.5.3.1000-1.cop.sgn<br /> |-<br /> | Turkish <br /> | ccp-language-tr_TR-8.5.3.1000-1.cop.sgn<br /> |}<br /> <br /> = System Backup and Restoration =<br /> <br /> Cisco SocialMiner supports the Cisco Unified OS ''Disaster Recovery System'' (DRS) to perform backup and restoration of the system. You access the Disaster Recovery System by going to the Administration Gadget, expanding the section on '''Platform Administration''', then selecting the link for '''Disaster Recovery System'''. <br /> <br /> SocialMiner uses the same platform administration tools as Cisco Unified Communications Manager. Detailed online help is available in the tools. <br /> <br /> You can manually back up your system using DRS, or schedule DRS to perform automatic backups. <br /> <br /> Complete details on using DRS are available in the DRS online help and in this guide: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/drs/8_0_1/drsag801.html. <br /> <br /> == Quick Manual Backup Instructions ==<br /> <br /> These instructions provide quick instructions to create a manual backup. You can also schedule backups to run automatically. Note that the system is not usable during a backup, and that new social contacts are not collected during a backup. Schedule your backups accordingly. <br /> <br /> The online help for the Disaster Recovery System provides complete details on all features of DRS. However, using DRS with SocialMiner is greatly simplified because SocialMiner supports only a single node and only uses network backups. <br /> <br /> To perform a manual backup: <br /> <br /> === Define Backup Device ===<br /> <br /> #Access the Disaster Recovery System by going to the Administration Gadget, expanding the section on '''Platform Administration''', then selecting the link for '''Cisco Disaster Recovery System'''. <br /> #Select '''Backup''' &amp;gt; '''Backup Device'''. <br /> #On the ''Backup Device List'' page, select '''Add New'''. <br /> #Provide a '''Device Name''' for the backup device. <br /> #SocialMiner only supports backing up to a Network Directory, provide the Network Directory details for a server that supports SFTP. <br /> #Provide the ''Number of backups to store on the Network Directory''. The default is two, so only the two latest backups are preserved. <br /> #Click '''Save''', the system verifies the information you entered and saves the backup device.<br /> <br /> The backup device is now saved. You do not need to repeat these steps the next time you backup the system unless you want to back up to a different device or change backup device settings. <br /> <br /> === Backup the System to the Backup Device ===<br /> <br /> #Access the Disaster Recovery System by going to the Administration Gadget, expanding the section on '''Platform Administration''', then selecting the link for '''Disaster Recovery System'''. Log in using the platform credentials you supplied when you installed SocialMiner. <br /> #Select '''Backup''' &amp;gt; '''Manual Backup'''. <br /> #Select the Backup Device you created earlier from the pull down menu in '''Select Backup Device'''. <br /> #In '''Selected Features''' check '''SOCIALMINER'''. <br /> #Click '''Start Backup'''. <br /> #A warning appears noting that you may need to use the security password to restore. Click '''OK'''. The backup begins. <br /> #The backup page refreshes periodically providing the status of the backup. The page also displays the name of the backup tar file that is being saved to the remote system. <br /> #After the backup completes, wait a few minutes before using SocialMiner so the SocialMiner system can start subsystems that may have been shutdown during the backup.<br /> <br /> === Restoring from a Backup File ===<br /> <br /> #Access the Disaster Recovery System by going to the Administration Gadget, expanding the section on '''Platform Administration''', then selecting the link for '''Disaster Recovery System'''. Log in using the platform credentials you supplied when you installed SocialMiner. <br /> #Select '''Restore''' &amp;gt; '''Restore Wizard'''. <br /> #Select the backup device from the drop-down menu and select '''Next'''. <br /> #Select the backup file you want to restore for the ''Tar file list'' drop-down menu and select '''Next'''. <br /> #Check '''SocialMiner''' in the ''Select Features'' section and select '''Next'''. <br /> #Read the warning on the page. Optionally select '''File Integrity Check''', then select the Server to be restored (typically the host name of the backed up system). Click '''Restore'''. <br /> #The restore page refreshes periodically providing the status of the restore. <br /> #After the restore completes, you must restart SocialMiner for the restoration to take effect.<br /> <br /> = Design Guidance =<br /> <br /> Topics: <br /> <br /> *[[#Advanced_UI_Options|Advanced UI Options]] <br /> *[[#Command_Line_Interface|Command Line Interface]] <br /> *[[#Deployment_Models|Deployment Models]] <br /> *[[#Hardware_and_Software_Specifications|Hardware and Software Specifications]] <br /> *[[#Obtaining a CA-Signed Certificate|Obtaining a CA-Signed Certificate]]<br /> *[[#Ports|Ports]] <br /> *[[#Sizing|Sizing]] <br /> *[[#SocialMiner_User_Accounts_and_Security|SocialMiner User Accounts and Security]]<br /> *[[#Twitter_Accounts_and_Security|Twitter Accounts and Security]] <br /> *[[#VMWare_Open_Virtual_Format_.28OVF.29|VMWare Open Virtual Format (OVF)]]<br /> <br /> &lt;br&gt;<br /> <br /> == Advanced UI Options ==<br /> <br /> The SocialMiner user interfaces are designed to be embedded in other web application user interfaces. <br /> <br /> '''&lt;font color=&quot;#006699&quot;&gt;Quad&lt;/font&gt;''' <br /> <br /> You can add a SocialMiner gadget to Quad using the &quot;Add Application&quot; button on Quad. You can find the specific URL of the SocialMiner gadget by using &quot;view source&quot; on your browser while looking at the gadgets on SocialMiner. <br /> <br /> '''&lt;font color=&quot;#006699&quot;&gt;iGoogle&lt;/font&gt;''' If the SocialMiner system is deployed in the Internet deployment model, you can add a SocialMiner gadget to iGoogle using the &quot;Add Stuff&quot; button on iGoogle. <br /> <br /> You can find the specific URL of the SocialMiner gadget by using &quot;view source&quot; on your browser while looking at the gadgets on SocialMiner. <br /> <br /> '''&lt;font color=&quot;#006699&quot;&gt;iFrames&lt;/font&gt;''' <br /> <br /> If your web site or application doesn't support OpenSocial, then you can add SocialMiner to a web page by using an iFrame. With this technique you can make a frame sized to show one of the SocialMiner web pages (most likely the campaign results gadget). <br /> <br /> == Command Line Interface ==<br /> <br /> To access the Command Line Interface for SocialMiner: <br /> <br /> *SSH to the address for your SocialMiner server. <br /> *Sign in with your administrator credentials. <br /> *Type a&amp;nbsp;? at the admin: prompt to see the list of commands.<br /> <br /> Refer to the [http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/8_0_1/cli_ref_801.html Cisco Systems CLI documentation]. <br /> <br /> Note that most CLI commands do not apply to, or have not been certified for, SocialMiner. <br /> <br /> == Deployment Models ==<br /> <br /> Version 8.5 of SocialMiner has a single-server all-in-one deployment model. You cannot use a load-balancing split data-center deployment. There is no replication. The solution is not redundant. The best availability solution for SocialMiner would be to back it up at a 2nd location using a scheduled backup. In the event of a site loss, you would restore into a new VM. <br /> <br /> The server may be deployed inside or outside the corporate firewall in &quot;intranet&quot; and &quot;Internet&quot; deployment models. <br /> <br /> *The intranet deployment model provides the additional security of the corporate network firewalls to reduce risk of an external party accessing the system. This deployment model is required if SocialMiner must access internal sites, for example an internal forum site. The downside of the intranet deployment model is that SocialMiner system cannot be accessed by partners lacking VPN access. It is common for some PR functions to be externally managed by an agency and therefore offering easy access (no VPN) to the SocialMiner system may be very useful. Also, the intranet deployment model does not allow rendering of SocialMiner OpenSocial Gadgets in a public Internet containers such as iGoogle. The intranet deployment model may complicate proxy configuration, however it likely simplifies directory integration. <br /> <br /> *The Internet deployment model puts SocialMiner outside the corporate firewall. This deployment model relies on the built-in security capabilities of the SocialMiner appliance. This may be acceptable from a security perspective depending on the system use and corporate policies. For example, in some applications the SocialMiner system handles 100% public postings and therefore there is no disclosure risk associated with a compromised SocialMiner system. The Internet deployment model may complicate directory integration.<br /> <br /> == Hardware and Software Specifications ==<br /> <br /> Cisco will support SocialMiner deployment on any hardware provided SocialMiner is installed within the Cisco provided VMWare OVF. <br /> <br /> Possible server options include Cisco UCS servers such as: <br /> <br /> {| border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;<br /> |-<br /> ! UCS Model <br /> ! SKU<br /> |-<br /> | C210-M2 <br /> | UCS-C210M2-VCD2<br /> |-<br /> | B200-M2 <br /> | UCS-B200M2-VCS1<br /> |}<br /> <br /> == Ports ==<br /> <br /> '''Port 25''' is the default port for Email. <br /> <br /> '''Port 465''' is used by the mail server for SSL/TLS connections. <br /> <br /> '''Port 443''' is used for a secure connection between the SocialMiner user interface and your browser. <br /> <br /> '''Port 80''' is used by SocialMiner for unsecure communication with Twitter and Facebook APIs. <br /> <br /> '''Port 7071''' is used for unsecure BOSH connections to the XMPP/Eventing server. <br /> <br /> '''Port 7443''' is used for secure BOSH connections to the XMPP/Eventing server. <br /> <br /> Your firewall configuration may need to be modified to open these ports for SocialMiner.<br /> <br /> == Obtaining a CA-Signed Certificate ==<br /> <br /> To eliminate browser security warnings each time you sign-in you must obtain an application and root certificate signed by a Certificate Authority (CA). <br /> <br /> To do this, use the Certificate Management utility from Cisco Unified Operating System Administration. <br /> <br /> Open Cisco Unified Operating System Administration from the Administration tab &amp;gt; Platform Administration. You can also use the URL <br /> &lt;pre&gt;http://&amp;lt;servername&amp;gt;/cmplatform&lt;/pre&gt;<br /> where ''servername'' is the Name or IP address of the server. Sign in with your Administrator credentials. <br /> <br /> &lt;br&gt;'''To obtain the certificates:''' <br /> <br /> #Select Security &amp;gt; Certificate Management &amp;gt; Generate CSR. <br /> #After the successful generation, click Download CSR. <br /> #Use the CSR to obtain both the signed application certificate and the CA root certificate from the CA.<br /> <br /> '''To upload the certificates:''' <br /> <br /> #When you receive the certificates, again open Cisco Unified Operating System Administration from the Administration tab &amp;gt; Platform Administration. <br /> #Select Security &amp;gt; Certificate Management &amp;gt; Upload Certificate. <br /> #Select the certificate name from the Certificate Name list. <br /> #Upload the root certificate. <br /> ##In the Upload dialog box, select TomCat Trust from the dropdown. <br /> ##Browse to the file and click Open. <br /> ##Click Upload File.<br /> #Upload the application certificate. <br /> ##In the Upload dialog box, select TomCat from the dropdown. <br /> ##Enter the name of the CA root in the Root Certificate text box. <br /> ##Browse to the file and click Open. <br /> ##Click Upload File.<br /> <br /> You can find detailed explanations in the Security topics of Cisco Unified CM Operating System Administration Online Help. <br /> <br /> &lt;br&gt;'''After you upload the certificates:''' <br /> <br /> #Sign out of SocialMiner. <br /> #Restart the XMPP Service. (SSH to SocialMiner and use this [[#Command Line Interface|CLI:]] ''admin:utils service restart SocialMiner XMPP Server''). <br /> #Restart Tomcat. (SSH to SocialMiner and use this CLI: ''admin:utils service restart Cisco Tomcat).'' <br /> #Sign in to SocialMiner.<br /> <br /> == Sizing ==<br /> <br /> The following table details the sizing limits for a single SocialMiner system. <br /> <br /> {| border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;<br /> |-<br /> | Concurrent Admin Users Signed In <br /> | 5<br /> |-<br /> | Concurrent Agents Signed In <br /> | 30<br /> |-<br /> | Total Feeds <br /> | 100<br /> |-<br /> | Total Campaigns <br /> | 50<br /> |-<br /> | Incoming Rate of Social Contacts (total per hour) <br /> | 10,000<br /> |-<br /> | Replies per Twitter Account per Hour <br /> | 30&lt;br&gt;'''Note:''' This limit is for a default polling interval of 5 minutes. If the polling interval is set lower than 5 minutes, then the limit is reduced depending on usage patterns.<br /> |}<br /> <br /> == SocialMiner User Accounts and Security ==<br /> <br /> SocialMiner is designed to minimize the storage of username/passwords to reduce the security risk of a compromised system. There is an administration account for the system setup, but all SocialMiner user access is controlled through Active Directory (AD) authentication. There are no SocialMiner user passwords stored on the SocialMiner System. <br /> <br /> Users do not need to be manually set up on SocialMiner in order to access the system. Any user that is authenticated via the Active Directory set-up can use the system. If there is need to limit who can use system then an AD group can be set up in AD and the SocialMiner system can be configured to only allow access from that group. <br /> <br /> AD authenticated users have access to all functions on the system, although gadgets access could be blocked by blocking certain URLs. <br /> == Twitter Accounts and Security ==<br /> <br /> Access to Twitter for the Twitter Account feed type is done via OAuth. When a &quot;Twitter Account&quot; Feed is created the user is prompted to authenticate with Twitter. The authentication token is stored by SocialMiner granting access to secured information from Twitter such as Direct Messages. This authentication also enables sending and replying to Twitter Direct Messages (DMs) from the account by using the Reply feature on the Home tab. <br /> <br /> '''Note''': All SocialMiner users are entitled to use Twitter accounts configured in the Twitter Account feed to read and respond to Direct Messages in that account. They are not required to enter the account password. This supports environments where the social-media care agents are not entitled to know the Twitter account password. Their ability to use SocialMiner is controlled via Active Directory and their ability to invoke post or perform actions on Twitter is controlled by SocialMiner. SocialMiner also tracks which SocialMiner User (AD account) makes each post; therefore it is possible for the enterprise to track which employee posted a tweet when sharing a Twitter account amongst a team. <br /> <br /> Twitter Stream feed type passwords are encrypted when stored in the SocialMiner configuration database and are also encrypted when sent to Twitter. <br /> <br /> === VMWare Open Virtual Format (OVF) ===<br /> <br /> The SocialMiner system supports one standard [http://www.vmware.com/appliances/getting-started/learn/ovf.html OVF] Appliance. The system requires ESXi version 4.0 Update 1 or ESXi 4.1 . <br /> <br /> For details on configuring VMWare and installing the OVF template, refer to [[Virtualization for Cisco SocialMiner]].<br /> <br /> = Developer Information =<br /> <br /> Developer information, including the SocialMiner API documentation and a discussion forum, is available on the Cisco developer site: http://developer.cisco.com/web/socialminer. <br /> <br /> Training labs are at http://docwiki.cisco.com/wiki/SocialMiner_Labs. <br /> <br /> = Copyright Notes =<br /> <br /> *Twitter is a registered trademark of Twitter, Inc. <br /> *Facebook is a registered trademark of Facebook, Inc. <br /> *iGoogle is a trademark of Google, Inc. <br /> *VMWare is a registered trademark of VMware, Inc. <br /> *Informix is a registered trademark of International Business Machines Corp.<br /> <br /> &lt;br&gt;''THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.'' <br /> <br /> ''THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.'' <br /> <br /> ''The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.'' <br /> <br /> ''NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED &quot;AS IS&quot; WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.'' <br /> <br /> ''IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA'' ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. <br /> <br /> ''Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at http://www.cisco.com/go/trademarks. All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R)'' <br /> <br /> ''Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.'' <br /> <br /> ''Copyright 2011 Cisco Systems, Inc. All rights reserved.'' <br /> <br /> [[Category:Cisco_SocialMiner]]</div>

Cchetty http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 2011-10-13T22:24:38Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''&lt;br&gt;<br /> <br /> ----<br /> <br /> Version compatibility of virtualized Cisco Unified Communications applications with various server/storage hardware options are listed below. <br /> <br /> *Support information below is as of the release date of '''Cisco Unified Communications 8.6(1)''', which updated '''8.0, 8.5 and 8.6''' support policies.<br /> <br /> *Ensure your deployment follows the rules listed [[High-level Checklist for Design and Implementation|here]].<br /> <br /> *Click on the application name for additional product-specific requirements and information (if any).<br /> <br /> *&quot;TRC&quot; = &quot;Tested Reference Configuration&quot; as described [[Unified Computing System Hardware|here]].<br /> <br /> &lt;br&gt;<br /> <br /> == Call Processing and System Management Applications&lt;br&gt; ==<br /> <br /> {| style=&quot;width: 1076px; height: 476px&quot; class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | Unified Communications Manager (1) <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]] <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> &lt;br&gt;<br /> <br /> |-<br /> | Cisco Emergency Responder <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | Session Manager Edition <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | Not supported <br /> &lt;br&gt;<br /> <br /> |-<br /> | Intercompany Media Engine <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> |-<br /> | Unified Attendant Consoles <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.0(3) <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> |-<br /> | UC Management Suite (OM, SM, SSM, PM) <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later<br /> |}<br /> <br /> &lt;br&gt;(1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes. <br /> <br /> == Messaging and Presence Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS)&lt;br&gt;<br /> |-<br /> | Cisco Unity Connection <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later<br /> |-<br /> | Cisco Unity <br /> | 7.0(2) and later <br /> | 7.0(2) and later <br /> | Not supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not Supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]] <br /> | 8.6(1) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Contact Center Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] &lt;br&gt;<br /> | 8.5(1) and later&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later&amp;nbsp;<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | 8.5(1) and later<br /> |-<br /> | [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO), Quality Management (QM), and WorkForce Management (WFM)] <br /> | 8.5(2) and later&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later<br /> |-<br /> | [[Unified Contact Center Enterprise]] &lt;br&gt;<br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below<br /> |-<br /> | - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tool,&amp;nbsp;limited/hybrid support for Unified ICME/CCH/ICMH <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported<br /> |-<br /> | - Progger, Outbound Option with SCCP Dialer, Webview, EIM/WIM, Expert Advisor, RSM, Unified CRM Connector <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | 8.0(3) and later <br /> | 8.5(2) and later&amp;nbsp; <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | Not supported<br /> |-<br /> | [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]&amp;nbsp; <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Unified Customer Voice Portal]] (all components) &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco MediaSense|Cisco MediaSense]] <br /> | Not supported&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]] <br /> | 8.5(3) and later &lt;br&gt;<br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later<br /> |-<br /> | [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager Unified Email Interaction Manager and Web Interaction Manager] <br /> | 4.4(1)<br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense 2011-10-11T06:49:02Z

<p>Cchetty: /* Cisco MediaSense-Specific Information for Sizing Guidelines */</p> <hr /> <div>{{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).}}&amp;nbsp; <br /> <br /> = Updates to this Page =<br /> <br /> The following is a list of significant updates to this page: <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Date <br /> ! Update<br /> |-<br /> | October 2011 <br /> | Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | June 2011 <br /> | Updated all links to align with the new Virtualization strucutre at [[Unified Communications in a Virtualized Environment]].<br /> |-<br /> | April 2011 <br /> | Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | November 2010 <br /> | Virtualization of Cisco MediaSense on UCS C Series hardware.<br /> |-<br /> | December 2010 <br /> | Updated OVA template download link.<br /> |}<br /> <br /> = Information for Partners about Cisco MediaSense Deployments =<br /> <br /> See [[Unified Communications in a Virtualized Environment]]. <br /> <br /> = VM-Specific Cisco MediaSense Hardware Requirements =<br /> <br /> See [[Tested Reference Configurations (TRC)]]. <br /> <br /> Before you install the Cisco MediaSense software in any server, you must address the following requirements: <br /> <br /> *Only Cisco MediaSense must be running on this VM host. No other product can be installed on this server. <br /> *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).<br /> <br /> = Cisco MediaSense-Specific Details for VMware Requirements =<br /> <br /> See [[Unified Communications VMWare Requirements]] <br /> <br /> *Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation. <br /> *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]. &lt;br&gt;<br /> <br /> == Cisco MediaSense, Release 8.5(1)&amp;nbsp; and 8.5(2) ==<br /> <br /> All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS). <br /> <br /> *Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1). <br /> *If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.<br /> <br /> <br /> <br /> == Cisco MediaSense, Release 8.5(3) ==<br /> <br /> {{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.}} <br /> <br /> 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.<br /> <br /> See the following links for more information: <br /> <br /> *See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications <br /> *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.&lt;br&gt;<br /> <br /> = Cisco MediaSense-Specific Information for OVA Templates =<br /> <br /> If your partitions (VM&amp;nbsp;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&amp;nbsp;templates provided by Cisco MediaSense.&lt;br&gt;<br /> <br /> See the following websites for more information:&lt;br&gt;<br /> <br /> *[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.2&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest Cisco MediaSense OVA Templates]<br /> <br /> &lt;br&gt;<br /> <br /> {{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]].}} <br /> <br /> &lt;br&gt;<br /> <br /> {{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.}}<br /> <br /> = Cisco MediaSense-Specific Information for Sizing Guidelines =<br /> <br /> 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.<br /> <br /> = How to Dump Install Logs to the VM Serial Port&lt;br&gt; =<br /> <br /> See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]]. <br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}<br /> <br /> [[Category:Cisco_MediaSense]]</div>

Cchetty http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense 2011-10-11T06:47:47Z

<p>Cchetty: /* Cisco MediaSense-Specific Information for Sizing Guidelines */</p> <hr /> <div>{{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).}}&amp;nbsp; <br /> <br /> = Updates to this Page =<br /> <br /> The following is a list of significant updates to this page: <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Date <br /> ! Update<br /> |-<br /> | October 2011 <br /> | Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | June 2011 <br /> | Updated all links to align with the new Virtualization strucutre at [[Unified Communications in a Virtualized Environment]].<br /> |-<br /> | April 2011 <br /> | Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | November 2010 <br /> | Virtualization of Cisco MediaSense on UCS C Series hardware.<br /> |-<br /> | December 2010 <br /> | Updated OVA template download link.<br /> |}<br /> <br /> = Information for Partners about Cisco MediaSense Deployments =<br /> <br /> See [[Unified Communications in a Virtualized Environment]]. <br /> <br /> = VM-Specific Cisco MediaSense Hardware Requirements =<br /> <br /> See [[Tested Reference Configurations (TRC)]]. <br /> <br /> Before you install the Cisco MediaSense software in any server, you must address the following requirements: <br /> <br /> *Only Cisco MediaSense must be running on this VM host. No other product can be installed on this server. <br /> *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).<br /> <br /> = Cisco MediaSense-Specific Details for VMware Requirements =<br /> <br /> See [[Unified Communications VMWare Requirements]] <br /> <br /> *Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation. <br /> *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]. &lt;br&gt;<br /> <br /> == Cisco MediaSense, Release 8.5(1)&amp;nbsp; and 8.5(2) ==<br /> <br /> All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS). <br /> <br /> *Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1). <br /> *If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.<br /> <br /> <br /> <br /> == Cisco MediaSense, Release 8.5(3) ==<br /> <br /> {{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.}} <br /> <br /> 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.<br /> <br /> See the following links for more information: <br /> <br /> *See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications <br /> *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.&lt;br&gt;<br /> <br /> = Cisco MediaSense-Specific Information for OVA Templates =<br /> <br /> If your partitions (VM&amp;nbsp;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&amp;nbsp;templates provided by Cisco MediaSense.&lt;br&gt;<br /> <br /> See the following websites for more information:&lt;br&gt;<br /> <br /> *[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.2&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest Cisco MediaSense OVA Templates]<br /> <br /> &lt;br&gt;<br /> <br /> {{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]].}} <br /> <br /> &lt;br&gt;<br /> <br /> {{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.}}<br /> <br /> = Cisco MediaSense-Specific Information for Sizing Guidelines =<br /> <br /> 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.<br /> <br /> = How to Dump Install Logs to the VM Serial Port&lt;br&gt; =<br /> <br /> See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]]. <br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}<br /> <br /> [[Category:Cisco_MediaSense]]</div>

Cchetty http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense 2011-10-11T06:47:26Z

<p>Cchetty: /* Cisco MediaSense-Specific Information for Sizing Guidelines */</p> <hr /> <div>{{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).}}&amp;nbsp; <br /> <br /> = Updates to this Page =<br /> <br /> The following is a list of significant updates to this page: <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Date <br /> ! Update<br /> |-<br /> | October 2011 <br /> | Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | June 2011 <br /> | Updated all links to align with the new Virtualization strucutre at [[Unified Communications in a Virtualized Environment]].<br /> |-<br /> | April 2011 <br /> | Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | November 2010 <br /> | Virtualization of Cisco MediaSense on UCS C Series hardware.<br /> |-<br /> | December 2010 <br /> | Updated OVA template download link.<br /> |}<br /> <br /> = Information for Partners about Cisco MediaSense Deployments =<br /> <br /> See [[Unified Communications in a Virtualized Environment]]. <br /> <br /> = VM-Specific Cisco MediaSense Hardware Requirements =<br /> <br /> See [[Tested Reference Configurations (TRC)]]. <br /> <br /> Before you install the Cisco MediaSense software in any server, you must address the following requirements: <br /> <br /> *Only Cisco MediaSense must be running on this VM host. No other product can be installed on this server. <br /> *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).<br /> <br /> = Cisco MediaSense-Specific Details for VMware Requirements =<br /> <br /> See [[Unified Communications VMWare Requirements]] <br /> <br /> *Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation. <br /> *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]. &lt;br&gt;<br /> <br /> == Cisco MediaSense, Release 8.5(1)&amp;nbsp; and 8.5(2) ==<br /> <br /> All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS). <br /> <br /> *Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1). <br /> *If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.<br /> <br /> <br /> <br /> == Cisco MediaSense, Release 8.5(3) ==<br /> <br /> {{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.}} <br /> <br /> 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.<br /> <br /> See the following links for more information: <br /> <br /> *See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications <br /> *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.&lt;br&gt;<br /> <br /> = Cisco MediaSense-Specific Information for OVA Templates =<br /> <br /> If your partitions (VM&amp;nbsp;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&amp;nbsp;templates provided by Cisco MediaSense.&lt;br&gt;<br /> <br /> See the following websites for more information:&lt;br&gt;<br /> <br /> *[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.2&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest Cisco MediaSense OVA Templates]<br /> <br /> &lt;br&gt;<br /> <br /> {{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]].}} <br /> <br /> &lt;br&gt;<br /> <br /> {{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.}}<br /> <br /> = Cisco MediaSense-Specific Information for Sizing Guidelines =<br /> <br /> 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.<br /> <br /> = How to Dump Install Logs to the VM Serial Port&lt;br&gt; =<br /> <br /> See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]]. <br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}<br /> <br /> [[Category:Cisco_MediaSense]]</div>

Cchetty http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense 2011-10-11T06:46:37Z

<p>Cchetty: /* Cisco MediaSense-Specific Information for Sizing Guidelines */</p> <hr /> <div>{{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).}}&amp;nbsp; <br /> <br /> = Updates to this Page =<br /> <br /> The following is a list of significant updates to this page: <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Date <br /> ! Update<br /> |-<br /> | October 2011 <br /> | Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | June 2011 <br /> | Updated all links to align with the new Virtualization strucutre at [[Unified Communications in a Virtualized Environment]].<br /> |-<br /> | April 2011 <br /> | Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | November 2010 <br /> | Virtualization of Cisco MediaSense on UCS C Series hardware.<br /> |-<br /> | December 2010 <br /> | Updated OVA template download link.<br /> |}<br /> <br /> = Information for Partners about Cisco MediaSense Deployments =<br /> <br /> See [[Unified Communications in a Virtualized Environment]]. <br /> <br /> = VM-Specific Cisco MediaSense Hardware Requirements =<br /> <br /> See [[Tested Reference Configurations (TRC)]]. <br /> <br /> Before you install the Cisco MediaSense software in any server, you must address the following requirements: <br /> <br /> *Only Cisco MediaSense must be running on this VM host. No other product can be installed on this server. <br /> *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).<br /> <br /> = Cisco MediaSense-Specific Details for VMware Requirements =<br /> <br /> See [[Unified Communications VMWare Requirements]] <br /> <br /> *Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation. <br /> *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]. &lt;br&gt;<br /> <br /> == Cisco MediaSense, Release 8.5(1)&amp;nbsp; and 8.5(2) ==<br /> <br /> All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS). <br /> <br /> *Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1). <br /> *If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.<br /> <br /> <br /> <br /> == Cisco MediaSense, Release 8.5(3) ==<br /> <br /> {{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.}} <br /> <br /> 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.<br /> <br /> See the following links for more information: <br /> <br /> *See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications <br /> *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.&lt;br&gt;<br /> <br /> = Cisco MediaSense-Specific Information for OVA Templates =<br /> <br /> If your partitions (VM&amp;nbsp;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&amp;nbsp;templates provided by Cisco MediaSense.&lt;br&gt;<br /> <br /> See the following websites for more information:&lt;br&gt;<br /> <br /> *[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.2&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest Cisco MediaSense OVA Templates]<br /> <br /> &lt;br&gt;<br /> <br /> {{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]].}} <br /> <br /> &lt;br&gt;<br /> <br /> {{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.}}<br /> <br /> = Cisco MediaSense-Specific Information for Sizing Guidelines =<br /> <br /> 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.<br /> <br /> = How to Dump Install Logs to the VM Serial Port&lt;br&gt; =<br /> <br /> See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]]. <br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}<br /> <br /> [[Category:Cisco_MediaSense]]</div>

Cchetty http://docwiki.cisco.com/wiki/Storage_System_Performance_Specifications 2011-10-10T16:42:21Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Before You Buy or Deploy - Considerations for Design and Procurement]]'''&lt;br&gt;<br /> <br /> &lt;br&gt;<br /> <br /> This page illustrates IOPS under various conditions for Unified Communications applications. This area is under construction. Check back frequently for updates. <br /> <br /> == Unified Communications Manager ==<br /> <br /> This section provides the IOPS data for a Cisco Unified Communications Manager system under load. <br /> <br /> These values are per active VM OVA. Which VM OVAs are active, and how many are active simultaneously, depends on how the CUCM cluster is setup (see www.cisco.com/go/ucsrnd for details). <br /> <br /> Active Call processing nodes: As a reference, the following steady state IOPS were observed at various loads (expressed in Busy Hour Call Attempts): <br /> <br /> ::*10K BHCA produces ~ 35 IOPS <br /> ::*25K BHCA produces ~ 50 IOPS <br /> ::*50K BHCA produces ~ 100 IOPS <br /> ::*100K BHCA produces ~ 150 IOPS<br /> <br /> {{note| The Unified Communications Manager data is based on ~93-98% sequential writes.}} <br /> <br /> *Software upgrades during business hours generate 800 to 1200 IOPS in addition to steady state IOPS. <br /> *CDR/CMR via CDR Analysis and Reporting (CAR) <br /> **CUCM sending CDR/CMR to the external billing server does not incur any additional IOPS. <br /> **Enabling CAR continuous loading results in around 300 IOPS average on the system. <br /> **Scheduled uploads are around 250 IOPS for Publisher's VM only.<br /> *Trace collection is 100 IOPS (occurs on all VMs for which tracing is enabled). <br /> *Nightly backup (usually Publisher's VM only) is 50 IOPS.<br /> <br /> == Cisco Unity Connection ==<br /> <br /> === Summary of IOPS for Unity Connection ===<br /> <br /> {| style=&quot;text-align: center; width: 75%&quot; border=&quot;1&quot;<br /> |-<br /> ! IOPS Type <br /> ! 1vCPU <br /> ! 2vCPU <br /> ! 4vCPU <br /> ! 7vCPU<br /> |-<br /> | Avg Total <br /> | 78.66 <br /> | 129.01 <br /> | 217.89 <br /> | 201.73<br /> |-<br /> | Peak Total <br /> | 760.99 <br /> | 714.06 <br /> | 867.88 <br /> | 773.70<br /> |-<br /> | Avg Read <br /> | 5.90 <br /> | 19.60 <br /> | 45.67 <br /> | 9.53<br /> |-<br /> | Peak Read <br /> | 601.84 <br /> | 469.46 <br /> | 693.21 <br /> | 526.22<br /> |-<br /> | Avg Write <br /> | 72.77 <br /> | 109.40 <br /> | 172.22 <br /> | 192.20<br /> |-<br /> | Peak Write <br /> | 247.14 <br /> | 293.51 <br /> | 371.97 <br /> | 413.50<br /> |}<br /> <br /> == Unified Presence ==<br /> <br /> The CUP 1000 user OVA generates about 60 IOPS during steady-state. Expect similar peaks as CUCM during backups and upgrades. <br /> <br /> &lt;br&gt;<br /> <br /> == Cisco Unified Attendant Consoles ==<br /> <br /> This section provides the IOPS data for Cisco Unified Attendant Consoles (using Enterprise Attendant Console to produce heaviest load). Load test and average operations are represented. These tests use the published OVA&amp;nbsp;template for Cisco Unified Attendant Consoles. <br /> <br /> {| border=&quot;1&quot; cellspacing=&quot;1&quot; cellpadding=&quot;1&quot; width=&quot;1172&quot;<br /> |-<br /> | bgcolor=&quot;#cccccc&quot; valign=&quot;middle&quot; colspan=&quot;9&quot; align=&quot;center&quot; | '''LOAD TESTING'''<br /> |-<br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; colspan=&quot;3&quot; align=&quot;center&quot; | '''IOPS (Read)''' <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; colspan=&quot;3&quot; align=&quot;center&quot; | '''IOPS (Write)''' <br /> | &lt;br&gt;<br /> |-<br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Min''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Max''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Average''' <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Min''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Max''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Average''' <br /> | '''Operating Conditions'''<br /> |-<br /> | Cisco Unified Attendant Console Server <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 1013.605 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0.442 <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 1112.87 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 12.121 <br /> | 5,000 calls per hour, 25 concurrent operators, continuous LDAP&amp;nbsp;sync, full logging<br /> |-<br /> | Upgrade <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 320.006 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 3.691 <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 105.001 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 10.341 <br /> | Major upgrade<br /> |-<br /> | bgcolor=&quot;#cccccc&quot; valign=&quot;middle&quot; colspan=&quot;9&quot; align=&quot;center&quot; | '''AVERAGE OPERATIONS'''<br /> |-<br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; colspan=&quot;3&quot; align=&quot;center&quot; | '''IOPS (Read)''' <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; colspan=&quot;3&quot; align=&quot;center&quot; | '''IOPS (Write)''' <br /> | &lt;br&gt;<br /> |-<br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Min''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Max''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Average''' <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Min''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Max''' <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | '''Average''' <br /> | '''Operating Conditions'''<br /> |-<br /> | Cisco Unified Attendant Console Server <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 11.6 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0.092 <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 561.05 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 10.82 <br /> | Synchronized directory, cached BLF, minimum online changes<br /> |-<br /> | Upgrade <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 107.001 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 5.751 <br /> | &lt;br&gt;<br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 0 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 50 <br /> | valign=&quot;middle&quot; align=&quot;center&quot; | 3.57 <br /> | Minor upgrade<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> &lt;br&gt;<br /> <br /> == Contact Center ==<br /> <br /> === [[Virtualization for Unified CCE|Contact Center Enterprise]]&lt;br&gt; ===<br /> <br /> The SAN must be able to handle the following Unified CCE application disk I/O characteristics. <br /> <br /> &lt;br&gt;<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! rowspan=&quot;2&quot; | Unified CCE Component <br /> ! colspan=&quot;3&quot; | IOPS <br /> ! colspan=&quot;3&quot; | Disk Read KBytes / sec <br /> ! colspan=&quot;3&quot; | Disk Write KBytes / sec <br /> ! rowspan=&quot;2&quot; | Operating Conditions<br /> |-<br /> | '''Peak''' <br /> | '''Avg.''' <br /> | '''95th Pct.''' <br /> | '''Peak''' <br /> | '''Avg.''' <br /> | '''95th Pct.''' <br /> | '''Peak''' <br /> | '''Avg.''' <br /> | '''95th Pct.''' <br /> &lt;br&gt;<br /> <br /> |-<br /> | Router <br /> | 20 <br /> | 8 <br /> | 10 <br /> | 520 <br /> | 30 <br /> | 180 <br /> | 400 <br /> | 60 <br /> | 150 <br /> | rowspan=&quot;3&quot; | 8,000 agents; 60 cps; ECC: 5 scalars @ 35 bytes each; No reporting.<br /> |-<br /> | Logger <br /> | 1,000 <br /> | 600 <br /> | 700 <br /> | 4,000 <br /> | 600 <br /> | 2,500 <br /> | 12,000 <br /> | 3,000 <br /> | 7,000<br /> |-<br /> | HDS <br /> | 1,600 <br /> | 1,000 <br /> | 1,100 <br /> | 600 <br /> | 70 <br /> | 400 <br /> | 6,000 <br /> | 2,000 <br /> | 3,800<br /> |-<br /> | Agent PG <br /> | 125 <br /> | 40 <br /> | 70 <br /> | 300 <br /> | 5 <br /> | 20 <br /> | 2,000 <br /> | 1,200 <br /> | 1,500 <br /> | 2,000 agents, 15 cps <br /> &lt;br&gt;<br /> <br /> |-<br /> | HDS <br /> | 3,900 <br /> | 2,500 <br /> | 3,800 <br /> | 75,000 <br /> | 30,000 <br /> | 50,000 <br /> | 9,500 <br /> | 2,200 <br /> | 5,800 <br /> | 8,000 agents; 60 cps; 200 reporting users at max query load; ECC: 5 scalars @ 35 bytes each.<br /> |-<br /> | ROGGER <br /> | 610 <br /> | 360 <br /> | 425 <br /> | 2,700 <br /> | 400 <br /> | 1,600 <br /> | 7,500 <br /> | 2,150 <br /> | 4,300 <br /> | 4,000 agents; 30 cps; ECC: 5 scalars @ 35 bytes each<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> === [[Virtualization for Unified CCX|Contact Center Express/IPIVR IOPS]] ===<br /> <br /> The following table lists the IOPS numbers for Unified Contact Center Express/IPIVR. <br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! IOPS Type <br /> ! 2vCPU<br /> |-<br /> | IOPS Avg per VM <br /> | 150<br /> |-<br /> | IOPS Max spike per VM <br /> | 1500<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> === [[Virtualization for Cisco MediaSense|Cisco MediaSense]] ===<br /> <br /> The following table lists the IOPS numbers for Cisco MediaSense partitions. <br /> <br /> {| style=&quot;width: 513px; height: 228px&quot; border=&quot;1&quot; cellspacing=&quot;1&quot; cellpadding=&quot;1&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Media Partitions&lt;br&gt;<br /> ! scope=&quot;col&quot; | IOPS Specifications&lt;br&gt;<br /> |-<br /> | <br /> Average IOPS for non-media partitions<br /> <br /> | 1700 ops/sec<br /> |-<br /> | Average IOPS for media partitions <br /> | 50 ops/sec<br /> |-<br /> | Average bandwidth for non-media partitions <br /> | 7300 kbytes/sec<br /> |-<br /> | Average bandwidth for media partitions <br /> | 1000 kbytes/sec<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> === [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager Cisco Unfied Email Interaction Manager and Web Interaction Manager] ===<br /> <br /> {| border=&quot;1&quot; cellspacing=&quot;1&quot; cellpadding=&quot;1&quot; width=&quot;800&quot;<br /> |-<br /> | rowspan=&quot;2&quot; | EIM-WIM compontnets<br /> | colspan=&quot;3&quot; | IOPS<br /> | colspan=&quot;3&quot; | Disk Read KBytes / sec <br /> | colspan=&quot;3&quot; | Disk Write KBytes / sec<br /> |-<br /> | Peak<br /> | 95th Pct.<br /> | Avg.<br /> | Peak<br /> | 95th Pct.<br /> | Avg.<br /> | Peak<br /> | 95th Pct.<br /> | Avg.<br /> |-<br /> | Application Server <br /> | 11.7 <br /> | 3.21 <br /> | 1.55<br /> | 51<br /> | 1 <br /> | 0.726<br /> | 103 <br /> | 19<br /> | 8.32<br /> |-<br /> | File Server <br /> | 43.65<br /> | 25.23 <br /> | 14.36<br /> | 189 <br /> | 2 <br /> | 2 <br /> | 1769 <br /> | 1025.9<br /> | 446<br /> |-<br /> | Database Server <br /> | 736.9<br /> | 552 <br /> | 263.31 <br /> | 35450<br /> | 23184 <br /> | 3903<br /> | 5737<br /> | 2872 <br /> | 1625<br /> |-<br /> | Messaging Server <br /> | 9.15 <br /> | 2.71 <br /> | 1.47<br /> | 57<br /> | 1 <br /> | 0.7 <br /> | 88 <br /> | 15.1<br /> | 8<br /> |-<br /> | Services Server <br /> | 11.15<br /> | 3.155<br /> | 1.53 <br /> | 55<br /> | 1 <br /> | 0.73<br /> | 1.89<br /> | 17 <br /> | 9<br /> |-<br /> | Web Server <br /> | 11.2 <br /> | 3.36 <br /> | 1.43 <br /> | 55<br /> | 1 <br /> | 0.8 <br /> | 173<br /> | 21 <br /> | 10.24<br /> |}<br /> <br /> &amp;nbsp;<br /> <br /> &amp;nbsp;<br /> <br /> &amp;nbsp;<br /> <br /> &amp;nbsp;<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE 2011-10-10T16:42:21Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Updates to this Page ==<br /> <br /> The following is a list of significant updates to this page: <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Date <br /> ! Update<br /> |-<br /> | June 28, 2011 <br /> | Updated list of Unified CCE components that have not been qualified and are not supported in virtualization.&lt;br&gt;Updated Section 5.1 ESXI 4.1 Software Requirements to add new link to Disable LRO.&lt;br&gt;Updated Section 6 Unified CCE Component Capacities and VM Configuration Requirements to add new link to Downloading OVA Templates for UC Applications.&lt;br&gt;Removed Section 7.2ESXi 4.1 Network Settings.&lt;br&gt;Changed title from Creating Virtual Machines from OVA VM Templates to Cisco Unified CCE-Specific Information for OVA Templates&lt;br&gt;Removed Section 12.1 Downloading OVA Templates and added new links to Unified Communications Virtualization Downloads and Unified CCE OVA Templates.<br /> |-<br /> | June 1, 2011 <br /> | Added Section 5.1 ESXi 4.1 Software Requirements.&lt;br&gt;Added Section 7.2 ESXi 4.1 Network Settings.&lt;br&gt;Removed references to ESXi 4.0.&lt;br&gt;Updated ''UCS Network Configuration'' section.<br /> |-<br /> | May 9, 2011 <br /> | Updated the ''Unified CCE Component Co-Residency and Sample Deployments ''section.<br /> |-<br /> | February 17, 2011 <br /> | <br /> Updated the ''Creating Virtual Machines from OVA VM Templates'' section.&lt;br&gt;Removed OVA&amp;nbsp;list from this page and added a link.&lt;br&gt;Added the Scalability Assumptions section.&lt;br&gt;Updated the CUIC&amp;nbsp;RAM (GB) numbers in the sample CCE&amp;nbsp;deployments.&lt;br&gt;Updated the sample deployment tables and highlighted optional items.<br /> <br /> |-<br /> | December 22, 2010 <br /> | Updated the pointer links for the Bill of Material, CCMP virtualization page, and the Hybrid Deployment section.<br /> |-<br /> | December 20, 2010 <br /> | Updated the Component Capacities section, the VM configuration requirements table, the Hybrid Deployment Options section, the steps for installing/migrating Unified CCE Components, the Support for Virtualization on the ESXi/UCS Platform section, and the Hardware Requirements section.<br /> |-<br /> | December 14, 2010 <br /> | Added Avaya ACD PG, TDM ACD PG, and Unified Contact Center Gateway to the Unified CCE Component Capacities and VM Configuration Requirements section. Updated the Steps for Installing/Migrating Unified CCE Components on Virtual Machines secton. Added Hybrid Deployment Options section.<br /> |-<br /> | December 10, 2010 <br /> | Added Unified CVP, Unified IC, Contact Center Management Portal (CCMP), and CAD to the sample deployments section.<br /> |-<br /> | October&amp;nbsp;1,&amp;nbsp;2010 <br /> | This page, [http://docwiki.cisco.com/wiki/UCCE_on_UCS_Deployment_Certification_Requirements_and_Ordering_Information UCCE on UCS Deployment Certification Requirements and Ordering Information], and [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE UCS Network Configuration for UCCE] updated to reflect support of UCS C-Series hardware on UCCE.<br /> |-<br /> | September&amp;nbsp;28,&amp;nbsp;2010 <br /> | CVP added to list of supported components/deployments.<br /> |-<br /> | September&amp;nbsp;21,&amp;nbsp;2010 <br /> | IPIVR added to list of supported components/deployments and as an optional component in the sample deployment tables at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Sample_CCE_Deployments Sample CCE Deployments].<br /> |}<br /> <br /> == Information for Partners about Unified CCE on UCS Deployment Certification and Ordering ==<br /> <br /> '''It is important that partners who are planning to sell UCS products on Unified Contact Center Enterprise read the DocWiki page''' [[Unified CCE on UCS Deployment Certification Requirements and Ordering Information]]. <br /> <br /> This page contains essential information for partners about the following: <br /> <br /> :*Partner Certification Requirements <br /> :*UCS Server Ordering Information <br /> :*Important Notes on Cisco UCS Service and Support<br /> <br /> == Unified CCE 8.x Support for Virtualization on the ESXi/UCS Platform ==<br /> <br /> Starting with Release 8.0(2), virtualization of the following deployments and Unified CCE components on Cisco Unified Computing Systems (UCS) B200 Series and C210 Series hardware is supported: <br /> <br /> :*Router <br /> :*Logger <br /> :*Agent PG <br /> :*MR PG <br /> :*VRU PG <br /> :*Unified Contact Center Gateway <br /> :*Avaya ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2) <br /> :*TDM ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2) <br /> :*Cisco Agent Desktop (CAD) Server <br /> :*Administration and Data Server with one of the following roles:<br /> ::*Administration Server and Real-time Data Server (AW) <br /> ::*Configuration-only Administration Server (AW-CONFIG) <br /> ::*Administration Server and Real-time and Historical Data Server (AW-HDS) <br /> ::*Administration Server, Real-time and Historical Data Server, and Detail Data Server (AW-HDS-DDS) <br /> ::*Historical Data Server and Detail Data Server (HDS-DDS)<br /> :*Administration Client <br /> :*Outbound Option with SIP Dialer (collocate SIP Dialer and MR PG with Agent PG in the same VM guest. Generic PG can also be collocated with the Agent PG in the same VM guest. Published agent capacity formula with Outbound Option applies.) <br /> :*Support Tools <br /> :*Rogger (a Router and a Logger in the same VM) <br /> :*The Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE is supported; see the section [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Support_for_UCM_Clustering_Over_the_WAN_with_Unified_CCE_on_UCS_Hardware Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware] for important information. <br /> :*Unified IP-IVR is supported with Unified CCE on UCS B-Series solution and on UCS C-Series with the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] only. Please refer to the IPIVR product specific pages for detail. <br /> :*CVP is supported with CCE on UCS solution. Please refer to the [http://docwiki.cisco.com/wiki/Unified_Customer_Voice_Portal Unified Customer Voice Portal] wiki page for details. <br /> :*Contact Center Management Portal (CCMP). See the [[Virtualization for CCMP with Unified CCE on UCS Hardware]] wiki page for details. <br /> :*Cisco Unified Intelligence Center (Unified IC). Please refer to the [[Cisco Unified Intelligence Center]] wiki page for details. <br /> :*Cisco E-mail Interaction Manager (EIM)/Web Interaction Manager (WIM). See the Virtualization for EIM-WIM wiki page for details<br /> <br /> The following deployments and Unified CCE components have not been qualified and '''are not supported''' in virtualization: <br /> <br /> :*Progger (a Router, a Logger, and a Peripheral Gateway); this all-in-one deployment configuration is not scalable in a virtualization environment. Instead, use the Rogger or Router/Logger VM deployment configuration. <br /> :*Unified CCH <br /> :*Unified ICMH <br /> :*Outbound Option with SCCP Dialer <br /> :*WebView Server <br /> :*Expert Advisor <br /> :*Remote Silent Monitoring (RSM) <br /> :*Span based Silent Monitoring on UCS B-series chassis <br /> :*Cisco Unified CRM Connector <br /> :*IPsec. UCS does not support IPsec off-board processing, therefore IPsec is not supported in virtualization.<br /> <br /> {{note|The hybrid (virtual and non-virtual server) deployment model is supported. Components that are not yet virtualized can continue to be on MCS in the UCCE on UCS deployment. See the [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Hybrid_Deployment_Options Hybrid Deployment Options] section for more information.}} <br /> <br /> The following VMware features are not supported with Unified CCE: <br /> <br /> :*VMware Physical to Virtual migration <br /> :*VMware snapshots <br /> :*VMware Consolidated Backup <br /> :*VMware High Availability (HA) <br /> :*VMware Site Recovery Manager <br /> :*VMware vCenter Update Manager <br /> :*VMware vCenter Converter<br /> <br /> == Hardware Requirements for Unified CCE Virtualized Systems ==<br /> <br /> Requirements for Cisco Unified CCE systems using UCS B200 or C210 hardware are located in the [[Unified Computing System Hardware|Unified Computing System Hardware]]. <br /> <br /> For UCS C210, Unified CCE supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] with a specific HDS Virtual Machine (VM) coresidence/population rule. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Sample_CCE_Deployments Sample CCE Deployments] <br /> <br /> Unified CCE supports MCS-7845-I3-CCE2 with virtualization. For a list of supported virtualized components on MCS servers, 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, Release, 8.0(x).] Unified CCE does not support UCS C200. <br /> <br /> == VMware and Application Software Requirements ==<br /> <br /> The following software requirements apply specifically to Unified Contact Center Enterprise: <br /> <br /> :*VMWare ESXi 4.0 or 4.1, minimum version 4.0U1. ''Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported.'' <br /> :*If you are upgrading ESXi software, see the section [http://docwiki-dev.cisco.com/wiki/Ongoing_Virtualization_Operations_and_Maintenance Upgrade ESXi]. <br /> :*The Windows, SQL, and other third party software requirements for the Unified CCE applications in the ESXi/UCS platform are the same as in the physical server. For such information see the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise &amp;amp; Hosted, Release 8.0(x)].<br /> <br /> === ESXi 4.1 Software Requirements ===<br /> <br /> When Cisco Unified CCE is running on ESXi 4.1, you must perform the following steps: <br /> <br /> :*You must install or upgrade VMware Tools for ESXi 4.1 on each of the VMs and use all of the VMware Tools default settings. For more information, see the section [http://docwiki-dev.cisco.com/wiki/VMware_Tools VMware Tools] <br /> :*You must disable Large Receive Offload (LRO). For details, see the section [http://docwiki-dev.cisco.com/wiki/Disable_LRO Disable LRO]<br /> <br /> &lt;br&gt;<br /> <br /> = Unified CCE Component Capacities and VM Configuration Requirements =<br /> <br /> For supported Unified CCE&amp;nbsp;component capacities and VM computing resource requirements, see the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise List of Unified CCE OVA Templates.] <br /> <br /> {{note| You must use the OVA VM templates to create the Unified CCE component VMs.}} <br /> <br /> &lt;br&gt;For instructions on how to obtain the OVA templates, see [http://docwiki.cisco.com/wiki/Downloading_OVA_Templates_for_UC_Applications Downloading OVA Templates for UC Applications] <br /> <br /> == Unified CCE Scalability Impacts ==<br /> <br /> The [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information] is based on the operating conditions published in the ''Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 8.x'', Chapter 10, ''Operating Conditions'' and the ''Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted'''','''''Release 8.x, Section 5. Both documents are available at [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Cisco.com]'''.''' <br /> <br /> The following features reduce the scalability of certain components below the agent count of the respective OVA [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information]. <br /> <br /> *CTI OS Security - CTI OS Server capacity is impacted when CTI OS Security is enabled; capacity is decreased by 25%. <br /> *Mobile Agents - Refer to the SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Mobile Agents. <br /> *Outbound Option – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Outbound Option. <br /> *Agent Greeting – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with the Agent Greeting feature enabled. <br /> *Extended Call Context (ECC) usage greater than the level noted in the Operating Conditions will have a performance and scalability impact on critical components of the Unified CCE solution. As noted in the SRND, the capacity impact will vary based on ECC configuration, therefore, guidance must be provided on a case-by-case basis.<br /> <br /> = UCS Network Configuration =<br /> <br /> :*'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (UCCE) on UCS servers, see [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE UCS Network Configuration for UCCE]. <br /> :*QoS should be enabled for the Router and PG configuration. For more information on QoS consideration, refer to Chapter 12, &amp;nbsp;[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND)]. <br /> :*For information on best practices for Cisco VLAN trunking to VMware, refer to [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003806 this website].<br /> <br /> == Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware ==<br /> <br /> You can deploy the Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE on UCS hardware. <br /> <br /> When you implement this deployment model, be sure to follow the best practices outlined in the section &quot;IPT: Clustering Over the WAN&quot; in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND).] <br /> <br /> In addition, note the following expectations for UCS hardware points of failure: <br /> <br /> *For communication path single point of failure performed by Cisco on the Unified CCE UCS B-series High Availability (HA) deployment, system call handling was observed to be degraded for up to 45 seconds while the system recovered from the fault, depending upon the subsystem faulted. Single points of failure will not cause the built-in ICM software failover to occur. Single points of failure include, but are not limited to, a single fabric interconnect failure, a single fabric extender failure, and single link failures.<br /> <br /> *Multiple points of failure on the Unified CCE UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.<br /> <br /> === B-Series Considerations ===<br /> <br /> When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS '''M81KR''' Virtual Interface Card is mandatory. <br /> <br /> New B-Series deployments using Clustering Over the WAN '''must''' use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G. <br /> <br /> See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#UCCE_on_UCS_B-Series_Network_Configuration UCCE on UCS B-Series Network Configuration]. <br /> <br /> === C-Series Considerations ===<br /> <br /> If deploying Clustering Over the WAN with C-Series hardware, '''do not''' trunk public and private networks. You '''must''' use separate physical interfaces off of the C-Series servers to create the public and private connections. See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#Network_Requirements_for_C-210_M1_Servers Network Requirements for C-210 M1 Servers]. <br /> <br /> &lt;br&gt;<br /> <br /> = Notes for Deploying Unified CCE Applications on UCS B-Series Hardware with SAN =<br /> <br /> In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays. <br /> <br /> In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore. <br /> <br /> Keep the following considerations in mind when deploying UCCE applications on UCS B-series hardware with SAN. <br /> <br /> *This deployment must comply with the conditions listed in Section 3.1.6 of the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware &amp;amp; System Software Specification (Bill of Materials) for Cisco Unified Contact Center Enterprise, Release 8.0(1).] In particular, SAN disk arrays must be configured as RAID 5 or RAID 10.&lt;br&gt;<br /> <br /> *Each Historical Data Server (HDS) requires a dedicated LUN and a datastore with a 2 MB block size. No other application can reside on the same datastore as the HDS. The HDS requires a 2 MB block size to accommodate the 500 GB OVA disk size, which exceeds the 256 GB file size supported by the default 1 MB block size for datastores. The HDS block size is configured in VMware at datastore creation.<br /> <br /> *To help keep your system running most efficiently, schedule automatic database purging to run when your system is least busy.&lt;br&gt;<br /> <br /> *The SAN design and configuration must meet the following VMware ESXi disk performance guidelines: <br /> **Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array. <br /> **Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.<br /> <br /> *The SAN design and configuration must meet the following Windows performance counters on UCCE VMs: <br /> **AverageDiskQueueLength must remain less than (1.5 ∗ (the total number of disks in the array)). <br /> **&amp;nbsp;%Disktime must remain less than 60%.&lt;br&gt;<br /> <br /> *Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CCE applications should be designed for the 95th percentile IOPS values published in this wiki. For other UC applications, please follow their respective IOPS requirements &amp;amp; guidelines.<br /> <br /> &lt;br&gt;<br /> <br /> See below for an example of SAN configuration for Rogger 2000 agent deployment. This example corresponds to the 2000 agent Sample CCE Deployment for UCS B-Series described in: [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Coresidency_and_Sample_Deployments Unified CCE Component Coresidency and Sample Deployments]. <br /> <br /> == Example of SAN Configuration for Unified CCE ROGGER Deployment up to 2000 Agents ==<br /> <br /> The following SAN configuration was a tested design, though generalized here for illustration. It is not the only possible way in which to provision SAN arrays, LUNs, and datastores to UC applications. However, you must adhere to the guidance given earlier in this section (above). <br /> <br /> === Rogger Side A ===<br /> <br /> [[Image:RoggerSideA.jpg]] <br /> <br /> === Rogger Side B ===<br /> <br /> [[Image:RoggerSideB.jpg]] <br /> <br /> = Steps for Installing/Migrating Unified CCE Components on Virtual Machines =<br /> <br /> Follow the steps and references below to install the Unified CCE components on virtual machines. You can use these instructions to install or upgrade systems running with Unified CCE 8.0(2) and later. You can also use these instructions to migrate virtualized systems from Unified CCE 7.5(x) to Unified CCE 8.0(2) or later, including the Avaya PG and other selected TDM PGs that were supported on Unified CCE 7.5(x). Not all TDM PGs supported in Unified CCE 7.5(x) are supported in Unified CCE 8.0(x). For more information, see [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).] <br /> <br /> #Acquire the supported servers for Unified CCE 8.0(x). <br /> #*Cisco UCS servers are specified in the [http://docwiki-dev.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE&amp;oldid=63654#Hardware_Requirements_for_Unified_CCE_Virtualized_Systems Hardware Requirements for Unified CCE Virtualized Systems] section. <br /> #*MCS-7845-I3-CCE2 is specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).] <br /> #*If there are PG VMs that are running on the following older MCS servers, MCS-7845-H2 or MCS-7845-I2, replace these servers with supported servers.<br /> #Install, setup, and configure the servers. <br /> #Configure the network. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#UCS_Network_Configuration UCS Network Configuration]. {{note |Configuring the network for the MCS servers is the same as configuring the network for the UCS C-Series servers.}} <br /> #If VMware VirtualCenter is used for virtualization management, install or update to VMware vCenter Server 4.0 or later. <br /> #Install and Boot VMWare ESXi. See the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide] or the [http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/os/vmware/install/vmware_install_c.html Cisco UCS C-Series Servers VMware Installation Guide]. On C-Series servers or MCS servers, you must configure the ESXi datastore block size for the Administration &amp;amp; Data Server. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Configuring_the_ESXi_Data_Store_Block_Size_for_Administration_and_Data_Server Configuring the ESXi Data Store Block Size for Administration and Data Server] for instructions. <br /> #Create the Unified CCE virtual machines from the OVA templates. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Creating_Virtual_Machines_from_OVA_VM_Templates Creating Virtual Machines from OVA VM Templates]. This is a requirement for all component running Unified CCE 8.0(2) and later. In Unified CCE 7.5(x), this is not a requirement. <br /> #Install VMware Tools with the ESXi version on the virtual machines. Install the same version of VMware Tools as the ESXi software on the virtual machines. <br /> #Install Windows OS and SQL Server (for Logger and HDS components) on the created virtual machines. {{note| Microsoft Windows Server 2003 ''Standard Edition'' and Microsoft SQL Server 2005 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.}} <br /> #Install or migrate the Unified CCE Software components on the configured virtual machines, using Fresh Install or Tech Refresh Upgrade, as described in [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Installing_Unified_CCE_Components_on_Virtual_Machines Installing Unified CCE components on virtual machines] and [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Migrating_Unified_CCE_Components_to_Virtual_Machines Migrating Unified CCE components].<br /> <br /> = Unified CCE Component Coresidency and Sample Deployments =<br /> <br /> You can have one or more Unified CCE VMs coresident on the same ESXi server (for example, B200M2 blade or C210M2 rack mount server).&amp;nbsp; However, you must follow the rules described below: <br /> <br /> :*You can have any number of Unified CCE virtual machines and combination of coresidency of Unified CCE virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation does not over commit the available ESXi server computing resources.&amp;nbsp; <br /> :*You must not have&amp;nbsp;CPU overcommit on the ESXi server that is running Unified CCE&amp;nbsp;realtime application components.&amp;nbsp; The total number of vCPUs among all&amp;nbsp;the virtual machines on an ESXi host must not be greater than the total number of CPUs available on the ESXi server.&amp;nbsp; In the case of the Cisco UCS B-200 and C-210, the total number of CPUs available is 8. <br /> :*You must not have&amp;nbsp;memory overcommit on the ESXi host running UC realtime applications.&amp;nbsp; You must allocate&amp;nbsp;a minimum&amp;nbsp;2GB of memory for the ESXi kernel.&amp;nbsp; For example, if an ESXi server on B-200 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel you have 34GB available for the virtual machines.&amp;nbsp; The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case. <br /> :*VM coresidency with Unified Communications '''and''' third party applications (for example, WFM) is '''not''' supported unless it is described in the following subsection. <br /> :*On a '''C-Series''' server, the HDS '''cannot''' co-reside with a Router, Logger, or a PG.<br /> <br /> The following table shows how Unified CCE components can be coresident on the same ESXi server. A diamond indicates that coresidency is allowed. For example, the first row shows that Unified Communications Applications can not be colocated with Contact Center Tier 1 Applicaitons. The third row shows that Third Party Applications can only be colocated with Contact Center Tier 3 Applications. <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Unified CCE Component Coresidency <br /> ! Contact Center Tier 1 Applications <br /> ! Contact Center Tier 2 Applications <br /> ! Contact Center Tier 3 Applications <br /> ! Unified Communications Applications <br /> ! Third Party Applications<br /> |-<br /> | '''Contact Center Tier 1 Applications: Router, Logger, Peripheral Gateway, ADS-HDS''' <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | <br /> | <br /> |-<br /> | '''Contact Center Tier 2 Applications: CVP Call + VXML Server, CVP Reporting Server, CUIC, CCMP'''&amp;nbsp; <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | <br /> |-<br /> | '''Contact Center Tier 3 Applications: ADS/AW (any non-HDS), Admin&amp;nbsp;Client,&amp;nbsp;Support&amp;nbsp;Tools, Windows AD DC, CVP Ops/OAMP Server,&amp;nbsp;CVP Media Server, SocialMiner'''&amp;nbsp; <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦<br /> |-<br /> | '''Unified Communications Applications: Communications Manager, Contact Center Express,&amp;nbsp;IPIVR, CUP, Unity, Unity Connection, MediaSense'''&amp;nbsp; <br /> | align=&quot;center&quot; | <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | align=&quot;center&quot; | ♦ <br /> | <br /> |-<br /> | <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> {{note|If Cisco Support determines that a third party application deployed coresident with a Contact Center Tier 3 application causes that application to fail in performance or function, the customer must address the issue by moving the applications to other servers as necessary to alleviate the failure.}} <br /> <br /> For&amp;nbsp;coresidency restrictions specific to individual&amp;nbsp;Unified Communications applications that run on VMs, see the Unified Communications Virtualization Sizing Guideline docwiki. <br /> <br /> The following section depicts the CCE sample UCS&amp;nbsp;deployments&amp;nbsp;compliant to&amp;nbsp;the coresidency rules described above. <br /> <br /> == Sample CCE Deployments ==<br /> <br /> '''Notes''' <br /> <br /> #The ESXi Servers listed in these tables can be deployed on either a B-Series or C-Series hardware platform. <br /> #Although the sample deployments in these tables reflect the C-Series restriction that the HDS cannot coreside with a Router, Logger, or a PG, this restriction is '''not''' present on a B-Series hardware platform. <br /> #For deployments where Historical Data Servers (HDSs) are coresident, two RAID 5 groups (one for each HDS) are recommended. <br /> #Any deployment &amp;gt; 2k agents requires at least 2 chassis <br /> #It may be preferable to place your domain controller on bare metal rather than in the UCS B-series chassis itself. When a power failure occurs, the vCenter login credentials are dependent on Active Directory, leading to a potential chicken-and-egg problem if the domain controller is down as well. <br /> #ACE (for CUIC) and CUSP (for CVP) components are not supported virtualized on UCS; these components are deployed on separate hardware. Please review the product SRND for more details.<br /> <br /> === ROGGER Example 1 ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |+ ROGGER (up to 450 CTIOS Agents, or 297 CAD Agents) with 150 IPIVR or 150 CVP ports (N+N), optional 50 CUIC reporting users, as examples <br /> |-<br /> ! colspan=&quot;4&quot; | Chassis X (B series)/ Rack of C series rack mount Servers <br /> ! colspan=&quot;4&quot; | Chassis Y (B series)/ Rack of C series rack mount Servers<br /> |-<br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)''' <br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)'''<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-1 <br /> | Rogger A <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;4&quot; | ESXi Server B-1 &lt;br&gt;<br /> | Rogger B <br /> | 4 <br /> | 4<br /> |-<br /> | Agent PG A (generic PG w/ optional VRU), CTIOS/CAD, optional MR PG <br /> | 1 <br /> | 2 <br /> | Agent PG B (generic PG w/ optional VRU), CTIOS/CAD, optional MR PG <br /> | 1 <br /> | 2<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Domain Controller A <br /> | 1 <br /> | 2 <br /> | Domain Controller B <br /> | 1 <br /> | 2<br /> |-<br /> | style=&quot;background: rgb(255,224,200)&quot; | Support Tools&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 1 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 2 <br /> | CVP Op Svr <br /> | 2&lt;br&gt;<br /> | 2&lt;br&gt;<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-2 <br /> | AW-HDS-DDS 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-2 <br /> | AW-HDS-DDS 2 <br /> | 4 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | CUIC 1 <br /> | 4 <br /> | 6 <br /> | CUIC 2 <br /> | 4 <br /> | 6<br /> |-<br /> | rowspan=&quot;3&quot; | ESXi Server A-3 <br /> | UCM Subscriber 1 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;3&quot; | ESXi Server B-3 <br /> | UCM Subscriber 2 <br /> | 2 <br /> | 6<br /> |-<br /> | UCM Publisher <br /> | 2 <br /> | 6 <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | IPIVR 1 or CUP Srv 1 <br /> | 2 <br /> | 4 <br /> | IPIVR 2 or CUP Srv 2 <br /> | 2 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-4 <br /> | CVP Call+VXML Srv 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-4 <br /> | CVP Call+VXML Srv 2 <br /> | 4 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | CVP Rpt Srv 1 <br /> | 4 <br /> | 4 <br /> | CVP Media Server <br /> | 2 <br /> | 2<br /> |-<br /> ! colspan=&quot;8&quot; | '''Legend'''<br /> |-<br /> | Not shaded <br /> | colspan=&quot;7&quot; | Required<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Shaded <br /> | colspan=&quot;7&quot; | Optional<br /> |}<br /> <br /> === ROGGER Example 2 ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |+ ROGGER (up to 2,000 CTIOS Agents, or up to 1,000 CAD Agents) with 600 IPIVR or 900 CVP ports (N+N), optional 200 CUIC reporting users, CCMP 1,500 users, as examples <br /> |-<br /> ! colspan=&quot;4&quot; | Chassis X (B series)/ Rack of C series rack mount Servers <br /> ! colspan=&quot;4&quot; | Chassis Y (B series)/ Rack of C series rack mount Servers<br /> |-<br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)''' <br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)'''<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-1 <br /> | Rogger A <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;4&quot; | ESXi Server B-1 <br /> | Rogger B <br /> | 4 <br /> | 4<br /> |-<br /> | Agent PG A (generic PG w/ optional VRU, CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4 <br /> | Agent PG B (generic PG w/ optional VRU, CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Domain Controller A <br /> | 1 <br /> | 2 <br /> | Domain Controller B <br /> | 1 <br /> | 2<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Support Tools&lt;br&gt;<br /> | 1&lt;br&gt;<br /> | 2&lt;br&gt;<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-2 <br /> | AW-HDS-DDS 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-2 <br /> | AW-HDS-DDS 2 <br /> | 4 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | AW-HDS-DDS 3&amp;nbsp; <br /> | 4 <br /> | 4 <br /> | AW-HDS-DDS 4&amp;nbsp; <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-3 &lt;br&gt;<br /> | UCM Subscriber 1 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;4&quot; | ESXi Server B-3 &lt;br&gt;<br /> | UCM Subscriber 3 <br /> | 2 <br /> | 6<br /> |-<br /> | UCM Subscriber 2&lt;br&gt;<br /> | 2 <br /> | 6 <br /> | UCM Subscriber 4&lt;br&gt;<br /> | 2&lt;br&gt;<br /> | 6&lt;br&gt;<br /> |-<br /> | UCM Publisher <br /> | 2&lt;br&gt;<br /> | 6&lt;br&gt;<br /> | CVP Op Srv &lt;br&gt;<br /> | 2&lt;br&gt;<br /> | 2&lt;br&gt;<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | IPIVR 1 or CUP Srv 1&lt;br&gt;<br /> | 2&lt;br&gt;<br /> | 4&lt;br&gt;<br /> | IPIVR 2 or CUP Srv 2&lt;br&gt;<br /> | 2&lt;br&gt;<br /> | 4&lt;br&gt;<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-4 <br /> | CVP Call+VXML Srv 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-4 <br /> | CVP Call+VXML Srv 2 <br /> | 4 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | CVP Rpt Srv 1 <br /> | 4 <br /> | 4 <br /> | CVP Rpt Srv 2 <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-5 &lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CUIC1 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 6&lt;br&gt;<br /> | rowspan=&quot;2&quot; | ESXi Server B-5 &lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CCMP (all in one) <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | CVP Media Server <br /> | 2 <br /> | 2 <br /> | CUIC 2 <br /> | 4 <br /> | 6<br /> |-<br /> ! colspan=&quot;8&quot; | '''Legend'''<br /> |-<br /> | Not shaded <br /> | colspan=&quot;7&quot; | Required<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Shaded <br /> | colspan=&quot;7&quot; | Optional<br /> |}<br /> <br /> === ROGGER Example 3 ===<br /> <br /> {| style=&quot;width: 1057px; height: 574px&quot; class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |+ ROGGER (up to 4,000 CTIOS Agents, or up to 2,000 CAD Agents) with 1,200 IPIVR or 1,800 CVP ports (N+N), optional 200 CUIC reporting users, CCMP 1,500 users, as examples <br /> |-<br /> ! colspan=&quot;4&quot; | Chassis X (B series)/ Rack of C series rack mount Servers <br /> ! colspan=&quot;4&quot; | Chassis Y (B series)/ Rack of C series rack mount Servers<br /> |-<br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)''' <br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)'''<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-1 <br /> | Rogger A <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-1 <br /> | Rogger B <br /> | 4 <br /> | 4<br /> |-<br /> | Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4 <br /> | Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-2 &lt;br&gt;<br /> |-<br /> | VRU PG A <br /> | 2 <br /> | 2 <br /> | rowspan=&quot;3&quot; | ESXi Server B-2 &lt;br&gt;<br /> | VRU PG B&lt;br&gt;<br /> | 2 <br /> | 2<br /> |-<br /> | style=&quot;background: rgb(255,224,200)&quot; | Support Tools&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 1&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 2&lt;br&gt;<br /> | CVP Op Srv <br /> | 2&lt;br&gt;<br /> | 2&lt;br&gt;<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Domain Controller A&amp;nbsp; <br /> | 1 <br /> | 2 <br /> | Domain Controller B&amp;nbsp; <br /> | 1 <br /> | 2<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-3 <br /> | width=&quot;145&quot; | Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-2 &lt;br&gt;&lt;br&gt;<br /> | Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | width=&quot;145&quot; | 2 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | CVP Rpt Srv 1 <br /> | 4 <br /> | 4 <br /> | CVP Rpt Srv 2 <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-4 <br /> | AW-HDS-DDS 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-3 <br /> | AW-HDS-DDS 2 <br /> | 4 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | AW-HDS-DDS 3&amp;nbsp; <br /> | 4 <br /> | 4 <br /> | AW-HDS-DDS 4&amp;nbsp; <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-5 <br /> | UCM Subscriber 1 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;4&quot; | ESXi Server B-4 <br /> | UCM Subscriber 2 <br /> | 2 <br /> | 6<br /> |-<br /> | UCM Subscriber 3 <br /> | 2 <br /> | 6 <br /> | UCM Subscriber 4 <br /> | 2 <br /> | 6<br /> |-<br /> | UCM Publisher <br /> | 2 <br /> | 6 <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | IPIVR 1 <br /> | 2 <br /> | 4 <br /> | IPIVR 3 <br /> | 2 <br /> | 4<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-6 <br /> | UCM Subscriber 5 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;4&quot; | ESXi Server B-5 <br /> | UCM Subscriber 6 <br /> | 2 <br /> | 6<br /> |-<br /> | UCM Subscriber 7 <br /> | 2 <br /> | 6 <br /> | UCM Subscriber 8 <br /> | 2 <br /> | 6<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | IPIVR 2&amp;nbsp; <br /> | 2 <br /> | 4 <br /> | IPIVR 4&amp;nbsp; <br /> | 2 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | CUP Server 1&amp;nbsp; <br /> | 2 <br /> | 4 <br /> | CUP Server 2&amp;nbsp; <br /> | 2 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-7 <br /> | CVP Call+VXML Srv 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-5 <br /> | CVP Call+VXML Srv 2 <br /> | 4 <br /> | 4<br /> |-<br /> | CVP Call+VXML Srv 3 <br /> | 4 <br /> | 4 <br /> | CVP Call+VXML Srv 4 <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-7 &lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CVP Media Server <br /> | style=&quot;background: rgb(255,224,200)&quot; | 2 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 2 <br /> | rowspan=&quot;2&quot; | ESXi Server B-6 &lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CUIC 2 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 6<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | CUIC 1 <br /> | 4 <br /> | 6 <br /> | CCMP (all in one) <br /> | 4 <br /> | 4<br /> |-<br /> | colspan=&quot;9&quot; | &lt;br&gt;<br /> |-<br /> | Not shaded <br /> | colspan=&quot;7&quot; | Required<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Shaded <br /> | colspan=&quot;7&quot; | Optional<br /> |}<br /> <br /> === Router/Logger Example 1 ===<br /> <br /> {| style=&quot;width: 1057px; height: 574px&quot; class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |+ Router/Logger (up to 8,000 CTIOS Agents, or up to 4,000 CAD Agents) with 3,600 CVP ports (N+N), optional 400 CUIC reporting users, CCMP 8,000 users, as examples <br /> |-<br /> ! colspan=&quot;4&quot; | Chassis X (B series)/ Rack of C series rack mount Servers <br /> ! colspan=&quot;4&quot; | Chassis Y (B series)/ Rack of C series rack mount Servers<br /> |-<br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)''' <br /> | '''ESXi Server''' <br /> | '''Component''' <br /> | '''#vCPU''' <br /> | '''RAM (GB)'''<br /> |-<br /> | rowspan=&quot;5&quot; | ESXi Server A-1 <br /> | width=&quot;145&quot; | Router A <br /> | 2 <br /> | 4 <br /> | rowspan=&quot;5&quot; | ESXi Server B-1 <br /> | width=&quot;145&quot; | Router B <br /> | 2 <br /> | 4<br /> |-<br /> | width=&quot;145&quot; | Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4 <br /> | width=&quot;145&quot; | Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4<br /> |-<br /> | width=&quot;145&quot; | Agent PG 3A (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4 <br /> | width=&quot;145&quot; | Agent PG 3B (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | width=&quot;145&quot; | Domain Controller A&amp;nbsp; <br /> | 1 <br /> | 2 <br /> | width=&quot;145&quot; | Domain Controller B&amp;nbsp; <br /> | 1 <br /> | 2<br /> |-<br /> | style=&quot;background: rgb(255,224,200)&quot; | Support Tools&amp;nbsp; <br /> | style=&quot;background: rgb(255,224,200)&quot; | 1 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 2 <br /> | width=&quot;145&quot; | &amp;nbsp; <br /> | &amp;nbsp; <br /> | &amp;nbsp;<br /> |-<br /> | rowspan=&quot;3&quot; | ESXi Server A-2 <br /> | width=&quot;145&quot; | Logger A <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;3&quot; | ESXi Server B-2 <br /> | width=&quot;145&quot; | Logger B <br /> | 4 <br /> | 4<br /> |-<br /> | width=&quot;145&quot; | Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4 <br /> | width=&quot;145&quot; | Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4<br /> |-<br /> | width=&quot;145&quot; | Agent PG 4A (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4 <br /> | width=&quot;145&quot; | Agent PG 4B (CTIOS/CAD, optional MR PG, SIP Dialer) <br /> | 2 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-3 <br /> | width=&quot;145&quot; | HDS-DDS 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-3 <br /> | width=&quot;145&quot; | HDS-DDS 2 <br /> | 4 <br /> | 4<br /> |-<br /> | width=&quot;145&quot; | AW-HDS 1 <br /> | 4 <br /> | 4 <br /> | width=&quot;145&quot; | AW-HDS 2 <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | AW-HDS 3&amp;nbsp; <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | AW-HDS 4&amp;nbsp; <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | width=&quot;145&quot; | AW-HDS 5&amp;nbsp; <br /> | 4 <br /> | 4 <br /> | width=&quot;145&quot; | AW-HDS 6&amp;nbsp; <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-5 <br /> | width=&quot;145&quot; | UCM 1 Subscriber 1 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;4&quot; | ESXi Server B-5 <br /> | width=&quot;145&quot; | UCM 1 Subscriber 2 <br /> | 2 <br /> | 6<br /> |-<br /> | width=&quot;145&quot; | UCM 2 Subscriber 1 <br /> | 2 <br /> | 6 <br /> | width=&quot;145&quot; | UCM 2 Subscriber 2 <br /> | 2 <br /> | 6<br /> |-<br /> | width=&quot;145&quot; | UCM 1 Subscriber 3 <br /> | 2 <br /> | 6 <br /> | width=&quot;145&quot; | UCM 1 Subscriber 4 <br /> | 2 <br /> | 6<br /> |-<br /> | width=&quot;145&quot; | UCM 2 Subscriber 3 <br /> | 2 <br /> | 6 <br /> | width=&quot;145&quot; | UCM 2 Subscriber 4 <br /> | 2 <br /> | 6<br /> |-<br /> | rowspan=&quot;4&quot; | ESXi Server A-6 <br /> | width=&quot;145&quot; | UCM 1 Subscriber 5 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;4&quot; | ESXi Server B-6 <br /> | width=&quot;145&quot; | UCM 1 Subscriber 6 <br /> | 2 <br /> | 6<br /> |-<br /> | width=&quot;145&quot; | UCM 2 Subscriber 5 <br /> | 2 <br /> | 6 <br /> | width=&quot;145&quot; | UCM 2 Subscriber 6 <br /> | 2 <br /> | 6<br /> |-<br /> | width=&quot;145&quot; | UCM 1 Subscriber 7 <br /> | 2 <br /> | 6 <br /> | width=&quot;145&quot; | UCM 1 Subscriber 8 <br /> | 2 <br /> | 6<br /> |-<br /> | width=&quot;145&quot; | UCM 2 Subscriber 7 <br /> | 2 <br /> | 6 <br /> | width=&quot;145&quot; | UCM 2 Subscriber 8 <br /> | 2 <br /> | 6<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-7 &lt;br&gt;<br /> | width=&quot;145&quot; | UCM Publisher 1 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;2&quot; | ESXi Server B-7 &lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CVP Op Srv <br /> | style=&quot;background: rgb(255,224,200)&quot; | 2 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 2<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | width=&quot;145&quot; | CUP Server 1&amp;nbsp; <br /> | 2 <br /> | 4 <br /> | width=&quot;145&quot; | CUP Server 2&amp;nbsp; <br /> | 2 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-8 <br /> | width=&quot;145&quot; | UCM Publisher 2 <br /> | 2 <br /> | 6 <br /> | rowspan=&quot;2&quot; | ESXi Server B-8 <br /> | style=&quot;background: rgb(255,224,200)&quot; | CVP Rpt Srv 2 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4<br /> |-<br /> | style=&quot;background: rgb(255,224,200)&quot; | CVP Rpt Srv 1 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | width=&quot;145&quot; | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-9 <br /> | width=&quot;145&quot; | CVP Call+VXML Srv 1 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-9 <br /> | width=&quot;145&quot; | CVP Call+VXML Srv 2 <br /> | 4 <br /> | 4<br /> |-<br /> | width=&quot;145&quot; | CVP Call+VXML Srv 3 <br /> | 4 <br /> | 4 <br /> | width=&quot;145&quot; | CVP Call+VXML Srv 4 <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-10 <br /> | width=&quot;145&quot; | CVP Call+VXML Srv 5 <br /> | 4 <br /> | 4 <br /> | rowspan=&quot;2&quot; | ESXi Server B-10 <br /> | width=&quot;145&quot; | CVP Call+VXML Srv 6 <br /> | 4 <br /> | 4<br /> |-<br /> | width=&quot;145&quot; | CVP Call+VXML Srv 7 <br /> | 4 <br /> | 4 <br /> | width=&quot;145&quot; | CVP Call+VXML Srv 8 <br /> | 4 <br /> | 4<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-11 <br /> | style=&quot;background: rgb(255,224,200)&quot; | CVP Media Server A&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 2&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 2&lt;br&gt;<br /> | rowspan=&quot;2&quot; | ESXi Server B-11 &lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CVP Media Server B&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 2&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | 2&lt;br&gt;<br /> |-<br /> | VRU PG A&lt;br&gt;<br /> | 2&lt;br&gt;<br /> | 2&lt;br&gt;<br /> | VRU PG B&lt;br&gt;<br /> | 2&lt;br&gt;<br /> | 2&lt;br&gt;<br /> |-<br /> | rowspan=&quot;2&quot; | ESXi Server A-12 <br /> | style=&quot;background: rgb(255,224,200)&quot; | CUIC 1&amp;nbsp; <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 6 <br /> | rowspan=&quot;2&quot; | ESXi Server B-12&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CUIC 2&amp;nbsp; <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 6<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | width=&quot;145&quot; | CUIC 3&amp;nbsp; <br /> | 4 <br /> | 6 <br /> | width=&quot;145&quot; | CUIC 4&amp;nbsp; <br /> | 4 <br /> | 6<br /> |-<br /> | ESXi Server A-13&lt;br&gt;<br /> | style=&quot;background: rgb(255,224,200)&quot; | CCMP DB&amp;nbsp; <br /> | style=&quot;background: rgb(255,224,200)&quot; | 8 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | ESXi Server B-13 <br /> | style=&quot;background: rgb(255,224,200)&quot; | CCMP Web/App Svr&amp;nbsp; <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4 <br /> | style=&quot;background: rgb(255,224,200)&quot; | 4<br /> |-<br /> ! colspan=&quot;8&quot; | '''Legend'''<br /> |-<br /> | Not shaded <br /> | colspan=&quot;7&quot; | Required<br /> |- style=&quot;background: rgb(255,224,200)&quot;<br /> | Shaded <br /> | colspan=&quot;7&quot; | Optional<br /> |}<br /> <br /> = Hybrid Deployment Options =<br /> <br /> Some Unified Contact Center deployments are supported in a &quot;hybrid&quot; fashion whereby certain components must be deployed on (bare-metal) Media Convergence Servers (MCS) or generic servers, and other components are deployed in virtual machine guests on Unified Computing System (UCS) or MCS servers. The following sub-sections provide further details on these hybrid deployment options. <br /> <br /> == Cisco Unified Contact Center Hosted ==<br /> <br /> *NAM Rogger is deployed on a (bare-metal) quad CPU server as specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).] <br /> *Each customer instance central controller (CICM) connecting to the NAM may be deployed in its own virtual machine as a Rogger or separate Router/Logger pair on UCS hardware. Multiple CICM instances are not supported collocated in one VM. Existing published rules and capacities apply to CICM Rogger and Router/Logger VMs. (Note: CICMs are not supported on bare-metal UCS.) <br /> *As in Enterprise deployments, each Agent PG is deployed in its own virtual machine. Multi-instance Agent PGs are not supported in a single VM. Existing published rules and capacities apply to PGs in Hosted deployments.<br /> <br /> == Parent/Child Deployments ==<br /> <br /> *The parent ICM is deployed on (bare-metal) servers as specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).]. <br /> *The Unified Contact Center Enterprise (or Express) child may be deployed virtualized according to existing published VM requirements. <br /> *The Unified Contact Center Enterprise Gateway PG and System PG are each deployed in its own virtual machine; agent capacity (and resources allocated to the VM) are the same as the Unified CCE Agent PG @ 2,000 agent capacity. Use the same virtual machine OVA template to create the CCE Gateway or System PG VM.<br /> <br /> = Cisco Unified CCE-Specific Information for OVA Templates =<br /> <br /> See the following websites for more information:&lt;br&gt;<br /> <br /> *[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Contact_Center_Enterprise Unified Communications Virtualization Downloads (including OVA/OVF Templates).] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=268439622&amp;release=1.1&amp;relind=AVAILABLE&amp;flowid=5210&amp;softwareid=283914286&amp;rellifecycle=&amp;reltype=latest Unified CCE OVA Templates]<br /> <br /> &lt;br&gt;<br /> <br /> == Creating Virtual Machines by Deploying the OVA Templates ==<br /> <br /> In the vSphere client, perform the following steps to deploy the Virtual machines. <br /> <br /> #Highlight the host or cluster to which you wish the VM to be deployed. <br /> #Select '''File''' &amp;gt; '''Deploy OVF Template'''. <br /> #Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''OR '''click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''. <br /> #Verify the details of the template, and click '''Next'''. <br /> #Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''. <br /> #Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''. <br /> #Choose a virtual network for the VM, then click '''Next'''. <br /> #Verify the deployment settings, then click '''Finish'''.<br /> <br /> == Notes ==<br /> <br /> :*VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Unified CCE applications on the VMware ESXi on UCS platform. <br /> :*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CCE applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. <br /> :*You cannot change the computing resource configuration of your VM at any time. <br /> :*You can never go below the minimum VM computing resource requirements as defined in the OVA templates. <br /> :*ESXi Server hyperthread is enabled by default.<br /> <br /> == Preparing for Windows Installation ==<br /> <br /> In the vSphere client, perform the following steps to prepare for operating system installation. <br /> <br /> #Right click on the virtual machine you want to edit and select '''Edit Settings'''. A Virtual Machine Properties dialog appears. <br /> #On the Hardware tab, select '''CD/DVD Drive 1'''. Under Device Type, select '''Datastore ISO File''' and enter the location of the operating system ISO. <br /> #Click '''OK''' to save setting changes. <br /> #Power up your VM and continue with operating system installation.<br /> <br /> &lt;br&gt;<br /> <br /> = Remote Control of the Virtual Machines =<br /> <br /> For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. The contact center supervisor can access the ClientAW VM using Windows Remote Desktop. <br /> <br /> = Installing VMware Tools =<br /> <br /> The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to VMware documentation for instructions on installing or upgrading VMware Tools on the VM with Windows operating system. <br /> <br /> = Installing Unified CCE Components on Virtual Machines =<br /> <br /> Install the Unified CCE components after you create and configure the virtual machine. Installation of the Unified CCE components on a virtual machine is the same as the installation of the components on physical hardware. <br /> <br /> Refer to the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html Unified CCE documentation] for the steps to install Unified CCE components. You can install the supported Virus Scan software, the Cisco Security Agent(CSA), or any other software in the same way as on physical hardware. <br /> <br /> = Migrating Unified CCE Components to Virtual Machines =<br /> <br /> Migrate the Unified CCE components from physical hardware or another virtual machine after you create and configure the virtual machine. Migration of these Unified CCE software components to a VM is the same as the migration of the components to new physical hardware and follows existing policies. It requires a Tech Refresh as described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/installation/guide/icm80ug.pdf Upgrade Guide for Cisco Unified ICM/Contact Center Enterprise &amp;amp; Hosted Release 8.0(1)]. <br /> <br /> = Configuring the ESXi Data Store Block Size for Administration and Data Server =<br /> <br /> This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks (3-10) are RAID 5. <br /> <br /> The creation of the virtual machine for the Unified CCE Administration and Data Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store block size to 2MB for it to handle the Unified CCE Administration and Data Server virtual disk size requirement before you deploy the OVAs for the following Unified CCE components: <br /> <br /> :*AW-HDS <br /> :*AW-HDS-DDS <br /> :*HDS-DDS<br /> <br /> &lt;br&gt;Steps to configure the ESXi data store block size to 2MB: <br /> <br /> #After you install ESXi on the first disk array group (RAID 1 with disk 1 and disk 2), boot ESXi 4.0 and use VMware vSphere Client to connect to the ESXi host. <br /> #On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB. <br /> #Right-click on this data store and delete it. We will add the data store back in the following steps. <br /> #Click on the “Add Storage…” and select the Disk/LUN. <br /> #The data store that was just deleted will now be available to add, select it. <br /> #In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.<br /> <br /> = Timekeeping Best Practices for Windows =<br /> <br /> You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1318 VMware KB: Timekeeping best practices for Windows]. <br /> <br /> *ESXi hosts and domain controllers should synchronize the time from the same NTP source. <br /> *When Unified CCE virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time. <br /> *Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.<br /> <br /> = System Performance Monitoring Using ESXi Counters =<br /> <br /> :*Make sure that you&amp;nbsp;follow VMware's ESXi best practices and SAN vendor's best practices for optimal system performance.&amp;nbsp; <br /> :*VMware provides a set of system monitoring tools for the ESXi platform and the VMs. These tools are accessible through the VMware Infrastructure Client or through VirtualCenter. <br /> :*You can use Windows Performance Monitor to monitor the performance of the VMs. Be aware that the CPU counters may not reflect the physical CPU usage since the Windows Operating System has no direct access to the physical CPU. <br /> :*You can use&amp;nbsp;Unified CCE Serviceability Tools and&amp;nbsp;Unified CCE reports to monitor the operation and performance of the&amp;nbsp;Unified CCE system. <br /> :*The ESXi Server and the virtual machines must operate within the limit of the following ESXi performance counters.<br /> <br /> You can use the following ESXi counters as performance indicators. <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Category <br /> ! Object <br /> ! Measurement <br /> ! Units <br /> ! Description <br /> ! Performance Indication and Threshold<br /> |-<br /> | CPU <br /> | <br /> :*ESXi Server <br /> :*VM<br /> <br /> | CPU Usage (Average) <br /> | Percent <br /> | CPU Usage Average in percentage for: <br /> :*ESXi server <br /> :*Virtual machine<br /> <br /> | Less than 60%.<br /> |-<br /> | CPU <br /> | <br /> :*ESXi Server Processor# <br /> :*VM_vCPU#<br /> <br /> | CPU Usage 0 - 7 (Average) <br /> | Percent <br /> | CPU Usage Average for: <br /> :*ESXi server for processors 0 to 7 <br /> :*Virtual machine vCPUs<br /> <br /> | Less than 60%<br /> |-<br /> | CPU <br /> | VM <br /> | CPU Ready <br /> | mSec <br /> | The time a virtual machine or other process waits in the queue in a ready-to-run state before it can be scheduled on a CPU. <br /> | Less than 150 mSec. If it is greater than 150 mSec doing system failure, you should investigate and understand why the machine is so busy.<br /> |-<br /> | Memory <br /> | <br /> :*ESXi Server <br /> :*VM<br /> <br /> | Memory Usage (Average) <br /> | Percent <br /> | Memory Usage = Active/ Granted * 100 <br /> | Less than 80%<br /> |-<br /> | Memory <br /> | <br /> :*ESXi Server <br /> :*VM<br /> <br /> | Memory Active&amp;nbsp;(Average) <br /> | KB <br /> | Memory that is actively used or being referenced by the guest OS and its applications. When it exceeds the amound of memory on the host, the server starts swap. <br /> | Less than 80% of the Granted memory<br /> |-<br /> | Memory <br /> | <br /> :*ESXi Server <br /> :*VM<br /> <br /> | Memory Balloon (Average) <br /> | KB <br /> | ESXi use balloon driver to recover memory from less memory-intensive VMs so it can be used by those with larger active sets of memory. <br /> | Since we do not over commit the memory, this should be 0 or very low. Note: ESXi performs memory ballooning before memory swap.<br /> |-<br /> | Memory <br /> | <br /> :*ESXi Server <br /> :*VM<br /> <br /> | Memory Swap used (Average) <br /> | KB <br /> | ESXi Server swap usage. Use the disk for RAM swap <br /> | Since we do&amp;nbsp;not over commit the memory,&amp;nbsp;this should be 0 or very low<br /> |-<br /> | Disk <br /> | <br /> :*ESXi Server <br /> :*VM<br /> <br /> | Disk Usage (Average) <br /> | KBps <br /> | Disk Usage = Disk Read rate + Disk Write rate <br /> | Ensure that your SAN is configured to handle&amp;nbsp;this amount of disk I/O.<br /> |-<br /> | Disk <br /> | <br /> :*ESXi Server vmhba ID <br /> :*VMbha ID<br /> <br /> | Disk Usage Read&amp;nbsp;rate&amp;nbsp; <br /> | KBps <br /> | Rate of reading data from the disk <br /> | Ensure that your SAN is configured to handle this amount of disk I/O<br /> |-<br /> | Disk <br /> | <br /> :*ESXi Server vmhba ID <br /> :*VM vmhba ID<br /> <br /> | Disk Usage Write rate <br /> | KBps <br /> | Rate of writing data to the disk <br /> | Ensure that your SAN is configured to handle&amp;nbsp;this amount of disk I/O<br /> |-<br /> | Disk <br /> | <br /> :*ESXi Server vmhba ID <br /> :*VM vmhba ID<br /> <br /> | Disk Commands Issued <br /> | Number <br /> | Number of disk commands issued on this disk in the period. <br /> | Ensure that your SAN is configured to handle&amp;nbsp;this amount of disk I/O<br /> |-<br /> | Disk <br /> | <br /> :*ESXi Server vmhba ID <br /> :*VM vmhba ID<br /> <br /> | Disk Command Aborts <br /> | Number <br /> | Number of disk commands&amp;nbsp;aborted on this disk in the period. Disk command aborts when the disk array is taking too long to respond to the command. (Command timeout) <br /> '''This counter should be zero. A non-zero value indicates storage performance issue.'''<br /> <br /> |-<br /> | Disk <br /> | <br /> :*ESXi Server vmhba ID <br /> :*VM vmhba ID<br /> <br /> | Disk Command Latency <br /> | mSec <br /> | The average amount of time taken for a command from the perspective of a Gust OS. Disk Command Latency = Kernel Command Latency + Physical Device Command Latency. <br /> | '''15ms latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array.'''<br /> |-<br /> | Disk <br /> | <br /> :*ESXi Server vmhba ID <br /> :*VM vmhba ID<br /> <br /> | Kernel Disk Command Latency <br /> | mSec <br /> | The average time spent in ESXi Server VMKernel per command <br /> | '''Kernel Command Latency should be very small in comparison to the Physical Device Command Latency, and it should be close to zero.&amp;nbsp; Kernel Command Latency can be high, or even higher than the Physical Device Command Latency if there is a lot of queuing in the ESXi kernel.'''<br /> |-<br /> | Network <br /> | <br /> :*ESXi Server <br /> :*VM<br /> <br /> | Network Usage (Average) <br /> | KBps <br /> | Network Usage = Data receive rate + Data transmit rate <br /> | Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.<br /> |-<br /> | Network <br /> | <br /> :*ESXi Server vmnic ID <br /> :*VM&amp;nbsp;vmnic ID<br /> <br /> | Network Data Receive Rate <br /> | KBps <br /> | Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.<br /> |-<br /> | Network <br /> | <br /> :*ESXi Server vmnic ID <br /> :*VM&amp;nbsp;vmnic ID<br /> <br /> | Network Data Transmit Rate <br /> | KBps <br /> | The average rate at which data is transmitted on this Ethernet port <br /> | Less than 30% of the available network bandwidth. &amp;nbsp;For example, it should be less than 300Mps for 1G network.<br /> |}<br /> <br /> = System Performance Monitoring Using Windows Perfmon Counters =<br /> <br /> You must comply with the best practices described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design(SRND), Release 8.0] section System Performance Monitoring, and in Chapter 8 Performance Counters in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/configuration/guide/icm80srvg.pdf Serviceability Best Practices Guide for Unified ICM/Contact Center Enterprise]. <br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}<br /> <br /> [[Category:Unified_Contact_Center_Enterprise]]</div>

Cchetty http://docwiki.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager 2011-10-10T16:42:20Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Updates to this Page ==<br /> <br /> The following is a list of significant updates to this page: <br /> <br /> &lt;br&gt; <br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Date <br /> ! Update<br /> |-<br /> | April 06 2011 <br /> | Initial version of virtualization information for Cisco Unified EIM-WIM<br /> |}<br /> <br /> &lt;br&gt; <br /> <br /> == Information for Partners about Cisco Unified EIM-WIM Deployment Certification and Ordering ==<br /> <br /> This page contains essential information for partners about the following: <br /> <br /> *Partner Certification Requirements <br /> *UCS Server Ordering Information <br /> *Important Notes on Cisco UCS Service and Support<br /> <br /> Please visit following page for more details http://docwiki.cisco.com/wiki/Unified_Communications_in_a_Virtualized_Environment<br /> <br /> == Cisco Unified EIM-WIM , Release 4.3(2) Support for Virtualization on the ESXi/UCS Platform ==<br /> <br /> Starting with Release 4.3(2), virtualization of Cisco Unified EIM-WIM on Cisco Unified Computing Systems(UCS)is supported B series models.To know about specific models please visit the following link http://docwiki-dev.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications <br /> <br /> == UCS Hardware Requirements ==<br /> <br /> Requirements for Cisco Unified EIM-WIM systems using UCS B200 M2 hardware are located [http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware#B-200_M1_Requirements here]. <br /> <br /> == VMware and Application Software Requirements ==<br /> <br /> The following software requirements apply specifically to Cisco Unified EIM-WIM&amp;nbsp;: <br /> <br /> *EIM-WIM support ESX 4.0U1 and subsequent updates and ESXi 4.1.<br /> <br /> == Configuring the ESXi Host Network for the Virtual Machines ==<br /> <br /> To configure the network for VMs, you create a virtual switch connected to an Ethernet port on the server, and then associate the virtual machine's network adapter to this virtual switch. To Add a vSwitch <br /> <br /> *Login to the ESXi host using VMware Infrastructure Client <br /> *Select the ESXi host <br /> *Click on the Configuration tab <br /> *Click on Hardware/Networking <br /> *Click on Add Networking... <br /> *Select Connection Types: Virtual Machine. Click Next. <br /> *Select &quot;Create a virtual switch&quot; and select an associated VM NIC. <br /> *Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: &quot;VM Network 1&quot;) <br /> *Click on Finish.<br /> <br /> To Associate a VM Network Adapter to Network Connection <br /> <br /> *Edit virtual machine settings. <br /> *Select the Network Adapter. <br /> *Select a virtual switch from the Network Connection/network label. (Example: &quot;VM Network 1&quot;) <br /> *Click OK. <br /> *Click on Hardware/Networking <br /> *Click on Add Networking... <br /> *Select Connection Types: Virtual Machine. Click Next. <br /> *Select &quot;Create a virtual switch&quot; and select an associated VM NIC. <br /> *Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: &quot;VM Network 1&quot;) <br /> *Click on Finish.<br /> <br /> To Associate a VM Network Adapter to Network Connection <br /> <br /> *Edit virtual machine settings. <br /> *Select the Network Adapter. <br /> *Select a virtual switch from the Network Connection/network label. (Example: &quot;VM Network 1&quot;) <br /> *Click OK.<br /> <br /> &lt;br&gt; <br /> <br /> &lt;br&gt; <br /> <br /> == Installing Cisco Unified EIM-WIM components on Virtual Machines ==<br /> <br /> Follow the steps and references below to install OR migrate the Cisco Unified EIM-WIM components on Virtual Machines. <br /> <br /> *Install setup and configure the UCS Hardware <br /> *Configure the UCS Network. Follow the link [[Unified Communications VMWare Requirements]]. <br /> *Install and Boot VMWare ESXi. Refer to the following installation guide: [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html|Cisco UCS B-Series Blade Servers VMware Installation Guide.] <br /> *Create Cisco Unified EIM-WIM Virtual Machines from the OVA template. OVA templates are available on Cisco.com.<br /> <br /> == Creating Virtual Machines from OVA VM Template ==<br /> <br /> Please follow below link for Unified Communications Virtualization Downloads (including OVA/OVF Templates) for more information. <br /> <br /> http://docwiki-dev.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29 <br /> <br /> == Downloading OVA Template ==<br /> <br /> :*Proceed to the [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&amp;flowid=5224&amp;softwareid=283929858&amp;release=1.0&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=latest Release 4.3(2) Cisco download page].<br /> <br /> :*To download a OVA file, click the '''Download File''' button next to that file. click the '''Add to Cart''' button next to file, then click on the '''Download Cart''' link. A Download Cart page appears.<br /> <br /> :*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.<br /> <br /> :*Read the Software License Agreement, then click the '''Agree''' button<br /> <br /> :*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.<br /> <br /> :*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.<br /> <br /> :*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.<br /> <br /> == Creating Virtual Machines by Deploying the OVA Templates ==<br /> <br /> In the vSphere client, perform the following steps to deploy the Virtual machines. <br /> <br /> *Highlight the host or cluster to which you wish the VM to be deployed. <br /> *Select File &amp;gt; Deploy OVF Template. <br /> *Click the Deploy from File radio button and specify the name and location of the file you downloaded in the previous section OR click the Deploy from URL radio button and specify the complete URL in the field, then click Next. <br /> *Verify the details of the template, and click Next. <br /> *Give the VM you are about to create a name, and choose an inventory location on your host, then click Next. <br /> *Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click Next. <br /> *Choose a virtual network for the VM, then click Next. <br /> *Verify the deployment settings, then click Finish.<br /> <br /> Note: <br /> <br /> *VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Cisco Unified EIM-WIM applications on the VMware ESXi on UCS platform. <br /> *VM resource Reservation - VM resource reservation is not supported for the VMs that are running Cisco Unified EIM-WIM applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations. <br /> *You cannot change the computing resource configuration of your VM at any time. <br /> *You can never go below the minimum VM computing resource requirements as defined in the OVA templates. <br /> *ESXi Server hyperthread is enabled by default.<br /> <br /> &lt;br&gt; <br /> <br /> == Cisco Unified EIM-WIM Component Capacities and VM Configuration Requirements ==<br /> <br /> This table shows the supported Cisco Unified EIM-WIM components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Cisco Unified EIM-WIM component VMs. <br /> <br /> Note: For Virtual Machines that need more than 4 vCPUs, the VMware vSphere ESXi Enterprise Plus licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.) <br /> <br /> For different sizing configuration , please refer [http://docwiki-dev.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates) here]&lt;br&gt;<br /> <br /> == Cisco Unified EIM-WIM Component Co-Residency ==<br /> <br /> You can have one or more EIM-WIM components co-resident on the same ESXi server. However, you must follow the rules described below: <br /> <br /> 1)DB server component for capacity above 360 agents is not co-resident with any other EIM-WIM or other applications - Requires its own blade. <br /> <br /> 2)Co-Residency of EIM-WIM components with UC applications and other third party application is not supported <br /> <br /> 3)You can have any number of EIM-WIM virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources. <br /> <br /> 4) You must not have CPU overcommitted on the ESXi server that is running EIM-WIM components . The total number of vCPUs among all the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server. In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8. <br /> <br /> 5)You must not have memory overcommitted on the ESXi host that is running UC realtime applications. You must allocate minimum 2GB of memory for the ESXi kernel. For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines. The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.<br /> <br /> == Performance Requirements ==<br /> <br /> CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. Memory usage (average) should not exceed 80%x for the ESXi Server and for each of the VMs. VM snapshots are not supported in production since they have significant impact on system performance. <br /> <br /> &lt;br&gt; The data is collected from the test run of 200 users working on Email, 200 users working on Chat and 200 more working on Blended Collaboration activities (Total of 600 agents). Email activities were processing at 12 per hour per agent and Chat and Blended Collaboration activities were processed at the rate of 10 per hour per agent. &lt;br&gt; <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! rowspan=&quot;2&quot; | EIM-WIM Components <br /> ! colspan=&quot;3&quot; | IOPS <br /> ! colspan=&quot;3&quot; | Disk Read KBytes / sec <br /> ! colspan=&quot;3&quot; | Disk Write KBytes / sec<br /> |-<br /> | '''Peak''' <br /> | '''95th Pct.''' <br /> | '''Avg.''' <br /> | '''Peak''' <br /> | '''95th Pct.''' <br /> | '''Avg.''' <br /> | '''Peak''' <br /> | '''95th Pct.''' <br /> | '''Avg.''' <br /> &lt;br&gt; <br /> <br /> |-<br /> | Application Server <br /> | 11.7 <br /> | 3.21<br /> | 1.55 <br /> | 51 <br /> | 1 <br /> | 0.726 <br /> | 103 <br /> | 19<br /> | 8.32<br /> |-<br /> | File Server <br /> | 43.65 <br /> | 25.23<br /> | 14.36 <br /> | 189 <br /> | 2 <br /> | 2 <br /> | 1769<br /> | 1025.9 <br /> | 446<br /> |-<br /> | Database Server <br /> | 736.9 <br /> | 552 <br /> | 263.31<br /> | 35450<br /> | 23184 <br /> | 3903 <br /> | 5737 <br /> | 2872<br /> | 1625<br /> |-<br /> | Messaging Server <br /> | 9.15 <br /> | 2.71 <br /> | 1.47<br /> | 57 <br /> | 1 <br /> | 0.7 <br /> | 88 <br /> | 15.1<br /> | 8<br /> |-<br /> | Services Server <br /> | 11.15 <br /> | 3.155 <br /> | 1.53 <br /> | 55<br /> | 1<br /> | 0.73<br /> | 1.89 <br /> | 17 <br /> | 9<br /> |-<br /> | Web Server <br /> | 11.2 <br /> | 3.36<br /> | 1.43 <br /> | 55 <br /> | 1 <br /> | 0.8 <br /> | 173 <br /> | 21 <br /> | 10.24<br /> |}<br /> <br /> == Installing VMware Tools ==<br /> <br /> The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system. <br /> <br /> == Installing Cisco Unified EIM-WIM Components on Virtual Machines ==<br /> <br /> You can install the Cisco Unified EIM-WIM components after the configuration of the VMs. Installation of these Cisco Unified EIM-WIM components on a VM is the same as the installation of these components on physical hardware. Refer to the Cisco Unified EIM-WIM Install Guide for the steps to install Cisco Unified EIM-WIM components. <br /> <br /> == Migrating ==<br /> <br /> Migration of EIM-WIM components from existing physical boxes to VMs is not supported.Also we do not support EIM-WIM deployments which are mix of physical hardware and VMs <br /> <br /> == Unified EIM-WIM, Release 4.3(2) Support for Virtualization on the ESXi/UCS Platform ==<br /> <br /> *Unified EIM-WIM is qualified with ESXi4.0 as of now and qualification on ESXi 4.1 is in progress.Note that once the VM is upgraded to ESXi 4.1 , VMWare tools need to upgraded as well in all VMs. For more information on upgrading refer to [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003806 VMware documentation]</div>

Cchetty http://docwiki.cisco.com/wiki/UC_Applications-Specific_Virtualization_Information 2011-10-10T16:42:20Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Guidelines to Edit UC Virtualization Pages]]''' <br /> <br /> &lt;br&gt;<br /> <br /> {{note| '''If a UC application is not listed in this page, then that application does not have any product-specific information. In this case, the information provided in the higher-level pages applies to those products.'''}}&lt;br&gt;<br /> <br /> = Call Processing and System Management Applications =<br /> <br /> *&lt;font size=&quot;2&quot;&gt;'''[[Cisco Unified Communications Manager Business Edition 6000]]'''&lt;/font&gt;&lt;br&gt;<br /> <br /> &lt;br&gt;<br /> <br /> = Contact Center Applications =<br /> <br /> *&lt;font size=&quot;2&quot;&gt;'''[[Virtualization for Cisco MediaSense]]'''&lt;/font&gt;&lt;br&gt;<br /> *&lt;font size=&quot;2&quot;&gt;'''[[Virtualization for Cisco SocialMiner]]'''&lt;/font&gt;&lt;br&gt;<br /> *&lt;font size=&quot;2&quot;&gt;'''[[Virtualization for Unified CCX]]'''&lt;/font&gt;&lt;br&gt;<br /> *&lt;font size=&quot;2&quot;&gt;'''[[Cisco Unified Intelligence Center|Virtualization for Unified IC]]'''&lt;/font&gt;&lt;br&gt;<br /> <br /> {{note| The following applications are not supported with the Nexus 1KV.}} <br /> <br /> *&lt;font size=&quot;2&quot;&gt;'''[[Virtualization for Unified CCE]]'''&lt;/font&gt;&lt;br&gt;<br /> *&lt;font size=&quot;2&quot;&gt;'''[[Virtualization for Unified CVP]]'''&lt;/font&gt;&lt;br&gt;<br /> *&lt;font size=&quot;2&quot;&gt;'''[[Virtualization for CCMP with Unified CCE on UCS Hardware]]'''&lt;/font&gt;&lt;br&gt;<br /> *[[Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager|&lt;font size=&quot;2&quot;&gt;'''Virtualization for Unfied EIM-WIM'''&lt;/font&gt;]]<br /> <br /> &lt;br&gt;<br /> <br /> = Messaging and Presence Applications =<br /> <br /> *&lt;font size=&quot;2&quot;&gt;'''[[Virtualization for Cisco Unified Presence]]'''&lt;/font&gt;&lt;br&gt;<br /> <br /> &lt;br&gt;<br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> &lt;br&gt;<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 2011-10-10T16:42:20Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''&lt;br&gt;<br /> <br /> ----<br /> <br /> Version compatibility of virtualized Cisco Unified Communications applications with various server/storage hardware options are listed below. <br /> <br /> *Support information below is as of the release date of '''Cisco Unified Communications 8.6(1)''', which updated '''8.0, 8.5 and 8.6''' support policies.<br /> <br /> *Ensure your deployment follows the rules listed [[High-level Checklist for Design and Implementation|here]].<br /> <br /> *Click on the application name for additional product-specific requirements and information (if any).<br /> <br /> *&quot;TRC&quot; = &quot;Tested Reference Configuration&quot; as described [[Unified Computing System Hardware|here]].<br /> <br /> &lt;br&gt;<br /> <br /> == Call Processing and System Management Applications&lt;br&gt; ==<br /> <br /> {| style=&quot;width: 1076px; height: 476px&quot; class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | Unified Communications Manager (1) <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]] <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> &lt;br&gt;<br /> <br /> |-<br /> | Cisco Emergency Responder <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | Session Manager Edition <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | Not supported <br /> &lt;br&gt;<br /> <br /> |-<br /> | Intercompany Media Engine <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> |-<br /> | Unified Attendant Consoles <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.0(3) <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> |-<br /> | UC Management Suite (OM, SM, SSM, PM) <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later<br /> |}<br /> <br /> &lt;br&gt;(1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes. <br /> <br /> == Messaging and Presence Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS)&lt;br&gt;<br /> |-<br /> | Cisco Unity Connection <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later<br /> |-<br /> | Cisco Unity <br /> | 7.0(2) and later <br /> | 7.0(2) and later <br /> | Not supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not Supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]] <br /> | 8.6(1) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Contact Center Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] &lt;br&gt;<br /> | 8.5(1) and later&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later&amp;nbsp;<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | 8.5(1) and later<br /> |-<br /> | [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO), Quality Management (QM), and WorkForce Management (WFM)] <br /> | 8.5(2) and later&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later<br /> |-<br /> | [[Unified Contact Center Enterprise]] &lt;br&gt;<br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below<br /> |-<br /> | - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tool,&amp;nbsp;limited/hybrid support for Unified ICME/CCH/ICMH <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported<br /> |-<br /> | - Progger, Outbound Option with SCCP Dialer, Webview, EIM/WIM, Expert Advisor, RSM, Unified CRM Connector <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | 8.0(3) and later <br /> | 8.5(2) and later&amp;nbsp; <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | Not supported<br /> |-<br /> | [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]&amp;nbsp; <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Unified Customer Voice Portal]] (all components) &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco MediaSense|Cisco MediaSense]] <br /> | Not supported&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]] <br /> | 8.5(3) and later &lt;br&gt;<br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later<br /> |-<br /> | [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager Unified Email Interaction Manager and Web Interaction Manager] <br /> | Not supported <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/Metadata_2 2011-10-08T22:59:28Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE Inbound Dial Peer Recording|'''Call Flow Details for CUBE Inbound Dial Peer Recording''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;pre&gt;{<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;sessionId&quot;:&quot;c13129fa8dc41&quot;,<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.122.80/archive/c13129fa8dc41&quot;<br /> },<br /> &quot;sessionStartDate&quot;:1310669311674,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;trackStartDate&quot;:1310669311674,<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagCreateDate&quot;:1310669314734,<br /> &quot;tagOffset&quot;:3026<br /> },<br /> {<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagCreateDate&quot;:1310669322609,<br /> &quot;tagOffset&quot;:10924<br /> },<br /> {<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagCreateDate&quot;:1310669322837,<br /> &quot;tagOffset&quot;:11151<br /> },<br /> {<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagCreateDate&quot;:1310669314940,<br /> &quot;tagOffset&quot;:3255<br /> }<br /> ],<br /> &quot;trackDuration&quot;:18224,<br /> &quot;downloadUrl&quot;:&quot;http://10.194.122.80:8081/ExportRaw?recording=c13129fa8dc41-TRACK1&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;participantStartDate&quot;:1310669322818,<br /> &quot;deviceRef&quot;:&quot;1021&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;xRefCi&quot;:&quot;2b13129faba421&quot;,<br /> &quot;participantDuration&quot;:7080<br /> },<br /> {<br /> &quot;participantStartDate&quot;:1310669311674,<br /> &quot;deviceRef&quot;:&quot;1020&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;xRefCi&quot;:&quot;2a13129fa8dc41&quot;,<br /> &quot;participantDuration&quot;:11144<br /> }<br /> ]<br /> },<br /> {<br /> &quot;trackStartDate&quot;:1310669311674,<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagCreateDate&quot;:1310669314734,<br /> &quot;tagOffset&quot;:3026<br /> },<br /> {<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagCreateDate&quot;:1310669322837,<br /> &quot;tagOffset&quot;:11151<br /> }<br /> ],<br /> &quot;trackDuration&quot;:18224,<br /> &quot;downloadUrl&quot;:&quot;http://10.194.122.80:8081/ExportRaw?recording=c13129fa8dc41-TRACK0&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;participantStartDate&quot;:1310669311674,<br /> &quot;deviceRef&quot;:&quot;1019&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;xRefCi&quot;:&quot;2913129fa8dc41&quot;,<br /> &quot;participantDuration&quot;:18224<br /> }<br /> ]<br /> }<br /> ],<br /> &quot;sessionDuration&quot;:18224,<br /> &quot;callControllerIP&quot;:&quot;10.194.122.73&quot;,<br /> &quot;ccid&quot;:&quot;3672593664-0000065536-0000001754-2159614892&quot;<br /> }<br /> &lt;/pre&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense 2011-10-08T22:46:03Z

<p>Cchetty: 1 revision</p> <hr /> <div>{{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).}}&amp;nbsp; <br /> <br /> = Updates to this Page =<br /> <br /> The following is a list of significant updates to this page: <br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Date <br /> ! Update<br /> |-<br /> | October 2011 <br /> | Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | June 2011 <br /> | Updated all links to align with the new Virtualization strucutre at [[Unified Communications in a Virtualized Environment]].<br /> |-<br /> | April 2011 <br /> | Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.<br /> |-<br /> | November 2010 <br /> | Virtualization of Cisco MediaSense on UCS C Series hardware.<br /> |-<br /> | December 2010 <br /> | Updated OVA template download link.<br /> |}<br /> <br /> = Information for Partners about Cisco MediaSense Deployments =<br /> <br /> See [[Unified Communications in a Virtualized Environment]]. <br /> <br /> = VM-Specific Cisco MediaSense Hardware Requirements =<br /> <br /> See [[Tested Reference Configurations (TRC)]]. <br /> <br /> Before you install the Cisco MediaSense software in any server, you must address the following requirements: <br /> <br /> *Only Cisco MediaSense must be running on this VM host. No other product can be installed on this server. <br /> *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).<br /> <br /> = Cisco MediaSense-Specific Details for VMware Requirements =<br /> <br /> See [[Unified Communications VMWare Requirements]] <br /> <br /> *Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation. <br /> *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]. &lt;br&gt;<br /> <br /> == Cisco MediaSense, Release 8.5(1)&amp;nbsp; and 8.5(2) ==<br /> <br /> All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS). <br /> <br /> *Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1). <br /> *If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.<br /> <br /> <br /> <br /> == Cisco MediaSense, Release 8.5(3) ==<br /> <br /> {{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.}} <br /> <br /> 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.<br /> <br /> See the following links for more information: <br /> <br /> *See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications <br /> *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.&lt;br&gt;<br /> <br /> = Cisco MediaSense-Specific Information for OVA Templates =<br /> <br /> If your partitions (VM&amp;nbsp;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&amp;nbsp;templates provided by Cisco MediaSense.&lt;br&gt;<br /> <br /> See the following websites for more information:&lt;br&gt;<br /> <br /> *[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.2&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest Cisco MediaSense OVA Templates]<br /> <br /> &lt;br&gt;<br /> <br /> {{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]].}} <br /> <br /> &lt;br&gt;<br /> <br /> {{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.}}<br /> <br /> = Cisco MediaSense-Specific Information for Sizing Guidelines =<br /> <br /> 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. <br /> <br /> = How to Dump Install Logs to the VM Serial Port&lt;br&gt; =<br /> <br /> See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]]. <br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}<br /> <br /> [[Category:Cisco_MediaSense]]</div>

Cchetty http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements 2011-10-08T20:19:35Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''&lt;br&gt;<br /> <br /> ----<br /> <br /> &lt;br&gt;<br /> <br /> This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications. <br /> <br /> == VMware is Mandatory for UC on UCS ==<br /> <br /> All UC on UCS servers require use of VMware to be supported. See the other sections on this page for specific VMware product, version and feature support. <br /> <br /> Nonvirtualized, physical, or bare-metal installations are not supported with UCS servers. <br /> <br /> UC on UCS requires Cisco Unified Communications 8.0(2) and later - specific applications and versions are covered at http://www.cisco.com/go/uc-virtualized. <br /> <br /> For &quot;legacy&quot; virtualization support of Version 7.x applications on VMware on 3rd-party servers, see the following documents: <br /> <br /> :*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide] <br /> :*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise &amp;amp; Hosted 7.5(3)]<br /> <br /> See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on customer purchase options and VMware license activation. <br /> <br /> Note: in all cases, the customer is required to have a valid service contract with VMware to be supported (see [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]]). <br /> <br /> == Hypervisor Support for Virtualized UC (Vendors, Products, Versions, Editions) ==<br /> <br /> At this time, the only hypervisor vendor supported for virtualized UC is VMware. <br /> <br /> &lt;br&gt;VMware vSphere ESXi is required for UC on UCS. <br /> <br /> *VMware ESX, regardless of version, is not supported for servers hosting Cisco Unified Communications. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications. <br /> *Versions of VMware ESXi prior to 4.0 are not supported due to technical reasons. Maintenance and patch versions and updates on a major release (such as 4.0 Update 1 or &quot;4.0U1&quot;) are supported at the time of release from VMware. <br /> *Supported versions of VMware ESXi are listed below. Unlisted versions are not supported for Cisco Unified Communications until explicitly indicated on this site.<br /> <br /> {{note| The minimum version may also be dependent on hardware - see the relevant supported applications matrix for the required product.}}&lt;br&gt;<br /> <br /> &lt;br&gt;<br /> <br /> === ESXi Support for Call Processing and System Management Applications&lt;br&gt; ===<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! <br /> Application&lt;br&gt;&lt;br&gt;<br /> <br /> ! VMware vSphere ESXi 4.0 and 4.0 Updates&lt;br&gt;&lt;br&gt;<br /> ! VMware vSphere ESXi 4.1 and 4.1 Updates&lt;br&gt;&lt;br&gt;<br /> |-<br /> | Unified Communications Manager <br /> | 8.0(2)+, 8.5(1)+ <br /> | 8.0(2)+, 8.5(1)+<br /> |-<br /> | [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]] <br /> | 8.5(1)+ <br /> | 8.5(1)+<br /> |-<br /> | Cisco Emergency Responder <br /> | 8.5(1)+, 8.6(1)+ <br /> | 8.5(1)+, 8.6(1)+<br /> |-<br /> | Session Manager Edition <br /> | 8.5(1)+ <br /> | 8.5(1)+<br /> |-<br /> | Unified Attendant Consoles <br /> | 8.0.3+, 8.5.1+ <br /> | 8.6.1+<br /> |-<br /> | UC Management Suite (OM, SM, SSM, PM) <br /> | 7.1 and later <br /> | 7.1 and later<br /> |}<br /> <br /> === ESXi Support for Messaging and Presence Applications&lt;br&gt; ===<br /> <br /> {| style=&quot;width: 812px; height: 108px&quot; class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application&lt;br&gt;&lt;br&gt;<br /> ! VMware vSphere ESXi 4.0 or 4.0 Update 1&lt;br&gt;&lt;br&gt;<br /> ! VMware vSphere ESXi 4.1<br /> |-<br /> | Cisco Unity Connection <br /> | 8.0(2) and later <br /> | 8.0(3) and later<br /> |-<br /> | Cisco Unity <br /> | 7.x and later <br /> | 7.x and later<br /> |-<br /> | [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]] <br /> | 8.0(2) and later <br /> | 8.0(2) and later<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> === ESXi Support for Contact Center Applications ===<br /> <br /> {{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}} <br /> <br /> {| style=&quot;width: 816px; height: 396px&quot; class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! VMware vSphere ESXi 4.0&amp;nbsp;and 4.0 Updates <br /> ! VMware vSphere ESXi 4.1&amp;nbsp; and 4.1 Updates<br /> |-<br /> | [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] <br /> | 8.0(2) and later or 8.5(1) and later <br /> | 8.0(2) SU2 and later or 8.5(1) and later<br /> |-<br /> | [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM),and Work Force Management (WFM)] <br /> | 8.5(1) and later <br /> | 8.5(2) and later<br /> |-<br /> | [[Unified Contact Center Enterprise]] &lt;br&gt;<br /> | ESXi 4.0 Update 1 (minimum required). See below <br /> | See below<br /> |-<br /> | - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools <br /> | 8.0(2) and later or 8.5(1) and later <br /> | 8.0(2) and later or 8.5(1) and later<br /> |-<br /> | [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]]&amp;nbsp; <br /> | 8.0(3) and later <br /> | 8.5(2) and later<br /> |-<br /> | [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] <br /> | 8.0(2) and later or 8.5(1) and later <br /> | 8.0(2) and later or 8.5(1) and later<br /> |-<br /> | [[Unified Customer Voice Portal]] (all components)&amp;nbsp; <br /> | 8.0(1) and later or 8.5(1) and later <br /> | 8.0(1) and later or 8.5(1) and later<br /> |-<br /> | [[Virtualization for Cisco MediaSense|Cisco MediaSense]] <br /> | 8.5(1) and later <br /> | 8.5(2) and later<br /> |-<br /> | [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]] <br /> | 8.5(1) and later <br /> | 8.5(1) and later<br /> |-<br /> | [[Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager|Unified Email Interaction Manager&amp;nbsp;and Web Interaction Manager]]<br /> | 4.3(2) and later<br /> | 4.3(2) and later<br /> |}<br /> <br /> === &lt;br&gt;Additional Information&lt;br&gt; ===<br /> <br /> This section provides additional information on ESXi features and support:&lt;br&gt;<br /> <br /> *To upgrade from ESX 4.0 to ESX 4.1, see the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1022140 Instructional Video] available at VMware's Knowledge Base website. <br /> *VMware ESXi is sold in several editions with different levels of feature support. A comparison of VMware ESXi editions is available at https://www.vmware.com/products/vsphere/buy/editions_comparison.html and in the “A La Carte Features” chapter of https://www.vmware.com/files/pdf/vsphere_pricing.pdf. <br /> *[http://www.vmware.com/products/vsphere-hypervisor/ VMware vSphere Hypervisor] (formerly named VMware ESXi Single Server Edition or “free ESXi”) is the minimum edition required for most software to install, but an edition that supports robust, multihost management via VMware vCenter - Standard, Advanced, Enterprise, or Enterprise Plus - is strongly recommended. Enterprise Plus license is mandatory when installing virtual machines that use more than 4 vCPUs, e.g. the 20,000 user Unity Connection overlay. <br /> *While any Edition may be used, Cisco Unified Communications may not yet support all the features in the desired Edition (such as VMware Data Recovery). See [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> *Any virtualized deployment that does not align with the above rules (even non-production labs) is not supported by Cisco TAC.<br /> <br /> == Support of Cisco VN-Link and Cisco Nexus 1000V ==<br /> <br /> Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]]. <br /> <br /> Unless otherwise indicated above, Cisco VN-Link and Cisco Nexus 1000V are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]). <br /> <br /> Cisco VN-Link, Cisco Nexus® 1000V and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]). Other editions do not support these capabilities. <br /> <br /> For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100. <br /> <br /> For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around. <br /> <br /> &lt;br&gt;For more information on Cisco VN-Link and Cisco Nexus 1000V, see http://www.cisco.com/en/US/netsol/ns894/index.html and http://www.cisco.com/en/US/products/ps9902/index.html. <br /> <br /> == VMware Infrastructure Feature Support ==<br /> <br /> {{note| VMware Infrastructure feature support for Cisco Unified Contact Center Enterprise varies by component - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} <br /> <br /> VMware vSphere and vCenter include a number of innovative features such as vMotion that are not available with traditional physical hardware installations. Not all of these features lend themselves to real-time streaming media applications such as Cisco Unified Communications. The table below lists VMware features and their current support status for use with Cisco Unified Communications application virtual machines. <br /> <br /> As Cisco Unified Communications adds support for additional VMware features, this site will be updated as applicable. For an authoritative description of each feature, see VMware collateral at '''[http://www.vmware.com/products/vsphere/buy/editions_comparison.html http://www.vmware.com/products/vsphere/buy/editions_comparison.html]'''. Note that virtualized UC usually only supports a subset of available VMware features as described in the table below. Feature support may vary by UC application, and features are usually supported only with conditions or caveats due to the real-time nature of UC. <br /> <br /> === &lt;br&gt;Legend for Feature Support Tables ===<br /> <br /> :*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details <br /> :*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details <br /> :*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.<br /> <br /> === VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''&lt;br&gt;'''<br /> |-<br /> ! Feature <br /> ! Unified CM <br /> ! CER <br /> ! SME <br /> ! Unified Attendant Consoles <br /> ! UC Management Suite (OM, SM, SSM, PM) &lt;br&gt;<br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! vSphere ESXi 4.0 Features <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]] <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Copy_Virtual_Machine|Copy Virtual Machine]] <br /> | Y(C) <br /> | Y(C) <br /> | &amp;nbsp;Y(C) <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Resize_Virtual_Machine|Resize Virtual Machine]] <br /> | Y(P) <br /> | Y(P) <br /> | Y(P) <br /> | Y(P) <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Hot_Add|VMware Hot Add]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]] <br /> | Y(P)&amp;nbsp;&amp;nbsp; <br /> | Y(P)&amp;nbsp;&amp;nbsp; <br /> | Y(P)&amp;nbsp;&amp;nbsp; <br /> | Y(P)&amp;nbsp;&amp;nbsp; <br /> | Y(P) &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]] <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | Y(C)&amp;nbsp;(PM&amp;nbsp;only)&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | Y(C) <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vMotion|VMware vMotion]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Long_Distance_vMotion|Long Distance vMotion]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Storage_vMotion|VMware Storage vMotion]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Snapshots|VMware Snapshots]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vCenter_Converter|VMware vCenter Converter]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMsafe|VMsafe]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vShield|VMware vShield]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! All others not listed <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! vSphere ESXi 4.1 Features <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Boot_from_SAN|VMware Boot from SAN]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | No&lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! All other vSphere ESXi 4.1 Features <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No&lt;br&gt;<br /> |}<br /> <br /> === VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===<br /> <br /> {| border=&quot;1&quot;<br /> |+ ' <br /> |-<br /> ! Feature <br /> ! Unity Connection <br /> ! Unity <br /> ! Unified Presence <br /> ! &lt;br&gt;<br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! vSphere ESXi 4.0 Features <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Copy_Virtual_Machine|Copy Virtual Machine]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Resize_Virtual_Machine|Resize Virtual Machine]] <br /> | Y(P) <br /> | Y(P) <br /> | Y(PP <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Hot_Add|VMware Hot Add]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]] <br /> | Y(P) <br /> | Y(P)&amp;nbsp; <br /> | Y(P)<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]] <br /> | No <br /> | No <br /> | Y(C) <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]] <br /> | Y(C) <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vMotion|VMware vMotion]] <br /> | Y(P) <br /> | No <br /> | Y(P) <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Long_Distance_vMotion|Long Distance vMotion]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Storage_vMotion|VMware Storage vMotion]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]] <br /> | No <br /> | Y(C) <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]] <br /> | No <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Snapshots|VMware Snapshots]] <br /> | No <br /> | Y(C) <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vCenter_Converter|VMware vCenter Converter]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMsafe|VMsafe]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vShield|VMware vShield]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]] <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! All others not listed <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! vSphere ESXi 4.1 Features <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Identity|Identity]] <br /> | No &amp;nbsp; <br /> | No &amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Boot_from_SAN|VMware Boot from SAN]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! All other vSphere ESXi 4.1 Features <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> === VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===<br /> <br /> {| style=&quot;width: 906px; height: 823px&quot; border=&quot;1&quot;<br /> |+ &amp;nbsp; <br /> |-<br /> ! Feature <br /> ! Unified CCX <br /> ! Cisco WFO, QM, and WFM <br /> ! Unified CCE, CVP <br /> ! Unified IC <br /> ! Cisco MediaSense <br /> ! SocialMiner <br /> ! Unfied EIM-WIM <br /> ! &lt;br&gt;<br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! vSphere ESXi 4.0 Features <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | <br /> |- align=&quot;center&quot;<br /> ! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Copy_Virtual_Machine|Copy Virtual Machine]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | Y(C)&amp;nbsp; <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Resize_Virtual_Machine|Resize Virtual Machine]] <br /> | Y(P) <br /> | Y(P)&amp;nbsp; <br /> | No <br /> | Y(P)&amp;nbsp; <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Hot_Add|VMware Hot Add]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]] <br /> | Y(P)&amp;nbsp; <br /> | Y(P)&amp;nbsp; <br /> | Y(P)&amp;nbsp; <br /> | Y(P)&amp;nbsp; <br /> | No <br /> | No <br /> | No<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]] <br /> | Y(C) <br /> | Y(C) <br /> | No <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vMotion|VMware vMotion]] <br /> | Y(C)&amp;nbsp; <br /> | Y(P)&amp;nbsp; <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Long_Distance_vMotion|Long Distance vMotion]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Storage_vMotion|VMware Storage vMotion]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Snapshots|VMware Snapshots]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vCenter_Converter|VMware vCenter Converter]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMsafe|VMsafe]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#VMware_vShield|VMware vShield]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]] <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! All others not listed <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! vSphere ESXi 4.1 Features <br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | &lt;br&gt;<br /> | <br /> |- align=&quot;center&quot;<br /> ! [[#Boot_from_SAN|VMware Boot from SAN]] <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | Y(C)&amp;nbsp; <br /> | Y(C) <br /> | Y(C) <br /> | &lt;br&gt;<br /> |- align=&quot;center&quot;<br /> ! All other vSphere ESXi 4.1 Features <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | No <br /> | &lt;br&gt;<br /> |}<br /> <br /> == Best Practices ==<br /> <br /> === Virtual Machine Templates (OVA files) ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package). <br /> <br /> “Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]]. <br /> <br /> === Copy Virtual Machine ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes. <br /> <br /> :*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application). <br /> :*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.<br /> <br /> === Restart Virtual Machine on Different ESXi Host ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform: <br /> <br /> :*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc. <br /> :*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager. <br /> :*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.<br /> <br /> === Resize Virtual Machine ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server. <br /> <br /> :*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below. <br /> :*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:<br /> ::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first. <br /> ::*Adding vRAM is supported but requires VM to be shutdown first. <br /> ::*Adding vDisk is not supported as it would require re-partitioning by the application.<br /> :*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]. <br /> :*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application. <br /> :*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application. <br /> :*Live runtime resizing via the VMware Hot Add feature is not supported.<br /> <br /> === VMware Hot Add ===<br /> <br /> Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]]. <br /> <br /> === Multiple Physical NICs and vNICs ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address. <br /> <br /> === VMware High Availability (HA) ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software. <br /> <br /> :*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs). <br /> :*Does not protect vs. faults with the SAN or network hardware.<br /> <br /> === VMware Site Recovery Manager (SRM) ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it. <br /> <br /> === VMware Identity ===<br /> <br /> The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords). <br /> <br /> You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence. <br /> <br /> === VMware vNetwork Distributed Switch ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V). <br /> <br /> &lt;br&gt;<br /> <br /> === VMware vMotion ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> This feature migrates a live, running Virtual Machine (VM) from one physical server to another. <br /> <br /> The following applies to any use of vMotion with UC apps: <br /> <br /> :*VM must be installed on shared storage (SAN). <br /> :*Source and destination physical servers must be connected to same SAN. <br /> :*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration. <br /> :*VMware “Long Distance vMotion” (site to site) is not supported. <br /> :*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues. <br /> :*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM). <br /> :*Moving a shut down VM during a maintenance window, i.e. a &quot;cold migration&quot; or &quot;host to host migration&quot;, is not vMotion and is supported.<br /> <br /> If the UC app is listed as &quot;Supported with Caveats&quot;, then support is as described below: <br /> <br /> :*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.<br /> <br /> If the UC app is listed as &quot;Partial&quot; support, then support is “maintenance mode only” as described below: <br /> <br /> :*&quot;Maintenance mode only&quot; - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.<br /> <br /> &lt;br&gt;<br /> <br /> === VMware Dynamic Resource Scheduler ===<br /> <br /> Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. <br /> <br /> === VMware Dynamic Power Management ===<br /> <br /> Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. <br /> <br /> === Long Distance vMotion ===<br /> <br /> Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf. <br /> <br /> === Storage vMotion ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions: <br /> <br /> :*Requires SAN storage. <br /> :*May only be done during a maintenance window with UC VMs shut down.<br /> <br /> === VMware vCenter Update Manager (VUM) ===<br /> <br /> NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246. <br /> <br /> This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager. <br /> <br /> === VMware Consolidated Backup (VCB) ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246. <br /> <br /> This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine. <br /> <br /> Existing UC app methods of backing up the software continue to be supported. <br /> <br /> === VMware Data Recovery ===<br /> <br /> Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported. <br /> <br /> === VMware Snapshots ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246. <br /> <br /> Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine. <br /> <br /> === VMware Fault Tolerance ===<br /> <br /> Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration. <br /> <br /> === VMware vCenter Converter ===<br /> <br /> P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is: <br /> <br /> :*upgrade to 8.x software version on the bare-metal server <br /> :*take a software backup <br /> :*fresh install 8.x software on VMware / UC on UCS <br /> :*restore from backup<br /> <br /> === VMsafe ===<br /> <br /> Not supported. See the documentation for the UC application software or UC appliance software to see what is supported. <br /> <br /> === VMware vShield ===<br /> <br /> Not supported. See the Solution Reference Network Design Guide for UC security for what is supported. <br /> <br /> === Virtual Appliance Packaging of UC apps ===<br /> <br /> Not supported. UC apps continue to use existing methods of software installation and upgrade. <br /> <br /> === 3rd-Party VM-based Backup Tools ===<br /> <br /> Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported. <br /> <br /> === 3rd-Party VM-based Deployment Tools ===<br /> <br /> Not supported. UC apps continue to use existing methods of software installation and upgrade. <br /> <br /> === 3rd-Party Physical To Virtual (P2V) Migration Tools ===<br /> <br /> Not supported. See VMware vCenter Converter for what is supported. <br /> <br /> === VMware Boot from SAN ===<br /> <br /> NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware_Infrastructure_Feature_Support|VMware Infrastructure Feature Support]]. <br /> <br /> VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a &quot;diskless&quot; server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy. <br /> <br /> == Services and Support Contracts for VMware are Required ==<br /> <br /> Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco. <br /> <br /> Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly). <br /> <br /> Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware. <br /> <br /> Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy. <br /> <br /> Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information. <br /> <br /> == Cisco TAC Support Expectations ==<br /> <br /> The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from. <br /> <br /> &lt;br&gt;<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! &lt;br&gt;<br /> ! Buy from Cisco as Collaboration SKU <br /> ! Buy from Cisco as Data Center SKU <br /> ! Buy from 3rd-party, or enterprise/site license<br /> |-<br /> ! Available VMware ESXi Editions <br /> | Standard <br /> | Advanced, Enterprise or Enterprise Plus <br /> | Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly &quot;Single Server Edition&quot; or &quot;free ESXi&quot;<br /> |-<br /> ! Mandatory Support Contracts <br /> | ISV1 from Cisco as Collaboration Service SKU <br /> | ISV1 from Cisco as Data Center Service SKU <br /> | &quot;SnS&quot; subscription from VMware<br /> |-<br /> ! Who takes first call? <br /> | Cisco <br /> | Cisco <br /> | VMware<br /> |}<br /> <br /> '''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco. <br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/Runtime:_Open_RTSP_session_to_MediaSense_failed_with_timeout 2011-10-08T20:19:34Z

<p>Cchetty: 1 revision</p> <hr /> <div>== MediaSense server is unable to keep up with incoming recordings ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | Open RTSP session to MediaSense failed with timeout.<br /> |-<br /> ! '''Error Message''' <br /> | Timeout on TCP socket.<br /> |-<br /> ! '''Possible Cause''' <br /> | The total number of media streams (recording, playback and live monitoring) exceeds 340 streams.<br /> |-<br /> ! '''Recommended Action''' <br /> | Verify that total number of media streams (recording, playback and live monitoring) is less than 340. Decrease the total number of media streams if necessary.<br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | CSCto60804.<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 2011-10-08T20:19:34Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''&lt;br&gt;<br /> <br /> ----<br /> <br /> Version compatibility of virtualized Cisco Unified Communications applications with various server/storage hardware options are listed below. <br /> <br /> *Support information below is as of the release date of '''Cisco Unified Communications 8.6(1)''', which updated '''8.0, 8.5 and 8.6''' support policies.<br /> <br /> *Ensure your deployment follows the rules listed [[High-level Checklist for Design and Implementation|here]].<br /> <br /> *Click on the application name for additional product-specific requirements and information (if any).<br /> <br /> *&quot;TRC&quot; = &quot;Tested Reference Configuration&quot; as described [[Unified Computing System Hardware|here]].<br /> <br /> &lt;br&gt;<br /> <br /> == Call Processing and System Management Applications&lt;br&gt; ==<br /> <br /> {| style=&quot;width: 1076px; height: 476px&quot; class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | Unified Communications Manager (1) <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.0(2+) <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]] <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> &lt;br&gt;<br /> <br /> |-<br /> | Cisco Emergency Responder <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> |-<br /> | Session Manager Edition <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | <br /> *8.5(x) <br /> *8.6(x)<br /> <br /> | Not supported <br /> &lt;br&gt;<br /> <br /> |-<br /> | Intercompany Media Engine <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> | <br /> *8.6(2+)<br /> <br /> |-<br /> | Unified Attendant Consoles <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.0(3) <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> | <br /> *8.6(x)<br /> <br /> |-<br /> | UC Management Suite (OM, SM, SSM, PM) <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later <br /> | 7.1 and later<br /> |}<br /> <br /> &lt;br&gt;(1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes. <br /> <br /> == Messaging and Presence Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS)&lt;br&gt;<br /> |-<br /> | Cisco Unity Connection <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(3) and later <br /> | 8.0(2) and later<br /> |-<br /> | Cisco Unity <br /> | 7.0(2) and later <br /> | 7.0(2) and later <br /> | Not supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not supported <br /> | Not Supported <br /> | Not Supported <br /> | 7.0(2) and later <br /> | Not Supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]] <br /> | 8.6(1) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.5 and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.0(2) and later <br /> | 8.5 and later <br /> | 8.5 and later<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Contact Center Applications&lt;br&gt; ==<br /> <br /> {| class=&quot;wikitable FCK__ShowTableBorders&quot;<br /> |-<br /> ! Application <br /> ! [[Specification-Based Hardware Support]] <br /> ! B200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M2 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! B200 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS+FC SAN) <br /> ! B200 M1 &lt;br&gt;TRC #2 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> ! C210 M2 &lt;br&gt;TRC #2 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M2 &lt;br&gt;TRC #3 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C210 M1 &lt;br&gt;TRC #1 &lt;br&gt;(DAS, single-VM) <br /> ! C210 M1 &lt;br&gt;TRC #2 &lt;br&gt;(DAS) <br /> ! C210 M1 &lt;br&gt;TRC #3 &lt;br&gt;(DAS+FC SAN) <br /> ! C210 M1 &lt;br&gt;TRC #4 &lt;br&gt;(Diskless, ESXi 4.1+ only) <br /> ! C200 M2 &lt;br&gt;TRC #1 &lt;br&gt;(DAS) <br /> &lt;br&gt;<br /> <br /> |-<br /> | [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] &lt;br&gt;<br /> | 8.5(1) and later&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later&amp;nbsp;<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | 8.0(2)SU2 and later <br /> | 8.5(1) and later<br /> |-<br /> | [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO), Quality Management (QM), and WorkForce Management (WFM)] <br /> | 8.5(2) and later&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later<br /> |-<br /> | [[Unified Contact Center Enterprise]] &lt;br&gt;<br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below <br /> | See below<br /> |-<br /> | - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tool,&amp;nbsp;limited/hybrid support for Unified ICME/CCH/ICMH <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | <br /> Not supported<br /> <br /> | Not supported<br /> |-<br /> | - Progger, Outbound Option with SCCP Dialer, Webview, EIM/WIM, Expert Advisor, RSM, Unified CRM Connector <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | 8.0(3) and later <br /> | 8.5(2) and later&amp;nbsp; <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.0(3) and later <br /> | 8.5(2) and later <br /> | Not supported<br /> |-<br /> | [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]&amp;nbsp; <br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Unified Customer Voice Portal]] (all components) &lt;br&gt;<br /> | Not supported&lt;br&gt;<br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(2) and later <br /> *8.5(1) and later<br /> <br /> | <br /> *8.0(1) and later <br /> *8.5(1) and later<br /> <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco MediaSense|Cisco MediaSense]] <br /> | Not supported&lt;br&gt;<br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(2) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | 8.5(1) and later <br /> | 8.5(1) and later <br /> | Not supported <br /> | Not supported <br /> | Not supported<br /> |-<br /> | [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]] <br /> | 8.5(3) and later &lt;br&gt;<br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later <br /> | 8.5(3) and later<br /> |-<br /> | Unified Email Interaction Manager and Web Interaction Manager <br /> | Not supported <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported <br /> | 4.3(2) and later <br /> | Not supported<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates) 2011-10-08T20:19:34Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''&lt;br&gt;<br /> <br /> ----<br /> <br /> &lt;br&gt;<br /> <br /> = Supported Virtual Machine OVA Templates =<br /> <br /> 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 &quot;.ova&quot;. <br /> <br /> 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. <br /> <br /> 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. <br /> <br /> &lt;br&gt;See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications. <br /> <br /> 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. <br /> <br /> == Unified Communications Manager ==<br /> <br /> *[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&amp;catid=278875240 General OVA&amp;nbsp;Download Location]&lt;br&gt;<br /> *[[OVA Template Details for Unified CM Release 8.0]]&lt;br&gt;<br /> *[[OVA Template Details for Unified CM Release 8.5]]&lt;br&gt;<br /> *[[OVA Template Details for Unified CM Release 8.6]]&lt;br&gt;<br /> <br /> &lt;br&gt;&lt;br&gt;<br /> <br /> == Cisco Emergency Responder ==<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Emergency Responder''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores and Speed per Core <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/pub/software/portal/select.html?&amp;mdfid=283314470&amp;flowid=24901&amp;softwareid=283831649 12,000 users (C200 only)] <br /> | 2 @ 2.13 GHz each&lt;br&gt;(600 MHz reserved) <br /> | 4 GB (4 GB reserved) <br /> | 1 x 80 GB <br /> | 1 <br /> | <br /> Use on C200 M2 TRC#1 only. <br /> <br /> Limits: <br /> <br /> :*12,000 IP phones <br /> :*2,500 analog phones <br /> :*1,200 roaming phones (per Emergency Responder cluster) <br /> :*500 LAN switches <br /> :*30,000 switch ports <br /> :*3,000 ERLs<br /> <br /> |-<br /> ! [http://www.cisco.com/cisco/pub/software/portal/select.html?&amp;mdfid=283314470&amp;flowid=24901&amp;softwareid=283831649 20,000 users] <br /> | 1 @ 2.55 MHz &lt;br&gt;(600 MHz reserved) <br /> | 2.25 GB (2.304 GB reserved) <br /> | 1 x 80 GB <br /> | 1 <br /> | <br /> Not for use on C200 M2 TRC#1. <br /> <br /> Limits: <br /> <br /> :*20,000 IP phones <br /> :*5,000 analog phones <br /> :*2,000 roaming phones (per Emergency Responder cluster) <br /> :*1,000 LAN switches <br /> :*60,000 switch ports <br /> :*7,500 ERLs<br /> <br /> |-<br /> ! [http://www.cisco.com/cisco/pub/software/portal/select.html?&amp;mdfid=283314470&amp;flowid=24901&amp;softwareid=283831649 30,000 users] <br /> | 2 @ 2.55 MHz each <br /> | 6 GB <br /> | 2 x 80 GB <br /> | 1 <br /> | <br /> Not for use on C200 M2 TRC#1. <br /> <br /> Limits: <br /> <br /> :*30,000 IP phones <br /> :*10,000 analog phones <br /> :*3,000 roaming phones (per Emergency Responder cluster) <br /> :*2,000 LAN switches <br /> :*120,000 switch ports <br /> :*10,000 ERLs<br /> <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Session Manager Edition ==<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Session Manager Edition''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores and Speed per Core <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&amp;isPlatform=Y&amp;mdfid=282827095&amp;sftType=Unified+Communications+Manager+Virtual+Machine+Templates&amp;treeName=Voice+and+Unified+Communications&amp;modelName=Cisco+Unified+Communications+Manager+Version+8.0&amp;mdfLevel=Software%20Version/Option&amp;treeMdfId=278875240&amp;modifmdfid=null&amp;imname=&amp;hybrid=Y&amp;imst=N Use CUCM &quot;7500 users&quot;] <br /> | See CUCM &quot;7500 users&quot; <br /> | See CUCM &quot;7500 users&quot; <br /> | See CUCM &quot;7500 users&quot; <br /> | See CUCM &quot;7500 users&quot; <br /> | <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Cisco Unified Attendant Consoles (Enterprise, Business, Department) ==<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Unified Attendant Consoles''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=282581449&amp;flowid=26483&amp;softwareid=283910832&amp;release=8.6%281%29&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest OVA for Cisco Unified Attendant Consoles] <br /> | 1 @ 2.13 GHz <br /> | 4 GB <br /> | 1x 40GB <br /> | 1 <br /> | <br /> *See [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications Supported Applications matrix] for allowed hardware choices. <br /> *This OVA applies to Cisco Unified Attendant Consoles versions 8.0.3 through 8.6.1 and all operator capacities (up to 25 for the Cisco Unified Enterprise Attendant Console) <br /> *The CUxAC server operating system must be Windows Server 2008 (32-bit) in a virtual environment<br /> <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Cisco Unity Connection ==<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Unity Connection''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&amp;mdfid=283062758&amp;sftType=Unity+Connection+Software&amp;optPlat=&amp;nodecount=2&amp;edesignator=null&amp;modelName=Cisco+Unity+Connection+Virtualization&amp;treeMdfId=278875240&amp;treeName=Voice+and+Unified+Communications&amp;modifmdfid=null&amp;imname=&amp;hybrid=null&amp;imst=null&amp;lr=Y 500 users] <br /> | 1 <br /> | For version 8.5 or lesser - 2 GB&lt;br&gt;<br /> For version 8.6(1) or higher - 4 GB<br /> <br /> | 1x 160 GB <br /> | 1 <br /> | <br /> Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]]. <br /> <br /> Limits for Standalone Configuration: <br /> <br /> :*16 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*4 ports iLBC or G.722<br /> <br /> Limits for Active/Active Cluster Configuration: <br /> <br /> :*32 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*8 ports iLBC or G.722<br /> <br /> |-<br /> ! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&amp;mdfid=283062758&amp;sftType=Unity+Connection+Software&amp;optPlat=&amp;nodecount=2&amp;edesignator=null&amp;modelName=Cisco+Unity+Connection+Virtualization&amp;treeMdfId=278875240&amp;treeName=Voice+and+Unified+Communications&amp;modifmdfid=null&amp;imname=&amp;hybrid=null&amp;imst=null&amp;lr=Y 1000 users] <br /> | 1 <br /> | 4 GB <br /> | 1x 160 GB <br /> | 1 <br /> | <br /> Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]]. <br /> <br /> Limits for Standalone Configuration: <br /> <br /> :*24 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*6 ports iLBC or G.722<br /> <br /> Limits for Active/Active Cluster Configuration: <br /> <br /> :*48 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*12 ports iLBC or G.722<br /> <br /> For use on CUCM-BE 6000.<br /> <br /> |-<br /> ! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&amp;mdfid=283062758&amp;sftType=Unity+Connection+Software&amp;optPlat=&amp;nodecount=2&amp;edesignator=null&amp;modelName=Cisco+Unity+Connection+Virtualization&amp;treeMdfId=278875240&amp;treeName=Voice+and+Unified+Communications&amp;modifmdfid=null&amp;imname=&amp;hybrid=null&amp;imst=null&amp;lr=Y 5000 users] <br /> | 2 <br /> | For version 8.5 or lesser - 4 GB&lt;br&gt;<br /> For version 8.6(1) or higher - 6 GB<br /> <br /> | 1x 200 GB <br /> | 1 <br /> | <br /> Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]]. <br /> <br /> Limits for Standalone Configuration: <br /> <br /> :*100 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*25 ports iLBC or G.722<br /> <br /> Limits for Active/Active Cluster Configuration: <br /> <br /> :*200 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*50 ports iLBC or G.722<br /> <br /> |-<br /> ! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&amp;mdfid=283062758&amp;sftType=Unity+Connection+Software&amp;optPlat=&amp;nodecount=2&amp;edesignator=null&amp;modelName=Cisco+Unity+Connection+Virtualization&amp;treeMdfId=278875240&amp;treeName=Voice+and+Unified+Communications&amp;modifmdfid=null&amp;imname=&amp;hybrid=null&amp;imst=null&amp;lr=Y 10,000 users] <br /> | 4 <br /> | For version 8.5 or lesser - 4 GB&lt;br&gt;<br /> For version 8.6(1) or higher - 6 GB<br /> <br /> | 2x 146 GB or&lt;br&gt;<br /> 2x 300 GB or&lt;br&gt;2x 500 GB<br /> <br /> | 1 <br /> | <br /> For the larger 300GB or 500 GB disks, the datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks. <br /> <br /> Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]]. <br /> <br /> Limits for Standalone Configuration: <br /> <br /> :*150 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*35 ports iLBC or G.722<br /> <br /> Limits for Active/Active Cluster Configuration: <br /> <br /> :*300 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*70 ports iLBC or G.722<br /> <br /> |-<br /> ! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&amp;mdfid=283062758&amp;sftType=Unity+Connection+Software&amp;optPlat=&amp;nodecount=2&amp;edesignator=null&amp;modelName=Cisco+Unity+Connection+Virtualization&amp;treeMdfId=278875240&amp;treeName=Voice+and+Unified+Communications&amp;modifmdfid=null&amp;imname=&amp;hybrid=null&amp;imst=null&amp;lr=Y 20,000 users] <br /> | 7 <br /> | 8 GB <br /> | 2x 300 GB or &lt;br&gt;2x 500 GB <br /> | 1 <br /> | <br /> Require ESXi Enterprise Plus Licensing since it uses over 4 vCPUs for the Virtual Machine. <br /> <br /> The datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks. <br /> <br /> Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]]. <br /> <br /> Limits for Standalone Configuration: <br /> <br /> :*250 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*60 ports iLBC or G.722<br /> <br /> Limits for Active/Active Cluster Configuration: <br /> <br /> :*500 ports G.711 or G.729a (combined TUI, VUI, or TTS) <br /> :*120 ports iLBC or G.722<br /> <br /> |}<br /> <br /> == Cisco Unity ==<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Unity''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! 5000 users <br /> | 2 (requires VMware CPU Affinity) <br /> | 4 GB <br /> | <br /> 4x 24 GB <br /> <br /> :*vDisk 1 = Operating system <br /> :*vDisk 2 = Cisco Unity binaries <br /> :*vDisk 3 = Cisco Unity logs, SQL Server transaction logs <br /> :*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database<br /> <br /> | 1 <br /> | <br /> *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]. <br /> *Limits:<br /> <br /> :*48 ports <br /> :*36 text-to-speech ports<br /> <br /> |-<br /> ! 15,000 users <br /> | 4 (requires VMware CPU Affinity) <br /> | 4 GB <br /> | <br /> 4x 24 GB <br /> <br /> :*vDisk 1 = Operating system <br /> :*vDisk 2 = Cisco Unity binaries <br /> :*vDisk 3 = Cisco Unity logs, SQL Server transaction logs <br /> :*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database<br /> <br /> | 1 <br /> | <br /> *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]. <br /> *Limits:<br /> <br /> :*144 ports <br /> :*36 text-to-speech ports<br /> <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Cisco Unified Presence ==<br /> <br /> See also: <br /> <br /> *[[Virtualization for Cisco Unified Presence|Virtualization for Cisco Unified Presence]] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283736431&amp;flowid=23181&amp;softwareid=282074312&amp;release=8.0%20-%208.5&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=latest OVA Template Download Page]<br /> <br /> &lt;br&gt;<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Unified Presence''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&amp;flowid=23181&amp;softwareid=282074312&amp;release=8.0%20-%208.5&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest 1000 users] <br /> | 1 (800 MHz reserved) <br /> | 2 GB <br /> | 1x 80 GB <br /> | 1 <br /> | <br /> For use on all supported UCS, IBM, HP, and Specs-based hardware platforms, including CUCM-BE 6000. Cisco also recommends using this OVA when migrating from an MCS Server with disks smaller than 80 GB (for example, MCS-7825-H2).<br /> <br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&amp;flowid=23181&amp;softwareid=282074312&amp;release=8.0%20-%208.5&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest 2500 users] <br /> | 2 (2000 MHz reserved) <br /> | 4 GB <br /> | 1x 80 GB <br /> | 1 <br /> | For use on B200, C210, and Specs-based supported platforms. Cisco also recommends using this OVA when migrating from an MCS Server with disks smaller than 80 GB (for example, MCS-7825-H2).<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&amp;flowid=23181&amp;softwareid=282074312&amp;release=8.0%20-%208.5&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest 5000 users] <br /> | 4 (4000 MHz reserved) <br /> | 6 GB <br /> | 2x 80 GB <br /> | 1 <br /> | For use on B200, C210, and Specs-based hardware platforms. This OVA must be used when migrating from MCS 7845 or other physical platform with disks larger than 80 GB.<br /> |}<br /> <br /> Note: Any of the user base sizes above can be used when performing a DRS migration from a physical machine with a disk capacity of less than 80 GB (for example, MCS-7825-H2). If the disk capacity of the physical machine on which Cisco Unified Presence is running exceeds 80 GB, the 5000 user OVA configuration must be used to accommodate the larger database. &lt;br&gt;<br /> <br /> == Cisco Unified Contact Center Express ==<br /> <br /> See also: <br /> <br /> *[[Virtualization for Unified CCX]] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.0&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest| Unified CCX OVA Templates]: Note that Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow Unified Communications VMware Requirements page for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)<br /> <br /> &lt;br&gt;<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Unified Contact Center Express''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! colspan=&quot;2&quot; | Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes<br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.0&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest 100 agents] (Release 8.5(1)) <br /> | 2 <br /> | 4 GB <br /> | 1x 146 GB <br /> :*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs<br /> <br /> | 1 <br /> | <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.0&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest 300 agents] (Release 8.0(2) and Release 8.5(1)) <br /> | 2 <br /> | 4 GB <br /> | <br /> 2x 146 GB <br /> <br /> :*vDisk 1 = Operating System and Unified CCX binaries <br /> :*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2<br /> <br /> | 1 <br /> | <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.0&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest 400 agents] (Release 8.5(1)) <br /> | 4 <br /> | 8 GB <br /> | <br /> 2x 146 GB <br /> <br /> :*vDisk 1 = Operating System and Unified CCX binaries <br /> :*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2<br /> <br /> | 1 <br /> | <br /> |-<br /> ! rowspan=&quot;3&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=latest Single OVA] (Release 8.5 (1) or later) <br /> ! 100 agents <br /> | 2 <br /> | 4 GB <br /> | 1x 146 GB <br /> :*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs<br /> <br /> | 1 <br /> | <br /> |-<br /> ! 300 agents <br /> | 2 <br /> | 4 GB <br /> | <br /> 2x 146 GB <br /> <br /> :*vDisk 1 = Operating System and Unified CCX binaries <br /> :*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2<br /> <br /> | 1 <br /> | <br /> |-<br /> ! 400 agents <br /> | 4 <br /> | 8 GB <br /> | <br /> 2x 146 GB <br /> <br /> :*vDisk 1 = Operating System and Unified CCX binaries <br /> :*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2<br /> <br /> | 1 <br /> | <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all Unified CCX WFM 8.5.2] <br /> | 2 <br /> | 4 GB <br /> | <br /> :*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files <br /> :*vDisk 2 = Optional - can be used to hold SQL Server Data files<br /> <br /> | 1 <br /> | <br /> Capacities <br /> <br /> :*900 named users <br /> :*300 concurrent users<br /> <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)] <br /> | 2 <br /> | 4 GB <br /> | <br /> :*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files <br /> :*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)<br /> <br /> | 1 <br /> | <br /> Capacities <br /> <br /> :*3600 named users <br /> :*1200 concurrent users<br /> <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=2.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)] <br /> | 4 <br /> | 4 GB <br /> | <br /> :*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries <br /> :*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache<br /> <br /> | 1 <br /> | <br /> Capacities <br /> <br /> :*300 concurrent voice recordings for Server (SPAN) and Network recording <br /> :*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording<br /> <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=1.0&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all Unified CCX WFM 8.5.1] <br /> | 2 <br /> | 2 GB <br /> | <br /> 2x 146 GB <br /> <br /> :*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files <br /> :*vDisk 2 = Optional - can be used to hold SQL Server Data files<br /> <br /> | 1 <br /> | <br /> Capacities <br /> <br /> :*300 named users <br /> :*150 concurrent users<br /> <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=1.0&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all Unified CCX WFO QM 8.5.1 Base Server Configuration (CR/QM/AQM)] <br /> | 2 <br /> | 2 GB <br /> | <br /> 2x 146 GB <br /> <br /> :*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files <br /> :*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)<br /> <br /> | 1 <br /> | <br /> Capacities <br /> <br /> :*300 named users <br /> :*150 concurrent users<br /> <br /> |-<br /> ! colspan=&quot;2&quot; | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&amp;flowid=5217&amp;softwareid=283733053&amp;release=1.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all Unified CCX WFO QM Configuration (CR/QM/AQM)] <br /> | 2 <br /> | 2 GB <br /> | <br /> 2x 146 GB <br /> <br /> :*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files <br /> :*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage )<br /> <br /> | 2 <br /> | <br /> Capacities <br /> <br /> :*300 named users <br /> :*150 concurrent users <br /> :*150 voice recordings, for all recording types (desktop, server and network) <br /> :*150 voice+screen recordings, for all recording types (desktop, server and network)<br /> <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == UC Management Suite (PM, OM, SM, SSM) ==<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! IOPS (avg) (1) <br /> ! IOPS (max) (1) <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! CUPM up to 1K phones (VM-CUCMS_1S) <br /> | 1 <br /> | 2 GB <br /> | 1x 30 GB <br /> | 100 <br /> | 500 <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUPM 1K to 10K phones <br /> | 4 <br /> | 4 GB <br /> | 1x 40 GB (2) <br /> | 100 <br /> | 500 <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUPM 10K to 60K phones app server <br /> | 4 <br /> | 4 GB <br /> | 1x 30 GB(3) <br /> | 100 <br /> | 500 <br /> | 1 <br /> | requires DB VM<br /> |-<br /> ! CUPM 10K to 60K phones database server <br /> | 4 <br /> | 8 GB <br /> | 1x 120 GB(3) <br /> | 100 <br /> | 500 <br /> | 1 <br /> | requires App VM<br /> |-<br /> ! CUOM/SM 1K phones <br /> | 1 <br /> | 3 GB <br /> | 1x 50 GB <br /> | 6 <br /> | 15 <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUOM 10K phones (VM-CUCMS_2L) <br /> | 2 <br /> | 8 GB <br /> | 1x 72 GB <br /> | <br /> | <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUOM 45K phones (VM-CUCMS_4L) <br /> | 4 <br /> | 8 GB <br /> | 2x 60 GB <br /> | <br /> | <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUSM 10K Phones (VM-CUCMS_2) <br /> | 2 <br /> | 4 GB <br /> | 1x 72 GB <br /> | <br /> | <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUSM 45K Server (VM-CUCMS_4) <br /> | 4 <br /> | 4 GB <br /> | 2x 60 GB <br /> | <br /> | <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUSSM 10K phones (VM-CUCMS_1) <br /> | 1 <br /> | 4 GB <br /> | 1x 60 GB <br /> | <br /> | <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUSSM 45K Phones <br /> | 2 <br /> | 4 GB <br /> | 1x 72 GB <br /> | <br /> | <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! CUCMS 10K phones Co-resident (VM_CUCMS_8) <br /> | 8 <br /> | 16 GB <br /> | 1x 320 GB (2) <br /> | 100 <br /> | 500 <br /> | 1 <br /> | &lt;br&gt;<br /> |}<br /> <br /> Notes: &lt;br&gt;(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. &lt;br&gt;(2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) &lt;br&gt;(3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned) <br /> <br /> There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments. <br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&amp;release=8.5&amp;relind=AVAILABLE&amp;flowid=24181&amp;softwareid=281934350&amp;rellifecycle=&amp;reltype=latest PM 1K Server OVA] <br /> | 1 <br /> | 2 GB <br /> | 1x 30 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&amp;release=8.5&amp;relind=AVAILABLE&amp;flowid=24181&amp;softwareid=281934350&amp;rellifecycle=&amp;reltype=latest PM 1K to 10K Server OVA] <br /> | 4 <br /> | 4 GB <br /> | 1x 40 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&amp;release=8.5&amp;relind=AVAILABLE&amp;flowid=24181&amp;softwareid=281934350&amp;rellifecycle=&amp;reltype=latest PM 10K to 60K App/Web Server OVA] <br /> | 4 <br /> | 4 GB <br /> | 1x 30 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&amp;release=8.5&amp;relind=AVAILABLE&amp;flowid=24181&amp;softwareid=281934350&amp;rellifecycle=&amp;reltype=latest PM 10K to 60K Database Server OVA] <br /> | 4 <br /> | 8 GB <br /> | 1x 120 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&amp;flowid=20421&amp;softwareid=282773197&amp;release=8.0&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&amp;amp;SM_1K)] <br /> | 1 <br /> | 3 GB <br /> | 1x 50 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&amp;flowid=19121&amp;softwareid=281934350&amp;release=2.2&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)] <br /> | 1 <br /> | 2 GB <br /> | 1x 30 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |}<br /> <br /> == Unified Contact Center Enterprise ==<br /> <br /> See also: <br /> <br /> *[[Unified Contact Center Enterprise]] <br /> *[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates] <br /> *See also [http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]<br /> <br /> Templates are available for Windows Server 2003 and Windows Server 2008 R2. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&amp;release=1.1&amp;relind=AVAILABLE&amp;flowid=5210&amp;softwareid=283914286&amp;rellifecycle=&amp;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. <br /> <br /> &lt;br&gt;<br /> <br /> {| border=&quot;1&quot; cellspacing=&quot;3&quot; cellpadding=&quot;3&quot;<br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Configuration Name <br /> ! vCPU Cores <br /> ! vRAM / Memory (GB) <br /> ! vDisk (GB) <br /> ! vNIC&lt;br&gt;<br /> ! Notes<br /> |-<br /> | colspan=&quot;7&quot; | '''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'''<br /> |-<br /> | '''Router 8000 agents''' <br /> | 2 <br /> | 4 <br /> | 1 x80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''Logger 8000 agents''' <br /> | 4 <br /> | 4 <br /> | 1x 80 for OS&lt;br&gt;1x 150 for DB <br /> | 2 <br /> | The two vDisks can be in the same datastore&amp;nbsp;<br /> |-<br /> | '''Rogger 4000 agents''' <br /> | 4 <br /> | 4 <br /> | 1x 80 for OS&lt;br&gt;1x 150 for DB <br /> | 2 <br /> | The two vDisks can be in the same datastore&amp;nbsp;<br /> |-<br /> | '''Agent PG – CTIOS 2000 agents''' <br /> | 2 <br /> | 4 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''Agent PG – CAD 1000 agents''' <br /> | 2 <br /> | 4 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''Agent PG – CTIOS 450 agents''' <br /> | 1 <br /> | 2 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''Agent PG – CAD 297 agents''' <br /> | 1 <br /> | 2 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''MR PG 2000 agents 10 pims''' <br /> | 2 <br /> | 4 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''MR PG 1000 agents 5 pims''' <br /> | 1 <br /> | 2 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''VRU PG 9600 ports 10 pims''' <br /> | 2 <br /> | 2 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''VRU PG 1200 ports 4 pims''' <br /> | 1 <br /> | 2 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''Avaya ACD PG''' <br /> | 2 <br /> | 4 <br /> | 1x 80 <br /> | 2 <br /> | 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.<br /> |-<br /> | '''TDM ACD PG 2000 agents''' <br /> | 2 <br /> | 4 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''TDM ACD PG 250 agents''' <br /> | 1 <br /> | 2 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''UCC Gateway PG 2000 agents''' <br /> | 2 <br /> | 4 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''UCC Gateway PG 450 agents''' <br /> | 1 <br /> | 2 <br /> | 1x 80 <br /> | 2 <br /> | &amp;nbsp;<br /> |-<br /> | '''Administration Client''' <br /> | 1 <br /> | 2 <br /> | 1x 40 <br /> | 1 <br /> | &amp;nbsp;(Client AW)<br /> |-<br /> | '''Administration Server - AW''' <br /> | 1 <br /> | 2 <br /> | 1x 40 <br /> | 1 <br /> | &amp;nbsp;<br /> |-<br /> | '''AW-HDS''' <br /> | 4 <br /> | 4 <br /> | 1x 80 for OS&lt;br&gt;1x 500 for DB <br /> | 1 <br /> | &amp;nbsp;(200 reporters.) The two vDisks can be in the same datastore<br /> |-<br /> | '''AW-HDS-DDS''' <br /> | 4 <br /> | 4 <br /> | 1x 80 for OS&lt;br&gt;1x 500 for DB <br /> | 1 <br /> | &amp;nbsp;(200 reporters.) The two vDisks can be in the same datastore<br /> |-<br /> | '''HDS-DDS''' <br /> | 4 <br /> | 4 <br /> | 1x 80 for OS&lt;br&gt;1x 500 for DB <br /> | 1 <br /> | (200 reporters.) The two vDisks can be in the same datastore &amp;nbsp;<br /> |-<br /> | '''CCMP single box 1500 agents''' <br /> | 4 <br /> | 4 <br /> | 1x 100 <br /> | 1 <br /> | &amp;nbsp;<br /> |-<br /> | '''CCMP Web/App Svr 8000 agents''' <br /> | 4 <br /> | 4 <br /> | 1x 100 <br /> | 1 <br /> | &amp;nbsp;<br /> |-<br /> | '''CCMP with Config AW 1500 agents''' <br /> | 4 <br /> | 4 <br /> | 1x 100 <br /> | 1 <br /> | &amp;nbsp;<br /> |-<br /> | '''CCMP DB only 8000 agents''' <br /> | 8 <br /> | 4 <br /> | 1x 250 <br /> | 1 <br /> | &amp;nbsp;<br /> |}<br /> <br /> == Unified Customer Voice Portal ==<br /> <br /> See also: <br /> <br /> *[[Unified Customer Voice Portal]] <br /> *[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Unified Customer Voice Portal''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions.&amp;nbsp;See CVP co-residency section for detail) <br /> | 4 <br /> | 4 GB <br /> | 1x 146 GB <br /> | 1 <br /> | Template Name: Cisco Unified CVP Call Server-VXML Server.ova<br /> |-<br /> ! Unified CVP Reporting Server (Large) <br /> | 4 <br /> | 4 GB <br /> | Disk 1 - 72 GB, Disk 2 - 438 GB <br /> | 1 <br /> | Template Name: Cisco Unified CVP Reporting Server.ova<br /> |-<br /> ! Unified CVP Operations Console <br /> | 2 <br /> | 2 GB <br /> | 1x 20 GB <br /> | 1 <br /> | Template Name: Cisco Unified CVP Operations Console.ova<br /> |}<br /> <br /> == Cisco MediaSense ==<br /> <br /> See also: <br /> <br /> *[[Virtualization for Cisco MediaSense]] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.2&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest Cisco MediaSense OVA Templates]<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco MediaSense''' <br /> |-<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes<br /> |-<br /> ! CMS_6T_main_server_v8.5_vmv7 <br /> | 7 <br /> | 8 GB <br /> | 2 X 146 GB (thick provisioning) <br /> | 1 <br /> | rowspan=&quot;3&quot; | Release 8.5(1)<br /> |-<br /> ! CMS_12T_main_server_v8.5_vmv7 <br /> | 7 <br /> | 8 GB <br /> | 2 X 300 GB (thick provisioning) <br /> | 1<br /> |-<br /> ! CMS_expansion_server_v8.5_vmv7 <br /> | 7&lt;br&gt;<br /> | 8 GB <br /> | 2 x 80 GB (thick provisioning) <br /> | 1<br /> |-<br /> ! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 &lt;br&gt;<br /> | 7&lt;br&gt;<br /> | 8 GB&lt;br&gt;<br /> | 2 X 150 GB (thick provisioning)&lt;br&gt;<br /> | 1 <br /> | rowspan=&quot;4&quot; | Release 8.5(2) and &lt;br&gt;Release 8.5(3)&amp;nbsp;<br /> |-<br /> ! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 &lt;br&gt;<br /> | 7&lt;br&gt;<br /> | 8 GB&lt;br&gt;<br /> | 2 X 300 GB (thick provisioning)&lt;br&gt;<br /> | 1<br /> |-<br /> ! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 &lt;br&gt;<br /> | 7&lt;br&gt;<br /> | 8 GB&lt;br&gt;<br /> | 2 X 600 GB (thick provisioning)&lt;br&gt;<br /> | 1<br /> |-<br /> ! CMS_expansion_server_v8.5.2_vmv7 <br /> | 7 <br /> | 8 GB <br /> | 2 x 80 GB (thick provisioning) <br /> | 1<br /> |}<br /> <br /> == Cisco Unified Intelligence Center ==<br /> <br /> See also: <br /> <br /> *[[Cisco Unified Intelligence Center]] <br /> *[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Unified Intelligence Center''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&amp;flowid=5228&amp;softwareid=283776220&amp;release=8.0(3)&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest CUIC (200 Reporting Users)] <br /> | 4 <br /> | 6 GB <br /> | 1x 146 GB <br /> | 1 <br /> | <br /> |}<br /> <br /> == Cisco Unified Contact Center Management Portal ==<br /> <br /> See also: <br /> <br /> *[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]] <br /> *[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! Unified CCMP (1500 Agents) <br /> | 4 <br /> | 4 GB <br /> | 1x 100 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! Unified CCMP (Web/App Srv Only) (8000 Agents) <br /> | 4 <br /> | 4 GB <br /> | 1x 100 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |-<br /> ! Unified CCMP (DB Only) (8000 Agents) <br /> | 8 <br /> | 4 GB <br /> | 1x 250 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |}<br /> <br /> == Cisco SocialMiner ==<br /> <br /> See also: <br /> <br /> *[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]] <br /> *[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&amp;softwareid=283733464&amp;release=8.5.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all| Cisco SocialMiner OVA Templates]<br /> <br /> {| border=&quot;1&quot;<br /> |+ '''Supported OVA Templates: Cisco SocialMiner''' <br /> |- style=&quot;background: rgb(229,228,226)&quot;<br /> ! Application, OVA Capacity and Notes+Download Link <br /> ! vCPU Cores <br /> ! vRAM / Memory <br /> ! vDisk <br /> ! vNIC <br /> ! Notes <br /> ! &lt;br&gt;<br /> |-<br /> ! Standard Production Server <br /> | 4 <br /> | 12 GB <br /> | 1x 146 GB and 1x 256 GB <br /> | 1 <br /> | &lt;br&gt;<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> == Cisco Unfied Email Interaction Manager and Web Interaction Manager ==<br /> <br /> &amp;nbsp; <br /> <br /> {| style=&quot;width: 1064px; height: 315px&quot; border=&quot;1&quot; cellspacing=&quot;1&quot; cellpadding=&quot;1&quot; width=&quot;1064&quot;<br /> |-<br /> | '''Application, OVA Capacity and Notes+Download Link''' <br /> | '''Contents''' <br /> | '''No of VM's to deploy of each component''' <br /> | '''vCPU''' <br /> | '''vDisk''' <br /> | '''vRAM/Memory'''<br /> |-<br /> | rowspan=&quot;2&quot; | 50 agents(all in one) <br /> | <br /> Web Server<br /> <br /> | 1 <br /> | 1 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Application server, Services server, File server, Messaging server,Database server and Web server <br /> | 1 <br /> | 4 <br /> | 1 x 150GB <br /> | 4<br /> |-<br /> | rowspan=&quot;5&quot; | 80 agents <br /> | Web Server <br /> | 1 <br /> | 1 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Application Server <br /> | 1 <br /> | 2 <br /> | 1 x 80 GB <br /> | 2<br /> |-<br /> | Services Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Database Server <br /> | 1 <br /> | 4 <br /> | <br /> 1 x 80GB for OS, <br /> <br /> 1 x 200GB forDB<br /> <br /> | 4<br /> |-<br /> | File and Messaging Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | rowspan=&quot;5&quot; | 120 agents <br /> | Web Server <br /> | 1 <br /> | 1 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Application Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Services Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | Database Server <br /> | 1 <br /> | 4 <br /> | <br /> 1 x 80GB&amp;nbsp; for OS, <br /> <br /> 1 x 200GB for DB<br /> <br /> | 4<br /> |-<br /> | File and Messaging Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | rowspan=&quot;5&quot; | 240 agents <br /> | Web Server <br /> | 2 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Application Server <br /> | 2 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Services Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | Database Server <br /> | 1 <br /> | 4 <br /> | <br /> 1 x 80GB for OS, <br /> <br /> 1 x 200GB for DB<br /> <br /> | 8<br /> |-<br /> | File and Messaging Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | rowspan=&quot;5&quot; | 360 agents <br /> | Web Server <br /> | 3 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Application Server <br /> | 3 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Services Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | Database Server <br /> | 1 <br /> | 8 <br /> | <br /> 1 x 80GB&amp;nbsp; for OS, <br /> <br /> 1 x 500GB forDB<br /> <br /> | 16<br /> |-<br /> | File and Messaging Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | rowspan=&quot;5&quot; | 480 agents <br /> | Web Server <br /> | 4 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Application Server <br /> | 4 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | Services Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | Database Server <br /> | 1 <br /> | 8 <br /> | <br /> 1 x 80GB for OS, <br /> <br /> 1 x 500GB for DB<br /> <br /> | 16<br /> |-<br /> | File and Messaging Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | rowspan=&quot;6&quot; | 600 agents <br /> | Web Server <br /> | 5 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Application Server <br /> | 5 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | Services Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |-<br /> | Database Server <br /> | 1 <br /> | 8 <br /> | <br /> 1 x 80GB for OS, <br /> <br /> 1 x 500GB for DB<br /> <br /> | 16<br /> |-<br /> | File Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 2<br /> |-<br /> | Messaging Server <br /> | 1 <br /> | 2 <br /> | 1 x 80GB <br /> | 4<br /> |}<br /> <br /> &amp;nbsp; <br /> <br /> ----<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255,215,0)&quot; | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]<br /> |}</div>

Cchetty http://docwiki.cisco.com/wiki/Upgrade:_Data_out_of_sync_after_upgrade 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>= Data out of sync after upgrade =<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | <br /> 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.&amp;nbsp;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.<br /> <br /> |-<br /> ! '''Error Message''' <br /> | <br /> Data is not synchronized between the primary database and secondary database.<br /> <br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> Mismatched software&amp;nbsp;versions on the primary and secondary servers may cause this issue if the upgrade process is not completed on both servers.<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> 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.<br /> <br /> |-<br /> ! '''Release''' <br /> | <br /> Release 8.5(3).<br /> <br /> |-<br /> ! '''Associated CDETS #''' <br /> | <br /> None.<br /> <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Upgrade:_Sync_after_switch_version_failed 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Upgrade: Sync after switch version failed ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | <br /> After you complete the switch version process on the primary server, you attempted to switch the version on the secondary server and did not succeed.<br /> <br /> |-<br /> ! '''Error Message''' <br /> | &lt;pre&gt;ERROR Sync after switch version failed&lt;/pre&gt;<br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> Not known at this point.<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> Reboot the secondary server and perform the switch version process again.<br /> <br /> |-<br /> ! '''Release''' <br /> | <br /> Relese 8.5(3).<br /> <br /> |-<br /> ! '''Associated CDETS #''' <br /> | <br /> None.<br /> <br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/General:_RTSP_live_monitoring_sessions_fail_when_using_CUBE 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== RTSP live monitoring sessions fail when using CUBE ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | When using a mixed load in a CUBE deployment, multiple RTSP live monitoring sessions failed (RTSP&amp;nbsp;packets were dropped). Recordings may also sound very choppy on playback.<br /> |-<br /> ! '''Error Message''' <br /> | None.<br /> |-<br /> ! '''Possible Cause''' <br /> | 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.<br /> |-<br /> ! '''Recommended Action''' <br /> | If your CUBE&amp;nbsp;deployment is running heavy loads, verify that the Ethernet cable connecting CUBE to the switch is 1 GB.&lt;br&gt;<br /> |-<br /> ! '''Release''' <br /> | Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> &lt;br&gt; <br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Database:_Database_no_longer_accepts_data 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Database no longer accepts data ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | <br /> The Cisco MediaSense Enterprise Replication Smart Blob (Binary Large Object) space, referred to as ora_ersb, does not accept any more data.&lt;br&gt;<br /> <br /> |-<br /> ! '''Error Message''' <br /> | <br /> Informix log:<br /> &lt;pre&gt;08/27/11 19:20:56 CDR QUEUER: Send Queue space is FULL - waiting for space in CDR_QDATA_SBSPACE<br /> 08/27/11 19:21:57 CDR WARNING:RQM sbspace ora_ersb is full, Please add the space. error number = 13<br /> &lt;/pre&gt;<br /> Application log:<br /> &lt;pre&gt;<br /> java.sql.BatchUpdateException: Long transaction aborted.<br /> &lt;/pre&gt;<br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> When the primary or secondary server is down, data continues to be written to the other server. Data replication does not happen until the affected server starts running again. Until that point, the data is accumulated in a designated space on the hard disk (in this case, the ora_ersb). When the ora_ersb is full, no more data can be written to the surviving server.<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> The only viable action is to bring up the affected node. You could also try to delete some existing data to make room for new data. See the Considerations for Failure Conditions section in the Cisco MediaSense Installation and Administration Guide.&lt;br&gt;<br /> <br /> The following&amp;nbsp;two actions will not solve this problem:<br /> <br /> #Disabling replication: curently, Cisco MediaSense does not have a CLI for this action.<br /> #Adding more space to ora_ersb requires root access and Database Administrator privileges.<br /> <br /> |-<br /> ! '''Release''' <br /> | <br /> Release 8.5(3).<br /> <br /> |-<br /> ! '''Associated CDETS #''' <br /> | <br /> None.<br /> <br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Configuration:_Calls_using_g.722_codec_are_not_recorded 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Calls using g.722 codec are not recorded&amp;nbsp; ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | When a call is established between two phones, the call is not recorded by Cisco MediaSense in both Unified CM and CUBE.<br /> |-<br /> ! '''Error Message''' <br /> | State of the recorded conversation is ERROR.<br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> Once a call is established between two phones and the g.722 codec is negotiated for that call, then Cisco MediaSense does not support the recording of g.722 calls. <br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | Disable g.722 codec in Unified CM to ensure that these calls are recorded by Cisco MediaSense. &lt;br&gt;<br /> |-<br /> ! '''Release''' <br /> | Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Administration:_Unknown_request_error_display 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Unknown request error display ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | Once you successfully login to the Cisco MediaSense Administration, an unknown request error displays in the UI.<br /> |-<br /> ! '''Error Message''' <br /> | &lt;pre&gt;You have reached this page in error. Most likely you typed a wrong URL in the address bar of your browser. <br /> If the problem persists, please contact your Administrator.&lt;/pre&gt;<br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> This error is known to display if you login to the Cisco MediaSense Administration immediately after implementing the post-installation setup procedure. &lt;br&gt;<br /> <br /> 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.&lt;br&gt;<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | Ignore this error and continue with your configuration. You only see this error once. You will not see this error when you login again.<br /> |-<br /> ! '''Release''' <br /> | Release 8.5(3)&amp;nbsp;<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/API:_Incorrect_session_or_participant_duration 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Incorrect session or participant duration ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | Track, participant, or session duration is incorrect or negative (for example: &quot;sessionDuration&quot;:-4776).<br /> |-<br /> ! '''Error Message''' <br /> | from /var/log/active/syslog/messages: &lt;pre&gt;Aug 23 02:51:05 pauems01 user 6 ilog_impl: Restarting NTP as time offset is -185.215622 msec.<br /> <br /> Aug 23 02:51:07 pauems01 user 6 ilog_impl: NTP servers list: 10.192.254.11 10.192.254.1&lt;/pre&gt;&lt;pre&gt;Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.11, \<br /> stratum 1, '''offset -185.225332''', delay 0.04140 23<br /> <br /> <br /> <br /> Aug 02:51:07 ntpdate[17992]: step time server 10.192.254.11 ''offset -185.225332 sec'' (rc=0).&lt;/pre&gt;&lt;pre&gt;Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.1, \<br /> stratum 2, '''offset 0.054938''', delay 0.02736 23<br /> <br /> <br /> <br /> Aug 02:51:07 ntpdate[18001]: adjust time server 10.192.254.1 offset 0.054938 sec (rc=0). &lt;/pre&gt;<br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> Incorrect duration could have several causes, unsynchronized NTP servers is a known possibility.<br /> <br /> 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.<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> Verify that both NTP servers provide synchronized times.<br /> <br /> |-<br /> ! '''Release''' <br /> | <br /> Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> <br /> |-<br /> ! '''Associated CDETS #''' <br /> | <br /> None.<br /> <br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/FAQs_for_Cisco_MediaSense 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Go to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> &lt;br&gt; <br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;background-color: rgb(255, 224, 200);&quot; | Introduction<br /> |-<br /> | <br /> This page lists frequently asked questions about Cisco MediaSense. <br /> <br /> |-<br /> | If you want to '''ask a question''', '''post a comment''', or '''discuss an issue''' regarding a specific article, then follow this procedure: <br /> ::#Log in <br /> ::#Navigate to the article in question <br /> ::#Click the '''Discussion''' tab at the top of the page <br /> ::#Edit the Discussion page as described above under Editing <br /> ::#To start a different thread under a new subheading on the Discussion page, click the '''+''' tab at the top of the page instead of the Edit tab.<br /> <br /> |}<br /> <br /> == How do you correlate reference call IDs for different call scenarios, under Unified CM phone forking? ==<br /> <br /> In Cisco MediaSense, the meta data for each call only provides the xRefCi (reference call ID) and the device ref (extension) of the forking device and the far-end device (can be a conference bridge or any other phone). <br /> <br /> The xRefCi parameter is Unified CM's identifier for a particular media stream. They do not always correspond 1-to-1 with the recorded tracks. <br /> <br /> === Agent Hold/Resume Scenario ===<br /> <br /> #Agent A (extn 1000) and Caller C (extn 2000) are talking to each other <br /> #Agent A puts call on hold <br /> #Agent A resumes call<br /> <br /> There are 2 recording sessions for this scenario: <br /> <br /> *Session with sessionId = S1 with following 2 tracks, for the time period /segment&amp;nbsp; before agent puts call on hold.&lt;br&gt;trackNumber=0 with participant A ( deviceRef=1000, xRefCi = aaaa) &lt;br&gt;trackNumber=1 with participant B (deviceRef=2000, xRefCi = cccc) <br /> *Session with sessionId = S2 with following 2 tracks, for the time period / segment after agent resumes the call. &lt;br&gt;trackNumber=0 with participant A( deviceRef=1000, xRefCi = aaaa) &lt;br&gt;trackNumber=1 with participant B (deviceRef=2000, xRefCi = cccc)<br /> <br /> MediaSense does not record the the segment of the call while agent has put the call on hold. <br /> <br /> === Customer Hold/Resume Scenario ===<br /> <br /> #Agent A (extn 1000) and Caller C (extn 2000) are talking to each other <br /> #Customer C puts call on hold <br /> #Customer C resumes call<br /> <br /> The entire call is recorded in one session for this scenario: <br /> <br /> *Session with sessionId = S1 with following 2 tracks&lt;br&gt;trackNumber=0 with participant A ( deviceRef=1000, xRefCi = aaaa) &lt;br&gt;trackNumber=1 with participant B ( deviceRef=2000, xRefCi = cccc)<br /> <br /> In this scenario MediaSense also records the the segment of the call while customer has put the call on hold. <br /> <br /> === Agent Transfer to Another Agent Scenario&amp;nbsp; ===<br /> <br /> #Agent A (extn 1000) and Caller C (extn 2000) are talking to each other <br /> #Agent A transfers call to another agent B (extn 3000). Both A and B's devices are set up for forking <br /> #B and C are talking. <br /> #After some time B and C end call<br /> <br /> There are 3 recording sessions for this scenario <br /> <br /> *Session with sessionId = S1 with following 2 tracks, for the time period /segment&amp;nbsp; before agent transfers call. As soon as A initiates transfer, S1 is marked as CLOSED_NORMAL<br /> <br /> :*trackNumber=0 with participant A (deviceRef=1000, xRefCi = a1) <br /> :*trackNumber=1 with participant C (deviceRef=2000, xRefCi = c1)<br /> <br /> *For the time period / segment A and B are consulting with each other, 2 new sessions will get created.<br /> <br /> :*Session with sessionId = S2 with following 2 tracks,&lt;br&gt;trackNumber=0 with participant A (deviceRef=1000, xRefCi = a2) &lt;br&gt;trackNumber=1 with participant B (deviceRef=3000, xRefCi = b2) <br /> :*Session with sessionId = S3 with following 2 tracks,&lt;br&gt;trackNumber=0 with participant B (deviceRef=3000, xRefCi = b2) &lt;br&gt;trackNumber=1 with participant A (deviceRef=1000, xRefCi = a2)<br /> <br /> *Once A completes transfer<br /> <br /> :*Session S2 is marked as CLOSED_NORMAL <br /> :*Session S3 gets updated with farend changing from A to C&lt;br&gt;trackNumber=0 with participant B (deviceRef=3000, xRefCi = b2) &lt;br&gt;trackNumber=1 with participant C (deviceRef=2000, xRefCi = c2) &lt;br&gt;Note that trackNumber 1 has 2 participants. Participant A before the transfer and participant C after tranbsfer<br /> <br /> *After B and C end the call<br /> <br /> :*session S3 is marked CLOSED_NORMAL&lt;br&gt;MediaSense does not record the the segment of the call while agent has put the call on hold.<br /> <br /> === Agent Conference with Another Agent Scenario&amp;nbsp; ===<br /> <br /> #Agent A (extn 1000) and Caller C (extn 2000) are talking to each other <br /> #Agent A conferences caller with another agent B (extn 3000). Both A and B's devices are set up for forking <br /> #A, B and C are talking. <br /> #A drops the call <br /> #After some time B and C end call<br /> <br /> There are 3 recording sessions for this scenario <br /> <br /> *Session with sessionId = S1 with following 2 tracks, for the time period /segment&amp;nbsp; before agent conferences call. As soon as A initiates conference, S1 is marked as CLOSED_NORMAL&lt;br&gt;trackNumber=0 with participant A (deviceRef=1000, xRefCi = a1) &lt;br&gt;trackNumber=1 with participant C (deviceRef=2000, xRefCi = c1)<br /> <br /> *For the time period / segment A and B are consulting with each other, 2 new sessions will get created.<br /> <br /> :*Session with sessionId = S2 with following 2 tracks,&lt;br&gt;trackNumber=0 with participant A (deviceRef=1000, xRefCi = a2) &lt;br&gt;trackNumber=1 with participant B (deviceRef=3000, xRefCi = b2) <br /> :*Session with sessionId = S3 with following 2 tracks,&lt;br&gt;trackNumber=0 with participant B (deviceRef=3000, xRefCi = b2) &lt;br&gt;trackNumber=1 with participant A (deviceRef=1000, xRefCi = a2)<br /> <br /> *Once A completes conference<br /> <br /> :*Session S2 gets marked as CLOSED_NORMAL <br /> :*Session S3 gets updated with farend changing from A to Conference bridge (CFB)&lt;br&gt;trackNumber=0 with participant C (deviceRef=2000, xRefCi = b2)&lt;br&gt;trackNumber=1 with participant CFB (deviceRef=b number of CFB,, xRefCi = cfb1)&lt;br&gt;Note that trackNumber 1 has 2 participants. Participant A before the conference and participant CFB after conference <br /> :*Session S4 gets created with &lt;br&gt;trackNumber=0 with participant A (deviceRef=1000, xRefCi = a1 , this is original xRefCi when A and C were talking)&lt;br&gt;trackNumber=1 with participant CFB (deviceRef=b number of CFB, xRefCi = cfb2)<br /> <br /> *After C drops the call<br /> <br /> :*S4 is updated with farend from Conference bridge (CFB) to B &lt;br&gt;trackNumber=1 with participant B (deviceRef=3000, xRefCi = b2) <br /> :*S3 is updated with farend changing from Conference bridge (CFB) to A. &lt;br&gt;trackNumber=1 with participant A (deviceRef=1000, xRefCi = a1)<br /> <br /> *After A and B end the call<br /> <br /> :*session S3 and S4 are marked CLOSED_NORMAL<br /> <br /> &lt;br&gt; <br /> <br /> &lt;br&gt; <br /> <br /> == How do you correlate reference call IDs for different call sessions, under CUBE forking? ==<br /> <br /> With CUBE forking, very few situations cause a call to be split into multiple recording sessions. Hold/Resume, transfer and conference operations do not start new recording sessions in most cases. In the few cases where new sessions are created, there is a common value, CCID (Call Correlation ID), which is common to all sessions in the call. CCID is the decimal form of Cisco-Guid, a unique call key which is generated by Cisco voice routers. The first router which receives a call generates this key, and passes it down the line to all subsequent devices including Cisco MediaSense. <br /> <br /> CUBE itself does not generate xRefCi values, but to create similarity with Unified CM phone forking calls, Cisco MediaSense also synthesizes a pair of xRefCi values for every CUBE call. These can be seen in the metadata at the track level, along with CCID, which appears at the session level. <br /> <br /> The following situations cause CUBE recordings to be split into multiple sessions. <br /> <br /> === Mid-call Codec Change ===<br /> <br /> If a transfer, conference, conference drop, or other operation causes the parties to renegotiate their codec, Cisco MediaSense ends the current recording session and starts a new one. The two sessions will share the same CCID and the same pair of xRefCi values. <br /> <br /> === Consult Transfers ===<br /> <br /> A consult transfer is a transfer from one agent to another, in which the two agents talk to each other for a while, with the original caller waiting on hold. The consult leg of the call is obviously related in some way to the overall call, and it is possible to configure Unified CM such that consult calls DO pass through CUBE. However, CUBE and Cisco MediaSense have no idea that these calls are related, and they create a new CCID and a new pair of xRefCi values for this session. <br /> <br /> These calls can however be associated with one another by comparing participant deviceRef and timestamp fields. Consider this scenario: <br /> <br /> #Caller C (extn 2000) calls Agent A (extn 1000) (sessionId=S1, CCID=C1) <br /> #Agent A consults with Agent B (extn 3000) (sessionId=S2, CCID=C2) <br /> #Agent A drops, and Caller C talks with Agent B (sessionId=S1, CCID=C1)<br /> <br /> The red flag in this scenario is in Step 2. During that period, Agent A (deviceRef 1000) is a participant in two recording sessions at once: <br /> <br /> *Session=S1 / CCID=C1, and <br /> *Session=S2 / CCID=C2<br /> <br /> Therefore S1 is related to S2, and C1 is related to C2. <br /> <br /> === Detecting Consult Calls&lt;br&gt; ===<br /> <br /> First we need a clear definition of consult call: ''any secondary call which is made by a current participant in an existing session to an endpoint which is outside that session, and which excludes the other participants in that session.'' In theory, this could include an agent placing the caller on hold to check with his boss about taking lunch, or even an agent putting the caller on hold to receive a call from his wife, but we will ignore those possibilities for now. <br /> <br /> It is possible for a client application to detect a consult call in real time by tracking the Cisco MediaSense event stream.&amp;nbsp; If the client observes a session STARTED event containing a given deviceRef, followed by ''another'' session STARTED event containing the same deviceRef with no intervening session ENDED event, it can conclude that the sessionId's and the CCIDs found in the two session STARTED events are associated.&amp;nbsp; <br /> <br /> Historically, a client can check for any consult calls which are associated with a given primary call, using the Cisco MediaSense API.&amp;nbsp; Assume the client knows that Agent A was using extn 1000, in CCID &amp;lt;C1&amp;gt;.&amp;nbsp; It can follow these instructions to find any associated consult calls: <br /> <br /> *Retrieve the session metadata for the primary call by issuing getSessionByCCID(&amp;lt;C1&amp;gt;).&amp;nbsp; <br /> *Extract the sessionStartDate (call it &amp;lt;Ta&amp;gt;), and sessionDuration. <br /> *Calculate the sessionEndDate (call it &amp;lt;Tb&amp;gt;) by adding sessionDuration to &amp;lt;Ta&amp;gt;.&amp;nbsp; <br /> *Issue the following API request:&lt;br&gt;<br /> &lt;pre&gt;https://10.194.118.1:8443/ora/queryService/query/getSessionsByDeviceRef?value=1000&amp;amp;minSessionStartDate=&amp;lt;Ta&amp;gt;&amp;amp;maxSessionStartDate=&amp;lt;Tb&amp;gt;&lt;/pre&gt; <br /> This query could return more than one session.&amp;nbsp; If it does, then all of them can be assumed to be associated with the same call. <br /> <br /> === Detecting Consult Calls from Multiple Participants&lt;br&gt; ===<br /> <br /> The above procedure will find all consult calls made from the device which received the initial phone call.&amp;nbsp; However, what if there are consult calls made from a device to which the call was subsequently transferred? <br /> <br /> Consider this procedure: <br /> <br /> *Caller calls Agent 1 <br /> *Agent 1 consults with Agent 2, then drops <br /> *Caller speaks with Agent 2 <br /> *Agent 2 consults with Agent 3, then drops <br /> *Caller speaks with Agent 3<br /> <br /> The procedure above will not catch the consult call between Agent 2 and Agent 3. <br /> <br /> Since this is a CUBE call, we can make use of the fact that all of the connections between the caller and each of the agents are included in the same recording session, and the fact that ''all'' of the agents involved will be listed as participants in the same session at one time or another.&amp;nbsp; Thus, from the primary session metadata, we can collect a list of all the deviceRef's which were involved.&amp;nbsp; To find those sessions, we can make a series of calls to getSessionsByDeviceRef, specifying the primary session's time range together with one deviceRef per request.&amp;nbsp; Alternatively, we can shortcut that process by issuing a single getSessions request such as the following:&lt;br&gt; <br /> &lt;pre&gt;{<br /> &quot;requestParameters&quot;: [<br /> {<br /> &quot;fieldName&quot;: &quot;deviceRef&quot;,<br /> &quot;fieldConditions&quot;: [<br /> {<br /> &quot;fieldOperator&quot;: &quot;equals&quot;,<br /> &quot;fieldValues&quot;: [<br /> &quot;1000&quot;<br /> ],<br /> &quot;fieldConnector&quot;: &quot;OR&quot;<br /> },<br /> {<br /> &quot;fieldOperator&quot;: &quot;equals&quot;,<br /> &quot;fieldValues&quot;: [<br /> &quot;2000&quot;<br /> ],<br /> &quot;fieldConnector&quot;: &quot;OR&quot;<br /> },<br /> {<br /> &quot;fieldOperator&quot;: &quot;equals&quot;,<br /> &quot;fieldValues&quot;: [<br /> &quot;3000&quot;<br /> ],<br /> &quot;fieldConnector&quot;: &quot;OR&quot;<br /> },<br /> {<br /> &quot;fieldOperator&quot;: &quot;equals&quot;,<br /> &quot;fieldValues&quot;: [<br /> &quot;4000&quot;<br /> ]<br /> }<br /> ],<br /> &quot;paramConnector&quot;: &quot;AND&quot;<br /> },<br /> {<br /> &quot;fieldName&quot;: &quot;sessionStartDate&quot;,<br /> &quot;fieldConditions&quot;: [<br /> {<br /> &quot;fieldOperator&quot;: &quot;between&quot;,<br /> &quot;fieldValues&quot;: [<br /> &amp;lt;Ta&amp;gt;, // session start time<br /> &amp;lt;Tb&amp;gt;// session end time<br /> ]<br /> }<br /> ]<br /> }<br /> ]<br /> }&lt;/pre&gt; <br /> This query will return all the consult calls associated with the original primary call and all of its transfers. <br /> <br /> The astute reader will note that the above procedure actually casts the net too broadly.&amp;nbsp; If for example, the agent at deviceRef 4000 conducted and terminated a completely independent call which happened to start ''after'' &amp;lt;Ta&amp;gt; and ''before'' he was added to the call in question, the above procedure will include that independent call in the set.&amp;nbsp; This problem can be solved though, using the information available in the primary session's metadata.&amp;nbsp; Each participant's information includes the time offset at which he joined the session, and the duration of his tenure.&amp;nbsp; Client code could use that information to simply delete the unrelated sessions from the list he received above.&amp;nbsp; Or, it could formulate a series of direct getSessions or getSessionByDeviceRef queries which correctly frame the time periods during which each agent was in the primary call.&amp;nbsp; We leave that as an exercise to the reader! <br /> <br /> === Putting it All Together ===<br /> <br /> Above, we presented precedures for retrieving all sessions associated with a given Cisco MediaSense recording session.&amp;nbsp; However, we have also seen that a given call may be divided into more than one session, as in the case of a mid-call codec change.&amp;nbsp; How do we retrieve ''all'' recordings (including consults) associated with ''all'' sessions connected to the caller's interaction?&amp;nbsp; <br /> <br /> The answer is to extend the instructions above for detecting multiple consult calls. First, we would collect all sessions which share the CCID of the primary session in question.&amp;nbsp; Then, we would build our list of participants from ''all'' of those session records.&amp;nbsp; Next we would calculate the time rangs as the sessionStartDate of the earliest session through the end of the latest session.&amp;nbsp; Finally, we can execute the getSessions query shown above. <br /> <br /> As before, we may end up capturing too many recordings in this net, so the client could execute a postprocessing step to delete those unrelated sessions from its list. <br /> <br /> == How do you associate calls in Cisco MediaSense to their appearance in other solution components? ==<br /> <br /> === Identifier Correlation Table ===<br /> <br /> Below are two tables - one for UCM calls and one for CUBE calls. Each column represents a solution component or protocol, with the first column representing Cisco MediaSense. Each row represents a particular type of identifier. <br /> <br /> To read the table, begin with a cell that represents the data item that you know, and then look horizontally to the column representing the solution component in which you want to find the call.&amp;nbsp; The entry in that cell indicates by what name the exact same data item is known in the target component.&amp;nbsp; If the target component has a blank cell in that row, then that data item is not known to that component.&amp;nbsp; You can instead look for an intervening column where you can cross vertically into another row where that cell is not blank in the target component's column. <br /> <br /> For example, with a UCM call, suppose you know the GED-188 CallReferenceID and want to find the call in Cisco MediaSense. Looking left from the GED-188 column you see that there is no value in the MediaSense column, so you cannot map directly to it. However, there are two columns where you can zig-zag across rows: UCM CDR and TAPI/JTAPI. Let's look the UCM CDR first. A client can select the proper UCM CDR record by searching for one in which the IncomingProtocolCallRef matches the GED-188 CallReferenceID. That record contains value called destLegCallIdentifier, which is the same as the MediaSense NearEnd xRefCi, and can therefore be used to find the corresponding record in Cisco MediaSense. <br /> <br /> UCM CDR records are not written until some time after the end of the call terminates, however, so the above method can only be used historically. If you need the information in real time, you can translate through TAPI/JTAPI protocol. GED-188 CallReferenceID matches the TAPI/JTAPI Cisco-Connection.UniqueID, and from there you can determine the Terminal.ConnectionID, which matches the NearEnd xRefCi in Cisco MediaSense. Obviously, this method can only work if you have a TAPI/JTAPI connection to UCM. <br /> <br /> There is another path as well. Look downward from the GED-188 CallReferenceID. It turns out that you can also use the AlertingDevice and AnsweringDevice to match the deviceRef field in MediaSense. This method also works in real time.&lt;br&gt; <br /> <br /> &lt;br&gt; <br /> <br /> {| width=&quot;200&quot; cellspacing=&quot;1&quot; cellpadding=&quot;3&quot; border=&quot;1&quot; style=&quot;&quot;<br /> |+ '''Call Correlation for Calls Forked by a Unified CM IP Phone''' <br /> |-<br /> ! scope=&quot;col&quot; | MediaSense&lt;br&gt; <br /> ! scope=&quot;col&quot; | Ingress Gateway or CUBE&lt;br&gt; <br /> ! scope=&quot;col&quot; | AAA RADIUS CDR&lt;br&gt;<br /> ! scope=&quot;col&quot; | UCM CDR&lt;br&gt; <br /> ! scope=&quot;col&quot; | TAPI/JTAPI field&lt;br&gt; <br /> ! scope=&quot;col&quot; | UCCE Database&lt;br&gt; <br /> ! scope=&quot;col&quot; | UCCE Script&lt;br&gt; <br /> ! scope=&quot;col&quot; | CTIOS&lt;br&gt; <br /> ! scope=&quot;col&quot; | GED-188&lt;br&gt;<br /> |-<br /> | (1)&lt;br&gt; <br /> | Cisco-Guid&lt;br&gt; <br /> | &lt;br&gt;<br /> | IncomingProtocolCallRef&lt;br&gt; <br /> | CiscoConnection.UniqueID&lt;br&gt; <br /> | TCD.CallReferenceID&lt;br&gt; <br /> | Call.CallGUID&lt;br&gt; <br /> | &lt;br&gt; <br /> | CallReferenceID&lt;br&gt;<br /> |-<br /> | NearEnd xRefCi&lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> | destLegCallIdentifier&lt;br&gt; <br /> | Terminal.ConnectionID&lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> |-<br /> | FarEnd xRefCi&lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> | origLegCallIdentifier&lt;br&gt; <br /> | Terminal.ConnectionID&lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> |-<br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> | global_CallID_call-ManagerId + global_CallID_callId&lt;br&gt;(A.K.A. UCM GCID)&lt;br&gt; <br /> | CiscoCall.CallID&lt;br&gt; <br /> | TCD.PeripheralCallKey&lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> |-<br /> | deviceId&lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | Agent.AgentInstrument&lt;br&gt; <br /> | &lt;br&gt;<br /> |-<br /> | deviceRef&lt;br&gt; <br /> | &lt;br&gt; <br /> | &lt;br&gt;<br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | TCD.InstrumentPortNumber (2)&lt;br&gt; <br /> | &lt;br&gt; <br /> | Agent.AgentExtension or Agent.Extension&lt;br&gt; <br /> | AlertingDevice or&lt;br&gt;AnsweringDevice&lt;br&gt;<br /> |}<br /> <br /> &lt;br&gt; &lt;br&gt; <br /> <br /> {| width=&quot;200&quot; cellspacing=&quot;1&quot; cellpadding=&quot;3&quot; border=&quot;1&quot;<br /> |+ '''Call Correlation for Calls Forked by CUBE''' <br /> |-<br /> ! scope=&quot;col&quot; | MediaSense&lt;br&gt; <br /> ! scope=&quot;col&quot; | Ingress Gateway or CUBE&lt;br&gt; <br /> ! scope=&quot;col&quot; | AAA RADIUS CDR&lt;br&gt;<br /> ! scope=&quot;col&quot; | UCM CDR&lt;br&gt; <br /> ! scope=&quot;col&quot; | TAPI/JTAPI field&lt;br&gt; <br /> ! scope=&quot;col&quot; | UCCE Database&lt;br&gt; <br /> ! scope=&quot;col&quot; | UCCE Script&lt;br&gt; <br /> ! scope=&quot;col&quot; | CTIOS&lt;br&gt; <br /> ! scope=&quot;col&quot; | GED-188&lt;br&gt;<br /> |-<br /> | CCID&lt;br&gt; <br /> | Cisco-Guid&lt;br&gt; <br /> | Cisco-Guid&lt;br&gt;<br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | TCD.CallReferenceID&lt;br&gt; <br /> | Call.CallGUID&lt;br&gt; <br /> | &lt;br&gt; <br /> | CallReferenceID&lt;br&gt;<br /> |-<br /> | deviceRef&lt;br&gt; <br /> | Called or calling party extn&lt;br&gt; <br /> | &lt;br&gt;<br /> | &lt;br&gt; <br /> | &lt;br&gt; <br /> | <br /> TCD.InstrumentPortNumber (2)&lt;br&gt; <br /> <br /> | &lt;br&gt; <br /> | Agent.AgentExtension or Agent.Extension&lt;br&gt; <br /> | AlertingDevice or&lt;br&gt;AnsweringDevice&lt;br&gt;<br /> |}<br /> <br /> &lt;br&gt; <br /> <br /> === Notes ===<br /> <br /> #In recordings of UCM calls, Cisco MediaSense does in fact receive a Cisco-Guid from UCM, but it is not the same one that is captured by the other solution devices. MediaSense therefore does not even store this value. <br /> #For agent-to-agent calls, TCD.InstrumentPortNumber is the destination agent’s extension. The calling agent’s extension can be found in TCD.ANI.<br /> <br /> &lt;br&gt; &lt;br&gt; <br /> <br /> == How do you determine which track has the calling and which has the called party?&lt;br&gt; ==<br /> <br /> === For Calls Forked by CUBE&lt;br&gt; ===<br /> <br /> For CUBE calls, Track 0 always maps to the Anchor leg media stream. The Anchor leg is the dial-peer which media recording profile is configured.&amp;nbsp; The second track maps to non-anchor leg. <br /> <br /> If you have media recording profile enabled on the&lt;span style=&quot;font-style: italic;&quot;&gt; &lt;/span&gt;''inbound ''dialpeer, then the anchor leg will be the in-leg. In other words, the calling party will be in Track 0, and the called party will be in Track 1.&lt;br&gt; <br /> <br /> If you have media recording profile enabled on the ''outbound ''dialpeer, then the anchor leg will be the out-leg.&amp;nbsp; In that case the calling party will be in Track 1, and the called party will be in Track 0.&lt;br&gt; <br /> <br /> === For Calls Forked by Unified CM Phones&lt;br&gt; ===<br /> <br /> For Unified CM forking, you can use the xRefCi fields in the metadata to determine which party is in which media track.&amp;nbsp; The numerically smaller xRefCi almost always refers to the calling party's track, and the called party's track will be numerically larger (usually by one, but it could be more under a reasonably loaded system). However, things start to get complicated once we get into conferencing and transferring. For some of those scenarios, additional CI's get generated and replaced when call legs are merged. <br /> <br /> That said, MediaSense only knows about a single pair of xRefCi values for any single recording session, and any supplementary service operations which generate new xRefCi values would also generate new recording sessions. So it is ok to assume that within a given session, the smaller xRefCi corresponds to the calling party, and the larger one corresponds to the called party. <br /> <br /> There is one additional caveat. The xRefCi values are assigned incrementally, and they eventually wrap around to zero. That means there is a 50/50 chance that the wrap-around will take place between tracks in the same call, in which case this numerical relationship will not hold.&lt;br&gt;&lt;br&gt; <br /> <br /> = What are the possible causes for a session state of CLOSED_ERROR?&lt;br&gt; =<br /> <br /> 1. Call control server got an error response from the Media (recording) server for the open or close request&lt;br&gt;2. Call control server detected a SIP signaling error, for example a missing ACK&lt;br&gt;3. Session was successfully closed, but ALL tracks have zero size <br /> <br /> When a session is in the ACTIVE state, it is normal that there is no duration in the metadata, because duration is not known until session is closed.&lt;br&gt; <br /> <br /> For a session which is in CLOSED_ERROR state, if either the session or track duration fields are not present in either the event or the getSessions data, then media for this track is not available.&lt;br&gt; <br /> <br /> = &lt;br&gt;What is the difference between Pruned and Deleted sessions?&lt;br&gt; =<br /> <br /> Consider the following two queries:&lt;br&gt; <br /> <br /> === Query 1: Using getAllPrunedSessions&lt;br&gt; ===<br /> &lt;pre&gt;https://10.192.252.171:8443/ora/queryService/query/getAllPrunedSessions?minSessionStartDate=1301788800000&amp;amp;maxSessionStartDate=1312329599000&lt;/pre&gt; <br /> This query returns a set of sessions, all of whose session states are DELETED.&lt;br&gt;&lt;br&gt; <br /> <br /> === Query 2: Using getSessions&lt;br&gt; ===<br /> &lt;pre&gt;https://10.192.252.171:8443/ora/queryService/query/getSessions<br /> {<br /> &quot;requestParameters&quot;: <br /> [{ <br /> &quot;fieldName&quot;&amp;nbsp;: &quot;sessionState&quot;, <br /> &quot;fieldConditions&quot;: <br /> [{ <br /> &quot;fieldOperator&quot;&amp;nbsp;: &quot;equals&quot;, <br /> &quot;fieldValues&quot;&amp;nbsp;: [ &quot;DELETED&quot; ] <br /> }],<br /> &quot;paramConnector&quot;&amp;nbsp;: &quot;AND&quot; <br /> },<br /> { <br /> &quot;fieldName&quot;&amp;nbsp;: &quot;sessionStartDate&quot;, <br /> &quot;fieldConditions&quot;: <br /> [{ <br /> &quot;fieldOperator&quot;&amp;nbsp;: &quot;between&quot;, <br /> &quot;fieldValues&quot;&amp;nbsp;: [ &quot;1301788800000&quot;, &quot;1312329599000&quot; ] <br /> }] <br /> }] <br /> }<br /> &lt;/pre&gt; <br /> This query returns no sessions at all.&lt;br&gt; <br /> <br /> === Why the difference?&lt;br&gt; ===<br /> <br /> This behavior is by design. Please refer to the following sections in the MediaSense Documentation: <br /> <br /> *The API Parameter Description: The getAllPrunedSessions API description:<br /> &lt;blockquote&gt;&quot;Use this API to search all pruned recordings. .... The term Pruned refers to recordings which are deleted by the Cisco MediaSense system. If you have explicitly deleted any recording using the deleteSessions API, then these deleted recordings are not considered as pruned recordings.&quot; &lt;/blockquote&gt; <br /> *The MediaSense SRND under the section &quot;Proactive Storage Management&quot;:<br /> &lt;blockquote&gt;&quot;When sessions are pruned, the metadata associated with those sessions remains in the database, though they are marked as &quot;pruned&quot;. This metadata does not take a large amount of storage space compared to the recordings themselves, but it does take some, and over time it will grow unbounded if not periodically cleaned up. .... Once these records are no longer needed, they should be periodically removed. &lt;/blockquote&gt;&lt;blockquote&gt;<br /> To aid in [this] activity, clients may periodically issue an API request for pruned sessions, or may elect to receive session pruned events, and explicitly delete those it no longer needs &quot; <br /> &lt;/blockquote&gt; <br /> To clarify, the two queries above are two entirely different queries. As a matter of fact, the second query (looking for all sessions whose state is &quot;DELETED&quot;) will ALWAYS return an empty set. Normal day-to-day queries filter out sessions whose state is DELETED (even if that is what is being asked for). The only exception is &quot;getAllPrunedSessions&quot;. This one is intended to assist the application in finding pruned sessions so that the application can request that these sessions really be deleted. <br /> <br /> Once you use the &quot;deleteSessions&quot; API on the list of pruned sessions you get from &quot;getAllPrunedSessions&quot;, these sessions will NO LONGER appear in the result of &quot;getAllPrunedSessions&quot;. Such sessions will be completely removed from the metadata within 24 hours. <br /> <br /> Another way to look at this is that &quot;pruned&quot; sessions are not the same thing as &quot;deleted&quot; sessions: <br /> <br /> *Pruned sessions are sessions that have been marked for removal by some algorithm in the MediaSense system. No person was involved in the decision to prune these sessions. So even though they are moved to the &quot;DELETED&quot; state, they will NOT actually be removed from the metadata. Human (or Application) intervention will be required. Because they are in the &quot;DELETED&quot; state, they will not be visible to most queries. However, these sessions WILL be visible to the &quot;getAllPrunedSessions&quot; query API. Also, if any mp4 files were generated for these sessions, they continue to be present on the disk and available for download until they are actually DELETED. <br /> *Deleted sessions are sessions that are marked for deletion by calling the &quot;deleteSessions&quot; API explicitly. This can be done to sessions that are already pruned or sessions that are not yet deleted at all. Once a session has been deleted by the deleteSessions API, it will not be visible to ANY query. This includes the getAllPrunedSessions API. These sessions will be removed from the metadata within 24 hours so that disk space can be reclaimed.&lt;br&gt;&lt;br&gt;<br /> <br /> &lt;br&gt; <br /> <br /> [[Category:Cisco_MediaSense]]</div>

Cchetty http://docwiki.cisco.com/wiki/Runtime:_MediaSense_server_is_unable_to_keep_up_with_incoming_recordings 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== MediaSense server is unable to keep up with incoming recordings ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | The Cisco MediaSense server is unable to keep up with the number of recordings it's supposed to capture.<br /> |-<br /> ! '''Error Message''' <br /> | None.<br /> |-<br /> ! '''Possible Cause''' <br /> | 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.<br /> |-<br /> ! '''Recommended Action''' <br /> | 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.<br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Installation:_Installation_halts_with_an_unrecoverable_error 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>&amp;nbsp; <br /> <br /> == The installation halts with an unrecoverable error ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | The installation fails with an unrecoverable error.&lt;br&gt;<br /> |-<br /> ! '''Error Message''' <br /> | Installation has encountered an unrecoverable internal error&lt;br&gt;<br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> The VM&amp;nbsp;Template or the VM&amp;nbsp;configuration does not meet the requirements. See [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all the Software Download page] for a list of supported VM&amp;nbsp;templates. <br /> <br /> See the&amp;nbsp;''Unified MCP-Specific Information for OVA Templates'' section in the&amp;nbsp;[[Virtualization for Cisco MediaSense]] website.&lt;br&gt;<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> Verify that the VM&amp;nbsp;configuration meets the minimum system requirements such as number of CPUs and other requirements specified in the read-me file for each supported VM&amp;nbsp;template. <br /> <br /> Cisco MediaSense, Release 8.5(2), only supports the VM templates listed in [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=8.5.1&amp;rellifecycle=&amp;relind=AVAILABLE&amp;reltype=all the Software Download page].&lt;br&gt;<br /> <br /> |-<br /> ! '''Release''' <br /> | Release 8.5(2) and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.&lt;br&gt;<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/General:_Performance_issues_as_a_result_of_hardware_failure 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Performance issues as a result of hardware failure ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | You may see performance issues (like recording errors) when a hardware failure has occurred.<br /> |-<br /> ! '''Error Message''' <br /> | None. You start seeing recording errors more frequently.<br /> |-<br /> ! '''Possible Cause''' <br /> | Hardware failures: For example, the disk drives attached to your host begin failing (most frequently seen).&lt;br&gt;<br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> Perform the following checks: &lt;br&gt;<br /> <br /> #Check the vSphere client. <br /> #Look for alarms generated against the VM host where you see the failure. <br /> #Replace the faulty hardware using the instructions applicable to your failure.<br /> <br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Database:_Database_not_updated_after_event_forwarding 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Database not updated after event forwarding ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | <br /> When a client receives an event that was forwarded from the other application server and immediately issues a query to the forwarding serverto get additional data related to the event, it does not see the updates that were reported in the event.<br /> <br /> |-<br /> ! '''Error Message''' <br /> | <br /> None.<br /> <br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> 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. <br /> <br /> 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. <br /> <br /> {{note| The forwarding node's database will be updated and the data will eventually be replicated.}}<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> If the recipient (client)&amp;nbsp;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.<br /> <br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/API:_Incorrect_participant_duration 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Incorrect participant duration ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | The far-end participant duration for the Session Query and Session Event APIs is incorrect.<br /> |-<br /> ! '''Error Message''' <br /> | None.<br /> |-<br /> ! '''Possible Cause''' <br /> | If a far-end participant is not present for the entire duration of a recording session, the duration response for that participant is incorrect.<br /> |-<br /> ! '''Recommended Action''' <br /> | At any time, a recording session can only have two participants: a near-end participant (identified by Track Number 0) and a far-end participant (any non-zero track number). Even in a conference scenario, only the conference bridge number is available to Cisco MediaSense. Consequently, if multiple participants are available in a bridge, Cisco MediaSense only displays one participant(identified by the isConference flag). <br /> The only way a participant list can be changed in a recording session is if the far-end participant performs a transfer or has a conference. If the near-end participant drops off or initiates a conference, the existing recording session terminates. <br /> <br /> So the workaround is to use the start time of a new far-end participant as the end time of the previous far-end participant and calculate the duration. <br /> <br /> Also use this workaround for SessionEvent to determine if a far-end participant (was) dropped from a recording session (and if so, at what time).<br /> <br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | [http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl47917 CSCtl47917]<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Print_Cisco_MediaSense_8.5_Troubleshooting_Tips 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back:''' [[Troubleshooting Tips for Cisco MediaSense 8.5]] <br /> <br /> === Create PDF for Cisco MediaSense Troubleshooting Tips ===<br /> <br /> {{Template:PDF_Print_Form|ROWS=45|DEFAULT_FILENAME=mcp85ts.pdf|BUTTON_LABEL=Create PDF|DEFAULT_TEXT=Troubleshooting Tips for Cisco MediaSense, Release 8.5 <br /> API: Incorrect participant duration<br /> API: Missing events and closed subscription<br /> API: Incorrect session or participant duration <br /> Administration: Administration Login returns unexpected error<br /> Administration: Unable to access Administration and Serviceability UI on a newly installed system<br /> Administration: Unknown request error display <br /> Configuration: Call between two RT phones is not recorded<br /> Configuration: Calls using g.722 codec are not recorded<br /> Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers<br /> Configuration: Conversation after a transfer is not recorded on RT-Lite phones<br /> Configuration: Failure to playback audio or video when using RT video phone<br /> Configuration: MediaSense application does not record even if recording is enabled <br /> Database: Database not updated after event forwarding<br /> Database: Database no longer accepts data <br /> General: Performance issues as a result of hardware failure<br /> General: RTSP live monitoring sessions fail when using CUBE<br /> Installation: Installation halts with an unrecoverable error <br /> Upgrade: Sync after switch version failed<br /> Upgrade: Data out of sync after upgrade <br /> Recording: QuickTime does not playback G.729 recording, but status bar keep moving <br /> RTMT: Unable to login to RTMT from the primary server <br /> Runtime: MediaSense server is unable to keep up with incoming recordings<br /> Runtime: Media server rejects open RTSP session<br /> Runtime: Open RTSP session to MediaSense failed with timeout<br /> Runtime: Close recording session failed with timeout <br /> }}</div>

Cchetty http://docwiki.cisco.com/wiki/Runtime:_Media_server_rejects_open_RTSP_session 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Media server rejects to open RTSP session ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | The Media Service rejects an RTSP request to open a session, if the DESCRIBE request is received before the first RTP packet.<br /> |-<br /> ! '''Error Message''' <br /> | In response to the RTSP DESCRIBE request, you receive the following error: <br /> &lt;code&gt;500 Server Error (Unable to open proxy)&amp;lt;code&amp;gt;&lt;/code&gt;<br /> <br /> |-<br /> ! '''Possible Cause''' <br /> | 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.<br /> |-<br /> ! '''Recommended Action''' <br /> | Repeat the DESCRIBE request.<br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Configuration:_Conversation_after_a_transfer_is_not_recorded_on_RT-Lite_phones 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Conversation after a transfer is not recorded on RT-Lite phones ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | No media streams are recorded after a transfer is completed using the RT-Lite (6961) phone with G.729.<br /> |-<br /> ! '''Error Message''' <br /> | None.<br /> |-<br /> ! '''Possible Cause''' <br /> | Phone load version is not supported.<br /> |-<br /> ! '''Recommended Action''' <br /> | Upgrade to the latest phone load.<br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Releae 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | CSCti71342.<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Configuration:_Call_between_two_RT_phones_is_not_recorded 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Call between two RT phones is not recorded ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | When a call is established between two RT phones (89XX and 99XX family), the call is not recorded by Unified MCP.<br /> |-<br /> ! '''Error Message''' <br /> | State of the recorded conversation is ERROR.<br /> |-<br /> ! '''Possible Cause''' <br /> | When a call is established between two RT phones (89XX and 99XX family), G722 codec is negotiated for the call. If G722 is disabled using service parameters, however, the 2 RT phones negotiate iSAC codec by default (Low Loss). Cisco MediaSense does not support G722 or iSAC codecs. Consequently, the call is not recorded.<br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> #Make sure to set up G729 codec for both of the RT phones OR <br /> #Install Unified CM 8.5(1)SU1 software update which allows you to disable iSAC codec for recording enabled devices AND&amp;nbsp;disable iSAC codec for recording enabled devices using the Unified CM Administration page.<br /> <br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | None.<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Administration:_Unable_to_access_Administration_and_Serviceability_UI_on_a_newly_installed_system 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Unable to access Administration and Serviceability UI on a newly installed system ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | 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.<br /> |-<br /> ! '''Error Message''' <br /> | Cannot contact the Server. Try again.<br /> |-<br /> ! '''Possible Cause''' <br /> | Cisco Security Agent intermittently blocks access to Ports 80 and 443.<br /> |-<br /> ! '''Recommended Action''' <br /> | Use port numbers as specified below: <br /> *HTTP URL for Administration: &lt;pre&gt;http://&amp;lt;ip address&amp;gt;:8080/oraadmin&lt;/pre&gt;<br /> *HTTP URL for Serviceability: &lt;pre&gt;http://&amp;lt;ip address&amp;gt;:8080/oraservice&lt;/pre&gt;<br /> *HTTPS URL for Administration: &lt;pre&gt;https://&amp;lt;ip address&amp;gt;:8443/oraadmin&lt;/pre&gt;<br /> *HTTPS URL for Serviceability: &lt;pre&gt;https://&amp;lt;ip address&amp;gt;:8443/oraservice&lt;/pre&gt;<br /> <br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), 8.5(2), and 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | CSCtj94150<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Administration:_Administration_Login_returns_unexpected_error 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>== Administration Login returns unexpected error ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> ! '''Problem Summary''' <br /> | Administrator is unable to log in to Cisco MediaSense Administration<br /> |-<br /> ! '''Error Message''' <br /> | Unexpected system error. Please contact your Administrator.<br /> |-<br /> ! '''Possible Cause''' <br /> | <br /> #Cisco MediaSense Database Service and Cisco MediaSense Configuration Service are not enabled(activated). <br /> #Cisco MediaSense Database Service and Cisco MediaSense Configuration Service are enabled but not running.<br /> <br /> |-<br /> ! '''Recommended Action''' <br /> | <br /> #Login to Cisco MediaSense Serviceability Administration and access the '''Tools''' &amp;gt; '''Service Activation'''. Verify that Cisco MediaSense Database Service and Cisco MediaSense Configuration Service are enabled. If they are not, then follow the procedure to enable both services. See the Installation and Administration guide for Cisco MediaSense to view the procedure. <br /> #Login to Cisco MediaSense Serviceability Administration and access the '''Tools''' &amp;gt; '''Service Activation'''. Verify that Cisco MediaSense Database Service and Cisco MediaSense Configuration Service are enabled. If they are, then access the '''Tools''' &amp;gt; '''Control Center-Feature Services''' and verify that the services are running. If they are not running, follow the procedure to start both services. See the Installation and Administration guide for Cisco MediaSense to view the procedure.&lt;br&gt;<br /> <br /> |-<br /> ! '''Release''' <br /> | Release 8.5(1), Release 8.5(2), and Release 8.5(3).<br /> |-<br /> ! '''Associated CDETS #''' <br /> | CSCtk11682 and CSCtk55457--both CDETS only apply to Release 8.5(1).<br /> |}<br /> <br /> [[Category:Cisco_MediaSense,_Release_8.5]]</div>

Cchetty http://docwiki.cisco.com/wiki/Troubleshooting_Tips_for_Cisco_MediaSense_8.5 2011-10-08T20:19:33Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back:''' [[Troubleshooting Cisco MediaSense]] <br /> <br /> '''Additional Troubleshooting Information''': [[Additional troubleshooting information for Cisco MediaSense 8.5]] <br /> <br /> '''Add tip:''' [[Create Contact Center Troubleshooting Tips]] <br /> <br /> '''Print PDF:''' [[Print Cisco MediaSense 8.5 Troubleshooting Tips]] <br /> <br /> ----<br /> <br /> {{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).'''}} <br /> <br /> ----<br /> <br /> The following tips were added by Cisco Documentation: <br /> <br /> == API ==<br /> <br /> *[[API: Incorrect participant duration]] <br /> *[[API: Missing events and closed subscription]] <br /> *[[API: Incorrect session or participant duration]]<br /> <br /> == Administration ==<br /> <br /> *[[Administration: Administration Login returns unexpected error]] <br /> *[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]] <br /> *[[Administration: Unknown request error display]]<br /> <br /> == Configuration ==<br /> <br /> *[[Configuration: Call between two RT phones is not recorded]] <br /> *[[Configuration: Calls using g.722 codec are not recorded]] <br /> *[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]] <br /> *[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]] <br /> *[[Configuration: Failure to playback audio or video when using RT video phone]] <br /> *[[Configuration: MediaSense application does not record even if recording is enabled]]<br /> <br /> == Database ==<br /> <br /> *[[Database: Database not updated after event forwarding]] <br /> *[[Database: Database no longer accepts data]]<br /> <br /> == General ==<br /> <br /> *[[General: Performance issues as a result of hardware failure]] <br /> *[[General: RTSP live monitoring sessions fail when using CUBE]]&lt;br&gt;<br /> <br /> == Installation ==<br /> <br /> *[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]<br /> <br /> == Upgrade ==<br /> <br /> *[[Upgrade: Sync after switch version failed]] <br /> *[[Upgrade: Data out of sync after upgrade]]<br /> <br /> == Recording ==<br /> <br /> *[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]<br /> <br /> == RTMT ==<br /> <br /> *[[RTMT: Unable to login to RTMT from the primary server]]<br /> <br /> == Runtime ==<br /> <br /> *[[Runtime: MediaSense server is unable to keep up with incoming recordings]] <br /> *[[Runtime: Media server rejects open RTSP session]] <br /> *[[Runtime: Open RTSP session to MediaSense failed with timeout]] <br /> *[[Runtime: Close recording session failed with timeout]]</div>

Cchetty http://docwiki.cisco.com/wiki/Metadata_vi 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;pre&gt;<br /> [<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionDuration&quot;:8592,<br /> &quot;sessionId&quot;:&quot;1e1328379957c1&quot;,<br /> &quot;sessionStartDate&quot;:1316465776246,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1e1328379957c1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:8592,<br /> &quot;participantStartDate&quot;:1316465776246,<br /> &quot;xRefCi&quot;:&quot;461328379957c1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465776258,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465776310,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:40,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:8592,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465776246<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1e1328379957c1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:8592,<br /> &quot;participantStartDate&quot;:1316465776246,<br /> &quot;xRefCi&quot;:&quot;451328379957c1&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:8592,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465776246<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/1e1328379957c1&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionId&quot;:&quot;1d132837961dc1&quot;,<br /> &quot;sessionStartDate&quot;:1316465763023,<br /> &quot;sessionState&quot;:&quot;ACTIVE&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantStartDate&quot;:1316465763023,<br /> &quot;xRefCi&quot;:&quot;44132837961dc1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465775904,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:12866,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465763040,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465763115,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:70,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465763023<br /> },<br /> {<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantStartDate&quot;:1316465763023,<br /> &quot;xRefCi&quot;:&quot;43132837961dc1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465763040,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465763023<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/live/1d132837961dc1&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionDuration&quot;:3397,<br /> &quot;sessionId&quot;:&quot;1c132837954991&quot;,<br /> &quot;sessionStartDate&quot;:1316465759613,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1c132837954991-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:3397,<br /> &quot;participantStartDate&quot;:1316465759613,<br /> &quot;xRefCi&quot;:&quot;42132837954991&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465762808,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:3169,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:3397,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465759613<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1c132837954991-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:3397,<br /> &quot;participantStartDate&quot;:1316465759613,<br /> &quot;xRefCi&quot;:&quot;41132837954991&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465762808,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:3169,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:3397,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465759613<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/1c132837954991&quot;<br /> }<br /> }<br /> ]<br /> &lt;/pre&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Event_vi 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;br&gt; <br /> &lt;pre&gt; {<br /> &quot;eventAction&quot;: &quot;STARTED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;: &quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionId&quot;: &quot;1c132837954991&quot;,<br /> &quot;sessionStartDate&quot;: 1316465759613,<br /> &quot;sessionState&quot;: &quot;ACTIVE&quot;,<br /> &quot;tracks&quot;: [<br /> {<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1057&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantStartDate&quot;: 1316465759613,<br /> &quot;xRefCi&quot;: &quot;42132837954991&quot;<br /> }],<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 1,<br /> &quot;trackStartDate&quot;: 1316465759613<br /> },<br /> {<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1053&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantStartDate&quot;: 1316465759613,<br /> &quot;xRefCi&quot;: &quot;41132837954991&quot;<br /> }],<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 0,<br /> &quot;trackStartDate&quot;: 1316465759613<br /> }<br /> ],<br /> &quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/1c132837954991&quot;}]<br /> },<br /> &quot;eventType&quot;: &quot;SESSION_EVENT&quot;<br /> }<br /> ---<br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1c132837954991&quot;,<br /> &quot;tagCreateDate&quot;: 1316465762808,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 3169,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 0<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1c132837954991&quot;,<br /> &quot;tagCreateDate&quot;: 1316465762808,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 3169,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 1<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ENDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;: &quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionDuration&quot;: 3397,<br /> &quot;sessionId&quot;: &quot;1c132837954991&quot;,<br /> &quot;sessionStartDate&quot;: 1316465759613,<br /> &quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;: [<br /> {<br /> &quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1c132837954991-TRACK1&quot;,<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1057&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantDuration&quot;: 3397,<br /> &quot;participantStartDate&quot;: 1316465759613,<br /> &quot;xRefCi&quot;: &quot;42132837954991&quot;<br /> }],<br /> &quot;tags&quot;: [{<br /> &quot;tagCreateDate&quot;: 1316465762808,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 3169,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;<br /> }],<br /> &quot;trackDuration&quot;: 3397,<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 1,<br /> &quot;trackStartDate&quot;: 1316465759613<br /> },<br /> {<br /> &quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1c132837954991-TRACK0&quot;,<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1053&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantDuration&quot;: 3397,<br /> &quot;participantStartDate&quot;: 1316465759613,<br /> &quot;xRefCi&quot;: &quot;41132837954991&quot;<br /> }],<br /> &quot;tags&quot;: [{<br /> &quot;tagCreateDate&quot;: 1316465762808,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 3169,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;<br /> }],<br /> &quot;trackDuration&quot;: 3397,<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 0,<br /> &quot;trackStartDate&quot;: 1316465759613<br /> }<br /> ],<br /> &quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/1c132837954991&quot;}]<br /> },<br /> &quot;eventType&quot;: &quot;SESSION_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;STARTED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;: &quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionId&quot;: &quot;1d132837961dc1&quot;,<br /> &quot;sessionStartDate&quot;: 1316465763023,<br /> &quot;sessionState&quot;: &quot;ACTIVE&quot;,<br /> &quot;tracks&quot;: [<br /> {<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1057&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantStartDate&quot;: 1316465763023,<br /> &quot;xRefCi&quot;: &quot;44132837961dc1&quot;<br /> }],<br /> &quot;tags&quot;: [{<br /> &quot;tagCreateDate&quot;: 1316465763040,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 0,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;<br /> }],<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 1,<br /> &quot;trackStartDate&quot;: 1316465763023<br /> },<br /> {<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1053&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantStartDate&quot;: 1316465763023,<br /> &quot;xRefCi&quot;: &quot;43132837961dc1&quot;<br /> }],<br /> &quot;tags&quot;: [{<br /> &quot;tagCreateDate&quot;: 1316465763040,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 0,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;<br /> }],<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 0,<br /> &quot;trackStartDate&quot;: 1316465763023<br /> }<br /> ],<br /> &quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/1d132837961dc1&quot;}]<br /> },<br /> &quot;eventType&quot;: &quot;SESSION_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1d132837961dc1&quot;,<br /> &quot;tagCreateDate&quot;: 1316465763040,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 0,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 0<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1d132837961dc1&quot;,<br /> &quot;tagCreateDate&quot;: 1316465763040,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 0,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 1<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1d132837961dc1&quot;,<br /> &quot;tagCreateDate&quot;: 1316465763115,<br /> &quot;tagName&quot;: &quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;: 70,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 1<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1d132837961dc1&quot;,<br /> &quot;tagCreateDate&quot;: 1316465775904,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 12866,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 1<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;STARTED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;: &quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionId&quot;: &quot;1e1328379957c1&quot;,<br /> &quot;sessionStartDate&quot;: 1316465776246,<br /> &quot;sessionState&quot;: &quot;ACTIVE&quot;,<br /> &quot;tracks&quot;: [<br /> {<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1057&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantStartDate&quot;: 1316465776246,<br /> &quot;xRefCi&quot;: &quot;461328379957c1&quot;<br /> }],<br /> &quot;tags&quot;: [{<br /> &quot;tagCreateDate&quot;: 1316465776258,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 0,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;<br /> }],<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 1,<br /> &quot;trackStartDate&quot;: 1316465776246<br /> },<br /> {<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1053&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantStartDate&quot;: 1316465776246,<br /> &quot;xRefCi&quot;: &quot;451328379957c1&quot;<br /> }],<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 0,<br /> &quot;trackStartDate&quot;: 1316465776246<br /> }<br /> ],<br /> &quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/1e1328379957c1&quot;}]<br /> },<br /> &quot;eventType&quot;: &quot;SESSION_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1e1328379957c1&quot;,<br /> &quot;tagCreateDate&quot;: 1316465776258,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 0,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 1<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ADDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;sessionId&quot;: &quot;1e1328379957c1&quot;,<br /> &quot;tagCreateDate&quot;: 1316465776310,<br /> &quot;tagName&quot;: &quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;: 40,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,<br /> &quot;trackNumber&quot;: 1<br /> },<br /> &quot;eventType&quot;: &quot;TAG_EVENT&quot;<br /> }<br /> ---<br /> <br /> {<br /> &quot;eventAction&quot;: &quot;ENDED&quot;,<br /> &quot;eventBody&quot;: {<br /> &quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;: &quot;3303966848-0000065536-0000005907-0745980426&quot;,<br /> &quot;sessionDuration&quot;: 8592,<br /> &quot;sessionId&quot;: &quot;1e1328379957c1&quot;,<br /> &quot;sessionStartDate&quot;: 1316465776246,<br /> &quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;: [<br /> {<br /> &quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1e1328379957c1-TRACK1&quot;,<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1057&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantDuration&quot;: 8592,<br /> &quot;participantStartDate&quot;: 1316465776246,<br /> &quot;xRefCi&quot;: &quot;461328379957c1&quot;<br /> }],<br /> &quot;tags&quot;: [<br /> {<br /> &quot;tagCreateDate&quot;: 1316465776258,<br /> &quot;tagName&quot;: &quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;: 0,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;: 1316465776310,<br /> &quot;tagName&quot;: &quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;: 40,<br /> &quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;: 8592,<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 1,<br /> &quot;trackStartDate&quot;: 1316465776246<br /> },<br /> {<br /> &quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1e1328379957c1-TRACK0&quot;,<br /> &quot;participants&quot;: [{<br /> &quot;deviceRef&quot;: &quot;1053&quot;,<br /> &quot;isConference&quot;: false,<br /> &quot;participantDuration&quot;: 8592,<br /> &quot;participantStartDate&quot;: 1316465776246,<br /> &quot;xRefCi&quot;: &quot;451328379957c1&quot;<br /> }],<br /> &quot;trackDuration&quot;: 8592,<br /> &quot;trackMediaType&quot;: &quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;: 0,<br /> &quot;trackStartDate&quot;: 1316465776246<br /> }<br /> ],<br /> &quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/1e1328379957c1&quot;}]<br /> },<br /> &quot;eventType&quot;: &quot;SESSION_EVENT&quot;<br /> } <br /> &lt;/pre&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Metadata_v 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;pre&gt;<br /> [<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3578934144-0000065536-0000005906-0745980426&quot;,<br /> &quot;sessionDuration&quot;:8171,<br /> &quot;sessionId&quot;:&quot;1b13283735ea81&quot;,<br /> &quot;sessionStartDate&quot;:1316465368977,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1b13283735ea81-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1054&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:8171,<br /> &quot;participantStartDate&quot;:1316465368977,<br /> &quot;xRefCi&quot;:&quot;3f13283735ea81&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465369050,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:49,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465368983,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:8171,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465368977<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1b13283735ea81-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:8171,<br /> &quot;participantStartDate&quot;:1316465368977,<br /> &quot;xRefCi&quot;:&quot;3e13283735ea81&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465369049,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:49,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465368983,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:8171,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465368977<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/1b13283735ea81&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3578934144-0000065536-0000005906-0745980426&quot;,<br /> &quot;sessionDuration&quot;:9433,<br /> &quot;sessionId&quot;:&quot;1a132837339ac1&quot;,<br /> &quot;sessionStartDate&quot;:1316465359523,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1a132837339ac1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1054&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:9433,<br /> &quot;participantStartDate&quot;:1316465359523,<br /> &quot;xRefCi&quot;:&quot;3c132837339ad1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465368654,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:9121,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:9433,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465359523<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1a132837339ac1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:9133,<br /> &quot;participantStartDate&quot;:1316465359523,<br /> &quot;xRefCi&quot;:&quot;3b132837339ad1&quot;<br /> },<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:300,<br /> &quot;participantStartDate&quot;:1316465368656,<br /> &quot;xRefCi&quot;:&quot;3d13283735e501&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465359674,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:120,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465359532,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465368654,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:9121,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:9433,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465359523<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/1a132837339ac1&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3398934144-0000065536-0000005905-0745980426&quot;,<br /> &quot;sessionDuration&quot;:23634,<br /> &quot;sessionId&quot;:&quot;19132837322321&quot;,<br /> &quot;sessionStartDate&quot;:1316465353505,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=19132837322321-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1054&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:8389,<br /> &quot;participantStartDate&quot;:1316465368750,<br /> &quot;xRefCi&quot;:&quot;4013283735eae1&quot;<br /> },<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:15245,<br /> &quot;participantStartDate&quot;:1316465353505,<br /> &quot;xRefCi&quot;:&quot;3a132837322321&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465353518,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465368666,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:15142,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465353589,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:60,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465368818,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:15297,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:23634,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465353505<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=19132837322321-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:23634,<br /> &quot;participantStartDate&quot;:1316465353505,<br /> &quot;xRefCi&quot;:&quot;39132837322321&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465353518,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465368818,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:15297,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:23634,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465353505<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/19132837322321&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3398934144-0000065536-0000005905-0745980426&quot;,<br /> &quot;sessionDuration&quot;:13813,<br /> &quot;sessionId&quot;:&quot;181328372ec3c1&quot;,<br /> &quot;sessionStartDate&quot;:1316465339674,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=181328372ec3c1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:13813,<br /> &quot;participantStartDate&quot;:1316465339674,<br /> &quot;xRefCi&quot;:&quot;381328372ec3c1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465353287,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:13588,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:13813,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465339674<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=181328372ec3c1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:13813,<br /> &quot;participantStartDate&quot;:1316465339674,<br /> &quot;xRefCi&quot;:&quot;371328372ec3c1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465353287,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:13588,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:13813,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465339674<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/181328372ec3c1&quot;<br /> }<br /> }<br /> ]<br /> &lt;/pre&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Event_v 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3398934144-0000065536-0000005905-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;181328372ec3c1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465339674,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465339674,&lt;br&gt;&quot;xRefCi&quot;: &quot;381328372ec3c1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465339674&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465339674,&lt;br&gt;&quot;xRefCi&quot;: &quot;371328372ec3c1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465339674&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/181328372ec3c1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---&lt;br&gt;{&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;181328372ec3c1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353287,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 13588,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;181328372ec3c1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353287,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 13588,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3398934144-0000065536-0000005905-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 13813,&lt;br&gt;&quot;sessionId&quot;: &quot;181328372ec3c1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465339674,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=181328372ec3c1-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 13813,&lt;br&gt;&quot;participantStartDate&quot;: 1316465339674,&lt;br&gt;&quot;xRefCi&quot;: &quot;381328372ec3c1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353287,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 13588,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 13813,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465339674&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=181328372ec3c1-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 13813,&lt;br&gt;&quot;participantStartDate&quot;: 1316465339674,&lt;br&gt;&quot;xRefCi&quot;: &quot;371328372ec3c1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353287,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 13588,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 13813,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465339674&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/181328372ec3c1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3398934144-0000065536-0000005905-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465353505,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465353505,&lt;br&gt;&quot;xRefCi&quot;: &quot;3a132837322321&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465353505&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465353505,&lt;br&gt;&quot;xRefCi&quot;: &quot;39132837322321&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465353505&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/19132837322321&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353589,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 60,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3578934144-0000065536-0000005906-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;1a132837339ac1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465359523,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465359523,&lt;br&gt;&quot;xRefCi&quot;: &quot;3c132837339ad1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465359523&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465359523,&lt;br&gt;&quot;xRefCi&quot;: &quot;3b132837339ad1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465359532,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465359523&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/1a132837339ac1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1a132837339ac1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465359532,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1a132837339ac1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465359674,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 120,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1a132837339ac1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368654,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 9121,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1a132837339ac1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368654,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 9121,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368666,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 15142,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;UPDATED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3578934144-0000065536-0000005906-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;1a132837339ac1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465359523,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465359523,&lt;br&gt;&quot;xRefCi&quot;: &quot;3c132837339ad1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368654,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 9121,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465359523&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 9133,&lt;br&gt;&quot;participantStartDate&quot;: 1316465359523,&lt;br&gt;&quot;xRefCi&quot;: &quot;3b132837339ad1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368656,&lt;br&gt;&quot;xRefCi&quot;: &quot;3d13283735e501&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465359674,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 120,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465359532,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368654,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 9121,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465359523&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/1a132837339ac1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;UPDATED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3398934144-0000065536-0000005905-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465353505,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368750,&lt;br&gt;&quot;xRefCi&quot;: &quot;4013283735eae1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 15245,&lt;br&gt;&quot;participantStartDate&quot;: 1316465353505,&lt;br&gt;&quot;xRefCi&quot;: &quot;3a132837322321&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368666,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 15142,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353589,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 60,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465353505&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465353505,&lt;br&gt;&quot;xRefCi&quot;: &quot;39132837322321&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465353505&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/19132837322321&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368818,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 15297,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368818,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 15297,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3578934144-0000065536-0000005906-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 9433,&lt;br&gt;&quot;sessionId&quot;: &quot;1a132837339ac1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465359523,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1a132837339ac1-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 9433,&lt;br&gt;&quot;participantStartDate&quot;: 1316465359523,&lt;br&gt;&quot;xRefCi&quot;: &quot;3c132837339ad1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368654,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 9121,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 9433,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465359523&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1a132837339ac1-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 9133,&lt;br&gt;&quot;participantStartDate&quot;: 1316465359523,&lt;br&gt;&quot;xRefCi&quot;: &quot;3b132837339ad1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 300,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368656,&lt;br&gt;&quot;xRefCi&quot;: &quot;3d13283735e501&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465359674,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 120,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465359532,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368654,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 9121,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 9433,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465359523&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/1a132837339ac1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3578934144-0000065536-0000005906-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;1b13283735ea81&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465368977,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368977,&lt;br&gt;&quot;xRefCi&quot;: &quot;3f13283735ea81&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368983,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465368977&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368977,&lt;br&gt;&quot;xRefCi&quot;: &quot;3e13283735ea81&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368983,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465368977&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/1b13283735ea81&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1b13283735ea81&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368983,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1b13283735ea81&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368983,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1b13283735ea81&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465369049,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 49,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;1b13283735ea81&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465369050,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 49,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3398934144-0000065536-0000005905-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 23634,&lt;br&gt;&quot;sessionId&quot;: &quot;19132837322321&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465353505,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=19132837322321-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 8389,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368750,&lt;br&gt;&quot;xRefCi&quot;: &quot;4013283735eae1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 15245,&lt;br&gt;&quot;participantStartDate&quot;: 1316465353505,&lt;br&gt;&quot;xRefCi&quot;: &quot;3a132837322321&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368666,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 15142,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353589,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 60,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368818,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 15297,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 23634,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465353505&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=19132837322321-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 23634,&lt;br&gt;&quot;participantStartDate&quot;: 1316465353505,&lt;br&gt;&quot;xRefCi&quot;: &quot;39132837322321&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465353518,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368818,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 15297,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 23634,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465353505&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/19132837322321&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3578934144-0000065536-0000005906-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 8171,&lt;br&gt;&quot;sessionId&quot;: &quot;1b13283735ea81&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465368977,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1b13283735ea81-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 8171,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368977,&lt;br&gt;&quot;xRefCi&quot;: &quot;3f13283735ea81&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465369050,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 49,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368983,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 8171,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465368977&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=1b13283735ea81-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 8171,&lt;br&gt;&quot;participantStartDate&quot;: 1316465368977,&lt;br&gt;&quot;xRefCi&quot;: &quot;3e13283735ea81&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465369049,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 49,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465368983,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 8171,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465368977&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/1b13283735ea81&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}<br /> <br /> &lt;br&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Metadata_iv 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;pre&gt;<br /> [<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;0798934144-0000065536-0000005904-0745980426&quot;,<br /> &quot;sessionDuration&quot;:22807,<br /> &quot;sessionId&quot;:&quot;17132836f04691&quot;,<br /> &quot;sessionStartDate&quot;:1316465083735,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=17132836f04691-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1054&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:11922,<br /> &quot;participantStartDate&quot;:1316465094620,<br /> &quot;xRefCi&quot;:&quot;36132836f2fdc1&quot;<br /> },<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:10885,<br /> &quot;participantStartDate&quot;:1316465083735,<br /> &quot;xRefCi&quot;:&quot;35132836f04691&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465094688,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:10938,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465094522,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:10779,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465083807,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:50,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465083742,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:22807,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465083735<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=17132836f04691-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:22807,<br /> &quot;participantStartDate&quot;:1316465083735,<br /> &quot;xRefCi&quot;:&quot;34132836f04691&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465094637,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:10893,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316465083742,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:22807,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465083735<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/17132836f04691&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;0798934144-0000065536-0000005904-0745980426&quot;,<br /> &quot;sessionDuration&quot;:3864,<br /> &quot;sessionId&quot;:&quot;16132836ef54b1&quot;,<br /> &quot;sessionStartDate&quot;:1316465079856,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=16132836ef54b1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:3864,<br /> &quot;participantStartDate&quot;:1316465079856,<br /> &quot;xRefCi&quot;:&quot;33132836ef54b1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465083515,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:3633,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:3864,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316465079856<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=16132836ef54b1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:3864,<br /> &quot;participantStartDate&quot;:1316465079856,<br /> &quot;xRefCi&quot;:&quot;32132836ef54b1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316465083515,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:3633,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:3864,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316465079856<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/16132836ef54b1&quot;<br /> }<br /> }<br /> ]<br /> &lt;/pre&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Event_iv 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0798934144-0000065536-0000005904-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;16132836ef54b1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465079856,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465079856,&lt;br&gt;&quot;xRefCi&quot;: &quot;33132836ef54b1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465079856&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465079856,&lt;br&gt;&quot;xRefCi&quot;: &quot;32132836ef54b1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465079856&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/16132836ef54b1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---&lt;br&gt;{&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;16132836ef54b1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083515,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3633,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;16132836ef54b1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083515,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3633,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0798934144-0000065536-0000005904-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 3864,&lt;br&gt;&quot;sessionId&quot;: &quot;16132836ef54b1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465079856,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=16132836ef54b1-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 3864,&lt;br&gt;&quot;participantStartDate&quot;: 1316465079856,&lt;br&gt;&quot;xRefCi&quot;: &quot;33132836ef54b1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083515,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3633,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 3864,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465079856&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=16132836ef54b1-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 3864,&lt;br&gt;&quot;participantStartDate&quot;: 1316465079856,&lt;br&gt;&quot;xRefCi&quot;: &quot;32132836ef54b1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083515,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3633,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 3864,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465079856&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/16132836ef54b1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0798934144-0000065536-0000005904-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465083735,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465083735,&lt;br&gt;&quot;xRefCi&quot;: &quot;35132836f04691&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465083735&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465083735,&lt;br&gt;&quot;xRefCi&quot;: &quot;34132836f04691&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465083735&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/17132836f04691&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083807,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 50,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094522,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10779,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;UPDATED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0798934144-0000065536-0000005904-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465083735,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465094620,&lt;br&gt;&quot;xRefCi&quot;: &quot;36132836f2fdc1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 10885,&lt;br&gt;&quot;participantStartDate&quot;: 1316465083735,&lt;br&gt;&quot;xRefCi&quot;: &quot;35132836f04691&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094522,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10779,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083807,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 50,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465083735&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316465083735,&lt;br&gt;&quot;xRefCi&quot;: &quot;34132836f04691&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094637,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10893,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465083735&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/17132836f04691&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094637,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10893,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094688,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10938,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0798934144-0000065536-0000005904-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 22807,&lt;br&gt;&quot;sessionId&quot;: &quot;17132836f04691&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316465083735,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=17132836f04691-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 11922,&lt;br&gt;&quot;participantStartDate&quot;: 1316465094620,&lt;br&gt;&quot;xRefCi&quot;: &quot;36132836f2fdc1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 10885,&lt;br&gt;&quot;participantStartDate&quot;: 1316465083735,&lt;br&gt;&quot;xRefCi&quot;: &quot;35132836f04691&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094688,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10938,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094522,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10779,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083807,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 50,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 22807,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316465083735&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=17132836f04691-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 22807,&lt;br&gt;&quot;participantStartDate&quot;: 1316465083735,&lt;br&gt;&quot;xRefCi&quot;: &quot;34132836f04691&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465094637,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 10893,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316465083742,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 22807,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316465083735&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/17132836f04691&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}</div>

Cchetty http://docwiki.cisco.com/wiki/Metadata_iii 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;pre&gt;<br /> [<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3233901440-0000065536-0000005903-0745980426&quot;,<br /> &quot;sessionDuration&quot;:12139,<br /> &quot;sessionId&quot;:&quot;15132836c7c4f1&quot;,<br /> &quot;sessionStartDate&quot;:1316464917846,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=15132836c7c4f1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:12139,<br /> &quot;participantStartDate&quot;:1316464917846,<br /> &quot;xRefCi&quot;:&quot;31132836c7c4f1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464917929,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:53,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464917851,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:12139,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316464917846<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=15132836c7c4f1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:12139,<br /> &quot;participantStartDate&quot;:1316464917846,<br /> &quot;xRefCi&quot;:&quot;30132836c7c4f1&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:12139,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316464917846<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/15132836c7c4f1&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;3233901440-0000065536-0000005903-0745980426&quot;,<br /> &quot;sessionDuration&quot;:23207,<br /> &quot;sessionId&quot;:&quot;14132836c21921&quot;,<br /> &quot;sessionStartDate&quot;:1316464894597,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=14132836c21921-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1054&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:23207,<br /> &quot;participantStartDate&quot;:1316464894597,<br /> &quot;xRefCi&quot;:&quot;2f132836c219a1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464901033,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:6426,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464900974,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:6368,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464917393,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:22786,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:23207,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316464894597<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=14132836c21921-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:23207,<br /> &quot;participantStartDate&quot;:1316464894597,<br /> &quot;xRefCi&quot;:&quot;2e132836c219a1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464894740,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:118,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464894602,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464900974,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:6368,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:23207,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316464894597<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/14132836c21921&quot;<br /> }<br /> }<br /> ]<br /> &lt;/pre&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Event_iii 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3233901440-0000065536-0000005903-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464894597,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464894597,&lt;br&gt;&quot;xRefCi&quot;: &quot;2f132836c219a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464894597&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464894597,&lt;br&gt;&quot;xRefCi&quot;: &quot;2e132836c219a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464894602,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464894597&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/14132836c21921&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---&lt;br&gt;{&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464894602,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464894740,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 118,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464900974,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 6368,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464900974,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 6368,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464901033,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 6426,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464917393,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 22786,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3233901440-0000065536-0000005903-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 23207,&lt;br&gt;&quot;sessionId&quot;: &quot;14132836c21921&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464894597,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=14132836c21921-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 23207,&lt;br&gt;&quot;participantStartDate&quot;: 1316464894597,&lt;br&gt;&quot;xRefCi&quot;: &quot;2f132836c219a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464901033,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 6426,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464900974,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 6368,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464917393,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 22786,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 23207,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464894597&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=14132836c21921-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 23207,&lt;br&gt;&quot;participantStartDate&quot;: 1316464894597,&lt;br&gt;&quot;xRefCi&quot;: &quot;2e132836c219a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464894740,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 118,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464894602,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464900974,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 6368,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 23207,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464894597&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/14132836c21921&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3233901440-0000065536-0000005903-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;15132836c7c4f1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464917846,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464917846,&lt;br&gt;&quot;xRefCi&quot;: &quot;31132836c7c4f1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464917851,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464917846&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464917846,&lt;br&gt;&quot;xRefCi&quot;: &quot;30132836c7c4f1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464917846&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/15132836c7c4f1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;15132836c7c4f1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464917851,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;15132836c7c4f1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464917929,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 53,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;3233901440-0000065536-0000005903-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 12139,&lt;br&gt;&quot;sessionId&quot;: &quot;15132836c7c4f1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464917846,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=15132836c7c4f1-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 12139,&lt;br&gt;&quot;participantStartDate&quot;: 1316464917846,&lt;br&gt;&quot;xRefCi&quot;: &quot;31132836c7c4f1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464917929,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 53,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464917851,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 12139,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464917846&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=15132836c7c4f1-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 12139,&lt;br&gt;&quot;participantStartDate&quot;: 1316464917846,&lt;br&gt;&quot;xRefCi&quot;: &quot;30132836c7c4f1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 12139,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464917846&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/15132836c7c4f1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}</div>

Cchetty http://docwiki.cisco.com/wiki/Metadata_ii 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;pre&gt;<br /> [<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;0573901440-0000065536-0000005902-0745980426&quot;,<br /> &quot;sessionDuration&quot;:13543,<br /> &quot;sessionId&quot;:&quot;131328368278a1&quot;,<br /> &quot;sessionStartDate&quot;:1316464633992,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=131328368278a1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:3497,<br /> &quot;participantStartDate&quot;:1316464633992,<br /> &quot;xRefCi&quot;:&quot;2c1328368278a1&quot;<br /> },<br /> {<br /> &quot;deviceRef&quot;:&quot;1054&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:10046,<br /> &quot;participantStartDate&quot;:1316464637489,<br /> &quot;xRefCi&quot;:&quot;2d132836836311&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464639778,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:5777,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464633998,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464634076,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:62,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464637553,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:3546,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464637410,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:3410,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464639890,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:5885,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:13543,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316464633992<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=131328368278a1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:13543,<br /> &quot;participantStartDate&quot;:1316464633992,<br /> &quot;xRefCi&quot;:&quot;2b1328368278a1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464633998,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464639844,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:5835,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:13543,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316464633992<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/131328368278a1&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;0573901440-0000065536-0000005902-0745980426&quot;,<br /> &quot;sessionDuration&quot;:5801,<br /> &quot;sessionId&quot;:&quot;12132836810ee1&quot;,<br /> &quot;sessionStartDate&quot;:1316464628174,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=12132836810ee1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:5801,<br /> &quot;participantStartDate&quot;:1316464628174,<br /> &quot;xRefCi&quot;:&quot;2a132836810ee1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464633733,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:5533,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:5801,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316464628174<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=12132836810ee1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:5801,<br /> &quot;participantStartDate&quot;:1316464628174,<br /> &quot;xRefCi&quot;:&quot;29132836810ee1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464633732,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:5533,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:5801,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316464628174<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/12132836810ee1&quot;<br /> }<br /> }<br /> ]<br /> &lt;/pre&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Event_ii 2011-10-08T20:19:32Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;br&gt;{&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0573901440-0000065536-0000005902-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;12132836810ee1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464628174,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464628174,&lt;br&gt;&quot;xRefCi&quot;: &quot;2a132836810ee1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464628174&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464628174,&lt;br&gt;&quot;xRefCi&quot;: &quot;29132836810ee1&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464628174&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/12132836810ee1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---&lt;br&gt;{&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;12132836810ee1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633732,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5533,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;12132836810ee1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633733,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5533,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0573901440-0000065536-0000005902-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 5801,&lt;br&gt;&quot;sessionId&quot;: &quot;12132836810ee1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464628174,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=12132836810ee1-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 5801,&lt;br&gt;&quot;participantStartDate&quot;: 1316464628174,&lt;br&gt;&quot;xRefCi&quot;: &quot;2a132836810ee1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633733,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5533,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 5801,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464628174&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=12132836810ee1-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 5801,&lt;br&gt;&quot;participantStartDate&quot;: 1316464628174,&lt;br&gt;&quot;xRefCi&quot;: &quot;29132836810ee1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633732,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5533,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackDuration&quot;: 5801,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464628174&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/12132836810ee1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;STARTED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0573901440-0000065536-0000005902-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464633992,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464633992,&lt;br&gt;&quot;xRefCi&quot;: &quot;2c1328368278a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464633992&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464633992,&lt;br&gt;&quot;xRefCi&quot;: &quot;2b1328368278a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464633992&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/131328368278a1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464634076,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 62,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464637410,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3410,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;UPDATED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0573901440-0000065536-0000005902-0745980426&quot;,&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464633992,&lt;br&gt;&quot;sessionState&quot;: &quot;ACTIVE&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 3497,&lt;br&gt;&quot;participantStartDate&quot;: 1316464633992,&lt;br&gt;&quot;xRefCi&quot;: &quot;2c1328368278a1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464637489,&lt;br&gt;&quot;xRefCi&quot;: &quot;2d132836836311&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464634076,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 62,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464637410,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3410,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464633992&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantStartDate&quot;: 1316464633992,&lt;br&gt;&quot;xRefCi&quot;: &quot;2b1328368278a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}],&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464633992&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/live/131328368278a1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464637553,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3546,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464639778,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5777,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464639844,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5835,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ADDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;tagCreateDate&quot;: 1316464639890,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5885,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;TAG_EVENT&quot;&lt;br&gt;}&lt;br&gt;---<br /> <br /> {&lt;br&gt;&quot;eventAction&quot;: &quot;ENDED&quot;,&lt;br&gt;&quot;eventBody&quot;: {&lt;br&gt;&quot;callControllerIP&quot;: &quot;172.27.98.111&quot;,&lt;br&gt;&quot;callControllerType&quot;: &quot;Cisco-SIPGateway&quot;,&lt;br&gt;&quot;ccid&quot;: &quot;0573901440-0000065536-0000005902-0745980426&quot;,&lt;br&gt;&quot;sessionDuration&quot;: 13543,&lt;br&gt;&quot;sessionId&quot;: &quot;131328368278a1&quot;,&lt;br&gt;&quot;sessionStartDate&quot;: 1316464633992,&lt;br&gt;&quot;sessionState&quot;: &quot;CLOSED_NORMAL&quot;,&lt;br&gt;&quot;tracks&quot;: [&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=131328368278a1-TRACK1&quot;,&lt;br&gt;&quot;participants&quot;: [&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1057&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 3497,&lt;br&gt;&quot;participantStartDate&quot;: 1316464633992,&lt;br&gt;&quot;xRefCi&quot;: &quot;2c1328368278a1&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;deviceRef&quot;: &quot;1054&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 10046,&lt;br&gt;&quot;participantStartDate&quot;: 1316464637489,&lt;br&gt;&quot;xRefCi&quot;: &quot;2d132836836311&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464639778,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5777,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464634076,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 62,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464637553,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3546,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464637410,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 3410,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464639890,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5885,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 13543,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 1,&lt;br&gt;&quot;trackStartDate&quot;: 1316464633992&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;downloadUrl&quot;: &quot;http://10.194.118.63:8081/ExportRaw?recording=131328368278a1-TRACK0&quot;,&lt;br&gt;&quot;participants&quot;: [{&lt;br&gt;&quot;deviceRef&quot;: &quot;1053&quot;,&lt;br&gt;&quot;isConference&quot;: false,&lt;br&gt;&quot;participantDuration&quot;: 13543,&lt;br&gt;&quot;participantStartDate&quot;: 1316464633992,&lt;br&gt;&quot;xRefCi&quot;: &quot;2b1328368278a1&quot;&lt;br&gt;}],&lt;br&gt;&quot;tags&quot;: [&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464633998,&lt;br&gt;&quot;tagName&quot;: &quot;TrackInactive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 0,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;},&lt;br&gt;{&lt;br&gt;&quot;tagCreateDate&quot;: 1316464639844,&lt;br&gt;&quot;tagName&quot;: &quot;TrackActive&quot;,&lt;br&gt;&quot;tagOffset&quot;: 5835,&lt;br&gt;&quot;tagType&quot;: &quot;SYSTEM_DEFINED&quot;&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;trackDuration&quot;: 13543,&lt;br&gt;&quot;trackMediaType&quot;: &quot;AUDIO&quot;,&lt;br&gt;&quot;trackNumber&quot;: 0,&lt;br&gt;&quot;trackStartDate&quot;: 1316464633992&lt;br&gt;}&lt;br&gt;],&lt;br&gt;&quot;urls&quot;: [{&quot;rtspUrl&quot;: &quot;rtsp://10.194.118.63/archive/131328368278a1&quot;}]&lt;br&gt;},&lt;br&gt;&quot;eventType&quot;: &quot;SESSION_EVENT&quot;&lt;br&gt;}&lt;br&gt;</div>

Cchetty http://docwiki.cisco.com/wiki/Metadata_i 2011-10-08T20:19:31Z

<p>Cchetty: 1 revision</p> <hr /> <div>'''Back to: '''[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']] <br /> <br /> '''Back to: '''[[Deployment Scenarios for Cisco MediaSense|'''Deployment Scenarios for Cisco MediaSense''']] <br /> <br /> '''Back to: '''[[:category:Cisco MediaSense|'''category:Cisco MediaSense''']] <br /> <br /> ----<br /> <br /> &lt;pre&gt;<br /> [<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;0398868736-0000065536-0000005901-0745980426&quot;,<br /> &quot;sessionDuration&quot;:10536,<br /> &quot;sessionId&quot;:&quot;111328361659f1&quot;,<br /> &quot;sessionStartDate&quot;:1316464191126,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=111328361659f1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:10536,<br /> &quot;participantStartDate&quot;:1316464191126,<br /> &quot;xRefCi&quot;:&quot;281328361659f1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464191242,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:84,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464191149,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:10536,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316464191126<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=111328361659f1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:10536,<br /> &quot;participantStartDate&quot;:1316464191126,<br /> &quot;xRefCi&quot;:&quot;271328361659f1&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:10536,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316464191126<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/111328361659f1&quot;<br /> }<br /> },<br /> {<br /> &quot;callControllerIP&quot;:&quot;172.27.98.111&quot;,<br /> &quot;callControllerType&quot;:&quot;Cisco-SIPGateway&quot;,<br /> &quot;ccid&quot;:&quot;0398868736-0000065536-0000005901-0745980426&quot;,<br /> &quot;sessionDuration&quot;:9791,<br /> &quot;sessionId&quot;:&quot;1013283613f5c1&quot;,<br /> &quot;sessionStartDate&quot;:1316464181309,<br /> &quot;sessionState&quot;:&quot;CLOSED_NORMAL&quot;,<br /> &quot;tracks&quot;:[<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1013283613f5c1-TRACK1&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1057&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:559,<br /> &quot;participantStartDate&quot;:1316464190541,<br /> &quot;xRefCi&quot;:&quot;261328361644d1&quot;<br /> },<br /> {<br /> &quot;deviceRef&quot;:&quot;1054&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:9232,<br /> &quot;participantStartDate&quot;:1316464181309,<br /> &quot;xRefCi&quot;:&quot;2513283613f5c1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464187140,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:5822,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464187100,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:5779,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464190456,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:9138,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464190602,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:9278,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464190734,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:9414,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:9791,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:1,<br /> &quot;trackStartDate&quot;:1316464181309<br /> },<br /> {<br /> &quot;downloadUrl&quot;:&quot;http://10.194.118.63:8081/ExportRaw?recording=1013283613f5c1-TRACK0&quot;,<br /> &quot;participants&quot;:[<br /> {<br /> &quot;deviceRef&quot;:&quot;1053&quot;,<br /> &quot;isConference&quot;:false,<br /> &quot;participantDuration&quot;:9791,<br /> &quot;participantStartDate&quot;:1316464181309,<br /> &quot;xRefCi&quot;:&quot;2413283613f5c1&quot;<br /> }<br /> ],<br /> &quot;tags&quot;:[<br /> {<br /> &quot;tagCreateDate&quot;:1316464187100,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:5779,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464181337,<br /> &quot;tagName&quot;:&quot;TrackInactive&quot;,<br /> &quot;tagOffset&quot;:0,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> },<br /> {<br /> &quot;tagCreateDate&quot;:1316464181403,<br /> &quot;tagName&quot;:&quot;TrackActive&quot;,<br /> &quot;tagOffset&quot;:71,<br /> &quot;tagType&quot;:&quot;SYSTEM_DEFINED&quot;<br /> }<br /> ],<br /> &quot;trackDuration&quot;:9791,<br /> &quot;trackMediaType&quot;:&quot;AUDIO&quot;,<br /> &quot;trackNumber&quot;:0,<br /> &quot;trackStartDate&quot;:1316464181309<br /> }<br /> ],<br /> &quot;urls&quot;:{<br /> &quot;rtspUrl&quot;:&quot;rtsp://10.194.118.63/archive/1013283613f5c1&quot;<br /> }<br /> }<br /> ]<br /> &lt;/pre&gt;</div>

Cchetty