search

santhoshpoojari14 / sipservlets

Automatically exported from code.google.com/p/sipservlets
0 stars 0 forks source link

Creating a MESSAGE with a charset=ISO-10646-UCS-2 parameter on Content header corrupts the message #165

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a MESSAGE with a Content: header of 
"text/plain;charset=ISO-10646-UCS-2"
2. Send it
3. The SIP headers section of the MESSAGE is UCS-2 encoded, the body is not

What is the expected output? What do you see instead?
Expected the body to be UCS-2 encoded; instead the headers are.

What version of the product are you using? On what operating system?
First seen on MSS 1.7 FINAL AS5 on CentOS 6.
Reproduced on MSS 1.8 Snapshot on Tomcat 7 (Build 376) on Windows 7

Please provide any additional information below.

Attached is a zip containing a test application. This accepts REGISTERs. When 
alice registers he gets a MESSAGE in UTF-8, when bob registers she gets a 
MESSAGE in UCS-2.

* Deploy the app
* Run the Server SIPp script on port 5060 (this just receives MESSAGE and sends 
200)
* Run the test1 script. This REGISTERs first alice, then bob
* The first MESSAGE is OK, the second MESSAGE is malformed.

The two traces show the signalling. AS5.pcap is on MSS 1.7 Final on JBoss AS5; 
tc7.pcap is 1.8 Snapshot 376 on Tomcat 7.
In both cases the final MESSAGE is malformed, and SIPp does not reply.

Original issue reported on code.google.com by andrew.m...@acision.com on 21 Sep 2012 at 6:29

Attachments:

GoogleCodeExporter commented 8 years ago 
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.

Original comment by andrew.m...@acision.com on 21 Sep 2012 at 6:34

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 19 Oct 2012 at 11:18

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 19 Oct 2012 at 11:18

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 5 Jul 2013 at 7:44

GoogleCodeExporter commented 8 years ago 
Did you try setting the JVM property -Dfile.encoding=UTF-8 as described in 
https://code.google.com/p/sipservlets/issues/detail?id=252 ?

Original comment by jean.deruelle on 18 Apr 2014 at 10:24

GoogleCodeExporter commented 8 years ago 
No I didn't try that, and the test system is now long gone I'm afraid

Original comment by andrew.m...@acision.com on 23 Apr 2014 at 9:54

GoogleCodeExporter commented 8 years ago 
No problem, sorry for the late reply. Closing this ticket as won't fix for now

Original comment by jean.deruelle on 23 Apr 2014 at 9:56

GoogleCodeExporter commented 8 years ago

Original comment by jean.der...@telestax.com on 25 Aug 2014 at 10:53