Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Keith on June 25, 2009, 02:04:20 PM
-
Hi,
once again Genesys is playing a cruel joke on me:
why in the world would sce -d NOT work on my cute and shiny DELL running Windows XP and CME 7.6?
I want to be able to tell DBID of every object, but -d does not seem to do it anymore? Did I get a counterfeat version of Genesys made in China?
-
Try running SCE -d from the config server directory, in a command prompt.
I seen a few machines lately where changing the target of the icon doesn't work.
-
I run a DELL with Windows XP and CME 7.6.
The -d switch works fine for me. :)
-
Dell too at work and does work. CME right?
-
What exactly "sce -d" does ? Where did you find the command line parameters ?
-
Have you tried does this ....go to Program->Genesys Solutions ->Framework -> Configuration Manager ->Start configuration Manager ...there right click and click on create shortcut ...once the short cut is created change the Target as "C:\Program Files\GCTI\Configuration Manager\sce.exe" -d ... ( i mean the full installation path followed by -d )
Regards
Harsh
-
@bounty : look the snapshot
CME 7.6.001.01 works fine with option -d (DELL / VMWare / WinXP SP3 or Win Server 2003)
[img width=640 height=386]http://ups.imagup.com/04/1246637609_cme.png[/img]
-
[quote]What exactly "sce -d" does ? Where did you find the command line parameters ?[/quote]
sce -d turns on the option is CME to display the DBID of each object. So when you open the properties of an object, the DBID appears in the title bar.
The command line parameters (there are not many) are in the Framework documentation
-
how cute is this :D
niceee :)
-
I think I may have come across this, more recently... Unfortunately...
We have a ticket raised with Genesys because some of the switches on CCP+ do not appear to work, either. Bascially, you can try to apply the [b]-port [/b] and [b]-host [/b] switches but the Application in itself is set to read those particular parameters from the Registry. So - the workaround is to update the Registry settings, to reflect the values you want on the switches.
Apparently, this is "cosmetic" and Genesys are looking at it as an FR, rather than an SR...
It's not the exact same scenario as here but it does indicate that perhaps the running parameters and switches do need to be looked at closer by the Genesys Developers...
Tony