Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Here is my situtation - Brand new 9.1.x cluster. LDAP was not ready, so local users we configured so that I could import the phones. In previous versions of CUCM, once LDAP intergation was enabled, the existing local users would be replaced by the ...
I have CUCM 9.1 and a standalone ELM server on the same UCS box. I migrated the licenses and everthing was running and licensed. I did a DRS backup of ELM and shutdown the server on UCS1. I built a fresh copy of ELM with the same IP, hostname, etc...
I have just upgraded from CUPS 7.0 to 8.0(2). I have upgraded the CUPC client from 7.x to 8.x. On the server I have started pretty much all of the new services except for the Cisco UP XCP Message Archiver and the Cisco UP XCP XMPP Federation Connec...
Trying to get CUPC Desk Phone Control working. Everything else seems to be working fine. Logging in, Controlling IP Communicator via CUPC, Searching LDAP directory, etc. I am using CUPS version 7.0.8, CUPC 7.1, CUCM 8.0.3. CUCM is using local use...
I have an existing 2921 CME/CUE version 7.x which currently has a PRI to the PSTN. I am trying to switch over to a SIP trunk provided by XO Communications. Right now my DID numbers only match the last two digits of my ephone-dn number. For example...
Nevermind. The Cisco UP XCP Directory Service (according to TAC) is only for connecting to an XMPP LDAP directory. The real issue was that somebody had chaged the password for the LDAP account that I was using to sync to AD.
I opened up a TAC case on the issue and this is what we found out:first of all, CUPS 7.x is NOT officially supported with CUCM 8.x, however we did get it working.In this enviornment I am pointing CUPS to AD, but I'm not doing AD integration with CUCM...
I'm having the same problem on Windows 2008 R2. I read on the Arc Solutions forum that (at least as of August 16th of this year) that 2008 R2 isn't current supported. My plan is to just install it on Windows 2003 server.
