Hi,
I am having a major problem with Genesys Voice Platform SDK (Java) and Unicode. In essense, we get all characters garbled if we do not compiled everything using MS832 encoding, which is scary.
Most of the people here use UTF-8 encoding, so we have developed our Java client application with UTF-8 encoding. Java client application connects to Genesys T-Server using Voice Platform SDK (Java) version 7.2
When softphone connected to T-Server directly attaches attach-data with UTF-8 charset, our server compiled using UTF-8 receives garbled characters from T-Server. If we compile our server with MS832 encoding, and have softphone send us data using MS832 charset, it is fine...
I remember reading that T-Server is encoding neutral and as long as T-Server clients use the same encoding, everything should be fine. But it seems like Voice Platform SDK only supports MS832 encoding, and any client connected to T-Server via Voice Platform SDK gets characters garbled if any other encoding is used between the clients.
For example:
[table border=1]
[table][tr]
[td]client A[/td]
[td]TServer<->Voice SDK to Client B[/td]
[td]client B[/td]
[td]result[/td]
[/tr]
[tr]
[td]UTF-8[/td]
[td]MS832[/td]
[td]UTF-8[/td]
[td]client B output is garbled[/td]
[/tr]
[tr]
[td]MS832[/td]
[td]MS832[/td]
[td]MS832[/td]
[td]client B output is fine[/td]
[/tr]
[tr]
[td]UTF-8[/td]
[td]MS832[/td]
[td]MS832[/td]
[td]client B output is garbled[/td]
[/tr]
[/table]
So, unless everything is done with MS832 , output will always be garbled. This does not make sense, since many systems rely on Genesys as go-between, and it is clear that they cannot all use MS832... So, how in the world do you get a non-MS832 encoding not get garbled when passing through T-Server<-> Voice Platform SDK???
Help!
