Genesys CTI User Forum
Genesys CTI User Forum => Genesys-related Development => Topic started by: Cuore_2003 on November 18, 2008, 03:49:35 PM
-
Dear colleagues.
We have an obsolete agent desktop application developed with T-Lib.
Now, we want make an implementation with outbound solution. My doubt is about SDK, I mean: what SDK I need if we want to develop with .net?
Voice platform SDK? Or Genesys Desktop .NET? or...
Are these SDKs licensed?
Thanks in advanced and BR!
-
Hi, I suppose you can use any of that. I participated in developing Customer Care Framework application on .NET. We've choose Genesys Desktop Application Blocks. You can find example VoiceSample at Quick Start Sample directory. About SDK, it's a little bit difficult to build applications on it :)
-
Yes a little bit more difficult but more power on what you can do.
You have:
1. Platforms SDK: They talk directly to the Genesys Servers like old TLIB and ActiveX did.
2. Integration SDK: This one needs a middle server named GIS (Genesys Interaction Server) and you use blocks of code from this, however you are limited to the block codes available.
3. Genesys Desktop .Net is a "block" of GIS.
You still can try get Genesys ActiveX Desktop Toolkit to develop in VB6 if you prefer. It is easier and much more documented even here with a lot of examples and code we have posted.
-
[quote author=cavagnaro link=topic=3584.msg15239#msg15239 date=1227122562]
Yes a little bit more difficult but more power on what you can do.
You have:
1. Platforms SDK: They talk directly to the Genesys Servers like old TLIB and ActiveX did.
2. Integration SDK: This one needs a middle server named GIS (Genesys Interaction Server) and you use blocks of code from this, however you are limited to the block codes available.
3. Genesys Desktop .Net is a "block" of GIS.
You still can try get Genesys ActiveX Desktop Toolkit to develop in VB6 if you prefer. It is easier and much more documented even here with a lot of examples and code we have posted.
[/quote]
I don't want to be rude Cavagnaro, but I need to correct you. GIS is Genesys INTEGRATION Server, not Interaction Server.
Luk.
-
:P yup correctly, thanks ;D will have to make a little memo with all those abbreviations
-
[quote author=Cuore_2003 link=topic=3584.msg15203#msg15203 date=1227023375]
Dear colleagues.
We have an obsolete agent desktop application developed with T-Lib.
Now, we want make an implementation with outbound solution. My doubt is about SDK, I mean: what SDK I need if we want to develop with .net?
Voice platform SDK? Or Genesys Desktop .NET? or...
Are these SDKs licensed?
Thanks in advanced and BR!
[/quote]
Hi, Cuore,
it really does not matter one way or another and mainly has to do with preference. We looked at both .NET and Platform SDK and decided that platform SDK would be the base for our products, because it has connection directly to T-Server, does not depend on any other componenets and at the end of the day, from programming perspective, we do not see much time difference in developing using either .NET or Platform.
-
Hi,
Genesys has announced the End Of Life (EOL) of AgentDesktop .NET Toolkit recently so this SDK is "out of game" now.
R.
-
What do you mean? What are we supposed to use?
-
I believe he means that GIS client, Platform SDK and GIS are still available, right René?
-
Hi,
AgentDesktop .NET Toolkit is set of .NET visual components and non-visual classes that encapsulates communication with GIS. It was intended for RAD (Rapid Application Development) of custom agent desktop. Only this product is now in EOL phase. Other SDKs - Platform SDK, Interaction SDK etc. and GIS are still available!
In case of development of agent application using .NET Framework there two possibilities:
- Platform SDK for .NET
- Web Services SDK (Agent Interaction, Configuration, Statistics) using Genesys Integration Server (GIS)
R.
-
Seriously, sometimes I wonder what Genesys is thinking... GIS is no where fast enough judging from my experience to handle multiple realtime requests and platform sdk is the only way to go.
-
I don't completely disagree with you, but 7.6 GIS is certainly better performing and when you have the luxury of being able to throw hardware at it then good load-balancing design can certainly improve performance.
It's certainly a product that requires careful planning, and if you have vast numbers of agents with load spread across multiple sites then it's probably not the best solution for you.