Any update on this?! I have this problem too. ... View more

Hi I want to share the problem I had, it was similar but with the server Prime License Manager 10.5 after upgrade from 9.1.1, after I upgraded the server, the service Cisco Tomcat don´t started so I ran the command "utils diagnose test" and I saw the Tomcat error then I collected the Tomcat logs and find a problem with the certificates, so the way I can solve the problem is creating the tomcat certificates so from the CLI of the server I ran the command "set web-security XXX XXX XXX XXX XXX" with the appropiate data and restart the server and problem solved! I hope this help somebody else with the same issue. ... View more

Hi, I have a similar problem with the installation of CUCM 6.1.2 on UCS C240M3 I got the same error, I want to migrate the DB of this version to 10.5 so I need to install this on the UCS server, well the way how I solved is creating the VM manually and choosing the version of Linux to Red Hat Enterprise 3 at 32 bits, also changed the Adapter of the NIC from Flexible to E1000, so when I tried again to install the installation worked fine. I hope this help somebody with the same problem. ... View more

Hi Thanks for the information, this help me a lot, I have the same issue but with some differences, because when I search the error on the log file, I saw 08/25/2014 06:14:49.911 installdb|   DOMErrorReporter::fatalError *ERROR* Fatal Error at file , line 0, column 0  message: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=/usr/local/cm/db/xml/xml/ICS77XX_MRP2XX_display_instance-bri.xml| 08/25/2014 06:14:49.911 installdb|<--DOMErrorReporter::fatalError | When I search the file I couldn´t find it, so I think this could be because I made a booteable ISO from an upgrade from the Cisco Page, so I go to the production server version 6.1.2 and copied the file missing into my lab and run the command "run loadxml" sucessfully, after that everything works great! Thanks in advance for your time to post this. Regards! ... View more

Hi Patrick it seems like you wrote your post a long time ago I did a deep search but I can´t find your post so I can see the script you made, because I have the same problem of Operations error (-7ff5ffff) could you tell me where can I find your script or post? Thanks a lot! ... View more

Ok thank you very much! ... View more

Why don't you try to find on the page of Cisco the Cisco webex social administration guide release 3.1 there come some information about the integration of LDAP remember that if you integrate the ldap whit webex social you must integrate the cucm too good look Sent from Cisco Technical Support Android App ... View more

Hello thank you very much when i Configure the Federation Routing IM and Presence FQDN with the new domain works fine for me. thanks a lot! ... View more

thank you very much you give me the idea and now its working just reinstall the cop file and it works again. =) ... View more

Hi AhmedEl-Eraky, Well maybe it's your version, because you do not try to upgrade to version 8.5.1 SU2 because I update the version and my version of UCCX to stay active 8.5.11002-22 and I have no problem. Try to update and hope it will resolve your problem. Just a question, you have the licensing to allow for a remote monitoring? And if you can, because if you try to have this same thing happens. I found this page to configure remote monitoring http://www.cisco.com/en/US/products/sw/custcosw/ps1846/products_tech_note09186a0080b5e901.shtml Just remember that the supervising officer must be his id with numbers for a remote monitoring agent Thanks. ... View more

Hello I have the same problem but what do i did to resolve the problem is to get out the supervisory agent of the supervisory capability and click save and get in back into the supervisory so when I go to subsystem >> RmCm >> remote monitoring i can see the supervisory agent so i click and assign to a CSQ or the agents that i want to monitor....and there is no more the error.. To see de ID of the CSQ you can perform in two ways one seen in the CAD (Agent Desktop) and see de Device parameter for the CSQ that are you want to monitor and the another way is to make a report and in the print report have the name of the CSQ and in the (x) has a number, that is the number ID of the CSQ that you must enter when the prompt ask. I hope this help you. ... View more

Hi AhmedEl-Eraky i hope my experience help you, when installed the uccx I made an upgrade to SU(2) for 8.5 and i configured the voip monitor service or monitoring silence and do worked properly so i open a TAC case and they tell me that i need to disable the advertise g722 on the device phone of the agents, so i disabled for enterprise parameters and service parameters and for the device phone also i configured the partition of the extensions of the agents and the extension for the supervisory in the same partition and a calling search space so they can reach one to another. And configured to enable  the span to pc ports, PC Voice Vlan Access, PC port enable for the device phone of the agents. And it works like a charm jaja! so i hope this help you.... I copied the check list that the TAC told me for the voice monitor. 1.    Ensure that the CAD and CSD version installed are 8.5.1.214 2.    For the agents phone, please ensure the following things are configured as follows:- a.    There is no shared line for the ICD extension for the agent. b.    Span to PC ports – Enabled c.    PC voice VLAN access- Enabled d.    PC port – Enabled e.    Advertise G.722 codec- Disabled 3.    On the Agents PC: a.    Please ensure there is no antivirus or firewall b.    Check the NIC binding order on the machine is correct, the active LAN card should always be on top. c.    Please check the NIC binding order by running the PostInstall on the agents PC. •    The first screen showed the IP address of the UCCX server, click OK. •    Then it showed the screen for the Cisco Agent Desktop Configuration Setup •    Under the VoIP monitor service, select the appropriate  NIC or IP address under Adapter •    Clicked Apply after selecting the NIC card. •    Logout the agent and login back. 4.    On the Cisco Desktop Administrator, please ensure that the agents MAC address has the desktop based monitoring has the Enable Desktop Monitoring check box checked in case of desktop based monitoring and unchecked in case span based monitoring. I hope this help you...sorry for my english. ... View more