Client exits when sigcomp over udp is enabled on recieving 401 .

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Enable sigcomp.
2.Register a client over udp (phone used sony ericsson Xperia X10 mini android 
1.6)
3.Client exits on receiving 401.

What is the expected output? What do you see instead?
Client should be able to process the 401 and send Register with authentication 
response.

What version of the product are you using? On what operating system?
IM-client/OMA1.0 IMSDroid/v1.0.271 (doubango r479) on android 1.6 (sony 
ericsson xperia x10 mini android 1.6)

Please provide any additional information below.
The 401 is sent over sigcomp, but the server has a special behaviour where it 
does not create urn:uuid type of compartment id for sigcomp, instead it waits 
for the registration to complete successfully and then creates a sigcomp 
compartment id based on the registration call-leg(nothing but a unique number 
in the server used to identify a subscriber). The impact of this is the 401 
will not be compressed, it could even expand in size.
A similar problem was observed with mercuro client.
Please let me know if i can provide any other details like a pcap or log file.

Original issue reported on code.google.com by sourab.d...@gmail.com on 2 Sep 2010 at 9:23

[GoogleCodeExporter]

Before passing the message to the UDVM the transport layer will check whether 
it's a SigComp message or not (magic code=0xF8). The client is prepared to 
receive both SigComp and non-SigComp messages on the same socket.
Wireshark capture will be helpful.

Original comment by boss...@yahoo.fr on 2 Sep 2010 at 7:47

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 26 Oct 2010 at 9:35

• Changed state: Invalid