Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Unable to log on to the Personal Communication Assistant in Cisco Unity 4.x with the error message "Unable to contact server. Try logging on again in a few minutes. if the problem persists, contact your Cisco Unity administrator."
On Cisco Unity 4.x with the Microsoft Exchange server offbox, when a subscriber attempts to log on to the Personal Communication Assistant (PCA), it fails and the Unable to contact server. Try logging on again in a few minutes. if the problem persists, contact your Cisco Unity administrator error message appears, even though in the web.xml file, the unityurl parameter has the IP address instead of the hostname.
In order to resolve this issue, first make sure the Cisco Unity Server has Cisco Unity Inbox subscribers under the licensing wizard , which is the required License feature in order to use the CiscoPCA feature by the users. Also ensure that Cisco Unity Inbox (Visual Messaging Interface) is checked, under Class of Service > Features, for those subscribers that require it.
After the appropriate licenses on the Cisco Unity Server are ensured, other possible reasons are the Cisco Unity server is down or a network connection has failed.
Recommended Action: Confirm that the Cisco Unity server runs, and that all network connections function properly. Restart the Cisco Unity server, as necessary. In order to verify that the problem is caused by a Cisco Unity server or a network failure, you can try to switch to an available failover Cisco Unity server in order to see whether the same error message occurs on the failover server. Alternatively, you can change the unityurl configuration setting to point to a Cisco Unity server that runs, and then restart the Tomcat service.
Possible Cause: AvXml directory security is not set correctly in IIS; Anonymous access can possibly be disabled or secure connections can be enabled. In order to confirm this is the case, open the ciscopca_log.txt, ciscopca_event_log.txt, or ciscopca_diags_log.txt files located in the CommServer\Cscoserv\Tomcat\Logs directory and search for an IOException message that mentions that HTTP returns a code 401 or 403. If such a message exists, directory security is not set correctly in IIS.