Comment #1 on issue 165 by [email protected]: Creating a MESSAGE with a charset=ISO-10646-UCS-2 parameter on Content header corrupts the message
http://code.google.com/p/sipservlets/issues/detail?id=165
Correction: It looks like the headers and the body are UCS-2 encoded. This is not what I saw on our real application. I don't know why it's different on the test application.
