Guys,
this sounds silly, but I cannot figure out how to send a TSendUserEvent to a remote T-Server’s DN without registering to that T-Server. I would think that it would be possible to do it using built-in ISCC functionality…
any ideas?
Vic
Hi Vic,
Why would you want to send user event on behalf DN which is not under your control and based on what input?
What is the call scenario?
e.
3 Likes
I am using Communication DN to exchange messages between different applications.
And now, I need to somehow send the message to a CommunicationDN the remote T-Server.
I guess, I can make a second TExtension and register to Remote T-Server as well; however, if there is a way for me to send a UserEvent to a DN on remote T-Server, I would be able to just keep one TConnection and use built-in multi-site functionality that Genesys already has.
Vic
No, there is nothing like this. Even OCS is communicating with third party apps using multiple DNs configured against multiple TServers in multisite env.
e.
Why, oh why, would I beg to differ… I just feel like there is a way to do it and I am not just thinking about it…
Perhaps a creative use of RequestDistributeEvent?
1 Like
But Vic, by basic architecture how can TServer will know where to send the Event To if that TServer is not monitoring that DN, something like DNB@TServerFarLand doesn’t work…
The idea however is interesting
TServers dont/cant register for each others DNs like OCS or Statserver do - which would break your model of communication by comDN, so I very much doubt this would work in the way you want it to.
I would have to leaf through the SDK but I bet there would be something in there to help you out.
1 Like
I am looking through T-Library SDK 7.2 C Developer’s Guide (I found it much more comprehensive than other documents available out there till now… at least to my liking) and I thought TSendUserEvent would be my best bet.
TSendEvent has TServer server member; however, it is a local handle for T-Server, thus unless you are connected directly, nothing happens…
I really think Genesys must have thought of a scenario where you might need to send messages to other T-Servers connected to your T-Server simply because until now, pretty much everything I have ever wanted to do was already there in place for me to just call and get it done…
Maybe TLib SDK is not enought, today I have been talking to a Genesys guy and mentioned a SMS (not the text messages) API, for what I understood was to control in a deeper way some interactions. Will try to get more info and see if it fits you Vic.