Curious about multi-site routing

[victor]

Hi, 

I have a question about creating something close to Network Overflow Manager for multi-site environment.

First, the concept:

Develop an application which would allow exchange of attach data between two Genesys T-Servers without the need for multi-site license.

How:

Use Genesys ActiveX component and/or Genesys SDK to connect two both T-Server and track EventRouteUsed and EventRouteCallRequest and use attributes such as ANI, OtherDN, ThisDN and such to identify calls and attach the data from the original call. The only thing we cannot do is set the call on the second call to the same connection ID.

My concern is simple - we know we can do it using Genesys Active X but would Genesys still require multi-site license if we did that? any clues?

(and if you are from Genesys, if you are reading this, please do reply!)

Best regards,
Vic

[bublepaw]

Hi,

We used similar solution written in C when 2 customers did want to have calls trasfered with AD between sites but didn't want to have any changes in configuration in their separate Genesys enviroments.
As long as we don't post any problems related to this mechanism, Genesys dosen't care about multisite license. I thnik that this is the same situation as with URS - You can write Your own if You need more seats but it is not supported by Genesys so it's up to You to keep it running when smt changes in TServers.

But of course this my private opinion ( I am not from Genesys )

[victor]

I was hoping the same thing, but recently Genesys has been really weird regarding license. Not only they now license SDK (which was free in form of ActiveX and came along with Framework), but are not demanding license fees for anything that uses ActiveX!

For example, we have developed VoIP recorder that uses Genesys ActiveX to track agent status, and now they demand that we pay recording(or was it monitoring?) license, even though we have purchased framework and these DNs are full-blown agent seats, meaning they are not free in a first place and are included with the framework license. They claim that since we are using Genesys ActiveX on these DNs for other things than softphone, it is not covered by the basic framework license.

Frankly, I really do not get it. It is the same DN that is tracked by softphone that gets the same events. Why pay more for something that is already covered by softphone? So, if I set softphone as a proxy and instead of using Genesys activeX to get the events for our recorder, I would send the events from softphone to the recorder, would I still be required to pay the recording license? (I am sure they would argue that yes...)

But, if you think of it, it is absurd. Because, in a way, right now, softphone is used by many call centers and data stored from softphone into DB is used later to look at agent performance. And this is done without purchasing the reporting license...So, in a way, softphone is used as a reporting proxy as well.

I really do not like how companies are starting to charge for functionality that is developed by the user. This new SDK "adaptor" license is exactly that - it is a creative way for Genesys to charge developers for their creativity: no longer are they (Genesys) content with just charging per seat per application that they develop, but now they also are starting to charge for what we (users) develop as well. I really do not understand why it costs more to use the same DN for call recording and call control as opposed for call control only. I do not recall agreeing to profit-sharing scheme with Genesys, do you?

Best regards,
Vic

[cavagnaro]

What! Appart from their high prices they want more money?? This is ridiculous! Whant they want? Us to begin to search for an alternative? and there are many right now. If Genesys keeps on this they will want to charge you event by created agent that is not necesarilly logged in! Come on!
This world economy shit...

[victor]

Oh, don't tempt me on starting to develop an alternative to T-Server. I am REALLY tempted!!! With Avaya link manual, it is actually pretty simple. Genesys pretty much paved the way, and if there is a really big need for it, give me three months and I will give you T-Server Alpha.

But, you know, Genesys is a pioneer in CTI and I do like most of their products. I think they do have the talent and expertise to get things working and keep them working when something goes wrong, so in a long term, I think I would rather have them continue to develop their product as they were doing until now. The problem is that we need to have them address their thinking on the licenses. It is simply not right.

Vic

[cavagnaro]

Wo that would be nice! To see and test at least!  Victor you are a really guru dude!
Can't wait to see it.
Will it be only for Avaya? Or made for another PBX's as Nortel or Alcatel??

[victor]

Cavagnaro,

you know, I think we should do it.

I will need to come up with Avaya PBX and its link and see if TSAPI is similar to that of Genesys, because if it is (and I suspect very little difference), I think we can easily make this a walk in a park. AES is pretty expensive this days. Does anyone have a good contact in Avaya we can approach regarding AES signaling documentation?

Best regards,
Vic