Not a question or an answer... But some advice on a curious "anomaly" with CCPulse+ start up parameters...
I have previously advised that anyone who wants to start CCPulse "automatically" (for a "lock down") should use Command Line conventions, such as:
SET CCPULSE_ACCESS=COMMAND_LINE
SET HOSTNAME=[color=blue]hostname[/color]
SET PORT=[color=blue]port number[/color]
SET APPLICATIONNAME=[color=blue]ApplicationName[/color]
SET USERNAME=[color=blue]Username[/color]
SET PASSWORD=[color=blue]Password[/color]
C:[color=blue]<path to...>[/color]CallCenter.exe -host %HOSTNAME% -port %PORT% -user %USERNAME% -pwd %PASSWORD% -app %APPLICATIONNAME%
____________________________________________
[b][color=red]If this is you... then please read on...[/color][/b]
____________________________________________
- I [i]believed [/i] this to work based on the parameters set. Unfortunately, I'm now not so sure...
One of the guys here has spotted that the HOST and PORT entered in the command line arguments within the script may not be used for the log in - instead the Registry entries are read off. If you have more than one environment (Development or a Pre-Production area, perhaps) you can test this for yourself:
View the Registry keys, at:
[color=blue]HKEY_CURRENT_USER\Software\GCTI\CallCenter\LoginInfo\Host1 & Port1
HKEY_CURRENT_USER\Software\GCTI\CallCenter\CFGSERVER\Host & Port[/color]
Create and run your script to start CCPulse+ using a different HOST and PORT to those in the Registry...
Once CCPulse+ has opened, check the Environment Settings - they will match the Registry - [b]not [/b] the HOST and PORT you entered in your Command Line arguments.
We've also checked this with NETSTAT and CCPulse+ appears to log in using the Registry Keys for HOST and PORT, not the Scripted ones...
So, if you are using the command line method to "lock down" access to CCPulse+ and you are using a different HOST and/or PORT from previous CCPulse+ sessions, make absolutely certain that your Registry Keys are updated to the values you want them to be, before applying these arguments, since HOST and PORT appear to be ignored.
The problem I can see here is if you want to move your CCPulse+ Users to a new HOST or PORT, for a Config Proxy and you have followed all of the advice from either me or Genesys, then you may not be aware that all of your Users are still using the original HOST and PORT, since the Registry has not been updated.
PS: This also makes me ask "why bother setting the parameters for HOST and PORT using [color=blue]-host [/color] and [color=blue]-port [/color] on the Command Line if they do not work...?" - an SR is open with Genesys...
Tony
PPS: Thanks to Milan and Phil!
