format of the message sent by TServer

[victor]

Hi, can someone please tell me what is the format of the message that is flying between TServer and softphone?

I think there is more to it then just TEvent. Any ideas?

[LeszekM]

This topic is for Genesys guys. They would know for sure.

I suppose a connection between TServer and its clients "contains" only TEvents and nothing else (requests have the same format or at least nearly the same format - that's my guess). User Data and other list attributes (like AttributeExtensions) are encoded into TEvents.

I think this is all when it comes to "voice" TServers. "Other media" TServers use the same TEvents for signalling but the media information (like mail subject, mail body, attachments)  is stored in the Contact Server database. The client applications are able to get this info using "hints" carried in User Data. There is no need for special channel in TServer.

What extra info besides TEvents do you expect to be carried "over the wires"?

Regards,
Leszek

[Adam G.]

I would surmise that Genesys' answer to this would be that it's proprietary information but then again you could use a packet sniffer such as Ethereal (google for it) and look at the data coming across to the port. 

[victor]

I looked at the data packets and there is more to it than just TEvent. I think there is something like TMessage. I will keep you updated as I try to understand this.

[Genecist]

For sure there will be more than the mere TEvent structure...but good luck in deciphering the packets. 

No doubt, Genesys, being one of the more secretive organizations producing the most closed software and documentation I've ever come across...it will be a proprietary protocol.