McDewey

For Connect Server, enter the IP address of the Finesse server. 11. If the Connection Security drop-down menu is present, choose Use encryption if available. 12. Click Save. Connect port and File transfer proxies should be filled in automatically (5222 should appear in the Connect port field). Note When connecting to the secure port 5223: 1. Add the Finesse Notification Service certificate in the Pidgin certificate manager. Finesse Notification Service shares the same certificate with Cisco Finesse Tomcat. 2. To download the certificate: a. Sign in to the Cisco Unified Operating System Administration through the URL (https://FQDN:8443/cmplatform, where FQDN is the fully qualified domain name of the primary Finesse server and 8443 is the port number). b. Click Security > Certificate Management. c. Click Find to get the list of all the certificates. d. In the Certificate List screen, choose Certificate from the Find Certificate List where drop-down menu, enter tomcat in the begins with option and click Find. e. Click the FQDN link which appears in the Common Name column parallel to the listed tomcat certificate. f. In the pop-up that appears, click the option Download .PEM File to save the file on your desktop. 3. In the Pidgin Certificate Manager, go to the Connection Security drop-down menu and choose Use old-style SSL. 4. In the Connect Server field, enter the FQDN of the Finesse server. Note The XMPP logo next to the agent's name becomes active (is no longer dimmed). To see event messages in Pidgin, open the XMPP Console. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 17 Lab Development Environment Validation with Cisco FinesseWeb Services APIs Pidgin for Windows