Hi Maheshwar,   Thank you for your query. Please find my response below: 1> Do we support recording with HCS environment and which 3rd party vendors are validated with HCS based call control 10.1.1? Answer: Whether you use a standalone UCM cluster, UCCE or HCS, call recording would be supported across the board in the same manner. Please refer to the following link: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/hcs-cc/10_0_1/Install_and_Config/CHCS_BK_ICC270D0_00_installing-and-configuring-cisco-hcs/CHCS_BK_ICC270D0_00_installing-and-configuring-cisco-hcs_chapter_011.html#CHCS_RF_T1105284_00   Option Notes Recording All Recording applications that are supported by Unified CCE are supported on HCS for CC. For details, see Recording section in Agent and Supervisor Capabilities.   With respect to which 3rd party vendors have been validated, marketplace.cisco.com is a good place to crosscheck this info. You will find a Cisco Compatible Logo against the partners listed there. The logo is used to signify that the PARTNER product has undergone technical interoperability testing with the Cisco product specified. The interoperability testing is conducted by a third party laboratory based on testing criteria set forth by Cisco. PARTNER is solely responsible for the support and warranty of its product. Placement of the PARTNER product or information pertaining thereto, on the Cisco Marketplace website does not constitute an offer to sell the PARTNER product in any way. For further information on the PARTNER products, please visit the PARTNER company website. Please refer to the following link and use the search field under Collaboration Technology: https://marketplace.cisco.com/catalog/search?utf8=%E2%9C%93&search[q]=&search[technology_category_ids]=23%2C24%2C197%2C1940%2C1941%2C1921%2C1576%2C1897%2C1983%2C2418%2C26%2C198%2C1904&search[order]=tier&per_page=20&_=1421663854257&ts=1421663855441   2> Which end points are supported for recording via HCS call control? Answer: The following link should help clarify this: http://solutionpartner.cisco.com/web/sip/wiki/-/wiki/Main/Unified+CM+Silent+Monitoring+Recording+Supported+Device+Matrix   Please let us know if you have any follow up questions. Hope this is helpful.   Regards, Harmit Singh. ... View more

HI Chandra, Chris, Glad I could help :-) See you guys around. -- Regards, Harmit. ... View more

A couple of things: 1> You need to configure " allow-connections sip to sip" under "voice service voip" before you can configure media flow-around. 2> Ensure your IOS supports the command and where you would like to configure it. A couple of links to refer to: http://www.cisco.com/en/US/docs/ios-xml/ios/voice/cube_proto/configuration/15-2mt/voi-media-flwaroun-sip.html http://www.cisco.com/en/US/docs/ios/12_3t/voice/command/reference/vrht_m1_ps5207_TSD_Products_Command_Reference_Chapter.html#wp1405588 HTH. -- Regards, Harmit. ... View more

+5 to Nishant, very good point, another thing to ensure it is same as rest of the cluster's, else that node will not participate in replication. -- Regards, Harmit. ... View more

Hi Sankar, Both reports are full of errors and reveal that there are connectivity / network issues between all these nodes. You need to make sure all 3 nodes are running exactly the same version as well ( you can check this by running "show version active" from the CLI of each of these nodes and compare). I see you used unrestricted media for one of the Subscribers. Are the other 2 nodes also installed with unrestricted version? Worth checking both these things. Unified CM Version Source has failed due to source on 152.63.1.100 timing out Source has failed due to source on 172.27.210.5 timing out The CUCM Version on all servers do not match View Details Server CUCM Version 152.63.1.100 Source has failed due to source on 152.63.1.100 timing out 172.27.210.5 Source has failed due to source on 172.27.210.5 timing out 152.63.1.19 cm-ver-8.6.2.23900-10  Unrestricted -- Regards, Harmit. ... View more

Hi Sankar, Please generate and upload the latest reports from Unified Reporting Tool: Unified CM Cluster Overview Unified CM Database Staus -- Regards, Harmit. ... View more

Hi Sankar, Sounds like the informix DB is not up on that node. I would check "utils service list" and ensure A Cisco DB and A Cisco DB Replicator services are up. -- Regards, Harmit. ... View more

Additionally, you can refer to the following links: https://supportforums.cisco.com/community/netpro/collaboration-voice-video/ip-telephony/blog/2012/10/26/understanding-cucm-dbreplication-runtimestate https://supportforums.cisco.com/docs/DOC-13672 -- Regards, Harmit. ... View more

Hi Sankar, Offline status is seen when the syscdr database is missing on that node. It doesn't necessarily mean that there is an issue with that node itself. It could be the Publisher or the other Subscriber as well. The reason for this is because of the full mesh architecture of the database in a cluster. What I would do is get to the bottom of it by: Taking a look at the Unified Reporting Tool reports - CM Summary and Database Status. These reports will tell you things like - connectivity between the nodes, entries in the cmhost, rhost and sqlhost tables, what are the entries in the syscdr db, etc just to name a few. Depending on the same, I would proceed forward with troubleshooting or corrective actions of running the appropriate DB commands on the cluster. But that's just how I troubleshoot db issues. If you're looking for direct steps to try to fix this, you can follow the stop, drop and roll process as below: 1> Run "utils dbreplication stop" on both Subscribers (can be done at the same time). Wait for it to complete. It can take ~5-10 minutes. 2> Run "utils dbreplication stop" on the Publisher. Wait for it to complete. It can take ~5-10 minutes. 3> Run "utils dbreplication dropadmindb" on the Publisher. Wait for it to complete. It can take ~5-10 minutes. 4> Run "utils dbreplication dropadmindb" on both Subscribers (can be done at the same time). Wait for it to complete. It can take ~5-10 minutes. 5> Run "utils dbreplication reset all" on the Publisher. Monitor the progress using "utils dbreplication runtimestate" on the Publisher. It can take anywhere from 45 minutes to many hours depending on size of the DB, network connectivity (WAN), etc. Hope this helps. -- Regards, Harmit. ... View more