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.
The following are the steps I took to upgrade from 4.1(3)SR1 to 7.0(2):On the 4.1(3)SR1 publisher server, I installed and ran the 'CallManager Upgrade Assistant' version 4.3(9) which told me that I had met all of the requirements to upgrade to 7.0(2)...
My management is wanting me to get rid of the certificate error messages when users access the CCMUser website. We are running CUCM 7.0(2).I think I understand the instructions for generating the CSR and uploading the CA generated certificate as wel...
I have Unity Connection 7.0(2) installed and configured to use LDAP sync and LDAP authentication for end users. I can successfully Import users that were synced from LDAP/AD and voice mail functionality works as expected.The users who are imported c...
Is CTA ever going to be upgraded to support Vista? We utilize the NAC framework with WinXP and Win2000 machines for 2.5 years now but with the eventual upgrade to Vista coming around the corner, we are stuck with the apparent lack of CTA for it.Than...
Has anyone ever implemented an automated announcement and/or emergency notification tool that either integrated into CallManager directly or via H.323/SIP/POTS that has the ability to record a greeting and schedule to call outbound to the PSTN to pla...
It wasn't my configuration, it was a bug - CSCsy48064. I am using SSL for LDAP Authentication. If I disable SSL and restart DirSync and IMAP services as the workaround states, it works just fine. I need to get a hold of the ES that fixes this now.
I am not referring to notification emergency personnel when 911 is dialing.I am asking about a tool that would dial out to PSTN destinations and spit out a pre-recorded message.
The calling number is an arbitrary number that I used that is not associated with a subscriber.I am not sure I understand what you are asking me to try here.
Cisco just updated the DST Field Notice for IP Communicator to require an upgrade to 2.0.2 in order to reflect new DST rules:http://www.cisco.com/en/US/customer/products/sw/voicesw/ps1860/products_field_notice09186a00807e0fd9.shtml
