Client Error: Client requests constantly result in "503 Service Unavailable" Error

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
Line 21: Line 21:
|-
|-
! '''Release'''  
! '''Release'''  
-
| Release 8.5(3), Release 9.0(1) 
+
| Release 8.5(3), Release 9.0(1), Release 9.1(1)
|-
|-
! '''Associated CDETS #'''  
! '''Associated CDETS #'''  
Line 29: Line 29:
<br>&nbsp; <br>
<br>&nbsp; <br>
-
[[Category:Cisco_Finesse,_Release_8.5]]  
+
[[Category:Cisco_Finesse,_Release_8.5]] [[Category:Cisco_Finesse,_Release_9.0]]&nbsp; [[Category:Cisco Finesse, Release 9.1]]
-
 
+
-
[[Category:Cisco Finesse, Release 9.0]]
+

Revision as of 20:46, 4 December 2012

Client requests result in "503 Service Unavailable" Error

Problem Summary All client requests receive the following response: "503 Service Unavailable".
Error Message 503 Service Unavailable
Possible Cause Finesse is unable to connect to either the Cisco Finesse Notification Service or the CTI server on Unified CCE.
Recommended Action
  1. Make sure that the Cisco Finesse Notification Service is running. Access the CLI and run the command "utils service list". 
  2. Check that the primary host/port and/or backup host/port are configured in the Server Settings gadget in the Finesse Administration Console, and that at least one of these CTI servers is up and running.
  3. Make sure that the Finesse server is restarted after making the admin changes.
  4. Check the CTI server logs to see if the OPEN_REQ is coming through from Finesse and to see if or why it is failing.
Release Release 8.5(3), Release 9.0(1), Release 9.1(1)
Associated CDETS # None.


 
 

Rating: 0.0/5 (0 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Client_Error:_Client_requests_constantly_result_in_%22503_Service_Unavailable%22_Error"
Personal tools