Friday, January 30, 2015

Use Gmail for your eGain email server

eGain can support Gmail POP and SMTP servers with a little under-the-hood wrench work.

Start by setting up your email alias in eGain Partition Administration (http://egainserver/default) with the following settings:

Incoming Email Alias Settings
Server type: POP3
Server name: pop.gmail.com
User name: the full email address on gmail
Password: the gmail password for this email address
Port: 995
Use SSL: Yes

Outgoing Email Alias Settings
Server type: ESMTP
Server name: smtp.gmail.com
User name: the full email address on gmail
Password: the gmail password for this email address
Port: 587
Use SSL: No


Now you need to disable plaintext authentication and enable StartTLS for this email alias. You must set these options in the database using SQL. Here is the script, just change the @email variable to be equal to the email address of your alias:

DECLARE @email varchar(MAX)
SET @email = 'myEgainAlias@gmail.com'
insert into EGPL_CONFIG_PROPERTY (DOMAIN,NAME,VALUE) values ('dx.alias.'+@email,'mail.smtp.starttls.enable', 'true')
insert into EGPL_CONFIG_PROPERTY (DOMAIN,NAME,VALUE) values ('dx.alias.'+@email,'mail.smtp.auth.plain.disable', 'false')

That's it! You'll still need to assign this alias to a Workflow Start as well as your retriever instance, and restart your retriever (and probably your dispatcher) instance for your partition.

If you want Gmail to be your eGain system's notification email server, you'll need to also run these 3 queries:
insert into EGPL_CONFIG_PROPERTY (DOMAIN,NAME,VALUE) values ('dx.smtp','mail.smtp.starttls.enable', 'true')
insert into EGPL_CONFIG_PROPERTY (DOMAIN,NAME,VALUE) values ('dx.smtp','mail.smtp.auth.plain.disable', 'false')
UPDATE EGPL_PREF_GLOBALSETTINGS SET SETTING_ACT_VAL='587' WHERE SETTING_NAME = 'common.services.dispatcher.mail.notificationemails.smtpport'

Wednesday, January 7, 2015

Disable Cisco Finesse gadget caching


Finesse will cache your gadgets, which can present a problem if you're trying to do gadget development and testing. To turn off caching, add this URL parameter to your Finesse Agent Desktop URL:
nocache=true

So, your login URL will look something like this:
http://finesse-pub.domain.com/desktop/container/?locale=en_US&nocache=true

The easiest way to get the right URL is to browse to your Finesse Agent Desktop login page, then just add "&nocache=true" to the end of the URL. You can do this before or after logging in to Finesse.

Wednesday, December 31, 2014

vCenter Appliance 5.5 - HTML5 VM Console - Could not connect to hostname:7331

VMware vCenter Server Appliance 5.5 has a bug where (after a reboot) the vSphere Web Client works but the VM Console connection page returns a "could not connect" error message. The problem is that the VCSA is not setting one of its JRE environment variables during boot. Here's the fix for it:
1. ssh into the vCenter Appliance as root (turn on SSH in the VCSA admin console at https://hostname:5480 if it's not already on)

2. edit this file:
/usr/lib/vmware-vsphere-client/server/wrapper/conf/wrapper.conf

3. add this line anywhere under # Environment Variables:
set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware

4. restart the vSphere client service with this command:
/etc/init.d/vsphere-client restart

Now, wait a few minutes for vsphere-client to finish initializing (after the command prompt says that it has restarted you still have to wait for it to finish starting up).

That's it! Next time you restart your VCSA, the VM consoles in the vSphere Web Client will work without any intervention.


VMware KB article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2060604

Thursday, December 18, 2014

Wednesday, December 3, 2014

CVP Call Studio 10.5 - RDP user workspaces

If you have CVP Call Studio on a Remote Desktop server where different users need to log in and have their own Call Studio workspaces, you can edit the C:\Cisco\CallStudio\startStudio.cmd file (just right-click > edit the desktop icon for Call Studio) to start Call Studio with a workspace in the user's folder:

start eclipse\eclipse.exe -data "%userprofile%\workspace" -vm eclipse\jre\bin\javaw.exe

CVP Call Studio 10.5 - Invalid Configuration Location

Cisco's CVP Call Studio 10.5 will complain about not being able to lock the configuration file if your user account doesn't have write privileges on the configuration folder. Here is a (poor) screenshot of the error:


To work around this, do as the message says and add this line to the end of your eclipse.ini file (located in C:\Cisco\CallStudio\eclipse\):
-Dosgi.locking=none

You'll need to have permission to edit that file, of course, so any user seeing the error message will likely not have that privilege.

CVP Call Studio 10.5 - Call Studio plugins not loading

I found out through trial and error that CVP Call Studio 10.5 must be installed with Windows UAC turned off. If you don't (at least, on Windows Server 2008 R2), Call Studio will open and only show the standard Eclipse features with no Call Studio projects or views available. This is due to it not loading the Audium plugins. The activation window will also not pop up at startup during the 30-day trial license that it comes with. Only uninstalling and reinstalling with UAC off will fix this issue.