With SigComp on Boghe client sometimes responds with a SIP rather than SIGCOMP message

[GoogleCodeExporter]

What steps will reproduce the problem?
1.See attached Wireshark logs
2.
3.

What is the expected output? What do you see instead?
Expect Boghe to respond with a SIGCOMP message rather than SIP message.

What version of the product are you using? On what operating system?
2.0.132.811

Please provide any additional information below.

Note Boghe Client on 156.141.115.182 and server on 156.141.115.236.

See the attached Wireshark log (BogheSIPNotSigComp) with a filter of 'sip' look 
for messages 614 (Trying) and 620 (Ringing) in response to message 613 (INVITE).

See also attached Wireshark log (BogheSIPNotSigCompMessageOK) with a filter of 
'sip' look for message 425 (MESSAGE) and message 430 (OK)

Original issue reported on code.google.com by alistair...@gmail.com on 4 Feb 2013 at 3:33

Attachments:

• BogheSIPNotSigComp.pcapng
• BogheSIPNotSigCompMessageOK.pcapng

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 5 Feb 2013 at 4:55

• Changed state: Accepted
• Added labels: SigComp

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 6 Feb 2013 at 10:53

• Changed state: NextRelease

[GoogleCodeExporter]

Fixed by r814

Original comment by boss...@yahoo.fr on 6 Feb 2013 at 12:10

• Changed state: Fixed