Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-2.0.0.FINAL
Roadmap-Fix
New 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
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.
Attachments:
ContentIssue.zip 7.0 KB
